need filesystem-level operations in assembly plugin
Hi all - I'm using maven-assembly-plugin to create zip distributions of our web application. It takes in the Apache Tomcat zip artifact, and the war artifact for the app, and creates an assembly. There are a couple of file operations I haven't figured out how to do yet. For example, Tomcat unzips to a folder called "apache-tomcat-7.0.42", which I want to rename to just "tomcat". I figured id use the exec plugin to fork a "rm" command, which I guess will work in theory but seems shoddy. Does anyone support having some "swiss army knife" file manipulation capabilities (at least rename & move) in the assembly plugin? Best regards, Richard - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
here is current state: - using github link does fix web access in modules problems: see actual 3.1.1staging [1] - with MPIR-291, branches and tags are supported: "git clone --branch " instructions are generated - with MPIR-290, I did a hack to remove module path from git clone instructions with these enhancements, I think git in reports is consistent now: no more non-working instructions generated What is still missing IMHO is: - git scm transform rule during release to modify web access link - update in scm component scm:git: format to support module path at end, to replace MPIR-290 hack with something better designed any other idea? anybody to work on some of the remaining points? Regards, Hervé [1] http://maven.apache.org/ref/3-LATEST/maven-core/source-repository.html Le lundi 2 septembre 2013 20:13:42 Robert Scholte a écrit : > Op Mon, 02 Sep 2013 07:13:27 +0200 schreef Chris Graham > > : > > On Sun, Sep 1, 2013 at 8:21 PM, Hervé BOUTEMY > > > > wrote: > >> if I read Jazz SCM url format [1], in a multi-module build, scm info > >> automatically calculated from root to modules (ie appending artifact-id) > >> will > >> give wrong scm info, no? > >> did you try it? > > > > All of my testing was for multi module projects. Nested ones. So it was > > never a problem. > > > > There is an ugly work around/hack (that automatically happens) for > > non-nest > > projects. So add a dummy path to the end of the Component name, and it > > seems to work out. > > > > As the SCM section is only in the root pom, it does not seem to be > > effected. > > > > A tag (in maven SCM terms) is the equivalent of a snapshot of a component > > (in Jazz SCM terms). Technically, it is a collection of Change Sets, but > > effectively works out to be a "tag" for a given component. > > > > So I think of all modules as a part of the same component (just like all > > modules under a trank/branch in svn). so it tends to work nicely. > > > >> there are 2 other parts: > >> - m-release-p: did you add any logic to deal with plugin scm info > >> modification > >> when tagging a version? > > > > I didn't, but I think that Robert had to add some logic in there that > > applied to Jazz (and I think some others as well). I'd have to go back > > and > > look. > > Indeed, there are several ScmTranslator implementations, see > http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/sr > c/main/java/org/apache/maven/shared/release/scm/ It's still a dream to > remove any scm implementation specific code from this project... > > Robert > > >> - m-pir-p: when you do a checkout (or clone, or view, I don't know the > >> exact > >> term for Jazz), IIUC, you get a repository copy: did you write some > >> instructions in the generated page to cd to module base directory? > >> (again > >> for > >> multi-module builds) > > > > You're the first to ask about this. > > > > I just quickly run a site build, and the generated URL's in the Source > > Repository pages are wrong, as they assume the ability to check out just > > one module of a multi module project (eg SVN terms, a svn checkout of > > .../trunk/Module). This shows the CVS/SVN embedded thinking that is > > pretty > > much implicit across much of the SCM and Release modules. > > > > I do not believe that it is possible to check out (via the command line, > > I > > think that you _may_ be able to via the GUI) one sub dir (ie Module) of a > > Jazz SCM Component. > > > > A checkout in Jazz SCM terms is a "Load". :-) > > > > See: > > > > http://maven.apache.org/scm/maven-scm-providers/maven-scm-provider-jazz/in > > dex.html > > > > > > [1] http://maven.apache.org/scm/jazz.html > > > >> Le dimanche 1 septembre 2013 09:54:39 Chris Graham a écrit : > >> > I did something similar in the Jazz provider. It's a complex URL, or > >> > >> can > >> be > >> > >> > if it needs to be, but it's still a single line. > >> > > >> > It's just a matter of making the parser smarted. And that's local to > >> > >> the > >> > >> > provider, so go nuts. I also put lots of unit tests in there to > >> > >> illustrate > >> > >> > the correct and incorrect usage. > >> > > >> > -Chris > >> > > >> > On Fri, Aug 30, 2013 at 6:33 AM, Hervé BOUTEMY >> > > >> >wrote: > >> > > Le samedi 24 août 2013 23:08:05 Robert Scholte a écrit : > >> > > > I agree that a single SCM line doesn't really match anymore with > >> > >> systems > >> > >> > > > like DSCM (git, Mercurial) > >> > > > It would have been better if we could think of a better way to > >> > >> define > >> > >> > > this > >> > > > >> > > > in a newer POM-model. > >> > > > >> > > it was overkill at the time Maven was done, and even today, > >> > >> splitting > >> scm > >> > >> > > developerConnection into 3 parts seems overkill for classical SCMs, > >> > >> even > >> > >> > > if > >> > > doable > >> > > > >> > > notice that even with "single SCM line", we can have multiple > >> > >> fields, > >> like > >> > >> > > we
Re: [VOTE] Release Maven 3.1.1
What do you think happened? Is this a change in the remote resources plugin? On Sep 10, 2013, at 11:33 AM, Daniel Kulp wrote: > > -1 > > The src.tar.gz and src.zip files have lost their top level NOTICE and LICENSE > files. This is a regression from 3.1.0 (and 3.0.5). That definitely needs > to be fixed. I don't have time today to look into that, but might tomorrow > if someone doesn't beat me to it. > > Ran a couple builds with the result of building the source and things look OK. > > I checked the rest of the contents with the tag and everything looks OK. > There are three files in the git repo that aren't part of the release > (/.gitignore, /.gitattributes, and /apache-maven/src/bin/.gitattributes), but > those files really are specific to our scm and thus don't need to be in the > source release. > > Most likely, the doap_Maven.rdf shouldn't be part of the release either. > Probalby shouldn't be in the main maven git repo. Definitely not a big deal. > > Dan > > > > On Sep 8, 2013, at 9:07 AM, Jason van Zyl wrote: > >> Hi, >> >> Here is a link to Jira with 6 issues resolved: >> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-016/ >> >> The distributable binaries and sources for testing can be found here: >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ >> >> Specifically the zip, tarball, and source archives can be found here: >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz >> >> Vote open for 72 hours. >> >> [ ] +1 >> [ ] +0 >> [ ] -1 >> >> Thanks, >> >> The Maven Team >> >> >> >> >> >> >> > > -- > Daniel Kulp > dk...@apache.org - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > > > - > 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 -
[ANN] Apache Maven Install Plugin 2.5 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Install Plugin, version 2.5 The Install Plugin is used during the install phase to add artifact(s) to the local repository. http://maven.apache.org/plugins/maven-install-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-install-plugin 2.5 Release Notes - Apache Maven Install Plugin - Version 2.5 ** Bug * [MINSTALL-92] - Docs says the skip param is required, which it isn't ** Improvement * [MINSTALL-39] - Maven Install Plugin always copy the artifact in the repository, even if there was no changes * [MINSTALL-90] - use last plexus-utils 3.0.7 which is faster on copying files. * [MINSTALL-95] - Enhance documentation of install-file ** New Feature * [MINSTALL-52] - install:install-file should default to a pom file found in the jar if available * [MINSTALL-93] - Add installAtEnd option for multimodule projects Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.1.1
On 10 September 2013 17:16, sebb wrote: > On 10 September 2013 16:33, Daniel Kulp wrote: > > > > -1 > > > > The src.tar.gz and src.zip files have lost their top level NOTICE and > LICENSE files. This is a regression from 3.1.0 (and 3.0.5). That > definitely needs to be fixed. I don't have time today to look into that, > but might tomorrow if someone doesn't beat me to it. > > > > Ran a couple builds with the result of building the source and things > look OK. > > > > I checked the rest of the contents with the tag and everything looks OK. >There are three files in the git repo that aren't part of the release > (/.gitignore, /.gitattributes, and /apache-maven/src/bin/.gitattributes), > but those files really are specific to our scm and thus don't need to be in > the source release. > > OK, so is it necessary to check the release against the tag? > Or is that just your personal take on what a reviewer should do? > > If it is necessary (for at least one reviewer) to do, then the SCM > coordinates need to be provided in a transparent manner so any > reviewer can do it, and the coordinates need to be part of the vote > e-mail "for the public record". > The source bundle contains the root pom which contains the SCM coordinates. The email contains the hash of the source bundle, and the source bundle is what we release. In this PMC's opinion there is no need to add more information to the email. > > > Most likely, the doap_Maven.rdf shouldn't be part of the release either. > Probalby shouldn't be in the main maven git repo. Definitely not a big > deal. > > > > Dan > > > > > > > > On Sep 8, 2013, at 9:07 AM, Jason van Zyl wrote: > > > >> Hi, > >> > >> Here is a link to Jira with 6 issues resolved: > >> > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 > >> > >> Staging repo: > >> https://repository.apache.org/content/repositories/maven-016/ > >> > >> The distributable binaries and sources for testing can be found here: > >> > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ > >> > >> Specifically the zip, tarball, and source archives can be found here: > >> > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip > >> > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz > >> > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip > >> > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz > >> > >> Vote open for 72 hours. > >> > >> [ ] +1 > >> [ ] +0 > >> [ ] -1 > >> > >> Thanks, > >> > >> The Maven Team > >> > >> > >> > >> > >> > >> > >> > > > > -- > > Daniel Kulp > > dk...@apache.org - http://dankulp.com/blog > > Talend Community Coder - http://coders.talend.com > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Release Maven 3.1.1
On Sep 10, 2013, at 12:16 PM, sebb wrote: > On 10 September 2013 16:33, Daniel Kulp wrote: >> >> -1 >> >> The src.tar.gz and src.zip files have lost their top level NOTICE and >> LICENSE files. This is a regression from 3.1.0 (and 3.0.5). That >> definitely needs to be fixed. I don't have time today to look into that, >> but might tomorrow if someone doesn't beat me to it. >> >> Ran a couple builds with the result of building the source and things look >> OK. >> >> I checked the rest of the contents with the tag and everything looks OK. >> There are three files in the git repo that aren't part of the release >> (/.gitignore, /.gitattributes, and /apache-maven/src/bin/.gitattributes), >> but those files really are specific to our scm and thus don't need to be in >> the source release. > > OK, so is it necessary to check the release against the tag? That's one way, sure. Personally, I log the trunk/master/branch, find the appropriate commit for "prepare release maven-3.1.1", check that out, then diff that with the src tar ball as well as diff that with the tag to make sure all three match up. Likely not necessary with git where the tag would apply directly to that commit, but with subversion, it is certainly possible that the three don't match and the diffs make sure to check that.If any of the three diffs find differences, it's an immediate red-flag for further review and likely require a -1 on the vote until resolved. > Or is that just your personal take on what a reviewer should do? A reviewer should do whatever they feel is necessary to do a thorough review. > If it is necessary (for at least one reviewer) to do, then the SCM > coordinates need to be provided in a transparent manner so any > reviewer can do it, and the coordinates need to be part of the vote > e-mail "for the public record". No, each reviewer should do what they feel is appropriate for them. If every reviewer did the exact same thing, we'd get the exact same result from each of them. Some reviewers may checkout the tag, others may troll back master, others may do something completely different. -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.1.1
On Sep 10, 2013, at 12:04 PM, Jason van Zyl wrote: > What do you think happened? Is this a change in the remote resources plugin? No…. in the old releases, they were named LICENSE.txt and NOTICE.txt (txt extension) which is not how the RR plugin would have ever generated them. This is a source archive and thus the generated LICENSE/NOTICE is likely not applicable (as that would have information about the binary jars and such that aren't included in the source archive). Dan > > On Sep 10, 2013, at 11:33 AM, Daniel Kulp wrote: > >> >> -1 >> >> The src.tar.gz and src.zip files have lost their top level NOTICE and >> LICENSE files. This is a regression from 3.1.0 (and 3.0.5). That >> definitely needs to be fixed. I don't have time today to look into that, >> but might tomorrow if someone doesn't beat me to it. >> >> Ran a couple builds with the result of building the source and things look >> OK. >> >> I checked the rest of the contents with the tag and everything looks OK. >> There are three files in the git repo that aren't part of the release >> (/.gitignore, /.gitattributes, and /apache-maven/src/bin/.gitattributes), >> but those files really are specific to our scm and thus don't need to be in >> the source release. >> >> Most likely, the doap_Maven.rdf shouldn't be part of the release either. >> Probalby shouldn't be in the main maven git repo. Definitely not a big >> deal. >> >> Dan >> >> >> >> On Sep 8, 2013, at 9:07 AM, Jason van Zyl wrote: >> >>> Hi, >>> >>> Here is a link to Jira with 6 issues resolved: >>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 >>> >>> Staging repo: >>> https://repository.apache.org/content/repositories/maven-016/ >>> >>> The distributable binaries and sources for testing can be found here: >>> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ >>> >>> Specifically the zip, tarball, and source archives can be found here: >>> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip >>> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz >>> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip >>> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz >>> >>> Vote open for 72 hours. >>> >>> [ ] +1 >>> [ ] +0 >>> [ ] -1 >>> >>> Thanks, >>> >>> The Maven Team >>> >>> >>> >>> >>> >>> >>> >> >> -- >> Daniel Kulp >> dk...@apache.org - http://dankulp.com/blog >> Talend Community Coder - http://coders.talend.com >> >> >> - >> 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 > - > > > > > > > -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.1.1
On Sun, 8 Sep 2013 09:07:33 -0400 Jason van Zyl wrote: +1 (none-binding) works fine for some mojo projects + nuiton.org and chorem.org projects. thanks, tony. > Hi, > > Here is a link to Jira with 6 issues resolved: > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 > > Staging repo: > https://repository.apache.org/content/repositories/maven-016/ > > The distributable binaries and sources for testing can be found here: > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ > > Specifically the zip, tarball, and source archives can be found here: > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > Thanks, > > The Maven Team > > > > > > > -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.1.1
-1 The src.tar.gz and src.zip files have lost their top level NOTICE and LICENSE files. This is a regression from 3.1.0 (and 3.0.5). That definitely needs to be fixed. I don't have time today to look into that, but might tomorrow if someone doesn't beat me to it. Ran a couple builds with the result of building the source and things look OK. I checked the rest of the contents with the tag and everything looks OK. There are three files in the git repo that aren't part of the release (/.gitignore, /.gitattributes, and /apache-maven/src/bin/.gitattributes), but those files really are specific to our scm and thus don't need to be in the source release. Most likely, the doap_Maven.rdf shouldn't be part of the release either. Probalby shouldn't be in the main maven git repo. Definitely not a big deal. Dan On Sep 8, 2013, at 9:07 AM, Jason van Zyl wrote: > Hi, > > Here is a link to Jira with 6 issues resolved: > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 > > Staging repo: > https://repository.apache.org/content/repositories/maven-016/ > > The distributable binaries and sources for testing can be found here: > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ > > Specifically the zip, tarball, and source archives can be found here: > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > Thanks, > > The Maven Team > > > > > > > -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.1.1
On 10 September 2013 16:33, Daniel Kulp wrote: > > -1 > > The src.tar.gz and src.zip files have lost their top level NOTICE and LICENSE > files. This is a regression from 3.1.0 (and 3.0.5). That definitely needs > to be fixed. I don't have time today to look into that, but might tomorrow > if someone doesn't beat me to it. > > Ran a couple builds with the result of building the source and things look OK. > > I checked the rest of the contents with the tag and everything looks OK. > There are three files in the git repo that aren't part of the release > (/.gitignore, /.gitattributes, and /apache-maven/src/bin/.gitattributes), but > those files really are specific to our scm and thus don't need to be in the > source release. OK, so is it necessary to check the release against the tag? Or is that just your personal take on what a reviewer should do? If it is necessary (for at least one reviewer) to do, then the SCM coordinates need to be provided in a transparent manner so any reviewer can do it, and the coordinates need to be part of the vote e-mail "for the public record". > Most likely, the doap_Maven.rdf shouldn't be part of the release either. > Probalby shouldn't be in the main maven git repo. Definitely not a big deal. > > Dan > > > > On Sep 8, 2013, at 9:07 AM, Jason van Zyl wrote: > >> Hi, >> >> Here is a link to Jira with 6 issues resolved: >> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-016/ >> >> The distributable binaries and sources for testing can be found here: >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ >> >> Specifically the zip, tarball, and source archives can be found here: >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz >> >> Vote open for 72 hours. >> >> [ ] +1 >> [ ] +0 >> [ ] -1 >> >> Thanks, >> >> The Maven Team >> >> >> >> >> >> >> > > -- > Daniel Kulp > dk...@apache.org - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.1.1
On Sep 10, 2013, at 10:11 AM, Jason van Zyl wrote: > > On Sep 10, 2013, at 9:58 AM, sebb wrote: > >> Which as I have argued all along is insufficient. >> - the vote email does not have vital information "for the record" >> - indeed in the case of this vote, neither the vote e-mail nor the >> source archive (on which people are supposed to be voting) has the >> information. >> >> I note that no-one who has voted so far has stated that the contents >> of the source archives are all present and correct and that no files >> are missing from the release and more importantly that there are no >> files in the source archive that should not be there. >> >> IMO this is the most important part of the release vote, along with >> the N&L contents. > > Get the PMC to agree and put it in the template and I'll use what's in the > template. > Which the PMC has already discussed and decided it was not needed. Sebb's opinion on this is respected, but it's still not something we, as the PMC, feel is required. The commits list is monitored If Sebb feels that strongly about it, he can take it up with the board or something, but for the purpose of this community, it's not something that is required. -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.1.1
On 10 September 2013 15:11, Jason van Zyl wrote: > > On Sep 10, 2013, at 9:58 AM, sebb wrote: > >> On 10 September 2013 14:23, Jason van Zyl wrote: >>> >>> On Sep 10, 2013, at 7:53 AM, sebb wrote: >>> I've just realised that you said the hash is in the maven core jar. That is a binary artifact, and has no direct relationship with the source artifact on which people are supposed to be voting. >>> >>> It is supposed to be the SHA1 of the release from which the build was made. >>> I don't think it's possible to tie the SCM tag to this vote thread "for the record" without the hash (and git repo) being provided in this e-mail. >>> >>> Well, I'm going to leave it out for now. I'll do what's strictly in the >>> template here: >>> >>> http://maven.apache.org/developers/release/maven-project-release-procedure.html#Call_the_vote >> >> Which as I have argued all along is insufficient. >> - the vote email does not have vital information "for the record" >> - indeed in the case of this vote, neither the vote e-mail nor the >> source archive (on which people are supposed to be voting) has the >> information. >> >> I note that no-one who has voted so far has stated that the contents >> of the source archives are all present and correct and that no files >> are missing from the release and more importantly that there are no >> files in the source archive that should not be there. >> >> IMO this is the most important part of the release vote, along with >> the N&L contents. > > Get the PMC to agree and put it in the template and I'll use what's in the > template. > >> >>> Also, I don't think the quoted hash is correct. >>> >>> It doesn't look correct, it appears to take the parent commit. This has >>> probably been >>> the case for quite some time, in that the "mvn -v" command doesn't actually >>> tell you >>> what commit it came from. I don't know if it's generally wrong, but this >>> this case >>> c9950d777c7368e51431500c29aecf1e11e3d2c6 is the parent of >> >> Where did you get the above hash from? >> It does not seem to be the same as the one in the binary archive I >> downloaded. >> > > There's the argument for automation! It's actually an argument for quoting the hash in the vote e-mail and for people to actually check it. I find it strange that none of the reviewers noticed the problem. That suggests to me that none of the reviewers are actually interested in doing due diligence on the source archive contents. > I didn't open up the JAR from the checked out build. So this is probably the > best way right now and you've verified the right hash is available from the > build itself so that's probably what you need. No, as I already wrote, that is not suitable. Voting is on source archives; it's no good having the hash buried away in an indirectly related binary archive. >> On the git page: >> >> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=summary >> >> the c995... hash seems to be associated with >> >> [MNG-5509] org.apache.maven.repository.legacy.DefaultWa... >> >> This happens to be the line after >> >> [maven-release-plugin] prepare release maven-3.1.1 >> maven-3.1.1 >> >> which seems to have the following hash: >> >>> 892b464683645bcdc1d28febf0bf3cc1c3181350 which is the SHA1 for the release. >> >> Also the above hash is the one I just found in build.properties. >> >> And it agrees with mvn -v >> >> Apache Maven 3.1.1 (892b464683645bcdc1d28febf0bf3cc1c3181350; >> 2013-09-05 18:04:21+0100) >> >> So I don't think there's a problem with the build process, but there >> is still a major problem with the vote e-mail contents. >> >>> >>> I assumed someone actually tested this, or maybe it's being used in the >>> release for something it wasn't intended for. I'll take a look at the code. >>> But for now I will make the template from: >>> >>> http://maven.apache.org/developers/release/maven-project-release-procedure.html#Call_the_vote >>> >>> Are you sure that c9950d777c7368e51431500c29aecf1e11e3d2c6 is the hash for the build? On 10 September 2013 09:19, Karl Heinz Marbaise wrote: > +1 [non-binding] > > Tested with > * appassembler-maven-plugin (trunk: r18705) > > * maven-invoker-plugin (trunk: r1521365), > > * iterator-maven-plugin (git: 07ddf1a6a8fe4b60dbb84ce944c3a4f7828bff3e > https://github.com/khmarbaise/iterator-maven-plugin), > > * several of my own projects worked like a charm. > > > > On 9/8/13 3:07 PM, Jason van Zyl wrote: >> >> Hi, >> >> Here is a link to Jira with 6 issues resolved: >> >> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-016/ >> >> The distributable binaries and sources for testing can be found here: >> >> https://repository.apache.org/content/repositories/maven
Re: [VOTE] Release Maven 3.1.1
On Sep 10, 2013, at 9:58 AM, sebb wrote: > On 10 September 2013 14:23, Jason van Zyl wrote: >> >> On Sep 10, 2013, at 7:53 AM, sebb wrote: >> >>> I've just realised that you said the hash is in the maven core jar. >>> That is a binary artifact, and has no direct relationship with the >>> source artifact on which people are supposed to be voting. >>> >> >> It is supposed to be the SHA1 of the release from which the build was made. >> >>> I don't think it's possible to tie the SCM tag to this vote thread >>> "for the record" without the hash (and git repo) being provided in >>> this e-mail. >>> >> >> Well, I'm going to leave it out for now. I'll do what's strictly in the >> template here: >> >> http://maven.apache.org/developers/release/maven-project-release-procedure.html#Call_the_vote > > Which as I have argued all along is insufficient. > - the vote email does not have vital information "for the record" > - indeed in the case of this vote, neither the vote e-mail nor the > source archive (on which people are supposed to be voting) has the > information. > > I note that no-one who has voted so far has stated that the contents > of the source archives are all present and correct and that no files > are missing from the release and more importantly that there are no > files in the source archive that should not be there. > > IMO this is the most important part of the release vote, along with > the N&L contents. Get the PMC to agree and put it in the template and I'll use what's in the template. > >> >>> Also, I don't think the quoted hash is correct. >>> >> >> It doesn't look correct, it appears to take the parent commit. This has >> probably been >> the case for quite some time, in that the "mvn -v" command doesn't actually >> tell you >> what commit it came from. I don't know if it's generally wrong, but this >> this case >> c9950d777c7368e51431500c29aecf1e11e3d2c6 is the parent of > > Where did you get the above hash from? > It does not seem to be the same as the one in the binary archive I downloaded. > There's the argument for automation! I didn't open up the JAR from the checked out build. So this is probably the best way right now and you've verified the right hash is available from the build itself so that's probably what you need. > On the git page: > > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=summary > > the c995... hash seems to be associated with > > [MNG-5509] org.apache.maven.repository.legacy.DefaultWa... > > This happens to be the line after > > [maven-release-plugin] prepare release maven-3.1.1 > maven-3.1.1 > > which seems to have the following hash: > >> 892b464683645bcdc1d28febf0bf3cc1c3181350 which is the SHA1 for the release. > > Also the above hash is the one I just found in build.properties. > > And it agrees with mvn -v > > Apache Maven 3.1.1 (892b464683645bcdc1d28febf0bf3cc1c3181350; > 2013-09-05 18:04:21+0100) > > So I don't think there's a problem with the build process, but there > is still a major problem with the vote e-mail contents. > >> >> I assumed someone actually tested this, or maybe it's being used in the >> release for something it wasn't intended for. I'll take a look at the code. >> But for now I will make the template from: >> >> http://maven.apache.org/developers/release/maven-project-release-procedure.html#Call_the_vote >> >> >>> Are you sure that >>> >>> c9950d777c7368e51431500c29aecf1e11e3d2c6 >>> >>> is the hash for the build? >>> >>> On 10 September 2013 09:19, Karl Heinz Marbaise wrote: +1 [non-binding] Tested with * appassembler-maven-plugin (trunk: r18705) * maven-invoker-plugin (trunk: r1521365), * iterator-maven-plugin (git: 07ddf1a6a8fe4b60dbb84ce944c3a4f7828bff3e https://github.com/khmarbaise/iterator-maven-plugin), * several of my own projects worked like a charm. On 9/8/13 3:07 PM, Jason van Zyl wrote: > > Hi, > > Here is a link to Jira with 6 issues resolved: > > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 > > Staging repo: > https://repository.apache.org/content/repositories/maven-016/ > > The distributable binaries and sources for testing can be found here: > > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ > > Specifically the zip, tarball, and source archives can be found here: > > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip > > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz > > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip > > https://repository.apache.org/content/repositories
Re: [VOTE] Release Maven 3.1.1
Hi, Here is a link to Jira with 6 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 Staging repo: https://repository.apache.org/content/repositories/maven-016/ https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip Source release checksum(s): apache-maven-3.1.1-bin.zip sha1: 46a49ea9baf862d1ca31a98a7d4e188c1ad1b7ac Staging site: http://people.apache.org/~jvanzyl/maven-3.1.1/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.1.1
Let's continue with the vote, the binaries are still good. I will send another message with a new email template for posterity. On Sep 8, 2013, at 9:07 AM, Jason van Zyl wrote: > Hi, > > Here is a link to Jira with 6 issues resolved: > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 > > Staging repo: > https://repository.apache.org/content/repositories/maven-016/ > > The distributable binaries and sources for testing can be found here: > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ > > Specifically the zip, tarball, and source archives can be found here: > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > Thanks, > > The Maven Team > > > > > > > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -
Re: [VOTE] Release Maven 3.1.1
On 10 September 2013 14:23, Jason van Zyl wrote: > > On Sep 10, 2013, at 7:53 AM, sebb wrote: > >> I've just realised that you said the hash is in the maven core jar. >> That is a binary artifact, and has no direct relationship with the >> source artifact on which people are supposed to be voting. >> > > It is supposed to be the SHA1 of the release from which the build was made. > >> I don't think it's possible to tie the SCM tag to this vote thread >> "for the record" without the hash (and git repo) being provided in >> this e-mail. >> > > Well, I'm going to leave it out for now. I'll do what's strictly in the > template here: > > http://maven.apache.org/developers/release/maven-project-release-procedure.html#Call_the_vote Which as I have argued all along is insufficient. - the vote email does not have vital information "for the record" - indeed in the case of this vote, neither the vote e-mail nor the source archive (on which people are supposed to be voting) has the information. I note that no-one who has voted so far has stated that the contents of the source archives are all present and correct and that no files are missing from the release and more importantly that there are no files in the source archive that should not be there. IMO this is the most important part of the release vote, along with the N&L contents. > >> Also, I don't think the quoted hash is correct. >> > > It doesn't look correct, it appears to take the parent commit. This has > probably been > the case for quite some time, in that the "mvn -v" command doesn't actually > tell you > what commit it came from. I don't know if it's generally wrong, but this this > case > c9950d777c7368e51431500c29aecf1e11e3d2c6 is the parent of Where did you get the above hash from? It does not seem to be the same as the one in the binary archive I downloaded. On the git page: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=summary the c995... hash seems to be associated with [MNG-5509] org.apache.maven.repository.legacy.DefaultWa... This happens to be the line after [maven-release-plugin] prepare release maven-3.1.1 maven-3.1.1 which seems to have the following hash: > 892b464683645bcdc1d28febf0bf3cc1c3181350 which is the SHA1 for the release. Also the above hash is the one I just found in build.properties. And it agrees with mvn -v Apache Maven 3.1.1 (892b464683645bcdc1d28febf0bf3cc1c3181350; 2013-09-05 18:04:21+0100) So I don't think there's a problem with the build process, but there is still a major problem with the vote e-mail contents. > > I assumed someone actually tested this, or maybe it's being used in the > release for something it wasn't intended for. I'll take a look at the code. > But for now I will make the template from: > > http://maven.apache.org/developers/release/maven-project-release-procedure.html#Call_the_vote > > >> Are you sure that >> >> c9950d777c7368e51431500c29aecf1e11e3d2c6 >> >> is the hash for the build? >> >> On 10 September 2013 09:19, Karl Heinz Marbaise wrote: >>> +1 [non-binding] >>> >>> Tested with >>> * appassembler-maven-plugin (trunk: r18705) >>> >>> * maven-invoker-plugin (trunk: r1521365), >>> >>> * iterator-maven-plugin (git: 07ddf1a6a8fe4b60dbb84ce944c3a4f7828bff3e >>> https://github.com/khmarbaise/iterator-maven-plugin), >>> >>> * several of my own projects worked like a charm. >>> >>> >>> >>> On 9/8/13 3:07 PM, Jason van Zyl wrote: Hi, Here is a link to Jira with 6 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 Staging repo: https://repository.apache.org/content/repositories/maven-016/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team >>> >>> >>> Mit freundlichem Gruß >>> Karl-Heinz Marbaise >>> -- >>> SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 >>> Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 >>> Hauptstrasse 177 USt.IdNr: DE191347579 >>> 52146 Würselen http://www.soebes.de >>> >>> >>> --
Re: [VOTE] Release Maven 3.1.1
On Sep 10, 2013, at 7:53 AM, sebb wrote: > I've just realised that you said the hash is in the maven core jar. > That is a binary artifact, and has no direct relationship with the > source artifact on which people are supposed to be voting. > It is supposed to be the SHA1 of the release from which the build was made. > I don't think it's possible to tie the SCM tag to this vote thread > "for the record" without the hash (and git repo) being provided in > this e-mail. > Well, I'm going to leave it out for now. I'll do what's strictly in the template here: http://maven.apache.org/developers/release/maven-project-release-procedure.html#Call_the_vote > Also, I don't think the quoted hash is correct. > It doesn't look correct, it appears to take the parent commit. This has probably been the case for quite some time, in that the "mvn -v" command doesn't actually tell you what commit it came from. I don't know if it's generally wrong, but this this case c9950d777c7368e51431500c29aecf1e11e3d2c6 is the parent of 892b464683645bcdc1d28febf0bf3cc1c3181350 which is the SHA1 for the release. I assumed someone actually tested this, or maybe it's being used in the release for something it wasn't intended for. I'll take a look at the code. But for now I will make the template from: http://maven.apache.org/developers/release/maven-project-release-procedure.html#Call_the_vote > Are you sure that > > c9950d777c7368e51431500c29aecf1e11e3d2c6 > > is the hash for the build? > > On 10 September 2013 09:19, Karl Heinz Marbaise wrote: >> +1 [non-binding] >> >> Tested with >> * appassembler-maven-plugin (trunk: r18705) >> >> * maven-invoker-plugin (trunk: r1521365), >> >> * iterator-maven-plugin (git: 07ddf1a6a8fe4b60dbb84ce944c3a4f7828bff3e >> https://github.com/khmarbaise/iterator-maven-plugin), >> >> * several of my own projects worked like a charm. >> >> >> >> On 9/8/13 3:07 PM, Jason van Zyl wrote: >>> >>> Hi, >>> >>> Here is a link to Jira with 6 issues resolved: >>> >>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 >>> >>> Staging repo: >>> https://repository.apache.org/content/repositories/maven-016/ >>> >>> The distributable binaries and sources for testing can be found here: >>> >>> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ >>> >>> Specifically the zip, tarball, and source archives can be found here: >>> >>> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip >>> >>> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz >>> >>> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip >>> >>> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz >>> >>> Vote open for 72 hours. >>> >>> [ ] +1 >>> [ ] +0 >>> [ ] -1 >>> >>> Thanks, >>> >>> The Maven Team >>> >>> >>> >>> >>> >>> >>> >>> >> >> >> Mit freundlichem Gruß >> Karl-Heinz Marbaise >> -- >> SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 >> Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 >> Hauptstrasse 177 USt.IdNr: DE191347579 >> 52146 Würselen http://www.soebes.de >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > - > 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 -
Re: [VOTE] Release Maven 3.1.1
Sure, I can remake the email, but the binaries are fine. I made a little tool for myself and I'll just use the template from the website. The SHA1 I took was for the release which is the value that's interpolated into the build.properties. On Sep 9, 2013, at 3:56 PM, Stephen Connolly wrote: > On 8 September 2013 18:51, Jason van Zyl wrote: > >> >> On Sep 8, 2013, at 1:12 PM, sebb wrote: >> >>> I thought you were going to include the SCM coordinates used to create >>> the tarballs? >>> >> >> Sorry, not intentional. I forgot. >> >>> It's particularly important here, because AFAICT the SCM coordinates >>> are not present in the POM. >>> If true, then it's not possible to verify the files in the source >> tarballs. >>> >> >> I hash is always in the distribution, it's how we show where it comes from >> when you type "mvn -v". It's in the build properties in the core JAR and >> the hash in there is: >> >> c9950d777c7368e51431500c29aecf1e11e3d2c6 >> > > Is that the SHA1 of the src.zip and src.tar.gz or is it the SHA1 of the git > commit. > > What we are looking for on the vote emails is the SHA1 and MD5 of the > src.zip and src.tar.gz so that interested parties can verify that the vote > was against the source distribution that ends up in dist and central. Since > the staging repository is deleted as part of the release process, and since > what the PMC is voting on is the source bundles, we need the vote email to > specify the hashes of the source bundle *for the record*... > > Of course this is really easy to do as Maven helpfully uploads the hashes > to the staging repository, but since "it didn't happen if it wasn't on a > mailing list" (stephenc rolls his eyes) we need the release manager to > ensure that the vote has this required information. > > Note: The commit hash is really nice to have, but is not part of the > minimum set of required information, and we are trying to stick to minimum > procedure. So we don't look for that *even* if other people think we should. > > >> >>> Also, AFAIK, the PMC agreed to include hashes of the tarballs in vote >> e-mails? >>> >>> On 8 September 2013 14:07, Jason van Zyl wrote: Hi, Here is a link to Jira with 6 issues resolved: >> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 Staging repo: https://repository.apache.org/content/repositories/maven-016/ The distributable binaries and sources for testing can be found here: >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ Specifically the zip, tarball, and source archives can be found here: >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team >>> >>> - >>> 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 >> - >> >> >> >> >> >> >> >> Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -
Re: [VOTE] Release Maven 3.1.1
+1 Den 8. sep. 2013 15:08 skrev "Jason van Zyl" følgende: > Hi, > > Here is a link to Jira with 6 issues resolved: > > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 > > Staging repo: > https://repository.apache.org/content/repositories/maven-016/ > > The distributable binaries and sources for testing can be found here: > > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ > > Specifically the zip, tarball, and source archives can be found here: > > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip > > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz > > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip > > https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > Thanks, > > The Maven Team > > > > > > > >
Re: [VOTE] Release Maven 3.1.1
I've just realised that you said the hash is in the maven core jar. That is a binary artifact, and has no direct relationship with the source artifact on which people are supposed to be voting. I don't think it's possible to tie the SCM tag to this vote thread "for the record" without the hash (and git repo) being provided in this e-mail. Also, I don't think the quoted hash is correct. Are you sure that c9950d777c7368e51431500c29aecf1e11e3d2c6 is the hash for the build? On 10 September 2013 09:19, Karl Heinz Marbaise wrote: > +1 [non-binding] > > Tested with > * appassembler-maven-plugin (trunk: r18705) > > * maven-invoker-plugin (trunk: r1521365), > > * iterator-maven-plugin (git: 07ddf1a6a8fe4b60dbb84ce944c3a4f7828bff3e > https://github.com/khmarbaise/iterator-maven-plugin), > > * several of my own projects worked like a charm. > > > > On 9/8/13 3:07 PM, Jason van Zyl wrote: >> >> Hi, >> >> Here is a link to Jira with 6 issues resolved: >> >> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-016/ >> >> The distributable binaries and sources for testing can be found here: >> >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ >> >> Specifically the zip, tarball, and source archives can be found here: >> >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip >> >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz >> >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip >> >> https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz >> >> Vote open for 72 hours. >> >> [ ] +1 >> [ ] +0 >> [ ] -1 >> >> Thanks, >> >> The Maven Team >> >> >> >> >> >> >> >> > > > Mit freundlichem Gruß > Karl-Heinz Marbaise > -- > SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 > Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 > Hauptstrasse 177 USt.IdNr: DE191347579 > 52146 Würselen http://www.soebes.de > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 3.1(.1) maven-dependency-plugin (trunk: rxxx
Hi, > whereas in Maven 3.1 the following two integration tests fail: this must be Maven 3.1.1 ...sorry...;-) Kind regards Karl-Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven 3.1(.1) maven-dependency-plugin (trunk: rxxx
Hi,
in relationship with the Maven 3.1.1 vote
I have found an interessting thing:
* maven-dependency-plugin (trunk: r1521365):
Maven 3.0.5:
The following integration tests have been skipped:
[INFO] Building: purge-local-repository-reresolve/pom.xml
[INFO] ..SKIPPED
[INFO] Building: purge-local-repository-snapshots-only/pom.xml
[INFO] run script setup.bsh
[INFO] run script verify.bsh
[INFO] ..SUCCESS (2.6 s)
[INFO] Building: purge-local-repository-version-range/pom.xml
[INFO] ..SKIPPED
whereas in Maven 3.1 the following two integration tests fail:
[INFO] Building: purge-local-repository-reresolve/pom.xml
[INFO] ..FAILED (2.9 s)
[INFO] The build exited with code 1. See
/Users/kama/workspace/maven-dependency-plugin/target/it/purge-local-repository-reresolve/build.log
for details.
..
[INFO] Building: purge-local-repository-version-range/pom.xml
[INFO] ..FAILED (2.9 s)
[INFO] The build exited with code 1. See
/Users/kama/workspace/maven-dependency-plugin/target/it/purge-local-repository-version-range/build.log
for details.
and in Maven 3.1.1 the same two integration tests fail.
After taken a deeper look into that and the related issue (MNG-5366) and
the invoker.properties give me the hint.
This means that currently the invoker.properties must be enhanced to
skipp these two IT's based on the Maven version 3.1.1
I've attached patch to solve that temporarily for the current trunk.
Kind regards
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
Index: src/it/purge-local-repository-reresolve/invoker.properties
===
--- src/it/purge-local-repository-reresolve/invoker.properties (revision
1521366)
+++ src/it/purge-local-repository-reresolve/invoker.properties (working copy)
@@ -1,3 +1,3 @@
invoker.goals =
${project.groupId}:${project.artifactId}:${project.version}:resolve
${project.groupId}:${project.artifactId}:${project.version}:purge-local-repository
-# [MNG-5366] Does not work in Maven 3.0.4 due to the resolveAlways operation
not correctly forcing a new download
-invoker.maven.version = !3.0.4,!3.0.5,!3.1.0
+# [MNG-5366] Does not work in Maven 3.0.4, 3.0.5, 3.1 and 3.1.1 due to the
resolveAlways operation not correctly forcing a new download
+invoker.maven.version = !3.0.4,!3.0.5,!3.1.0,!3.1.1
Index: src/it/purge-local-repository-version-range/invoker.properties
===
--- src/it/purge-local-repository-version-range/invoker.properties
(revision 1521366)
+++ src/it/purge-local-repository-version-range/invoker.properties
(working copy)
@@ -1,3 +1,3 @@
invoker.goals =
${project.groupId}:${project.artifactId}:${project.version}:purge-local-repository
-# [MNG-5366] Does not work in Maven 3.0.4 due to the resolveAlways operation
not correctly forcing a new download
-invoker.maven.version = !3.0.4,!3.0.5,!3.1.0
+# [MNG-5366] Does not work in Maven 3.0.4, 3.0.5, 3.1 and 3.1.1 due to the
resolveAlways operation not correctly forcing a new download
+invoker.maven.version = !3.0.4,!3.0.5,!3.1.0,!3.1.1
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.1.1
+1 [non-binding] Tested with * appassembler-maven-plugin (trunk: r18705) * maven-invoker-plugin (trunk: r1521365), * iterator-maven-plugin (git: 07ddf1a6a8fe4b60dbb84ce944c3a4f7828bff3e https://github.com/khmarbaise/iterator-maven-plugin), * several of my own projects worked like a charm. On 9/8/13 3:07 PM, Jason van Zyl wrote: Hi, Here is a link to Jira with 6 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18968 Staging repo: https://repository.apache.org/content/repositories/maven-016/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team Mit freundlichem Gruß Karl-Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
