I definitely miss something here, that is how to create a product configuration from an existing source-plugin module (that builds fine by the way).
I don't know enough about Eclipse RCP and product configuration to be able to adapt the process to this particular maven setup. Has anyone already managed to do that? 2007/11/19, Sebastien ARBOGAST <[EMAIL PROTECTED]>: > Thanks a lot for all your help Michal. I was afraid of renaming of > renaming the name of those projects without changing the name of tha > packages inside them (which I cannot do), but it worked. Well at least > it compiles and tests pass. > > Now I would like to check that it runs. In the original project, the > one I'm mavenizing, I have a .product file that I could run directly > inside Eclipse to launch my RCP application. Should I keep this file? > And if yes, where is it best to put it? root of the main plugin or > src/main/resources? > > 2007/11/16, eSonic <[EMAIL PROTECTED]>: > > > > > > > > Sebastien Arbogast wrote: > > > > > > I managed to get through the previous issue by creating artificial > > > SNAPSHOT versions of the dependencies Maven asked for. > > > But now I'm facing yet another strange issue. The build fails on a > > > message saying that org.eclipse.test_3.2.0 plugin is missing in > > > eclipse/plugins, but just before that, it does a cleanup on the > > > eclipse installation and deletes a lot of plugins, including > > > org.eclipse.test_3.2.0. > > > > > > > I'm afraid your artificial module solution won't work here. psteclipse does > > the testing by copying your plugins into the Eclipse directory and deleting > > them after testing has been done. It finds the plugins to delete by the > > prefix, so if your own plugins start with org.eclipse it's very likely that > > psteclipse will delete some of Eclipse;s internals, hence the missing > > dependencies. > > > > The only solution I see for you here is changing the naming of your plugins. > > It's not that big of a problem, since Eclipse offers very decent refactoring > > features to do that across different projects. > > > > -- > > Michal > > -- > > View this message in context: > > http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13802852 > > Sent from the Maven - Users mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Sébastien Arbogast > > http://www.sebastien-arbogast.com > -- Sébastien Arbogast http://www.sebastien-arbogast.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
