ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: How to override targets specified in import file
Date Mon, 21 Sep 2009 20:48:56 GMT
> -----Original Message-----
> From: Martin Gainty []
> Sent: Monday, September 21, 2009 1:23 PM
> To: Ant Users List
> Subject: RE: How to override targets specified in import file
> weblogic does that does that for each ear in the build e.g.
> EAR1
>  WAR
>    lib
>    classes
>    lib
>    classes

Perhaps we're misunderstanding each other.  I know what WebLogic's
APP-INF/lib directory is used for.  The target that assembles my EAR is
defined in the imported "build.xml".  I might be able to change that
common target, but I have to do it in a way that won't affect other
sub-projects that use the same imported build script.  I was thinking I
could make the common target execute a possibly overridden target, but
that seems harder to do than simply have it call a target with an "if"
attribute where the value of that is only defined in the subprojects
that need to copy jars to APP-INF/lib.

Assuming I use that latter strategy, I'm having a little trouble getting
it to work.  In the subproject's "build.xml", I defined a "fileset" with
a particular "id" value, containing the files from that subproject that
I want copied into APP-INF/lib.  In the imported target, I defined a
target with an "if" attribute referencing that same "id" value.
Unfortunately, when the target executes, the "if" test apparently fails,
because it doesn't execute the conditional target.  I don't know whether
the value of the "if" attribute can be the value of the "id" attribute
on a fileset.

> > Subject: How to override targets specified in import file
> > Date: Mon, 21 Sep 2009 12:58:21 -0700
> > From:
> > To:
> >
> > I imagine by now I'm the umpteenth person to ask about something
> > this, but the search patterns to find this don't seem to be that
> simple.
> >
> > I'm working on a small project inside a large EAR.  The small
> > imports the main project build file, which defines the important
> > "create-ear" target.
> >
> > I have a need to modify this so the main "create-ear" target calls a
> > "stub" target that can be overridden in sub-projects to do
> > work in the EAR construction.  If the sub-project doesn't need to do
> any
> > additional work, it wouldn't define the target, so only the empty
> stub
> > would execute.
> >
> > In my case, at least my sub-project has to create an APP-INF/lib
> > directory (if it doesn't exist), and copy certain jars from the
> > sub-project into that created directory.
> >
> > I suppose I could instead make the "stub" instead do real work and
> > assume that the sub-project has defined a "app-inf-jars" property
> (for
> > instance) and create the APP-INF/lib directory and copy in the paths
> > specified in that property, and do nothing if that property isn't
> set.
> > I'm not sure which is more reasonable.
> >
> >
> > To unsubscribe, e-mail:
> > For additional commands, e-mail:
> >
> _________________________________________________________________
> Bing brings you health info from trusted sources.
> TXT_MHEINA_Health_Health_PetAllergy_1x1

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message