You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
(1) |
Oct
|
Nov
|
Dec
(6) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
(11) |
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
(4) |
Aug
(2) |
Sep
(1) |
Oct
|
Nov
(3) |
Dec
|
2008 |
Jan
(3) |
Feb
(8) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
(2) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
(3) |
Oct
|
Nov
(4) |
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(2) |
From: SourceForge.net <no...@so...> - 2010-12-21 19:54:06
|
Support Requests item #3141375, was opened at 2010-12-21 20:07 Message generated for change (Comment added) made by lukas_theussl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497854&aid=3141375&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: brian hughes (madderscience) Assigned to: Nobody/Anonymous (nobody) Summary: documentation update needed for rpm-maven-plugin Initial Comment: apologies in advance as I have undoubtedly selected the wrong category and everything else for this issue. rpm-maven-plugin documentation at http://mojo.codehaus.org/rpm-maven-plugin/params.html does not mention that the plugin supports: <autoProvides>yes|no</autoProvides> (default yes) <autoRequires>yes|no</autoRequires> (default yes) The actual feature does work. It just does not appear to be documented. I had to download the source to figure out that the capability to control these properties within the spec file was supported and how to do it. I am using rpm-maven-plugin 2,0.1 and that was the source code version I downloaded to verify that these properties are supported. ---------------------------------------------------------------------- >Comment By: Lukas Theussl (lukas_theussl) Date: 2010-12-21 20:54 Message: Wrong project, see http://mojo.codehaus.org/rpm-maven-plugin/issue-tracking.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497854&aid=3141375&group_id=61626 |
From: SourceForge.net <no...@so...> - 2010-12-21 19:07:51
|
Support Requests item #3141375, was opened at 2010-12-21 11:07 Message generated for change (Tracker Item Submitted) made by madderscience You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497854&aid=3141375&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: brian hughes (madderscience) Assigned to: Nobody/Anonymous (nobody) Summary: documentation update needed for rpm-maven-plugin Initial Comment: apologies in advance as I have undoubtedly selected the wrong category and everything else for this issue. rpm-maven-plugin documentation at http://mojo.codehaus.org/rpm-maven-plugin/params.html does not mention that the plugin supports: <autoProvides>yes|no</autoProvides> (default yes) <autoRequires>yes|no</autoRequires> (default yes) The actual feature does work. It just does not appear to be documented. I had to download the source to figure out that the capability to control these properties within the spec file was supported and how to do it. I am using rpm-maven-plugin 2,0.1 and that was the source code version I downloaded to verify that these properties are supported. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497854&aid=3141375&group_id=61626 |
From: SourceForge.net <no...@so...> - 2010-11-18 09:39:08
|
Feature Requests item #3111339, was opened at 2010-11-18 08:39 Message generated for change (Comment added) made by lukas_theussl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497856&aid=3111339&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: findbugs Group: None >Status: Closed >Resolution: Wont Fix Priority: 5 Private: No Submitted By: fazend.com () Assigned to: Nobody/Anonymous (nobody) Summary: log bugs/errors/warnings to console Initial Comment: Would be very convenient if maven-findbugs-plugin can protocol everything found to console. See also: http://stackoverflow.com/questions/1263409 ---------------------------------------------------------------------- >Comment By: Lukas Theussl (lukas_theussl) Date: 2010-11-18 10:39 Message: Please file this at http://jira.codehaus.org/browse/MFINDBUGS ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497856&aid=3111339&group_id=61626 |
From: SourceForge.net <no...@so...> - 2010-11-18 07:39:53
|
Feature Requests item #3111339, was opened at 2010-11-18 07:39 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497856&aid=3111339&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: findbugs Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: fazend.com () Assigned to: Nobody/Anonymous (nobody) Summary: log bugs/errors/warnings to console Initial Comment: Would be very convenient if maven-findbugs-plugin can protocol everything found to console. See also: http://stackoverflow.com/questions/1263409 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497856&aid=3111339&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-11-12 14:29:45
|
Bugs item #2894697, was opened at 2009-11-09 11:35 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2894697&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: dbunit Group: None >Status: Closed >Resolution: Rejected Priority: 5 Private: No Submitted By: Mykola Golubyev (mykolagolubyev) Assigned to: Jeff Jensen (jeffjensen) Summary: INFO logs in err stream Initial Comment: Maven db-unit plugin output appears to be in error stream instead of normal output. So every continuous integration server treat the following message as the error. Please investigate. 938 [main] INFO org.dbunit.database.DatabaseDataSet - database name=Oracle database version=Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options database major version=10 database minor version=2 jdbc driver name=Oracle JDBC driver jdbc driver version=10.2.0.3.0 jdbc driver major version=10 jdbc driver minor version=2 ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2009-11-12 08:29 Message: You are using Maven 2. These are Maven 1 plugins. See this page for Maven 2 plugins: http://maven.apache.org/plugins/index.html ---------------------------------------------------------------------- Comment By: Mykola Golubyev (mykolagolubyev) Date: 2009-11-12 06:54 Message: org.codehaus.mojo:dbunit-maven-plugin:1.0-beta-3 Maven version: 2.0.10 Java version: 1.5.0_17 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2009-11-11 17:01 Message: What Maven version and plugin version are you using? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2894697&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-11-12 12:54:07
|
Bugs item #2894697, was opened at 2009-11-09 19:35 Message generated for change (Comment added) made by mykolagolubyev You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2894697&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: dbunit Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mykola Golubyev (mykolagolubyev) Assigned to: Jeff Jensen (jeffjensen) Summary: INFO logs in err stream Initial Comment: Maven db-unit plugin output appears to be in error stream instead of normal output. So every continuous integration server treat the following message as the error. Please investigate. 938 [main] INFO org.dbunit.database.DatabaseDataSet - database name=Oracle database version=Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options database major version=10 database minor version=2 jdbc driver name=Oracle JDBC driver jdbc driver version=10.2.0.3.0 jdbc driver major version=10 jdbc driver minor version=2 ---------------------------------------------------------------------- Comment By: Mykola Golubyev (mykolagolubyev) Date: 2009-11-12 14:54 Message: org.codehaus.mojo:dbunit-maven-plugin:1.0-beta-3 Maven version: 2.0.10 Java version: 1.5.0_17 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2009-11-12 01:01 Message: What Maven version and plugin version are you using? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2894697&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-11-11 23:01:56
|
Bugs item #2894697, was opened at 2009-11-09 11:35 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2894697&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: dbunit Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mykola Golubyev (mykolagolubyev) Assigned to: Jeff Jensen (jeffjensen) Summary: INFO logs in err stream Initial Comment: Maven db-unit plugin output appears to be in error stream instead of normal output. So every continuous integration server treat the following message as the error. Please investigate. 938 [main] INFO org.dbunit.database.DatabaseDataSet - database name=Oracle database version=Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options database major version=10 database minor version=2 jdbc driver name=Oracle JDBC driver jdbc driver version=10.2.0.3.0 jdbc driver major version=10 jdbc driver minor version=2 ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2009-11-11 17:01 Message: What Maven version and plugin version are you using? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2894697&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-11-09 17:35:11
|
Bugs item #2894697, was opened at 2009-11-09 19:35 Message generated for change (Tracker Item Submitted) made by mykolagolubyev You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2894697&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: dbunit Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mykola Golubyev (mykolagolubyev) Assigned to: Jeff Jensen (jeffjensen) Summary: INFO logs in err stream Initial Comment: Maven db-unit plugin output appears to be in error stream instead of normal output. So every continuous integration server treat the following message as the error. Please investigate. 938 [main] INFO org.dbunit.database.DatabaseDataSet - database name=Oracle database version=Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options database major version=10 database minor version=2 jdbc driver name=Oracle JDBC driver jdbc driver version=10.2.0.3.0 jdbc driver major version=10 jdbc driver minor version=2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2894697&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-09-04 14:14:39
|
Bugs item #2851027, was opened at 2009-09-04 04:51 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2851027&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: findbugs Group: None >Status: Closed >Resolution: Rejected Priority: 7 Private: No Submitted By: Mircea Markus (mircea_markus) >Assigned to: Jeff Jensen (jeffjensen) Summary: findbugs report generation failure Initial Comment: when running 'mvn findbugs:check' following warn message is output: [INFO] Adding Source Directory: /Users/mmarkus/code/ispn/trunk/core/target/classes [java] The following classes needed for analysis were missing: [java] javax.annotation.Nonnull [java] Missing classes: 1 <?xml version="1.0" encoding="UTF-8"?> <BugCollection version='1.3.9' threshold='' effort='min'><Error></Error><Project><SrcDir>/Users/mmarkus/code/ispn/trunk/core/src/main/java</SrcDir></Project></BugCollection>[INFO] [findbugs:check {execution: default-cli}] Then the report does not contain *any* result of the failure at all, even though there are issues that findbugs can report. I've attached a simple test, just go to core and run 'mvn findbugs:check' ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2009-09-04 09:14 Message: You are using Maven 2. This is a Maven 1 findbugs plugin.. Go here instead: http://mojo.codehaus.org/findbugs-maven-plugin/2.0.1/issue-tracking.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2851027&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-09-04 09:51:44
|
Bugs item #2851027, was opened at 2009-09-04 12:51 Message generated for change (Settings changed) made by mircea_markus You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2851027&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None >Priority: 7 Private: No Submitted By: Mircea Markus (mircea_markus) Assigned to: Nobody/Anonymous (nobody) Summary: findbugs report generation failure Initial Comment: when running 'mvn findbugs:check' following warn message is output: [INFO] Adding Source Directory: /Users/mmarkus/code/ispn/trunk/core/target/classes [java] The following classes needed for analysis were missing: [java] javax.annotation.Nonnull [java] Missing classes: 1 <?xml version="1.0" encoding="UTF-8"?> <BugCollection version='1.3.9' threshold='' effort='min'><Error></Error><Project><SrcDir>/Users/mmarkus/code/ispn/trunk/core/src/main/java</SrcDir></Project></BugCollection>[INFO] [findbugs:check {execution: default-cli}] Then the report does not contain *any* result of the failure at all, even though there are issues that findbugs can report. I've attached a simple test, just go to core and run 'mvn findbugs:check' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2851027&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-09-04 09:51:09
|
Bugs item #2851027, was opened at 2009-09-04 12:51 Message generated for change (Tracker Item Submitted) made by mircea_markus You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2851027&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mircea Markus (mircea_markus) Assigned to: Nobody/Anonymous (nobody) Summary: findbugs report generation failure Initial Comment: when running 'mvn findbugs:check' following warn message is output: [INFO] Adding Source Directory: /Users/mmarkus/code/ispn/trunk/core/target/classes [java] The following classes needed for analysis were missing: [java] javax.annotation.Nonnull [java] Missing classes: 1 <?xml version="1.0" encoding="UTF-8"?> <BugCollection version='1.3.9' threshold='' effort='min'><Error></Error><Project><SrcDir>/Users/mmarkus/code/ispn/trunk/core/src/main/java</SrcDir></Project></BugCollection>[INFO] [findbugs:check {execution: default-cli}] Then the report does not contain *any* result of the failure at all, even though there are issues that findbugs can report. I've attached a simple test, just go to core and run 'mvn findbugs:check' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2851027&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-08-25 12:58:46
|
Bugs item #2844114, was opened at 2009-08-25 03:51 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2844114&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: dbunit Group: release >Status: Closed >Resolution: Rejected Priority: 5 Private: No Submitted By: Udo Kuehne (udokuehne) Assigned to: Jeff Jensen (jeffjensen) Summary: Error: missing plugin descriptor Initial Comment: snippet of my pom-file: <!-- Plugin zum Ex- und Imort-Handling mittels "DBUnit" --> <plugins> ... <plugin> <groupId>maven-plugins</groupId> <artifactId>maven-dbunit-plugin</artifactId> <version>1.9</version> <configuration> <dbunit.dataTypeFactoryName.dev>org.dbunit.ext.mssql.MsSqlDataTypeFactory</dbunit.dataTypeFactoryName.dev> <maven.dbunit.datatypeFactory>${dbunit.dataTypeFactoryName.dev}</maven.dbunit.datatypeFactory> <maven.dbunit.driverClassName>${dbunit.driver.dev}</maven.dbunit.driverClassName> <maven.dbunit.user>${dbunit.username.dev}</maven.dbunit.user> <maven.dbunit.password>${dbunit.password.dev}</maven.dbunit.password> <maven.dbunit.url>${dbunit.url.dev}</maven.dbunit.url> </configuration> <!-- Datenbanktreiber Zugriff für dbunit --> <dependencies> <dependency> <groupId>com.microsoft.sqlserver</groupId> <artifactId>sqlserver-jdbc</artifactId> <version>2.0.1803.100</version> </dependency> <dependency> <groupId>com.ibm.db2</groupId> <artifactId>db2jcc</artifactId> <version>9.0</version> </dependency> <dependency> <groupId>com.ibm.db2</groupId> <artifactId>db2jcc_license_cu</artifactId> <version>9.0</version> </dependency> </dependencies> </plugin> ... </plugins> mvn -e -Pdev dbunit:generate-dataset -Dtables=Vertrag,Abschlagsregeln -Ddest=sample-data.xml [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] The plugin descriptor for the plugin Plugin [maven-plugins:maven-dbunit-plugin] was not found. Please verify that the plugin JAR C:\develop\lib\java\m2repo\maven-plugins\maven-dbunit-plugin\1.9\maven-dbunit-plugin-1.9.jar is intact. [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.IllegalStateException: The plugin descriptor for the plugin Plugin [maven-plugins:maven-dbunit-plugin] was not found. Please verify that the plugin JAR C:\develop\lib\java\m2repo\maven-plugins\maven-dbunit-plugin\1.9\maven-dbunit- plugin-1.9.jar is intact. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:353) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:217) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:177) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1744) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto r.java:446) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:176) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2009-08-25 07:58 Message: This plugin is for Maven 1. You are using Maven 2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2844114&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-08-25 08:51:21
|
Bugs item #2844114, was opened at 2009-08-25 10:51 Message generated for change (Tracker Item Submitted) made by udokuehne You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2844114&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: dbunit Group: release Status: Open Resolution: None Priority: 5 Private: No Submitted By: Udo Kuehne (udokuehne) Assigned to: Jeff Jensen (jeffjensen) Summary: Error: missing plugin descriptor Initial Comment: snippet of my pom-file: <!-- Plugin zum Ex- und Imort-Handling mittels "DBUnit" --> <plugins> ... <plugin> <groupId>maven-plugins</groupId> <artifactId>maven-dbunit-plugin</artifactId> <version>1.9</version> <configuration> <dbunit.dataTypeFactoryName.dev>org.dbunit.ext.mssql.MsSqlDataTypeFactory</dbunit.dataTypeFactoryName.dev> <maven.dbunit.datatypeFactory>${dbunit.dataTypeFactoryName.dev}</maven.dbunit.datatypeFactory> <maven.dbunit.driverClassName>${dbunit.driver.dev}</maven.dbunit.driverClassName> <maven.dbunit.user>${dbunit.username.dev}</maven.dbunit.user> <maven.dbunit.password>${dbunit.password.dev}</maven.dbunit.password> <maven.dbunit.url>${dbunit.url.dev}</maven.dbunit.url> </configuration> <!-- Datenbanktreiber Zugriff für dbunit --> <dependencies> <dependency> <groupId>com.microsoft.sqlserver</groupId> <artifactId>sqlserver-jdbc</artifactId> <version>2.0.1803.100</version> </dependency> <dependency> <groupId>com.ibm.db2</groupId> <artifactId>db2jcc</artifactId> <version>9.0</version> </dependency> <dependency> <groupId>com.ibm.db2</groupId> <artifactId>db2jcc_license_cu</artifactId> <version>9.0</version> </dependency> </dependencies> </plugin> ... </plugins> mvn -e -Pdev dbunit:generate-dataset -Dtables=Vertrag,Abschlagsregeln -Ddest=sample-data.xml [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] The plugin descriptor for the plugin Plugin [maven-plugins:maven-dbunit-plugin] was not found. Please verify that the plugin JAR C:\develop\lib\java\m2repo\maven-plugins\maven-dbunit-plugin\1.9\maven-dbunit-plugin-1.9.jar is intact. [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.IllegalStateException: The plugin descriptor for the plugin Plugin [maven-plugins:maven-dbunit-plugin] was not found. Please verify that the plugin JAR C:\develop\lib\java\m2repo\maven-plugins\maven-dbunit-plugin\1.9\maven-dbunit- plugin-1.9.jar is intact. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:353) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:217) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:177) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1744) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto r.java:446) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:176) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2844114&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-06-06 02:20:35
|
Feature Requests item #2795374, was opened at 2009-05-22 12:44 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497856&aid=2795374&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: cobertura Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Martin (devmapo) Assigned to: Jeff Jensen (jeffjensen) Summary: Align plugin with maven.test.skip property Initial Comment: Hi, I would really appreciate if the plugin would use the maven.test.skip property. As a patch the option haltOnFailure could be equal to the opposite of the skip property. So setting the property test.skip to true would set automatically the haltOnFailure to false. This option could be set by adding a tag <alignWithMavenTestSkip/> But a better implementation would not run cobertura when the test are skip. Right now I have to create my own property and tell people to set it to false when they skip the test. Thanks ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2009-06-06 02:20 Message: This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2009-05-22 14:35 Message: Please verify which version of Maven you are using. This plugin/site is for Maven 1.x, not 2.x. Moving item to feature requests. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497856&aid=2795374&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-05-22 14:35:14
|
Feature Requests item #2795374, was opened at 2009-05-22 07:44 Message generated for change (Settings changed) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497856&aid=2795374&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: cobertura Group: None >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: Martin (devmapo) Assigned to: Jeff Jensen (jeffjensen) Summary: Align plugin with maven.test.skip property Initial Comment: Hi, I would really appreciate if the plugin would use the maven.test.skip property. As a patch the option haltOnFailure could be equal to the opposite of the skip property. So setting the property test.skip to true would set automatically the haltOnFailure to false. This option could be set by adding a tag <alignWithMavenTestSkip/> But a better implementation would not run cobertura when the test are skip. Right now I have to create my own property and tell people to set it to false when they skip the test. Thanks ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2009-05-22 09:35 Message: Please verify which version of Maven you are using. This plugin/site is for Maven 1.x, not 2.x. Moving item to feature requests. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497856&aid=2795374&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-05-22 12:44:14
|
Bugs item #2795374, was opened at 2009-05-22 08:44 Message generated for change (Tracker Item Submitted) made by devmapo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2795374&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: cobertura Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Martin (devmapo) Assigned to: Jeff Jensen (jeffjensen) Summary: Align plugin with maven.test.skip property Initial Comment: Hi, I would really appreciate if the plugin would use the maven.test.skip property. As a patch the option haltOnFailure could be equal to the opposite of the skip property. So setting the property test.skip to true would set automatically the haltOnFailure to false. This option could be set by adding a tag <alignWithMavenTestSkip/> But a better implementation would not run cobertura when the test are skip. Right now I have to create my own property and tell people to set it to false when they skip the test. Thanks ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2795374&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-02-12 14:07:48
|
Bugs item #2593045, was opened at 2009-02-12 08:34 Message generated for change (Settings changed) made by jweden You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2593045&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: findbugs Group: None >Status: Closed Resolution: Invalid Priority: 5 Private: No Submitted By: Jason Weden (jweden) Assigned to: Jeff Jensen (jeffjensen) Summary: xml report output contains wrong category designations Initial Comment: Every bug listing in the xml output for version the findbugs maven plugin is listed in the "CORRECTNESS" category. I'm using the findbugs-maven-plugin-2.0-20090121.135609-24.jar. I've checked with the findbugs group and they say this isn't standard findbugs xml output and that it is specific to the plugin. The xml bug snippet below is an example of something that should be "MULTITHREADED CORRECTNESS" according to: http://findbugs.sourceforge.net/bugDescriptions.html : - <bug> <message>Synchronization on boxed primitive values</message> <priority>NORMAL</priority> <key>11974</key> - <lineRanges> - <range> <start>68</start> <end>68</end> </range> </lineRanges> <primaryLineNumber>68</primaryLineNumber> <fileName>E:/hudson/jobs/configserver-main-separate/workspace/rwc467_builds erver_AXSV_R7_sip_config_int_separate/qbvision-nms/client/devicemgr/src/com /quantumbridge/client/devicemgr/graphics/NetworkPanel.java</fileName> <moduleName>findbugs</moduleName> <packageName>com.quantumbridge.client.devicemgr.graphics</packageName> <category>CORRECTNESS</category> <type>DL_SYNCHRONIZATION_ON_UNSHARED_BOXED_PRIMITIVE</type> <contextHashCode>11975</contextHashCode> <tooltip /> <instanceHash>297b57c391d5aa2c8854ab537de763a8</instanceHash> </bug> Here is the maven configuration. I'm generating the standard findbugs.xml as a result of my ant target below: <target name="findbugs" description="Runs findbugs. Requires OS variable for findbugs.home and jars to be packaged."> <mkdir dir="${findbugs.dir}"/> <findbugs effort="max" jvmargs="-Xmx1024M" home="${env.findbugs.home}" output="xml:withMessages" outputFile="${findbugs.dir}/findbugs.xml" stylesheet="default.xsl" timeout="7200000"> <auxClasspath> <fileset dir="${lib.dir}/ext/"> <include name="*.jar" /> </fileset> </auxClasspath> <sourcePath refid="all-src-ref"/> <class location="${lib.dir}/*.jar"/> </findbugs> </target> ---------------------------------------------------------------------- >Comment By: Jason Weden (jweden) Date: 2009-02-12 09:07 Message: ok, thanks. ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2009-02-12 08:54 Message: findbugs-maven-plugin is a Maven 2 plugin. This tracker is for Maven 1. You want ot go here: http://jira.codehaus.org/browse/MFINDBUGS ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2593045&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-02-12 13:54:30
|
Bugs item #2593045, was opened at 2009-02-12 07:34 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2593045&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: findbugs Group: None Status: Open >Resolution: Invalid Priority: 5 Private: No Submitted By: Jason Weden (jweden) Assigned to: Jeff Jensen (jeffjensen) Summary: xml report output contains wrong category designations Initial Comment: Every bug listing in the xml output for version the findbugs maven plugin is listed in the "CORRECTNESS" category. I'm using the findbugs-maven-plugin-2.0-20090121.135609-24.jar. I've checked with the findbugs group and they say this isn't standard findbugs xml output and that it is specific to the plugin. The xml bug snippet below is an example of something that should be "MULTITHREADED CORRECTNESS" according to: http://findbugs.sourceforge.net/bugDescriptions.html : - <bug> <message>Synchronization on boxed primitive values</message> <priority>NORMAL</priority> <key>11974</key> - <lineRanges> - <range> <start>68</start> <end>68</end> </range> </lineRanges> <primaryLineNumber>68</primaryLineNumber> <fileName>E:/hudson/jobs/configserver-main-separate/workspace/rwc467_builds erver_AXSV_R7_sip_config_int_separate/qbvision-nms/client/devicemgr/src/com /quantumbridge/client/devicemgr/graphics/NetworkPanel.java</fileName> <moduleName>findbugs</moduleName> <packageName>com.quantumbridge.client.devicemgr.graphics</packageName> <category>CORRECTNESS</category> <type>DL_SYNCHRONIZATION_ON_UNSHARED_BOXED_PRIMITIVE</type> <contextHashCode>11975</contextHashCode> <tooltip /> <instanceHash>297b57c391d5aa2c8854ab537de763a8</instanceHash> </bug> Here is the maven configuration. I'm generating the standard findbugs.xml as a result of my ant target below: <target name="findbugs" description="Runs findbugs. Requires OS variable for findbugs.home and jars to be packaged."> <mkdir dir="${findbugs.dir}"/> <findbugs effort="max" jvmargs="-Xmx1024M" home="${env.findbugs.home}" output="xml:withMessages" outputFile="${findbugs.dir}/findbugs.xml" stylesheet="default.xsl" timeout="7200000"> <auxClasspath> <fileset dir="${lib.dir}/ext/"> <include name="*.jar" /> </fileset> </auxClasspath> <sourcePath refid="all-src-ref"/> <class location="${lib.dir}/*.jar"/> </findbugs> </target> ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2009-02-12 07:54 Message: findbugs-maven-plugin is a Maven 2 plugin. This tracker is for Maven 1. You want ot go here: http://jira.codehaus.org/browse/MFINDBUGS ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2593045&group_id=61626 |
From: SourceForge.net <no...@so...> - 2009-02-12 13:34:34
|
Bugs item #2593045, was opened at 2009-02-12 08:34 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2593045&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: findbugs Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jason Weden (jweden) Assigned to: Jeff Jensen (jeffjensen) Summary: xml report output contains wrong category designations Initial Comment: Every bug listing in the xml output for version the findbugs maven plugin is listed in the "CORRECTNESS" category. I'm using the findbugs-maven-plugin-2.0-20090121.135609-24.jar. I've checked with the findbugs group and they say this isn't standard findbugs xml output and that it is specific to the plugin. The xml bug snippet below is an example of something that should be "MULTITHREADED CORRECTNESS" according to: http://findbugs.sourceforge.net/bugDescriptions.html : - <bug> <message>Synchronization on boxed primitive values</message> <priority>NORMAL</priority> <key>11974</key> - <lineRanges> - <range> <start>68</start> <end>68</end> </range> </lineRanges> <primaryLineNumber>68</primaryLineNumber> <fileName>E:/hudson/jobs/configserver-main-separate/workspace/rwc467_builds erver_AXSV_R7_sip_config_int_separate/qbvision-nms/client/devicemgr/src/com /quantumbridge/client/devicemgr/graphics/NetworkPanel.java</fileName> <moduleName>findbugs</moduleName> <packageName>com.quantumbridge.client.devicemgr.graphics</packageName> <category>CORRECTNESS</category> <type>DL_SYNCHRONIZATION_ON_UNSHARED_BOXED_PRIMITIVE</type> <contextHashCode>11975</contextHashCode> <tooltip /> <instanceHash>297b57c391d5aa2c8854ab537de763a8</instanceHash> </bug> Here is the maven configuration. I'm generating the standard findbugs.xml as a result of my ant target below: <target name="findbugs" description="Runs findbugs. Requires OS variable for findbugs.home and jars to be packaged."> <mkdir dir="${findbugs.dir}"/> <findbugs effort="max" jvmargs="-Xmx1024M" home="${env.findbugs.home}" output="xml:withMessages" outputFile="${findbugs.dir}/findbugs.xml" stylesheet="default.xsl" timeout="7200000"> <auxClasspath> <fileset dir="${lib.dir}/ext/"> <include name="*.jar" /> </fileset> </auxClasspath> <sourcePath refid="all-src-ref"/> <class location="${lib.dir}/*.jar"/> </findbugs> </target> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2593045&group_id=61626 |
From: SourceForge.net <no...@so...> - 2008-09-24 03:36:43
|
Bugs item #2114755, was opened at 2008-09-16 14:26 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2114755&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: findbugs Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Craig (craigandrews) Assigned to: Jeff Jensen (jeffjensen) >Summary: [findbugs] Bump to 1.3.2/1.3.5 Initial Comment: Can you please update the plugins dependencies? The latest version of findbugs is 1.3.2 in maven, but I just files a request to have findbugs 1.3.5 put into the repository: http://sourceforge.net/tracker/index.php?func=detail&aid=2114752&group_id=96405&atid=614693 Also, some of your other dependencies could use a bump. asm is up to 3.1 (from 3.0), and dom4j is up to 1.6.1 (from 1.4). Thanks! ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2008-09-23 22:36 Message: IIRC (I looked into doing this a long time ago), the updated deps for newer FindBugs versions would cause a conflict with the versions Maven itself declared. To be fully correct, we would have to update one or more Maven dependencies and release a new Maven version too. If that is incorrect, we can easily do it. Or we can roll the dice and take a chance without the Maven update... Lukas/Arnaud, your advice? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2114755&group_id=61626 |
From: SourceForge.net <no...@so...> - 2008-09-23 09:48:22
|
Bugs item #2124157, was opened at 2008-09-23 10:27 Message generated for change (Comment added) made by lukas_theussl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2124157&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: dotuml Group: None >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Ricky Clarkson (ricky_clarkson) Assigned to: Nobody/Anonymous (nobody) Summary: Plugin descriptor missing Initial Comment: When I use the XML below to add dotuml to my pom.xml, and run mvn site, I get this output: [INFO] The PluginDescriptor for the plugin Plugin [maven-plugins:maven-dotuml-plugin] was not found. [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [maven-plugins:maven-dotuml-plugin] was not found. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:325) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) at org.apache.maven.plugin.DefaultPluginManager.verifyReportPlugin(DefaultPluginManager.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyReportPlugin(DefaultLifecycleExecutor.java:1314) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:685) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:661) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:536) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) The XML mentioned above: <plugin> <groupId>maven-plugins</groupId> <artifactId>maven-dotuml-plugin</artifactId> <version>1.0</version> </plugin> On initial browsing of documentation, it seems the plugin's .jar on http://repo1.maven.org/maven2/maven-plugins/maven-dotuml-plugin/1.0/ should contain a plugin.xml, but it doesn't. ---------------------------------------------------------------------- >Comment By: Lukas Theussl (lukas_theussl) Date: 2008-09-23 11:48 Message: This is a maven 1 plugin, it doesn't work with m2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2124157&group_id=61626 |
From: SourceForge.net <no...@so...> - 2008-09-23 08:27:47
|
Bugs item #2124157, was opened at 2008-09-23 08:27 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2124157&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: dotuml Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ricky Clarkson (ricky_clarkson) Assigned to: Nobody/Anonymous (nobody) Summary: Plugin descriptor missing Initial Comment: When I use the XML below to add dotuml to my pom.xml, and run mvn site, I get this output: [INFO] The PluginDescriptor for the plugin Plugin [maven-plugins:maven-dotuml-plugin] was not found. [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [maven-plugins:maven-dotuml-plugin] was not found. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:325) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) at org.apache.maven.plugin.DefaultPluginManager.verifyReportPlugin(DefaultPluginManager.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyReportPlugin(DefaultLifecycleExecutor.java:1314) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:685) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:661) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:536) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) The XML mentioned above: <plugin> <groupId>maven-plugins</groupId> <artifactId>maven-dotuml-plugin</artifactId> <version>1.0</version> </plugin> On initial browsing of documentation, it seems the plugin's .jar on http://repo1.maven.org/maven2/maven-plugins/maven-dotuml-plugin/1.0/ should contain a plugin.xml, but it doesn't. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2124157&group_id=61626 |
From: SourceForge.net <no...@so...> - 2008-09-16 12:26:59
|
Bugs item #2114755, was opened at 2008-09-16 15:26 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2114755&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: findbugs Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Craig (craigandrews) Assigned to: Jeff Jensen (jeffjensen) Summary: Bump to findbugs 1.3.2/1.3.5 Initial Comment: Can you please update the plugins dependencies? The latest version of findbugs is 1.3.2 in maven, but I just files a request to have findbugs 1.3.5 put into the repository: http://sourceforge.net/tracker/index.php?func=detail&aid=2114752&group_id=96405&atid=614693 Also, some of your other dependencies could use a bump. asm is up to 3.1 (from 3.0), and dom4j is up to 1.6.1 (from 1.4). Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=2114755&group_id=61626 |
From: SourceForge.net <no...@so...> - 2008-03-01 04:14:52
|
Feature Requests item #1872688, was opened at 2008-01-16 05:42 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497856&aid=1872688&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: JavaNCSS Group: Next Release (example) >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Xavier Chatelain (xaviou) Assigned to: Jeff Jensen (jeffjensen) Summary: [maven-javancss-plugin] Upgrade to 28.49 Initial Comment: It seems maven-javancss-plugin version 1.3.1 comes with the oldest version of javancss (21.41, md5sum 8d51423d054285a8712810ac746a9e98). Could it be upgraded with the latest version of JavaNCSS (28.49)? This latest version (28.49) comes with "Various Java 1.5 grammar parser bugs fixed". With the current version (21.41) we have ParseException like that: [echo] Generating the JavaNCSS... javancss: [echo] Generating JavaNCSS report for site generation javancss:do-xml: [...] [java] Lexical error at line 35, column 8. Encountered: "@" (64), after : "" [...] [java] Encountered "enum" at line 32, column 8. [java] Was expecting one of: [java] "abstract" ... [java] "interface" ... [java] "public" ... [java] "final" ... [java] "synchronized" ... [java] "strictfp" ... [java] "class" ... ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2008-02-29 22:14 Message: Logged In: YES user_id=498804 Originator: NO Great! Thanks for testing - glad it works. Sorry, the maven-plugins has its own repos. This is the snapshots location: http://maven-plugins.sourceforge.net/snapshot-repository/maven-plugins/ For future reference, the main page (http://maven-plugins.sourceforge.net/) has links to the release and snapshot repos. I will release... ---------------------------------------------------------------------- Comment By: Xavier Chatelain (xaviou) Date: 2008-02-28 05:18 Message: Logged In: YES user_id=932495 Originator: YES Hi Jeff! I eventually had the time to test it, and it works (I don't get anymore the Java5 bugs as explained above)! Here was my test plan (just to say there was one) : 1. I tested with the 1.3.1 version, and the bug appeared 2. I uninstalled the 1.3.1 version from my maven 1 installation 3. Actually I did not find the snapshot (on http://people.apache.org/repo/m1-snapshot-repository/maven/plugins/), so I updated the new files from the CVS (the project.xml and the 3 jars) and built and install the 1.3.2 snapshot. 4. I tested with the 1.3.2.snapshot, and it works! So it can be released! ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2008-02-11 13:31 Message: Logged In: YES user_id=498804 Originator: NO It seems so - I updated all 3 and checked them in. It looks like it did not change, but the other 2 did. The file sizes between the new and old are the same too. ---------------------------------------------------------------------- Comment By: Xavier Chatelain (xaviou) Date: 2008-02-11 08:40 Message: Logged In: YES user_id=932495 Originator: YES Thanks Jeff for the snapshot. I did not have the chance to test it yet (I am away until the end of the week), but I noticed that jhbasic.jar has not been updated in the CVS repo (in /maven-plugins/javancss/jars). Is it normal? ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2008-02-10 11:19 Message: Logged In: YES user_id=498804 Originator: NO Thank you very much for your simple instructions and trying it first. I deployed a 1.3.2 snapshot; please verify it works so we can release it! I can't believe almost a month has passed since you entered them...I am sorry it took so long for me to do this. You are of course correct on the "hack packaging". I did not make any attempt to change that! If you find want to, please do... :-) I don't remember history on that, and it could very well be there were issues getting the artifacts in central/ibiblio at one time. ---------------------------------------------------------------------- Comment By: Xavier Chatelain (xaviou) Date: 2008-01-16 10:55 Message: Logged In: YES user_id=932495 Originator: YES Hi Jeff! Here is a quick hack, in order to release a maven-javancss-plugin with the latest JavaNCSS JAR: 1. Download the latest version of JavaNCSS here: http://www.kclee.de/clemens/java/javancss/javancss28.49.zip 2. Unzip, and commit the 3 JARs (ccl.jar, javancss.jar and jhbasic.jar) in the /maven-plugins/javancss/jars CVS repository. I did a plugin install and tested it, it works fine (I don't get anymore the Java5 bugs as explained above). Note (this may be another feature/bug request): this hack is as dirty as the plugin packaging is today: actually the 3 JARs are packed within the plugin, but this may not be necessary as they are available in the Maven repo (here: http://repo1.maven.org/maven/javancss/jars/). ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2008-01-16 07:04 Message: Logged In: YES user_id=498804 Originator: NO Hi Xavier! Do you have time to determine the changes and test it, then attach the patch file(s)? Besides making the time to get to it, I don't have a working setup of this plugin (which not only adds to the time, it reduces the test cases!). I'll gladly package and release it for you... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497856&aid=1872688&group_id=61626 |
From: SourceForge.net <no...@so...> - 2008-02-28 11:18:39
|
Feature Requests item #1872688, was opened at 2008-01-16 12:42 Message generated for change (Comment added) made by xaviou You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497856&aid=1872688&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: JavaNCSS Group: Next Release (example) Status: Open Resolution: Fixed Priority: 5 Private: No Submitted By: Xavier Chatelain (xaviou) Assigned to: Jeff Jensen (jeffjensen) Summary: [maven-javancss-plugin] Upgrade to 28.49 Initial Comment: It seems maven-javancss-plugin version 1.3.1 comes with the oldest version of javancss (21.41, md5sum 8d51423d054285a8712810ac746a9e98). Could it be upgraded with the latest version of JavaNCSS (28.49)? This latest version (28.49) comes with "Various Java 1.5 grammar parser bugs fixed". With the current version (21.41) we have ParseException like that: [echo] Generating the JavaNCSS... javancss: [echo] Generating JavaNCSS report for site generation javancss:do-xml: [...] [java] Lexical error at line 35, column 8. Encountered: "@" (64), after : "" [...] [java] Encountered "enum" at line 32, column 8. [java] Was expecting one of: [java] "abstract" ... [java] "interface" ... [java] "public" ... [java] "final" ... [java] "synchronized" ... [java] "strictfp" ... [java] "class" ... ---------------------------------------------------------------------- >Comment By: Xavier Chatelain (xaviou) Date: 2008-02-28 12:18 Message: Logged In: YES user_id=932495 Originator: YES Hi Jeff! I eventually had the time to test it, and it works (I don't get anymore the Java5 bugs as explained above)! Here was my test plan (just to say there was one) : 1. I tested with the 1.3.1 version, and the bug appeared 2. I uninstalled the 1.3.1 version from my maven 1 installation 3. Actually I did not find the snapshot (on http://people.apache.org/repo/m1-snapshot-repository/maven/plugins/), so I updated the new files from the CVS (the project.xml and the 3 jars) and built and install the 1.3.2 snapshot. 4. I tested with the 1.3.2.snapshot, and it works! So it can be released! ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2008-02-11 20:31 Message: Logged In: YES user_id=498804 Originator: NO It seems so - I updated all 3 and checked them in. It looks like it did not change, but the other 2 did. The file sizes between the new and old are the same too. ---------------------------------------------------------------------- Comment By: Xavier Chatelain (xaviou) Date: 2008-02-11 15:40 Message: Logged In: YES user_id=932495 Originator: YES Thanks Jeff for the snapshot. I did not have the chance to test it yet (I am away until the end of the week), but I noticed that jhbasic.jar has not been updated in the CVS repo (in /maven-plugins/javancss/jars). Is it normal? ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2008-02-10 18:19 Message: Logged In: YES user_id=498804 Originator: NO Thank you very much for your simple instructions and trying it first. I deployed a 1.3.2 snapshot; please verify it works so we can release it! I can't believe almost a month has passed since you entered them...I am sorry it took so long for me to do this. You are of course correct on the "hack packaging". I did not make any attempt to change that! If you find want to, please do... :-) I don't remember history on that, and it could very well be there were issues getting the artifacts in central/ibiblio at one time. ---------------------------------------------------------------------- Comment By: Xavier Chatelain (xaviou) Date: 2008-01-16 17:55 Message: Logged In: YES user_id=932495 Originator: YES Hi Jeff! Here is a quick hack, in order to release a maven-javancss-plugin with the latest JavaNCSS JAR: 1. Download the latest version of JavaNCSS here: http://www.kclee.de/clemens/java/javancss/javancss28.49.zip 2. Unzip, and commit the 3 JARs (ccl.jar, javancss.jar and jhbasic.jar) in the /maven-plugins/javancss/jars CVS repository. I did a plugin install and tested it, it works fine (I don't get anymore the Java5 bugs as explained above). Note (this may be another feature/bug request): this hack is as dirty as the plugin packaging is today: actually the 3 JARs are packed within the plugin, but this may not be necessary as they are available in the Maven repo (here: http://repo1.maven.org/maven/javancss/jars/). ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2008-01-16 14:04 Message: Logged In: YES user_id=498804 Originator: NO Hi Xavier! Do you have time to determine the changes and test it, then attach the patch file(s)? Besides making the time to get to it, I don't have a working setup of this plugin (which not only adds to the time, it reduces the test cases!). I'll gladly package and release it for you... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497856&aid=1872688&group_id=61626 |