[jira] Created: (MAVENUPLOAD-2000) Set up rsync for ant-contrib
Set up rsync for ant-contrib Key: MAVENUPLOAD-2000 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2000 Project: maven-upload-requests Issue Type: Bug Reporter: Curt Arnold rsync-ssh request for ant-contrib (cpptasks/1.0b5 is newly released) ant-contrib,[EMAIL PROTECTED]:/home/groups/a/an/ant-contrib/htdocs/m2-repo,rsync_ssh,Curt Arnold,[EMAIL PROTECTED],, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-273) Regression: NullPointerException at end of standalone release:perform
[
http://jira.codehaus.org/browse/MRELEASE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105665
]
Curt Arnold commented on MRELEASE-273:
--
This is also occuring with the log4j releases. I'm able to muddle through by
specifying -Dgoals=test site-deploy assembly:attached deploy to push the NPE
way back until all the essential actions have been accomplished, but it is a
real pain. If you set up your machine to redirect people.apache.org to
localhost (or some other machine under your control), set up
/www/people.apache.org/builds/logging/repo on localhost to act as the staging
repo, and add a server section to your conf/settings.xml like:
server
idlogging.repo/id
usernameUSERNAME for people.apache.org/username
privateKey/home/ubuntu/.ssh/id_rsa/privateKey
passphrase/passphrase
/server
Then you should be able to recreate the NPE by:
mvn release:perform
-DconnectionUrl=scm:svn:https://svn.apache.org/repos/asf/logging/log4j/tags/v1_2_15_rc6
If that doesn't work, try adding a -Dgoals=deploy
Regression: NullPointerException at end of standalone release:perform
---
Key: MRELEASE-273
URL: http://jira.codehaus.org/browse/MRELEASE-273
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-6
Environment: Maven 2.0.7, maven-release-plugin 2.0-alpha-6
Reporter: Max Bowsher
Priority: Blocker
I executed mvn release:perform -DconnectionUrl=scm:svn:... The actual
performing succeeded, but then the plugin failed with a NullPointerException
- it seems that the plugin attempts to unconditionally run code analogous to
mvn release:clean, but this is inappropriate because release:perform is not
supposed to require a project to be able to run.
Output:
{noformat}
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 28 seconds
[INFO] Finished at: Thu Aug 02 12:53:49 BST 2007
[INFO] Final Memory: 13M/23M
[INFO]
[INFO] Cleaning up after release...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[DEBUG] Trace
java.lang.NullPointerException
at
org.apache.maven.shared.release.util.ReleaseUtil.getReleasePom(ReleaseUtil.java:73)
at
org.apache.maven.shared.release.util.ReleaseUtil.getStandardPom(ReleaseUtil.java:61)
at
org.apache.maven.shared.release.phase.AbstractBackupPomsPhase.getPomBackup(AbstractBackupPomsPhase.java:37)
at
org.apache.maven.shared.release.phase.AbstractBackupPomsPhase.deletePomBackup(AbstractBackupPomsPhase.java:51)
at
org.apache.maven.shared.release.phase.CreateBackupPomsPhase.clean(CreateBackupPomsPhase.java:70)
at
org.apache.maven.shared.release.DefaultReleaseManager.clean(DefaultReleaseManager.java:427)
at
org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:324)
at
org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:267)
at
org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:260)
at
org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:102)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
[jira] Created: (MNG-2986) NullPointerException in o.a.m.shared.release.phase.AbstractBackupPomsPhase.getPomBackup
NullPointerException in o.a.m.shared.release.phase.AbstractBackupPomsPhase.getPomBackup --- Key: MNG-2986 URL: http://jira.codehaus.org/browse/MNG-2986 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.6 Environment: Windows 2000 SP4, Sun JDK 1.4.2_18 Reporter: Curt Arnold Got the following stack trace after an apparent successful deploy to a previously empty staging repository: C:\...mvn release:perform -DconnectionUrl=scm:svn:http://svn.apache.org/repos/asf/logging/log4j/tags/v1_2_15_rc2 ... ... ... 1044/1047K 1047/1047K 1047K uploaded [INFO] - --- [INFO] BUILD SUCCESSFUL [INFO] - --- [INFO] Total time: 3 minutes 51 seconds [INFO] Finished at: Wed May 16 17:18:02 CDT 2007 [INFO] Final Memory: 14M/29M [INFO] - --- [INFO] Cleaning up after release... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.shared.release.phase.AbstractBackupPomsPhase.getPomB ackup(AbstractBackupPomsPhase.java:38) at org.apache.maven.shared.release.phase.AbstractBackupPomsPhase.deleteP omBackup(AbstractBackupPomsPhase.java:43) at org.apache.maven.shared.release.phase.CreateBackupPomsPhase.clean(Cre ateBackupPomsPhase.java:69) at org.apache.maven.shared.release.DefaultReleaseManager.clean(DefaultRe leaseManager.java:506) at org.apache.maven.shared.release.DefaultReleaseManager.perform(Default ReleaseManager.java:447) at org.apache.maven.shared.release.DefaultReleaseManager.perform(Default ReleaseManager.java:281) at org.apache.maven.shared.release.DefaultReleaseManager.perform(Default ReleaseManager.java:273) at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformRe leaseMojo.java:96) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone Goal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.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: 4 minutes 33 seconds [INFO] Finished at: Wed May 16 17:18:02 CDT 2007 [INFO] Final Memory: 4M/9M [INFO] C:\prep -- 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-1152) Upload log4j 1.2.14 release
Upload log4j 1.2.14 release --- Key: MAVENUPLOAD-1152 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1152 Project: maven-upload-requests Issue Type: Task Reporter: Curt Arnold Release notice: http://logging.apache.org/site/news.html The pom.xml is an modification of the log4j-1.2.13 pom.xml. Added an xmlns attribute on the project element so that it would pass schema validation. Added mailing lists, scm, issueManagement, inceptionYear, organization elements. An dist-maven target was added to the log4j 1.2 build.xml which repackages the logging-log4j-1.2.14.tar.gz file. log4j-1.2.14.jar is identical to that in the logging-log4j-1.2.14.tar.gz archive. All files in the log4j-1.2.14-sources.jar and log4j-1.2.14-javadoc.jar should be identical to the corresponding file in the logging-log4j-1.2.14.tar.gz file. In future releases the bundle will be created simulatenously with the release. The MD5 checksum for the bundle is MD5(logging-log4j-1.2.14-bundle.jar)= 01b8cd0ad9fd7e2654d30844e84b9dd6 http://www.ibiblio.org/maven/log4j/licenses/ contains ASL 1.1 licenses. ASL 2.0 (http://www.apache.org/licenses/LICENSE-2.0.txt) licenses should be added or replace the ASL 1.1 licenses. Any issues with the pom.xml or the packaging can be added to http://issues.apache.org/bugzilla/show_bug.cgi?id=40604. -- 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-1152) Upload log4j 1.2.14 release
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1152?page=comments#action_75718 ] Curt Arnold commented on MAVENUPLOAD-1152: -- I'll confirm that the initial bundle URL is incorrect and should be http://people.apache.org/builds/logging/log4j/log4j-1.2.14/logging-log4j-1.2.14-bundle.jar . Sorry about that. I had a bad URL at one point but thought that I had fixed it before I submitted the form. Upload log4j 1.2.14 release --- Key: MAVENUPLOAD-1152 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1152 Project: maven-upload-requests Issue Type: Task Reporter: Curt Arnold Release notice: http://logging.apache.org/site/news.html The pom.xml is an modification of the log4j-1.2.13 pom.xml. Added an xmlns attribute on the project element so that it would pass schema validation. Added mailing lists, scm, issueManagement, inceptionYear, organization elements. An dist-maven target was added to the log4j 1.2 build.xml which repackages the logging-log4j-1.2.14.tar.gz file. log4j-1.2.14.jar is identical to that in the logging-log4j-1.2.14.tar.gz archive. All files in the log4j-1.2.14-sources.jar and log4j-1.2.14-javadoc.jar should be identical to the corresponding file in the logging-log4j-1.2.14.tar.gz file. In future releases the bundle will be created simulatenously with the release. The MD5 checksum for the bundle is MD5(logging-log4j-1.2.14-bundle.jar)= 01b8cd0ad9fd7e2654d30844e84b9dd6 http://www.ibiblio.org/maven/log4j/licenses/ contains ASL 1.1 licenses. ASL 2.0 (http://www.apache.org/licenses/LICENSE-2.0.txt) licenses should be added or replace the ASL 1.1 licenses. Any issues with the pom.xml or the packaging can be added to http://issues.apache.org/bugzilla/show_bug.cgi?id=40604. -- 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
