Hi, On Tue, Apr 10, 2012 at 11:48 AM, Clement Escoffier < [email protected]> wrote:
> Hi, > > On 07.04.2012, at 14:04, Göktürk Gezer wrote: > > > Hi again, > > > > I deployed external builders but, for %100 consistency with maven and > > eclipse, is it possible to instruct maven-ipojo-plugin to update manifest > > and classes in project foldet with manipulated versions during maven > build ? > > > > Unfortunately no. The maven-ipojo-plugin does not have the options to use > the directory manipulation. It can be a nice improvement. > Then let me create a jira for this and start working on it: https://issues.apache.org/jira/browse/FELIX-3452 Question is, in which shape we should integrate that facility into maven build: * A new goal for directoryManipulation for use in 'compile' phase * A new boolean property for ipojo-bundle goal to unpack manipulated content into project folder * Modification of current mojo to also accept directory paths as manipulation candidate * Or combination of above approaches, I'll be glad if you give me a pointers on how would you prefer it to be handled. Regards, Gokturk > Regards, > > Clement > > > Thanks, > > Göktürk > > On Apr 4, 2012 8:08 PM, "Clement Escoffier" <[email protected] > > > > wrote: > > > >> Hi, > >> > >> You can plug an external builder using Ant doing the manipulation and > the > >> manifest change 'in-place'. So, every time you change something, the > >> builder call an Ant target (using the iPOJO Ant Task) and you get your > data > >> updated. > >> You can download the project template here: > >> > http://felix.apache.org/site/apache-felix-ipojo-eclipse-integration.data/MyiPOJOBundle-1.4.2.zip > >> > >> The page > >> > http://felix.apache.org/site/apache-felix-ipojo-eclipse-integration.htmlgivesyou > some details. > >> > >> Regards, > >> > >> Clement > >> > >> On 04.04.2012, at 16:06, Göktürk Gezer wrote: > >> > >>> Hi Everyone, > >>> > >>> We're using IPojo inside some Eclipse Plugin project for Eclipse > itself. > >>> > >>> Problem is: > >>> > >>> IPojo manipulates the classes and generate new MANIFEST.MF file with > >>> IPojo-Components contents. No problem with generated bundle but while > >>> debugging, Eclipse picks the MANIFEST.MF in [PROJECT]/META-INF/ > directory > >>> and also loads the classes in [PROJECT]/target/classes which is default > >>> behaviour. So clearly the problem is, these two aspects are not synched > >>> with the manipulated bundle, thus, wrong MANIFEST.MF and nonmanipulated > >>> classes are loaded into Equinox. > >>> > >>> I have to manually change those things for our plugins to work > correctly > >>> inside Eclipse, which is not an acceptable solution. I would like to > know > >>> if there is some sophisticated method to handle these issues. > >>> > >>> Regards, > >>> Gokturk > >> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
