Re: [VOTE] Release Apache Maven Javadoc Plugin version 2.10
+1 On 16 September 2014 06:32, Dennis Lundberg wrote: > Hi, > > The main focus for this release is Java 8 compatibility. > > We solved 11 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138&styleName=Html&version=19448 > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11138&status=1 > > Staging repo: > https://repository.apache.org/content/repositories/maven-1061/ > https://repository.apache.org/content/repositories/maven-1061 > /org/apache/maven/plugins/maven-javadoc-plugin/2.10/maven-javadoc-plugin-2.10-source-release.zip > > Source release checksum(s): > maven-javadoc-plugin-2.10-source-release.zip sha1: > 5e824c3ae6a8885eaecbe7645e10c441fa69038f > > Staging site: > http://maven.apache.org/plugins-archives/maven-javadoc-plugin-LATEST/ > (waiting for the sync to complete) > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > > -- > Dennis Lundberg > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Olivier 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
Re: [VOTE] Release Apache Maven Release Plugin version 2.5.1
I thought it was strange, too. Background: I checked out the trunk of
maven-release, built, and got that error. I scratched my head for a
day, and then a vague memory caused me to try setting M2_HOME. Bingo!
So, since it was that way before I changed anything, and I'm pretty
sure, in fact, that it was that way when I started the process of
making the previous release, I didn't feel inclined to go Yak-Shaving
in an effort to explain or remove the effect.
On Thu, Sep 18, 2014 at 5:00 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> I have admit the setting of M2_HOME did the trick...which looks a little bit
> strange for me...
>
>
> So maven 3.0.5 worked...but I have checked Maven 2.2.1 where integration
> tests of maven-release-plugin failed:
>
> [DEBUG] (f) waitBeforeTagging = 0
> [DEBUG] -- end configuration --
> [INFO] [release:prepare {execution: default-cli}]
> [DEBUG] release.properties not found - using empty properties
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: **/pom.xml.backup, **/release.properties,
> **/pom.xml.branch, **/pom.xml.next, **/pom.xml.releaseBackup, **/pom.xml.tag
> [INFO] Checking dependencies and plugins for snapshots ...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [DEBUG] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.shared.release.phase.MapVersionsPhase.resolveSuggestedVersion(MapVersionsPhase.java:323)
> at
> org.apache.maven.shared.release.phase.MapVersionsPhase.resolveNextVersion(MapVersionsPhase.java:266)
> at
> org.apache.maven.shared.release.phase.MapVersionsPhase.execute(MapVersionsPhase.java:172)
> at
> org.apache.maven.shared.release.phase.MapVersionsPhase.simulate(MapVersionsPhase.java:380)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:228)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:169)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:146)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:107)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:286)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:240)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
>
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Thu Sep 18 22:47:20 CEST 2014
> [INFO] Final Memory: 30M/302M
> [INFO]
>
>
> I'm not sure but it could be caused by missing artifacts which are not
> correctly mentioned for the maven-invoker-plugin (extraArtifacts)...?
>
>
> On 9/18/14 10:18 PM, Dan Tran wrote:
>>
>> Strange M2_HOME implicitly set at mvn.bat/mvn startup scripts.
>>
>> -D
>>
>> On Thu, Sep 18, 2014 at 1:14 PM
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.13
wow, I didn't see this MCHECKSTYLE-249 created: we'll need to fix it for the next version Notice that one (good) solution is not to use Windows ;) Regards, Hervé Le jeudi 18 septembre 2014 22:38:51 Robert Scholte a écrit : > Based on the zip-file > > +0 > > [INFO] - > [INFO] Build Summary: > [INFO] Passed: 28, Failed: 4, Errors: 0, Skipped: 0 > [INFO] - > [ERROR] The following builds failed: > [ERROR] * avalon-checks\pom.xml > [ERROR] * check-fail\pom.xml > [ERROR] * MCHECKSTYLE-169\pom.xml > [ERROR] * turbine-checks\pom.xml > [INFO] - > > They all fail for the same reason: > NewlineAtEndOfFile: File does not end with a newline. > > The reason: > Subversion is capable in translating the line endings when checking out. > The zip uses the line-endings based on the OS where it was generated. > I've confirmed this by running the code from tag, which indeed runs fine. > > This means that the official release(i.e the zipped distribution) has > become OS dependent, since you can't build it on Windows anymore without > skipping these ITs. > > thanks, > Robert > > Op Thu, 18 Sep 2014 17:19:26 +0200 schreef Karl Heinz Marbaise > > : > > Hi, > > > > Tested with Maven 2.2.1, 3.0.5, 3.1.1, 3.2.1, 3.2.2 > > > > via mvn -Prun-its clean verify > > > > so +1 from me. > > > > > Hi, > >> > >> We solved 24 issues: > >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127&styleNam > >> e=Html&version=20185 > >> > >> There are still a couple of issues left in JIRA: > >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11127&; > >> status=1 > >> > >> Staging repo: > >> https://repository.apache.org/content/repositories/maven-1063/ > >> http://repository.apache.org/content/repositories/maven-1063/org/apache/m > >> aven/plugins/maven-checkstyle-plugin/2.13/maven-checkstyle-plugin-2.13-so > >> urce-release.zip > >> > >> Source release checksum(s): > >> maven-checkstyle-plugin-2.13-source-release.zip sha1: > >> e5378d97f75de890b02665c7f853cc9f6d7d8f6b > > > > SHA1 sum checked... > > > >> Staging site: > >> http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/ > > > > Site looks ok... > > > >> 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Release Plugin version 2.5.1
Hi,
I have admit the setting of M2_HOME did the trick...which looks a little
bit strange for me...
So maven 3.0.5 worked...but I have checked Maven 2.2.1 where integration
tests of maven-release-plugin failed:
[DEBUG] (f) waitBeforeTagging = 0
[DEBUG] -- end configuration --
[INFO] [release:prepare {execution: default-cli}]
[DEBUG] release.properties not found - using empty properties
[INFO] Verifying that there are no local modifications...
[INFO] ignoring changes on: **/pom.xml.backup, **/release.properties,
**/pom.xml.branch, **/pom.xml.next, **/pom.xml.releaseBackup, **/pom.xml.tag
[INFO] Checking dependencies and plugins for snapshots ...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[DEBUG] Trace
java.lang.NullPointerException
at
org.apache.maven.shared.release.phase.MapVersionsPhase.resolveSuggestedVersion(MapVersionsPhase.java:323)
at
org.apache.maven.shared.release.phase.MapVersionsPhase.resolveNextVersion(MapVersionsPhase.java:266)
at
org.apache.maven.shared.release.phase.MapVersionsPhase.execute(MapVersionsPhase.java:172)
at
org.apache.maven.shared.release.phase.MapVersionsPhase.simulate(MapVersionsPhase.java:380)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:228)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:169)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:146)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:107)
at
org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:286)
at
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:240)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Sep 18 22:47:20 CEST 2014
[INFO] Final Memory: 30M/302M
[INFO]
I'm not sure but it could be caused by missing artifacts which are not
correctly mentioned for the maven-invoker-plugin (extraArtifacts)...?
On 9/18/14 10:18 PM, Dan Tran wrote:
Strange M2_HOME implicitly set at mvn.bat/mvn startup scripts.
-D
On Thu, Sep 18, 2014 at 1:14 PM, Benson Margulies
wrote:
You need to set M2 HOME. I have no longer underscore on my phone.
On Sep 18, 2014 3:48 PM, "Karl Heinz Marbaise" wrote:
Hi Benson,
Checksum Ok.
Site looks ok.
Just a question: Do i need a special setup to run tests etc. of the
package cause i got the following:
tried via mvn -Prun-its clean verify
Environment:
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
14:51:28+0100)
Maven home: /usr/share/maven
Java version: 1.7.0_21, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_
21.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.8.5", arch: "x86_64", family: "mac"
Results :
Tests in error:
InvokerMavenExecutorTest.testEncryptSettings:132 » Illeg
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.13
Based on the zip-file +0 [INFO] - [INFO] Build Summary: [INFO] Passed: 28, Failed: 4, Errors: 0, Skipped: 0 [INFO] - [ERROR] The following builds failed: [ERROR] * avalon-checks\pom.xml [ERROR] * check-fail\pom.xml [ERROR] * MCHECKSTYLE-169\pom.xml [ERROR] * turbine-checks\pom.xml [INFO] - They all fail for the same reason: NewlineAtEndOfFile: File does not end with a newline. The reason: Subversion is capable in translating the line endings when checking out. The zip uses the line-endings based on the OS where it was generated. I've confirmed this by running the code from tag, which indeed runs fine. This means that the official release(i.e the zipped distribution) has become OS dependent, since you can't build it on Windows anymore without skipping these ITs. thanks, Robert Op Thu, 18 Sep 2014 17:19:26 +0200 schreef Karl Heinz Marbaise : Hi, Tested with Maven 2.2.1, 3.0.5, 3.1.1, 3.2.1, 3.2.2 via mvn -Prun-its clean verify so +1 from me. > Hi, We solved 24 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127&styleName=Html&version=20185 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11127&status=1 Staging repo: https://repository.apache.org/content/repositories/maven-1063/ http://repository.apache.org/content/repositories/maven-1063/org/apache/maven/plugins/maven-checkstyle-plugin/2.13/maven-checkstyle-plugin-2.13-source-release.zip Source release checksum(s): maven-checkstyle-plugin-2.13-source-release.zip sha1: e5378d97f75de890b02665c7f853cc9f6d7d8f6b SHA1 sum checked... Staging site: http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/ Site looks ok... 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
MCHANGES-341: Best way to configure specific Mojo
Hello everybody, I want to take a stance at above issue[1]. REST-requests to JIRA timeout after +- 30 seconds right now. Internally we use a misconfigured JIRA instance where the call to the status-URL needs 4 minutes (400.000 issues with 400 resolutions, that is what happens when 120 people are JIRA-admins ;-))! Should I just add additional parameters to the announcement-generate, announcement-mail and jira-report? Maybe it would be better to use environment variables as these mojo already have loads of configuration parameters and the use case is very specific. What do you think? Best Regards Mirko [1] https://jira.codehaus.org/browse/MCHANGES-341 Externalize JIRA server timeout values to the configuration section - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Release Plugin version 2.5.1
Strange M2_HOME implicitly set at mvn.bat/mvn startup scripts. -D On Thu, Sep 18, 2014 at 1:14 PM, Benson Margulies wrote: > You need to set M2 HOME. I have no longer underscore on my phone. > On Sep 18, 2014 3:48 PM, "Karl Heinz Marbaise" wrote: > > > Hi Benson, > > > > Checksum Ok. > > Site looks ok. > > > > Just a question: Do i need a special setup to run tests etc. of the > > package cause i got the following: > > > > tried via mvn -Prun-its clean verify > > > > Environment: > > Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 > > 14:51:28+0100) > > Maven home: /usr/share/maven > > Java version: 1.7.0_21, vendor: Oracle Corporation > > Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_ > > 21.jdk/Contents/Home/jre > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "10.8.5", arch: "x86_64", family: "mac" > > > > > > > > Results : > > > > Tests in error: > > InvokerMavenExecutorTest.testEncryptSettings:132 » IllegalState Maven > > applicat... > > > > Tests run: 592, Failures: 0, Errors: 1, Skipped: 1 > > > > ? > > Kind regards > > Karl-Heinz Marbaise > > > > > > On 9/17/14 7:37 PM, Benson Margulies wrote: > > > >> Hi, > >> > >> We solved 4 issues: > >> > >> http://jira.codehaus.org/secure/ReleaseNote.jspa? > >> projectId=11144&version=20578 > >> > >> > >> There are still a couple of issues left in JIRA: > >> http://jira.codehaus.org/secure/ReleaseNote.jspa? > >> projectId=11144&version=20578 > >> > >> Staging repo: > >> https://repository.apache.org/content/repositories/maven-1062 > >> http://repository.apache.org/content/repositories/maven- > >> 1062/org/apache/maven/release/maven-release/2.5.1/maven- > >> release-2.5.1-source-release.zip > >> > >> Source release checksum(s): > >> maven-release-2.5.1-source-release.zip sha1: > >> 894c26647abe1a0fef9929c2f7bfd662f2f240b9 > >> > >> Staging site: > >> maven-release-archives/maven-release-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 > > > > >
Re: [VOTE] Release Apache Maven Release Plugin version 2.5.1
You need to set M2 HOME. I have no longer underscore on my phone. On Sep 18, 2014 3:48 PM, "Karl Heinz Marbaise" wrote: > Hi Benson, > > Checksum Ok. > Site looks ok. > > Just a question: Do i need a special setup to run tests etc. of the > package cause i got the following: > > tried via mvn -Prun-its clean verify > > Environment: > Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 > 14:51:28+0100) > Maven home: /usr/share/maven > Java version: 1.7.0_21, vendor: Oracle Corporation > Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_ > 21.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.8.5", arch: "x86_64", family: "mac" > > > > Results : > > Tests in error: > InvokerMavenExecutorTest.testEncryptSettings:132 » IllegalState Maven > applicat... > > Tests run: 592, Failures: 0, Errors: 1, Skipped: 1 > > ? > Kind regards > Karl-Heinz Marbaise > > > On 9/17/14 7:37 PM, Benson Margulies wrote: > >> Hi, >> >> We solved 4 issues: >> >> http://jira.codehaus.org/secure/ReleaseNote.jspa? >> projectId=11144&version=20578 >> >> >> There are still a couple of issues left in JIRA: >> http://jira.codehaus.org/secure/ReleaseNote.jspa? >> projectId=11144&version=20578 >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-1062 >> http://repository.apache.org/content/repositories/maven- >> 1062/org/apache/maven/release/maven-release/2.5.1/maven- >> release-2.5.1-source-release.zip >> >> Source release checksum(s): >> maven-release-2.5.1-source-release.zip sha1: >> 894c26647abe1a0fef9929c2f7bfd662f2f240b9 >> >> Staging site: >> maven-release-archives/maven-release-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 > >
Re: [VOTE] Release Apache Maven Release Plugin version 2.5.1
Hi Benson, Checksum Ok. Site looks ok. Just a question: Do i need a special setup to run tests etc. of the package cause i got the following: tried via mvn -Prun-its clean verify Environment: Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Maven home: /usr/share/maven Java version: 1.7.0_21, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.8.5", arch: "x86_64", family: "mac" Results : Tests in error: InvokerMavenExecutorTest.testEncryptSettings:132 » IllegalState Maven applicat... Tests run: 592, Failures: 0, Errors: 1, Skipped: 1 ? Kind regards Karl-Heinz Marbaise On 9/17/14 7:37 PM, Benson Margulies wrote: Hi, We solved 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144&version=20578 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144&version=20578 Staging repo: https://repository.apache.org/content/repositories/maven-1062 http://repository.apache.org/content/repositories/maven-1062/org/apache/maven/release/maven-release/2.5.1/maven-release-2.5.1-source-release.zip Source release checksum(s): maven-release-2.5.1-source-release.zip sha1: 894c26647abe1a0fef9929c2f7bfd662f2f240b9 Staging site: maven-release-archives/maven-release-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
[VOTE] Release Apache Maven Dependency Plugin version 2.9
Hi, We solved 17 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214&version=19229 There are still a couple of issues left in JIRA: http://jira.codehaus.org/issues/?jql=project%20%3D%20MDEP%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: http://repository.apache.org/content/repositories/maven-1064/ http://repository.apache.org/content/repositories/maven-1064/org/apache/maven/plugins/maven-dependency-plugin/2.9/maven-dependency-plugin-2.9-source-release.zip Source release checksum(s): maven-dependency-plugin-2.9-source-release.zip sha1: 026be37ea26f2f986da0aa74862f969777dfb376 Staging site: http://maven.apache.org/plugins-archives/maven-dependency-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
Re: [VOTE] Release Apache Maven Javadoc Plugin version 2.10
+1 Op Thu, 18 Sep 2014 20:30:22 +0200 schreef Dennis Lundberg : +1 from me -- Dennis Lundberg Den 15 sep 2014 22:32 skrev "Dennis Lundberg" : Hi, The main focus for this release is Java 8 compatibility. We solved 11 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138&styleName=Html&version=19448 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11138&status=1 Staging repo: https://repository.apache.org/content/repositories/maven-1061/ https://repository.apache.org/content/repositories/maven-1061 /org/apache/maven/plugins/maven-javadoc-plugin/2.10/maven-javadoc-plugin-2.10-source-release.zip Source release checksum(s): maven-javadoc-plugin-2.10-source-release.zip sha1: 5e824c3ae6a8885eaecbe7645e10c441fa69038f Staging site: http://maven.apache.org/plugins-archives/maven-javadoc-plugin-LATEST/ (waiting for the sync to complete) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Javadoc Plugin version 2.10
+1 from me -- Dennis Lundberg Den 15 sep 2014 22:32 skrev "Dennis Lundberg" : > Hi, > > The main focus for this release is Java 8 compatibility. > > We solved 11 issues: > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138&styleName=Html&version=19448 > > There are still a couple of issues left in JIRA: > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11138&status=1 > > Staging repo: > https://repository.apache.org/content/repositories/maven-1061/ > https://repository.apache.org/content/repositories/maven-1061 > > /org/apache/maven/plugins/maven-javadoc-plugin/2.10/maven-javadoc-plugin-2.10-source-release.zip > > Source release checksum(s): > maven-javadoc-plugin-2.10-source-release.zip sha1: > 5e824c3ae6a8885eaecbe7645e10c441fa69038f > > Staging site: > http://maven.apache.org/plugins-archives/maven-javadoc-plugin-LATEST/ > (waiting for the sync to complete) > > 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 >
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.13
Hi, Tested with Maven 2.2.1, 3.0.5, 3.1.1, 3.2.1, 3.2.2 via mvn -Prun-its clean verify so +1 from me. > Hi, We solved 24 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127&styleName=Html&version=20185 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11127&status=1 Staging repo: https://repository.apache.org/content/repositories/maven-1063/ http://repository.apache.org/content/repositories/maven-1063/org/apache/maven/plugins/maven-checkstyle-plugin/2.13/maven-checkstyle-plugin-2.13-source-release.zip Source release checksum(s): maven-checkstyle-plugin-2.13-source-release.zip sha1: e5378d97f75de890b02665c7f853cc9f6d7d8f6b SHA1 sum checked... Staging site: http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/ Site looks ok... 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
Re: java_home detection bug in maven 3.2.3
To file a ticket at jira.c.o, you first need to create an account at http://xircles.codehaus.org/. Please file this bug report to make sure it gets handled. /Anders On Thu, Sep 18, 2014 at 9:31 AM, Ye Xianjin wrote: > Hi, Developers: > I found this bug today on Mac OS X 10.10. > > Maven version: 3.2.3 > File path: apache-maven-3.2.3/apache-maven/src/bin/mvn line86 > Code snippet: > >if [[ -z "$JAVA_HOME" && -x "/usr/libexec/java_home" ]] ; then > # > # Apple JDKs > # > export JAVA_HOME=/usr/libexec/java_home >fi > >It should be : > >if [[ -z "$JAVA_HOME" && -x "/usr/libexec/java_home" ]] ; then > # > # Apple JDKs > # > export JAVA_HOME=`/usr/libexec/java_home` >fi > >I wanted to file a jira to http://jira.codehaus.org ( > http://jira.codehaus.org/). But it seems it's not open for registration. > So I think maybe it's a good idea to send an email here. > > -- > Ye Xianjin > Sent with Sparrow (http://www.sparrowmailapp.com/?sig) > >
java_home detection bug in maven 3.2.3
Hi, Developers: I found this bug today on Mac OS X 10.10. Maven version: 3.2.3 File path: apache-maven-3.2.3/apache-maven/src/bin/mvn line86 Code snippet: if [[ -z "$JAVA_HOME" && -x "/usr/libexec/java_home" ]] ; then # # Apple JDKs # export JAVA_HOME=/usr/libexec/java_home fi It should be : if [[ -z "$JAVA_HOME" && -x "/usr/libexec/java_home" ]] ; then # # Apple JDKs # export JAVA_HOME=`/usr/libexec/java_home` fi I wanted to file a jira to http://jira.codehaus.org (http://jira.codehaus.org/). But it seems it's not open for registration. So I think maybe it's a good idea to send an email here. -- Ye Xianjin Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
