I'm pretty sure this is still an issue for every project.
IIRC this is exactly the reason why Stephen thought of including/moving
the mock repository manager to the maven-invoker-plugin.
That much better to maintain than including all the extraArtifacts.
btw, with "Offline (no internet connection) and a clean local repository",
where should the artifacts come from? I wonder if "offline" is a valid
usecase.
Robert
Op Fri, 19 Sep 2014 21:47:11 +0200 schreef Karl Heinz Marbaise
<khmarba...@gmx.de>:
Hi,
after diving a little bit more i found the following issues...
prerequisites:
Offline (no internet connection) and a clean local repository:
mvn -Prun-its clean verify
so you got failures within the intergration test based on missing
artifacts like:
[ERROR] The following builds failed:
[ERROR] * setup/maven-scm-provider-dummy/pom.xml
[ERROR] * setup/maven-scm-provider-stub/pom.xml
[ERROR] * setup/maven-wagon-provider-dummy/pom.xml
[ERROR] * projects/prepare/completion-goals/pom.xml
[ERROR] * projects/prepare/flat-multi-module/parent-project/pom.xml
[ERROR] * projects/prepare/forked-basic/pom.xml
[ERROR] * projects/prepare/invoker-basic/pom.xml
[ERROR] * projects/prepare/MRELEASE-128/pom.xml
[ERROR] * projects/prepare/MRELEASE-156/pom.xml
[ERROR] * projects/prepare/MRELEASE-420/pom.xml
[ERROR] * projects/prepare/MRELEASE-483/pom.xml
[ERROR] * projects/prepare/MRELEASE-533/other-pom.xml
[ERROR] * projects/prepare/MRELEASE-571_M3/pom.xml
[ERROR] * projects/prepare/MRELEASE-618/my-pom.xml
[ERROR] * projects/prepare/MRELEASE-667/pom.xml
[ERROR] * projects/prepare/regular-multi-module/pom.xml
maven-compiler-plugin:2.0.2, wagon-provider-api:2.2, maven-scm-api:1.5,
maven-surefire-plugin:2.12.4 etc. maven-install-plugin etc.
If i add those artifacts via extraArtifact for the maven-invoker-plugin
you will get them to run...but one problem will be left unsolved...
There are some artifacts which are used like maven-install-plugin during
the integration test but which are NOT pinned in the pom files of the
integration tests which makes the IT's maven dependent...
The only solution i know is to create a parent pom for all integration
tests to solve this problem...
What do you think ?
On 9/18/14 11: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, Benson Margulies
<bimargul...@gmail.com>
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" <khmarba...@gmx.de>
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
---------------------------------------------------------------------
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
