[jira] Created: (MRELEASE-84) Check in release.properties into CVS during the tag then remove
Check in release.properties into CVS during the tag then remove --- Key: MRELEASE-84 URL: http://jira.codehaus.org/browse/MRELEASE-84 Project: Maven 2.x Release Plugin Type: Improvement Environment: windows 2000 Reporter: Todd Nine Is it possible to add an enhancement that will check in the release.properties before tagging takes place? Alternatively it could be added and tagged after the tagging of the initial project to ensure the tag went smoothly This way any developer can pull down the source with a give tag, say foo-1_0_5, and perform a mvn release:perform to quickly create a build. A good use would be if the local maven 2 repository is lost due to system failure, the artifacts could easily be re-created from the SCM tag. Todd -- 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: (MEJB-7) Transitive Classpath not written to the manifest
Transitive Classpath not written to the manifest Key: MEJB-7 URL: http://jira.codehaus.org/browse/MEJB-7 Project: Maven 2.x Ejb Plugin Type: Bug Reporter: Todd Nine The transitive classpath of all dependencies from the dependencies in an EJB pom are not added to the MANIFEST.MF classpath. This causes the ejb to not deploy correctly. Todd -- 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: (MSITE-25) mvn site:site ignores server configuration in settings.xml
[ http://jira.codehaus.org/browse/MSITE-25?page=comments#action_61275 ] Todd Nine commented on MSITE-25: I am also experiencing this issue. This bug eliminates most large organizations from using the site plug-in due to the windows platform. Is there a system property that can be set for the site build that will override the ssh executable until the plug-in is fixed? > mvn site:site ignores server configuration in settings.xml > -- > > Key: MSITE-25 > URL: http://jira.codehaus.org/browse/MSITE-25 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Alan Cabrera > Priority: Critical > Fix For: 2.0 > > > mvn site:site ignores parts of my settings.xml: > > livetribe-website > 664 > 775 > > plink > pscp > > livetribe > > It uses the username when ssh but does not invoke plink. > [INFO] [site:deploy] > Using private key: C:\Documents and Settings\adc\.ssh\id_dsa > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Opened > Executing command: ssh -i "C:\Documents and Settings\adc\.ssh\id_dsa" -o > "BatchMode yes" [EMAIL PROTECTED] "mkdir -p > /home/projects/livetribe/public_html/maven/." > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Disconnecting > scpexe://repo.livetribe.org/home/projects/livetribe/public_html/maven/ - > Session: Disconnected -- 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: (MSUREFIRE-83) Tests run with Surefire are not able to make remote calls to an RMI server of an EJB server
Tests run with Surefire are not able to make remote calls to an RMI server of an EJB server --- Key: MSUREFIRE-83 URL: http://jira.codehaus.org/browse/MSUREFIRE-83 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.1.2 Environment: Windows 2000, Java JDK 1.4 Reporter: Todd Nine Priority: Blocker Attachments: verbose_app_ output.txt I am unable run any unit tests that connect to a remote RMI server. This includes vanilla RMI, or JBoss remote connections. I can however use the same classpath set by maven with the maven 2 eclipse plugin, and all tests execute successfully. I always receive a socket timeout, which seems to be the root cause of the remote connectivity issues, but I only receive them when running the tests from within surefire. I have attached a stack trace and verbose output. -- 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-6) Multiproject Release: No check in
[ http://jira.codehaus.org/browse/MRELEASE-6?page=comments#action_62988 ] Todd Nine commented on MRELEASE-6: -- I agree that making assumptions about the scm url in an eclipse "flat" directory structure is not a good implementation. However if each pom explicitly states the scmurl, why is that not used in the reactor as each child is built? Can that simply be the required behavior in order to fix this bug when using a flat directory structure? > Multiproject Release: No check in > - > > Key: MRELEASE-6 > URL: http://jira.codehaus.org/browse/MRELEASE-6 > Project: Maven 2.x Release Plugin > Type: Bug > Environment: Windows XP, Eclipse Workspace > Reporter: Bernd Mau > Priority: Critical > > > I tried to release a multiproject with 5 modules (on a Branch). Well, > the POMs of all modules are changed and there are some dependencies > which have been updated correctly. But only the master has been checked > in correctly. > I'm changed the recommended layout, to fit in an eclipse workspace. I > have one master at the same level as the other modules. > The module section of the master pom.xml: > > ../hhla.library.pom > ../hhla.library.site > ../hhla.lang > ../hhla.common.log4jx > -- 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-2213) Current settings.xml example incorrect
Current settings.xml example incorrect --- Key: MNG-2213 URL: http://jira.codehaus.org/browse/MNG-2213 Project: Maven 2 Type: Improvement Versions: 2.0.3 Reporter: Todd Nine The settings.xml in the example is incorrect. The child tags of repository and pluginRepository are releases and snapshots, not release and snapshot. Todd -- 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-94) Modified Parent POM is not commited
Modified Parent POM is not commited --- Key: MRELEASE-94 URL: http://jira.codehaus.org/browse/MRELEASE-94 Project: Maven 2.x Release Plugin Type: Bug Versions: 2.0-beta-3 Environment: Windows 2k, or Windows XP. JDK 1.4.2, scpexe=pscp sshexe=plink cvs=cvs.exe CVS_RSH=plink. Key authentication via pageant Reporter: Todd Nine Priority: Blocker I can successfully tag all sub projects of a parent pom (with the standard directory structure), but I'm unable complete the release:prepare operation since the parent POM is not checked in. As a result I am unable to perform a multi-project release. Each child pom has the scm repotisotries declared in the pom. Attached is verbose output of the command. mvn -Duser.name=c200506 -X clean release:prepare [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-plugin-parameter-documenter:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-error-diagnostics:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0:runtime (selected for runtime)[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven:maven-monitor:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-monitor:jar:2.0:runtime (selected for runtime ) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:mav en-settings:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for runtim e) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtim e (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven:maven-plugin-descriptor:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0:runtime (selected f or runtime) [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for ru ntime) [DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5:runtime (selected f or runtime) [DEBUG] com.jcraft:jsch:jar:0.1.23:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] Retrieving parent-POM: org.apache.maven.reporting:maven-reporting::2.0 f or project: null:maven-reporting-api:jar:2.0 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven.reporting:maven-reporting:pom:2.0 from the repository. [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0:runtime (sele cted for runtime) [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (selected for runtime ) [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for runt ime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apac he.maven:maven-plugin-registry:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - near er found: 1.1) [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for runtim e) [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] Skipping disabled repository central [DEBUG] maven-scm-manager-plexus: resolved to version 1.0-beta-3-20060330.123807 -1 from repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven.scm:maven-scm-managers::1.0-beta -3-SNAPSHOT for project: null:maven-scm-manager-plexus:jar:1.0-beta-3-20060330.1 23807-1 from the repository. [DEBUG] Skipping disabled repository central [DEBUG] maven-scm-managers: resolved to version 1.0-beta-3-20060330.123807-1 fro m repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven.scm:maven-scm::1.0-beta-3-SNAPSH OT for project: null:maven-scm-managers:pom:1.0-beta-3-SNAPSHOT from the reposit ory. [DEBUG] maven-scm: resolved to version 1.0-beta-3-20060330.123807-1 from reposit ory apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org .apache.maven.s
[jira] Commented: (MNG-2242) mvn command gives a Null Pointer Exception when a plugin is invalid
[ http://jira.codehaus.org/browse/MNG-2242?page=comments#action_70530 ] Todd Nine commented on MNG-2242: I am also receiving this error on a Maven1 plugin. However it has been wrapped with a Maven 2 POM, and it will run at the command line. For instance, if I execute the following command, the plugin runs successfully. mvn clean antlr:generate -Dgrammars=com/ata/util/validator/validwhen/ValidWhenParser.g However if I set up the following plugin maven maven-antlr-plugin 1.2.1 generate generate-sources com/ata/util/validator/validwhen/ValidWhenParser.g I receive a NullPointerException. If I can run the task from the command line, why can't I execute it as a plugin? I would really prefer to have this generated automatically before my compile task runs. Thanks, Todd Todd > mvn command gives a Null Pointer Exception when a plugin is invalid > --- > > Key: MNG-2242 > URL: http://jira.codehaus.org/browse/MNG-2242 > Project: Maven 2 > Issue Type: Bug > Environment: Windows XP, Mavne 2.0.2 >Reporter: Kin Leung > Fix For: 2.1 > > Attachments: pom.xml > > > I tried to use xdoclet with Maven 2.0.2 by adding those lines in pom.xml: > > bookstore-web > > > xdoclet > maven-xdoclet-plugin > 1.2 > > > generate-deployment-decriptor > generate-sources > > > > > >web.xml >src/main/webapp/WEB-INF > > > > webdoclet > > > > > > After I saved the file and run mvn (mvn install and mvn clean), it gives me > Null Pointer Exception: > Downloading: > http://repo1.maven.org/maven2/xdoclet/maven-xdoclet-plugin/1.2/mave > n-xdoclet-plugin-1.2.pom > 159b downloaded > Downloading: > http://repo1.maven.org/maven2/xdoclet/maven-xdoclet-plugin/1.2/mave > n-xdoclet-plugin-1.2.jar > 34K downloaded > [INFO] > - > --- > [ERROR] FATAL ERROR > [INFO] > - > --- > [INFO] null > [INFO] > - > --- > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginM > anager.java:295) > at > org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(De > faultPluginManager.java:200) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlug > inManager.java:165) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa > ultLifecycleExecutor.java:1218) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifec > ycle(DefaultLifecycleExecutor.java:1182) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycl > eMappings(DefaultLifecycleExecutor.java:950) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:450) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:270) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:139) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Meth
[jira] Created: (MANTLR-7) Cannot execute the plugin automatically in a pom
Cannot execute the plugin automatically in a pom Key: MANTLR-7 URL: http://jira.codehaus.org/browse/MANTLR-7 Project: Maven 2.x Antlr Plugin Issue Type: Bug Environment: Windows 2000 JDK 1.4 Reporter: Todd Nine I cannot execute the plugin automatically. Maven 2 configuration maven maven-antlr-plugin 1.2.1 generate generate-sources com/ata/util/validator/validwhen/ValidWhenParser.g C:\appdev\proj\partnership\partnershipBusiness>mvn -e clean compile + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] - --- [INFO] Building Partnership Business Logic [INFO]task-segment: [clean, compile] [INFO] - --- [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:163) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1216) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:982) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) 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.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Jul 24 14:19:41 EDT 2006 [INFO] Final Memory: 1M/3M [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: (MRELEASE-155) Multiproject Release Fails on Windows
Multiproject Release Fails on Windows - Key: MRELEASE-155 URL: http://jira.codehaus.org/browse/MRELEASE-155 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-4 Environment: Windows 2000, Tortoise CVS 1.8.26. Maven 2.0.4, release 2.0-beta 4. Reporter: Todd Nine I am receiving errors when attempting to check in on a multiproject release. Below is my output. As you can see, it is not checking in the parent pom. If I manually execute the command in the output, the parent pom is correctly checked in. Is it possible the first file in the output (which happens to be the parent pom) is not getting added to the arguments when the commit command is executed? [INFO] Checking in modified POMs... [INFO] Executing: cvs -z3 -f -d :ext:[EMAIL PROTECTED]:/a01/proj/CVS -q commit -R -F C:\DOCUME~1\u84172\LOCALS~1\Temp\scm-commit-message27749.txt pom.xml messageDrivenSender/pom.xml messageDrivenPojo/pom.xml messageDrivenDelegate/pom.xml [INFO] Working directory: C:\development\ata\utilities [INFO] Tagging release with the label utilitiesParent-1_0_0... [INFO] Executing: cvs -z3 -f -d :ext:[EMAIL PROTECTED]:/a01/proj/CVS -q tag -F -c utilitiesParent-1_0_0 [INFO] Working directory: C:\development\ata\utilities [WARNING] Unknown status: '? '. [INFO] --- [ERROR] BUILD FAILURE [INFO] --- [INFO] Unable to tag SCM Provider message: The cvs tag command failed. Command output: cvs tag: pom.xml is locally modified cvs [tag aborted]: correct the above errors first! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MRELEASE-94) Modified Parent POM is not commited
[ http://jira.codehaus.org/browse/MRELEASE-94?page=all ] Todd Nine reopened MRELEASE-94: --- I do not believe this is a cvs nt command problem. If I execute the command manually from the command line, it executes correctly. See the linked issue for a better explanation > Modified Parent POM is not commited > --- > > Key: MRELEASE-94 > URL: http://jira.codehaus.org/browse/MRELEASE-94 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-3 > Environment: Windows 2k, or Windows XP. JDK 1.4.2, scpexe=pscp > sshexe=plink cvs=cvs.exe CVS_RSH=plink. Key authentication via pageant >Reporter: Todd Nine > Assigned To: Brett Porter >Priority: Blocker > > I can successfully tag all sub projects of a parent pom (with the standard > directory structure), but I'm unable complete the release:prepare operation > since the parent POM is not checked in. As a result I am unable to perform a > multi-project release. Each child pom has the scm repotisotries declared in > the pom. Attached is verbose output of the command. > mvn -Duser.name=c200506 -X clean release:prepare > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-plugin-parameter-documenter:jar:2.0 from the repository. > [DEBUG] > org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > nearer found: 1.1) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-error-diagnostics:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0:runtime > (selected for runtime)[DEBUG] Retrieving parent-POM: > org.apache.maven:maven::2.0 for project: org.apac > he.maven:maven-monitor:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-monitor:jar:2.0:runtime (selected for > runtime > ) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:mav > en-settings:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for > runtim > e) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] > org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtim > e (selected for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime > (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven:maven-plugin-descriptor:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0:runtime > (selected f > or runtime) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > ru > ntime) > [DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime) > [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5:runtime > (selected f > or runtime) > [DEBUG] com.jcraft:jsch:jar:0.1.23:runtime (selected for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] Retrieving parent-POM: > org.apache.maven.reporting:maven-reporting::2.0 f > or project: null:maven-reporting-api:jar:2.0 from the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven.reporting:maven-reporting:pom:2.0 from the repository. > [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0:runtime > (sele > cted for runtime) > [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (selected for > runtime > ) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > runt > ime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven:maven-plugin-registry:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0:runtime (selected > for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > runtim > e) > [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > nearer > found: 1.1) > [DEBUG] Skipping disabled repository central > [DEBUG] maven-scm-manager-plexus: resolved to version > 1.0-beta-3-20060330.123807 > -1 from repository apache.snapshots > [DEBUG] Retrieving parent-POM: > org.apache.maven.scm:maven-
[jira] Updated: (MRELEASE-94) Modified Parent POM is not commited
[ http://jira.codehaus.org/browse/MRELEASE-94?page=all ] Todd Nine updated MRELEASE-94: -- Attachment: ScmCommitPhase-patch.txt Added capability for users to specify winntcvs to check in each file individually. > Modified Parent POM is not commited > --- > > Key: MRELEASE-94 > URL: http://jira.codehaus.org/browse/MRELEASE-94 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-3 > Environment: Windows 2k, or Windows XP. JDK 1.4.2, scpexe=pscp > sshexe=plink cvs=cvs.exe CVS_RSH=plink. Key authentication via pageant >Reporter: Todd Nine > Assigned To: Brett Porter >Priority: Blocker > Attachments: ScmCommitPhase-patch.txt > > > I can successfully tag all sub projects of a parent pom (with the standard > directory structure), but I'm unable complete the release:prepare operation > since the parent POM is not checked in. As a result I am unable to perform a > multi-project release. Each child pom has the scm repotisotries declared in > the pom. Attached is verbose output of the command. > mvn -Duser.name=c200506 -X clean release:prepare > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-plugin-parameter-documenter:jar:2.0 from the repository. > [DEBUG] > org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > nearer found: 1.1) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-error-diagnostics:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0:runtime > (selected for runtime)[DEBUG] Retrieving parent-POM: > org.apache.maven:maven::2.0 for project: org.apac > he.maven:maven-monitor:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-monitor:jar:2.0:runtime (selected for > runtime > ) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:mav > en-settings:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for > runtim > e) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] > org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtim > e (selected for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime > (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven:maven-plugin-descriptor:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0:runtime > (selected f > or runtime) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > ru > ntime) > [DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime) > [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5:runtime > (selected f > or runtime) > [DEBUG] com.jcraft:jsch:jar:0.1.23:runtime (selected for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] Retrieving parent-POM: > org.apache.maven.reporting:maven-reporting::2.0 f > or project: null:maven-reporting-api:jar:2.0 from the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven.reporting:maven-reporting:pom:2.0 from the repository. > [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0:runtime > (sele > cted for runtime) > [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (selected for > runtime > ) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > runt > ime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven:maven-plugin-registry:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0:runtime (selected > for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > runtim > e) > [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > nearer > found: 1.1) > [DEBUG] Skipping disabled repository central > [DEBUG] maven-scm-manager-plexus: resolved to version > 1.0-beta-3-20060330.123807 > -1 from repository apache.snapshots > [DEBUG] Retrieving parent-POM: > org.apache.maven.scm:maven-scm-managers::1.0-bet
[jira] Updated: (MRELEASE-94) Modified Parent POM is not commited
[ http://jira.codehaus.org/browse/MRELEASE-94?page=all ] Todd Nine updated MRELEASE-94: -- Attachment: ScmCommitPhaseTest-patch.txt Added test case to test the wincvsnt value set to true > Modified Parent POM is not commited > --- > > Key: MRELEASE-94 > URL: http://jira.codehaus.org/browse/MRELEASE-94 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-3 > Environment: Windows 2k, or Windows XP. JDK 1.4.2, scpexe=pscp > sshexe=plink cvs=cvs.exe CVS_RSH=plink. Key authentication via pageant >Reporter: Todd Nine > Assigned To: Brett Porter >Priority: Blocker > Attachments: howto.apt-patch.txt, ScmCommitPhase-patch.txt, > ScmCommitPhaseTest-patch.txt > > > I can successfully tag all sub projects of a parent pom (with the standard > directory structure), but I'm unable complete the release:prepare operation > since the parent POM is not checked in. As a result I am unable to perform a > multi-project release. Each child pom has the scm repotisotries declared in > the pom. Attached is verbose output of the command. > mvn -Duser.name=c200506 -X clean release:prepare > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-plugin-parameter-documenter:jar:2.0 from the repository. > [DEBUG] > org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > nearer found: 1.1) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-error-diagnostics:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0:runtime > (selected for runtime)[DEBUG] Retrieving parent-POM: > org.apache.maven:maven::2.0 for project: org.apac > he.maven:maven-monitor:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-monitor:jar:2.0:runtime (selected for > runtime > ) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:mav > en-settings:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for > runtim > e) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] > org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtim > e (selected for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime > (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven:maven-plugin-descriptor:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0:runtime > (selected f > or runtime) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > ru > ntime) > [DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime) > [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5:runtime > (selected f > or runtime) > [DEBUG] com.jcraft:jsch:jar:0.1.23:runtime (selected for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] Retrieving parent-POM: > org.apache.maven.reporting:maven-reporting::2.0 f > or project: null:maven-reporting-api:jar:2.0 from the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven.reporting:maven-reporting:pom:2.0 from the repository. > [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0:runtime > (sele > cted for runtime) > [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (selected for > runtime > ) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > runt > ime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven:maven-plugin-registry:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0:runtime (selected > for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > runtim > e) > [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > nearer > found: 1.1) > [DEBUG] Skipping disabled repository central > [DEBUG] maven-scm-manager-plexus: resolved to version > 1.0-beta-3-20060330.123807 > -1 from repository apache.snapshots > [DEBUG] Retrieving parent-POM: > org.apache.maven.sc
[jira] Updated: (MRELEASE-94) Modified Parent POM is not commited
[ http://jira.codehaus.org/browse/MRELEASE-94?page=all ] Todd Nine updated MRELEASE-94: -- Attachment: howto.apt-patch.txt Added the documentation on how to configure for winntcvs > Modified Parent POM is not commited > --- > > Key: MRELEASE-94 > URL: http://jira.codehaus.org/browse/MRELEASE-94 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-3 > Environment: Windows 2k, or Windows XP. JDK 1.4.2, scpexe=pscp > sshexe=plink cvs=cvs.exe CVS_RSH=plink. Key authentication via pageant >Reporter: Todd Nine > Assigned To: Brett Porter >Priority: Blocker > Attachments: howto.apt-patch.txt, ScmCommitPhase-patch.txt, > ScmCommitPhaseTest-patch.txt > > > I can successfully tag all sub projects of a parent pom (with the standard > directory structure), but I'm unable complete the release:prepare operation > since the parent POM is not checked in. As a result I am unable to perform a > multi-project release. Each child pom has the scm repotisotries declared in > the pom. Attached is verbose output of the command. > mvn -Duser.name=c200506 -X clean release:prepare > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-plugin-parameter-documenter:jar:2.0 from the repository. > [DEBUG] > org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > nearer found: 1.1) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-error-diagnostics:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0:runtime > (selected for runtime)[DEBUG] Retrieving parent-POM: > org.apache.maven:maven::2.0 for project: org.apac > he.maven:maven-monitor:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-monitor:jar:2.0:runtime (selected for > runtime > ) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:mav > en-settings:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for > runtim > e) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] > org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtim > e (selected for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime > (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven:maven-plugin-descriptor:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0:runtime > (selected f > or runtime) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > ru > ntime) > [DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime) > [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5:runtime > (selected f > or runtime) > [DEBUG] com.jcraft:jsch:jar:0.1.23:runtime (selected for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] Retrieving parent-POM: > org.apache.maven.reporting:maven-reporting::2.0 f > or project: null:maven-reporting-api:jar:2.0 from the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven.reporting:maven-reporting:pom:2.0 from the repository. > [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0:runtime > (sele > cted for runtime) > [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (selected for > runtime > ) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > runt > ime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven:maven-plugin-registry:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0:runtime (selected > for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > runtim > e) > [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > nearer > found: 1.1) > [DEBUG] Skipping disabled repository central > [DEBUG] maven-scm-manager-plexus: resolved to version > 1.0-beta-3-20060330.123807 > -1 from repository apache.snapshots > [DEBUG] Retrieving parent-POM: > org.apache.maven.scm:maven
[jira] Updated: (MRELEASE-41) release:prepare fails when CVS tagging gives a warning
[ http://jira.codehaus.org/browse/MRELEASE-41?page=all ] Todd Nine updated MRELEASE-41: -- Attachment: howto.apt-patch.txt > release:prepare fails when CVS tagging gives a warning > -- > > Key: MRELEASE-41 > URL: http://jira.codehaus.org/browse/MRELEASE-41 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Environment: Maven 2, release plugin version 2.0-beta-3. Scm url is > scm:cvs:ext:[EMAIL PROTECTED]:_CVSROOT_. The host that runs the release is on > Linux and the CVS repository is on Linux. >Reporter: Ørjan Austvold > Assigned To: Brett Porter > Attachments: howto.apt-patch.txt, howto.apt-patch.txt, > ScmCommitPhase-patch.txt, ScmCommitPhaseTest-patch.txt > > > The release:prepare target fails with > [INFO] Tagging release with the label ADMIN_CONSOLE_3_2_8. > [EMAIL PROTECTED]'s password: > Provider message: > The cvs tag command failed. > Command output: > Warning: No xauth data; using fake authentication data for X11 forwarding. > cvs tag: pom.xml is locally modified > Looking through the code it seems like the release fails beacuse the cvs > command returns a status different from successful. -- 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: (MRELEASE-41) release:prepare fails when CVS tagging gives a warning
[ http://jira.codehaus.org/browse/MRELEASE-41?page=all ] Todd Nine updated MRELEASE-41: -- Attachment: ScmCommitPhaseTest-patch.txt ScmCommitPhase-patch.txt howto.apt-patch.txt Updated settings property to be more generic > release:prepare fails when CVS tagging gives a warning > -- > > Key: MRELEASE-41 > URL: http://jira.codehaus.org/browse/MRELEASE-41 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Environment: Maven 2, release plugin version 2.0-beta-3. Scm url is > scm:cvs:ext:[EMAIL PROTECTED]:_CVSROOT_. The host that runs the release is on > Linux and the CVS repository is on Linux. >Reporter: Ørjan Austvold > Assigned To: Brett Porter > Attachments: howto.apt-patch.txt, howto.apt-patch.txt, > ScmCommitPhase-patch.txt, ScmCommitPhaseTest-patch.txt > > > The release:prepare target fails with > [INFO] Tagging release with the label ADMIN_CONSOLE_3_2_8. > [EMAIL PROTECTED]'s password: > Provider message: > The cvs tag command failed. > Command output: > Warning: No xauth data; using fake authentication data for X11 forwarding. > cvs tag: pom.xml is locally modified > Looking through the code it seems like the release fails beacuse the cvs > command returns a status different from successful. -- 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: (MRELEASE-94) Modified Parent POM is not commited
[ http://jira.codehaus.org/browse/MRELEASE-94?page=all ] Todd Nine updated MRELEASE-94: -- Attachment: ScmCommitPhaseTest-patch.txt ScmCommitPhase-patch.txt howto.apt-patch.txt updated settings name to be more generic > Modified Parent POM is not commited > --- > > Key: MRELEASE-94 > URL: http://jira.codehaus.org/browse/MRELEASE-94 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-3 > Environment: Windows 2k, or Windows XP. JDK 1.4.2, scpexe=pscp > sshexe=plink cvs=cvs.exe CVS_RSH=plink. Key authentication via pageant >Reporter: Todd Nine > Assigned To: Brett Porter >Priority: Blocker > Attachments: howto.apt-patch.txt, howto.apt-patch.txt, > ScmCommitPhase-patch.txt, ScmCommitPhase-patch.txt, > ScmCommitPhaseTest-patch.txt, ScmCommitPhaseTest-patch.txt > > > I can successfully tag all sub projects of a parent pom (with the standard > directory structure), but I'm unable complete the release:prepare operation > since the parent POM is not checked in. As a result I am unable to perform a > multi-project release. Each child pom has the scm repotisotries declared in > the pom. Attached is verbose output of the command. > mvn -Duser.name=c200506 -X clean release:prepare > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-plugin-parameter-documenter:jar:2.0 from the repository. > [DEBUG] > org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > nearer found: 1.1) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-error-diagnostics:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0:runtime > (selected for runtime)[DEBUG] Retrieving parent-POM: > org.apache.maven:maven::2.0 for project: org.apac > he.maven:maven-monitor:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-monitor:jar:2.0:runtime (selected for > runtime > ) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:mav > en-settings:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for > runtim > e) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] > org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtim > e (selected for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime > (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven:maven-plugin-descriptor:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0:runtime > (selected f > or runtime) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > ru > ntime) > [DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime) > [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5:runtime > (selected f > or runtime) > [DEBUG] com.jcraft:jsch:jar:0.1.23:runtime (selected for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] Retrieving parent-POM: > org.apache.maven.reporting:maven-reporting::2.0 f > or project: null:maven-reporting-api:jar:2.0 from the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven.reporting:maven-reporting:pom:2.0 from the repository. > [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0:runtime > (sele > cted for runtime) > [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (selected for > runtime > ) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > runt > ime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven:maven-plugin-registry:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0:runtime (selected > for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > runtim > e) > [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > nearer > found: 1.1) > [DEBUG] Skipping disabled repository central > [DEBUG] maven-scm-manager-plexus:
[jira] Commented: (MRELEASE-94) Modified Parent POM is not commited
[ http://jira.codehaus.org/browse/MRELEASE-94?page=comments#action_74419 ] Todd Nine commented on MRELEASE-94: --- Note that the files that are gray are old patches > Modified Parent POM is not commited > --- > > Key: MRELEASE-94 > URL: http://jira.codehaus.org/browse/MRELEASE-94 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-3 > Environment: Windows 2k, or Windows XP. JDK 1.4.2, scpexe=pscp > sshexe=plink cvs=cvs.exe CVS_RSH=plink. Key authentication via pageant >Reporter: Todd Nine > Assigned To: Brett Porter >Priority: Blocker > Attachments: howto.apt-patch.txt, howto.apt-patch.txt, > ScmCommitPhase-patch.txt, ScmCommitPhase-patch.txt, > ScmCommitPhaseTest-patch.txt, ScmCommitPhaseTest-patch.txt > > > I can successfully tag all sub projects of a parent pom (with the standard > directory structure), but I'm unable complete the release:prepare operation > since the parent POM is not checked in. As a result I am unable to perform a > multi-project release. Each child pom has the scm repotisotries declared in > the pom. Attached is verbose output of the command. > mvn -Duser.name=c200506 -X clean release:prepare > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-plugin-parameter-documenter:jar:2.0 from the repository. > [DEBUG] > org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > nearer found: 1.1) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-error-diagnostics:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0:runtime > (selected for runtime)[DEBUG] Retrieving parent-POM: > org.apache.maven:maven::2.0 for project: org.apac > he.maven:maven-monitor:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-monitor:jar:2.0:runtime (selected for > runtime > ) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:mav > en-settings:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for > runtim > e) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] > org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtim > e (selected for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime > (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven:maven-plugin-descriptor:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0:runtime > (selected f > or runtime) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > ru > ntime) > [DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime) > [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5:runtime > (selected f > or runtime) > [DEBUG] com.jcraft:jsch:jar:0.1.23:runtime (selected for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] Retrieving parent-POM: > org.apache.maven.reporting:maven-reporting::2.0 f > or project: null:maven-reporting-api:jar:2.0 from the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven.reporting:maven-reporting:pom:2.0 from the repository. > [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0:runtime > (sele > cted for runtime) > [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (selected for > runtime > ) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > runt > ime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apac > he.maven:maven-plugin-registry:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0:runtime (selected > for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > near > er found: 1.1) > [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for > runtim > e) > [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for > runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - > nearer > found: 1.1) > [DEBUG] Skipping disabled repository central > [DEBUG] maven-scm-manager-plexus: resolved to version > 1.0-beta-3-20060330.123807 > -1 from repository apa
[jira] Created: (WAGONHTTP-13) Allow username and password inputs to http
Allow username and password inputs to http -- Key: WAGONHTTP-13 URL: http://jira.codehaus.org/browse/WAGONHTTP-13 Project: wagon-http Issue Type: Improvement Affects Versions: 1.0-alpha-6 Environment: Any Reporter: Todd Nine Some teams will need repositories available via the web, but will not want their repository publicly available. They can secure their repository with BASIC or DIGEST authentication. I can be configured via settings.xml in the following way. Server settings maven2 maven test01 Profile Repositories true true maven2 Maven repository http://maven.mycompany.com default If the repository Id matches a server id, then the username and password can be used in both basic and digest mode. For digest specs, see the RFC here. http://www.ietf.org/rfc/rfc2617.txt -- 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-190) Offline Mode does not set the plugin in offline
Offline Mode does not set the plugin in offline --- Key: MECLIPSE-190 URL: http://jira.codehaus.org/browse/MECLIPSE-190 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Environment: Windows XP Eclipse 3.2 Reporter: Todd Nine When checking the "Offline" check box in the maven 2 settings, maven does not build offline. This makes it impossible for me to use the maven plug in when I'm on a plane, I obviously have no net connectivity. It does not seem possible to download the dependencies then set the plug in to off line mode. -- 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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105944 ] Todd Nine commented on MJAR-28: --- I'm also experiencing this. We're working on a huge project with about 15 sub projects. This really causes problems with our deployable artifacts. Is there anyone working on it? If not, where would I begin looking to fix this? > Using the jar plugin with addClasspath and snapshots can create manifest > classpath with incorrect jar versions > -- > > Key: MJAR-28 > URL: http://jira.codehaus.org/browse/MJAR-28 > Project: Maven 2.x Jar Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Mark J. Titorenko > Attachments: MJAR-28-patch.txt > > > When the POM contains dependencies to snapshot versions of jars, and snapshot > versions of those jars are downloaded from a remote repository, the name of > the jar contained in the classpath added to the manifest, of the form > artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar > downloaded, which contains version information of the form > artifactID-X.X-MMDD.HHmmss-V.jar. > This does not affect snapshot versions which have been directly installed > into a local repository and have no uploaded version within the remote > repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar > form. -- 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: (MINSTALL-82) Add sha 256 support
Add sha 256 support --- Key: MINSTALL-82 URL: http://jira.codehaus.org/browse/MINSTALL-82 Project: Maven 2.x Install Plugin Issue Type: New Feature Components: install:install Affects Versions: 2.3.1 Reporter: Todd Nine Attachments: sha256.patch Currently no facility for sha 256 exists in the install plugin. Utilities such as chef depend on sha 256 to validate downloaded files. I have added the functionality to the plugin. Node that my 2 plexus classes are not properly loaded and I have hard coded the sha256 implementation. I'm unfamiliar with plexus, but all the classes should be correct to submit to the digest utilities. Thanks, Todd -- 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
