On 10/15/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> On 10/15/05, Matt Raible <[EMAIL PROTECTED]> wrote:
> > This seems to work, but I've had to exclude a lot of dependencies in
> > order to trim the JARs down to what I had previous with
> > all-jars-in-CVS. The one I can't seem to get rid of is
> > servlet-api-2.4.jar. Is there a quick way to find out which
> > dependency is causing it to be included?
>
> verbose="true" shows the dependency tree. Probably what you want to do
> is use it for compiling, so you should explicitly include it, but set
> the scope as "provided".
>
Thanks, that's a useful setting to see everything. I do have the
scope set to provided. My guess is the following <copy> task ignores
this setting.
<mkdir dir="${build.dir}/jars"/>
<copy todir="${build.dir}/jars">
<fileset refid="compile.fileset"/>
<fileset refid="runtime.fileset"/>
<mapper type="flatten"/>
</copy>
As far as the pom.xml, I can't seem to figure out how to exclude
certain classes in my test tree from running. I have a base class
that I changed to abstract (didn't help) and a jWebUnit test that I
want to exclude during normal testing. How do I exclude the classes?
Their patterns are *TestCase and *WebTest - where as the rest end in
*Test.
Lastly, is it possible to include XML from another file in a POM, or
is the easiest way to use entity includes? I have a base pom.xml that
will need manipulation when other packages are installed (i.e.
persistence framework or web framework). I figure the easy way to do
this is to separate those out into separate files and allow the
installer to overwrite them.
Thanks,
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
