Skip to main content


Eclipse Community Forums

      Home
Home » Modeling » EMF » [Oomph] Targlet resolve fails for feature with mixed plugin locations
[Oomph] Targlet resolve fails for feature with mixed plugin locations [message #1274515] Fri, 21 March 2014 11:33 Go to next message
Eclipse UserFriend
Hi,

I would like to use a targlet task to import a feature and all included
plugins from a git repo into the workspace. It seems to work by using
the 'feature.group' suffix.

Now I run into this issue:

One of the plugins included by the feature is not part of the git repo.
it is rather provided by a p2 repo. I add the repo to the targlet's
repository list, but the installer reports that it cannot find that plugin.

Any suggestion on how to handle this case?

Below the model and the error:

<?xml version="1.0" encoding="UTF-8"?>
<setup:Project setup:toolVersion="8" xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:setup="http://www.eclipse.org/CDO/releng/setup/1.0" name="ocl"
label="MDT OCL">
<branches name="master">
<setupTasks xsi:type="setup:GitCloneTask"
location="${setup.branch.dir/git/ocl}"
remoteURI="ssh://git.eclipse.org:29418/ocl/org.eclipse.ocl"
checkoutBranch="master"/>
<setupTasks xsi:type="setup:TargletTask" name="OCL"
activeRepositoryList="">
<roots id="org.eclipse.ocl.examples.feature.group"/>
<sourceLocators rootFolder="${setup.branch.dir/git/ocl}"
locateNestedProjects="true"/>
<repositoryLists name="Luna Dependencies">
<p2Repositories url="http://download.eclipse.org/releases/luna"/>
<p2Repositories
url="http://download.eclipse.org/modeling/mdt/ocl/updates/nightly"/>
</repositoryLists>
</setupTasks>
</branches>
</setup:Project>


[2014-03-21 16:05:23] Resolving Target Contents...
[2014-03-21 16:05:23] Reading plug-ins
[2014-03-21 16:05:24] Fetching p2.index from
http://download.eclipse.org/releases/luna/
[2014-03-21 16:05:25] Fetching p2.index from
http://download.eclipse.org/releases/luna/201403140900/
[2014-03-21 16:05:28] Fetching p2.index from
http://download.eclipse.org/releases/luna/201401310900/
[2014-03-21 16:05:30] Fetching p2.index from
http://download.eclipse.org/releases/luna/201312200900/
[2014-03-21 16:05:37] Fetching p2.index from
http://download.eclipse.org/modeling/mdt/ocl/updates/nightly/
[2014-03-21 16:05:38] Fetching p2.index from
http://download.eclipse.org/modeling/mdt/ocl/updates/nightly/4.2.0/
[2014-03-21 16:05:39] Fetching p2.index from
http://download.eclipse.org/modeling/mdt/ocl/updates/nightly/5.0.0/
[2014-03-21 16:05:39] Calculating requirements and dependencies.
[2014-03-21 16:05:40] Cannot complete the request. Generating details.
[2014-03-21 16:05:40] ERROR: org.eclipse.pde.core code=0 Problems
occurred while resolving the target contents
at
org.eclipse.emf.cdo.releng.internal.setup.targlets.TargletContainer.forceUpdate(TargletContainer.java:596)
at
org.eclipse.emf.cdo.releng.setup.impl.TargletTaskImpl.perform(TargletTaskImpl.java:785)
at
org.eclipse.emf.cdo.releng.internal.setup.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:891)
at
org.eclipse.emf.cdo.releng.internal.setup.SetupTaskPerformer.access$0(SetupTaskPerformer.java:868)
at
org.eclipse.emf.cdo.releng.internal.setup.SetupTaskPerformer$2.run(SetupTaskPerformer.java:857)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2333)
at
org.eclipse.emf.cdo.releng.internal.setup.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:851)
at
org.eclipse.emf.cdo.releng.internal.setup.SetupTaskPerformer$1.run(SetupTaskPerformer.java:834)
at
org.eclipse.emf.cdo.releng.internal.setup.ui.ProgressDialog$12$1.run(ProgressDialog.java:608)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
ERROR: org.eclipse.equinox.p2.director code=10053 Cannot complete the
install because one or more required items could not be found.
ERROR: org.eclipse.equinox.p2.director code=0 Software being
installed: OCL Examples and Editors SDK 3.4.0
(org.eclipse.ocl.examples.feature.group 3.4.0)
ERROR: org.eclipse.equinox.p2.director code=0 Missing requirement:
OCL Classic: Ecore Parser,Evaluator 3.4.0 (org.eclipse.ocl.feature.group
3.4.0) requires 'lpg.runtime.java [2.0.17.qualifier]' but it could not
be found
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: OCL Classic:
Ecore/UML Parsers,Evaluator 5.0.0 (org.eclipse.ocl.all.feature.group 5
Re: [Oomph] Targlet resolve fails for feature with mixed plugin locations [message #1274525 is a reply to message #1274515] Fri, 21 March 2014 11:43 Go to previous messageGo to next message
Eclipse UserFriend
Felix,

It's hard to say, but do you know which repo provides lpg.runtime.java.
Perhaps Orbit needs to be in the list of bundles because there's some
bundle OCL depends on that's not part of the release train?


On 21/03/2014 8:33 AM, Felix Dorner wrote:
> Hi,
>
> I would like to use a targlet task to import a feature and all
> included plugins from a git repo into the workspace. It seems to work
> by using the 'feature.group' suffix.
>
> Now I run into this issue:
>
> One of the plugins included by the feature is not part of the git
> repo. it is rather provided by a p2 repo. I add the repo to the
> targlet's repository list, but the installer reports that it cannot
> find that plugin.
>
> Any suggestion on how to handle this case?
>
> Below the model and the error:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <setup:Project setup:toolVersion="8" xmi:version="2.0"
> xmlns:xmi="http://www.omg.org/XMI"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:setup="http://www.eclipse.org/CDO/releng/setup/1.0" name="ocl"
> label="MDT OCL">
> <branches name="master">
> <setupTasks xsi:type="setup:GitCloneTask"
> location="${setup.branch.dir/git/ocl}"
> remoteURI="ssh://git.eclipse.org:29418/ocl/org.eclipse.ocl"
> checkoutBranch="master"/>
> <setupTasks xsi:type="setup:TargletTask" name="OCL"
> activeRepositoryList="">
> <roots id="org.eclipse.ocl.examples.feature.group"/>
> <sourceLocators rootFolder="${setup.branch.dir/git/ocl}"
> locateNestedProjects="true"/>
> <repositoryLists name="Luna Dependencies">
> <p2Repositories url="http://download.eclipse.org/releases/luna"/>
> <p2Repositories
> url="http://download.eclipse.org/modeling/mdt/ocl/updates/nightly"/>
> </repositoryLists>
> </setupTasks>
> </branches>
> </setup:Project>
>
>
> [2014-03-21 16:05:23] Resolving Target Contents...
> [2014-03-21 16:05:23] Reading plug-ins
> [2014-03-21 16:05:24] Fetching p2.index from
> http://download.eclipse.org/releases/luna/
> [2014-03-21 16:05:25] Fetching p2.index from
> http://download.eclipse.org/releases/luna/201403140900/
> [2014-03-21 16:05:28] Fetching p2.index from
> http://download.eclipse.org/releases/luna/201401310900/
> [2014-03-21 16:05:30] Fetching p2.index from
> http://download.eclipse.org/releases/luna/201312200900/
> [2014-03-21 16:05:37] Fetching p2.index from
> http://download.eclipse.org/modeling/mdt/ocl/updates/nightly/
> [2014-03-21 16:05:38] Fetching p2.index from
> http://download.eclipse.org/modeling/mdt/ocl/updates/nightly/4.2.0/
> [2014-03-21 16:05:39] Fetching p2.index from
> http://download.eclipse.org/modeling/mdt/ocl/updates/nightly/5.0.0/
> [2014-03-21 16:05:39] Calculating requirements and dependencies.
> [2014-03-21 16:05:40] Cannot complete the request. Generating details.
> [2014-03-21 16:05:40] ERROR: org.eclipse.pde.core code=0 Problems
> occurred while resolving the target contents
> at
> org.eclipse.emf.cdo.releng.internal.setup.targlets.TargletContainer.forceUpdate(TargletContainer.java:596)
> at
> org.eclipse.emf.cdo.releng.setup.impl.TargletTaskImpl.perform(TargletTaskImpl.java:785)
> at
> org.eclipse.emf.cdo.releng.internal.setup.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:891)
> at
> org.eclipse.emf.cdo.releng.internal.setup.SetupTaskPerformer.access$0(SetupTaskPerformer.java:868)
> at
> org.eclipse.emf.cdo.releng.internal.setup.SetupTaskPerformer$2.run(SetupTaskPerformer.java:857)
> at
> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2333)
> at
> org.eclipse.emf.cdo.releng.internal.setup.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:851)
> at
> org.eclipse.emf.cdo.releng.internal.setup.SetupTaskPerformer$1.run(SetupTaskPerformer.java:834)
> at
> org.eclipse.emf.cdo.releng.internal.setup.ui.ProgressDialog$12$1.run(ProgressDialog.java:608)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> ERROR: org.eclipse.equinox.p2.director code=10053 Cannot complete
> the install because one or more required items could not be found.
> ERROR: org.eclipse.equinox.p2.director code=0 Software being
> installed: OCL Examples and Editors SDK 3.4.0
> (org.eclipse.ocl.examples.feature.group 3.4.0)
> ERROR: org.eclipse.equinox.p2.director code=0 Missing requirement:
> OCL Classic: Ecore Parser,Evaluator 3.4.0
> (org.eclipse.ocl.feature.group 3.4.0) requires 'lpg.runtime.java
> [2.0.17.qualifier]' but it could not be found
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
> dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: OCL Classic:
> Ecore/UML Parsers,Evaluator 5.0.0 (org.eclipse.ocl.all.feature.group 5
>
Re: [Oomph] Targlet resolve fails for feature with mixed plugin locations [message #1274530 is a reply to message #1274525] Fri, 21 March 2014 11:49 Go to previous messageGo to next message
Eclipse UserFriend
On 21/03/2014 16:43, Ed Merks wrote:

> It's hard to say, but do you know which repo provides lpg.runtime.java.
> Perhaps Orbit needs to be in the list of bundles because there's some
> bundle OCL depends on that's not part of the release train?
>

It's in the OCL update site that I added to the targlet repository list.
It is also in Orbit, I tried that too, but the same.

If I remove the source locator it all installs fine, (but well.. no more
sources, so that doesn't serve anything but to confirm that the bundle
is reachable)
Re: [Oomph] Targlet resolve fails for feature with mixed plugin locations [message #1274536 is a reply to message #1274530] Fri, 21 March 2014 11:56 Go to previous messageGo to next message
Eclipse UserFriend
Hi

You can look at the PSF files to see where the relevant imports are found.

The LPG tooling comes from CVS in SourceForge.

Regards

Ed Willink

On 21/03/2014 15:49, Felix Dorner wrote:
> On 21/03/2014 16:43, Ed Merks wrote:
>
>> It's hard to say, but do you know which repo provides lpg.runtime.java.
>> Perhaps Orbit needs to be in the list of bundles because there's some
>> bundle OCL depends on that's not part of the release train?
>>
>
> It's in the OCL update site that I added to the targlet repository
> list. It is also in Orbit, I tried that too, but the same.
>
> If I remove the source locator it all installs fine, (but well.. no
> more sources, so that doesn't serve anything but to confirm that the
> bundle is reachable)
>
>
Re: [Oomph] Targlet resolve fails for feature with mixed plugin locations [message #1274586 is a reply to message #1274536] Fri, 21 March 2014 13:21 Go to previous messageGo to next message
Eclipse UserFriend
On 21/03/2014 16:56, Ed Willink wrote:
> Hi
>
> You can look at the PSF files to see where the relevant imports are found.
>
> The LPG tooling comes from CVS in SourceForge.

And there it shall stay :p. I don't want sources for LPG. Maybe Eike
will comment on it later.
Re: [Oomph] Targlet resolve fails for feature with mixed plugin locations [message #1275593 is a reply to message #1274586] Sun, 23 March 2014 05:27 Go to previous messageGo to next message
Eclipse UserFriend
Hi Felix,

I suggest that you submit a bugzilla. Instead of adding the http: URL of your setup model please attach the version of
that file that we can use to reproduce the problem. Then we should be able to find the cause quickly. Here's a link for
your convenience:
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EMF&component=cdo.releng&version=4.3&bug_severity=enhancement&short_desc=%5BOomph%5D%20Please%20include%20model%20for%20project%20X

The ".qualifier" in the error message makes me suspicious, though. In
http://git.eclipse.org/c/mdt/org.eclipse.ocl.git/tree/features/org.eclipse.ocl-feature/feature.xml I can see that you're
referring to your license feature with a ".qualifier" version. That seems wrong to me and I wonder if it makes a
difference regarding the problem you've reported. Can you check that?

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper



Am 21.03.2014 18:21, schrieb Felix Dorner:
> On 21/03/2014 16:56, Ed Willink wrote:
>> Hi
>>
>> You can look at the PSF files to see where the relevant imports are found.
>>
>> The LPG tooling comes from CVS in SourceForge.
>
> And there it shall stay :p. I don't want sources for LPG. Maybe Eike will comment on it later.
Re: [Oomph] Targlet resolve fails for feature with mixed plugin locations [message #1275596 is a reply to message #1275593] Sun, 23 March 2014 05:32 Go to previous messageGo to next message
Eclipse UserFriend
Am 23.03.2014 10:27, schrieb Eike Stepper:
> Hi Felix,
>
> I suggest that you submit a bugzilla. Instead of adding the http: URL of your setup model please attach the version of
> that file that we can use to reproduce the problem. Then we should be able to find the cause quickly. Here's a link
> for your convenience:
> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EMF&component=cdo.releng&version=4.3&bug_severity=enhancement&short_desc=%5BOomph%5D%20Please%20include%20model%20for%20project%20X
>
> The ".qualifier" in the error message makes me suspicious, though. In
> http://git.eclipse.org/c/mdt/org.eclipse.ocl.git/tree/features/org.eclipse.ocl-feature/feature.xml
Oh, I overlooked this part of the file:

| <plugin
id="lpg.runtime.java"
download-size="0"
install-size="0"
version="2.0.17.qualifier"
unpack="false"/>


It strikes me that the version should be just|"|2.0.17|" or even "0.0.0".

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Re: [Oomph] Targlet resolve fails for feature with mixed plugin locations [message #1276222 is a reply to message #1275596] Mon, 24 March 2014 05:04 Go to previous messageGo to next message
Eclipse UserFriend
Hi Eike,

> | <plugin
> id="lpg.runtime.java"
> download-size="0"
> install-size="0"
> version="2.0.17.qualifier"
> unpack="false"/>
>
>
> It strikes me that the version should be just|"|2.0.17|" or even "0.0.0".

If I use "0.0.0" it works. If I use "2.0.17" without the .qualifier I
get exactly the same error (but without the .qualifier in the error
message).

It's weird, because the version I end up with 0.0.0 is 2.0.17.

Or did you mean to literally put the | in the version attribute, like
this: version="|2.0.17|"?
Re: [Oomph] Targlet resolve fails for feature with mixed plugin locations [message #1276258 is a reply to message #1276222] Mon, 24 March 2014 05:55 Go to previous messageGo to next message
Eclipse UserFriend
Am 24.03.2014 10:04, schrieb Felix Dorner:
> Hi Eike,
>
> > | <plugin
>> id="lpg.runtime.java"
>> download-size="0"
>> install-size="0"
>> version="2.0.17.qualifier"
>> unpack="false"/>
>>
>>
>> It strikes me that the version should be just|"|2.0.17|" or even "0.0.0".
>
> If I use "0.0.0" it works. If I use "2.0.17" without the .qualifier I get exactly the same error (but without the
> .qualifier in the error message).
>
> It's weird, because the version I end up with 0.0.0 is 2.0.17.
>
> Or did you mean to literally put the | in the version attribute, like this: version="|2.0.17|"?
No clue where the pipe symbols came from. Now I think that "2.0.17" is really not good for feature content. Only "0.0.0"
has the special meaning of "take what's available" at feature build/export time, which is the typical usage. Go with it
unless you have other specific problems ;-)

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Re: [Oomph] Targlet resolve fails for feature with mixed plugin locations [message #1276267 is a reply to message #1276258] Mon, 24 March 2014 06:10 Go to previous messageGo to next message
Eclipse UserFriend
On 24/03/2014 10:55, Eike Stepper wrote:
> No clue where the pipe symbols came from. Now I think that "2.0.17" is
> really not good for feature content. Only "0.0.0" has the special
> meaning of "take what's available" at feature build/export time, which
> is the typical usage. Go with it unless you have other specific problems
> ;-)

Ok. Thanks for the help. For info, I created
https://bugs.eclipse.org/bugs/show_bug.cgi?id=430983 where further OCL
Oomph stuff can be discussed.
Re: [Oomph] Targlet resolve fails for feature with mixed plugin locations [message #1286486 is a reply to message #1274515] Sun, 06 April 2014 15:58 Go to previous messageGo to next message
Eclipse UserFriend
I am facing currently the same issue in an e4 tooling oomph setup file.

I have specified a Targlet Task to import the feature

org.eclipse.e4.core.tools.feature.feature.group


The feature.xml file includes amongh others the following plugin dependency

[...]
   <plugin
         id="org.mozilla.javascript"
         download-size="0"
         install-size="0"
         version="1.7.2.qualifier"
         unpack="false"/>
[...]


The setup fails with the following error:

  ERROR: org.eclipse.equinox.p2.director code=10053 Cannot complete the install because one or more required items could not be found.
    ERROR: org.eclipse.equinox.p2.director code=0 Software being installed: Eclipse e4 Tools (Incubation) 0.14.0 (org.eclipse.e4.core.tools.feature.feature.group 0.14.0)
    ERROR: org.eclipse.equinox.p2.director code=0 Missing requirement: Eclipse e4 Tools (Incubation) 0.14.0 (org.eclipse.e4.core.tools.feature.feature.group 0.14.0) requires 'org.mozilla.javascript [1.7.2.qualifier]' but it could not be found



Eike already clarified that the .qualifier suffix is causing the problem and using this suffix is "wrong":

Eike Stepper

I can see that you're
referring to your license feature with a ".qualifier" version. That seems wrong to me and I wonder if it makes a
difference regarding the problem you've reported. Can you check that?


I would appreciate some clarification on the "that seems wrong" part. Can you explain why using the .qualifier suffix is wrong, so that I can submit a bugzilla.
Re: [Oomph] Targlet resolve fails for feature with mixed plugin locations [message #1288268 is a reply to message #1286486] Tue, 08 April 2014 08:16 Go to previous messageGo to next message
Eclipse UserFriend
Hi Nicolaj,

The reasons why I consider the specification of ".qualifier" in feature contents a bad practice are:

1) It doesn't buy you anything.
2) It prevents you from closing the project that contains the included plugin/feature and letting the feature content
entry in question to resolve against your target platform.

You're always better off with an omni version "0.0.0", but I've changed our TargletContainer to cope with ".qualifier"
versions in feature contents more gracefully now.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper



Am 07.04.2014 14:45, schrieb Nicolaj Hoess:
> I am facing currently the same issue in an e4 tooling oomph setup file.
>
> I have specified a Targlet Task to import the feature
>
> org.eclipse.e4.core.tools.feature.feature.group
>
> The http://git.eclipse.org/c/e4/org.eclipse.e4.tools.git/tree/features/org.eclipse.e4.core.tools.feature/feature.xml
> file includes amongh others the following plugin dependency
>
>
> [...]
> <plugin
> id="org.mozilla.javascript"
> download-size="0"
> install-size="0"
> version="1.7.2.qualifier"
> unpack="false"/>
> [...]
>
>
> The setup fails with the following error:
>
>
> ERROR: org.eclipse.equinox.p2.director code=10053 Cannot complete the install because one or more required items
> could not be found.
> ERROR: org.eclipse.equinox.p2.director code=0 Software being installed: Eclipse e4 Tools (Incubation) 0.14.0
> (org.eclipse.e4.core.tools.feature.feature.group 0.14.0)
> ERROR: org.eclipse.equinox.p2.director code=0 Missing requirement: Eclipse e4 Tools (Incubation) 0.14.0
> (org.eclipse.e4.core.tools.feature.feature.group 0.14.0) requires 'org.mozilla.javascript [1.7.2.qualifier]' but it
> could not be found
>
>
>
> Eike already clarified that the .qualifier suffix is causing the problem and using this suffix is "wrong":
>
> Eike Stepper
>> I can see that you're
>> referring to your license feature with a ".qualifier" version. That seems wrong to me and I wonder if it makes a
>> difference regarding the problem you've reported. Can you check that?
>
>
> I would appreciate some clarification on the "that seems wrong" part. Can you explain why using the .qualifier suffix
> is wrong, so that I can submit a bugzilla.
Re: [Oomph] Targlet resolve fails for feature with mixed plugin locations [message #1290954 is a reply to message #1288268] Thu, 10 April 2014 11:34 Go to previous message
Eclipse UserFriend
Eike Stepper wrote on Tue, 08 April 2014 08:16

You're always better off with an omni version "0.0.0", but I've changed our TargletContainer to cope with ".qualifier"
versions in feature contents more gracefully now.


Yea, can confirm that. Build N20140408-0807 is working for me now.
Thanks for the work, Eike Smile
Previous Topic:[CDO] RootResourceID is null; is the repository not yet initialized?
Next Topic:EContentAdapter registered twice
Goto Forum:
  


Current Time: Wed Jul 16 07:23:52 EDT 2025

Powered by FUDForum. Page generated in 0.29036 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly