Yes, the pom is the easiest way - otherwise we'd need to have one of
each of the Id parameters for each scope.
- Brett
On 10/15/05, Matt Raible <[EMAIL PROTECTED]> wrote:
> On 10/14/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > I share Matt's concern. It'd be nice if I can do something like:
> >
> > <artifact:dependencies scope="runtime"
> > pathId="project.classpath.core" filesetId="project.classpath.fileset">
> > <artifact:pom file="pom.xml" />
> > <artifact:remoteRepository url="${project.repository}" />
> > </artifact:dependencies>
> >
>
> You can do this:
>
> <artifact:dependencies useScope="runtime"...
>
> What I'm trying to avoid was having <artifact:dependencies> 3 times in
> my build.xml file - mainly b/c I want to specify the dependencies
> inline. I'm fine with using a pom like you do - I just wanted to make
> sure that this was the easiest way to do this.
>
> Matt
>
> > There's no way to make dependencies accept a paramter as a filter akin
> > to syslog's levle scheme? Test meaning everything, compile meaning a
> > base set and runtime just a small set? Cue people to chime in w/
> > counter examples if they exist.
> >
> > Dave Brondsema wrote:
> >
> > >Matt Raible wrote:
> > >
> > >
> > >>I'm just starting to play around with Maven 2's Ant tasks. While I
> > >>like the transitive dependencies, it seems like I have to exclude more
> > >>than I'd normally include. ;-)
> > >>
> > >>Onto my question - is it possible to declare a single
> > >><artifact:dependencies>, set the scopes appropriately and then
> > >>copy/include only the compile+runtime JARS in WEB-INF/lib? As far as
> > >>I can tell this is not possible - unless you declare dependencies in a
> > >>pom.xml and use different <artifact:dependencies> for compile, test
> > >>and runtime.
> > >>
> > >>
> > >>
> > >
> > >What's wrong with that? It's good to seperate concerns of {project
> > >dependency info} with {project build functionality}. In my case it's
> > >necessary because we use Ant imports to achieve a generic ant build tool
> > >(same functionality everywhere) with configuration files, like pom.xml,
> > >for each project (different dependencies for each project).
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
