Martin Gainty wrote:
i downloaded maven-3.0 full
at command line ran
mvn -e -X install
I don't want to sound rude but those few lines aren't really helpful either.
You "downloaded maven-3.0 full", is that "downloaded" as in you
downloaded some source/binary archive from some URL, or more as in you
checked out some SVN URL?
You ran "mvn -e -X install". Which version of Maven was that, the
"maven-3.0 full" you just downloaded or something else?
What I wanted to illustrate is that the given information doesn't allow
us to reproduce your issue, making proper assistance impossible. I can
imagine that it might be hard to consider all the pieces that somebody
else needs to reproduce an issue. For a case like this where you're
building Maven itself the best I can suggest is to provide instructions
that are as detailed that we could create a CI job from them.
Maven being a build tool, the minimum of information required to analyze
build errors are:
- the project sources including but not limited to a complete POM,
either given by a SCM URL + Revision or a ready-made archive to unpack
- the sequence of Maven commands that were executed on the project, for
multi-module projects also indicating the working directory for each
command, last but not least, the version of Maven being used
- especially for issues related to dependency resolution, some infos
about the network infrastructure, configured repos, mirrors, proxies,
authentication yes/no
- the JDK (vendor/version) being used to run Maven
Maven's trunk is building fine on CI [0] so what's the difference
between our CI and your environment?
Benjamin
[0] https://grid.sonatype.org/ci/job/maven-3.0.x/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
