[jira] (MRELEASE-797) support semantic versioning
Matthew Daniel created MRELEASE-797:
---
Summary: support semantic versioning
Key: MRELEASE-797
URL: https://jira.codehaus.org/browse/MRELEASE-797
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Components: update-versions
Affects Versions: 2.3.2
Environment: Maven 3.0.4
Reporter: Matthew Daniel
Priority: Minor
When a project is using [semantic versioning|http://semver.org/], the
maven-release-plugin will only increment the right-most version identifier
(which corresponds to a patch release in semver terminology). It would be
helpful if the maven-release-plugin understood the 3 normal release severities:
major, minor and patch.
Current behavior:
# Given a {{pom.xml}} with version {{1.0.50-SNAPSHOT}}
# When the user executes {{mvn release:update-versions -Dsemver=major}} (as a
hypothetical syntax)
# Then observe that {{pom.xml}} contains {{1.0.51-SNAPSHOT}}, not
{{2.0.0-SNAPSHOT}} as a major release would dictate
Expected behavior:
# Given a pom version in {{X.Y.Z}} format
# When one indicates the desired semantic version release level to
maven-release-plugin
# Then maven-release-plugin increments {{X.Y.Z}} according to the user's
indicated release level
It would be an error condition for the user to request a semantic version
release level when the pom's version is not in {{X.Y.Z}} format (plus any
miscellaneous trailing text as specified in rules 10, 11 or 12 of the semver
specification).
It is currently possible to work around this via manual construction of a
{{release.properties}} file, but that requires a 2 step build process: run the
script then run the Maven targets. Further, one would expect that all Maven
projects that use semantic versioning would need to implement their own
pre-release scripts, which is wasteful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4818) NPE in legacy.DefaultWagonManager.getArtifact
[ http://jira.codehaus.org/browse/MNG-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235798#action_235798 ] Matthew Daniel commented on MNG-4818: - My sincere apologies, it appears that I left out -DdownloadSources=true from step 3. The good(?) news is that yes, I experience this on 3.0-RC1 also. Just for clarity, I'll repeat the correct reproduction steps: 1. mkdir \tmp\foo 2. cd \tmp\foo 3. mvn -DgroupId=my.group -DartifactId=myart -Dpackage=com.example.foo -Dpackaging=jar archetype:create 4. cd myart 5. edit pom.xml and add dependency (org.apache.commons:commons-jexl:2.0.1:jar) with no scope 6. rmdir /s /q %M2_LOCAL_REPO%\org\apache\commons\commons-jexl 7. mvn -e -DdownloadSources=true idea:idea NPE in legacy.DefaultWagonManager.getArtifact - Key: MNG-4818 URL: http://jira.codehaus.org/browse/MNG-4818 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0 Environment: At revision 998131; 1.6.0_21 (32-bit); win7ent-x64 Reporter: Matthew Daniel Attachments: bug.log 1. mvn archetype:create (with your favorite -DgroupId etc) 2. add some non-local dependency to the pom (I used commons-jexl:2.0.1) 3. mvn idea:idea 4. kaboom The problem is that the Logger is declared as @Requirement but it is evidently not being provided (any path leading to a logging statement yields the NPE) I regret that I don't know enough plexus-voodoo to even create a TestCase for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4818) NPE in legacy.DefaultWagonManager.getArtifact
[ http://jira.codehaus.org/browse/MNG-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235759#action_235759 ] Matthew Daniel commented on MNG-4818: - I was using a clean build of Maven-3 out of Subversion, yes, but I will be glad to test it with 3.0-RC1 and see what happens. I'll do that tomorrow, since my work machine has all the toys on it. NPE in legacy.DefaultWagonManager.getArtifact - Key: MNG-4818 URL: http://jira.codehaus.org/browse/MNG-4818 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0 Environment: At revision 998131; 1.6.0_21 (32-bit); win7ent-x64 Reporter: Matthew Daniel Attachments: bug.log 1. mvn archetype:create (with your favorite -DgroupId etc) 2. add some non-local dependency to the pom (I used commons-jexl:2.0.1) 3. mvn idea:idea 4. kaboom The problem is that the Logger is declared as @Requirement but it is evidently not being provided (any path leading to a logging statement yields the NPE) I regret that I don't know enough plexus-voodoo to even create a TestCase for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4818) NPE in legacy.DefaultWagonManager.getArtifact
NPE in legacy.DefaultWagonManager.getArtifact - Key: MNG-4818 URL: http://jira.codehaus.org/browse/MNG-4818 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0 Environment: At revision 998131; 1.6.0_21 (32-bit); win7ent-x64 Reporter: Matthew Daniel Attachments: bug.log 1. mvn archetype:create (with your favorite -DgroupId etc) 2. add some non-local dependency to the pom (I used commons-jexl:2.0.1) 3. mvn idea:idea 4. kaboom The problem is that the Logger is declared as @Requirement but it is evidently not being provided (any path leading to a logging statement yields the NPE) I regret that I don't know enough plexus-voodoo to even create a TestCase for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WAGONHTTP-8) wagon-http does not MKCOL for missing parent resources during deploy
[ http://jira.codehaus.org/browse/WAGONHTTP-8?page=comments#action_66836 ]
Matthew Daniel commented on WAGONHTTP-8:
{quote}
Confirm lack of MKCOL issue, tested on Fedora Core 5/Apache2.2 DAV w/ wagon
1.0-alpha-6.
{quote}
Oh, sorry, I saw lack of issue and thought you were confirming that I was
crazy. :-)
That code snippet (at least at a cursory glance) looks like it would do the
job, but it can't do that with an existing URI (at least according to section
8.3.1 of RFC 2518). There is one school of thought that says try to PUT the
artifact, and *check the damn response code*. If it needs a MKCOL, try the
whole URI and *check the damn response code* for 409 and the walk the URI like
you suggested. Oh, and while walking the URI, maybe the code should check the
response code from time to time.
That part about access denided really raises my blood pressure because it's
not just wrong, it's misleading.
wagon-http does not MKCOL for missing parent resources during deploy
Key: WAGONHTTP-8
URL: http://jira.codehaus.org/browse/WAGONHTTP-8
Project: wagon-http
Type: Bug
Versions: 1.0-alpha-6
Environment: Linux/x86_64, FC4, jdk 1.5.0_06-b05, mvn 2.0.2, against
Apache/2.0.54 (Fedora) DAV/2
Reporter: Matthew Daniel
Priority: Blocker
Please see MNG-1580 and
When trying to deploy using wagon-http, it does not understand the concept of
parent directories and just issues a blind PUT with the resource URI. Further
to the user's confusion, it does not report a helpful message but Access
denided which is 100% not true.
{quote}
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
artifactat
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error deploying
artifact
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:160)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
... 16 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException:
Error deploying artifact: Authorization failed: Access denided to:
http://servername/path/to/a/non-existant/1.5-SNAPSHOT/artifactid-1.5-20060209.202937-1.jar
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:91)
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:148)
... 18 more
Caused by: org.apache.maven.wagon.TransferFailedException: Authorization
failed: Access denided to:
http://servername/path/to/a/non-existant/1.5-SNAPSHOT/artifactid-1.5-20060209.202937-1.jar
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:215)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77)
... 19 more
Caused by: org.apache.maven.wagon.authorization.AuthorizationException:
Access denided to:
http://servername/path/to/a/non-existant/1.5-SNAPSHOT/artifactid-1.5-20060209.202937-1.jar
