Could you please explain me what's the difference with using an assembly ?
I've setup an assembly that creates a Jar with all classes from my two modules. The resulting Jar is fine according to my goal of a single artifact from tow maven modules. This doesn't solve the issue that the deployed POM is set with packaging "pom". I could use XSLT to convert the POM to "jar" packaging prior to deploy. Nico. 2006/12/14, Wendy Smoak <[EMAIL PROTECTED]>:
On 12/14/06, nicolas de loof <[EMAIL PROTECTED]> wrote: > I also tried to use multiple compiler execution with various > includes/excludes, but I'm using JDBC code, which API changed between Java > 1.3 and 1.4. I can't have all my code compile in my IDE when using a single > project for all classes. Using 2 maven modules with different JDK configured > make it possible. What about using the dependency plugin to unpack the contents of the two jars built with different jdk version, then packaging up the result as a new jar? -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
