OK, here's the situation.

The JIBX bytecode enhancer modifies classes across multiple modules and it
has to work this way because of dependencies between the classes.  This is
executed with a process-classes phase after all the jars are built, but
before the war is built.  Since all the jars are built before the JIBX
plugin can run, the enhanced classes are in the jar modules target/classes
directory but not in the jar.

Another possibility is if there was a way to run the jibx plugin after all
the modules are compiled but before they are assembled into jars that would
work too.

I can live with the jars being built so continuum can work.


stojcevicht wrote:
> 
> maven isn't really setup to be able to "reach into" other projects, to
> use artifacts created in other projects, you should go through jars
> via the repo
> 
> You can however still do it by using the antrun plugin and ant's copy
> target with relative referencing  "../project-a/target/classes", but
> doing so you loose true project independence (and you won't be able to
> add the projects individually to continuum if you use continuum).
> 
> To stop the jar packaging you could:
> 1 - just call mvn compile in the common project, that won't jar up the
> classes
> 2 - change the project type in the pom from jar to pom, but then
> you'll have to setup each plugin you want to call since the jar
> lifecycle won't get called
> 
> 
> Couldn't you just add the class file post processing to the projects
> that the class files are compiled in?
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Building-war-with-multi-module-classes-and-no-module-jars-tp14332309s177p14339854.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to