Re: [vote] Release Maven 2.0.3
Don't want to be annoying, but I'd be really happy if anyone could upgrade WAGONSSH-36 to blocker. This is the last big remaining issue for us (and our customers). Nightly site deployments with Continuum are made impossible by this one! +1 I tested it with our full product build and it appears to work well. I would like to see WAGONSSH-36 fixed if possible - the fix is so trivial I don't know why it hasn't been integrated already. I'm also looking forward to the upcoming site and cobertura releases! -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 21, 2006 10:07 PM To: Maven Developers List Subject: [vote] Release Maven 2.0.3 Hi, I think it's time to release Maven 2.0.3. This release will incorporate 21 resolved JIRA issues, including some critical fixes for Continuum and users of the embedder. The full listing of fixes can be found here: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleNa me=Htmlversion=12107 The remaining open issues are reminders for the site publishing process which should accompany this binary release. If you're interested, you can take the current release candidate for a test drive. The RC tarball is at: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-2006 0222.031501.tar.gz I'll leave the vote open for the customary 72 hours before summarizing. Please cast your vote as: [ ] +1 Yes, release [ ] 0 No opinion [ ] -1 No, don't release Here's my +1. Cheers, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel P: +41 61 226 99 63 - F: +41 61 226 99 69 [EMAIL PROTECTED]; http://www.giniality.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release Maven 2.0.3
I usually don't add my 2 cents to this, but I do hope that maven-2.0.3 includes the fix for WAGONSSH-36 (not MNG, I know, but since it comes bundled...). For CI, this is certainly a blocker! Regards, Michael On Wed, 22 Feb 2006, Stephane Nicoll wrote: +1, with 2 comments: 1) no earth shaking fixes.. why not wait a bit longer? 2) it might be nice if 2.0.3 included these: http://jira.codehaus.org/browse/MNG-1317 (mvn.bat doesn't work on win2k/xp) (and possibly this one: http://jira.codehaus.org/browse/MNG-1415 (fix quoted args for *nix) ) -- Kenney +1 On 2/22/06, John Casey [EMAIL PROTECTED] wrote: Hi, I think it's time to release Maven 2.0.3. This release will incorporate 21 resolved JIRA issues, including some critical fixes for Continuum and users of the embedder. The full listing of fixes can be found here: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=12107 The remaining open issues are reminders for the site publishing process which should accompany this binary release. If you're interested, you can take the current release candidate for a test drive. The RC tarball is at: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060222.031501.tar.gz I'll leave the vote open for the customary 72 hours before summarizing. Please cast your vote as: [ ] +1 Yes, release [ ] 0 No opinion [ ] -1 No, don't release Here's my +1. Cheers, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .::You're welcome ::. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel P: +41 61 226 99 63 - F: +41 61 226 99 69 [EMAIL PROTECTED]; http://www.giniality.com/
easymock ibiblio upload: classifier or artifactId?
Hi there, I about to upload easymock-1.2 to ibiblio. There are two versions: one for java1.3, one for java1.5. Do I correctly assume that this is a prime example of using classifiers, or do I have to append the variation to the artifactId? Which one wins: easymock-1.2-java1.3.jar vs. easymock-java1.3-1.2.jar Btw., the maven-install-plugins does not seem to honor the -DpomFile parameter, thus making it impossible to install an artifact using classifiers, since there isn't a -Dclassifier argument available. Is this known or shall I create a feature request? Thanks, Michael -- Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel P: +41 61 226 99 63 - F: +41 61 226 99 69 [EMAIL PROTECTED]; http://www.giniality.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deploying signed releases
Hi Alan , Next time, please write to users@maven.apache.org, this list is for maven development! To use Jar signing, you have to checkout the latest SVN version of the maven-jar-plugin and install it. Then, include this in your POM: project build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId version2.1-SNAPSHOT/version executions execution idjar.sign/id goals goalsign/goal /goals configuration !-- Attach signed artifact -- classifiersigned/classifier /configuration /execution /executions /plugin How, your signed artifacts will be deployed as artifactId-version-signed.jar Simply use signed as classifier in your dependecies-section to use the signed instead of the unsigned version. Regards, Michael How do I do this? Regards, Alan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel P: +41 61 226 99 63 - F: +41 61 226 99 69 [EMAIL PROTECTED]; http://www.giniality.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bug in POM validation when using dependencyManagement
Hi,
I make extensive use of the dependencyManagement section over multiple
POM hierchies.
I have them setup like this:
dependencyManagement
dependencies
dependency
groupId${pom.groupId}/groupId
artifactIdsome-artifact/artifactId
version${some-artifact}/version
/dependency
/dependencies
/dependencyManagement
The actual version is defined in the same POM in the properties
section as e.g. some-artifact1.0-SNAPSHOT/some-artifact (so that I
can define the version of child projects in one central place and use it
in the dependencyManagement at the same time).
When I declare this artifact as dependency in a child POM, I have to add
version${some-artifact}/version, or else it will say
'dependencies.dependency.version' is missing for [...]:
dependency
groupIdorg.dummy/groupId
artifactIdsome-artifact/artifactId
version${some-artifact}/version
/dependency
Of course, version${some-artifact}/version should not be necessary,
as dependencyManagement in a parent pom already defined it.
Executing help:effective-pom shows that the elements in the
dependencyManagement section are correctly populated, including
org.dummy:some-artifact:1.0-SNAPSHOT, so it looks like only the pom
validation is borked, not the actual dependencyManagement implementation.
Is this a known Bug?
Regards,
Michael
--
Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel
P: +41 61 226 99 63 - F: +41 61 226 99 69
[EMAIL PROTECTED]; http://www.giniality.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Bug in maven-site-plugin
Hi, this behaviour seems strange to me: I define the site URL in a parent POM, and for every level I go down in the inheritance hierarchy, each pom adds its artifact-id to the site URL. IMHO, the URL should be used exactly as specified, nothing should be appended to it. I can define my own namespace! This issue may be related to MSITE-72. Me file Jira? Regards, Michael -- Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel P: +41 61 226 99 63 - F: +41 61 226 99 69 [EMAIL PROTECTED]; http://www.giniality.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Current Maven SVN misses build dependency doxia-sink-api-1.0-alpha-7
Hi, just wanted to report that the current Maven SVN doesn't build because it misses the artifact *doxia-sink-api-1.0-alpha-7.jar.* I hope this is the right place to report, as the page building maven 2.0 says: If you have any problems or get any failures during the run, please report them to the Maven Developers List http://maven.apache.org/mail-lists.html.. I got the following repos in my profile: - http://m2.safehaus.org - http://snapshots.maven.codehaus.org/maven2 - http://ibiblio.org/maven2 Regards, Michael -- Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel P: +41 61 226 99 63 - F: +41 61 226 99 69 [EMAIL PROTECTED]; http://www.giniality.com/
Re: [m2] Current Maven SVN misses build dependency doxia-sink-api-1.0-alpha-7
It was definitely not there when I checked 3 hours ago (besides Maven saying so, I manually browsed there and looked, could have been a timeout after all), thats why I had to build the 1.0-alpha-7 myself. Probably just one of those ibiblio mysteries... Sorry for the inconvenience. http://www.ibiblio.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-7/ Are you sure? - Brett Michael Böckling wrote: Hi, just wanted to report that the current Maven SVN doesn't build because it misses the artifact *doxia-sink-api-1.0-alpha-7.jar.* I hope this is the right place to report, as the page building maven 2.0 says: If you have any problems or get any failures during the run, please report them to the Maven Developers List http://maven.apache.org/mail-lists.html.. I got the following repos in my profile: - http://m2.safehaus.org - http://snapshots.maven.codehaus.org/maven2 - http://ibiblio.org/maven2 Regards, Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel P: +41 61 226 99 63 - F: +41 61 226 99 69 [EMAIL PROTECTED]; http://www.giniality.com/
