[jira] Commented: (MASSEMBLY-210) repository does not include the parent pom
[
http://jira.codehaus.org/browse/MASSEMBLY-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99163
]
Stephane Nicoll commented on MASSEMBLY-210:
---
Still the same issue, even if I build the plugin myself from trunk. I'm using
the latest 2.0.7 SNAP but I have the same with 2.0.6
Are you using 2.1 or something?
> repository does not include the parent pom
> --
>
> Key: MASSEMBLY-210
> URL: http://jira.codehaus.org/browse/MASSEMBLY-210
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-1
>Reporter: Stephane Nicoll
>Assignee: John Casey
> Fix For: 2.2-beta-2
>
>
> I am running the assembly on a project with a parent pom. encoding="ISO-8859-15"?> dist
> zip
> true
> foo-${version}
> . foo-base
> true
> /target/
> repository
> test
> The parent pom is not included 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] Created: (MNG-3048) Xpp3Dom gets in the way of org.omg.CORBA.INITIALIZE
Xpp3Dom gets in the way of org.omg.CORBA.INITIALIZE --- Key: MNG-3048 URL: http://jira.codehaus.org/browse/MNG-3048 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0.6 Reporter: Emilian Bold I have a unit test which creates an InitialContext and connects to a Glassfish application. I'm using sunfire 2.1.3 (in order to -disableassertions). While creating the InitialContext, I get exception at the end of the post. Basically I have appserver-rt in the dependency list (in my local repository). This jar contains the com/sun/corba/ee/impl/orb/ORBImpl.class. maven-surefire-plugin is also configured this way in the build: 2.1.3 pertest -da true Note my test with childDelegation which seems to do nothing in particular. org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation com.sun.corba.ee.impl.orb.ORBImpl vmcid: 0x0 minor code: 0 completed: No at org.omg.CORBA.ORB.create_impl(ORB.java:297) at org.omg.CORBA.ORB.init(ORB.java:336) at com.sun.enterprise.util.ORBManager.initORB(ORBManager.java:506) at com.sun.enterprise.util.ORBManager.getORB(ORBManager.java:264) at com.sun.enterprise.naming.SerialInitContextFactory.getInitialContext(SerialInitContextFactory.java:141) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.(InitialContext.java:175) at com.example.xxx.xxx.TestMe.connect(TestParent.java:41) at com.example.xxx.TestTransactions.setUp(TestTransactions.java:33) at junit.framework.TestCase.runBare(TestCase.java:125) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.battery.JUnitBattery.executeJUnit(JUnitBattery.java:242) at org.apache.maven.surefire.battery.JUnitBattery.execute(JUnitBattery.java:216) at org.apache.maven.surefire.Surefire.executeBattery(Surefire.java:215) at org.apache.maven.surefire.Surefire.run(Surefire.java:126) at org.apache.maven.surefire.Surefire.run(Surefire.java:87) at org.apache.maven.surefire.Surefire.run(Surefire.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.SurefireBooter.main(SurefireBooter.java:785) Caused by: java.lang.VerifyError: (class: com/sun/corba/ee/impl/orb/ORBImpl, method: create_context_list signature: ()Lorg/omg/CORBA/ContextList;) Incompatible argument to function at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at org.omg.CORBA.ORB.create_impl(ORB.java:295) ... 32 more -- 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: (MDEP-94) Add dependency:tree goal
[ http://jira.codehaus.org/browse/MDEP-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99165 ] Mark Hobson commented on MDEP-94: - You running this in an IDE? Note the maven-plugin-testing-harness dependency has been upped to 1.1-SNAPSHOT, it looks like it's still on 1.0-beta-1. > Add dependency:tree goal > > > Key: MDEP-94 > URL: http://jira.codehaus.org/browse/MDEP-94 > Project: Maven 2.x Dependency Plugin > Issue Type: New Feature > Components: tree >Affects Versions: 2.0-alpha-5 >Reporter: Mark Hobson >Assignee: Brian Fox > Attachments: MDEP-94-test.patch, patch.txt > > > The attached patch adds the help:dependencies goal from the maven-help-plugin > to the maven-dependency-plugin as dependency:tree, as discussed on the dev > mailing list. -- 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: (MRELEASE-248) release:prepare fails with Starteam 2006
[ http://jira.codehaus.org/browse/MRELEASE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99166 ] Giovanni Pedone commented on MRELEASE-248: -- The problem arises when the release:prepare tries to checkin the modified pom. Once again, it does NOT happen with stcmd Starteam 2005. [INFO] Checking in modified POMs... [WARNING] Your scm URL use a deprecated format. The new format is :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] [INFO] Working directory: D:\gpedone\Documenti\Projects\PostePerNoi\webcontainer [INFO] Command line: stcmd ci -x -nologo -stop -p [EMAIL PROTECTED]:49201/epv3_webapps/webcontainer -fp D:/gpedone/Documenti/Projects/PostePerNoi/webcontainer -r "[maven-release-plugin] prepare release webcontainer-1.2" pom.xml [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to commit files Provider message: The starteam command failed. Command output: Error occurred: Cannot validate check-in operation for a file with Unknown status. Please check out the file first or use force check-in, if you are confident of your changes. > release:prepare fails with Starteam 2006 > > > Key: MRELEASE-248 > URL: http://jira.codehaus.org/browse/MRELEASE-248 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 > Environment: windows xp, starteam 2006 >Reporter: Giovanni Pedone > > when performing release:prepare and issuing the command stcmd, it fails to > checkout/checkin, complaining about "Unknown status". > It does not happen with stcmd shipping with Starteam 2005 R2. > It happens only with Starteam 2006 stcmd. -- 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-249) Maven 2.0.x Releases now broken post 2.0-beta-4
Maven 2.0.x Releases now broken post 2.0-beta-4 --- Key: MRELEASE-249 URL: http://jira.codehaus.org/browse/MRELEASE-249 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-6, 2.0-beta-5 Reporter: Jason van Zyl The Maven 2.0.x releases no longer work due to the plugin getting confused about using a property to specify a version which is used in the dependencyManagement section. -- 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-2934) Cannot Deploy Using Webdav due to DependencyManagement
[ http://jira.codehaus.org/browse/MNG-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99171 ] Jochen Wiedmann commented on MNG-2934: -- Is this actually fixed? I've got the same problem with 2.0.7-SNAPSHOT, as picked from prople.apache.org/~jvanzyl some minutes ago. > Cannot Deploy Using Webdav due to DependencyManagement > -- > > Key: MNG-2934 > URL: http://jira.codehaus.org/browse/MNG-2934 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, Deployment >Affects Versions: 2.0.6 >Reporter: Stephen Duncan Jr >Assignee: Jason van Zyl > Fix For: 2.0.7 > > Attachments: pom.xml > > > The webdav wagon requires commons-httpclient-2.0.2.jar. If I have a > dependencyManagement section that specifies commons-httpclient 3.0.1, then > deployment fails. > The resulting output is: > [EMAIL PROTECTED] webdavtest]$ mvn deploy > [INFO] Scanning for projects... > [INFO] artifact org.apache.maven.wagon:wagon-webdav: checking for updates > from ce-releases > - > this realm = app0.child-container[extensions] > urls[0] = > file:/home/duncans/.m2/repository/de/zeigermann/xml/xml-im-exporter/1.1/xml-im-exporter-1.1.jar > urls[1] = file:/home/duncans/.m2/repository/jdom/jdom/1.0/jdom-1.0.jar > urls[2] = > file:/home/duncans/.m2/repository/org/apache/maven/wagon/wagon-webdav/1.0-beta-2/wagon-webdav-1.0-beta-2.jar > urls[3] = > file:/home/duncans/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar > urls[4] = > file:/home/duncans/.m2/repository/slide/slide-webdavlib/2.1/slide-webdavlib-2.1.jar > urls[5] = > file:/home/duncans/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > urls[6] = > file:/home/duncans/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar > urls[7] = > file:/home/duncans/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar > urls[8] = file:/home/duncans/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar > Number of imports: 0 > this realm = plexus.core > urls[0] = file:/home/duncans/apps/maven/lib/maven-core-2.0.6-uber.jar > Number of imports: 0 > - > [INFO] > > [INFO] Building Unnamed - test:webdavtest:pom:1.0-SNAPSHOT > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [site:attach-descriptor] > [INFO] [install:install] > [INFO] Installing /home/duncans/tmp/webdavtest/pom.xml to > /home/duncans/.m2/repository/test/webdavtest/1.0-SNAPSHOT/webdavtest-1.0-SNAPSHOT.pom > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from snapshots > [WARNING] repository metadata for: 'snapshot test:webdavtest:1.0-SNAPSHOT' > could not be retrieved from repository: snapshots due to an error: > Unsupported Protocol: 'dav': Cannot find wagon which supports the requested > protocol: dav > [INFO] Repository 'snapshots' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find > wagon which supports the requested protocol: dav > Component descriptor cannot be found in the component repository: > org.apache.maven.wagon.Wagondav. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Thu Apr 05 13:49:52 EDT 2007 > [INFO] Final Memory: 6M/10M > [INFO] > -- 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-2934) Cannot Deploy Using Webdav due to DependencyManagement
[ http://jira.codehaus.org/browse/MNG-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99174 ] Jochen Wiedmann commented on MNG-2934: -- Is this actually fixed? I still do have the same problem, with 2.0.7-SNAPSHOT as available from Jason's home on people.apache.org with a date of 10-June-2007. > Cannot Deploy Using Webdav due to DependencyManagement > -- > > Key: MNG-2934 > URL: http://jira.codehaus.org/browse/MNG-2934 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, Deployment >Affects Versions: 2.0.6 >Reporter: Stephen Duncan Jr >Assignee: Jason van Zyl > Fix For: 2.0.7 > > Attachments: pom.xml > > > The webdav wagon requires commons-httpclient-2.0.2.jar. If I have a > dependencyManagement section that specifies commons-httpclient 3.0.1, then > deployment fails. > The resulting output is: > [EMAIL PROTECTED] webdavtest]$ mvn deploy > [INFO] Scanning for projects... > [INFO] artifact org.apache.maven.wagon:wagon-webdav: checking for updates > from ce-releases > - > this realm = app0.child-container[extensions] > urls[0] = > file:/home/duncans/.m2/repository/de/zeigermann/xml/xml-im-exporter/1.1/xml-im-exporter-1.1.jar > urls[1] = file:/home/duncans/.m2/repository/jdom/jdom/1.0/jdom-1.0.jar > urls[2] = > file:/home/duncans/.m2/repository/org/apache/maven/wagon/wagon-webdav/1.0-beta-2/wagon-webdav-1.0-beta-2.jar > urls[3] = > file:/home/duncans/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar > urls[4] = > file:/home/duncans/.m2/repository/slide/slide-webdavlib/2.1/slide-webdavlib-2.1.jar > urls[5] = > file:/home/duncans/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > urls[6] = > file:/home/duncans/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar > urls[7] = > file:/home/duncans/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar > urls[8] = file:/home/duncans/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar > Number of imports: 0 > this realm = plexus.core > urls[0] = file:/home/duncans/apps/maven/lib/maven-core-2.0.6-uber.jar > Number of imports: 0 > - > [INFO] > > [INFO] Building Unnamed - test:webdavtest:pom:1.0-SNAPSHOT > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [site:attach-descriptor] > [INFO] [install:install] > [INFO] Installing /home/duncans/tmp/webdavtest/pom.xml to > /home/duncans/.m2/repository/test/webdavtest/1.0-SNAPSHOT/webdavtest-1.0-SNAPSHOT.pom > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from snapshots > [WARNING] repository metadata for: 'snapshot test:webdavtest:1.0-SNAPSHOT' > could not be retrieved from repository: snapshots due to an error: > Unsupported Protocol: 'dav': Cannot find wagon which supports the requested > protocol: dav > [INFO] Repository 'snapshots' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find > wagon which supports the requested protocol: dav > Component descriptor cannot be found in the component repository: > org.apache.maven.wagon.Wagondav. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Thu Apr 05 13:49:52 EDT 2007 > [INFO] Final Memory: 6M/10M > [INFO] > -- 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-2934) Cannot Deploy Using Webdav due to DependencyManagement
[ http://jira.codehaus.org/browse/MNG-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99175 ] Jason van Zyl commented on MNG-2934: Yes, given the sample POM I was given. I correct the extension loader and the right version of httpclient is loaded. > Cannot Deploy Using Webdav due to DependencyManagement > -- > > Key: MNG-2934 > URL: http://jira.codehaus.org/browse/MNG-2934 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, Deployment >Affects Versions: 2.0.6 >Reporter: Stephen Duncan Jr >Assignee: Jason van Zyl > Fix For: 2.0.7 > > Attachments: pom.xml > > > The webdav wagon requires commons-httpclient-2.0.2.jar. If I have a > dependencyManagement section that specifies commons-httpclient 3.0.1, then > deployment fails. > The resulting output is: > [EMAIL PROTECTED] webdavtest]$ mvn deploy > [INFO] Scanning for projects... > [INFO] artifact org.apache.maven.wagon:wagon-webdav: checking for updates > from ce-releases > - > this realm = app0.child-container[extensions] > urls[0] = > file:/home/duncans/.m2/repository/de/zeigermann/xml/xml-im-exporter/1.1/xml-im-exporter-1.1.jar > urls[1] = file:/home/duncans/.m2/repository/jdom/jdom/1.0/jdom-1.0.jar > urls[2] = > file:/home/duncans/.m2/repository/org/apache/maven/wagon/wagon-webdav/1.0-beta-2/wagon-webdav-1.0-beta-2.jar > urls[3] = > file:/home/duncans/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar > urls[4] = > file:/home/duncans/.m2/repository/slide/slide-webdavlib/2.1/slide-webdavlib-2.1.jar > urls[5] = > file:/home/duncans/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > urls[6] = > file:/home/duncans/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar > urls[7] = > file:/home/duncans/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar > urls[8] = file:/home/duncans/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar > Number of imports: 0 > this realm = plexus.core > urls[0] = file:/home/duncans/apps/maven/lib/maven-core-2.0.6-uber.jar > Number of imports: 0 > - > [INFO] > > [INFO] Building Unnamed - test:webdavtest:pom:1.0-SNAPSHOT > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [site:attach-descriptor] > [INFO] [install:install] > [INFO] Installing /home/duncans/tmp/webdavtest/pom.xml to > /home/duncans/.m2/repository/test/webdavtest/1.0-SNAPSHOT/webdavtest-1.0-SNAPSHOT.pom > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from snapshots > [WARNING] repository metadata for: 'snapshot test:webdavtest:1.0-SNAPSHOT' > could not be retrieved from repository: snapshots due to an error: > Unsupported Protocol: 'dav': Cannot find wagon which supports the requested > protocol: dav > [INFO] Repository 'snapshots' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find > wagon which supports the requested protocol: dav > Component descriptor cannot be found in the component repository: > org.apache.maven.wagon.Wagondav. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Thu Apr 05 13:49:52 EDT 2007 > [INFO] Final Memory: 6M/10M > [INFO] > -- 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-2934) Cannot Deploy Using Webdav due to DependencyManagement
[ http://jira.codehaus.org/browse/MNG-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99176 ] Jason van Zyl commented on MNG-2934: If you have a problem, give me your sample build and open another issue. > Cannot Deploy Using Webdav due to DependencyManagement > -- > > Key: MNG-2934 > URL: http://jira.codehaus.org/browse/MNG-2934 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, Deployment >Affects Versions: 2.0.6 >Reporter: Stephen Duncan Jr >Assignee: Jason van Zyl > Fix For: 2.0.7 > > Attachments: pom.xml > > > The webdav wagon requires commons-httpclient-2.0.2.jar. If I have a > dependencyManagement section that specifies commons-httpclient 3.0.1, then > deployment fails. > The resulting output is: > [EMAIL PROTECTED] webdavtest]$ mvn deploy > [INFO] Scanning for projects... > [INFO] artifact org.apache.maven.wagon:wagon-webdav: checking for updates > from ce-releases > - > this realm = app0.child-container[extensions] > urls[0] = > file:/home/duncans/.m2/repository/de/zeigermann/xml/xml-im-exporter/1.1/xml-im-exporter-1.1.jar > urls[1] = file:/home/duncans/.m2/repository/jdom/jdom/1.0/jdom-1.0.jar > urls[2] = > file:/home/duncans/.m2/repository/org/apache/maven/wagon/wagon-webdav/1.0-beta-2/wagon-webdav-1.0-beta-2.jar > urls[3] = > file:/home/duncans/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar > urls[4] = > file:/home/duncans/.m2/repository/slide/slide-webdavlib/2.1/slide-webdavlib-2.1.jar > urls[5] = > file:/home/duncans/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > urls[6] = > file:/home/duncans/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar > urls[7] = > file:/home/duncans/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar > urls[8] = file:/home/duncans/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar > Number of imports: 0 > this realm = plexus.core > urls[0] = file:/home/duncans/apps/maven/lib/maven-core-2.0.6-uber.jar > Number of imports: 0 > - > [INFO] > > [INFO] Building Unnamed - test:webdavtest:pom:1.0-SNAPSHOT > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [site:attach-descriptor] > [INFO] [install:install] > [INFO] Installing /home/duncans/tmp/webdavtest/pom.xml to > /home/duncans/.m2/repository/test/webdavtest/1.0-SNAPSHOT/webdavtest-1.0-SNAPSHOT.pom > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from snapshots > [WARNING] repository metadata for: 'snapshot test:webdavtest:1.0-SNAPSHOT' > could not be retrieved from repository: snapshots due to an error: > Unsupported Protocol: 'dav': Cannot find wagon which supports the requested > protocol: dav > [INFO] Repository 'snapshots' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find > wagon which supports the requested protocol: dav > Component descriptor cannot be found in the component repository: > org.apache.maven.wagon.Wagondav. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Thu Apr 05 13:49:52 EDT 2007 > [INFO] Final Memory: 6M/10M > [INFO] > -- 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-1596) Please add Sesame 1.2.7 and Rio 1.0.10 bundles to your maven2 repository
Please add Sesame 1.2.7 and Rio 1.0.10 bundles to your maven2 repository Key: MAVENUPLOAD-1596 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1596 Project: maven-upload-requests Issue Type: Task Reporter: Arjohn Kampman http://www.openrdf.org/maven/sesame-1.2.7-bundle.jar http://www.openrdf.org/maven/rio-1.0.10-bundle.jar http://www.openrdf.org/maven/openrdf-util-1.2.7-bundle.jar http://www.openrdf.org/maven/openrdf-model-1.2.7-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: (MNG-2934) Cannot Deploy Using Webdav due to DependencyManagement
[ http://jira.codehaus.org/browse/MNG-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99179 ] Jochen Wiedmann commented on MNG-2934: -- Ok, confirmed, 2.0.7-SNAPSHOT works. I didn't have declared wagon-webdav as an extension. > Cannot Deploy Using Webdav due to DependencyManagement > -- > > Key: MNG-2934 > URL: http://jira.codehaus.org/browse/MNG-2934 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, Deployment >Affects Versions: 2.0.6 >Reporter: Stephen Duncan Jr >Assignee: Jason van Zyl > Fix For: 2.0.7 > > Attachments: pom.xml > > > The webdav wagon requires commons-httpclient-2.0.2.jar. If I have a > dependencyManagement section that specifies commons-httpclient 3.0.1, then > deployment fails. > The resulting output is: > [EMAIL PROTECTED] webdavtest]$ mvn deploy > [INFO] Scanning for projects... > [INFO] artifact org.apache.maven.wagon:wagon-webdav: checking for updates > from ce-releases > - > this realm = app0.child-container[extensions] > urls[0] = > file:/home/duncans/.m2/repository/de/zeigermann/xml/xml-im-exporter/1.1/xml-im-exporter-1.1.jar > urls[1] = file:/home/duncans/.m2/repository/jdom/jdom/1.0/jdom-1.0.jar > urls[2] = > file:/home/duncans/.m2/repository/org/apache/maven/wagon/wagon-webdav/1.0-beta-2/wagon-webdav-1.0-beta-2.jar > urls[3] = > file:/home/duncans/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar > urls[4] = > file:/home/duncans/.m2/repository/slide/slide-webdavlib/2.1/slide-webdavlib-2.1.jar > urls[5] = > file:/home/duncans/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > urls[6] = > file:/home/duncans/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar > urls[7] = > file:/home/duncans/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar > urls[8] = file:/home/duncans/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar > Number of imports: 0 > this realm = plexus.core > urls[0] = file:/home/duncans/apps/maven/lib/maven-core-2.0.6-uber.jar > Number of imports: 0 > - > [INFO] > > [INFO] Building Unnamed - test:webdavtest:pom:1.0-SNAPSHOT > [INFO]task-segment: [deploy] > [INFO] > > [INFO] [site:attach-descriptor] > [INFO] [install:install] > [INFO] Installing /home/duncans/tmp/webdavtest/pom.xml to > /home/duncans/.m2/repository/test/webdavtest/1.0-SNAPSHOT/webdavtest-1.0-SNAPSHOT.pom > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from snapshots > [WARNING] repository metadata for: 'snapshot test:webdavtest:1.0-SNAPSHOT' > could not be retrieved from repository: snapshots due to an error: > Unsupported Protocol: 'dav': Cannot find wagon which supports the requested > protocol: dav > [INFO] Repository 'snapshots' will be blacklisted > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find > wagon which supports the requested protocol: dav > Component descriptor cannot be found in the component repository: > org.apache.maven.wagon.Wagondav. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Thu Apr 05 13:49:52 EDT 2007 > [INFO] Final Memory: 6M/10M > [INFO] > -- 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-143) improve error reporting on corrupt jars, poms, etc
[ http://jira.codehaus.org/browse/MRM-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99181 ] Maria Odea Ching commented on MRM-143: -- A jar is corrupted when: - it is not readable - the jar's filename does not match it's pom's artifactId and version (pom included in the jar) - the files inside the jar file are not readable (?) A pom is corrupted when: - it is not readable - the pom file itself does not match the artifactId and version in its content - the pom file does not match its corresponding jar file (if present) Are there other things that were not included above? And are the metadata and checksum files also included here? > improve error reporting on corrupt jars, poms, etc > -- > > Key: MRM-143 > URL: http://jira.codehaus.org/browse/MRM-143 > Project: Archiva > Issue Type: Improvement > Components: indexing >Reporter: Brett Porter >Assignee: Maria Odea Ching > Fix For: 1.0-alpha-2 > > > currently, many failures can be detected during indexing but none are > reported anywhere other than the logs. Either these need to be sent through > the regular reporting mechanism, or the regular reporting mechanism needs to > be able to come back later and pick up the same issues. -- 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-338) Unable to disable assertions (-da)
Unable to disable assertions (-da) -- Key: SUREFIRE-338 URL: http://jira.codehaus.org/browse/SUREFIRE-338 Project: Maven Surefire Issue Type: Bug Components: plugin Affects Versions: 2.3 Environment: Ubuntu Linux, Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing), maven 2.0.6 Reporter: Emilian Bold Attachments: maven-disable-assertions.zip I'm unable to disable assertions while running tests with the surefire plugin. I have product "assert1" with a code with "assert false" (this always throws an AssertionError when assertions are enabled). I use the code in assert2 in a unit-test and it *always* throws an assertion error with surefire 2.3. org.apache.maven.plugins maven-surefire-plugin pertest -da false I can play with various values for forkMode and childDelegation with no luck. The only working way is forcing the version to 2.1.33 and with the above settings (pertest forkmode, false childDelegation). I'm attaching a zip with 2 projects. Trying to run mvn test on assert2 will throw an assertion error except if forcing the surefire version to 2.1.3. -- 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: (MRELEASE-248) release:prepare fails with Starteam 2006
[ http://jira.codehaus.org/browse/MRELEASE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99187 ] Dan Tran commented on MRELEASE-248: --- are you able to execute the same command line with additional password argument ( see stdcmd syntax for detail? ) > release:prepare fails with Starteam 2006 > > > Key: MRELEASE-248 > URL: http://jira.codehaus.org/browse/MRELEASE-248 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 > Environment: windows xp, starteam 2006 >Reporter: Giovanni Pedone > > when performing release:prepare and issuing the command stcmd, it fails to > checkout/checkin, complaining about "Unknown status". > It does not happen with stcmd shipping with Starteam 2005 R2. > It happens only with Starteam 2006 stcmd. -- 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-1597) jemmy 2.2.7.5
jemmy 2.2.7.5 - Key: MAVENUPLOAD-1597 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1597 Project: maven-upload-requests Issue Type: Task Reporter: Denis N. Antonioli -- 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: (MRELEASE-248) release:prepare fails with Starteam 2006
[ http://jira.codehaus.org/browse/MRELEASE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99189 ] Giovanni Pedone commented on MRELEASE-248: -- Dan, what do you mean ? the password is not the issue, it works just fine. By the way, I won't be able to modify any of the stcmd commmand line arguments when using thru the release:prepare plugin ;-) > release:prepare fails with Starteam 2006 > > > Key: MRELEASE-248 > URL: http://jira.codehaus.org/browse/MRELEASE-248 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 > Environment: windows xp, starteam 2006 >Reporter: Giovanni Pedone > > when performing release:prepare and issuing the command stcmd, it fails to > checkout/checkin, complaining about "Unknown status". > It does not happen with stcmd shipping with Starteam 2005 R2. > It happens only with Starteam 2006 stcmd. -- 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-1598) JasperReports 1.3.4 upload
JasperReports 1.3.4 upload -- Key: MAVENUPLOAD-1598 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1598 Project: maven-upload-requests Issue Type: Task Reporter: Teodor Danciu http://rs.jaspersoft.com/maven2/jasperreports-1.3.4-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: (MECLIPSE-281) Documentation patch for PDE support
Documentation patch for PDE support --- Key: MECLIPSE-281 URL: http://jira.codehaus.org/browse/MECLIPSE-281 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: PDE support Affects Versions: 2.3 Reporter: Graham Leggett Fix For: 2.4 Attachments: pde-docs.diff The attached patch documents the PDE feature of maven-eclipse-plugin. -- 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: (MASSEMBLY-210) repository does not include the parent pom
[
http://jira.codehaus.org/browse/MASSEMBLY-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MASSEMBLY-210:
-
If I build with 2.1-snapshot of maven, I get:
org.apache.maven.BuildFailureException
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:296)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:112)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:906)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:367)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
Caused by: java.lang.NullPointerException
at
org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:94)
at
org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:278)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:643)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:354)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:255)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:141)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
... 11 more
> repository does not include the parent pom
> --
>
> Key: MASSEMBLY-210
> URL: http://jira.codehaus.org/browse/MASSEMBLY-210
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-1
>Reporter: Stephane Nicoll
>Assignee: John Casey
> Fix For: 2.2-beta-2
>
>
> I am running the assembly on a project with a parent pom. encoding="ISO-8859-15"?> dist
> zip
> true
> foo-${version}
> . foo-base
> true
> /target/
> repository
> test
> The parent pom is not included 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: (MASSEMBLY-210) repository does not include the parent pom
[
http://jira.codehaus.org/browse/MASSEMBLY-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MASSEMBLY-210:
-
I've upgraded the version of the plexus-maven-plugin in the POM to 1.3.5, which
fixes my NPE using maven-2.1-snapshot. I've also verified that this project
builds under maven-2.0.6, at least with the new plexus-maven-plugin version.
Can you try it again? I've deployed the assembly plugin version that I built
with maven 2.0.5.
> repository does not include the parent pom
> --
>
> Key: MASSEMBLY-210
> URL: http://jira.codehaus.org/browse/MASSEMBLY-210
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-1
>Reporter: Stephane Nicoll
>Assignee: John Casey
> Fix For: 2.2-beta-2
>
>
> I am running the assembly on a project with a parent pom. encoding="ISO-8859-15"?> dist
> zip
> true
> foo-${version}
> . foo-base
> true
> /target/
> repository
> test
> The parent pom is not included 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] Created: (MAVENUPLOAD-1600) mockejb 0.6-beta2
mockejb 0.6-beta2 -- Key: MAVENUPLOAD-1600 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1600 Project: maven-upload-requests Issue Type: Improvement Reporter: Andy Lawrence Attachments: mockejb-0.6-beta2-bundle.jar the attached is a bundle I made for including mockejb 0.6-beta2 into the central repo. I am NOT a developer on this project -- only a user who wants to make this more accessible. Of course, if there are issues with this submission, I am willing to fix. -- 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-1600) mockejb 0.6-beta2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1600. --- Assignee: Carlos Sanchez Resolution: Fixed > mockejb 0.6-beta2 > -- > > Key: MAVENUPLOAD-1600 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1600 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: Andy Lawrence >Assignee: Carlos Sanchez > Attachments: mockejb-0.6-beta2-bundle.jar > > > the attached is a bundle I made for including mockejb 0.6-beta2 into the > central repo. > I am NOT a developer on this project -- only a user who wants to make this > more accessible. > Of course, if there are issues with this submission, I am willing to fix. -- 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-1599) Java port of Mozilla charset detector
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99254 ] Carlos Sanchez commented on MAVENUPLOAD-1599: - groupId should be net.sourceforge.jchardet > Java port of Mozilla charset detector > - > > Key: MAVENUPLOAD-1599 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1599 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: Raphaël Piéroni > Attachments: jchardet-1.0-bundle.jar, LICENSE.txt > > > http://jchardet.sourceforge.net/ > http://sourceforge.net/projects/jchardet/ > email : i18nfaq at users.sourceforge.net > Java port of Mozilla's automatic charset detection algorithm. > See... http://www.mozilla.org/projects/intl/chardet.html\";> > http://www.mozilla.org/projects/intl/chardet.html for > the details of the orginal code and Author. > The bundle was created using the information on the web site and from the jar > file found in the folowwing download URL > http://sourceforge.net/project/showfiles.php?group_id=85452&package_id=88539&release_id=171192 > Regards, > Raphaël -- 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-1596) Please add Sesame 1.2.7 and Rio 1.0.10 bundles to your maven2 repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1596. --- Assignee: Carlos Sanchez Resolution: Fixed > Please add Sesame 1.2.7 and Rio 1.0.10 bundles to your maven2 repository > > > Key: MAVENUPLOAD-1596 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1596 > Project: maven-upload-requests > Issue Type: Task >Reporter: Arjohn Kampman >Assignee: Carlos Sanchez > > http://www.openrdf.org/maven/sesame-1.2.7-bundle.jar > http://www.openrdf.org/maven/rio-1.0.10-bundle.jar > http://www.openrdf.org/maven/openrdf-util-1.2.7-bundle.jar > http://www.openrdf.org/maven/openrdf-model-1.2.7-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] Updated: (MANTTASKS-18) filesetId does not contain all dependencies when artifact was not yet locally installed
[ http://jira.codehaus.org/browse/MANTTASKS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MANTTASKS-18: --- Attachment: MANTTASKS-18_new2.diff Yeah! looking for a real fix, I just found MNG-2961 DefaultArtifact getBaseVersion is changed to "-SNAPSHOT" only if you first call isSnapshot() That's it!!! Here is a new patch with this little workaround: simply call artifact.isSnapshot() before calculating filename. Unit test show that it works: cool. Now, the real bug is in MNG-2961, and the workaround in Maven Ant Tasks is really simple. > filesetId does not contain all dependencies when artifact was not yet locally > installed > --- > > Key: MANTTASKS-18 > URL: http://jira.codehaus.org/browse/MANTTASKS-18 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: dependencies task >Affects Versions: 2.0.6 > Environment: java version "1.4.2_04", Linux 2.6.11.12, Apache Ant > version 1.6.5 >Reporter: Ingo Weichsel >Priority: Critical > Fix For: 2.0.7 > > Attachments: MANTTASKS-18_new.diff, MANTTASKS-18_new.tgz, > MANTTASKS-18_new2.diff, patch.txt > > > In the artifact:dependencies task the filesetId is only correctly set, when > the artifact was installed locally before running ant. > After deletion of the local repository the dependant artifacts will be > downloaded to the local repository, but only one of two dependant files will > be included in the ant fileset. The classpath is set correctly. > After running "mvn install" locally for the "as-base-launcher" maven project, > ant computes the correct filesetId. > The ant-project depends on the artifact "as-base-launcher" which itselfs > depends only on classworlds. Snippets from ant buildfiles, poms and ant > output follows: > From the ant buildfile: > > > > pathId="as-launcher.classpath" verbose="true"> > > > > > > > > > > > > > > > > > The referenced POM defining the ant dependencies: > > 4.0.0 > actis > ant-as-base > 1.0-SNAPSHOT > > > actis > as-base-launcher > 1.0-SNAPSHOT > > > > > actisRepository > actisRepository > http://company.com:/repository/ > > > > Output of the ant run: > launcherJAR: > actis:ant-as-base:jar:1.0-SNAPSHOT (selected) > actis:as-base-launcher:jar:1.0-SNAPSHOT (selected) > classworlds:classworlds:jar:1.1-alpha-1 (selected) > [echo] CLASSPATH: > /home/iwe/.m2/repository/classworlds/classworlds/1.1-alpha-1/classworlds-1.1-alpha-1.jar:/home/iwe/.m2/repository/actis/as-base-launcher/1.0-20051103.102305-8/as-base-launcher-1.0-20051103.102305-8.jar > [echo] FILESET: > /home/iwe/.m2/repository/classworlds/classworlds/1.1-alpha-1/classworlds-1.1-alpha-1.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: (MAVENUPLOAD-1597) jemmy 2.2.7.5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99260 ] Carlos Sanchez commented on MAVENUPLOAD-1597: - I can't read the pom without line returns > jemmy 2.2.7.5 > - > > Key: MAVENUPLOAD-1597 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1597 > Project: maven-upload-requests > Issue Type: Task >Reporter: Denis N. Antonioli > -- 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-1598) JasperReports 1.3.4 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1598. --- Assignee: Carlos Sanchez Resolution: Fixed > JasperReports 1.3.4 upload > -- > > Key: MAVENUPLOAD-1598 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1598 > Project: maven-upload-requests > Issue Type: Task >Reporter: Teodor Danciu >Assignee: Carlos Sanchez > > http://rs.jaspersoft.com/maven2/jasperreports-1.3.4-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: (MRELEASE-248) release:prepare fails with Starteam 2006
[ http://jira.codehaus.org/browse/MRELEASE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99261 ] Dan Tran commented on MRELEASE-248: --- I just want to make sure you can run the stdcmd line outside of release:prepare scope, and use it to trouble shoot the problem. More likely, starteam 2006 may have changed some syntax. Also please use starteam gui interface to find out why you to be checked file has a "unknown status" > release:prepare fails with Starteam 2006 > > > Key: MRELEASE-248 > URL: http://jira.codehaus.org/browse/MRELEASE-248 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 > Environment: windows xp, starteam 2006 >Reporter: Giovanni Pedone > > when performing release:prepare and issuing the command stcmd, it fails to > checkout/checkin, complaining about "Unknown status". > It does not happen with stcmd shipping with Starteam 2005 R2. > It happens only with Starteam 2006 stcmd. -- 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-1597) jemmy 2.2.7.5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99263 ] Denis N. Antonioli commented on MAVENUPLOAD-1597: - Sorry. Just uploaded a new version with better formatting of the pom. > jemmy 2.2.7.5 > - > > Key: MAVENUPLOAD-1597 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1597 > Project: maven-upload-requests > Issue Type: Task >Reporter: Denis N. Antonioli > -- 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-250) release perform fails because it cannot find the distributionManagement in the base pom
release perform fails because it cannot find the distributionManagement in the base pom --- Key: MRELEASE-250 URL: http://jira.codehaus.org/browse/MRELEASE-250 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-6 Reporter: James William Dumay Attachments: release-perform-log.txt We have specified in our base pom the distribution repository for other maven 2 projects to inherit from. The trouble is when we run mvn release:perform, maven compains that there was no distributionManagement set. I have also check that the base pom is correct and that the child pom inherits off of the base pom correctly. A small log is attached. -- 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
