Hi Henrique,
On 24/04/2008, at 1:06 AM, Henrique Prange wrote:
Hi Lachlan,
On Tue, Apr 22, 2008 at 9:31 PM, Lachlan Deck
<[EMAIL PROTECTED]> wrote:
My dependent frameworks are not of packaging woframework, but jar
I think you really should try to use the woframework packaging. You
will have to write much less configuration.
There was hardly any actually.
-- parent pom --
<?xml version="1.0" encoding="UTF-8"?>
<project ...>
...
<build>
<sourceDirectory>src</sourceDirectory>
<testSourceDirectory>tests</testSourceDirectory>
<resources>
<resource>
<targetPath>Resources</targetPath>
<filtering>true</filtering>
<directory>../src/main/resources</directory>
</resource>
<resource>
<targetPath>Resources</targetPath>
<filtering>false</filtering>
<directory>Components</directory>
</resource>
<resource>
<targetPath>Resources</targetPath>
<filtering>false</filtering>
<directory>Resources</directory>
</resource>
<resource>
<targetPath>WebServerResources</targetPath>
<filtering>false</filtering>
<directory>WebServerResources</directory>
</resource>
</resources>
</build>
</project>
Then all the child modules are quite short.
- so I can't see what options/configurations to provide to bundle
the relevant dependent
jars (or indeed - what scope they should be).
Why do you need the dependencies packaged inside a woframework jar?
The dependencies are declared in the pom.xml. When you declare a
woframework as dependency, Maven automatically adds the transitive
dependencies to your project. For example, if you have a woframework
that depends upon a library A. When you add this woframework to a
project, Maven will add the dependency A transitively to your project.
Okay. Thanks for the explanation.
with regards,
--
Lachlan Deck
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
