My project is using maven2 and the release plugin. However, the
release plugin only works with released plugins (otherwise, our
release builds are not reproducible). We've had to locally patch a
half-dozen plugins just to mark them as released just in order to be
able to do a release build
Hi Mike,
I'm assuming you're talking about running 1 goal in the same phase?
Order is not guaranteed. Annoying.
Documentation at http://maven.apache.org/guides/introduction/
introduction-to-the-lifecycle.html would imply that they are applied
in the order they're found in poms, but that
Hi Marco,
On Sep 20, 2006, at 10:56 AM, Marco Mistroni wrote:
hi all,
i m trying to run my tests using maven2 and testNG
i followed instructions at http://testng.org/doc/maven.html
You need to have a testing.xml.
See http://www.nabble.com/product-codes-at-java-1.4%2C-test-sources-
How do I get a list of these?
Clearly I can reference anything in settings.xml and pom.xml and all
system properties, but what else? ${basedir} seems to give me
directory of current pom.xml. I can't find one place where all these
useful things are documented. Hell, I'm not even sure what a
I have to start up 2 servers and a bunch of webservices in pre-
integration-test. Then I run my integration tests. Then post-
integration-test stops my servers. However, if some of my integration
tests fail, maven exits and does not stop my services. Despite being
annoying when I'm just
If I have a layout like this:
+ head
+-- A
+-- A1
+-- A2
+-- B
I want B to depend on A1 A2 ( A3 when I add that). Is there any
way to tell it to depend on all of A's modules instead of having to
specify the artifact, group and version for A1, A2, etc.?
I have a project structure like this:
head/
- docs
- libs/
-- libA
-- libB
If I cd to head/libs and run mvn -Daggregate=true jxr:jxr, libs/
target/site/xref has exactly what I expect. However, I really want to
be able to do this from head/docs and have the xrefs for libA libB.
I'm not
