On 02/23/2013 12:21 AM, Dennis Lundberg wrote: > On 2013-02-22 21:38, t...@apache.org wrote: >> Author: tn >> Date: Fri Feb 22 20:38:59 2013 >> New Revision: 1449206 >> >> URL: http://svn.apache.org/r1449206 >> Log: >> Fix jar deploy, add osgi bundle metadata. >> >> Modified: >> commons/proper/logging/trunk/pom.xml >> >> Modified: commons/proper/logging/trunk/pom.xml >> URL: >> http://svn.apache.org/viewvc/commons/proper/logging/trunk/pom.xml?rev=1449206&r1=1449205&r2=1449206&view=diff >> ============================================================================== >> --- commons/proper/logging/trunk/pom.xml (original) >> +++ commons/proper/logging/trunk/pom.xml Fri Feb 22 20:38:59 2013 >> @@ -189,11 +189,6 @@ under the License. >> <plugin> >> <groupId>org.apache.maven.plugins</groupId> >> <artifactId>maven-jar-plugin</artifactId> >> - <configuration> >> - <archive> >> - <manifestFile>src/conf/MANIFEST.MF</manifestFile> >> - </archive> >> - </configuration> >> <executions> >> <execution> >> <!-- >> @@ -253,6 +248,21 @@ under the License. >> </excludes> >> </configuration> >> </execution> >> + >> + <!-- >> + - Define the full jar last, the deploy/install plugin seems to >> be broken >> + - and takes the last definition from here. >> + --> > > What kinds of problems are you seeing? > This shouldn't be needed.
I thought so too, but if this is not present, the following happens when doing a deploy/install: [INFO] Installing /home/tn/workspace/apache/logging/target/commons-logging-adapters-1.1.2-SNAPSHOT.jar to /home/tn/.m2/repository/commons-logging/commons-logging/1.1.2-SNAPSHOT/commons-logging-1.1.2-SNAPSHOT.jar It looks like the last execution definition overrides something. Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org