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]
