Hi Felix, Just curious what were those two problems?
I did not know off the top of my head if there was a clear way now besides some workarounds I've seen in the past for building eclipse RCP bundles using Maven. I guess this is what you want to do right? I just googled it for the heck of it and there seems to be a lot around this topic in the works. There seems to be a lot here to weed through but it looks like workarounds are still in play. http://www.google.com/search?hl=en&rls=com.microsoft%3A*%3AIE-SearchBox&rlz=1I7ADBR&q=maven+rcp+plugin Perhaps another more specific plugin is in order that just pulls all these approaches together in a clean way. Also I found a PDE maven plugin. Don't know if this has any value towards what you're looking into. Alex On 10/22/07, Felix Knecht <[EMAIL PROTECTED]> wrote: > > For the moment I'm stating 2 problems I haven't found a solution for and > where I think it make sense to write an own plugin: > > - Adapting the <Bundle-Classpath> in Manifest files > <configuration> > <classpath>., ...</classpath> > <artifactItems> > <artifact> > <groupId></groupId> > <artifactId></artifactId> > </artifact> > .... > </artifactItems> > </configuration> > > - Updating jar archives in a given location (e.g. replace plugin.xml) > <configuration> > <!-- Location of the jar archives to replace a file within --> > <location>target/ApacheDirectoryStudio/plugins</location> > <!-- Src of the replacing file --> > > > <replaceSrc>src/main/configuration/org.eclipse.search/plugin.xml</replaceSrc> > <!-- target location in jar archive for the src file --> > <!-- target location in jar archive for the src file --> > <replaceDest>plugin.xml</replaceDest> > <!-- The archives the replace the file within --> > <artifactItems> > <artifact> > <groupId></groupId> > <artifactId></artifactId> > </artifact> > .... > </artifactItems> > </configuration> > > > If nobody nows about a plugins providing such features I'm going to > write one. > > > Regards > Felix >
