hi, @ide-support: since you get an additional all-in-one sources jar file, it should work. i've created external codi examples which use the all-in-one jar of codi and the ide support works perfectly.
@osgi: if there are restrictions, we should improve the shade plugin. (for now: osgi users just can't use this optional all-in-one jar file - if we document it, it shouldn't be a problem.) @use-case: we should really get rid of the shared module. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/11/8 Leonardo Uribe <lu4...@gmail.com> > Hi > > Unfortunately, maven-shade-plugin has some unwanted side effects. > > - The source jar file is not updated too, so if we "shade" shared, the > sources are not updated. In theory, the source jar is used by IDEs like > Eclipse or Netbeans to show the source file of a .class. > - It does not play well with osgi bundle plugin (the one that create > manifest.mf). The problem is the manifest is generated before "shade", and > we need the later. Really that one is a problem related to maven itself. > > The only valid use case I found where maven-shade-plugin fits well is with > implee6 module, but anyway it was required to do some hacks to make bundle > plugin works well. > > regards, > > Leonardo Uribe >
