This is easier in m2... in m1, I'd suggest having another parent that
simply extends the original parent and adds the core dep. All the
projects except core should extend that.
On 8/26/05, Litton, Tom - CEPM <[EMAIL PROTECTED]> wrote:
> I was hoping to get some advice from all of you brilliant and kind maven
> users.
>
> I have several projects (about 10) that all depend on a core library. All
> the projects and the core extend from the same project.xml.
>
> I would really like to add the dependency on the core library in the parent
> project.xml, however, this causes a problem when compiling the core library.
> Has anyone come up with a good idea of what to do in this case? What is the
> best practice in this case?
>
> I've tried adding this to the parent project.xml:
>
> <j:if test="${pom.getProperty('artifactId') != 'core'}">
> <dependency>
> <groupId>mygroup</groupId>
> <artifactId>core</artifactId>
> <version>1.1-SNAPSHOT</version>
> </dependency>
> </j:if>
>
> But, it isn't working and is kind of a hack anyways.
>
> Thanks all,
>
>
> ----------------------------------------------------------------------
> The information contained in this transmission is intended only for
> the personal and confidential use of the designated recipients named
> herein. If the reader of this transmission is not the intended
> recipient or an agent responsible for delivering it to the intended
> recipient, you are hereby notified that you have received this
> transmission in error, and that any review, dissemination,
> distribution, or copying of this transmission is strictly prohibited.
> If you have received this communication in error, please notify the
> sender and return and delete the original transmission immediately.
> Thank you.
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
