Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-dev] tycho-compiler-plugin - working with outputjars doesn't compile to

I think this is a fundamental limitation of the maven model:
it has only one output folder for classes per module.
PDE allows more and hence if you use more then we can't map those back to the maven model for intra-reactor dependencies.

Simply copying all classes to the output folder is not a valid solution because then all classes would end up merged in the main jar.

AFAICT this is one of the points where the maven and PDE build model simply can't be mapped 1:1.
As such it's a limitation for non-OSGi aware tools from the maven world such as sonar (tycho itself supports all the nested jar/dir cases).
For details see 

If you can provide a sample project demonstrating the sonar issue, we may be able to suggest a workaround.


From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Juan Alonso
Sent: Freitag, 25. Mai 2012 13:20
To: Tycho developers list
Subject: [tycho-dev] tycho-compiler-plugin - working with outputjars doesn't compile to

Hi all,

We have some problems building a feature with bundles that contains outputjars in the file because tycho-compiler-plugin compiles to: jarName + "-classes".

Our problems came when trying to execute Sonar because sonar (and all others) is looking for the value of variable I'm wondering if the problem is when we execute maven in two different steps. 
1. maven install 
2. maven sonar:sonar (in another jenkins/hudson job for example)
But, also with one step, if tycho sets the to the outputjar folder, What will be the variable value with multiple outputjars?

I attached a possible patch, that works for me. I'm working with tycho 0.14.x

Rgds, Juan.

Back to the top