Re: [VOTE] Release Maven Javadoc Plugin version 2.10.1
+1 Regards, Hervé Le samedi 27 septembre 2014 16:34:00 Michael Osipov a écrit : Hi, We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138version=206 44 There are still a couple of issues left in JIRA: http://jira.codehaus.org/issues/?jql=project%20%3D%20MJAVADOC%20AND%20resolu tion%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1069/ http://repository.apache.org/content/repositories/maven-1069/org/apache/mave n/plugins/maven-javadoc-plugin/2.10.1/maven-javadoc-plugin-2.10.1-source-rel ease.zip Source release checksum(s): maven-javadoc-plugin-2.10.1-source-release.zip sha1: 991cf644f9ec95a53899ca6a53dba0d14b74799b Staging site: http://maven.apache.org/plugins-archives/maven-javadoc-plugin-LATEST/ 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Resources Plugin version 2.7
+1 Regards, Hervé Le lundi 29 septembre 2014 23:48:55 Karl Heinz Marbaise a écrit : Hi, We solved 6 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11145version=186 45 There are still a couple of issues left in JIRA: http://jira.codehaus.org/issues/?jql=project%20%3D%20MRESOURCES%20AND%20stat us%20%3D%20Open%20ORDER%20BY%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1071 http://repository.apache.org/content/repositories/maven-1071/org/apache/mave n/plugins/maven-resources-plugin/2.7/maven-resources-plugin-2.7-source-relea se.zip Source release checksum(s): maven-resources-plugin-source-release.zip sha1: 96ffedc92fab107561632114bd027bdd0cd667f1 Staging site: http://maven.apache.org/plugins-archives/maven-resources-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Kind regards Karl-Heinz Marbaise - 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
[RESULT] [VOTE] Release Maven Javadoc Plugin version 2.10.1
Hi, The vote has passed with the following result: +1 (binding): Karl-Heinz Marbaise, Robert Scholte, Hervé Boutemy, Olivier Lamy +1 (non-binding): Mirko Friedenhagen I will promote the artifacts to the central repo. PMCs please promote the source release ZIP file and add this release the board report. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Javadoc Plugin 2.10.1 released
The Apache Maven team is pleased to announce the release of the Maven Javadoc Plugin, version 2.10.1. This module generates browsable HTML pages from Java source code. http://maven.apache.org/plugins/maven-javadoc-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.10.1/version /plugin Release Notes - Maven Javadoc Plugin - Version 2.10.1 ** Bug * [MJAVADOC-406] - Regression: MJAVADOC-398 commit changed wrong line * [MJAVADOC-407] - Cannot parse annotations when generating javadoc * [MJAVADOC-416] - java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast to com.sun.javadoc.AnnotationTypeDoc ** Improvement * [MJAVADOC-412] - Update version of plexus-archiver to 2.5 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: Seems like I have totally and fully broken windows support on trunk
We're back to normal now ! Fixing all windows/jDK permutations took a little time. Thank goodness for Jenkins ... K 29. Sep. 2014 09:27 skrev Kristian Rosenvold kristian.rosenv...@gmail.com følgende: Virtualbox to the rescue. I'm looking at it :) Kristian 2014-09-29 8:38 GMT+02:00 Kristian Rosenvold kristian.rosenv...@gmail.com : Using java 7 or better: git clone https://github.com/sonatype/plexus-io.git build it git clone https://github.com/sonatype/plexus-archiver.git build it On maven-war-plugin (trunk), update plexus-io to 2.1.2-SNAPSHOT and plexus-archiver to 2.6.2-SNAPSHOT. Run mvn -Prun-its clean install If it works now, my patch is good. Kristian 2014-09-29 8:04 GMT+02:00 Dennis Lundberg denn...@apache.org: Hi Kristian, Let me know if you need any help. I have Jenkins set up locally on my windows box with most versions of Java and Maven available. What needs testing? -- Dennis Lundberg Den 28 sep 2014 21:27 skrev Kristian Rosenvold kristian.rosenv...@gmail.com: I have fixed it, but I'll see if I can dig up a windows box tomorrow to actually test it before releasing more. Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Seems like I have totally and fully broken windows support on trunk
The end result was p-io 2.1.3 and archiver 2.6.3. I will do a jira sweep later today. Kristian 2. Okt. 2014 12:24 skrev Kristian Rosenvold kristian.rosenv...@gmail.com følgende: We're back to normal now ! Fixing all windows/jDK permutations took a little time. Thank goodness for Jenkins ... K 29. Sep. 2014 09:27 skrev Kristian Rosenvold kristian.rosenv...@gmail.com følgende: Virtualbox to the rescue. I'm looking at it :) Kristian 2014-09-29 8:38 GMT+02:00 Kristian Rosenvold kristian.rosenv...@gmail.com: Using java 7 or better: git clone https://github.com/sonatype/plexus-io.git build it git clone https://github.com/sonatype/plexus-archiver.git build it On maven-war-plugin (trunk), update plexus-io to 2.1.2-SNAPSHOT and plexus-archiver to 2.6.2-SNAPSHOT. Run mvn -Prun-its clean install If it works now, my patch is good. Kristian 2014-09-29 8:04 GMT+02:00 Dennis Lundberg denn...@apache.org: Hi Kristian, Let me know if you need any help. I have Jenkins set up locally on my windows box with most versions of Java and Maven available. What needs testing? -- Dennis Lundberg Den 28 sep 2014 21:27 skrev Kristian Rosenvold kristian.rosenv...@gmail.com: I have fixed it, but I'll see if I can dig up a windows box tomorrow to actually test it before releasing more. Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] Maven Javadoc Plugin 2.10.1 released
Hi Michael, added artifacts to distribution area and updated board report accordingly. Kind regards Karl-Heinz Marbaise On 10/2/14 10:42 AM, Michael Osipov wrote: The Apache Maven team is pleased to announce the release of the Maven Javadoc Plugin, version 2.10.1. This module generates browsable HTML pages from Java source code. http://maven.apache.org/plugins/maven-javadoc-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.10.1/version /plugin Release Notes - Maven Javadoc Plugin - Version 2.10.1 ** Bug * [MJAVADOC-406] - Regression: MJAVADOC-398 commit changed wrong line * [MJAVADOC-407] - Cannot parse annotations when generating javadoc * [MJAVADOC-416] - java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast to com.sun.javadoc.AnnotationTypeDoc ** Improvement * [MJAVADOC-412] - Update version of plexus-archiver to 2.5 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: [RESULT] [VOTE] Release Maven Javadoc Plugin version 2.10.1
Hi Michael, can you please forward this result mail to: CC: Maven Project Management Committee List priv...@maven.apache.org See also http://maven.apache.org/developers/release/maven-project-release-procedure.html On 10/2/14 9:39 AM, Michael Osipov wrote: Hi, The vote has passed with the following result: +1 (binding): Karl-Heinz Marbaise, Robert Scholte, Hervé Boutemy, Olivier Lamy +1 (non-binding): Mirko Friedenhagen I will promote the artifacts to the central repo. PMCs please promote the source release ZIP file and add this release the board report. Kind Regards Karl-Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1628003 - /maven/shared/trunk/maven-shared-utils/pom.xml
Hi Dennis, Karl-Heinz, the issue mentioned compatibility and based on the changes it looked to me that the intention doesn't match the actual behavior in the end. With plugins it is very easy to force a specific version of Maven: set the prerequisite. *If* the idea was that changing the maven dependency version in shared-utils to 2.2.1 would help us to push users towards newer versions of Maven, then that idea was not correct. It is possible, if you specify the dependency like: dependency groupIdorg.apache.maven/groupId artifactIdmaven-toolchain/artifactId version[2.2.1,)/version scopeprovided/scope /dependency The downside of this construction is that the project using shared-utils is now responsible to specify the preferred version, otherwise the latest will be used. If this change is just about housekeeping, that's fine too. But then the issue text is misleading. I hope this clears things up :) Robert Op Tue, 30 Sep 2014 13:43:06 +0200 schreef Dennis Lundberg denn...@apache.org: Hi Robert, Isn't the idea of the work Karl-Heinz is doing to unify the version of maven core libraries in our other components/plugins? It is true that the mavenVersion property has a dual meaning: 1. setting a prerequisite for the version of Maven required to build the project 2. setting the version of dependencies on maven core components IIUC Karl-Heinz is mainly trying to solve 2 by changing the value of mavenVersion. We have already in our docs that we require at least Maven 2.2.1 to build our projects, and in some cases (site) Maven 3.0.5. I don't see any negative sideeffect of changing the mavenVersion property. Perhaps I am missing something? When Karl-Heinz has finished upgrading to 2.2.1 everywhere, why would anyone want to redefine the preferred version to an earlier verion like 2.0.9? I can't think of a way to prevent that. Introducing a version range like [2.2.1,) for the prerequisites doesn't change anything as I understand it. On Sat, Sep 27, 2014 at 10:58 PM, Robert Scholte rfscho...@apache.org wrote: Hi, I wonder if this does what we want to achieve: forcing projects using maven-shared-utils to be executed with at least Maven 2.2.1. Right now it is just the preferred version, no problem if the project itself redefines it to 2.0.9 for instance. Is that a problem or should we say [2.2.1,) ? thanks, Robert Op Sat, 27 Sep 2014 22:30:03 +0200 schreef khmarba...@apache.org: Author: khmarbaise Date: Sat Sep 27 20:30:03 2014 New Revision: 1628003 URL: http://svn.apache.org/r1628003 Log: [MSHARED-359] - Upgrade to Maven 2.2.1 build and compatibility. Modified: maven/shared/trunk/maven-shared-utils/pom.xml Modified: maven/shared/trunk/maven-shared-utils/pom.xml URL: http://svn.apache.org/viewvc/maven/shared/trunk/maven-shared-utils/pom.xml?rev=1628003r1=1628002r2=1628003view=diff == --- maven/shared/trunk/maven-shared-utils/pom.xml (original) +++ maven/shared/trunk/maven-shared-utils/pom.xml Sat Sep 27 20:30:03 2014 @@ -55,7 +55,7 @@ /distributionManagement properties -mavenVersion2.1.0/mavenVersion +mavenVersion2.2.1/mavenVersion /properties dependencies - 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
[RESULT] [VOTE] Release Apache Maven Resources Plugin version 2.7
Hi, the vote has passed with the following result: +1 (binding): Olivier Lamy, Hervé Boutemy, Karl-Heinz Marbaise +1 (non binding): none I will promote the artifacts to the central repo. Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Apache Maven Resources Plugin Version 2.7 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Resources Plugin, version 2.7 The Resources Plugin handles the copying of project resources to the output directory. http://maven.apache.org/plugins/maven-resources-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId version2.7/version /plugin Release Notes - Maven Resources Plugin - Version 2.7 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11145version=18645 Bug: * [MRESOURCES-182] - Example Custom resource filters incorrect Improvements: * [MRESOURCES-177] - Use version 1.2 of maven-filtering to use improvements * [MRESOURCES-180] - Documentation does not use correct versions * [MRESOURCES-181] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MRESOURCES-183] - Upgrade to Maven 2.2.1 compatiblity * [MRESOURCES-184] - Removing plexus-container-default dependency Enjoy, -The Apache Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
PR 24 for plexus-compiler
It seems that I don't have access to commit directly to plexus-compiler. I've got a fix for the broken IT in the compiler plugin (for MCOMPILER-224, which is currently pegged at JDK 1.7+ since it can't handle output from JDK 1.6). Can someone merge the PR or give me access to do it? https://github.com/sonatype/plexus-compiler/pull/24 Thanks, -john -- John Casey --- GitHub: https://github.com/jdcasey/ Twitter: http://twitter.com/buildchimp - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: PR 24 for plexus-compiler
No idea how to give you access but I will merge that. Maybe Brian? On 3 October 2014 07:38, John Casey jdca...@commonjava.org wrote: It seems that I don't have access to commit directly to plexus-compiler. I've got a fix for the broken IT in the compiler plugin (for MCOMPILER-224, which is currently pegged at JDK 1.7+ since it can't handle output from JDK 1.6). Can someone merge the PR or give me access to do it? https://github.com/sonatype/plexus-compiler/pull/24 Thanks, -john -- John Casey --- GitHub: https://github.com/jdcasey/ Twitter: http://twitter.com/buildchimp - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
