Forking the bundle:manifest within studio:eclipse is now working, but it's missing all the specific configurations for the bundle plugin (of course). Because of this I'm not sure if it really makes sense to fork the bundle:manifest as well.
WDYT? Regarsd Felix [EMAIL PROTECTED] schrieb: > Author: felixk > Date: Wed Sep 24 02:37:25 2008 > New Revision: 698479 > > URL: http://svn.apache.org/viewvc?rev=698479&view=rev > Log: > Add bundle-plugin as dependency, otherwise it's not found as it is not > registered in the common maven plugin registry (groupId is not o.a.m.plugins > but o.a.felix) > > Modified: > directory/studio-plugin/trunk/pom.xml > > Modified: directory/studio-plugin/trunk/pom.xml > URL: > http://svn.apache.org/viewvc/directory/studio-plugin/trunk/pom.xml?rev=698479&r1=698478&r2=698479&view=diff > ============================================================================== > --- directory/studio-plugin/trunk/pom.xml (original) > +++ directory/studio-plugin/trunk/pom.xml Wed Sep 24 02:37:25 2008 > @@ -95,6 +95,11 @@ > > <dependencies> > <dependency> > + <groupId>org.apache.felix</groupId> > + <artifactId>maven-bundle-plugin</artifactId> > + <version>1.4.3</version> > + </dependency> > + <dependency> > <groupId>org.apache.maven.release</groupId> > <artifactId>maven-release-manager</artifactId> > <version>1.0-alpha-4</version> > > >
