Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » strange problem with Buckminster Wizard for existing Xtext language projects
strange problem with Buckminster Wizard for existing Xtext language projects [message #892217] Wed, 27 June 2012 12:30 Go to next message
Lorenzo Bettini is currently offline Lorenzo Bettini
Messages: 1368
Registered: July 2009
Senior Member
Hi

I started using this wonderful wizard which comes with Xtext 2.3.0 for
building my Xtext language with Buckminster and Jenkins

now I have a strange problem:

The jenkins commands (based on the commands.txt generated by the wizard) are

resolve releng/it.xsemantics.buckminster/projects-platform.cquery
resolve releng/it.xsemantics.buckminster/project.cquery
clean
build
perform -D target.os=* -D target.ws=* -D target.arch=*
it.xsemantics.site#buckminster.clean
perform -D target.os=* -D target.ws=* -D target.arch=*
it.xsemantics.site#site.p2.zip

and some junit tests

when I run the Jenkins job in a clean workspace (e.g., the first time I
run the job or after a wipe out of the workspace), the target platform
is resolved, but then project.cquery resolve fails with some errors due
to source bundles which are not found, e.g., (only some of the errors
are shown):

ERROR [0019] : No suitable provider for component
org.eclipse.xtext.junit4.source:osgi.bundle/[2.3.0.v201206120633,2.3.0.v201206120633]
was found in resourceMap
file:/usr/share/tomcat6/.jenkins/workspace/xsemantics-buckminster-gerrit/releng/it.xsemantics.buckminster/project.rmap
ERROR [0019] : Unable to find a searchPath for
org.eclipse.xtext.junit4.source:osgi.bundle/[2.3.0.v201206120633,2.3.0.v201206120633]
ERROR [0019] : No suitable provider for component
org.eclipse.xtext.junit.source:osgi.bundle/[2.3.0.v201206120633,2.3.0.v201206120633]
was found in resourceMap
file:/usr/share/tomcat6/.jenkins/workspace/xsemantics-buckminster-gerrit/releng/it.xsemantics.buckminster/project.rmap
ERROR [0019] : Unable to find a searchPath for
org.eclipse.xtext.junit.source:osgi.bundle/[2.3.0.v201206120633,2.3.0.v201206120633]

....

ERROR [0044] : No suitable provider for component
org.hamcrest.integration.source:osgi.bundle/[1.1.0.v20090501071000,1.1.0.v20090501071000]
was found in resourceMap
file:/usr/share/tomcat6/.jenkins/workspace/xsemantics-buckminster-gerrit/releng/it.xsemantics.buckminster/project.rmap
ERROR [0044] : Unable to find a searchPath for
org.hamcrest.integration.source:osgi.bundle/[1.1.0.v20090501071000,1.1.0.v20090501071000]

If I then run the job again (without wiping the workspace) then
everything goes fine...

the project-platform.cquery (generated by the wizard) has an advisor
node to skip sources

<cq:advisorNode namePattern="^.*\.source$" skipComponent="true"/>

so why should it want to resolve source bundles?

can it be due to the fact that in my repository I also insert the source
feature (but only of my own plugins)?

I would also like to track down the issue... but I don't know how to
interpret INFO such as

ERROR [0044] : No suitable provider for component
org.hamcrest.library.source:osgi.bundle/[1.1.0.v20090501071000,1.1.0.v20090501071000]
was found in resourceMap
file:/usr/share/tomcat6/.jenkins/workspace/xsemantics-buckminster-gerrit/releng/it.xsemantics.buckminster/project.rmap
ERROR [0044] : Unable to find a searchPath for
org.hamcrest.library.source:osgi.bundle/[1.1.0.v20090501071000,1.1.0.v20090501071000]
INFO: TAG-ID 0019 = Query for it.xsemantics.site:eclipse.feature, path:
it.xsemantics.site:eclipse.feature$1.0.0.qualifier ->
it.xsemantics.tests.feature:eclipse.feature$1.0.100.qualifier ->
org.eclipse.xtext.sdk:eclipse.feature$2.3.0.v201206120633
TAG-ID 0022 = Query for it.xsemantics.site:eclipse.feature, path:
it.xsemantics.site:eclipse.feature$1.0.0.qualifier ->
it.xsemantics.example.expressions.tests:osgi.bundle$1.0.100.qualifier ->
it.xsemantics.example.expressions:osgi.bundle$1.0.100.qualifier
TAG-ID 0044 = Query for it.xsemantics.site:eclipse.feature, path:
it.xsemantics.site:eclipse.feature$1.0.0.qualifier ->
it.xsemantics.tests.feature:eclipse.feature$1.0.100.qualifier ->
org.eclipse.swtbot:eclipse.feature$2.0.5.20111003_1754-3676ac8-dev-e36

can I understand from this who's trying to import source bundles?

thanks in advance
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net
Re: strange problem with Buckminster Wizard for existing Xtext language projects [message #892229 is a reply to message #892217] Wed, 27 June 2012 12:58 Go to previous messageGo to next message
Dennis Huebner is currently offline Dennis Huebner
Messages: 213
Registered: July 2009
Senior Member

Hi Lorenzo!
Missing Xtext sources come it.xsemantics.tests.feature:eclipse.feature (you should not include Xtext SDK in your feature).
And hamcrest stuff comes definitely from the swtbot feature: http://git.eclipse.org/c/swtbot/org.eclipse.swtbot.git/tree/org.eclipse.swtbot/feature.xml

To track an error, you should look at the error id e.g. in hamcrest case its 0044:
ERROR [0044] : No suitable provider for component 
org.hamcrest.integration.source:osgi.bundle/[1.1.0.v20090501071000,1.1.0.v20090501071000] 
was found in resourceMap 


So if you check the trace below you can see that org.eclipse.swtbot requested it
TAG-ID 0044 = Query for it.xsemantics.site:eclipse.feature, path: 
it.xsemantics.site:eclipse.feature$1.0.0.qualifier -> 
it.xsemantics.tests.feature:eclipse.feature$1.0.100.qualifier -> 
org.eclipse.swtbot:eclipse.feature$2.0.5.20111003_1754-3676ac8-dev-e36


Re: strange problem with Buckminster Wizard for existing Xtext language projects [message #892252 is a reply to message #892217] Wed, 27 June 2012 13:50 Go to previous messageGo to next message
Dennis Huebner is currently offline Dennis Huebner
Messages: 213
Registered: July 2009
Senior Member

Quote:

<cq:advisorNode namePattern="^.*\.source$" skipComponent="true"/>

so why should it want to resolve source bundles?

The advisor node is in the target platform cquery. But your source dependencies comes from the project cquery so the node is not active.
Quote:

can it be due to the fact that in my repository I also insert the source
feature (but only of my own plugins)?

Your project dependencies require this sources. So it's better to add them to your target platform.

I've added the "skip sources" advisor node to minimize the TP download size, so you can just remove or edit it.
If you would like to include the swtbot sources in your project's repository, add following line to your buckminster.scpec (and edit or remove the advisor node above, of cause) :
 <cs:dependency name="org.eclipse.swtbot" componentType="eclipse.feature"/>



Re: strange problem with Buckminster Wizard for existing Xtext language projects [message #892260 is a reply to message #892229] Wed, 27 June 2012 14:11 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo Bettini
Messages: 1368
Registered: July 2009
Senior Member
On 06/27/2012 02:58 PM, Dennis Huebner wrote:
> Hi Lorenzo!

Hi Dennis! Thanks for the quick reply!

> Missing Xtext sources come it.xsemantics.tests.feature:eclipse.feature
> (you should not include Xtext SDK in your feature).

I added xtext sdk to the tests feature because I run swtbot tests that
test that I can create a project with the wizard for some DSL examples,
and also that I can create in the workspace some examples projects
(similar to the examples projects of Xtext itself)... so I thought I'd
need xtext sdk in the test feature to perform swtbot tests, am I right?

> And hamcrest stuff comes definitely from the swtbot feature:
> http://git.eclipse.org/c/swtbot/org.eclipse.swtbot.git/tree/org.eclipse.swtbot/feature.xml
>
>
> To track an error, you should look at the error id e.g. in hamcrest
> case its 0044:
> ERROR [0044] : No suitable provider for component
> org.hamcrest.integration.source:osgi.bundle/[1.1.0.v20090501071000,1.1.0.v20090501071000]
> was found in resourceMap
> So if you check the trace below you can see that org.eclipse.swtbot
> requested it
> TAG-ID 0044 = Query for it.xsemantics.site:eclipse.feature, path:
> it.xsemantics.site:eclipse.feature$1.0.0.qualifier ->
> it.xsemantics.tests.feature:eclipse.feature$1.0.100.qualifier ->
> org.eclipse.swtbot:eclipse.feature$2.0.5.20111003_1754-3676ac8-dev-e36

OK, thanks for the clarification :)

please see also my other answer

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net
Re: strange problem with Buckminster Wizard for existing Xtext language projects [message #892261 is a reply to message #892252] Wed, 27 June 2012 14:11 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo Bettini
Messages: 1368
Registered: July 2009
Senior Member
Hi again :)

On 06/27/2012 03:50 PM, Dennis Huebner wrote:
> Quote:
>> <cq:advisorNode namePattern="^.*\.source$" skipComponent="true"/>
>>
>> so why should it want to resolve source bundles?
>
> The advisor node is in the target platform cquery. But your source
> dependencies comes from the project cquery so the node is not active.
> Quote:
>> can it be due to the fact that in my repository I also insert the
>> source feature (but only of my own plugins)?
>
> Your project dependencies require this sources. So it's better to add
> them to your target platform.
>

so I did some experiments before you wrote this other message, and I
modified projects-platform.cquery as follows:

<?xml version="1.0" encoding="UTF-8"?>
<cq:componentQuery
xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
resourceMap="projects-platform.rmap">
<cq:rootRequest name="it.xsemantics.buckminster"
componentType="buckminster"/>
<cq:property key="buckminster.download.source" value="true"/>
<cq:property key="target.arch" value="*"/>
<cq:property key="target.os" value="*"/>
<cq:property key="target.ws" value="*"/>
</cq:componentQuery>

thus, I removed the advisor node, and request explicit download of
sources...

things get better now: if I wipe the workspace before the build the
sources are downloaded... but one problem remains: I get errors only for
this source bundle

INFO: resolve 'releng/it.xsemantics.buckminster/project.cquery'
WARNING [0012] : Component request
org.apache.log4j:osgi.bundle/[1.2.13.v200903072027,1.2.13.v200903072027]
is in conflict with request org.apache.log4j:osgi.bundle/1.2.15
ERROR [0012] : No suitable provider for component
org.apache.log4j.source:osgi.bundle/[1.2.13.v200903072027,1.2.13.v200903072027]
was found in resourceMap
file:/usr/share/tomcat6/.jenkins/workspace/xsemantics-buckminster-gerrit/releng/it.xsemantics.buckminster/project.rmap
ERROR [0012] : Unable to find a searchPath for
org.apache.log4j.source:osgi.bundle/[1.2.13.v200903072027,1.2.13.v200903072027]
WARNING [0012] : Component request
org.apache.log4j.source:osgi.bundle/[1.2.13.v200903072027,1.2.13.v200903072027]
is in conflict with request
org.apache.log4j.source:osgi.bundle/[1.2.15.v201012070815,1.2.15.v201012070815]
WARNING [0012] : Component request
org.apache.log4j:osgi.bundle/[1.2.13.v200903072027,1.2.13.v200903072027]
is in conflict with request
org.apache.log4j:osgi.bundle/[1.2.15.v201012070815,1.2.15.v201012070815]
WARNING [0012] : Component request
org.apache.log4j.source:osgi.bundle/[1.2.13.v200903072027,1.2.13.v200903072027]
is in conflict with request
org.apache.log4j.source:osgi.bundle/[1.2.15.v201012070815,1.2.15.v201012070815]
INFO: TAG-ID 0012 = Query for it.xsemantics.site:eclipse.feature, path:
it.xsemantics.site:eclipse.feature$1.0.0.qualifier ->
it.xsemantics.tests.feature:eclipse.feature$1.0.100.qualifier ->
org.eclipse.swtbot:eclipse.feature$2.0.5.20111003_1754-3676ac8-dev-e36

Now... this log4j plugin always troubled me (for instance, in my eclipse
installation I usually end up having both 1.2.13 and 1.2.15 and if I
don't remove manually 1.2.13 then xtend2 editor stops working...)

now it looks like it cannot get the source correctly (again, if I run
the job again, without wiping out the workspace, everything goes on
without errors, only warnings).

can I deal with this conflict somehow?

> I've added the "skip sources" advisor node to minimize the TP download
> size, so you can just remove or edit it. If you would like to include
> the swtbot sources in your project's repository, add following line to
> your buckminster.scpec (and edit or remove the advisor node above, of
> cause) :
> <cs:dependency name="org.eclipse.swtbot" componentType="eclipse.feature"/>

actually I wouldn't need the swtbot sources... but somehow this is
requested by something in my tests feature...

I understand that xtext sources come from xtext.sdk feature... but
there's no sdk feature for swtbot in my tests feature... or probably
it's org.eclipse.swtbot feature itself which wants sources...

thanks in advance
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net
Re: strange problem with Buckminster Wizard for existing Xtext language projects [message #892460 is a reply to message #892261] Thu, 28 June 2012 10:03 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo Bettini
Messages: 1368
Registered: July 2009
Senior Member
On 06/27/2012 04:11 PM, Lorenzo Bettini wrote:
> things get better now: if I wipe the workspace before the build the
> sources are downloaded... but one problem remains: I get errors only for
> this source bundle
>
> INFO: resolve 'releng/it.xsemantics.buckminster/project.cquery'
> WARNING [0012] : Component request
> org.apache.log4j:osgi.bundle/[1.2.13.v200903072027,1.2.13.v200903072027]
> is in conflict with request org.apache.log4j:osgi.bundle/1.2.15
> ERROR [0012] : No suitable provider for component
> org.apache.log4j.source:osgi.bundle/[1.2.13.v200903072027,1.2.13.v200903072027]
> was found in resourceMap
> file:/usr/share/tomcat6/.jenkins/workspace/xsemantics-buckminster-gerrit/releng/it.xsemantics.buckminster/project.rmap
>
> ERROR [0012] : Unable to find a searchPath for
> org.apache.log4j.source:osgi.bundle/[1.2.13.v200903072027,1.2.13.v200903072027]
>
> WARNING [0012] : Component request
> org.apache.log4j.source:osgi.bundle/[1.2.13.v200903072027,1.2.13.v200903072027]
> is in conflict with request
> org.apache.log4j.source:osgi.bundle/[1.2.15.v201012070815,1.2.15.v201012070815]
>
> WARNING [0012] : Component request
> org.apache.log4j:osgi.bundle/[1.2.13.v200903072027,1.2.13.v200903072027]
> is in conflict with request
> org.apache.log4j:osgi.bundle/[1.2.15.v201012070815,1.2.15.v201012070815]
> WARNING [0012] : Component request
> org.apache.log4j.source:osgi.bundle/[1.2.13.v200903072027,1.2.13.v200903072027]
> is in conflict with request
> org.apache.log4j.source:osgi.bundle/[1.2.15.v201012070815,1.2.15.v201012070815]
>
> INFO: TAG-ID 0012 = Query for it.xsemantics.site:eclipse.feature, path:
> it.xsemantics.site:eclipse.feature$1.0.0.qualifier ->
> it.xsemantics.tests.feature:eclipse.feature$1.0.100.qualifier ->
> org.eclipse.swtbot:eclipse.feature$2.0.5.20111003_1754-3676ac8-dev-e36
>
> Now... this log4j plugin always troubled me (for instance, in my eclipse
> installation I usually end up having both 1.2.13 and 1.2.15 and if I
> don't remove manually 1.2.13 then xtend2 editor stops working...)
>
> now it looks like it cannot get the source correctly (again, if I run
> the job again, without wiping out the workspace, everything goes on
> without errors, only warnings).
>
> can I deal with this conflict somehow?
>
>> I've added the "skip sources" advisor node to minimize the TP download
>> size, so you can just remove or edit it. If you would like to include
>> the swtbot sources in your project's repository, add following line to
>> your buckminster.scpec (and edit or remove the advisor node above, of
>> cause) :
>> <cs:dependency name="org.eclipse.swtbot"
>> componentType="eclipse.feature"/>
>
> actually I wouldn't need the swtbot sources... but somehow this is
> requested by something in my tests feature...
>
> I understand that xtext sources come from xtext.sdk feature... but
> there's no sdk feature for swtbot in my tests feature... or probably
> it's org.eclipse.swtbot feature itself which wants sources...

Hi

I think I solved this problem (but any feedback would be welcome :)

of course I need xtext sources since the test feature includes xtext.sdk
which seems to require sources

as for log4j it looks like the orbit update site provides the sources
for log4j 1.2.15, but not for 1.2.13 (for this, only the binaries) (!)

see for instance
http://download.eclipse.org/tools/orbit/downloads/drops/R20120526062928/

fortunately, the sources for log4j are not strictly required by swtbot,
thus I can modify the projects-platform.cquery as follows

<?xml version="1.0" encoding="UTF-8"?>
<cq:componentQuery
xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
resourceMap="projects-platform.rmap">
<cq:rootRequest name="it.xsemantics.buckminster"
componentType="buckminster"/>
<cq:property key="buckminster.download.source" value="true"/>
<cq:property key="target.arch" value="*"/>
<cq:property key="target.os" value="*"/>
<cq:property key="target.ws" value="*"/>
<cq:advisorNode namePattern="^org\.apache.*\.source$"
skipComponent="true"/>
</cq:componentQuery>

i.e., instruct to download also the sources (required by xtext.sdk), but
excluding the sources for org.apache.* bundles with the advisor node.

This, however would trouble project.cquery, since the target platform
would be resolved, but then, when resolving the projects the sources for
log4j would still be required (I don't know how, actually), thus, I need
to modify project.cquery with a similar advisor node

<?xml version="1.0" encoding="UTF-8"?>
<cq:componentQuery
xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
resourceMap="project.rmap">
<cq:rootRequest name="it.xsemantics.site"
componentType="eclipse.feature"/>
<cq:advisorNode namePattern="^org\.apache.*\.source$"
skipComponent="true"/>
</cq:componentQuery>

this solves my problems (the Jenkins job works both from a wiped
workspace and from an existing workspace)

but I'd like to know whether the solution makes sense :)

thanks in advance
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net
Re: strange problem with Buckminster Wizard for existing Xtext language projects [message #892470 is a reply to message #892460] Thu, 28 June 2012 10:42 Go to previous messageGo to next message
Dennis Huebner is currently offline Dennis Huebner
Messages: 213
Registered: July 2009
Senior Member

Quote:

of course I need xtext sources since the test feature includes xtext.sdk
which seems to require sources

You probably just need xtext.junit or xtext.junit4 bundles from the xtext.sdk and not the whole feature.

Quote:

fortunately, the sources for log4j are not strictly required by swtbot,

It don't require it at all I think, see http://git.eclipse.org/c/swtbot/org.eclipse.swtbot.git/tree/org.eclipse.swtbot/feature.xml
I think that buckminster.download.source value="true" cause that log4j sources became required.

Quote:

thus I can modify the projects-platform.cquery as follows
...
i.e., instruct to download also the sources (required by xtext.sdk), but
excluding the sources for org.apache.* bundles with the advisor node.

IMHO it is better to remove buckminster.download.source value="true" again, and instead add only the stuff you really need in your buckminster.cspec
 <cs:dependency name="org.eclipse.platform" componentType="eclipse.feature"/>
        <cs:dependency name="org.eclipse.xtext.sdk" componentType="eclipse.feature"/>
         <cs:dependency name="org.eclipse.swtbot" componentType="eclipse.feature"/>

Or even better add the dependencies to the bundles not to the features (where possible). I.e. if you need a bundle X you don't have to import the whole feature with lots of other bundles(and probably extra dependencies) in it.
Quote:

This, however would trouble project.cquery, since the target platform
would be resolved, but then, when resolving the projects the sources for
log4j would still be required (I don't know how, actually), thus, I need
to modify project.cquery with a similar advisor node

The task of the platform cquery file, is to materialize the platform your project can build on. So after it is resolved any 3rd party artifacts should be missing or requested by the project cquery.

Regards,
Dennis.


Re: strange problem with Buckminster Wizard for existing Xtext language projects [message #892533 is a reply to message #892470] Thu, 28 June 2012 14:38 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo Bettini
Messages: 1368
Registered: July 2009
Senior Member
On 06/28/2012 12:42 PM, Dennis Huebner wrote:
> Quote:
>> of course I need xtext sources since the test feature includes
>> xtext.sdk which seems to require sources
>
> You probably just need xtext.junit or xtext.junit4 bundles from the
> xtext.sdk and not the whole feature.
>

I'll try this also even because I now have another problem (see below)

> Quote:
>> fortunately, the sources for log4j are not strictly required by swtbot,
>
> It don't require it at all I think, see
> http://git.eclipse.org/c/swtbot/org.eclipse.swtbot.git/tree/org.eclipse.swtbot/feature.xml
>
> I think that buckminster.download.source value="true" cause that log4j
> sources became required.

I had solved this with the specific advisor node but...

>
> Quote:
>> thus I can modify the projects-platform.cquery as follows
>> ...
>> i.e., instruct to download also the sources (required by xtext.sdk),
>> but excluding the sources for org.apache.* bundles with the advisor node.
>
> IMHO it is better to remove buckminster.download.source value="true"
> again, and instead add only the stuff you really need in your
> buckminster.cspec
> <cs:dependency name="org.eclipse.platform"
> componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.xtext.sdk"
> componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.swtbot"
> componentType="eclipse.feature"/>

I already had this but the sources, from what I understand, are required
at the moment that buckminster imports my test feature which includes
xtext.sdk if I understand correctly...

> Or even better add the dependencies to the bundles not to the features
> (where possible). I.e. if you need a bundle X you don't have to import
> the whole feature with lots of other bundles(and probably extra
> dependencies) in it.
> Quote:
>> This, however would trouble project.cquery, since the target platform
>> would be resolved, but then, when resolving the projects the sources
>> for log4j would still be required (I don't know how, actually), thus,
>> I need to modify project.cquery with a similar advisor node
>
> The task of the platform cquery file, is to materialize the platform
> your project can build on. So after it is resolved any 3rd party
> artifacts should be missing or requested by the project cquery.

I see

now after switching to xtext 2.3 Juno released today, I updated the rmap
in order to use juno update site and xtext composite release update site
and the problem with sources looks solved, but now I have problems when
building the site:

INFO: perform '-D' 'target.os=*' '-D' 'target.ws=*' '-D'
'target.arch=*' 'it.xsemantics.site#site.p2.zip'
CSpec org.eclipse.equinox.common:osgi.bundle$3.6.100.v20120522-1841 has
no action, group, or local artifact named java.binaries

that's why I want to get rid of downloading sources

but can the error above be due also to the fact that I'm still using
buckminster 3.7?

I'll now try to get rid of sources anyway :)

thanks again
cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net
Re: strange problem with Buckminster Wizard for existing Xtext language projects [message #892808 is a reply to message #892470] Fri, 29 June 2012 19:16 Go to previous message
Lorenzo Bettini is currently offline Lorenzo Bettini
Messages: 1368
Registered: July 2009
Senior Member
On 06/28/2012 12:42 PM, Dennis Huebner wrote:
> Quote:
>> of course I need xtext sources since the test feature includes
>> xtext.sdk which seems to require sources
>
> You probably just need xtext.junit or xtext.junit4 bundles from the
> xtext.sdk and not the whole feature.
>
> Quote:
>> fortunately, the sources for log4j are not strictly required by swtbot,
>
> It don't require it at all I think, see
> http://git.eclipse.org/c/swtbot/org.eclipse.swtbot.git/tree/org.eclipse.swtbot/feature.xml
>
> I think that buckminster.download.source value="true" cause that log4j
> sources became required.
>
> Quote:
>> thus I can modify the projects-platform.cquery as follows
>> ...
>> i.e., instruct to download also the sources (required by xtext.sdk),
>> but excluding the sources for org.apache.* bundles with the advisor node.
>
> IMHO it is better to remove buckminster.download.source value="true"
> again, and instead add only the stuff you really need in your
> buckminster.cspec
> <cs:dependency name="org.eclipse.platform"
> componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.xtext.sdk"
> componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.swtbot"
> componentType="eclipse.feature"/>
> Or even better add the dependencies to the bundles not to the features
> (where possible). I.e. if you need a bundle X you don't have to import
> the whole feature with lots of other bundles(and probably extra
> dependencies) in it.

Hi Dennis

I managed to remove xtext.sdk from the test feature and now I don't need
sources anymore :)

thanks a lot!
cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net
Previous Topic:Buckminster plans for Eclipse Juno (4.2)
Next Topic:Hudson
Goto Forum:
  


Current Time: Thu Oct 23 00:39:58 GMT 2014

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

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