>>>>> "Tom Huybrechts" <[EMAIL PROTECTED]>:
> On 11/10/06, Steinar Bang <[EMAIL PROTECTED]> wrote:
>> Now, I need to find out if I can make maven pull in the eclipse
>> bundles neccessary for the runtime, as well. This would avoid this
>> as a copying step.
> Declare them as runtime dependencies ?
Yes, that is the obvious approach. My problem is that I don't know
exactly which eclipse bundles to depend on, and from where.
And perhaps I should be careful of doing this, and instead just copy
the runtime from my eclipse installation like I've been doing?
I've just spent some time debugging why I got an SWT compile time
error, and the reason was that my maven copy-dependencies pulled in an
earlier, and presumably incompatible, version of the OSGi framework,
than the one provided by eclipse itself.
So I need to figure out a how to stop it from doing that.
Also, my earlier fragment of copy-dependencies was incomplete. That
one only copied in the files my bundles depended on, but it didn't
copy in my bundles.
To do that, I need this as well:
<execution>
<id>copy</id>
<phase>package</phase>
<goals>
<goal>copy</goal>
</goals>
<configuration>
<artifactItems>
<artifactItem>
<groupId>${project.groupId}</groupId>
<artifactId>${project.artifactId}</artifactId>
<version>${project.version}</version>
<type>${project.packaging}</type>
</artifactItem>
</artifactItems>
<outputDirectory>${user.home}/pde_target_platform/plugins</outputDirectory>
</configuration>
</execution>
This copies in some .pom files as well as the bundle JARs, but they
don't seem to do any harm.
But I have to stop it from copying the older OSGi framework.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
