|
| Re: xtext P2 referencing specific version with P2 reader. [message #1015061 is a reply to message #1015057] |
Wed, 27 February 2013 10:38   |
|
Although I've never done that myself, I think you should specify a
version range in the cquery...
On 02/27/2013 11:16 AM, Christophe Bouhier wrote:
> Hello,
>
> I am trying to import a specific version from the Xtext update site with
> this .rmap entry:
>
>
> <rm:searchPath name="org.eclipse.xtext">
> <rm:provider
> componentTypes="buckminster,osgi.bundle,eclipse.feature"
> readerType="p2" source="false" mutable="false">
> <rm:property key="buckminster.source" value="false" />
> <rm:property key="buckminster.mutable" value="false" />
> <rm:uri
>
> format="http://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases/{0}">
>
> <bc:propertyRef key="xtext.version" />
> </rm:uri>
> </rm:provider>
> </rm:searchPath>
>
>
> Unfortunnately this doesn't work, as I can't simply concat the version
> behind the uri fragment /releases/. How do I reference a specific
> category in the p2 update site? I have tried with setting the
> xtext.version to "TMF 20Xtext-2.0.1" with no success. (I can see this
> category exists when trying the update site in the Eclipse IDE).
>
>
> This is bucky's error:
>
> ERROR [0019] : No suitable provider for component
> org.eclipse.xtext:osgi.bundle was found in searchPath org.eclipse.xtext
> ERROR [0019] : Rejecting provider
> p2(http://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases/{0}[http://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases/TMF
> Xtext-2.0.1]): No component match was found
> ERROR No repository found at
> http://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases/TMF%20Xtext-2.0.1/.
>
>
>
> Thank You ! Christophe
>
>
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
|
|
|
|
|
| Re: xtext P2 referencing specific version with P2 reader. [message #1015096 is a reply to message #1015071] |
Wed, 27 February 2013 12:57 |
 Christophe Bouhier
Messages: 937
Registered: July 2009 |
Senior Member |
|
|
Hi,
I have been looking how, I can add a version constraint in a cquery, but
I don't see where and how this is done. Can someone please explain?
If it's done through an advisor node, which section should I use?
Is it the filter in the General section? If it's override, it seems this
is really to change the version in the materialized component right?
thank you, Christophe
On 27-02-13 12:06, Christophe Bouhier wrote:
> On 27-02-13 11:58, Dennis Huebner wrote:
>> ERROR No repository found at
>> http://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases/TMF%20Xtext-2.0.1/
>>
>>
>>
>> You can't navigate through the composite repository by using an update
>> site category label "TMF Xtext-2.0.1".
>>
>> Xtext 2.0.1 repository is located here:
>> http://download.eclipse.org/modeling/tmf/xtext/updates/releases/head/R201108020636/
>>
>>
> Thanks! I just wonder where this URL is published on the web. I can't
> find it in the Xtext download section here:
>
> http://www.eclipse.org/modeling/tmf/downloads/?project=xtext
>
>>
>> If you would like to use the composite one, you have to use a version
>> constraint in your cquery, like Lorenzo has suggested. Or put a version
>> constraint in your feature. Buckminster will grab the right one.
> OK, will try this!
>
>
|
|
|
| Re: xtext P2 referencing specific version with P2 reader. [message #1015097 is a reply to message #1015096] |
Wed, 27 February 2013 13:07 |
|
Normally I use the constraints in my buckminster CSPEC
<cs:cspec xmlns:cs="http://www.eclipse.org/buckminster/CSpec-1.0" name="org.eclipse.xtext.releng" componentType="buckminster" version="1.0.0.qualifier">
<cs:dependencies>
<cs:dependency name="com.google.guava" componentType="osgi.bundle" versionDesignator="[10.0.0,12.0.0)"/>
Sometimes it's necessary to override version cotraint in the cquery:
<cq:advisorNode namePattern="org.eclipse.emf.ecore.editor" componentType="osgi.bundle" useTargetPlatform="false" versionOverride="[2.5.0,2.6.0)"/>
+Dennis Huebner
Get professional support from the Xtext committers at www.typefox.io
|
|
|
|
| Re: xtext P2 referencing specific version with P2 reader. [message #1015104 is a reply to message #1015101] |
Wed, 27 February 2013 13:26 |
|
Yes, I have an own CSPEC for my releng project in order to set up the target platform first.
However, you can also use your "main/build" feature to define constraints e.g
<requires>
<import feature="org.eclipse.xtend.sdk" version="2.4.0" match="equivalent"/>
<import plugin="org.eclipse.emf.ecore" version="2.5.0" match="greaterOrEqual"/>
<import plugin="org.eclipse.emf.common" version="2.5.0" match="greaterOrEqual"/>
<import plugin="org.eclipse.emf.ecore.source" version="2.5.0" match="greaterOrEqual"/>
<import plugin="org.eclipse.emf.common.source" version="2.5.0" match="greaterOrEqual"/>
</requires>
Buckminster will take care that this contraints are fulfilled.
+Dennis Huebner
Get professional support from the Xtext committers at www.typefox.io
|
|
|
|
|
|
|
| Re: xtext P2 referencing specific version with P2 reader. [message #1022340 is a reply to message #1015104] |
Thu, 21 March 2013 17:46 |
|
Hi
I'm resuming this thread for a similar question:
On 02/27/2013 02:26 PM, Dennis Huebner wrote:
> Yes, I have an own CSPEC for my releng project in order to set up the
> target platform first.
> However, you can also use your "main/build" feature to define
> constraints e.g
>
I tried to put in my main feature this
<requires>
<import feature="org.eclipse.xtext.sdk" version="2.3.1" match="equivalent"/>
</requires>
which should be equivalent to [2.3.1,2.4.0)
however, the materialization still drags in Xtext 2.4.0...
can it be because I also have a dependency on org.eclipse.xtext.sdk in
my main cspec (without any version designator)?
thanks in advance
Lorenzo
>
> <requires>
> <import feature="org.eclipse.xtend.sdk" version="2.4.0"
> match="equivalent"/>
> <import plugin="org.eclipse.emf.ecore" version="2.5.0"
> match="greaterOrEqual"/>
> <import plugin="org.eclipse.emf.common" version="2.5.0"
> match="greaterOrEqual"/>
> <import plugin="org.eclipse.emf.ecore.source" version="2.5.0"
> match="greaterOrEqual"/>
> <import plugin="org.eclipse.emf.common.source" version="2.5.0"
> match="greaterOrEqual"/>
> </requires>
>
>
> Buckminster will take care that this contraints are fulfilled.
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
|
|
|
Powered by
FUDForum. Page generated in 0.04522 seconds
] 
Search
Help
Register
Login
Home
