Stuart, Once again thanks for the reply. Regarding *auto-generate IDE files* can you please let me know where I can find this property? Where is it in the top-level pom. Which Plugin is it part of?
Thanks Matt On Tue, Aug 2, 2011 at 10:01 AM, Stuart McCulloch <[email protected]> wrote: > On 2 Aug 2011, at 15:40, Matt Madhavan wrote: > > HI Stuart, > I turned on the debug for mvn install! I looked at the trace. I do not see > MavenFelix Plugin doing this. But I see output from Pax Plugin doing this as > follows: > > > That suggests you've uncommented the "auto-generate IDE files" section in > the top-level pom.xml file which means that it will try to regenerate the > Eclipse files on every install (using the Felix maven-bundle-plugin for the > manifest). Commenting that section back out will stop the regeneration on > each install and you can then generate the files as you need them from the > command-line (remember to refresh the project otherwise Eclipse won't know > the file has changed on the file-system, which can be the cause of some red > markers). > > If you're doing a lot of Eclipse development then you might want to look at > Maven-Tycho: > > http://tycho.sonatype.org/ > > since this has much better integration with Eclipse - unfortunately the > support for Eclipse development in pax-construct hasn't been touched for a > while and is more static (ie. generation of Eclipse files) > > You could also look at the following configuration: > > > http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html#ApacheFelixMavenBundlePlugin%28BND%29-Eclipse%2FPDEintegration > > to generate your manifests - although you may find the same problems as > before with red markers (at least until you refresh the project), since > Eclipse/PDE likes to be in control of the manifest (ie. the same > manifest-first approach used in Tycho) > > I should also point to bndtools as an alternative for Eclipse/OSGi > development: > > http://bndtools.org/ > > although the Maven integration for bndtools is still work-in-progress. > > [DEBUG] Configuring mojo 'org.ops4j:maven-pax-plugin:1.5:eclipse' --> > [DEBUG] (s) addGroupIdToProjectName = false > [DEBUG] (s) addVersionToProjectName = false > [DEBUG] (s) buildOutputDirectory = > C:\NewWorkSpace\JDKVersionTest\com.pax.jdkversiontest\com.pax.jdkversiontest.bundle1\target\classes > [DEBUG] (s) executedProject = MavenProject: unknown:empty-project:0 @ > [DEBUG] (f) limitProjectReferencesToWorkspace = false > [DEBUG] (s) localRepository = Repository[local|file://C:\Documents and > Settings\I304326\.m2\repository] > *[DEBUG] (f) manifest = > C:\NewWorkSpace\JDKVersionTest\com.pax.jdkversiontest\com.pax.jdkversiontest.bundle1\META-INF\MANIFEST.MF > * > [DEBUG] (f) packaging = bundle > [DEBUG] (f) pde = false > [DEBUG] (s) project = MavenProject: > com.pax.jdkversiontest:com.pax.jdkversiontest.bundle1:1.0.0 @ > C:\NewWorkSpace\JDKVersionTest\com.pax.jdkversiontest\com.pax.jdkversiontest.bundle1\pom.xml > [DEBUG] (s) reactorProjects = [MavenProject: > com.pax.jdkversiontest:com.pax.jdkversiontest.bundle1:1.0.0 @ > C:\NewWorkSpace\JDKVersionTest\com.pax.jdkversiontest\com.pax.jdkversiontest.bundle1\pom.xml] > [DEBUG] (s) remoteArtifactRepositories = [Repository[central| > http://central]] > [DEBUG] (f) skip = false > > And to verify and double check, I had the following entry on the Felix > Plugin: > > <plugin> > <groupId>org.apache.felix</groupId> > <artifactId>maven-bundle-plugin</artifactId> > <extensions>true</extensions> > <configuration> > <manifestLocation>*MY-META/META-INF*</manifestLocation> > > I got one manifest.mf generated at the MY-META/META-INF folder and one more > at the META-INF folder. > > My hunch is that PaxPlugin invokes the Felix Plug in to create this folder! > > Any ideas please? I'm probably involved with the biggest/largest OSGi > enterprise project now, for my client. My client also has teams/folks from > 'big' firms involved in OSGi project for which I'm creating the standard. I > have to be extra studious. > > All the help is appreciated. > > Thanks in advance! > > Matt > > > > > > > > > > > > > > > > On Tue, Aug 2, 2011 at 9:22 AM, Stuart McCulloch <[email protected]>wrote: > >> On 2 Aug 2011, at 15:15, Matt Madhavan wrote: >> >> > Hello, >> > In PAX generated projects, when I do mvn pax:install the >> maven-pax-plugin automatically creates a META-INF/manifest.mf in the bundle >> root! Often times eclipse marks this in error (for whatever reason even >> though all the imported packages are available). So pretty much all my >> bundle projects are marked as error in eclipse and this is ugly! >> > >> > The new folks I'm training/introducing OSGi/PAX think something is wrong >> with the project or OSGi is problamatic etc. >> > >> > I would rather have the maven-pax-plugin not generate the >> META-INF/manifest.mf at all and rather use the maven-felix-plugin to >> generate (I think this should be the right plugin to do this job anyway!) >> >> the manifest is generated by the maven-bundle-plugin from Felix - all the >> pax plugin does it move it to where Eclipse PDE expects it (and fix any >> relative references) >> >> > Any ideas on how to prevent MavenPaxPlugin from generating >> META-INF/manifest.mf? >> > >> > Thanks in advance! >> > >> > Matt >> > _______________________________________________ >> > general mailing list >> > [email protected] >> > http://lists.ops4j.org/mailman/listinfo/general >> >> >> _______________________________________________ >> general mailing list >> [email protected] >> http://lists.ops4j.org/mailman/listinfo/general >> > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > > > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > >
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
