Re: [VOTE] Release Maven Docck Plugin version 1.0
Here's my +1 But we're still one binding vote short... Dennis Lundberg wrote: Hi, We solved 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11361styleName=Htmlversion=13651 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11361status=1 Staging repo: http://people.apache.org/~dennisl/staging-repo/maven-docck-plugin/ Staging site: http://maven.apache.org/plugins/maven-docck-plugin-1.0/ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mercury status and roadmap
Le jeudi 13 novembre 2008, Oleg Gusakov a écrit :
Man, you got me scared s..less today when suddenly all my commits
started failing because of conflicts with SVN :)
:)
As for the mercury-pom - I guess we can move it into the upmost reactor
POM if it's easier to work with it that way. Maybe you can create a jira
for that?
done
http://jira.codehaus.org/browse/MERCURY-34
Thanks a lot!
Oleg
Hervé BOUTEMY wrote:
Le mercredi 12 novembre 2008, Oleg Gusakov a écrit :
inheriting from parent won't add any dependencies to the code. And if
dependencyManagements values don't fit your need, no problem to
override them. I don't see what we loose with this parent, but we win a
lot of things. Or we'll need to improve mercury-pom with configuration
that is missing, copying/pasting from maven-parent when necessary...
Good point about people discovering it though. We need to do something
about it.
I'll add site.xml and work on reporting, if you're ok.
done
this show some little problems with overall modules organization:
- having mercury-pom a sub-module and parent of every other siblings
causes problems in site plugin breadcrumbs and scm url construction
- projects name in pom.xml are not adequate for breadcrumbs: for example
nameMercury Reactor:${project.version}/name
but all in all, site can be published now.
Go for it, that would be awesome.
Thanks for the help!
Oleg
-
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]
Re: [VOTE] Release Maven Docck Plugin version 1.0
+1 Regards, Hervé Le samedi 15 novembre 2008, Dennis Lundberg a écrit : Here's my +1 But we're still one binding vote short... Dennis Lundberg wrote: Hi, We solved 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11361styleNam e=Htmlversion=13651 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11361; status=1 Staging repo: http://people.apache.org/~dennisl/staging-repo/maven-docck-plugin/ Staging site: http://maven.apache.org/plugins/maven-docck-plugin-1.0/ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Version range special cases?
yes, there are special cases hardwired, that were not meant to be weird but
useful features added to Maven Artifact 3.0 :)
see the proposal [1], the current implementation [2] and test-case [3]
the rationale is that snapshot alpha beta milestone release candidate
release service pack
regards,
Hervé
[1] http://docs.codehaus.org/display/MAVEN/Versioning
[2]
http://svn.apache.org/viewvc/maven/artifact/trunk/src/main/java/org/apache/maven/artifact/versioning/ComparableVersion.java?view=markup
[3]
http://svn.apache.org/viewvc/maven/artifact/trunk/src/test/java/org/apache/maven/artifact/versioning/ComparableVersionTest.java?view=markup
Le jeudi 13 novembre 2008, Dave Syer a écrit :
Can anyone explain why the first test succeeds (as expected) but the second
and third fails?
@Test
public void testVanillaVersionRangeExcludesDotQualifier() throws
Exception
{
VersionRange range =
VersionRange.createFromVersionSpec([1.0.0,2.0.0));
assertFalse(range.containsVersion(new
DefaultArtifactVersion(2.0.0.RELEASE)));
}
@Test
public void testVanillaVersionRangeExcludesDotQualifierMilestone()
throws
Exception {
VersionRange range =
VersionRange.createFromVersionSpec([1.0.0,2.0.0));
// Fails even in Maven 3.0
assertFalse(range.containsVersion(new
DefaultArtifactVersion(2.0.0.M1)));
}
@Test
public void
testVanillaVersionRangeExcludesDotQualifierReleaseCandidate()
throws Exception {
VersionRange range =
VersionRange.createFromVersionSpec([1.0.0,2.0.0));
// Fails even in Maven 3.0
assertFalse(range.containsVersion(new
DefaultArtifactVersion(2.0.0.RC1)));
}
It seems like there is some weird special case hard wired to recognise M
and RC as special prefixes (and do the wrong thing with them - as far as
I can see).
This is with 3.0-alpha-2-SNAPSHOT version of maven-artifact.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [2.0.10 RC] Please test
Hi Brian, Brian E. Fox wrote: The version is correct but it does seem to have the wrong embedded version. There must be a property in the pom that the release plugin didn't update. On the wagon-ssh, I'm not having issues, can you give more info on how to reproduce it? Sure. It's an open source project. You can find the pom.xml here [1] and the project source here [2]. If you change the version of wagon-ssh to 1.0-beta-4 or remove the version tag, it doesn't work. Following is the snippet of my settings.xml with the server connection data. server idwebobjects.mdimension.com/dist/snapshots/id usernamemyusername/username password![CDATA[***]]/password /server Does 2.1M1 work for you? (I ported back the exact fix from that branch) I've tried it again and it didn't work too. :( On both versions (2.1-M1 and 2.0.10-RC3), it only work with wagon-ssh-1.0-beta-2. I don't know why it have worked the first time. As I've cleaned my local repo, I can't reproduce the same environment I had at that time. :( [1]https://svn.objectstyle.org/repos/woproject/trunk/woproject/pom.xml [2]https://svn.objectstyle.org/repos/woproject/trunk/woproject/ Cheers, Henrique -Original Message- From: Henrique Prange [mailto:[EMAIL PROTECTED] Sent: Friday, November 14, 2008 5:04 PM To: Maven Users List Cc: dev@maven.apache.org Subject: Re: [2.0.10 RC] Please test Hi Brian, I've tried the RC3 but it seems to be the old RC2. I've downloaded distinct packages (tar.gz and zip) on different browsers (Safari and Firefox) to avoid any cache problems. :( Following is the mvn -v output: Maven version: 2.0.10-RC2 Java version: 1.5.0_16 OS name: mac os x version: 10.5.5 arch: i386 Family: unix I've tested anyway and the wagon-ssh issue is still there. Are you sure the staged version is the right one? Cheers, Henrique Brian Fox wrote: Hello, This RC fixes the SCP wagon problem identified in RC2 (MNG-3717). No other issues where identified in RC2 so hopefully this will become the last RC. Here's the list of issues fixed in 2.0.10: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112styleName =HtmlprojectId=10500Create=Create And I've staged RC-3 here: http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa che-maven/2.0.10-RC3/ Please try it out and see if we have any remaining regressions over 2.0.9. Thanks, Brian -- Brian Fox Apache Maven PMC http://blogs.sonatype.com/people/brian/ - 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] - 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]
Re: Mercury status and roadmap
The webdav server which is currently a plexus component is here: https://svn.sonatype.org/spice/trunk/plexus-webdav It should probably be renamed as it's a server not a client implementation. On 14-Nov-08, at 9:55 PM, Oleg Gusakov wrote: I added it to http://jira.codehaus.org/browse/MERCURY-25 Will definitely try it. Thanks Stephen! Stephen Connolly wrote: There's also http://milton.ettrema.com/index.html Which is using the ASLv2 license. I have not used it myself, but it's looking tempting for some stuff I want to do (unless Jason wants to show me where his one is ;-) ) -Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [2.0.10 RC] Please test
Le samedi 15 novembre 2008, Henrique Prange a écrit : Hi Brian, Brian E. Fox wrote: The version is correct but it does seem to have the wrong embedded version. There must be a property in the pom that the release plugin didn't update. yes, the release plugin din't update mavenVersion property when preparing 2.0.10-RC3-SNAPSHOT (see r709065). I fixed the pom for the actual RC4-SNAPSHOT version, but too late for RC3: it contains RC2 Maven components regards, Hervé - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
