Like any other maven dependency or plugin, it lives in an artifact repository.
Specifically, in central [1]. There you'll see generally available versions.
[1]
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/
-Original Message-
From: Martin Gainty
Can the tests be in a separate jar? If so they could include the original jar
with the code to test but exclude dependencies as needed.
Steven
-Original Message-
From: Henrik [mailto:hen...@team11.org]
Sent: Thursday, May 07, 2009 6:04 AM
To: users@maven.apache.org
Subject: Exclude
Check out
http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html
-Original Message-
From: tubin gen [mailto:fachh...@gmail.com]
Sent: Thursday, May 07, 2009 11:52 AM
To: users@maven.apache.org
Subject: exclude transitive dependency
My
You can actually configure maven-eclipse-plugin [1] to generate specific files
into the .settings folder on eclipse:eclipse. I think you have to be able to
specify the entire contents of the file being written, but here is an example:
plugin
Trying to achieve consistency between organizations ahead of time could prove
difficult. I would instead suggest trying for consistency within your
organization and sharing notes about what worked and what didn't either on this
mailing list or perhaps the Maven wiki. Perhaps that could help
