On 10/14/05, Dave Brondsema <[EMAIL PROTECTED]> 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).
>
There's nothing wrong with it per se. I just want to know if it's
possible to do the simple way (single build.xml file) as well as the
more complicated way (build.xml + pom.xml). Using a pom.xml certainly
makes sense for larger projects, but what about a simple 5 page, 15
class web application? Also, I find the Ant task syntax more consice
to read b/c it uses attributes over elements.
Of course, since most folks on this list probably use Maven (and love
the pom.xml), I'm probably barking up the wrong tree. ;-)
Matt
> --
> Dave Brondsema
> Software Developer
> Cornerstone University
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
