This is an error that I get when I execute my project in Eclipse/STS
while running from a RAM drive.
If I run the same project running on Eclipse/STS while running on a
regular disk drive it works.
It is pretty deep in the Maven code and looks like Maven/Plexus sends a
bad argument to a Java f
There you go, at the bottom if this page:
http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html
Am Donnerstag, 3. Oktober 2013 schrieb Russell Gold :
> Hi,
>
> We have some unit tests that were always forked per-test in ant, and are
> now conver
Hi,
We have some unit tests that were always forked per-test in ant, and are now
converting to maven. The forkmode = always setting works, but without it, a
number of the tests fail (there are issues with the way they are written, and
we don't have time to rewrite them right now). The forkmode
That makes sense.
--
View this message in context:
http://maven.40175.n5.nabble.com/Parent-SNAPSHOT-not-resolved-Maven-2-2-1-3-0-4-Nexus-repo-tp5772374p5772388.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
On 3 Oct 2013, at 14:31, NRO wrote:
> Thanks for the clear explanation.
>
> All our artifacts are served by our Nexus Repository Manager (external and
> internal).
> All our repositories (hosted and proxy) are managed by Nexus, this is why
> our settings.xml and parent poms does not need to refer
Thanks for the clear explanation.
All our artifacts are served by our Nexus Repository Manager (external and
internal).
All our repositories (hosted and proxy) are managed by Nexus, this is why
our settings.xml and parent poms does not need to refer to other
repositories because we want to control
The scenario described below fails for me with or without a mirror setting - as
I would expect it to.
Given a child project with a missing parent pom Maven will attempt to resolve
the parent given the available context, namely:
settings.xml
current pom.xml
Maven's super-
Ok, lets talk with a concrete simple example:
PARENT POM:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
a.b.c
parente
0.0.1-SNAPSHOT
p
On 3 Oct 2013, at 11:11, Anders Hammar wrote:
> It should be the same for deps as well as parents. One difference could be
> if you have a repo declared in the pom (not setiings.xml). It might be that
> that repo is only used for deps and not the parent, I don't know.
FWIW, I've run some tests lo
It should be the same for deps as well as parents. One difference could be
if you have a repo declared in the pom (not setiings.xml). It might be that
that repo is only used for deps and not the parent, I don't know.
/Anders
On Thu, Oct 3, 2013 at 12:08 PM, NRO wrote:
> I understand your point
I understand your point, but the explaination you provide is based on how it
is implemented...and not on how it is specified.
The fact that maven can resolve the same artifact when it is a dependency
means that it is not a limitation but an implementation issue.
That looks bad to me to have to ad
You wrote it so nicely:
repo != mirror.
So, you have no repo set (only Central, that cannot contain snapshots), so
there is no "candidate" repo at all present to even try to get a snapshot
from.
Mirror on the other hand is NOT a repo, it merely _redirects_ existing
reposes to some other URL.
As I believe this was discussed on the Nexus list, the reason is what you
state. You have no repo defined in settings.xml, which means that only the
default central repo declaration is used which is only configured for
releases and not snapshots. And you're trying to retreieve a snapshot.
So this w
A maven project which have a parent SNAPSHOT cannot be resolved when :
a) the Parent SNAPSHOT pom is not present in the local maven repository
b) the Parent SNAPSHOT pom is deployed in a Nexus repository by another
developer.
c) settings.xml has a mirror redirecting all (*) to Nexus
d) there is n
14 matches
Mail list logo
