-
1. Re: how to release assembly artifacts
pgier Feb 26, 2008 6:35 PM (in response to starksm64)There isn't any way to release just the client jar by itself. You would have to do a release of the project, and the client jar can be deployed to the repository at the same time as the main jar. When a release is done, maven just runs "deploy" so anything that happens in a snapshot deploy will also happen in a release.
I'm not sure I understand the problem with having two separate projects. Couldn't you just have one for the client and one for the server and then release them separately? -
2. Re: how to release assembly artifacts
starksm64 Feb 26, 2008 6:41 PM (in response to starksm64)They are not disjoint code bases. The client jar is a subset of the server jar, so its an artifical separation to have two projects. I see plugins like the ejb plugin support the concept of a client jar.
-
3. Re: how to release assembly artifacts
starksm64 Feb 26, 2008 6:47 PM (in response to starksm64)The previous version did have an essentially empty project that build the client jar from the server project:
https://svn.jboss.org/repos/repository.jboss.org/maven2/org/jboss/jnp-client/5.0.0.Beta3/jnp-client-5.0.0.Beta3.pom<build> <plugins> <plugin> <artifactId>maven-antrun-plugin</artifactId> <version>1.1</version> <executions> <execution> <id>buildjar</id> <phase>package</phase> <goals> <goal>run</goal> </goals> <configuration> <tasks> <jar jarfile="${basedir}/target/jnp-client-5.0.0.Beta3.jar" update="true" manifest="${basedir}/../jnpserver/src/etc/default.mf"> <fileset dir="${basedir}/../jnpserver/target/classes"> <include name="org/jnp/interfaces/**"></include> <include name="org/jboss/naming/**"></include> </fileset> <fileset file="${basedir}/JBossORG-EULA.txt"></fileset> </jar> </tasks> </configuration> </execution> </executions> <inherited>true</inherited> </plugin> </plugins> </build>
I guess I'll have to go back to that.