Sebastien Arbogast wrote:
>
> Obviously, I'm missing something with version numbers here, as:
> - the version in the POM for com.mycompany.framework.common is
> 1.0-SNAPSHOT
> - the resulting version in the manifest after running
> psteclipse:eclipse-plugin is 1.0
> - the version com.mycompany.framework.eclipse.rcp is looking for is
> 1.0.0-SNAPSHOT
>
Well, I had trouble with versions initially as well. Here's the way to
handle your issue:
1. The binary plugin that is being depended on should be added to the
MANIFEST.MF file through Eclipse (in the dependent plugin) and NOT in the
dependent's POM file, ie.
A - is binary
B - depends on A
so A is added as a plugin dependency in B's MANIFEST.MF.
2. When adding A to B's MANIFEST supply a version - Eclipse expects here a
3-part number (ie. x.x.x, like 1.0.0), so even if you write 1.0 it WILL
CHANGE IT to 1.0.0.
3. psteclipse will parse the MANIFEST of B at compile time, find the
dependency on A and add the -SNAPSHOT suffix, so...
4. A's version as declared in the POM should actually be:
<version>1.0.0-SNAPSHOT</version>
--
Michal
--
View this message in context:
http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13789763
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
