Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » problems when using Oomph with RAP
problems when using Oomph with RAP [message #1735079] Wed, 15 June 2016 11:40 Go to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1762
Registered: July 2009
Location: Firenze, Italy
Senior Member
Hi

in the Eclipse project EMF Parsley we've always been using Oomph with a
setup,
http://git.eclipse.org/c/emf-parsley/org.eclipse.emf-parsley.git/tree/devtools/org.eclipse.emf.parsley.oomph/EMFParsley.setup
, with two subprojects: RCP for materializing a development workspace
for the RCP version, and RAP for developing the RAP version.

It has always worked. Now, when switching to Neon rimrel, the RCP works
as before but the RAP version of the workspace always fails when
resolving the targlet with problems of the shape

ERROR: org.eclipse.equinox.p2.director code=0 Software being
installed: artificial_root 1.0.0.v1465989132800
ERROR: org.eclipse.equinox.p2.director code=0 Software being
installed: workspace_requirements 1.0.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root
1.0.0.v1465989132800
ERROR: org.eclipse.equinox.p2.director code=0 To:
org.eclipse.rap.examples.feature.feature.group 0.0.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
0.8.0.v20160509-1054 (org.eclipse.emf.parsley 0.8.0.v20160509-1054)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
org.eclipse.jface.databinding 1.2.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
0.8.0.v20160509-1054 (org.eclipse.emf.parsley 0.8.0.v20160509-1054)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
org.eclipse.ui 3.5.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
1.0.0.v20160524-1223 (org.eclipse.emf.parsley 1.0.0.v20160524-1223)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
org.eclipse.jface.databinding 1.2.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
1.0.0.v20160524-1223 (org.eclipse.emf.parsley 1.0.0.v20160524-1223)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
org.eclipse.ui 3.5.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
1.0.0.v20160601-1323 (org.eclipse.emf.parsley 1.0.0.v20160601-1323)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
org.eclipse.jface.databinding 1.2.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
1.0.0.v20160601-1323 (org.eclipse.emf.parsley 1.0.0.v20160601-1323)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
org.eclipse.ui 3.5.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
0.8.0.v20160509-1054 (org.eclipse.emf.parsley.dsl 0.8.0.v20160509-1054)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
org.eclipse.emf.parsley 0.0.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
1.0.0.v20160524-1223 (org.eclipse.emf.parsley.dsl 1.0.0.v20160524-1223)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
org.eclipse.emf.parsley 0.0.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
1.0.0.v20160601-1323 (org.eclipse.emf.parsley.dsl 1.0.0.v20160601-1323)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
org.eclipse.emf.parsley 0.0.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From:
org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160524-1223
(org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160524-1223)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
org.eclipse.emf.parsley.dsl 0.0.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From:
org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160601-1323
(org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160601-1323)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
org.eclipse.emf.parsley.dsl 0.0.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Examples
3.1.0.20160422-0843 (org.eclipse.rap.examples.feature.feature.group
3.1.0.20160422-0843)
ERROR: org.eclipse.equinox.p2.director code=0 To:
org.eclipse.rap.feature.feature.group [3.1.0,4.0.0)
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
3.1.0.20160511-1131 (org.eclipse.rap.feature.feature.group
3.1.0.20160511-1131)
ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui 0.0.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
3.1.0.20160523-1225 (org.eclipse.rap.feature.feature.group
3.1.0.20160523-1225)
ERROR: org.eclipse.equinox.p2.director code=0 To:
org.eclipse.jface.databinding 0.0.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
3.1.0.20160527-1719 (org.eclipse.rap.feature.feature.group
3.1.0.20160527-1719)
ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui 0.0.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From:
workspace_requirements 1.0.0
ERROR: org.eclipse.equinox.p2.director code=0 To:
org.eclipse.emf.parsley.dsl.ide 0.0.0

I see many things that are strange to me:

ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
3.1.0.20160511-1131 (org.eclipse.rap.feature.feature.group
3.1.0.20160511-1131)
ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui 0.0.0
ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
3.1.0.20160523-1225 (org.eclipse.rap.feature.feature.group
3.1.0.20160523-1225)
ERROR: org.eclipse.equinox.p2.director code=0 To:
org.eclipse.jface.databinding 0.0.0

RAP should have its version of org.eclipse.ui, and it should get that
version...

ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
0.8.0.v20160509-1054 (org.eclipse.emf.parsley.dsl 0.8.0.v20160509-1054)
ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
org.eclipse.emf.parsley 0.0.0

The Parsley DSL is not part of the targlet (it's only installed in the
IDE, but not in the targlet for the RAP version). I guess it finds it
in the Neon update site, but it's never referenced in the RAP subproject
targlet specification.

The tycho build works for RAP: we use a TP using the
includeMode="slicer" which is a strict requirement for RAP (from what I
understand).

Has anything changed in the Oomph targlet resolution so that a "slicer"
mode has to be made explicit?

Thanks in advance
Lorenzo

--
Prof. Lorenzo Bettini, Computer Science, DISIA, Univ. Firenze
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book


Re: problems when using Oomph with RAP [message #1735097 is a reply to message #1735079] Wed, 15 June 2016 14:10 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 31048
Registered: July 2009
Senior Member
Lorenzo,

If at least one Targlet specifies includeAllRequirements as false, then
all requirements are essentially treated as optional so failure to
resolve something should just result in it being absent, not failing the
resolution overall.


On 15.06.2016 13:41, Lorenzo Bettini wrote:
> Hi
>
> in the Eclipse project EMF Parsley we've always been using Oomph with a
> setup,
> http://git.eclipse.org/c/emf-parsley/org.eclipse.emf-parsley.git/tree/devtools/org.eclipse.emf.parsley.oomph/EMFParsley.setup
> , with two subprojects: RCP for materializing a development workspace
> for the RCP version, and RAP for developing the RAP version.
>
> It has always worked. Now, when switching to Neon rimrel, the RCP works
> as before but the RAP version of the workspace always fails when
> resolving the targlet with problems of the shape
>
> ERROR: org.eclipse.equinox.p2.director code=0 Software being
> installed: artificial_root 1.0.0.v1465989132800
> ERROR: org.eclipse.equinox.p2.director code=0 Software being
> installed: workspace_requirements 1.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root
> 1.0.0.v1465989132800
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.rap.examples.feature.feature.group 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley 0.8.0.v20160509-1054)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.jface.databinding 1.2.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley 0.8.0.v20160509-1054)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.ui 3.5.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley 1.0.0.v20160524-1223)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.jface.databinding 1.2.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley 1.0.0.v20160524-1223)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.ui 3.5.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley 1.0.0.v20160601-1323)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.jface.databinding 1.2.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley 1.0.0.v20160601-1323)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.ui 3.5.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley.dsl 0.8.0.v20160509-1054)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.emf.parsley 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley.dsl 1.0.0.v20160524-1223)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.emf.parsley 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley.dsl 1.0.0.v20160601-1323)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.emf.parsley 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From:
> org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160524-1223
> (org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160524-1223)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.emf.parsley.dsl 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From:
> org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160601-1323
> (org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160601-1323)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.emf.parsley.dsl 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Examples
> 3.1.0.20160422-0843 (org.eclipse.rap.examples.feature.feature.group
> 3.1.0.20160422-0843)
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.rap.feature.feature.group [3.1.0,4.0.0)
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
> 3.1.0.20160511-1131 (org.eclipse.rap.feature.feature.group
> 3.1.0.20160511-1131)
> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
> 3.1.0.20160523-1225 (org.eclipse.rap.feature.feature.group
> 3.1.0.20160523-1225)
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.jface.databinding 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
> 3.1.0.20160527-1719 (org.eclipse.rap.feature.feature.group
> 3.1.0.20160527-1719)
> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From:
> workspace_requirements 1.0.0
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.emf.parsley.dsl.ide 0.0.0
>
> I see many things that are strange to me:
>
> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
> 3.1.0.20160511-1131 (org.eclipse.rap.feature.feature.group
> 3.1.0.20160511-1131)
> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
> 3.1.0.20160523-1225 (org.eclipse.rap.feature.feature.group
> 3.1.0.20160523-1225)
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.jface.databinding 0.0.0
>
> RAP should have its version of org.eclipse.ui, and it should get that
> version...
>
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley.dsl 0.8.0.v20160509-1054)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.emf.parsley 0.0.0
>
> The Parsley DSL is not part of the targlet (it's only installed in the
> IDE, but not in the targlet for the RAP version). I guess it finds it
> in the Neon update site, but it's never referenced in the RAP subproject
> targlet specification.
>
> The tycho build works for RAP: we use a TP using the
> includeMode="slicer" which is a strict requirement for RAP (from what I
> understand).
>
> Has anything changed in the Oomph targlet resolution so that a "slicer"
> mode has to be made explicit?
>
> Thanks in advance
> Lorenzo
>
Re: problems when using Oomph with RAP [message #1735105 is a reply to message #1735097] Wed, 15 June 2016 14:42 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1762
Registered: July 2009
Location: Firenze, Italy
Senior Member
Hi Ed

indeed by setting the targlet with includeAllRequirements to false, RAP
features and bundles can be resolved without taking eclipse.ui bundles
(and using the counterparts from RAP).

The problem that still remains is that I reduced the targlet part for
our source project (for RAP) to a single bundle,
https://git.eclipse.org/r/#/c/75317/1/devtools/org.eclipse.emf.parsley.oomph/EMFParsley.setup,
i.e.,

org.eclipse.emf.parsley.rap.runtime which depends on
org.eclipse.emf.parsley.runtime.common

which in turn has no other dependencies on our projects, so I'd expect
to have only two projects in the workspace.

During targlet resolution, Oomph imports in the workspace also other
Parsley projects, including the RCP ones and DSL projects... I really
have no idea on why it does that...

any clue of why I'm experiencing such a behavior?

thanks in advance
Lorenzo

On 15/06/2016 16:10, Ed Merks wrote:
> Lorenzo,
>
> If at least one Targlet specifies includeAllRequirements as false, then
> all requirements are essentially treated as optional so failure to
> resolve something should just result in it being absent, not failing the
> resolution overall.
>
>
> On 15.06.2016 13:41, Lorenzo Bettini wrote:
>> Hi
>>
>> in the Eclipse project EMF Parsley we've always been using Oomph with a
>> setup,
>> http://git.eclipse.org/c/emf-parsley/org.eclipse.emf-parsley.git/tree/devtools/org.eclipse.emf.parsley.oomph/EMFParsley.setup
>>
>> , with two subprojects: RCP for materializing a development workspace
>> for the RCP version, and RAP for developing the RAP version.
>>
>> It has always worked. Now, when switching to Neon rimrel, the RCP works
>> as before but the RAP version of the workspace always fails when
>> resolving the targlet with problems of the shape
>>
>> ERROR: org.eclipse.equinox.p2.director code=0 Software being
>> installed: artificial_root 1.0.0.v1465989132800
>> ERROR: org.eclipse.equinox.p2.director code=0 Software being
>> installed: workspace_requirements 1.0.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root
>> 1.0.0.v1465989132800
>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>> org.eclipse.rap.examples.feature.feature.group 0.0.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley 0.8.0.v20160509-1054)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>> org.eclipse.jface.databinding 1.2.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley 0.8.0.v20160509-1054)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>> org.eclipse.ui 3.5.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley 1.0.0.v20160524-1223)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>> org.eclipse.jface.databinding 1.2.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley 1.0.0.v20160524-1223)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>> org.eclipse.ui 3.5.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley 1.0.0.v20160601-1323)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>> org.eclipse.jface.databinding 1.2.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley 1.0.0.v20160601-1323)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>> org.eclipse.ui 3.5.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley.dsl 0.8.0.v20160509-1054)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>> org.eclipse.emf.parsley 0.0.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
>> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley.dsl 1.0.0.v20160524-1223)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>> org.eclipse.emf.parsley 0.0.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
>> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley.dsl 1.0.0.v20160601-1323)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>> org.eclipse.emf.parsley 0.0.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>> org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160524-1223
>> (org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160524-1223)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>> org.eclipse.emf.parsley.dsl 0.0.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>> org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160601-1323
>> (org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160601-1323)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>> org.eclipse.emf.parsley.dsl 0.0.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Examples
>> 3.1.0.20160422-0843 (org.eclipse.rap.examples.feature.feature.group
>> 3.1.0.20160422-0843)
>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>> org.eclipse.rap.feature.feature.group [3.1.0,4.0.0)
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>> 3.1.0.20160511-1131 (org.eclipse.rap.feature.feature.group
>> 3.1.0.20160511-1131)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui
>> 0.0.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>> 3.1.0.20160523-1225 (org.eclipse.rap.feature.feature.group
>> 3.1.0.20160523-1225)
>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>> org.eclipse.jface.databinding 0.0.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>> 3.1.0.20160527-1719 (org.eclipse.rap.feature.feature.group
>> 3.1.0.20160527-1719)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui
>> 0.0.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>> workspace_requirements 1.0.0
>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>> org.eclipse.emf.parsley.dsl.ide 0.0.0
>>
>> I see many things that are strange to me:
>>
>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>> 3.1.0.20160511-1131 (org.eclipse.rap.feature.feature.group
>> 3.1.0.20160511-1131)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui 0.0.0
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>> 3.1.0.20160523-1225 (org.eclipse.rap.feature.feature.group
>> 3.1.0.20160523-1225)
>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>> org.eclipse.jface.databinding 0.0.0
>>
>> RAP should have its version of org.eclipse.ui, and it should get that
>> version...
>>
>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>> dependency:
>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley.dsl 0.8.0.v20160509-1054)
>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>> org.eclipse.emf.parsley 0.0.0
>>
>> The Parsley DSL is not part of the targlet (it's only installed in the
>> IDE, but not in the targlet for the RAP version). I guess it finds it
>> in the Neon update site, but it's never referenced in the RAP subproject
>> targlet specification.
>>
>> The tycho build works for RAP: we use a TP using the
>> includeMode="slicer" which is a strict requirement for RAP (from what I
>> understand).
>>
>> Has anything changed in the Oomph targlet resolution so that a "slicer"
>> mode has to be made explicit?
>>
>> Thanks in advance
>> Lorenzo
>>
>


--
Prof. Lorenzo Bettini, Computer Science, DISIA, Univ. Firenze
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book


Re: problems when using Oomph with RAP [message #1735110 is a reply to message #1735105] Wed, 15 June 2016 15:12 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 31048
Registered: July 2009
Senior Member
Lorenzo,

Comments below.


On 15.06.2016 16:42, Lorenzo Bettini wrote:
> Hi Ed
>
> indeed by setting the targlet with includeAllRequirements to false, RAP
> features and bundles can be resolved without taking eclipse.ui bundles
> (and using the counterparts from RAP).
>
> The problem that still remains is that I reduced the targlet part for
> our source project (for RAP) to a single bundle,
> https://git.eclipse.org/r/#/c/75317/1/devtools/org.eclipse.emf.parsley.oomph/EMFParsley.setup,
> i.e.,
>
> org.eclipse.emf.parsley.rap.runtime which depends on
> org.eclipse.emf.parsley.runtime.common
And you have only this one targlet involved (not also the RCP one) and
it has only this one Parsely requirement?
>
> which in turn has no other dependencies on our projects, so I'd expect
> to have only two projects in the workspace.
>
> During targlet resolution, Oomph imports in the workspace also other
> Parsley projects, including the RCP ones and DSL projects... I really
> have no idea on why it does that...
I wonder if bundles reexporting packages and having package imports
might result in that bundle being used to resolve the package import?
>
> any clue of why I'm experiencing such a behavior?
No, it's hard to imagine how p2 would come up with such requirements if
they're not strictly needed. But I'm more familiar with how it resolves
bundle requirements not package requirements...

I'd need to set the problem in action, but it will be a while before I
can't look into that... I'm traveling for a while...
>
> thanks in advance
> Lorenzo
>
> On 15/06/2016 16:10, Ed Merks wrote:
>> Lorenzo,
>>
>> If at least one Targlet specifies includeAllRequirements as false, then
>> all requirements are essentially treated as optional so failure to
>> resolve something should just result in it being absent, not failing the
>> resolution overall.
>>
>>
>> On 15.06.2016 13:41, Lorenzo Bettini wrote:
>>> Hi
>>>
>>> in the Eclipse project EMF Parsley we've always been using Oomph with a
>>> setup,
>>> http://git.eclipse.org/c/emf-parsley/org.eclipse.emf-parsley.git/tree/devtools/org.eclipse.emf.parsley.oomph/EMFParsley.setup
>>>
>>> , with two subprojects: RCP for materializing a development workspace
>>> for the RCP version, and RAP for developing the RAP version.
>>>
>>> It has always worked. Now, when switching to Neon rimrel, the RCP works
>>> as before but the RAP version of the workspace always fails when
>>> resolving the targlet with problems of the shape
>>>
>>> ERROR: org.eclipse.equinox.p2.director code=0 Software being
>>> installed: artificial_root 1.0.0.v1465989132800
>>> ERROR: org.eclipse.equinox.p2.director code=0 Software being
>>> installed: workspace_requirements 1.0.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root
>>> 1.0.0.v1465989132800
>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>> org.eclipse.rap.examples.feature.feature.group 0.0.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley 0.8.0.v20160509-1054)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>> org.eclipse.jface.databinding 1.2.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley 0.8.0.v20160509-1054)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>> org.eclipse.ui 3.5.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley 1.0.0.v20160524-1223)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>> org.eclipse.jface.databinding 1.2.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley 1.0.0.v20160524-1223)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>> org.eclipse.ui 3.5.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley 1.0.0.v20160601-1323)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>> org.eclipse.jface.databinding 1.2.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley 1.0.0.v20160601-1323)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>> org.eclipse.ui 3.5.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
>>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley.dsl 0.8.0.v20160509-1054)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>> org.eclipse.emf.parsley 0.0.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
>>> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley.dsl 1.0.0.v20160524-1223)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>> org.eclipse.emf.parsley 0.0.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
>>> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley.dsl 1.0.0.v20160601-1323)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>> org.eclipse.emf.parsley 0.0.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>>> org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160524-1223
>>> (org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160524-1223)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>> org.eclipse.emf.parsley.dsl 0.0.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>>> org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160601-1323
>>> (org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160601-1323)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>> org.eclipse.emf.parsley.dsl 0.0.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Examples
>>> 3.1.0.20160422-0843 (org.eclipse.rap.examples.feature.feature.group
>>> 3.1.0.20160422-0843)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>> org.eclipse.rap.feature.feature.group [3.1.0,4.0.0)
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>> 3.1.0.20160511-1131 (org.eclipse.rap.feature.feature.group
>>> 3.1.0.20160511-1131)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui
>>> 0.0.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>> 3.1.0.20160523-1225 (org.eclipse.rap.feature.feature.group
>>> 3.1.0.20160523-1225)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>> org.eclipse.jface.databinding 0.0.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>> 3.1.0.20160527-1719 (org.eclipse.rap.feature.feature.group
>>> 3.1.0.20160527-1719)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui
>>> 0.0.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>>> workspace_requirements 1.0.0
>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>> org.eclipse.emf.parsley.dsl.ide 0.0.0
>>>
>>> I see many things that are strange to me:
>>>
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>> 3.1.0.20160511-1131 (org.eclipse.rap.feature.feature.group
>>> 3.1.0.20160511-1131)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui 0.0.0
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>> 3.1.0.20160523-1225 (org.eclipse.rap.feature.feature.group
>>> 3.1.0.20160523-1225)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>> org.eclipse.jface.databinding 0.0.0
>>>
>>> RAP should have its version of org.eclipse.ui, and it should get that
>>> version...
>>>
>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>> dependency:
>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
>>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley.dsl 0.8.0.v20160509-1054)
>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>> org.eclipse.emf.parsley 0.0.0
>>>
>>> The Parsley DSL is not part of the targlet (it's only installed in the
>>> IDE, but not in the targlet for the RAP version). I guess it finds it
>>> in the Neon update site, but it's never referenced in the RAP subproject
>>> targlet specification.
>>>
>>> The tycho build works for RAP: we use a TP using the
>>> includeMode="slicer" which is a strict requirement for RAP (from what I
>>> understand).
>>>
>>> Has anything changed in the Oomph targlet resolution so that a "slicer"
>>> mode has to be made explicit?
>>>
>>> Thanks in advance
>>> Lorenzo
>>>
>
Re: problems when using Oomph with RAP [message #1735118 is a reply to message #1735110] Wed, 15 June 2016 15:56 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1762
Registered: July 2009
Location: Firenze, Italy
Senior Member
Ed, my answers inline

On 15/06/2016 17:12, Ed Merks wrote:
> On 15.06.2016 16:42, Lorenzo Bettini wrote:
>> Hi Ed
>>
>> indeed by setting the targlet with includeAllRequirements to false, RAP
>> features and bundles can be resolved without taking eclipse.ui bundles
>> (and using the counterparts from RAP).
>>
>> The problem that still remains is that I reduced the targlet part for
>> our source project (for RAP) to a single bundle,
>> https://git.eclipse.org/r/#/c/75317/1/devtools/org.eclipse.emf.parsley.oomph/EMFParsley.setup,
>>
>> i.e.,
>>
>> org.eclipse.emf.parsley.rap.runtime which depends on
>> org.eclipse.emf.parsley.runtime.common
> And you have only this one targlet involved (not also the RCP one) and
> it has only this one Parsely requirement?

Yes. I mean, my only targlet is the RAP one; then there is the "Eclipse
Platform" targlet which is automatically used, but it only defines the
Neon update site and no explicit requirement.

>>
>> which in turn has no other dependencies on our projects, so I'd expect
>> to have only two projects in the workspace.
>>
>> During targlet resolution, Oomph imports in the workspace also other
>> Parsley projects, including the RCP ones and DSL projects... I really
>> have no idea on why it does that...
> I wonder if bundles reexporting packages and having package imports
> might result in that bundle being used to resolve the package import?

but package imports should promote the fact that then you need to
explicitly declare the bundles that provide such packages as
requirements, so there should be no automatic resolution strategies in
the presence of import packages, if that's what you meant...

in any case the runtime.common has no other deps on any Parsley packages

>>
>> any clue of why I'm experiencing such a behavior?
> No, it's hard to imagine how p2 would come up with such requirements if
> they're not strictly needed. But I'm more familiar with how it resolves
> bundle requirements not package requirements...
>
> I'd need to set the problem in action, but it will be a while before I
> can't look into that... I'm traveling for a while...

things are getting completely weird here: just for experiment, I also
removed the only Parsley requirement from the Targlet,
org.eclipse.emf.parsley.rap.runtime, and I left only
org.eclipse.rap.equinox.target.feature, just to try, so the targlet is
only an external binary dependency
org.eclipse.rap.equinox.target.feature ... and... targlet resolution
still imports in the workspace some parsley projects, including the RCP
ones and DSL projects, but no RAP projects (and this is the only thing
that makes sense since there's no mention now of our RAP projects in the
targlet). At this point I'm completely lost, and I really don't know
where it takes those projects from...

cheers
Lorenzo

>>
>> thanks in advance
>> Lorenzo
>>
>> On 15/06/2016 16:10, Ed Merks wrote:
>>> Lorenzo,
>>>
>>> If at least one Targlet specifies includeAllRequirements as false, then
>>> all requirements are essentially treated as optional so failure to
>>> resolve something should just result in it being absent, not failing the
>>> resolution overall.
>>>
>>>
>>> On 15.06.2016 13:41, Lorenzo Bettini wrote:
>>>> Hi
>>>>
>>>> in the Eclipse project EMF Parsley we've always been using Oomph with a
>>>> setup,
>>>> http://git.eclipse.org/c/emf-parsley/org.eclipse.emf-parsley.git/tree/devtools/org.eclipse.emf.parsley.oomph/EMFParsley.setup
>>>>
>>>>
>>>> , with two subprojects: RCP for materializing a development workspace
>>>> for the RCP version, and RAP for developing the RAP version.
>>>>
>>>> It has always worked. Now, when switching to Neon rimrel, the RCP
>>>> works
>>>> as before but the RAP version of the workspace always fails when
>>>> resolving the targlet with problems of the shape
>>>>
>>>> ERROR: org.eclipse.equinox.p2.director code=0 Software being
>>>> installed: artificial_root 1.0.0.v1465989132800
>>>> ERROR: org.eclipse.equinox.p2.director code=0 Software being
>>>> installed: workspace_requirements 1.0.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>>>> artificial_root
>>>> 1.0.0.v1465989132800
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>>> org.eclipse.rap.examples.feature.feature.group 0.0.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley 0.8.0.v20160509-1054)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>> org.eclipse.jface.databinding 1.2.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley 0.8.0.v20160509-1054)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>> org.eclipse.ui 3.5.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>>> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley 1.0.0.v20160524-1223)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>> org.eclipse.jface.databinding 1.2.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>>> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley 1.0.0.v20160524-1223)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>> org.eclipse.ui 3.5.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>>> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley 1.0.0.v20160601-1323)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>> org.eclipse.jface.databinding 1.2.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>>> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley 1.0.0.v20160601-1323)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>> org.eclipse.ui 3.5.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf
>>>> Parsley DSL
>>>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley.dsl 0.8.0.v20160509-1054)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>> org.eclipse.emf.parsley 0.0.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf
>>>> Parsley DSL
>>>> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley.dsl 1.0.0.v20160524-1223)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>> org.eclipse.emf.parsley 0.0.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf
>>>> Parsley DSL
>>>> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley.dsl 1.0.0.v20160601-1323)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>> org.eclipse.emf.parsley 0.0.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>>>> org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160524-1223
>>>> (org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160524-1223)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>> org.eclipse.emf.parsley.dsl 0.0.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>>>> org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160601-1323
>>>> (org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160601-1323)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>> org.eclipse.emf.parsley.dsl 0.0.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Examples
>>>> 3.1.0.20160422-0843 (org.eclipse.rap.examples.feature.feature.group
>>>> 3.1.0.20160422-0843)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>>> org.eclipse.rap.feature.feature.group [3.1.0,4.0.0)
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>>> 3.1.0.20160511-1131 (org.eclipse.rap.feature.feature.group
>>>> 3.1.0.20160511-1131)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui
>>>> 0.0.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>>> 3.1.0.20160523-1225 (org.eclipse.rap.feature.feature.group
>>>> 3.1.0.20160523-1225)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>>> org.eclipse.jface.databinding 0.0.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>>> 3.1.0.20160527-1719 (org.eclipse.rap.feature.feature.group
>>>> 3.1.0.20160527-1719)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui
>>>> 0.0.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>>>> workspace_requirements 1.0.0
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>>> org.eclipse.emf.parsley.dsl.ide 0.0.0
>>>>
>>>> I see many things that are strange to me:
>>>>
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>>> 3.1.0.20160511-1131 (org.eclipse.rap.feature.feature.group
>>>> 3.1.0.20160511-1131)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui 0.0.0
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>>> 3.1.0.20160523-1225 (org.eclipse.rap.feature.feature.group
>>>> 3.1.0.20160523-1225)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>>> org.eclipse.jface.databinding 0.0.0
>>>>
>>>> RAP should have its version of org.eclipse.ui, and it should get that
>>>> version...
>>>>
>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>> dependency:
>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
>>>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley.dsl 0.8.0.v20160509-1054)
>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>> org.eclipse.emf.parsley 0.0.0
>>>>
>>>> The Parsley DSL is not part of the targlet (it's only installed in the
>>>> IDE, but not in the targlet for the RAP version). I guess it finds it
>>>> in the Neon update site, but it's never referenced in the RAP
>>>> subproject
>>>> targlet specification.
>>>>
>>>> The tycho build works for RAP: we use a TP using the
>>>> includeMode="slicer" which is a strict requirement for RAP (from what I
>>>> understand).
>>>>
>>>> Has anything changed in the Oomph targlet resolution so that a "slicer"
>>>> mode has to be made explicit?
>>>>
>>>> Thanks in advance
>>>> Lorenzo
>>>>
>>
>


--
Prof. Lorenzo Bettini, Computer Science, DISIA, Univ. Firenze
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book


Re: problems when using Oomph with RAP [message #1735139 is a reply to message #1735118] Wed, 15 June 2016 18:18 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 31048
Registered: July 2009
Senior Member
Lorenzo,

I think the problem (quickly debugging) is that your binary repos
contain binary versions of the Parsley things (0.8.0 versions), and the
git repo contains 1.0.0 versions, and requirements that are in the git
repo that aren't also in the binary repo are added as
workspace_requirements, which results in the extra things being pulled
into the workspace. Please open a Bugzilla. I have no idea yet how to
fix this nor when I'll have time...


On 15.06.2016 17:56, Lorenzo Bettini wrote:
> Ed, my answers inline
>
> On 15/06/2016 17:12, Ed Merks wrote:
>> On 15.06.2016 16:42, Lorenzo Bettini wrote:
>>> Hi Ed
>>>
>>> indeed by setting the targlet with includeAllRequirements to false, RAP
>>> features and bundles can be resolved without taking eclipse.ui bundles
>>> (and using the counterparts from RAP).
>>>
>>> The problem that still remains is that I reduced the targlet part for
>>> our source project (for RAP) to a single bundle,
>>> https://git.eclipse.org/r/#/c/75317/1/devtools/org.eclipse.emf.parsley.oomph/EMFParsley.setup,
>>>
>>> i.e.,
>>>
>>> org.eclipse.emf.parsley.rap.runtime which depends on
>>> org.eclipse.emf.parsley.runtime.common
>> And you have only this one targlet involved (not also the RCP one) and
>> it has only this one Parsely requirement?
> Yes. I mean, my only targlet is the RAP one; then there is the "Eclipse
> Platform" targlet which is automatically used, but it only defines the
> Neon update site and no explicit requirement.
>
>>> which in turn has no other dependencies on our projects, so I'd expect
>>> to have only two projects in the workspace.
>>>
>>> During targlet resolution, Oomph imports in the workspace also other
>>> Parsley projects, including the RCP ones and DSL projects... I really
>>> have no idea on why it does that...
>> I wonder if bundles reexporting packages and having package imports
>> might result in that bundle being used to resolve the package import?
> but package imports should promote the fact that then you need to
> explicitly declare the bundles that provide such packages as
> requirements, so there should be no automatic resolution strategies in
> the presence of import packages, if that's what you meant...
>
> in any case the runtime.common has no other deps on any Parsley packages
>
>>> any clue of why I'm experiencing such a behavior?
>> No, it's hard to imagine how p2 would come up with such requirements if
>> they're not strictly needed. But I'm more familiar with how it resolves
>> bundle requirements not package requirements...
>>
>> I'd need to set the problem in action, but it will be a while before I
>> can't look into that... I'm traveling for a while...
> things are getting completely weird here: just for experiment, I also
> removed the only Parsley requirement from the Targlet,
> org.eclipse.emf.parsley.rap.runtime, and I left only
> org.eclipse.rap.equinox.target.feature, just to try, so the targlet is
> only an external binary dependency
> org.eclipse.rap.equinox.target.feature ... and... targlet resolution
> still imports in the workspace some parsley projects, including the RCP
> ones and DSL projects, but no RAP projects (and this is the only thing
> that makes sense since there's no mention now of our RAP projects in the
> targlet). At this point I'm completely lost, and I really don't know
> where it takes those projects from...
>
> cheers
> Lorenzo
>
>>> thanks in advance
>>> Lorenzo
>>>
>>> On 15/06/2016 16:10, Ed Merks wrote:
>>>> Lorenzo,
>>>>
>>>> If at least one Targlet specifies includeAllRequirements as false, then
>>>> all requirements are essentially treated as optional so failure to
>>>> resolve something should just result in it being absent, not failing the
>>>> resolution overall.
>>>>
>>>>
>>>> On 15.06.2016 13:41, Lorenzo Bettini wrote:
>>>>> Hi
>>>>>
>>>>> in the Eclipse project EMF Parsley we've always been using Oomph with a
>>>>> setup,
>>>>> http://git.eclipse.org/c/emf-parsley/org.eclipse.emf-parsley.git/tree/devtools/org.eclipse.emf.parsley.oomph/EMFParsley.setup
>>>>>
>>>>>
>>>>> , with two subprojects: RCP for materializing a development workspace
>>>>> for the RCP version, and RAP for developing the RAP version.
>>>>>
>>>>> It has always worked. Now, when switching to Neon rimrel, the RCP
>>>>> works
>>>>> as before but the RAP version of the workspace always fails when
>>>>> resolving the targlet with problems of the shape
>>>>>
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 Software being
>>>>> installed: artificial_root 1.0.0.v1465989132800
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 Software being
>>>>> installed: workspace_requirements 1.0.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>>>>> artificial_root
>>>>> 1.0.0.v1465989132800
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>>>> org.eclipse.rap.examples.feature.feature.group 0.0.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>>>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley 0.8.0.v20160509-1054)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>>> org.eclipse.jface.databinding 1.2.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>>>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley 0.8.0.v20160509-1054)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>>> org.eclipse.ui 3.5.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>>>> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley 1.0.0.v20160524-1223)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>>> org.eclipse.jface.databinding 1.2.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>>>> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley 1.0.0.v20160524-1223)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>>> org.eclipse.ui 3.5.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>>>> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley 1.0.0.v20160601-1323)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>>> org.eclipse.jface.databinding 1.2.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley
>>>>> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley 1.0.0.v20160601-1323)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>>> org.eclipse.ui 3.5.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf
>>>>> Parsley DSL
>>>>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley.dsl 0.8.0.v20160509-1054)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>>> org.eclipse.emf.parsley 0.0.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf
>>>>> Parsley DSL
>>>>> 1.0.0.v20160524-1223 (org.eclipse.emf.parsley.dsl 1.0.0.v20160524-1223)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>>> org.eclipse.emf.parsley 0.0.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf
>>>>> Parsley DSL
>>>>> 1.0.0.v20160601-1323 (org.eclipse.emf.parsley.dsl 1.0.0.v20160601-1323)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>>> org.eclipse.emf.parsley 0.0.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>>>>> org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160524-1223
>>>>> (org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160524-1223)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>>> org.eclipse.emf.parsley.dsl 0.0.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>>>>> org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160601-1323
>>>>> (org.eclipse.emf.parsley.dsl.ide 1.0.0.v20160601-1323)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>>> org.eclipse.emf.parsley.dsl 0.0.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Examples
>>>>> 3.1.0.20160422-0843 (org.eclipse.rap.examples.feature.feature.group
>>>>> 3.1.0.20160422-0843)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>>>> org.eclipse.rap.feature.feature.group [3.1.0,4.0.0)
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>>>> 3.1.0.20160511-1131 (org.eclipse.rap.feature.feature.group
>>>>> 3.1.0.20160511-1131)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui
>>>>> 0.0.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>>>> 3.1.0.20160523-1225 (org.eclipse.rap.feature.feature.group
>>>>> 3.1.0.20160523-1225)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>>>> org.eclipse.jface.databinding 0.0.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>>>> 3.1.0.20160527-1719 (org.eclipse.rap.feature.feature.group
>>>>> 3.1.0.20160527-1719)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui
>>>>> 0.0.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From:
>>>>> workspace_requirements 1.0.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>>>> org.eclipse.emf.parsley.dsl.ide 0.0.0
>>>>>
>>>>> I see many things that are strange to me:
>>>>>
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>>>> 3.1.0.20160511-1131 (org.eclipse.rap.feature.feature.group
>>>>> 3.1.0.20160511-1131)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.ui 0.0.0
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP Runtime
>>>>> 3.1.0.20160523-1225 (org.eclipse.rap.feature.feature.group
>>>>> 3.1.0.20160523-1225)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To:
>>>>> org.eclipse.jface.databinding 0.0.0
>>>>>
>>>>> RAP should have its version of org.eclipse.ui, and it should get that
>>>>> version...
>>>>>
>>>>> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy
>>>>> dependency:
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 From: Emf Parsley DSL
>>>>> 0.8.0.v20160509-1054 (org.eclipse.emf.parsley.dsl 0.8.0.v20160509-1054)
>>>>> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
>>>>> org.eclipse.emf.parsley 0.0.0
>>>>>
>>>>> The Parsley DSL is not part of the targlet (it's only installed in the
>>>>> IDE, but not in the targlet for the RAP version). I guess it finds it
>>>>> in the Neon update site, but it's never referenced in the RAP
>>>>> subproject
>>>>> targlet specification.
>>>>>
>>>>> The tycho build works for RAP: we use a TP using the
>>>>> includeMode="slicer" which is a strict requirement for RAP (from what I
>>>>> understand).
>>>>>
>>>>> Has anything changed in the Oomph targlet resolution so that a "slicer"
>>>>> mode has to be made explicit?
>>>>>
>>>>> Thanks in advance
>>>>> Lorenzo
>>>>>
>
Re: problems when using Oomph with RAP [message #1735227 is a reply to message #1735139] Thu, 16 June 2016 13:11 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1762
Registered: July 2009
Location: Firenze, Italy
Senior Member
On 15/06/2016 20:18, Ed Merks wrote:
> Lorenzo,
>
> I think the problem (quickly debugging) is that your binary repos
> contain binary versions of the Parsley things (0.8.0 versions), and the
> git repo contains 1.0.0 versions, and requirements that are in the git
> repo that aren't also in the binary repo are added as
> workspace_requirements, which results in the extra things being pulled
> into the workspace. Please open a Bugzilla. I have no idea yet how to
> fix this nor when I'll have time...

Hi Ed

I think that's exactly the cause of the problem:

org.eclipse.emf.parsley.dsl.ide is a new bundle in version 1.0.0 which
was not there in version 0.8.0 and that's the one that causes some
additional projects (besides itself) to be imported in the workspace!
In fact, using the Neon staging repository, which only contains the last
version, i.e., 1.0.0, (temporarily) fixes this problem.

I'll file a new bug as soon as Bugzilla works again.

thanks
Lorenzo


--
Prof. Lorenzo Bettini, Computer Science, DISIA, Univ. Firenze
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book


Re: problems when using Oomph with RAP [message #1735230 is a reply to message #1735139] Thu, 16 June 2016 13:11 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1762
Registered: July 2009
Location: Firenze, Italy
Senior Member
On 15/06/2016 20:18, Ed Merks wrote:
> Lorenzo,
>
> I think the problem (quickly debugging) is that your binary repos
> contain binary versions of the Parsley things (0.8.0 versions), and the
> git repo contains 1.0.0 versions, and requirements that are in the git
> repo that aren't also in the binary repo are added as
> workspace_requirements, which results in the extra things being pulled
> into the workspace. Please open a Bugzilla. I have no idea yet how to
> fix this nor when I'll have time...

Hi Ed

I think that's exactly the cause of the problem:

org.eclipse.emf.parsley.dsl.ide is a new bundle in version 1.0.0 which
was not there in version 0.8.0 and that's the one that causes some
additional projects (besides itself) to be imported in the workspace!
In fact, using the Neon staging repository, which only contains the last
version, i.e., 1.0.0, (temporarily) fixes this problem.

I'll file a new bug as soon as Bugzilla works again.

thanks
Lorenzo


--
Prof. Lorenzo Bettini, Computer Science, DISIA, Univ. Firenze
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book


Re: problems when using Oomph with RAP [message #1736331 is a reply to message #1735227] Tue, 28 June 2016 12:58 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 31048
Registered: July 2009
Senior Member
Lorenzo,

I worked on a fix for the problem. Instead of these artificial direct
workspace (and license) requirements, I instead modify the binary IUs
requirements to include any additional requirements of the corresponding
workspace IU that's not already present in the binary IU. This way such
additional requirement's IU is resolved into the TP (or workspace), only
if the binary IU itself is required. That should produce the desired
results, i.e., for this scenario, only the rap.runtime and
runtime.common bundles end up in the workspace, not the ide bundle
(which can't be fully resolved for the RAP scenario).

I'll commit the fix against the Bugzilla, once you open it.


On 16.06.2016 09:11, Lorenzo Bettini wrote:
> On 15/06/2016 20:18, Ed Merks wrote:
>> Lorenzo,
>>
>> I think the problem (quickly debugging) is that your binary repos
>> contain binary versions of the Parsley things (0.8.0 versions), and the
>> git repo contains 1.0.0 versions, and requirements that are in the git
>> repo that aren't also in the binary repo are added as
>> workspace_requirements, which results in the extra things being pulled
>> into the workspace. Please open a Bugzilla. I have no idea yet how to
>> fix this nor when I'll have time...
> Hi Ed
>
> I think that's exactly the cause of the problem:
>
> org.eclipse.emf.parsley.dsl.ide is a new bundle in version 1.0.0 which
> was not there in version 0.8.0 and that's the one that causes some
> additional projects (besides itself) to be imported in the workspace!
> In fact, using the Neon staging repository, which only contains the last
> version, i.e., 1.0.0, (temporarily) fixes this problem.
>
> I'll file a new bug as soon as Bugzilla works again.
>
> thanks
> Lorenzo
>
>
Re: problems when using Oomph with RAP [message #1736391 is a reply to message #1736331] Wed, 29 June 2016 06:54 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1762
Registered: July 2009
Location: Firenze, Italy
Senior Member
On 28/06/2016 14:58, Ed Merks wrote:
> Lorenzo,
>
> I worked on a fix for the problem. Instead of these artificial direct
> workspace (and license) requirements, I instead modify the binary IUs
> requirements to include any additional requirements of the corresponding
> workspace IU that's not already present in the binary IU. This way such
> additional requirement's IU is resolved into the TP (or workspace), only
> if the binary IU itself is required. That should produce the desired
> results, i.e., for this scenario, only the rap.runtime and
> runtime.common bundles end up in the workspace, not the ide bundle
> (which can't be fully resolved for the RAP scenario).
>
> I'll commit the fix against the Bugzilla, once you open it.

Hi Ed

I forgot to post that I had already opened a bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=496350

at the moment I couldn't test the fix because since Neon has been
released now there's only one version of Parsley.

thanks
Lorenzo

>
>
> On 16.06.2016 09:11, Lorenzo Bettini wrote:
>> On 15/06/2016 20:18, Ed Merks wrote:
>>> Lorenzo,
>>>
>>> I think the problem (quickly debugging) is that your binary repos
>>> contain binary versions of the Parsley things (0.8.0 versions), and the
>>> git repo contains 1.0.0 versions, and requirements that are in the git
>>> repo that aren't also in the binary repo are added as
>>> workspace_requirements, which results in the extra things being pulled
>>> into the workspace. Please open a Bugzilla. I have no idea yet how to
>>> fix this nor when I'll have time...
>> Hi Ed
>>
>> I think that's exactly the cause of the problem:
>>
>> org.eclipse.emf.parsley.dsl.ide is a new bundle in version 1.0.0 which
>> was not there in version 0.8.0 and that's the one that causes some
>> additional projects (besides itself) to be imported in the workspace!
>> In fact, using the Neon staging repository, which only contains the last
>> version, i.e., 1.0.0, (temporarily) fixes this problem.
>>
>> I'll file a new bug as soon as Bugzilla works again.
>>
>> thanks
>> Lorenzo
>>
>>
>


--
Prof. Lorenzo Bettini, Computer Science, DISIA, Univ. Firenze
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book


Re: problems when using Oomph with RAP [message #1736428 is a reply to message #1736391] Wed, 29 June 2016 11:41 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 31048
Registered: July 2009
Senior Member
Lorenzo,

Thanks. To reproduce the problem, I pointed the setup at an older
update site containing 0.8, so I could definitely reproduce the problem,
the fix definitely fixes it, and it seems unlikely to break anything
else because the design is consistent with the purpose, i.e., to augment
the binary IU requirements with additional newly-introduced workspace IU
requirements which of course should only be required if binary IU (which
replaces the workspace IU in the IU metadata) itself is required...


On 29.06.2016 02:54, Lorenzo Bettini wrote:
> On 28/06/2016 14:58, Ed Merks wrote:
>> Lorenzo,
>>
>> I worked on a fix for the problem. Instead of these artificial direct
>> workspace (and license) requirements, I instead modify the binary IUs
>> requirements to include any additional requirements of the corresponding
>> workspace IU that's not already present in the binary IU. This way such
>> additional requirement's IU is resolved into the TP (or workspace), only
>> if the binary IU itself is required. That should produce the desired
>> results, i.e., for this scenario, only the rap.runtime and
>> runtime.common bundles end up in the workspace, not the ide bundle
>> (which can't be fully resolved for the RAP scenario).
>>
>> I'll commit the fix against the Bugzilla, once you open it.
> Hi Ed
>
> I forgot to post that I had already opened a bug
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=496350
>
> at the moment I couldn't test the fix because since Neon has been
> released now there's only one version of Parsley.
>
> thanks
> Lorenzo
>
>>
>> On 16.06.2016 09:11, Lorenzo Bettini wrote:
>>> On 15/06/2016 20:18, Ed Merks wrote:
>>>> Lorenzo,
>>>>
>>>> I think the problem (quickly debugging) is that your binary repos
>>>> contain binary versions of the Parsley things (0.8.0 versions), and the
>>>> git repo contains 1.0.0 versions, and requirements that are in the git
>>>> repo that aren't also in the binary repo are added as
>>>> workspace_requirements, which results in the extra things being pulled
>>>> into the workspace. Please open a Bugzilla. I have no idea yet how to
>>>> fix this nor when I'll have time...
>>> Hi Ed
>>>
>>> I think that's exactly the cause of the problem:
>>>
>>> org.eclipse.emf.parsley.dsl.ide is a new bundle in version 1.0.0 which
>>> was not there in version 0.8.0 and that's the one that causes some
>>> additional projects (besides itself) to be imported in the workspace!
>>> In fact, using the Neon staging repository, which only contains the last
>>> version, i.e., 1.0.0, (temporarily) fixes this problem.
>>>
>>> I'll file a new bug as soon as Bugzilla works again.
>>>
>>> thanks
>>> Lorenzo
>>>
>>>
>
Previous Topic:What could cause additional repository & requirement to be ignored in an existing working model?
Next Topic:[Solved] Deactivate 'Launch automatically' automatically
Goto Forum:
  


Current Time: Thu Apr 09 21:36:10 GMT 2020

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

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

Back to the top