On Thu, 23 Feb 2017 03:08:10 +0100, Christian Schulte <c...@schulte.it>
wrote:
Am 02/20/17 um 18:28 schrieb Robert Scholte:
On Mon, 20 Feb 2017 02:17:12 +0100, Christian Schulte <c...@schulte.it>
wrote:
Am 02/20/17 um 01:53 schrieb Christian Schulte:
Hi,
I cannot build 'maven-dependency-analyzer' trunk on Windows. Is there
some dependency I could upgrade to get this going? This is what I am
doing locally:
svn checkout
..../repos/asf/maven/shared/trunk/maven-dependency-analyzer
cd maven-dependency-analyzer
mvn verify -Papache-snapshots,run-its
Jenkins build job is here:
<https://builds.apache.org/view/Maven%20Master%20Release%20Status/job/maven-master-release-status-test-shared-windows/>
Regards,
Seems we cannot rename the mvn.bat file to mvn.cmd. Can someone clarify
this, please. Is it "just" our invoker relying on this?
Effective pom says maven-invoker-plugin-2.0.0 is used, which is aware of
both mvn.bat and mvn.cmd
Robert
Can you build the shared trunk on Windows using 3.5.0-SNAPSHOT? I am
running into issues related to something not finding the mvn.bat file. I
manually copied the mvn.cmd to mvn.bat and things started to work.
Regards,
Ok, got it. The *unit-tests* were failing due to an ancient version of
maven-plugin-testing-tools (which is kind of weird, since
dependency-analyzing should not be aware of plugins...). Easiest fix is to
ensure that at least maven-invoker-2.2 is used. The project depends on
Maven-2.0.5 dependencies, so we could also upgrade it all, in which case
is faces similar issues for these tests as when upgrading plugins[1]
In case of *integration-tests* with maven-invoker-plugin, you can use
version maven-invoker-plugin:2.0.0
Robert
[1]
https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
