[jira] Created: (NMAVEN-114) Jetty is pulled out by plugins, even if it isn't needed
Jetty is pulled out by plugins, even if it isn't needed --- Key: NMAVEN-114 URL: http://jira.codehaus.org/browse/NMAVEN-114 Project: NMaven Issue Type: Improvement Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez Priority: Minor Jetty isn't necessary in most of the plugins, but it is still downloaded as a dependency of the plugins. -- 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: (NMAVEN-114) Jetty is pulled out by plugins, even if it isn't needed
[ http://jira.codehaus.org/browse/NMAVEN-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated NMAVEN-114: --- Attachment: NMAVEN-114.patch The patch removes the jetty dependency from the plugins as it isn't necessary at all. Diff'd against the STABLE-2007-12-16 tag. > Jetty is pulled out by plugins, even if it isn't needed > --- > > Key: NMAVEN-114 > URL: http://jira.codehaus.org/browse/NMAVEN-114 > Project: NMaven > Issue Type: Improvement >Affects Versions: 0.14 (Unreleased) > Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 >Reporter: Napoleon Esmundo C. Ramirez >Priority: Minor > Attachments: NMAVEN-114.patch > > > Jetty isn't necessary in most of the plugins, but it is still downloaded as a > dependency of the plugins. -- 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: (NMAVEN-115) Using the systemPath element in a dependecy doesn't work
Using the systemPath element in a dependecy doesn't work Key: NMAVEN-115 URL: http://jira.codehaus.org/browse/NMAVEN-115 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez Using a system scope w/ a systemPath element in a dependency won't work, NMaven always points to local repo. -- 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: (NMAVEN-115) Using the systemPath element in a dependecy doesn't work
[ http://jira.codehaus.org/browse/NMAVEN-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated NMAVEN-115: --- Attachment: NMAVEN-115.patch Patch implements the systemPath element in the dependency element. > Using the systemPath element in a dependecy doesn't work > > > Key: NMAVEN-115 > URL: http://jira.codehaus.org/browse/NMAVEN-115 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 >Reporter: Napoleon Esmundo C. Ramirez > Attachments: NMAVEN-115.patch > > > Using a system scope w/ a systemPath element in a dependency won't work, > NMaven always points to local repo. -- 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: (NMAVEN-115) Using the systemPath element in a dependecy doesn't work
[ http://jira.codehaus.org/browse/NMAVEN-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated NMAVEN-115: --- Attachment: NMAVEN-115-vs-support.patch The patch implements the systemPath element for the VS support. > Using the systemPath element in a dependecy doesn't work > > > Key: NMAVEN-115 > URL: http://jira.codehaus.org/browse/NMAVEN-115 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 >Reporter: Napoleon Esmundo C. Ramirez > Attachments: NMAVEN-115-vs-support.patch, NMAVEN-115.patch > > > Using a system scope w/ a systemPath element in a dependency won't work, > NMaven always points to local repo. -- 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: (NMAVEN-116) Add feature for Solution.JavaBinding plugin to pickup resource file in the source directory
Add feature for Solution.JavaBinding plugin to pickup resource file in the source directory --- Key: NMAVEN-116 URL: http://jira.codehaus.org/browse/NMAVEN-116 Project: NMaven Issue Type: New Feature Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez If *.resx file is found in the source directory of nmaven project, Solution.JavaBinding will generate the reference entry in *.csproj/.*vbproj 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] Updated: (NMAVEN-117) The project generated by the NMaven netexecutable archetype defaults to version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT
[ http://jira.codehaus.org/browse/NMAVEN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated NMAVEN-117: --- Attachment: NMAVEN-117.patch > The project generated by the NMaven netexecutable archetype defaults to > version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT > --- > > Key: NMAVEN-117 > URL: http://jira.codehaus.org/browse/NMAVEN-117 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 >Reporter: Napoleon Esmundo C. Ramirez > Attachments: NMAVEN-117.patch > > > The project generated by the NMaven netexecutable archetype defaults to > version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT. It should probably > be filtered out. -- 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: (NMAVEN-117) The project generated by the NMaven netexecutable archetype defaults to version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT
The project generated by the NMaven netexecutable archetype defaults to version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT --- Key: NMAVEN-117 URL: http://jira.codehaus.org/browse/NMAVEN-117 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez The project generated by the NMaven netexecutable archetype defaults to version 0.14-maestro-1.5 when it should be 1.0-SNAPSHOT. It should probably be filtered out. -- 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: (NMAVEN-116) Add feature for Solution.JavaBinding plugin to pickup resource file in the source directory
[ http://jira.codehaus.org/browse/NMAVEN-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated NMAVEN-116: --- Attachment: NMAVEN-116.patch > Add feature for Solution.JavaBinding plugin to pickup resource file in the > source directory > --- > > Key: NMAVEN-116 > URL: http://jira.codehaus.org/browse/NMAVEN-116 > Project: NMaven > Issue Type: New Feature >Affects Versions: 0.14 (Unreleased) > Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 >Reporter: Napoleon Esmundo C. Ramirez > Attachments: NMAVEN-116.patch > > > If *.resx file is found in the source directory of nmaven project, > Solution.JavaBinding will generate the reference entry in *.csproj/.*vbproj > 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] Updated: (NMAVEN-118) Errors from .NET plugins are not recognized
[ http://jira.codehaus.org/browse/NMAVEN-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Napoleon Esmundo C. Ramirez updated NMAVEN-118: --- Attachment: NMAVEN-118.patch Patch used p.WaitForExit() to allow process to finish. > Errors from .NET plugins are not recognized > --- > > Key: NMAVEN-118 > URL: http://jira.codehaus.org/browse/NMAVEN-118 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 >Reporter: Napoleon Esmundo C. Ramirez > Attachments: NMAVEN-118.patch > > > Errors are not detected because the process isn't allowed to finish. -- 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: (NMAVEN-118) Errors from .NET plugins are not recognized
Errors from .NET plugins are not recognized --- Key: NMAVEN-118 URL: http://jira.codehaus.org/browse/NMAVEN-118 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 Reporter: Napoleon Esmundo C. Ramirez Errors are not detected because the process isn't allowed to finish. -- 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: (MAVENUPLOAD-2004) Hessian 3.1.5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] evgeny updated MAVENUPLOAD-2004: Attachment: hessian-3.1.5-bundle.jar > Hessian 3.1.5 > - > > Key: MAVENUPLOAD-2004 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2004 > Project: maven-upload-requests > Issue Type: Task >Reporter: evgeny > Attachments: hessian-3.1.5-bundle.jar, hessian-3.1.5-bundle.jar > > > The Hessian binary web service protocol makes web services usable without > requiring a large framework, and without learning yet another alphabet soup > of protocols. Because it is a binary protocol, it is well-suited to sending > binary data without any need to extend the protocol with attachments. -- 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-2004) Hessian 3.1.5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12#action_12 ] evgeny commented on MAVENUPLOAD-2004: - Sorry, I took example from request on hessian-3.0.8. Hope its bundle is valid. > Hessian 3.1.5 > - > > Key: MAVENUPLOAD-2004 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2004 > Project: maven-upload-requests > Issue Type: Task >Reporter: evgeny > Attachments: hessian-3.1.5-bundle.jar, hessian-3.1.5-bundle.jar > > > The Hessian binary web service protocol makes web services usable without > requiring a large framework, and without learning yet another alphabet soup > of protocols. Because it is a binary protocol, it is well-suited to sending > binary data without any need to extend the protocol with attachments. -- 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] Issue Comment Edited: (MAVENUPLOAD-2004) Hessian 3.1.5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12#action_12 ] evgeny edited comment on MAVENUPLOAD-2004 at 4/7/08 6:17 AM: - Sorry, I took example from request on hessian-3.0.8. Hope new bundle is valid. was (Author: evgeny): Sorry, I took example from request on hessian-3.0.8. Hope its bundle is valid. > Hessian 3.1.5 > - > > Key: MAVENUPLOAD-2004 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2004 > Project: maven-upload-requests > Issue Type: Task >Reporter: evgeny > Attachments: hessian-3.1.5-bundle.jar, hessian-3.1.5-bundle.jar > > > The Hessian binary web service protocol makes web services usable without > requiring a large framework, and without learning yet another alphabet soup > of protocols. Because it is a binary protocol, it is well-suited to sending > binary data without any need to extend the protocol with attachments. -- 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: (MRM-243) 507 Insufficient Storage when deploying artifact with webdav
[ http://jira.codehaus.org/browse/MRM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129986#action_129986 ] Brett Porter commented on MRM-243: -- please check the 1.0.2 candidate build (see developers list archives for recent vote) - but otherwise the issue should be cloned > 507 Insufficient Storage when deploying artifact with webdav > > > Key: MRM-243 > URL: http://jira.codehaus.org/browse/MRM-243 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-alpha-1, 1.0-alpha-2, 1.0-beta-1, 1.0-beta-2 > Environment: mvn 2.0.4, Windows Server 2003, Tomcat 5.5.17, Sun JDK > 1.5.0_08, archiva HEAD >Reporter: Magne Rasmussen >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > > Sometimes when deploying with dav I get a "507 Insufficient Storage" error. > The artifact (.../group/artifact/version/artifact-version.jar) gets deployed > (with checksums). > The metadata (.../group/artifact/version/maven-metatdata.xml) gets deployed > (with checksums). > It seems to happen when maven tries to upload the updated parent metadata > (.../group/artifact/maven-metadata.xml). The checksums for this metadata > deploys OK. -- 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-233) Create an Eclipse plugin to edit Doxia files
[ http://jira.codehaus.org/browse/DOXIA-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated DOXIA-233: -- Attachment: screenshot-2.jpg > Create an Eclipse plugin to edit Doxia files > > > Key: DOXIA-233 > URL: http://jira.codehaus.org/browse/DOXIA-233 > Project: Maven Doxia > Issue Type: New Feature > Components: Doxia Tools >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Attachments: screenshot 1.jpg, screenshot-1.jpg, screenshot-2.jpg > > > Editor plugin to play with Doxia formats -- 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-233) Create an Eclipse plugin to edit Doxia files
[ http://jira.codehaus.org/browse/DOXIA-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated DOXIA-233: -- Attachment: screenshot 1.jpg > Create an Eclipse plugin to edit Doxia files > > > Key: DOXIA-233 > URL: http://jira.codehaus.org/browse/DOXIA-233 > Project: Maven Doxia > Issue Type: New Feature > Components: Doxia Tools >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Attachments: screenshot 1.jpg, screenshot-1.jpg, screenshot-2.jpg > > > Editor plugin to play with Doxia formats -- 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-233) Create an Eclipse plugin to edit Doxia files
[ http://jira.codehaus.org/browse/DOXIA-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated DOXIA-233: -- Attachment: screenshot-1.jpg > Create an Eclipse plugin to edit Doxia files > > > Key: DOXIA-233 > URL: http://jira.codehaus.org/browse/DOXIA-233 > Project: Maven Doxia > Issue Type: New Feature > Components: Doxia Tools >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Attachments: screenshot 1.jpg, screenshot-1.jpg, screenshot-2.jpg > > > Editor plugin to play with Doxia formats -- 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: (DOXIA-233) Create an Eclipse plugin to edit Doxia files
[ http://jira.codehaus.org/browse/DOXIA-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130006#action_130006 ] Vincent Siveton commented on DOXIA-233: --- First done in r645518 Please read the README first https://svn.apache.org/repos/asf/maven/doxia/doxia-tools/trunk/doxia-ide/eclipse/README.TXT > Create an Eclipse plugin to edit Doxia files > > > Key: DOXIA-233 > URL: http://jira.codehaus.org/browse/DOXIA-233 > Project: Maven Doxia > Issue Type: New Feature > Components: Doxia Tools >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Attachments: screenshot 1.jpg, screenshot-1.jpg, screenshot-2.jpg > > > Editor plugin to play with Doxia formats -- 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: (SUREFIRE-481) java.lang.NoSuchMethodError when forking on a 1.3 JDK
java.lang.NoSuchMethodError when forking on a 1.3 JDK - Key: SUREFIRE-481 URL: http://jira.codehaus.org/browse/SUREFIRE-481 Project: Maven Surefire Issue Type: Bug Components: Junit 4.x support Affects Versions: 2.4.2, 2.4.1, 2.4 Environment: Maven version: 2.0.7, 2.0.8, 2.0.9-RC8 or Java version: 1.5.0_12 Reporter: David J. M. Karlsen [INFO] [surefire:test] [DEBUG] dummy:dummy:jar:1.0 (selected for null) [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.4.2:runtime (selected for runtime) [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4.2:runtime (selected for runtime) [DEBUG] Adding to surefire booter test classpath: /heim/ab62939/.m2/repository/org/apache/maven/surefire/surefire-booter/2.4.2/surefire-booter-2.4.2.jar [DEBUG] Adding to surefire booter test classpath: /heim/ab62939/.m2/repository/org/apache/maven/surefire/surefire-api/2.4.2/surefire-api-2.4.2.jar [DEBUG] dummy:dummy:jar:1.0 (selected for null) [DEBUG] Retrieving parent-POM: org.apache.maven.surefire:surefire-providers::2.4.2 for project: null:surefire-junit:jar:null from the repository. [DEBUG] Adding managed dependencies for unknown:surefire-junit [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4.2 [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.4.2 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.9 [DEBUG] org.apache.maven.surefire:surefire-junit:jar:2.4.2:test (selected for test) [DEBUG] junit:junit:jar:3.8.1:test (selected for test) [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4.2:test (selected for test) [DEBUG] Adding to surefire test classpath: /heim/ab62939/.m2/repository/org/apache/maven/surefire/surefire-junit/2.4.2/surefire-junit-2.4.2.jar [DEBUG] Adding to surefire test classpath: /heim/ab62939/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar [DEBUG] Adding to surefire test classpath: /heim/ab62939/.m2/repository/org/apache/maven/surefire/surefire-api/2.4.2/surefire-api-2.4.2.jar [DEBUG] Test Classpath : [snip...] [INFO] Surefire report directory: /tmp/dnbnorapi-trunk/dnbnorapi-server/target/surefire-reports Forking command line: /bin/sh -c "cd /tmp/dnbnorapi-trunk/dnbnorapi-server && /dnb/prosess/WebSphere5/AppServer/java/jre/bin/java -Xmx128M -jar /var/tmp/surefirebooter29275.jar /var/tmp/surefire29273tmp /var/tmp/surefire29274tmp" java.lang.NoSuchMethodError at org.apache.maven.surefire.util.UrlUtils.getURL(UrlUtils.java:39) at org.apache.maven.surefire.booter.SurefireBooter.createClassLoader(SurefireBooter.java:730) at org.apache.maven.surefire.booter.SurefireBooter.createClassLoader(SurefireBooter.java:715) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:277) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993) [ERROR] There are test failures. -- 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-481) java.lang.NoSuchMethodError when forking on a 1.3 JDK
[ http://jira.codehaus.org/browse/SUREFIRE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130007#action_130007 ] David J. M. Karlsen commented on SUREFIRE-481: -- This might have been fixed in r635738? Could somebody push out a new snapshot so that it can be verified? TIA, David > java.lang.NoSuchMethodError when forking on a 1.3 JDK > - > > Key: SUREFIRE-481 > URL: http://jira.codehaus.org/browse/SUREFIRE-481 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 2.4, 2.4.1, 2.4.2 > Environment: Maven version: 2.0.7, 2.0.8, 2.0.9-RC8 or > Java version: 1.5.0_12 >Reporter: David J. M. Karlsen > > [INFO] [surefire:test] > [DEBUG] dummy:dummy:jar:1.0 (selected for null) > [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.4.2:runtime > (selected for runtime) > [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4.2:runtime > (selected for runtime) > [DEBUG] Adding to surefire booter test classpath: > /heim/ab62939/.m2/repository/org/apache/maven/surefire/surefire-booter/2.4.2/surefire-booter-2.4.2.jar > [DEBUG] Adding to surefire booter test classpath: > /heim/ab62939/.m2/repository/org/apache/maven/surefire/surefire-api/2.4.2/surefire-api-2.4.2.jar > [DEBUG] dummy:dummy:jar:1.0 (selected for null) > [DEBUG] Retrieving parent-POM: > org.apache.maven.surefire:surefire-providers::2.4.2 for project: > null:surefire-junit:jar:null from the repository. > [DEBUG] Adding managed dependencies for unknown:surefire-junit > [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4.2 > [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.4.2 > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.9 > [DEBUG] org.apache.maven.surefire:surefire-junit:jar:2.4.2:test (selected > for test) > [DEBUG] junit:junit:jar:3.8.1:test (selected for test) > [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4.2:test (selected > for test) > [DEBUG] Adding to surefire test classpath: > /heim/ab62939/.m2/repository/org/apache/maven/surefire/surefire-junit/2.4.2/surefire-junit-2.4.2.jar > [DEBUG] Adding to surefire test classpath: > /heim/ab62939/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar > [DEBUG] Adding to surefire test classpath: > /heim/ab62939/.m2/repository/org/apache/maven/surefire/surefire-api/2.4.2/surefire-api-2.4.2.jar > [DEBUG] Test Classpath : > [snip...] > [INFO] Surefire report directory: > /tmp/dnbnorapi-trunk/dnbnorapi-server/target/surefire-reports > Forking command line: /bin/sh -c "cd /tmp/dnbnorapi-trunk/dnbnorapi-server && > /dnb/prosess/WebSphere5/AppServer/java/jre/bin/java -Xmx128M -jar > /var/tmp/surefirebooter29275.jar /var/tmp/surefire29273tmp > /var/tmp/surefire29274tmp" > java.lang.NoSuchMethodError > at org.apache.maven.surefire.util.UrlUtils.getURL(UrlUtils.java:39) > at > org.apache.maven.surefire.booter.SurefireBooter.createClassLoader(SurefireBooter.java:730) > at > org.apache.maven.surefire.booter.SurefireBooter.createClassLoader(SurefireBooter.java:715) > at > org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:277) > at > org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993) > [ERROR] There are test failures. -- 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-3505) check scm files into local vss server
check scm files into local vss server - Key: MNG-3505 URL: http://jira.codehaus.org/browse/MNG-3505 Project: Maven 2 Issue Type: Task Environment: maven2,continuum1.1,subversion Reporter: tianxiang I use subversion (on a remote server) in normal development , and wanna after every auto building (by continuum) maven coule check the new source also in my local vss server for backing up. Does maven have any funtions to do with this operation ? Thanks! Best Wishes ! -- 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-461) -Xbootclasspath specified in not passed to forked JVM
[ http://jira.codehaus.org/browse/SUREFIRE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130018#action_130018 ] Jason Voegele commented on SUREFIRE-461: Can you confirm that this issue exists? I've included a sample project that demonstrates the issue. > -Xbootclasspath specified in not passed to forked JVM > --- > > Key: SUREFIRE-461 > URL: http://jira.codehaus.org/browse/SUREFIRE-461 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.4, 2.4.1, 2.4.2 >Reporter: Jason Voegele > Attachments: surefire-argline-bug.tar.gz > > > The 2.4.x versions of maven-surefire-plugin do not propagate the > bootclasspath to the forked JVM that executes the tests. > I have attached a sample project that demonstrates this problem. The sample > application has a test case that verifies that the -Xbootclasspath parameter > given in the of the POM is properly passed to the JVM running the > tests, but the test fails when using 2.4.x versions. > If you modify the POM to use 2.3 version instead of 2.4.2, the tests pass. -- 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: (MECLIPSE-424) New submodules do not show up as seperate projects
New submodules do not show up as seperate projects -- Key: MECLIPSE-424 URL: http://jira.codehaus.org/browse/MECLIPSE-424 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Multi-projects Affects Versions: 2.5.1 Environment: win xp, eclipse 3.3 Reporter: Nayan Hajratwala Scenario: 1) User A checks out a maven project from SVN using "Checkout as Maven Project". All modules are now listed as seperate projects in Eclipse 2) User B creates a new module in the project, and checks it into SVN 3) User A updates project 4) New module does not show up as a seperate project. 5) User A cries. -- 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-2009) Please sync net.sourceforge.htmlunit
Please sync net.sourceforge.htmlunit Key: MAVENUPLOAD-2009 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2009 Project: maven-upload-requests Issue Type: Wish Reporter: Marc Guillemot "net.sourceforge.htmlunit","[EMAIL PROTECTED]:/home/groups/h/ht/htmlunit/htdocs/m2-repo","rsync_ssh","Marc Guillemot","[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] Created: (MSITE-314) use ${project.build.sourceEncoding} as default value for "inputEncoding" parameter
use ${project.build.sourceEncoding} as default value for "inputEncoding"
parameter
--
Key: MSITE-314
URL: http://jira.codehaus.org/browse/MSITE-314
Project: Maven 2.x Site Plugin
Issue Type: Improvement
Components: encoding
Affects Versions: 2.0-beta-6
Reporter: Herve Boutemy
see
http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding
--
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: (MANTRUN-85) Plublic documentation is out of sync with released plugin
Plublic documentation is out of sync with released plugin - Key: MANTRUN-85 URL: http://jira.codehaus.org/browse/MANTRUN-85 Project: Maven 2.x Antrun Plugin Issue Type: Bug Affects Versions: 1.1 Reporter: Michael Buckley The public docs (e.g. http://maven.apache.org/plugins/maven-antrun-plugin/examples/tasksAttributes.html ) describe features that are not implemented in a released version (i.e. 1.1). Users get confused when you document features that don't exist. I wasted time, and had to discover that this problem has existed for months. Fix: Re-publish the site based on 1.1 so the docs match the release. Or release 1.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] Commented: (MANTRUN-41) Easy access to dependency jars
[
http://jira.codehaus.org/browse/MANTRUN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130061#action_130061
]
Michael Buckley commented on MANTRUN-41:
Please don't hold up 1.2 for this.
> Easy access to dependency jars
> --
>
> Key: MANTRUN-41
> URL: http://jira.codehaus.org/browse/MANTRUN-41
> Project: Maven 2.x Antrun Plugin
> Issue Type: New Feature
>Affects Versions: 1.1
>Reporter: Patrick Lightbody
>Assignee: Kenney Westerhof
> Fix For: 1.2
>
> Attachments: MANTRUN-41-maven-antrun-plugin.patch
>
>
> It would be nice to have an easy access to the dependency jars located in
> ~/.m2. A couple ideas tossed around in #maven were:
> ${dep.XXX.YYY.jar}, where XXX and YYY are the groupId and artifactId
> OR
> a new Ant task:
>
> Where you could then reference ${jarpath}
--
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: (MANTRUN-83) Please roll a release of the antrun plugin
[ http://jira.codehaus.org/browse/MANTRUN-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130062#action_130062 ] Michael Buckley commented on MANTRUN-83: It has been almost 2 years since a release. Please release 1.2 > Please roll a release of the antrun plugin > -- > > Key: MANTRUN-83 > URL: http://jira.codehaus.org/browse/MANTRUN-83 > Project: Maven 2.x Antrun Plugin > Issue Type: Task >Affects Versions: 1.2 > Environment: N/A >Reporter: Allen Servedio >Priority: Minor > > It looks like it has been a long time (10 Oct 2007 per > http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-antrun-plugin/1.2-SNAPSHOT/) > that a snapshot has been created for this project. However, there do seem to > be several things that were fixed since the last 1.1 release back in 2006. > Is there anyway that a release can be generated from the 10 Oct 2007 snapshot > to at least get the fixes out into the community? > I see one blocker open (http://jira.codehaus.org/browse/MANTRUN-58) which, if > 1.1 has the same issue (???) should not block a release. > In the meantime, we have, of course released your last snapshot into our > internal repository so that we are only using released plugins. -- 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-3507) ANSI Color logging for improved output visibility.
ANSI Color logging for improved output visibility. -- Key: MNG-3507 URL: http://jira.codehaus.org/browse/MNG-3507 Project: Maven 2 Issue Type: Improvement Reporter: Rahul Thakur Is it possible for Maven to use ANSI color logging? IMO it would make Maven logs much easier to read and increase the visibility of items that the user want to see at any given point in time. I think Andrew Williams did some work under Plexus sandbox to enable color logging. There also a color logger available in Ant. http://ant.apache.org/manual/listeners.html#AnsiColorLogger -- 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-424) New submodules do not show up as seperate projects
[ http://jira.codehaus.org/browse/MECLIPSE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130064#action_130064 ] Arnaud Heritier commented on MECLIPSE-424: -- With this command line plugin, each time you receive an updated pom from your SVN you have to update eclipse settings (mvn eclipse:eclipse) and t reimport your projects if a new new modules was added. Are you sure that user A did it ? If you wantsomething automatic you to look at eclipse plugins for maven like "Maven Eclipse Integration" or "Q4E". (but you'll have less feature for JEE developments if you need them). > New submodules do not show up as seperate projects > -- > > Key: MECLIPSE-424 > URL: http://jira.codehaus.org/browse/MECLIPSE-424 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Multi-projects >Affects Versions: 2.5.1 > Environment: win xp, eclipse 3.3 >Reporter: Nayan Hajratwala > > Scenario: > 1) User A checks out a maven project from SVN using "Checkout as Maven > Project". All modules are now listed as seperate projects in Eclipse > 2) User B creates a new module in the project, and checks it into SVN > 3) User A updates project > 4) New module does not show up as a seperate project. > 5) User A cries. -- 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: (NMAVEN-110) Ability to generate .vbproj files
[ http://jira.codehaus.org/browse/NMAVEN-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Catherine Tan updated NMAVEN-110: --- Attachment: NMAVEN-110.patch attached patch that fixes this issue > Ability to generate .vbproj files > - > > Key: NMAVEN-110 > URL: http://jira.codehaus.org/browse/NMAVEN-110 > Project: NMaven > Issue Type: New Feature >Reporter: Maria Catherine Tan > Attachments: NMAVEN-110.patch > > > this applies to > https://svn.apache.org/repos/asf/incubator/nmaven/tags/STABLE-2007-12-16/ -- 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: (NMAVEN-112) Unable to generate solution file from test project
[
http://jira.codehaus.org/browse/NMAVEN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Catherine Tan updated NMAVEN-112:
---
Attachment: NMAVEN-112.patch
submitted patch that fixes this issue
> Unable to generate solution file from test project
> --
>
> Key: NMAVEN-112
> URL: http://jira.codehaus.org/browse/NMAVEN-112
> Project: NMaven
> Issue Type: Bug
>Reporter: Maria Catherine Tan
>Priority: Critical
> Attachments: NMAVEN-112.patch
>
>
> To reproduce:
> mvn archetype:create -DgroupId=NMaven -DartifactId=NMaven.Test
> -DarchetypeArtifactId=maven-archetype-dotnet-simple
> -DarchetypeGroupId=org.apache.maven.dotnet
> -DarchetypeVersion=0.14-maestro-1.5-M3
> cd NMaven.Test
> mvn install
> mvn clean
> mvn org.apache.maven.dotnet.plugins:maven-vsinstaller-plugin:install
> mvn NMaven.Plugins:NMaven.Plugin.Solution.JavaBinding:Solution
> This results in some build output, then an error/debug dialog:
> NMaven.Plugin.Loader has encountered a problem and needs to close
> Console output:
> {code}
> [INFO] [NMaven.Plugin.Solution.JavaBinding:Solution]
> NMAVEN: Start Process = 12/10/2007 2:35:19 PM
> "parameterFile=C:\DOCUME~1\wsmoak\LOCALS~1\Temp\Plugin34917.xml"
> "assemblyFile=C
> :\Documents and
> Settings\wsmoak\.m2\pab\gac_msil\NMaven.Plugin.Solution\0.14-mae
> stro-1.5-M3__NMaven.Plugins\NMaven.Plugin.Solution.dll"
> "mojoName=NMaven.Plugin.
> Solution.SolutionMojo" "startProcessAssembly=C:\Documents and
> Settings\wsmoak\.m
> 2\pab\gac_msil\NMaven.Plugin.Loader\0.14-maestro-1.5-M3__NMaven.Plugin\NMaven.Pl
> ugin.Loader.exe"
> NMAVEN: End Process = 12/10/2007 2:35:19 PM
> Creating Plugin Domain Manager
> ParamFile = C:\DOCUME~1\wsmoak\LOCALS~1\Temp\Plugin34917.xml, AssemblyFile =
> C:\
> Documents and
> Settings\wsmoak\.m2\pab\gac_msil\NMaven.Plugin.Solution\0.14-maest
> ro-1.5-M3__NMaven.Plugins\NMaven.Plugin.Solution.dll, MojoName =
> NMaven.Plugin.S
> olution.SolutionMojo
> Loading Plugin: C:\Documents and
> Settings\wsmoak\.m2\pab\gac_msil\NMaven.Plugin.
> Solution\0.14-maestro-1.5-M3__NMaven.Plugins
> Creating Plugin Domain Manager
> System.String:NMaven.Model.Pom.Model
> System.String:System.String
> NMaven.Model.Pom.Model:NMaven.Model.Pom.Model
> System.String:NMaven.Model.Pom.Model
> System.String:System.String
> [ERROR]
> [ERROR] Unhandled Exception: System.IO.FileNotFoundException: Could not load
> fil
> e or assembly 'NMaven.Solution, Version=0.14.0.0, Culture=neutral,
> PublicKeyToke
> n=null' or one of its dependencies. The system cannot find the file specified.
> [ERROR] File name: 'NMaven.Solution, Version=0.14.0.0, Culture=neutral,
> PublicKe
> yToken=null'
> [ERROR]at NMaven.Plugin.Solution.SolutionMojo.Execute()
> [ERROR]at NMaven.Plugin.AbstractMojo.Execute()
> [ERROR]at NMaven.Plugin.Loader.PluginLoader.Main(String[] args)
> [ERROR]
> [ERROR] WRN: Assembly binding logging is turned OFF.
> [ERROR] To enable assembly bind failure logging, set the registry value
> [HKLM\So
> ftware\Microsoft\Fusion!EnableLog] (DWORD) to 1.
> [ERROR] Note: There is some performance penalty associated with assembly bind
> failure logging.
> [ERROR] To turn this feature off, remove the registry value
> [HKLM\Software\Microsoft\Fusion!EnableLog].
> [ERROR]
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] NMAVEN-xxx-000
> Embedded error: NMAVEN-063-000: Execution Path = C:\Documents and
> Settings\wsmoa
> k\.m2\pab\gac_msil\NMaven.Plugin.Runner\0.14-maestro-1.5-M3__NMaven.Plugin,
> Comm
> and = [parameterFile=C:\DOCUME~1\wsmoak\LOCALS~1\Temp\Plugin34917.xml,
> assemblyF
> ile=C:\Documents and
> Settings\wsmoak\.m2\pab\gac_msil\NMaven.Plugin.Solution\0.1
> 4-maestro-1.5-M3__NMaven.Plugins\NMaven.Plugin.Solution.dll,
> mojoName=NMaven.Plu
> gin.Solution.SolutionMojo, startProcessAssembly=C:\Documents and
> Settings\wsmoak
> \.m2\pab\gac_msil\NMaven.Plugin.Loader\0.14-maestro-1.5-M3__NMaven.Plugin\NMaven
> .Plugin.Loader.exe]
> NMAVEN-040-001: Could not execute: Command = NMaven.Plugin.Runner.exe
> parameterF
> ile=C:\DOCUME~1\wsmoak\LOCALS~1\Temp\Plugin34917.xml
> "assemblyFile=C:\Documents
> and
> Settings\wsmoak\.m2\pab\gac_msil\NMaven.Plugin.Solution\0.14-maestro-1.5-M3_
> _NMaven.Plugins\NMaven.Plugin.Solution.dll"
> mojoName=NMaven.Plugin.Solution.Solu
> tionMojo "startProcessAssembly=C:\Documents and
> Settings\wsmoak\.m2\pab\gac_msil
> \NMaven.Plugin.Loader\0.14-maestro-1.5-M3__NMaven.Plugin\NMaven.Plugin.Loader.ex
> e", Result = 0
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> -
[jira] Updated: (NMAVEN-111) the visual studio installer plugin doesn't work on an empty local repository
[ http://jira.codehaus.org/browse/NMAVEN-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Catherine Tan updated NMAVEN-111: --- Attachment: NMAVEN-111.patch attached patch that fixes this issue > the visual studio installer plugin doesn't work on an empty local repository > > > Key: NMAVEN-111 > URL: http://jira.codehaus.org/browse/NMAVEN-111 > Project: NMaven > Issue Type: Bug >Reporter: Maria Catherine Tan > Attachments: NMAVEN-111.patch > > > This applies for > https://svn.apache.org/repos/asf/incubator/nmaven/tags/STABLE-2007-12-16/ > You currently have to run both "mvn install" on an NMaven project and to > generate the solution file to get the following artifacts in your local > repository for the vsinstaller plugin to succeed: > * NMaven.Plugins:NMaven.Plugin.Settings.JavaBinding > * NMaven.Plugins:NMaven.Plugin.Solution > In addition, you have to manually install the dotnet-embedder WAR file using > the following: > mvn install:install-file -DgroupId=org.apache.maven.dotnet > -DartifactId=dotnet-service-embedder -Dversion=0.14-maestro-1.5-M3 > -Dpackaging=war > -Dfile=%REPOSITORY%\org\apache\maven\dotnet\dotnet-service-embedder\0.14-maestro-1.5-M3\dotnet-service-embedder-0.14-maestro-1.5-M3.war > > -DpomFile=%REPOSITORY%\org\apache\maven\dotnet\dotnet-service-embedder\0.14-maestro-1.5-M3\dotnet-service-embedder-0.14-maestro-1.5-M3.pom > (Assumes %REPOSITORY% is the location of the MPS releases repository - > obviously not always available on the client... so maybe a POM is better). -- 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: (NMAVEN-110) Ability to generate .vbproj files
[ http://jira.codehaus.org/browse/NMAVEN-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130071#action_130071 ] Maria Catherine Tan commented on NMAVEN-110: The first patch attached NMAVEN-110.patch contains a bug. I will include the bug fix on the second patch. > Ability to generate .vbproj files > - > > Key: NMAVEN-110 > URL: http://jira.codehaus.org/browse/NMAVEN-110 > Project: NMaven > Issue Type: New Feature >Reporter: Maria Catherine Tan > Attachments: NMAVEN-110.patch > > > this applies to > https://svn.apache.org/repos/asf/incubator/nmaven/tags/STABLE-2007-12-16/ -- 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: (NMAVEN-110) Ability to generate .vbproj files
[ http://jira.codehaus.org/browse/NMAVEN-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Catherine Tan updated NMAVEN-110: --- Attachment: NMAVEN-110-COMPLETE.patch Submitted NMAVEN-110-COMPLETE.patch which is composed of the fix for this issue plus the bug fix for NMAVEN-110.patch (Please use this patch instead of NMAVEN-110.patch) > Ability to generate .vbproj files > - > > Key: NMAVEN-110 > URL: http://jira.codehaus.org/browse/NMAVEN-110 > Project: NMaven > Issue Type: New Feature >Reporter: Maria Catherine Tan > Attachments: NMAVEN-110-COMPLETE.patch, NMAVEN-110.patch > > > this applies to > https://svn.apache.org/repos/asf/incubator/nmaven/tags/STABLE-2007-12-16/ -- 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: (MPH-38) mvn help:active-profiles won't show the active profiles in settings.xml
mvn help:active-profiles won't show the active profiles in settings.xml Key: MPH-38 URL: http://jira.codehaus.org/browse/MPH-38 Project: Maven 2.x Help Plugin Issue Type: Bug Affects Versions: 2.1 Environment: linux (never tried it in windows), sun's jdk 1.5.0_12 Reporter: Allan G. Ramirez settings.xml has this appserverConfig pom.xml of MavenProject2 project has this appserverConfig-dev-2 true env dev-2 /path/to/another/dev/appserver2 I tried mvn help:active-profiles using the maven 2.1-SNAPSHOT I only got - appserverConfig-dev-2 (source: pom) appserverConfig defined in settings.xml is not shown -- 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: (MNGSITE-47) Comparison matrix for artifact managers
Comparison matrix for artifact managers --- Key: MNGSITE-47 URL: http://jira.codehaus.org/browse/MNGSITE-47 Project: Maven 2 Project Web Site Issue Type: Sub-task Reporter: Erik Drolshammer Priority: Minor It would be really nice to have a matrix for comparing the features of the different available products. Something like http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix. ColumnHeaders: Proxy - yes/no Internal repository - yes/no Virtual repository - yes/no (Virtual repo = a logical view of multiple repos without duplicating artifacts) Authentication support: (ldap, custom, etc.) Persistence: (filesystem, javaspace with jfrog, database) GUI: (wicket, ExtJS,) Configuration: from the gui and/or with a file I consider Artifactory, Nexus and Archiva the hottest candidates. So helping users comparing those is the main design goal of the matrix. It should however, be expanded to include the rest of the alternatives later. If there is interest for something like this, I can submit a path to the repo page with what I know of these artifact managers. -- 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
