Wayne,
It looks like 'mvn -U package' followed by a 'mvn clean' and a 'mvn
package' again did the trick.
Thanks for your help.
Werner
Wayne Fay wrote:
Try "mvn help:effective-pom" to see all the various configuration
options you've set. Also try "mvn -U package" to perhaps update some
of your plugins.
It sounds like you have something special going on in your
environment. I just did a test run myself, and the resources from test
are definitely not included in target/classes nor are they included in
the JAR. So I think you have some non-standard configuration options
affecting your build.
Wayne
On 9/3/07, Werner Guttmann <[EMAIL PROTECTED]> wrote:
Hi,
did a 'mvn clean' folowed by a 'mvn package', and the JAR file in target
still contains the various resources as stored in src/test/resources.
Werner
Werner Guttmann wrote:
Damien,
Damien Lecan wrote:
When you do mvn package, what is the content of your artifact ?
Let me get back to you with a reply to this question tomomrrow afternoon.
Do you have any special profiles activated when releasing ?
No, no profiles. I basically did a standard 'mvn deploy'.
You have got another problem : your app has been released with
SNAPSHOT dependencies.
I have got an awareness of this. Thanks for pointing this out again.
Look at :
<dependency>
<groupId>org.codehaus.castor</groupId>
<artifactId>castor-jdo</artifactId>
<version>1.1.3-SNAPSHOT</version>
</dependency>
I was not able to found spring-orm 1.1 tag in your svn
(http://svn.castor.codehaus.org/browse/castor/castor-spring/tags)
This is because I have used a 'mvn deploy' to deploy the artefacts to
the Codehaus snapshot repo.
Damien
2007/9/3, Werner Guttmann <[EMAIL PROTECTED]>:
Hi,
let me just restate my own question(s) below. I have had a look at
existing Jira issues, and I cannot find anything that relates to my
problem.
As stated below, I have recently made available a final release of the
Spring ORM for Castor JDO using Maven 2 (standard 'mvn deploy'), and to
my surprise the JAR file uploaded to
http://repository.codehaus.org/org/codehaus/castor/spring-orm/1.1/
included test artefacts as pointed out below - which it should not. And
which is causing quite some problems with our users.
Is anybody aware of a problem like this (where test resources are
included with a deployed JAR) ?
Werner
Werner Guttmann wrote:
Hi,
a few days ago, I have made available a new (snapshot) release of a
Castor module using Maven 2. A user just pointed out to me that the JAR
file in question
http://repository.codehaus.org/org/codehaus/castor/spring-orm/1.1/spring-orm-1.1.jar
includes a few resources at the root level that it should not
include by
default.
A short investigation revealed that the JAR file indeed includes e.g. a
castor.properties file that within the project happens to be living in
src/test/resources, viewable at
http://svn.castor.codehaus.org/browse/castor/castor-spring/trunk/src/test/resources
As far as I remember, I have built this release using Maven 2.0.7. Can
anybody please try to explain what has gone wrong.
Werner
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
