[jira] Created: (CONTINUUM-1237) Create web UI tests for Continuum - Project operations
Create web UI tests for Continuum - Project operations -- Key: CONTINUUM-1237 URL: http://jira.codehaus.org/browse/CONTINUUM-1237 Project: Continuum Issue Type: Test Components: Web - UI Reporter: Teodoro Cue Jr. Priority: Minor Need to test invalid inputs on the fields such as empty strings and spaces. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1238) Create web UI tests for Continuum - Build Definition operations
Create web UI tests for Continuum - Build Definition operations --- Key: CONTINUUM-1238 URL: http://jira.codehaus.org/browse/CONTINUUM-1238 Project: Continuum Issue Type: Test Components: Web - UI Reporter: Teodoro Cue Jr. Priority: Minor Need to test invalid inputs on the fields such as empty strings and spaces. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1237) Create web UI tests for Continuum - Project operations
[ http://jira.codehaus.org/browse/CONTINUUM-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91772 ] Teodoro Cue Jr. commented on CONTINUUM-1237: Since I added updates on 1 file with the fix on this and the fix on CONTINUUM-1238, I'm attaching the patch here. > Create web UI tests for Continuum - Project operations > -- > > Key: CONTINUUM-1237 > URL: http://jira.codehaus.org/browse/CONTINUUM-1237 > Project: Continuum > Issue Type: Test > Components: Web - UI >Reporter: Teodoro Cue Jr. >Priority: Minor > Attachments: CONTINUUM-1237-continuum-webapp-test.patch > > > Need to test invalid inputs on the fields such as empty strings and spaces. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1237) Create web UI tests for Continuum - Project operations
[ http://jira.codehaus.org/browse/CONTINUUM-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teodoro Cue Jr. updated CONTINUUM-1237: --- Attachment: CONTINUUM-1237-continuum-webapp-test.patch > Create web UI tests for Continuum - Project operations > -- > > Key: CONTINUUM-1237 > URL: http://jira.codehaus.org/browse/CONTINUUM-1237 > Project: Continuum > Issue Type: Test > Components: Web - UI >Reporter: Teodoro Cue Jr. >Priority: Minor > Attachments: CONTINUUM-1237-continuum-webapp-test.patch > > > Need to test invalid inputs on the fields such as empty strings and spaces. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1238) Create web UI tests for Continuum - Build Definition operations
[ http://jira.codehaus.org/browse/CONTINUUM-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91773 ] Teodoro Cue Jr. commented on CONTINUUM-1238: Since I added updates on 1 file with the fix on this and the fix on CONTINUUM-1237, I'm attaching the patch on CONTINUUM-1237. > Create web UI tests for Continuum - Build Definition operations > --- > > Key: CONTINUUM-1238 > URL: http://jira.codehaus.org/browse/CONTINUUM-1238 > Project: Continuum > Issue Type: Test > Components: Web - UI >Reporter: Teodoro Cue Jr. >Priority: Minor > > Need to test invalid inputs on the fields such as empty strings and spaces. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2917) Ant classpath issue in maven 2.0.6
Ant classpath issue in maven 2.0.6 -- Key: MNG-2917 URL: http://jira.codehaus.org/browse/MNG-2917 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.6 Reporter: Yuri Schimke Priority: Critical This was working in 2.0.5. Unfortunately I'm guessing its related to the woefully bad xdoclet-maven-plugin The main error is that the xdoclet-maven-plugin can't find one of the ant classes Caused by: java.lang.NoClassDefFoundError: org/apache/tools/ant/PropertyHelper - this realm = app0.child-container[org.codehaus.mojo:xdoclet-maven-plugin] urls[0] = file:/C:/Docume~1/nbk7xsp/.m2/repository/org/codehaus/mojo/xdoclet-maven-plugin/1.0-alpha-2/xdoclet-maven-plugin-1.0-alpha-2.jar urls[1] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-wsee-module/1.2.3/xdoclet-wsee-module-1.2.3.jar urls[2] = file:/C:/Docume~1/nbk7xsp/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar urls[3] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-jboss-module/1.2.3/xdoclet-jboss-module-1.2.3.jar urls[4] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-xdoclet-module/1.2.3/xdoclet-xdoclet-module-1.2.3.jar urls[5] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-orion-module/1.2.3/xdoclet-orion-module-1.2.3.jar urls[6] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-jmx-module/1.2.3/xdoclet-jmx-module-1.2.3.jar urls[7] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-ibm-module/1.2.3/xdoclet-ibm-module-1.2.3.jar urls[8] = file:/C:/Docume~1/nbk7xsp/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar urls[9] = file:/C:/Docume~1/nbk7xsp/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar urls[10] = file:/C:/Docume~1/nbk7xsp/.m2/repository/ant/ant/1.5.2/ant-1.5.2.jar urls[11] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-apache-module/1.2.3/xdoclet-apache-module-1.2.3.jar urls[12] = file:/C:/Docume~1/nbk7xsp/.m2/repository/ant/ant-launcher/1.6.5/ant-l auncher-1.6.5.jar urls[13] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-fr_FR-locale/1.2.3/xdoclet-fr_FR-locale-1.2.3.jar urls[14] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-objectweb-module/1.2.3/xdoclet-objectweb-module-1.2.3.jar urls[15] = file:/C:/Docume~1/nbk7xsp/.m2/repository/org/apache/maven/plugins/maven-antrun-plugin/1.0/maven-antrun-plugin-1.0.jar urls[16] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-java-module/1.2.3/xdoclet-java-module-1.2.3.jar urls[17] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-exolab-module/1.2.3/xdoclet-exolab-module-1.2.3.jar urls[18] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-bea-module/1.2.3/xdoclet-bea-module-1.2.3.jar urls[19] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-mvcsoft-module/1.2.3/xdoclet-mvcsoft-module-1.2.3.jar urls[20] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-sun-module/1.2.3/xdoclet-sun-module-1.2.3.jar urls[21] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-spring-module/1.2.3/xdoclet-spring-module-1.2.3.jar urls[22] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-de-locale/1.2.3/xdoclet-de-locale-1.2.3.jar urls[23] = file:/C:/Docume~1/nbk7xsp/.m2/repository/jboss/jboss-j2ee/3.2.1/jboss-j2ee-3.2.1.jar urls[24] = file:/C:/Docume~1/nbk7xsp/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar urls[25] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-web-module/1.2.3/xdoclet-web-module-1.2.3.jar urls[26] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-caucho-module/1.2.3/xdoclet-caucho-module-1.2.3.jar urls[27] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-jdo-module/1.2.3/xdoclet-jdo-module-1.2.3.jar urls[28] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-tjdo-module/1.2.3/xdoclet-tjdo-module-1.2.3.jar urls[29] = file:/C:/Docume~1/nbk7xsp/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar urls[30] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-openejb-module/1.2.3/xdoclet-openejb-module-1.2.3.jar urls[31] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-oracle-module/1.2.3/xdoclet-oracle-module-1.2.3.jar urls[32] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-hp-module/1.2.3/xdoclet-hp-module-1.2.3.jar urls[33] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-webwork-module/1.2.3/xdoclet-webwork-module-1.2.3.jar urls[34] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-mx4j-module/1.2.3/xdoclet-mx4j-module-1.2.3.jar urls[35] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-solarmetric-module/1.2.3/xdoclet-solarmetric-module-1.2.3.jar urls[36] = file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet/1.2.3/xdoclet-1.2.3.jar urls[37] =
[jira] Created: (MAVENUPLOAD-1456) JasperReports 1.3.2 upload
JasperReports 1.3.2 upload -- Key: MAVENUPLOAD-1456 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1456 Project: maven-upload-requests Issue Type: Task Reporter: Teodor Danciu http://rs.jaspersoft.com/maven2/jasperreports-1.3.2-bundle.jar http://sourceforge.net/projects/jasperreports http://sourceforge.net/project/memberlist.php?group_id=36382 Open Source Reporting Engine -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2918) Active-by-default profiles from settings.xml are not active without pom.xml
Active-by-default profiles from settings.xml are not active without pom.xml --- Key: MNG-2918 URL: http://jira.codehaus.org/browse/MNG-2918 Project: Maven 2 Issue Type: Wish Components: Profiles Affects Versions: 2.0.5 Reporter: Roman Alekseenkov Attachments: settings.xml I use Archiva as Maven proxy, see Maven settings file attached for details. It contains only one profile that is active by default and contains repository URLs on our local area network. If I try to build a specific project, which has pom.xml of course, the profile is being activated and downloads appropriate artifacts from the proxy server. However, when I execute a specific plugin goal without any project, Maven downloads all required artifacts from its central repository, which indicated that the profile hasn't been activated. I'm not sure, whether it is a bug or not. Anyway, it would be good to have _all_ traffic going through the proxy server. C:\Java>mvn archetype:create [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:create] (aggregator-style) [INFO] Downloading: http://repo1.maven.org/maven2/plexus/plexus-utils/1.0.2/plexus-utils-1.0.2.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2919) Scope defined in dependencyManagement section of parent pom overwrites scope of current artifact
Scope defined in dependencyManagement section of parent pom overwrites scope of current artifact Key: MNG-2919 URL: http://jira.codehaus.org/browse/MNG-2919 Project: Maven 2 Issue Type: Bug Components: Dependencies Affects Versions: 2.0.6 Reporter: Joerg Schaible Priority: Critical If the dependencyManagement contains also the current artifact with a scope, this scope will overwrite the scope of the current project. Use case: A global parent POM that defines the released versions of all artifacts. Those artifacts are all defined with "runtime" scope to enforce projects to declare compile time deps (workaround for MNG-2589) or some are declared with scope "test" since they should only be used in unit or it tests. Problem: If that artifact is build with M206, it does no longer compile. Reason: The declaration in the dependencyManagement section overwrites also the scope of the current artifact itself i.e. all the declared dependencies are suddenly also no longer in the compile scope. Solution: The dependencyManagement may not overwrite the scope of the current artifact. Workaround: Add for the current artifact in its own POM a dependencyManagement section where it is itself declared again with compile scope. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2919) Scope defined in dependencyManagement section of parent pom overwrites scope of current artifact
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MNG-2919: Attachment: MNG-2919.zip Simple setup to demonstrate the problem. > Scope defined in dependencyManagement section of parent pom overwrites scope > of current artifact > > > Key: MNG-2919 > URL: http://jira.codehaus.org/browse/MNG-2919 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.6 >Reporter: Joerg Schaible >Priority: Critical > Attachments: MNG-2919.zip > > > If the dependencyManagement contains also the current artifact with a scope, > this scope will overwrite the scope of the current project. > Use case: A global parent POM that defines the released versions of all > artifacts. Those artifacts are all defined with "runtime" scope to enforce > projects to declare compile time deps (workaround for MNG-2589) or some are > declared with scope "test" since they should only be used in unit or it tests. > Problem: If that artifact is build with M206, it does no longer compile. > Reason: The declaration in the dependencyManagement section overwrites also > the scope of the current artifact itself i.e. all the declared dependencies > are suddenly also no longer in the compile scope. > Solution: The dependencyManagement may not overwrite the scope of the current > artifact. > Workaround: Add for the current artifact in its own POM a > dependencyManagement section where it is itself declared again with compile > scope. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-210) A release don't perform on multi-modules projects with a non-default name of the pom even if pomFileName is defined
A release don't perform on multi-modules projects with a non-default name of the pom even if pomFileName is defined --- Key: MRELEASE-210 URL: http://jira.codehaus.org/browse/MRELEASE-210 Project: Maven 2.x Release Plugin Issue Type: Bug Reporter: Jaubert On doing a release on a multi-modules project where the parent and all subprojects have a pom named "pom-ver.xml", it takes, for the modules, the "pom.xml" file which is completely different, even if the variable pomFileName of the release plugin has been defined (in every poms or with "-D" option). the "-f pom-ver.xml" option is the only which works but it only works on the parent. So the release plugin seems to don't use the pomFileName variable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2917) Ant classpath issue in maven 2.0.6
[ http://jira.codehaus.org/browse/MNG-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuri Schimke closed MNG-2917. - Resolution: Incomplete I'm closing this one because after making some cleanups of our POMs etc, the issue has gone away. I think the maven 2.0.6 was just triggering some latent issue. > Ant classpath issue in maven 2.0.6 > -- > > Key: MNG-2917 > URL: http://jira.codehaus.org/browse/MNG-2917 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.6 >Reporter: Yuri Schimke >Priority: Critical > > This was working in 2.0.5. Unfortunately I'm guessing its related to the > woefully bad xdoclet-maven-plugin > The main error is that the xdoclet-maven-plugin can't find one of the ant > classes > Caused by: java.lang.NoClassDefFoundError: org/apache/tools/ant/PropertyHelper > - > this realm = app0.child-container[org.codehaus.mojo:xdoclet-maven-plugin] > urls[0] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/org/codehaus/mojo/xdoclet-maven-plugin/1.0-alpha-2/xdoclet-maven-plugin-1.0-alpha-2.jar > urls[1] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-wsee-module/1.2.3/xdoclet-wsee-module-1.2.3.jar > urls[2] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar > urls[3] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-jboss-module/1.2.3/xdoclet-jboss-module-1.2.3.jar > urls[4] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-xdoclet-module/1.2.3/xdoclet-xdoclet-module-1.2.3.jar > urls[5] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-orion-module/1.2.3/xdoclet-orion-module-1.2.3.jar > urls[6] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-jmx-module/1.2.3/xdoclet-jmx-module-1.2.3.jar > urls[7] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-ibm-module/1.2.3/xdoclet-ibm-module-1.2.3.jar > urls[8] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar > urls[9] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar > urls[10] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/ant/ant/1.5.2/ant-1.5.2.jar > urls[11] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-apache-module/1.2.3/xdoclet-apache-module-1.2.3.jar > urls[12] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/ant/ant-launcher/1.6.5/ant-l > auncher-1.6.5.jar > urls[13] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-fr_FR-locale/1.2.3/xdoclet-fr_FR-locale-1.2.3.jar > urls[14] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-objectweb-module/1.2.3/xdoclet-objectweb-module-1.2.3.jar > urls[15] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/org/apache/maven/plugins/maven-antrun-plugin/1.0/maven-antrun-plugin-1.0.jar > urls[16] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-java-module/1.2.3/xdoclet-java-module-1.2.3.jar > urls[17] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-exolab-module/1.2.3/xdoclet-exolab-module-1.2.3.jar > urls[18] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-bea-module/1.2.3/xdoclet-bea-module-1.2.3.jar > urls[19] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-mvcsoft-module/1.2.3/xdoclet-mvcsoft-module-1.2.3.jar > urls[20] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-sun-module/1.2.3/xdoclet-sun-module-1.2.3.jar > urls[21] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-spring-module/1.2.3/xdoclet-spring-module-1.2.3.jar > urls[22] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-de-locale/1.2.3/xdoclet-de-locale-1.2.3.jar > urls[23] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/jboss/jboss-j2ee/3.2.1/jboss-j2ee-3.2.1.jar > urls[24] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar > urls[25] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-web-module/1.2.3/xdoclet-web-module-1.2.3.jar > urls[26] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-caucho-module/1.2.3/xdoclet-caucho-module-1.2.3.jar > urls[27] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-jdo-module/1.2.3/xdoclet-jdo-module-1.2.3.jar > urls[28] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-tjdo-module/1.2.3/xdoclet-tjdo-module-1.2.3.jar > urls[29] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > urls[30] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-openejb-module/1.2.3/xdoclet-openejb-module-1.2.3.jar > urls[31] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xdoclet/xdoclet-oracle-module/1.2.3/xdoclet-oracle-module-1.2.3.jar > urls[32] = > file:/C:/Docume~1/nbk7xsp/.m2/repository/xd
[jira] Updated: (MNG-2919) Scope defined in dependencyManagement section of parent pom overwrites scope of current artifact
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2919: --- Fix Version/s: 2.0.7 > Scope defined in dependencyManagement section of parent pom overwrites scope > of current artifact > > > Key: MNG-2919 > URL: http://jira.codehaus.org/browse/MNG-2919 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.6 >Reporter: Joerg Schaible >Priority: Critical > Fix For: 2.0.7 > > Attachments: MNG-2919.zip > > > If the dependencyManagement contains also the current artifact with a scope, > this scope will overwrite the scope of the current project. > Use case: A global parent POM that defines the released versions of all > artifacts. Those artifacts are all defined with "runtime" scope to enforce > projects to declare compile time deps (workaround for MNG-2589) or some are > declared with scope "test" since they should only be used in unit or it tests. > Problem: If that artifact is build with M206, it does no longer compile. > Reason: The declaration in the dependencyManagement section overwrites also > the scope of the current artifact itself i.e. all the declared dependencies > are suddenly also no longer in the compile scope. > Solution: The dependencyManagement may not overwrite the scope of the current > artifact. > Workaround: Add for the current artifact in its own POM a > dependencyManagement section where it is itself declared again with compile > scope. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2920) [M206] Test doesn't work anymore
[M206] Test doesn't work anymore Key: MNG-2920 URL: http://jira.codehaus.org/browse/MNG-2920 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.6 Environment: Windows XP Reporter: Denis Cabasson Priority: Blocker Attachments: 206-test.zip, test-exec-205.txt, test-exec-206.txt When running "mvn test" on the simple use cas attached, M205 is doing fine, while M206 is crashing with a java.lang.IllegalArgumentException, apparently due to a diffrence in the command line used to fork the JVM for surefire. Attached are the 2 executions, with M205 and M206. I haven't managed to figure out where this bug is coming from -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-211) set version in batch mode
set version in batch mode
-
Key: MRELEASE-211
URL: http://jira.codehaus.org/browse/MRELEASE-211
Project: Maven 2.x Release Plugin
Issue Type: New Feature
Affects Versions: 2.0-beta-5
Environment: win XP pro SP2, maven 2.0.5, maven release plugin
2.0-beta-5
Reporter: Andrew Chikvaidze
I think a lot of developer teams often don't need generate javadoc for their
project every time when running release:perform.
I think it's very useful to add an option to disable javadoc creation.
When I tried to pass to maven "-DperformRelease=false" this haven't effect.
Later I saw in function
private void perform( ReleaseDescriptor releaseDescriptor, Settings
settings, List reactorProjects,
File checkoutDirectory, String goals, boolean
useReleaseProfile,
ReleaseManagerListener listener, ReleaseResult result
)
the code:
if ( useReleaseProfile )
{
if ( !StringUtils.isEmpty( additionalArguments ) )
{
/*
evil hack (we don't need javadoc)
additionalArguments = additionalArguments + "
-DperformRelease=true";
*/
additionalArguments = additionalArguments + "
-DperformRelease=false";
}
else
{
/*
evil hack (we don't need javadoc)
additionalArguments = "-DperformRelease=true";
*/
additionalArguments = "-DperformRelease=false";
}
}
so, unfortunately now I cannot set -DperformRelease=false..
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHANGES-73) No longer integrates with JIRA
No longer integrates with JIRA -- Key: MCHANGES-73 URL: http://jira.codehaus.org/browse/MCHANGES-73 Project: Maven 2.x Changes Plugin Issue Type: Bug Affects Versions: 2.0-beta-2 Environment: Windows XP, Linux (RHEL3) Reporter: Immo Huneke As of this morning (2nd April 2007), the Maven Changes Plugin suddenly stopped working with a fatal error. Nothing about our POMs or the JIRA system used here had changed overnight - yet we were seeing decoding errors in some builds. In an attempt to resolve the situation, we deleted the local Maven repository - with the result that now ALL builds failed during site generation! The configured issue-tracking section of the POM is as follows: JIRA http://jira-xtools.ldn.swissbank.com:7500/jira/secure/BrowseProject.jspa?pid=10193 We previously had IssueNavigator.jspa, but the result was identical. Part of the error message is shown below: artifact org.apache.maven.skins:maven-default-skin: checking for updates from central Generating /sbclocal/icc/teamcity/buildagent1/ICC_Tools_BuildSystemHooks/SubversionHooks/target/site/jira-report.html Generate "Jira Report" report. JIRA lives at: http://jira-xtools.ldn.swissbank.com:7500/jira FATAL ERROR org/apache/commons/codec/DecoderException Trace java.lang.NoClassDefFoundError: org/apache/commons/codec/DecoderException at org.apache.commons.httpclient.HttpMethodBase.(HttpMethodBase.java:217) at org.apache.commons.httpclient.methods.GetMethod.(GetMethod.java:88) at org.apache.maven.plugin.jira.AbstractJiraDownloader.download(AbstractJiraDownloader.java:479) at org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:241) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:181) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:67) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2920) [M206] Test doesn't work anymore
[ http://jira.codehaus.org/browse/MNG-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated MNG-2920: Attachment: diff.txt here is the diff between 2.0.5 output and 2.0.6 The command line is definitely different -Forking command line: "D:\Program Files\insee\atelier-dev-2\applications\jdk15\jdk-1.5.0_07\jre\bin\java" -classpath d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-archiver\1.0-alpha-7\plexus-archiver-1.0-alpha-7.jar;d:\eewu49\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar;d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-container-default\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar;d:\eewu49\.m2\repository\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar;d:\eewu49\.m2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-utils\1.4.1-SNAPSHOT\plexus-utils-1.4.1-SNAPSHOT.jar;d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-booter\2.3.1-SNAPSHOT\surefire-booter-2.3.1-SNAPSHOT.jar;d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-api\2.3.1-SNAPSHOT\surefire-api-2.3.1-SNAPSHOT.jar org.apache.maven.surefire.booter.SurefireBooter C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire16110tmp C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire16111tmp +Forking command line: cmd.exe /X /C '"D:\Program Files\insee\atelier-dev-2\applications\jdk15\jdk-1.5.0_07\jre\bin\java" -classpath d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-archiver\1.0-alpha-7\plexus-archiver-1.0-alpha-7.jar;d:\eewu49\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar;d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-container-default\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar;d:\eewu49\.m2\repository\classworlds\classworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar;d:\eewu49\.m2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\eewu49\.m2\repository\org\codehaus\plexus\plexus-utils\1.4.1-SNAPSHOT\plexus-utils-1.4.1-SNAPSHOT.jar;d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-booter\2.3.1-SNAPSHOT\surefire-booter-2.3.1-SNAPSHOT.jar;d:\eewu49\.m2\repository\org\apache\maven\surefire\surefire-api\2.3.1-SNAPSHOT\surefire-api-2.3.1-SNAPSHOT.jar org.apache.maven.surefire.booter.SurefireBooter C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire15149tmp C:\DOCUME~1\eewu49\LOCALS~1\Temp\surefire15150tmp' > [M206] Test doesn't work anymore > > > Key: MNG-2920 > URL: http://jira.codehaus.org/browse/MNG-2920 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.6 > Environment: Windows XP >Reporter: Denis Cabasson >Priority: Blocker > Attachments: 206-test.zip, diff.txt, test-exec-205.txt, > test-exec-206.txt > > > When running "mvn test" on the simple use cas attached, M205 is doing fine, > while M206 is crashing with a java.lang.IllegalArgumentException, apparently > due to a diffrence in the command line used to fork the JVM for surefire. > Attached are the 2 executions, with M205 and M206. I haven't managed to > figure out where this bug is coming from -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2920) [M206] Test doesn't work anymore
[ http://jira.codehaus.org/browse/MNG-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated MNG-2920: Attachment: pom.xml The problem only happens with surefire 2.3.1-SNAPSHOT I've tried 2.3 and 2.4-SNAPSHOT and everything is fine > [M206] Test doesn't work anymore > > > Key: MNG-2920 > URL: http://jira.codehaus.org/browse/MNG-2920 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.6 > Environment: Windows XP >Reporter: Denis Cabasson >Priority: Blocker > Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, > test-exec-206.txt > > > When running "mvn test" on the simple use cas attached, M205 is doing fine, > while M206 is crashing with a java.lang.IllegalArgumentException, apparently > due to a diffrence in the command line used to fork the JVM for surefire. > Attached are the 2 executions, with M205 and M206. I haven't managed to > figure out where this bug is coming from -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-316) [M206] Test doesn't work anymore
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez moved MNG-2920 to SUREFIRE-316: -- Affects Version/s: (was: 2.0.6) Key: SUREFIRE-316 (was: MNG-2920) Project: Maven Surefire (was: Maven 2) > [M206] Test doesn't work anymore > > > Key: SUREFIRE-316 > URL: http://jira.codehaus.org/browse/SUREFIRE-316 > Project: Maven Surefire > Issue Type: Bug > Environment: Windows XP >Reporter: Denis Cabasson >Priority: Blocker > Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, > test-exec-206.txt > > > When running "mvn test" on the simple use cas attached, M205 is doing fine, > while M206 is crashing with a java.lang.IllegalArgumentException, apparently > due to a diffrence in the command line used to fork the JVM for surefire. > Attached are the 2 executions, with M205 and M206. I haven't managed to > figure out where this bug is coming from -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-316) [M206] Test doesn't work anymore
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated SUREFIRE-316: Priority: Major (was: Blocker) > [M206] Test doesn't work anymore > > > Key: SUREFIRE-316 > URL: http://jira.codehaus.org/browse/SUREFIRE-316 > Project: Maven Surefire > Issue Type: Bug > Environment: Windows XP >Reporter: Denis Cabasson > Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, > test-exec-206.txt > > > When running "mvn test" on the simple use cas attached, M205 is doing fine, > while M206 is crashing with a java.lang.IllegalArgumentException, apparently > due to a diffrence in the command line used to fork the JVM for surefire. > Attached are the 2 executions, with M205 and M206. I haven't managed to > figure out where this bug is coming from -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1457) Upload OpenOffice.org Java/Uno JARs 2.2.0
Upload OpenOffice.org Java/Uno JARs 2.2.0 - Key: MAVENUPLOAD-1457 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1457 Project: maven-upload-requests Issue Type: Task Reporter: Mirko Nasato OpenOffice.org includes some JARs that can be used in a standalone Java app to connect to a running OpenOffice.org instance. Please find the bundles here: http://www.artofsolving.com/files/juh-2.2.0-bundle.jar http://www.artofsolving.com/files/jurt-2.2.0-bundle.jar http://www.artofsolving.com/files/ridl-2.2.0-bundle.jar http://www.artofsolving.com/files/unoil-2.2.0-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-67) The changes plugin should not hard code the "team-list.html" file
[ http://jira.codehaus.org/browse/MCHANGES-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91806 ] Henning Schmiedehausen commented on MCHANGES-67: Any news on this? I am using this patch in building a site where the team members are listed on a different page and it works well. > The changes plugin should not hard code the "team-list.html" file > -- > > Key: MCHANGES-67 > URL: http://jira.codehaus.org/browse/MCHANGES-67 > Project: Maven 2.x Changes Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-2, 2.0-beta-3 >Reporter: Henning Schmiedehausen > Attachments: changes5.patch > > > Projects that do not have a team-list file or use a different file will have > a number of broken links on the changes-plugin report page. > The attached patch makes the URL of the team-list file configurable with the > default being the "team-list.html" file. This can be changed by setting the > > foo.html > > parameter. When this parameter is set to empty (e.g. > > > > then no link is generated and just the names are reported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-118) J2EE (runtime) dependencies of a Webapp-Library-Parent hierarchy not correct
[ http://jira.codehaus.org/browse/MECLIPSE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91809 ] Cameron Fieber commented on MECLIPSE-118: - this problem still occurs in 2.3 > J2EE (runtime) dependencies of a Webapp-Library-Parent hierarchy not correct > > > Key: MECLIPSE-118 > URL: http://jira.codehaus.org/browse/MECLIPSE-118 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.2 >Reporter: Andreas Schildbach > > When "mvn eclipse:eclipse" is invoked on the parent project P of two modules, > a webapp W and a dependant library L, the J2EE (runtime) dependencies are not > done right. This means that the classes of L are not available to W if W is > deployed in a container with Web Tools Project > In GUI talk, the project needs to be checked in the tab "Project J2EE > dependencies" of the projects properties. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
[
http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91810
]
Jason Chaffee commented on SUREFIRE-316:
> > This works fine in maven-2.0.5.
> >
> > I have the following surefire configuration:
> >
> >
> > org.apache.maven.plugins
> > maven-surefire-plugin
> >
> > once
> >
> >
> -javaagent:${project.build.directory}/test-lib/aspectjweaver.
> ja
> > r -Xmx256m
> >
> >
> >
> > I get this error in 2.0.6
> >
> > [INFO] [surefire:test]
> > [INFO]
> >
> --
> --
> > [ERROR] FATAL ERROR
> > [INFO]
> >
> --
> --
> > [INFO] null
> > [INFO]
> >
> --
> --
> > [INFO] Trace
> > java.lang.NullPointerException
> > at
> > org.apache.maven.artifact.DefaultArtifact.getSelectedVersion(Default
> > A
> > rtifact.java:582)
> > at
> > org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBoo
> > t
> > er(SurefirePlugin.java:490)
> > at
> > org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlug
> > i
> > n.java:391)
> > at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlug
> > i
> > nManager.java:443)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Def
> > a
> > ultLifecycleExecutor.java:539)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithL
> > i
> > fecycle(DefaultLifecycleExecutor.java:480)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defa
> > u
> > ltLifecycleExecutor.java:459)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa
> > n
> > dleFailures(DefaultLifecycleExecutor.java:311)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme
> > n
> > ts(DefaultLifecycleExecutor.java:278)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultL
> > i
> > fecycleExecutor.java:143)
> > at
> > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> > at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> > java:39)
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce
> > s
> > sorImpl.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)
> [M206] Test doesn't work anymore
>
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
>Reporter: Denis Cabasson
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt,
> test-exec-206.txt
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine,
> while M206 is crashing with a java.lang.IllegalArgumentException, apparently
> due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to
> figure out where this bug is coming from
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91811 ] Carlos Sanchez commented on SUREFIRE-316: - I don't see how that last comment relates to this issue, this one is about a IllegalArgumentException Also try setting explicitly the plugin version as in attached pom to know what version of surefire plugin are you using > [M206] Test doesn't work anymore > > > Key: SUREFIRE-316 > URL: http://jira.codehaus.org/browse/SUREFIRE-316 > Project: Maven Surefire > Issue Type: Bug > Environment: Windows XP >Reporter: Denis Cabasson > Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, > test-exec-206.txt > > > When running "mvn test" on the simple use cas attached, M205 is doing fine, > while M206 is crashing with a java.lang.IllegalArgumentException, apparently > due to a diffrence in the command line used to fork the JVM for surefire. > Attached are the 2 executions, with M205 and M206. I haven't managed to > figure out where this bug is coming from -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (WAGON-77) Amazon S3 provider
[ http://jira.codehaus.org/browse/WAGON-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Redmond resolved WAGON-77. --- Resolution: Fixed committed > Amazon S3 provider > -- > > Key: WAGON-77 > URL: http://jira.codehaus.org/browse/WAGON-77 > Project: wagon > Issue Type: New Feature >Reporter: Eric Redmond >Priority: Minor > Attachments: wagon-s3-2.diff, wagon-s3.diff > > > Attached is a wagon provider for uploading to / downloading from Amazon's S3 > accounts - utilizes the jets3t package, and includes REST and SOAP interfaces. > Note: You must have a valid S3 account key to test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91815 ] Jason Chaffee commented on SUREFIRE-316: Ok, I will create a new issue. I have stated on several occasions that I am using version 2.3 of the surefire plugin with both 2.0.5 and 2.0.6 . It works in 2.0.5 and it does not work in 2.0.6. I actually do think these bugs are related because it is related to the forking and my case is causing a different Exception. > [M206] Test doesn't work anymore > > > Key: SUREFIRE-316 > URL: http://jira.codehaus.org/browse/SUREFIRE-316 > Project: Maven Surefire > Issue Type: Bug > Environment: Windows XP >Reporter: Denis Cabasson > Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, > test-exec-206.txt > > > When running "mvn test" on the simple use cas attached, M205 is doing fine, > while M206 is crashing with a java.lang.IllegalArgumentException, apparently > due to a diffrence in the command line used to fork the JVM for surefire. > Attached are the 2 executions, with M205 and M206. I haven't managed to > figure out where this bug is coming from -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-292) Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in memory clientspec names
[ http://jira.codehaus.org/browse/SCM-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-292: - Assignee: Mike Perham > Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in > memory clientspec names > > > Key: SCM-292 > URL: http://jira.codehaus.org/browse/SCM-292 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-perforce >Affects Versions: 1.0-beta-4 >Reporter: Emmanuel Venisse > Assigned To: Mike Perham >Priority: Critical > Fix For: 1.0 > > > With a Map instead of a system property, we'll can support more that one > clientspec in the jvm. It's necessary for Continuum because it access to more > than one project in Perforce. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91818 ] Carlos Sanchez commented on SUREFIRE-316: - but the example you are putting doesn't have tag, how are you setting the version of the plugin? > [M206] Test doesn't work anymore > > > Key: SUREFIRE-316 > URL: http://jira.codehaus.org/browse/SUREFIRE-316 > Project: Maven Surefire > Issue Type: Bug > Environment: Windows XP >Reporter: Denis Cabasson > Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, > test-exec-206.txt > > > When running "mvn test" on the simple use cas attached, M205 is doing fine, > while M206 is crashing with a java.lang.IllegalArgumentException, apparently > due to a diffrence in the command line used to fork the JVM for surefire. > Attached are the 2 executions, with M205 and M206. I haven't managed to > figure out where this bug is coming from -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SCM-21) separate revision and tag handling
[
http://jira.codehaus.org/browse/SCM-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse closed SCM-21.
---
Assignee: Emmanuel Venisse
Resolution: Fixed
Fix Version/s: (was: future)
1.0
> separate revision and tag handling
> --
>
> Key: SCM-21
> URL: http://jira.codehaus.org/browse/SCM-21
> Project: Maven SCM
> Issue Type: Task
> Components: maven-scm-api
>Reporter: Brett Porter
> Assigned To: Emmanuel Venisse
> Fix For: 1.0
>
>
> while in CVS revision# and tag are handled in the same way, the concepts can
> be separated and will make other SCMs easier.
> for example, in subversion, valid revisions are:
> rev#
> HEAD
> BASE
> COMMITTED
> PREV
> {DATE}
> tags are normal checkouts from a different base.
> In CVS, revisions are:
> rev# (per file only really makes sense here, but can apply to several)
> HEAD
> SOME_BRANCH_TAG
> {DATE}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-292) Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in memory clientspec names
[
http://jira.codehaus.org/browse/SCM-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91824
]
Mike Perham commented on SCM-292:
-
E, can you give more details about how you expect this to work? Am I supposed
to map { directory -> clientspec-name }? The SCM provider really only knows
the current directory it is working with. So how will Continuum pass me the
clientspec name to use?
> Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in
> memory clientspec names
>
>
> Key: SCM-292
> URL: http://jira.codehaus.org/browse/SCM-292
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-perforce
>Affects Versions: 1.0-beta-4
>Reporter: Emmanuel Venisse
> Assigned To: Patrick Schneider
>Priority: Critical
> Fix For: 1.0
>
>
> With a Map instead of a system property, we'll can support more that one
> clientspec in the jvm. It's necessary for Continuum because it access to more
> than one project in Perforce.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-292) Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in memory clientspec names
[ http://jira.codehaus.org/browse/SCM-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91825 ] Emmanuel Venisse commented on SCM-292: -- Continuum know only the scm url.and the working directory. The actual DEFAULT_CLIENTSPEC_PROPERTY system property can't be used because in a CI tool like continuum, we manage more that one project so more than one clientspec, and this system property allow only one. I thought to a map that will contain all client specs with the scm url in the key and the client spec in the value. Do you think it can work? The client spec is generated at the end of the checkout, right? > Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in > memory clientspec names > > > Key: SCM-292 > URL: http://jira.codehaus.org/browse/SCM-292 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-perforce >Affects Versions: 1.0-beta-4 >Reporter: Emmanuel Venisse > Assigned To: Patrick Schneider >Priority: Critical > Fix For: 1.0 > > > With a Map instead of a system property, we'll can support more that one > clientspec in the jvm. It's necessary for Continuum because it access to more > than one project in Perforce. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1457) Upload OpenOffice.org Java/Uno JARs 2.2.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1457. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload OpenOffice.org Java/Uno JARs 2.2.0 > - > > Key: MAVENUPLOAD-1457 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1457 > Project: maven-upload-requests > Issue Type: Task >Reporter: Mirko Nasato > Assigned To: Carlos Sanchez > > OpenOffice.org includes some JARs that can be used in a standalone Java app > to connect to a running OpenOffice.org instance. > Please find the bundles here: > http://www.artofsolving.com/files/juh-2.2.0-bundle.jar > http://www.artofsolving.com/files/jurt-2.2.0-bundle.jar > http://www.artofsolving.com/files/ridl-2.2.0-bundle.jar > http://www.artofsolving.com/files/unoil-2.2.0-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1456) JasperReports 1.3.2 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1456. --- Assignee: Carlos Sanchez Resolution: Fixed > JasperReports 1.3.2 upload > -- > > Key: MAVENUPLOAD-1456 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1456 > Project: maven-upload-requests > Issue Type: Task >Reporter: Teodor Danciu > Assigned To: Carlos Sanchez > > http://rs.jaspersoft.com/maven2/jasperreports-1.3.2-bundle.jar > http://sourceforge.net/projects/jasperreports > http://sourceforge.net/project/memberlist.php?group_id=36382 > Open Source Reporting Engine -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1455) java exchange connector
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91826 ] Carlos Sanchez commented on MAVENUPLOAD-1455: - missing license and scm info > java exchange connector > --- > > Key: MAVENUPLOAD-1455 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1455 > Project: maven-upload-requests > Issue Type: Wish >Reporter: eli hasson > > java exchange connector is a pure java api for Microsoft exchange server. > for more information: > [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1447) upload vraptor 2.3.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1447. --- Assignee: Carlos Sanchez Resolution: Cannot Reproduce > upload vraptor 2.3.2 > > > Key: MAVENUPLOAD-1447 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1447 > Project: maven-upload-requests > Issue Type: Task >Reporter: Nico Steppat > Assigned To: Carlos Sanchez > > VRaptor 2 is a mvc controller based on the idea (stolen) from Rails that > configuration should be minimal and conventions should be maximized. > VRaptor's 2.3.2 comes with many bug fixes, better spring ioc integration, > support on constructor injection on interceptors and auto-loading disabling > option. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1451) upload apt-jelly
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1451. --- Assignee: Carlos Sanchez Resolution: Fixed > upload apt-jelly > > > Key: MAVENUPLOAD-1451 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1451 > Project: maven-upload-requests > Issue Type: Task >Reporter: Ryan Heaton > Assigned To: Carlos Sanchez > > http://apt-jelly.sf.net/apt-jelly-2.3-bundle.jar > http://apt-jelly.sf.net/ > http://apt-jelly.sourceforge.net/index.html#about > APT-Jelly is an engine for generating artifacts from Java source code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MAVENUPLOAD-1447) upload vraptor 2.3.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez reopened MAVENUPLOAD-1447: - > upload vraptor 2.3.2 > > > Key: MAVENUPLOAD-1447 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1447 > Project: maven-upload-requests > Issue Type: Task >Reporter: Nico Steppat > Assigned To: Carlos Sanchez > > VRaptor 2 is a mvc controller based on the idea (stolen) from Rails that > configuration should be minimal and conventions should be maximized. > VRaptor's 2.3.2 comes with many bug fixes, better spring ioc integration, > support on constructor injection on interceptors and auto-loading disabling > option. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1447) upload vraptor 2.3.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1447. --- Resolution: Incomplete > upload vraptor 2.3.2 > > > Key: MAVENUPLOAD-1447 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1447 > Project: maven-upload-requests > Issue Type: Task >Reporter: Nico Steppat > Assigned To: Carlos Sanchez > > VRaptor 2 is a mvc controller based on the idea (stolen) from Rails that > configuration should be minimal and conventions should be maximized. > VRaptor's 2.3.2 comes with many bug fixes, better spring ioc integration, > support on constructor injection on interceptors and auto-loading disabling > option. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (WAGON-77) Amazon S3 provider
[ http://jira.codehaus.org/browse/WAGON-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Redmond closed WAGON-77. - > Amazon S3 provider > -- > > Key: WAGON-77 > URL: http://jira.codehaus.org/browse/WAGON-77 > Project: wagon > Issue Type: New Feature >Reporter: Eric Redmond >Priority: Minor > Attachments: wagon-s3-2.diff, wagon-s3.diff > > > Attached is a wagon provider for uploading to / downloading from Amazon's S3 > accounts - utilizes the jets3t package, and includes REST and SOAP interfaces. > Note: You must have a valid S3 account key to test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-316) [M206] Test doesn't work anymore
[
http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91827
]
Jason Chaffee commented on SUREFIRE-316:
The version is being set in a parent pom that has the . The
configuration I provided is the the specific configuration for a particular
project that manifests this bug. In other words, I have the following config
in the parent pom.xml:
org.apache.maven.plugins
maven-surefire-plugin
2.3
true
false
user.dir
${basedir}
sun.net.client.defaultConnectTimeout
6
sun.net.client.defaultReadTimeout
6
> [M206] Test doesn't work anymore
>
>
> Key: SUREFIRE-316
> URL: http://jira.codehaus.org/browse/SUREFIRE-316
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Windows XP
>Reporter: Denis Cabasson
> Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt,
> test-exec-206.txt
>
>
> When running "mvn test" on the simple use cas attached, M205 is doing fine,
> while M206 is crashing with a java.lang.IllegalArgumentException, apparently
> due to a diffrence in the command line used to fork the JVM for surefire.
> Attached are the 2 executions, with M205 and M206. I haven't managed to
> figure out where this bug is coming from
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-316) [M206] Test doesn't work anymore
[ http://jira.codehaus.org/browse/SUREFIRE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated SUREFIRE-316: Attachment: test.tgz Jason, i can't reproduce your error, try attached sample I imagine you just pasted the wrong xml, because you are missing the plugins tag between plugin and pluginManagement > [M206] Test doesn't work anymore > > > Key: SUREFIRE-316 > URL: http://jira.codehaus.org/browse/SUREFIRE-316 > Project: Maven Surefire > Issue Type: Bug > Environment: Windows XP >Reporter: Denis Cabasson > Attachments: 206-test.zip, diff.txt, pom.xml, test-exec-205.txt, > test-exec-206.txt, test.tgz > > > When running "mvn test" on the simple use cas attached, M205 is doing fine, > while M206 is crashing with a java.lang.IllegalArgumentException, apparently > due to a diffrence in the command line used to fork the JVM for surefire. > Attached are the 2 executions, with M205 and M206. I haven't managed to > figure out where this bug is coming from -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-292) Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in memory clientspec names
[ http://jira.codehaus.org/browse/SCM-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91830 ] Patrick Schneider commented on SCM-292: --- I am pretty busy, but I can take a look. > Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in > memory clientspec names > > > Key: SCM-292 > URL: http://jira.codehaus.org/browse/SCM-292 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-perforce >Affects Versions: 1.0-beta-4 >Reporter: Emmanuel Venisse > Assigned To: Patrick Schneider >Priority: Critical > Fix For: 1.0 > > > With a Map instead of a system property, we'll can support more that one > clientspec in the jvm. It's necessary for Continuum because it access to more > than one project in Perforce. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-292) Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in memory clientspec names
[ http://jira.codehaus.org/browse/SCM-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91832 ] Mike Perham commented on SCM-292: - But where does this map come from? Who creates it? No, the clientspec is completely independent from the checkout and in most cases is not created by the provider. > Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in > memory clientspec names > > > Key: SCM-292 > URL: http://jira.codehaus.org/browse/SCM-292 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-perforce >Affects Versions: 1.0-beta-4 >Reporter: Emmanuel Venisse > Assigned To: Patrick Schneider >Priority: Critical > Fix For: 1.0 > > > With a Map instead of a system property, we'll can support more that one > clientspec in the jvm. It's necessary for Continuum because it access to more > than one project in Perforce. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-292) Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in memory clientspec names
[ http://jira.codehaus.org/browse/SCM-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91833 ] Mike Perham commented on SCM-292: - I might be able to get the existing clientspec name using 'p4 where pom.xml' and examining the output but this doesn't help in the case where I want to checkout a new project using an existing clientspec. Let me think about this more. > Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in > memory clientspec names > > > Key: SCM-292 > URL: http://jira.codehaus.org/browse/SCM-292 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-perforce >Affects Versions: 1.0-beta-4 >Reporter: Emmanuel Venisse > Assigned To: Patrick Schneider >Priority: Critical > Fix For: 1.0 > > > With a Map instead of a system property, we'll can support more that one > clientspec in the jvm. It's necessary for Continuum because it access to more > than one project in Perforce. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MGROOVY-1) Support mojo plugin.xml generation for Groovy mojos
[
http://jira.codehaus.org/browse/MGROOVY-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91837
]
Jason Dillon commented on MGROOVY-1:
FYI, I've recently learned (from looking at the new groovydoc sources) how to
use the existing compiler to parse out all of the details needed to generate
the plugin.xml from a *.groovy source. Might have this working by the end of
the week, with Groovy 1.0 too :-)
> Support mojo plugin.xml generation for Groovy mojos
> ---
>
> Key: MGROOVY-1
> URL: http://jira.codehaus.org/browse/MGROOVY-1
> Project: Maven 2.x Groovy Plugin
> Issue Type: New Feature
>Reporter: Jason Dillon
> Assigned To: Jason Dillon
> Fix For: 1.0-alpha-3
>
>
> Right now there isn't really a good way to generate a plugin.xml for a Mojo
> implemented in Groovy.
> There is the {{javalike-maven-plugin-tools}} module which kinda works, though
> requires some icky ";" tokens to get qDox to properly parse out javadocs for
> parameters. I'm not sure that this module handles annotations on
> super-classes either.
> I've hacked up an extractor.groovy a while ago (MNG-1664) which uses regex,
> but that doesn't handle super-classes either.
> Really need a nice way to parse regular groovy (w/o needing ";') to generate
> a plugin.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MGROOVY-25) Groovy scripts compiled by the maven groovy plugin does not have the org.apache.maven.plugin package on its classpath
Groovy scripts compiled by the maven groovy plugin does not have the
org.apache.maven.plugin package on its classpath
-
Key: MGROOVY-25
URL: http://jira.codehaus.org/browse/MGROOVY-25
Project: Maven 2.x Groovy Plugin
Issue Type: Bug
Affects Versions: 1.0-alpha-2
Environment: all
Reporter: Jesse Eichar
Assigned To: Jason Dillon
Priority: Minor
consider the following script:
class ScriptClass{
def testRequirements(){
def requiredFile=new File("/requiredFile")
if( !requiredFile.exists ){
throw new org.apache.maven.plugin.MojoFailureException( "RequiredFile
does not exist" )
}
}
}
This script will not compile correctly using the compile plugin because the
MojoFailureException is not on the classpath. As a work around you can throw
an AssertionError or a RuntimeException but in both cases you get a big ugly
stacktrace. If you can throw a MojoFailureException the maven build will fail
cleaning reporting the error and the stack trace can be shown using the -e
stack trace.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MGROOVY-25) Groovy scripts compiled by the maven groovy plugin does not have the org.apache.maven.plugin package on its classpath
[
http://jira.codehaus.org/browse/MGROOVY-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91838
]
Jesse Eichar commented on MGROOVY-25:
-
I tried looking for a maven plugin that I could add as a dependency but
couldn't find one. If you can find one maybe that can be the fix. But it
seems to be part of the default maven.
I think this is the area to look for. This may just be a case of ignorance on
my part and not a bug at all.
> Groovy scripts compiled by the maven groovy plugin does not have the
> org.apache.maven.plugin package on its classpath
> -
>
> Key: MGROOVY-25
> URL: http://jira.codehaus.org/browse/MGROOVY-25
> Project: Maven 2.x Groovy Plugin
> Issue Type: Bug
>Affects Versions: 1.0-alpha-2
> Environment: all
>Reporter: Jesse Eichar
> Assigned To: Jason Dillon
>Priority: Minor
>
> consider the following script:
> class ScriptClass{
> def testRequirements(){
> def requiredFile=new File("/requiredFile")
> if( !requiredFile.exists ){
> throw new org.apache.maven.plugin.MojoFailureException( "RequiredFile
> does not exist" )
> }
> }
> }
> This script will not compile correctly using the compile plugin because the
> MojoFailureException is not on the classpath. As a work around you can throw
> an AssertionError or a RuntimeException but in both cases you get a big ugly
> stacktrace. If you can throw a MojoFailureException the maven build will
> fail cleaning reporting the error and the stack trace can be shown using the
> -e stack trace.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MGROOVY-25) Groovy scripts compiled by the maven groovy plugin does not have the org.apache.maven.plugin package on its classpath
[
http://jira.codehaus.org/browse/MGROOVY-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91839
]
Jason Dillon commented on MGROOVY-25:
-
You need to include *everything* you depend on when compiling, including any
Maven or Groovy bits. They are not currently included to avoid classloading
issues. May eventually add an optional flag to propagate the plugins classpath
to the compiler, but right now you need to be very explicit when using
groovy:compile or groovy:testCompile.
--jason
> Groovy scripts compiled by the maven groovy plugin does not have the
> org.apache.maven.plugin package on its classpath
> -
>
> Key: MGROOVY-25
> URL: http://jira.codehaus.org/browse/MGROOVY-25
> Project: Maven 2.x Groovy Plugin
> Issue Type: Bug
>Affects Versions: 1.0-alpha-2
> Environment: all
>Reporter: Jesse Eichar
> Assigned To: Jason Dillon
>Priority: Minor
>
> consider the following script:
> class ScriptClass{
> def testRequirements(){
> def requiredFile=new File("/requiredFile")
> if( !requiredFile.exists ){
> throw new org.apache.maven.plugin.MojoFailureException( "RequiredFile
> does not exist" )
> }
> }
> }
> This script will not compile correctly using the compile plugin because the
> MojoFailureException is not on the classpath. As a work around you can throw
> an AssertionError or a RuntimeException but in both cases you get a big ugly
> stacktrace. If you can throw a MojoFailureException the maven build will
> fail cleaning reporting the error and the stack trace can be shown using the
> -e stack trace.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-141) Possible security hole when deploying site
[ http://jira.codehaus.org/browse/MSITE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MSITE-141: --- Fix Version/s: 2.0-beta-7 > Possible security hole when deploying site > -- > > Key: MSITE-141 > URL: http://jira.codehaus.org/browse/MSITE-141 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 > Environment: Linux gentoo 2.6.16 64bit, maven 2.0.2 >Reporter: Martin Vysny >Priority: Critical > Fix For: 2.0-beta-7 > > > When the site is deployed into a directory /foo/bar, the following command is > issued over a ssh: > chmod -Rf g+w /foo/bar/ > it was intended to use g+r I presume? :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-47) validate input format of docs
[ http://jira.codehaus.org/browse/MSITE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MSITE-47: -- Fix Version/s: 2.0-beta-7 > validate input format of docs > - > > Key: MSITE-47 > URL: http://jira.codehaus.org/browse/MSITE-47 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Brett Porter > Fix For: 2.0-beta-7 > > > valid: > - xdoc > - apt (done on the fly) > - fml > - site.xml > (most should be on the fly, verify that it handles appropriately). > Perhaps make whether this is an error or ignored should be configurable -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-130) Site generation fails for site.xml in UTF8 with BOM
[ http://jira.codehaus.org/browse/MSITE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MSITE-130: --- Fix Version/s: 2.0-beta-7 > Site generation fails for site.xml in UTF8 with BOM > --- > > Key: MSITE-130 > URL: http://jira.codehaus.org/browse/MSITE-130 > Project: Maven 2.x Site Plugin > Issue Type: Improvement >Reporter: Shinobu Kawai >Priority: Critical > Fix For: 2.0-beta-7 > > > I get the following error if I edit site.xml with Windows Notepad. > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error during page generation > Embedded error: Can't read site descriptor. > only whitespace content allowed before start tag and not \uef (position: > START_DOCUMENT seen \uef... @1:1) > This is due to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4508058 . > Since Sun is saying they won't fix this "RFE" (which I think is a bug), we > need a workaround. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-135) inherited site.xml files are interpolated with the originating project's model values and not the consumer project's values
[
http://jira.codehaus.org/browse/MSITE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MSITE-135:
---
Fix Version/s: 2.0-beta-7
> inherited site.xml files are interpolated with the originating project's
> model values and not the consumer project's values
> ---
>
> Key: MSITE-135
> URL: http://jira.codehaus.org/browse/MSITE-135
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-5
> Environment: 2.0.4
>Reporter: John Allen
> Fix For: 2.0-beta-7
>
>
> inherited site.xml files are interpolated with the originating project's
> model values and not the consumer project's values
> i have a n-deep multiproject env; when a sub-project uses the root project's
> site.xml file, any ${project.*} expressions defined in the root site.xml are
> replaced with values from the root project and not the project that is being
> rendered, ie. title in index.html would be "root project" and not
> "sub-sub-sub-project". This applied to all ${project.*} expressions in the
> site.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-163) site modules menu does not inherit
[ http://jira.codehaus.org/browse/MSITE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MSITE-163: --- Fix Version/s: 2.0-beta-7 > site modules menu does not inherit > -- > > Key: MSITE-163 > URL: http://jira.codehaus.org/browse/MSITE-163 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 > Environment: ubuntu linux / debian linux >Reporter: Andrew Williams > Fix For: 2.0-beta-7 > > > if I have a site.xml in a parent project that contains the line ref="modules" inherit="top" /> it is not inherited by child projects. > works, as does parent. > This happens when the parent project has no modules of its own. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-105) review error handling
review error handling - Key: DOXIA-105 URL: http://jira.codehaus.org/browse/DOXIA-105 Project: doxia Issue Type: Improvement Components: Core Reporter: Brett Porter Fix For: 1.0 Issue to revise how errors are handled through Doxia as there seem to be occasional stack traces shown for non-fatal errors, and some errors being swallowed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-170) [ERROR] VM #displayTree: error : too few arguments to macro
[ http://jira.codehaus.org/browse/MSITE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MSITE-170: --- Fix Version/s: 2.0-beta-6 Does velocity 1.5 help with this? > [ERROR] VM #displayTree: error : too few arguments to macro > --- > > Key: MSITE-170 > URL: http://jira.codehaus.org/browse/MSITE-170 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: fabrizio giustina > Fix For: 2.0-beta-6 > > > when running mvn site:site a couple of "too few arguments to macro" always > pop up. This is extremely bad in terms of user experience, and we should find > a way to remove these logs: > [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0 > [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0 > These errors are due to a known velocity bug related to the use of recursive > macros: > http://issues.apache.org/bugzilla/show_bug.cgi?id=13623 > http://mail-archives.apache.org/mod_mbox/jakarta-velocity-user/200402.mbox/[EMAIL > PROTECTED] > Recursive macros are defined in > org/apache/maven/doxia/siterenderer/resources/default-site.vm in the doxia > site-renderer component. > Logging is handled in the plexus velocity component. > This velocity bug is still open in velocity and no patch will be available > anytime soon. In the meanwhile we should try to handle this situation in some > way by filtering out messages or removing the use of recursive macros (very > hard, they are used to print out the site tree)... or switching to a better > templating engine like freemarker. > This issue could probably be addressed in the plexus velocity component or in > the doxia site renderer (given that waiting for a bugfixed velocity release > is not an option). I'm anyway assigning it to the site plugin since it's > where users see these logs coming from and where probably users could open > similar issues. > Any suggestion on how to dirty-patch this? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-194) xdoc's gets rendered in the HTML body, not in head
[ http://jira.codehaus.org/browse/MSITE-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MSITE-194: --- Fix Version/s: 2.0-beta-7 > xdoc's gets rendered in the HTML body, not in head > -- > > Key: MSITE-194 > URL: http://jira.codehaus.org/browse/MSITE-194 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: Brett Porter > Fix For: 2.0-beta-7 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-179) Maven-site-plugin ignores the encoding specified in XML file (e.g. site.xml or xdoc/x.xml).
[ http://jira.codehaus.org/browse/MSITE-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MSITE-179: --- Fix Version/s: 2.0-beta-7 > Maven-site-plugin ignores the encoding specified in XML file (e.g. site.xml > or xdoc/x.xml). > --- > > Key: MSITE-179 > URL: http://jira.codehaus.org/browse/MSITE-179 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Bernhard Wellhöfer > Fix For: 2.0-beta-7 > > Attachments: MSITE179DemoProject.zip > > > Each XML document defines the used encoding. The maven-site-plugin ignores > this encoding and always uses the value of the inputEncoding configuration > value. The inputEncoding value should only be used for the non XML site files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-177) Docs are not updated if only site.xml changed
[ http://jira.codehaus.org/browse/MSITE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MSITE-177: --- Fix Version/s: 2.0-beta-7 > Docs are not updated if only site.xml changed > - > > Key: MSITE-177 > URL: http://jira.codehaus.org/browse/MSITE-177 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: Jörg Hohwiller > Fix For: 2.0-beta-7 > > > If I update site.xml (e.g. add new menu-items) and regenerate my existing > site, the index gets updated but other existing pages are not rebuild and > therefore show the menus in the state before the site.xml has changed (so new > menus are missing). This causes a confusing site where menus appear and > disappear while surfing. > I only use xdos (and they are in a subfolder) so I can not tell if this > happens with apt as well. I reproduced the problem with "mvn site" and "mvn > site:stage". > As a workaround I can delete the old site before building. Since I stage the > site directly to the final destination on the local machine where it is > served this is not very suitable because then the site is broken until it is > completely rebuild. > If you consider to fix this issue please beware that site.xml can inherit > stuff in multiproject envronments. > So it is unclear if the optimization to only re-generate if something has > changed makes sense at all. It might be quite complicated to determine this - > the question is how much time is saved by this at all. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIA-82) Doxia default site renderer redefines local macros over and over again
[ http://jira.codehaus.org/browse/DOXIA-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated DOXIA-82: -- Fix Version/s: 1.0 > Doxia default site renderer redefines local macros over and over again > -- > > Key: DOXIA-82 > URL: http://jira.codehaus.org/browse/DOXIA-82 > Project: doxia > Issue Type: Bug >Reporter: Henning Schmiedehausen > Fix For: 1.0 > > > The Doxia default site renderer uses Apache Velocity to render its pages. > Every time a page is rendered, Doxia tries to define Velocity Macros but the > Plexus Velocity component sets the replacement of Velocity Macro to false > (the default). > In Velocity Version 1.4, these error messages are silently discarded. In > newer Versions (1.5 beta 2 and beyond), these messages are logged out and > appear to be errors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIA-92) cannot load images in APT files
[ http://jira.codehaus.org/browse/DOXIA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated DOXIA-92: -- Fix Version/s: 1.0 Patch attached: Yes > cannot load images in APT files > --- > > Key: DOXIA-92 > URL: http://jira.codehaus.org/browse/DOXIA-92 > Project: doxia > Issue Type: Bug >Reporter: Martin Goldhahn >Priority: Critical > Fix For: 1.0 > > Attachments: DoxiaRenderBooksMojo.patch, ITextSink.patch > > > I want to render an APT file that I use in my site as a PDF file. > Maven's site plugin finds the image because it is located in > src/site/resources. It seams that this path is not added to doxia's > classpath. Thus it cannot find the image. > How do I tell the doxia-maven-plugin that it should search the resources > folder as well? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIA-91) Update Doxia Decoration model to actually work in reactor build.
[ http://jira.codehaus.org/browse/DOXIA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated DOXIA-91: -- Fix Version/s: 1.0 > Update Doxia Decoration model to actually work in reactor build. > > > Key: DOXIA-91 > URL: http://jira.codehaus.org/browse/DOXIA-91 > Project: doxia > Issue Type: Improvement > Components: Decoration Model >Reporter: Henning Schmiedehausen > Fix For: 1.0 > > Attachments: doxia-decoration-3.patch, doxia-decoration.patch, > doxia-decoration.patch, > org.apache.maven.doxia.site.decoration.inheritance.DecorationModelInheritenceAssemblerTest.txt > > > This is a major patch to the decoration model to bring some sanity in the > link resolution when it is used under the reactor build. It generates > breadcrumbs and item links correctly in all scenarios that I have tested (the > current HEAD code does not) and passes all the unit tests that are already > there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIA-95) Doxia omits closing elements
[ http://jira.codehaus.org/browse/DOXIA-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated DOXIA-95: -- Fix Version/s: 1.0-alpha-9 > Doxia omits closing elements > - > > Key: DOXIA-95 > URL: http://jira.codehaus.org/browse/DOXIA-95 > Project: doxia > Issue Type: Bug >Reporter: Henning Schmiedehausen > Fix For: 1.0-alpha-9 > > > Consider the following xdoc file: > > > > test1 > > > > text > > list1 > > text2 > > list1 > > > > > > This renders to the following HTML output: > section name > text > > list1 > > text2 > > list1 > > > Please note that there is no closing between and > This is obviously no valid XHTML. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-315) The redirectTestOutputToFile does not handle output before tests, nor does it handle capturing output on both streams
[ http://jira.codehaus.org/browse/SUREFIRE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-315: -- Fix Version/s: 2.3.1 Patch attached: Yes > The redirectTestOutputToFile does not handle output before tests, nor does it > handle capturing output on both streams > - > > Key: SUREFIRE-315 > URL: http://jira.codehaus.org/browse/SUREFIRE-315 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Jason Dillon >Priority: Critical > Fix For: 2.3.1 > > Attachments: SUREFIRE-315.diff > > > The redirectTestOutputToFile feature does not handle cases when output is > soaked up before the tests actually run, like output from static blocks or > from test case constructors. If output is detected before the > testSetStarting is invoked, then all further output will be due to a thrown > ISE, which gets eatten up somewhere in surefire. > Additionally, when a test outputs to STDOUT and STDERR, the output is not > muxed properly into the -output.txt file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2461) Write JavaDoc documentation
[ http://jira.codehaus.org/browse/MNG-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91843 ] Art Pope commented on MNG-2461: --- Classes in org.apache.maven.reporting, such as MavenReport, also lack javadoc comments, making it difficult to write report plugins. > Write JavaDoc documentation > --- > > Key: MNG-2461 > URL: http://jira.codehaus.org/browse/MNG-2461 > Project: Maven 2 > Issue Type: Task > Components: Documentation: General >Reporter: Simon Kepp Nielsen >Priority: Critical > > There hardly exists any JavaDoc documentation for Maven 2. Even very central > classes such as Mojo, AbstractMojo, MavenProject, MavenProjectHelper and > Artifact are completely undocumented. This makes it very difficult to write > your own plugins, which seriously limits adoption of Maven 2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-67) j2ee archetype unbuildable
j2ee archetype unbuildable -- Key: ARCHETYPE-67 URL: http://jira.codehaus.org/browse/ARCHETYPE-67 Project: Maven Archetype Issue Type: Bug Components: Archetypes Affects Versions: 1.0 Reporter: Eric Redmond The archetype pom contains a "site" module that is not created when running the archetype. Please remove. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MSOURCES-14) Replace maven-verifier with maven-plugin-testing-harness
[ http://jira.codehaus.org/browse/MSOURCES-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MSOURCES-14 started by Maria Odea Ching. > Replace maven-verifier with maven-plugin-testing-harness > > > Key: MSOURCES-14 > URL: http://jira.codehaus.org/browse/MSOURCES-14 > Project: Maven 2.x Sources Plugin > Issue Type: Bug >Affects Versions: 2.0.3 >Reporter: Jochen Wiedmann > Assigned To: Maria Odea Ching > Attachments: maven-source-plugin-harness.patch > > > The test suite of the maven-sources-plugin is currently based on the > maven-verifier. This has the undesirable consequence, that the test uses the > *installed* version of the maven-sources-plugin, as opposed to the local > version. > The attached patch replaces the maven-verifier with the > maven-plugin-testing-harness, which doesn't suffer from the same problem. > Additionally, the speed of the test suite is drastically improved. > For reviewers: When considering the patches quality, keep in mind that the > actual Mojo classes and the concrete test classes are almost unchanged. (For > the latter, there is the required addition of a protected method getGoal().) > For reviewers: Note the following comment in AbstractSourcePluginTestCase: > * I don't know, why revision 518116 of this class had the parameters > * "properties" and "expectNoErrors". The following checks > demonstrate, > * that the parameters aren't actually used and may safely be removed. > * This should be done by the patch reviewer. > I recommend that the reviewer follows my suggestion by applying a refactoring > method after applying my patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-223) make velocity processing of input documents optional
make velocity processing of input documents optional Key: MSITE-223 URL: http://jira.codehaus.org/browse/MSITE-223 Project: Maven 2.x Site Plugin Issue Type: Task Affects Versions: 2.0-beta-6 Reporter: Brett Porter per discussion on dev list - we need to do this before the next site plugin release. There are probably a couple of implementation options: - only processing files that have .vm appended to the filename - adding configuration to the site plugin that is passed through to doxia as includes/excludes - ...? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-223) make velocity processing of input documents optional
[ http://jira.codehaus.org/browse/MSITE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MSITE-223: --- Fix Version/s: 2.0-beta-6 > make velocity processing of input documents optional > > > Key: MSITE-223 > URL: http://jira.codehaus.org/browse/MSITE-223 > Project: Maven 2.x Site Plugin > Issue Type: Task >Affects Versions: 2.0-beta-6 >Reporter: Brett Porter > Fix For: 2.0-beta-6 > > > per discussion on dev list - we need to do this before the next site plugin > release. > There are probably a couple of implementation options: > - only processing files that have .vm appended to the filename > - adding configuration to the site plugin that is passed through to doxia as > includes/excludes > - ...? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MWAR-96) WebResource not filtered with system properties.
WebResource not filtered with system properties.
Key: MWAR-96
URL: http://jira.codehaus.org/browse/MWAR-96
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.0.2
Environment: java 5.0, Windows XP
Reporter: KlaasJan Elzinga
When filtering a resource:
${basedir}/src/main/resources/
true
index.jsp
The index.jsp contains:
java version${java.version}
Project${pom.name}
Version${pom.version}
After mvn clean install the filtered index.jsp looks like:
java version1.0.0.SNAPSHOT
ProjectFrieslandBank TMS TNS WebApp
Version1.0.0.SNAPSHOT
The value java.version is filtered to the version of the pom and not the
system property. The same goes for os.name which is translated to pom.name.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
