Wendy,
I can't say I've had this exact problem, but I can think of two approaches
I'd consider:
1) Create a separate project, let's call it jsf. Have all the RI/MyFaces
jars listed in its dependency list. No code is involved, but the build
produces two artifacts, both "uberjars" (not that you'd u
From: "Jay H. Hartley" <[EMAIL PROTECTED]>
2) Create two different "parent" project files, and have the "extends"
parameter depend on a property:
${jsf.project.file}
That has promise! Thanks, I didn't know you could do that. :)
If it's not painfully obvious by this point, this is an existi
This is a bit "dangerous".
1) a project will have a different model depending on that property. It will
ripple into needing to change other things like the final name of the built
artifact to ensure you don't end up with one thing sometimes being something
different
2) you can only do this tri
From: "Jay H. Hartley" <[EMAIL PROTECTED]>
2) Create two different "parent" project files, and have the "extends"
parameter depend on a property:
${jsf.project.file}
Jay, this turned out to work *perfectly*!
project.properties:
maven.shale.jsf.impl.default=myfaces
-project.xml
${maven.sha
t models that just happen to
share the same codebase.
Good luck,
Jay
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 01, 2005 10:40 AM
To: Maven Users List
Subject: Re: [m1] Conditional dependencies
From: "Jay H. Hartley" <[EMAIL PROTE
From: "Brett Porter" <[EMAIL PROTECTED]>
This is a bit "dangerous".
Agreed. :) But it works.
1) a project will have a different model depending on that property. It
will ripple into needing to change other things like the final name of the
built artifact to ensure you don't end up with one
