How about moving the input file into a dependency for the other three projects
(each using the same plugin configured for one of its three modes)?
You end up with four projects instead of one, but it's maven compliant. Also
you get the (unwanted in your case) option of having different versions
Hi!
This could be a no-no, but can I create a MavenProject object from a POM
(other than the one executed) within my plugin?
I've traversed the JavaDocs, but there is no obvious way (all methods
require arguments I cannot provide, e.g. ProfileManager).
/jonas
Also, you mention the 9.2 release. As we're using WLS 8.1.3 will we miss out on
this fix?
/jonas
-Ursprungligt meddelande-
Från: Manu [mailto:[EMAIL PROTECTED]
Skickat: den 2 november 2006 10:27
Till: Maven Users List
Ämne: Re: [M2]weblogic:appc classpath issue
Can you also tell to
Perhaps the original question is wrongly put, IMHO?
If you have a shared library it should only be included ONCE in the end
product, right?
And this inclusion should be of a specific version (to allow build
re-production), right?
So all users of the shared library should list it as provided and
!
--
Jonas Olsson
System Designer
Cambio Healthcare Systems
Detta e-mail har blivit undersökt av http://www.virus112.se
projects. Just specify each dependencies' version
once in that section of the top-level POM...
Tom
On 10/30/06, Jonas Olsson [EMAIL PROTECTED] wrote:
Hi!
We're introducing Maven to our multi-artifact product build and we'de
really like to get full usage of the dependency mechanism. We've got
many
dependencies,
but it's worth a try. If you build a default site, this report will be
included. An example can be seen at
http://maven.apache.org/ref/current/dependency-convergence.html
Tom
On 10/30/06, Jonas Olsson [EMAIL PROTECTED] wrote:
I'll try to visualise the issue:
pom.xml (top level
