A1) Because you are specifying your source directory as 'src'. The standard
is src/main/java (inherited from the super pom). This would treat
src/spring/context as source.
A2) Not sure, probably a knock-on effect of the above
If you are going to deviate from the standard directory structure it is
worth explicitly setting all the paths normally set in the super pom so you
can achieve some clarity when looking through the pom and when trying to
debug unexpected outcomes.
----- Original Message -----
From: "Jeff Mutonho" <[EMAIL PROTECTED]>
To: "Maven Users List" <[email protected]>
Sent: Thursday, June 22, 2006 4:10 PM
Subject: Re: jarring non class files
On 6/22/06, Kieran Brady <[EMAIL PROTECTED]> wrote:
Specify them as resources:
...
<build>
<resources>
<resource>
<directory>src/spring/context</directory>
</resource>
...
HTH :)
Thanx.My build section in my pom reads :
<build>
<sourceDirectory>src</sourceDirectory>
</build>
(i.e I do not specify any <resources> section) .How ever when bundle
this the resulting jar has the following structure
spring/context/databaseContext.xml
spring/context/ldapContext.xml
com/blah blah blah....
databaseContext.xml
ldapContext.xml
Q1)Why is maven including these in jar even though I haven't
specifiying them yet?
Q2)The two xml files are NOT suppose to be in the root directory of
the jar , but here they are being included twice(i.e both in the root
directory of the jar as well as in spring/context) .How can I prevent
this from happening?
---------------------------------------------------------------------
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]
