Hi Clement, Thanks for the pointers.
Regards, Gokturk On Wed, Apr 4, 2012 at 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.htmlgives > you 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 > >
