|
On 07/24/2012 11:08 PM, Craig Foote
wrote:
We have several component projects each with its own
parent pom project as well as a "targetplatform" project housing a
.target file specific for that component's dependencies.
We want to move all these component projects under a "grandparent"
pom project with its own toolkit.target file referenced by
all the component projects.
I can make this work with the component parent continuing to use a
"target-platform-configuration" identifying its original
targetplatform project then that targetplatform project having a
"build-helper-maven-plugin" specifying an "attach-artifact" goal
for, rather then its own component.target, the grandparent's
toolkit.target, i.e. ../../../toolkit.target. I'd
like to remove this relative file path and make each component
specify directly the GAV of the grandparent and its
toolkit.target. But I'm getting an error because my component's
feature needs but can't find org.eclipse.ui - even though
it's in toolkit.target. Any ideas if this can be done or what I'm
doing wrong?
Are you sure your target-platform can be resolved? Can it load into
IDE without trouble? Maybe your feature looks for a version of
org.eclipse.ui that is not the one available in .target file.
On a site note:
* target-platform-validation-plugin:
http://wiki.eclipse.org/Tycho/Release_Notes/0.16#New_Features
* An eclipse-target-platform packaging type:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=383865
HTH,
|
