Re: maven-release-plugin release?
Hi Brett, Brett Porter wrote: On 17/09/2010, at 2:23 AM, Jörg Schaible wrote: Hi Baptiste, Baptiste MATHUS wrote: Well, from my understanding, this is not a regression. What Paul says in the end http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment- tabpanel#action_235494is not a workaround, but the right way to go. It *is* a regression with the release plugin, if you cannot release with such a pom. See the first comment. If I understand correctly, it's more that the release plugin doesn't yet understand relativePath/releativePath, which is something new in Maven 3 to represent no relative path for the warning? Yep. That's what the reporter in the first comment said. - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-release-plugin release?
I answered that since I opened the attached test project, and I didn't see any relativePath tag anywhere (though I might have missed it). Cheers 2010/9/17 Jörg Schaible joerg.schai...@gmx.de Hi Brett, Brett Porter wrote: On 17/09/2010, at 2:23 AM, Jörg Schaible wrote: Hi Baptiste, Baptiste MATHUS wrote: Well, from my understanding, this is not a regression. What Paul says in the end http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment- tabpanel#action_235494is not a workaround, but the right way to go. It *is* a regression with the release plugin, if you cannot release with such a pom. See the first comment. If I understand correctly, it's more that the release plugin doesn't yet understand relativePath/releativePath, which is something new in Maven 3 to represent no relative path for the warning? Yep. That's what the reporter in the first comment said. - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: maven-release-plugin release?
Baptiste MATHUS wrote: I answered that since I opened the attached test project, and I didn't see any relativePath tag anywhere (though I might have missed it). The problem is that the author of comment #1 did not open a new issue for the release plugin but used instead this maven issue to report a problem with the proposed solution. However, if a new release of the release plugin is coming, it should work now flawlessly with M3 (resp. the documented migration solutions). - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Bug: profile activation not detected in a parent pom.xml
I have discovered a bug in mvn 2.2.1 in relation to inheritance of profiles. It affects profile inheritance within MavenProject and the maven-help-plugin. 1. The help mojo issue: This appears to be a bug that has been re-introduced into mvn 2.2.1: http://jira.codehaus.org/browse/MPH-16 There is a test file attached to the jira, helptest.zip. The original recursive tree walk appears to have been removed for some reason, or made to depend on mavenProject.getActiveProfiles(). Testing was performed using command line: mvn help:active-profiles 2. This relates to profile information containing repository and build plugins in a parent pom (anywhere in the hierarchy tree). A mvn deploy failed as no distribution repository details were loaded. Reference docs on profiles: http://maven.apache.org/settings.html#Profilesand http://docs.codehaus.org/display/MAVEN/Build+Profiles Would anyone know of a fix or workaround for (2) please? Moving the profile and its build plugins to settings.xml or profiles.xml does not help as the schema does not support the build element beneath profile. The profile's build plugins are a system wide feature for me. Effectively, in my production profile a series of plugins run to integrate details to a wider system, which are not to be executed in my staging and development profiles.
Re: [PLEASE TEST] Apache Maven 3.0-RC1
On 09/15/2010 04:34 PM, Benjamin Bentmann wrote: If you encounter unexpected build issues, please fil[e] a report in JIRA Would be good to take a look at http://jira.codehaus.org/browse/MNG-4428 (server redirect handling) and reconsider its low priority. Although it is claimed to affect 2.2.1 and hence not be a M3 regression, my experience in http://jira.codehaus.org/browse/MNG-4816 is that some bug in M2 masks it under certain circumstances, so that M3 effectively regresses. A patch has been available for over six months with no official comment. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Fwd: archetype-catalog.xml and its properties and goals elements, what populates them?
Hervé BOUTEMY wrote: Forwarding this question to dev list... Yay! I have the attention of the right person at the right time. Hervé BOUTEMY wrote: archetype descriptor [2] should have goals I'll dump related thoughts here: * I like the ability to add goals in archetype descriptor * sometimes certain goals will always have to be executed after an archetype, why not allow it to be done automatically, less instructions for the archetype consumers to follow * It cleanly augments the velocity templating with custom logic * I use one-off Groovy+AntDSL mojos in my highly-specialized archetypes to continue the conversation started by archetype, I need the boost of logic to really add value to the archetype * My follow-up goals have interactivity in CLI, not sure how m2e would handle that in its wizard * the goals need to allow properties (e.g. goaldoit -DmyProperty=true/goal) * goals need to execute in order, currently I don't think order is respected with the catalog descriptor method and somewhat-related: * archetype has some default properties (package, artifactId), which is nice, but it is hard to override and/or not use them, e.g. if I add a package property, it shows up twice in the list displayed to user -- View this message in context: http://maven.40175.n5.nabble.com/Fwd-archetype-catalog-xml-and-its-properties-and-goals-elements-what-populates-them-tp2843289p2843788.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin deployment problems
Any ideas on this one? It's blocking me from releasing the maven-checkstyle-plugin which I'd like to do ASAP. Mark On 16 September 2010 18:44, Mark Hobson markhob...@gmail.com wrote: Hi there, I've been updating my environment to release the Checkstyle plugin and am having problems even deploying a snapshot. I've configured settings.xml as specified [1] but still get: [INFO] Error deploying artifact: Authorization failed: Access denied to: https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-checkstyle-plugin/2.6-SNAPSHOT/maven-checkstyle-plugin-2.6-20100916.173741-5.jar I've used the same credentials that are in my settings.xml for apache.snapshots.https to successfully log into Apache's Nexus. Is there anything I'm missing? Cheers, Mark [1] http://www.apache.org/dev/publishing-maven-artifacts.html#settings - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin deployment problems
We switched over to using LDAP a while back so I don't when you last deployed. You might have to reset your LDAP password. On Sep 17, 2010, at 1:17 PM, Mark Hobson wrote: Any ideas on this one? It's blocking me from releasing the maven-checkstyle-plugin which I'd like to do ASAP. Mark On 16 September 2010 18:44, Mark Hobson markhob...@gmail.com wrote: Hi there, I've been updating my environment to release the Checkstyle plugin and am having problems even deploying a snapshot. I've configured settings.xml as specified [1] but still get: [INFO] Error deploying artifact: Authorization failed: Access denied to: https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-checkstyle-plugin/2.6-SNAPSHOT/maven-checkstyle-plugin-2.6-20100916.173741-5.jar I've used the same credentials that are in my settings.xml for apache.snapshots.https to successfully log into Apache's Nexus. Is there anything I'm missing? Cheers, Mark [1] http://www.apache.org/dev/publishing-maven-artifacts.html#settings - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Three people can keep a secret provided two of them are dead. -- Unknown
Re: Plugin deployment problems
But he could log into the Apache Nexus instance through the UI, so that can't be the case. Mark, are you sure the server id in settings.xml match the id of the repo (e.i. apache.snapshots.https)? Is the password encrypted? /Anders On Fri, Sep 17, 2010 at 19:21, Jason van Zyl ja...@sonatype.com wrote: We switched over to using LDAP a while back so I don't when you last deployed. You might have to reset your LDAP password. On Sep 17, 2010, at 1:17 PM, Mark Hobson wrote: Any ideas on this one? It's blocking me from releasing the maven-checkstyle-plugin which I'd like to do ASAP. Mark On 16 September 2010 18:44, Mark Hobson markhob...@gmail.com wrote: Hi there, I've been updating my environment to release the Checkstyle plugin and am having problems even deploying a snapshot. I've configured settings.xml as specified [1] but still get: [INFO] Error deploying artifact: Authorization failed: Access denied to: https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-checkstyle-plugin/2.6-SNAPSHOT/maven-checkstyle-plugin-2.6-20100916.173741-5.jar I've used the same credentials that are in my settings.xml for apache.snapshots.https to successfully log into Apache's Nexus. Is there anything I'm missing? Cheers, Mark [1] http://www.apache.org/dev/publishing-maven-artifacts.html#settings - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Three people can keep a secret provided two of them are dead. -- Unknown
[RESULT] [VOTE] Release Maven antrun plugin version 1.5
Hi, The vote has passed with the following result: +1 (binding): Paul Gier, Arnaud Héritier, Benjamin Bentmann, Emmanuel Venisse I will promote the artifacts to the central repository and continue with the release. On 09/14/2010 01:19 PM, Paul Gier wrote: Hi, We solved 9 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125version=16504 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11125status=1 Staging repo: https://repository.apache.org/content/repositories/maven-023/ Staging site: http://maven.apache.org/plugins/maven-antrun-plugin-1.5/ SCM Tag: http://svn.apache.org/repos/asf/maven/plugins/tags/maven-antrun-plugin-1.5/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven EJB Plugin version 2.3
+1 2010/9/15 Dennis Lundberg denn...@apache.org: Hi, We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11134styleName=Htmlversion=16518 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11134status=1 Staging repo: https://repository.apache.org/content/repositories/maven-027/ Staging site: http://maven.apache.org/plugins/maven-ejb-plugin-2.3/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Antrun Plugin 1.5 Released
The Maven team is pleased to announce the release of the Maven Antrun
Plugin, version 1.5
This plugin allows Ant tasks to be run within a Maven build. See the
plugin's site for more details:
http://maven.apache.org/plugins/maven-antrun-plugin/
You should specify the version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-XXX-plugin/artifactId
version1.5/version
/plugin
Enjoy,
-The Maven team
Release Notes - Maven 2.x Antrun Plugin - Version 1.5
** Bug
* [MANTRUN-119] - copy task does not respect failonerror=false
* [MANTRUN-140] - project.build.outputDirectory property is invalid
* [MANTRUN-143] - Regression: 1.4 does not resolve
$(settings.localRepository} or ${localRepository}
** Improvement
* [MANTRUN-132] - Allow the antrun plugin to set the namespace for
the built in tasks.
* [MANTRUN-141] - Merge the AbstractAntMojo with the AntRunMojo
* [MANTRUN-142] - Refactor the tasks parameter to simplify
integration with Ant
* [MANTRUN-144] - Debug info being thrown in System.out.println
* [MANTRUN-145] - Rename ITs so that they describe what they test
* [MANTRUN-146] - Some refactoring seems to have broken the plugin
with Maven 3
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin deployment problems
On 17 September 2010 19:41, Anders Hammar and...@hammar.net wrote: But he could log into the Apache Nexus instance through the UI, so that can't be the case. Mark, are you sure the server id in settings.xml match the id of the repo (e.i. apache.snapshots.https)? Is the password encrypted? As sure as I can be as it is encrypted. I can try without encryption just to make sure that isn't causing problems. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin deployment problems
That's what I would do. Start with a simple setup and when that works add the encryption. /Anders On Fri, Sep 17, 2010 at 22:35, Mark Hobson markhob...@gmail.com wrote: On 17 September 2010 19:41, Anders Hammar and...@hammar.net wrote: But he could log into the Apache Nexus instance through the UI, so that can't be the case. Mark, are you sure the server id in settings.xml match the id of the repo (e.i. apache.snapshots.https)? Is the password encrypted? As sure as I can be as it is encrypted. I can try without encryption just to make sure that isn't causing problems. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-release-plugin release?
So... does someone want to open it? :) On 17/09/2010, at 1:07 AM, Jörg Schaible wrote: Baptiste MATHUS wrote: I answered that since I opened the attached test project, and I didn't see any relativePath tag anywhere (though I might have missed it). The problem is that the author of comment #1 did not open a new issue for the release plugin but used instead this maven issue to report a problem with the proposed solution. However, if a new release of the release plugin is coming, it should work now flawlessly with M3 (resp. the documented migration solutions). - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-release-plugin release?
On 17/09/2010, at 1:07 AM, Jörg Schaible wrote: Baptiste MATHUS wrote: I answered that since I opened the attached test project, and I didn't see any relativePath tag anywhere (though I might have missed it). The problem is that the author of comment #1 did not open a new issue for the release plugin but used instead this maven issue to report a problem with the proposed solution. However, if a new release of the release plugin is coming, it should work now flawlessly with M3 (resp. the documented migration solutions). Ok. Would someone familiar with the issue like to open it with the appropriate amount of detail? Thanks, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
