Yes, that's what I did and once again, I stepped further and stalled. Now the issue is that I have a source-plugin depending on org.eclipse.core.runtime. The dependecy is specified in the manifest and I've specified the version I'm depending on (3.3.100), the one that has been scraped and deployed to my local repository. Yet when I try to build this source-plugin, it's looking for version 3.3.100-SNAPSHOT instead of 3.3.100. Any idea? Could this be linked to the fact that my source-plugin's name is something like org.eclipse... ?
2007/11/16, eSonic <[EMAIL PROTECTED]>: > > > > Sebastien Arbogast wrote: > > > > It seems like I'm gonna have to modify psteclipse a little bit. > > > > Not really. It's enough to do what the link you provided suggests - copy the > jar from the plugins directory into Eclipse's main directory as startup.jar > and psteclipse will work just fine. > > I already wrote to Peter asking to work on the issue and have psteclipse > support the new jar placement in some near version of the plugin. > > -- > Michal > -- > View this message in context: > http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13793438 > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
