Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » Buckminster does not materialize the source for all plugins(Buckminster materializes two versions of org.apache.commons.logging (1.0.4 and 1.1.1), but only the source for one of them and that leads to the subsequent build failure)
Buckminster does not materialize the source for all plugins [message #720522] Tue, 30 August 2011 18:51 Go to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
I am trying to find out why buckminster does not materialize the source for all plugins. This is a problem is discovered and described in this thread.

As you can see buckminster materializes two versions of org.apache.commons.logging
(1.0.4 and 1.1.1), but only the source for one of them and that leads to the subsequent build failure.

Any help to fix this problem is highly appreciated.


Validating what buckminster did materialize:
$ find targetPlatform -name "*org.apache.commons.logging*"

targetPlatform/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar
targetPlatform/plugins/org.apache.commons.logging.source_1.0.4.v201101211617.jar
targetPlatform/plugins/org.apache.commons.logging_1.0.4.v201101211617.jar



Here's my buckminster configuration I use:

test_rcp.cquery:
<?xml version="1.0" encoding="UTF-8"?>
<cq:componentQuery xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0" resourceMap="initial.rmap">
    <cq:rootRequest name="test_rcp_components" componentType="buckminster"/>
    <cq:advisorNode namePattern=".*" useTargetPlatform="true" useWorkspace="false"/>
    <cq:property key="target.arch" value="*"/>
    <cq:property key="target.os" value="*"/>
    <cq:property key="target.ws" value="*"/>
    <cq:property key="buckminster.download.source" value="true"/>
    <cq:property key="buckminster.convert.source" value="true"/>
</cq:componentQuery>


test_rcp_components/buckminster.cspec:
<?xml version="1.0" encoding="UTF-8"?>
<cs:cspec xmlns:cs="http://www.eclipse.org/buckminster/CSpec-1.0"
   name="test_rcp_components"
   shortDesc="test_rcp_components"
   version="1.0.0"
   versionType="OSGi">

   <cs:dependencies>
    <cs:dependency name="org.eclipse.platform" componentType="eclipse.feature"/>
    <cs:dependency name="org.eclipse.equinox.sdk" componentType="eclipse.feature"/>
    <cs:dependency name="org.eclipse.equinox.p2.sdk" componentType="eclipse.feature"/>
    <cs:dependency name="org.eclipse.sdk" componentType="eclipse.feature"/>
    <cs:dependency name="org.eclipse.emf.sdk" componentType="eclipse.feature"/>
    <cs:dependency name="org.eclipse.emf.cdo.sdk" componentType="eclipse.feature"/>
    <cs:dependency name="org.eclipse.net4j.sdk" componentType="eclipse.feature"/>
    <cs:dependency name="org.eclipse.net4j.db.feature.group" componentType="eclipse.feature"/>
    <cs:dependency name="org.eclipse.ocl.core.sdk" componentType="eclipse.feature"/>
    <cs:dependency name="org.eclipse.birt" componentType="eclipse.feature"/>
    
    <cs:dependency name="com.mysql.jdbc" componentType="osgi.bundle"/>
    <cs:dependency name="org.eclipse.net4j.db.mysql" componentType="osgi.bundle"/>
    <cs:dependency name="org.apache.commons.beanutils" componentType="osgi.bundle"/>
    <cs:dependency name="org.apache.commons.collections" componentType="osgi.bundle"/>
    <cs:dependency name="org.apache.commons.logging" componentType="osgi.bundle"/>
    <cs:dependency name="org.apache.shiro.core" componentType="osgi.bundle"/>
    <cs:dependency name="org.apache.shiro.web" componentType="osgi.bundle"/>
    <cs:dependency name="slf4j.api" componentType="osgi.bundle"/>
    <cs:dependency name="slf4j.jcl" componentType="osgi.bundle"/>
    <cs:dependency name="slf4j.simple" componentType="osgi.bundle"/>
   </cs:dependencies>
</cs:cspec>


test_rcp.mspec:
<?xml version="1.0" encoding="UTF-8"?>
<mspec
	xmlns="http://www.eclipse.org/buckminster/MetaData-1.0"
	name="Target Platform MSPEC"
	materializer="p2"
	installLocation="${targetPlatformPath}"
	url="test_rcp.cquery">
<property key="target.arch" value="*" />
<property key="target.os" value="*" />
<property key="target.ws" value="*" />
</mspec>


initial.rmap:
<rm:rmap xmlns:rm="http://www.eclipse.org/buckminster/RMap-1.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
  xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
>
  <rm:searchPath name="buckminster">
    <rm:provider componentTypes="buckminster" readerType="local">
      <rm:uri format="file://{0}/../{1}">
	<bc:propertyRef key="workspace.root" />
        <bc:propertyRef key="buckminster.component"/>
      </rm:uri>
    </rm:provider>
  </rm:searchPath>

  <rm:locator searchPathRef="buckminster" pattern="^test_rcp_components" failOnError="true" />
  <rm:redirect href="platform.rmap" />
</rm:rmap>


platform.rmap:
<rm:rmap xmlns:rm="http://www.eclipse.org/buckminster/RMap-1.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
  xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
>
  <rm:property key="eclipse.release" value="indigo"/>
  
  <rm:searchPath name="org.eclipse.platform">
    <rm:provider
      resolutionFilter="(eclipse.release=indigo)"
      componentTypes="osgi.bundle,eclipse.feature"
      readerType="p2"
      source="false"
      mutable="false"
    >
      <rm:uri format="http://download.eclipse.org/eclipse/updates/3.7/?importType=binary"/>
    </rm:provider>
    <rm:provider
      resolutionFilter="(eclipse.release=helios)"
      componentTypes="osgi.bundle,eclipse.feature"
      readerType="p2"
      source="false"
      mutable="false"
    >
      <rm:uri format="http://download.eclipse.org/eclipse/updates/3.6/?importType=binary"/>
    </rm:provider>
    <rm:provider
      resolutionFilter="(eclipse.release=galileo)"
      componentTypes="osgi.bundle,eclipse.feature"
      readerType="p2"
      source="false"
      mutable="false"
    >
      <rm:uri format="http://download.eclipse.org/eclipse/updates/3.5/?importType=binary"/>
    </rm:provider>
  </rm:searchPath>
  
  <rm:searchPath name="org.eclipse">
    <rm:provider
      resolutionFilter="(eclipse.release=indigo)"
      componentTypes="osgi.bundle,eclipse.feature"
      readerType="p2"
      source="false"
      mutable="false"
    >
      <rm:uri format="http://download.eclipse.org/releases/indigo/?importType=binary"/>
    </rm:provider>
    <rm:provider
      resolutionFilter="(eclipse.release=helios)"
      componentTypes="osgi.bundle,eclipse.feature"
      readerType="p2"
      source="false"
      mutable="false"
    >
      <rm:uri format="http://download.eclipse.org/releases/helios/?importType=binary"/>
    </rm:provider>
    <rm:provider
      resolutionFilter="(eclipse.release=galileo)"
      componentTypes="osgi.bundle,eclipse.feature"
      readerType="p2"
      source="false"
      mutable="false"
    >
      <rm:uri format="http://download.eclipse.org/releases/galileo/?importType=binary"/>
    </rm:provider>
  </rm:searchPath>
  
  <rm:searchPath name="org.eclipse.emf.cdo">
    <rm:provider
      resolutionFilter="(eclipse.release=helios)"
      componentTypes="osgi.bundle,eclipse.feature"
      readerType="p2"
      source="false"
      mutable="false"
    >
      <rm:uri format="http://download.eclipse.org/modeling/emf/cdo/updates/releases/3.0/?importType=binary"/>
    </rm:provider>

    <rm:provider
      resolutionFilter="(eclipse.release=indigo)"
      componentTypes="osgi.bundle,eclipse.feature"
      readerType="p2"
      source="false"
      mutable="false"
    >
      <rm:uri format="http://download.eclipse.org/modeling/emf/cdo/updates/releases/4.0/?importType=binary"/>
    </rm:provider>
  </rm:searchPath>

  <rm:searchPath name="net4j.sourceforge.net">
    <rm:provider
      componentTypes="osgi.bundle,eclipse.feature"
      readerType="p2"
      source="false"
      mutable="false"
    >
      <rm:uri format="http://net4j.sourceforge.net/update/?importType=binary"/>
    </rm:provider>
  </rm:searchPath>

  <rm:searchPath name="maven">
    <rm:provider
      xsi:type="mp:MavenProvider"
      readerType="maven2"
      componentTypes="maven,osgi.bundle"
      mutable="false"
      source="false"
    >
      <rm:uri format="http://repo1.maven.org/maven2"/>
      <mp:mappings>
	<mp:entry artifactId="shiro-core" groupId="org.apache.shiro" name="org.apache.shiro.core" />
	<mp:entry artifactId="shiro-web" groupId="org.apache.shiro" name="org.apache.shiro.web" />
	<mp:entry artifactId="slf4j-api" groupId="org.slf4j" name="slf4j.api" />
	<mp:entry artifactId="slf4j-jcl" groupId="org.slf4j" name="slf4j.jcl" />
	<mp:entry artifactId="slf4j-simple" groupId="org.slf4j" name="slf4j.simple" />
      </mp:mappings>
    </rm:provider>
  </rm:searchPath>

  <rm:searchPath name="orbit">
    <rm:provider
      componentTypes="osgi.bundle,eclipse.feature"
      readerType="p2"
      source="false"
      mutable="false"
    >
      <rm:uri format="http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/repository/?importType=binary"/>
    </rm:provider>
  </rm:searchPath>

  <rm:locator searchPathRef="maven" pattern="^org\.apache\.shiro(\..+)?" failOnError="true" />
  <rm:locator searchPathRef="maven" pattern="^slf4j(\..+)?" failOnError="true" />
  <rm:locator searchPathRef="org.eclipse.emf.cdo" pattern="^org.eclipse.emf.cdo(\..+)?" failOnError="true" />
  <rm:locator searchPathRef="org.eclipse.emf.cdo" pattern="^org.eclipse.net4j(\..+)?" failOnError="true" />
  <rm:locator searchPathRef="net4j.sourceforge.net" pattern="^org.eclipse.net4j(\..+)?" failOnError="true" />
  <rm:locator searchPathRef="net4j.sourceforge.net" pattern="^com.mysql.jdbc(\..+)?" failOnError="true" />
  <rm:locator searchPathRef="org.eclipse.platform" failOnError="false" />
  <rm:locator searchPathRef="org.eclipse" failOnError="true" />
  <!--rm:locator searchPathRef="orbit" failOnError="true" /-->
</rm:rmap>


Re: Buckminster does not materialize the source for all plugins [message #720577 is a reply to message #720522] Tue, 30 August 2011 20:37 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
You get errors indicating failure to find the org.apache.commons.logging.source bundle using the 'local' readerType in
searchPath 'local'. I can't understand how that would happen given the cquery/rmaps that you attached.

- thomas

On 2011-08-30 20:51, Lothar Werzinger wrote:
> I am trying to find out why buckminster does not materialize the source for all plugins. This is a problem is discovered
> and described in http://www.eclipse.org/forums/index.php/t/237023/.
>
> As you can see buckminster materializes two versions of org.apache.commons.logging
> (1.0.4 and 1.1.1), but only the source for one of them and that leads to the subsequent build failure.
>
> Any help to fix this problem is highly appreciated.
>
>
> Validating what buckminster did materialize:
>
> $ find targetPlatform -name "*org.apache.commons.logging*"
>
> targetPlatform/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar
> targetPlatform/plugins/org.apache.commons.logging.source_1.0.4.v201101211617.jar
> targetPlatform/plugins/org.apache.commons.logging_1.0.4.v201101211617.jar
>
>
>
> Here's my buckminster configuration I use:
>
> test_rcp.cquery:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <cq:componentQuery xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0" resourceMap="initial.rmap">
> <cq:rootRequest name="test_rcp_components" componentType="buckminster"/>
> <cq:advisorNode namePattern=".*" useTargetPlatform="true" useWorkspace="false"/>
> <cq:property key="target.arch" value="*"/>
> <cq:property key="target.os" value="*"/>
> <cq:property key="target.ws" value="*"/>
> <cq:property key="buckminster.download.source" value="true"/>
> <cq:property key="buckminster.convert.source" value="true"/>
> </cq:componentQuery>
>
>
> test_rcp_components/buckminster.cspec:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <cs:cspec xmlns:cs="http://www.eclipse.org/buckminster/CSpec-1.0"
> name="test_rcp_components"
> shortDesc="test_rcp_components"
> version="1.0.0"
> versionType="OSGi">
>
> <cs:dependencies>
> <cs:dependency name="org.eclipse.platform" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.equinox.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.equinox.p2.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.emf.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.emf.cdo.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.net4j.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.net4j.db.feature.group" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.ocl.core.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.birt" componentType="eclipse.feature"/>
> <cs:dependency name="com.mysql.jdbc" componentType="osgi.bundle"/>
> <cs:dependency name="org.eclipse.net4j.db.mysql" componentType="osgi.bundle"/>
> <cs:dependency name="org.apache.commons.beanutils" componentType="osgi.bundle"/>
> <cs:dependency name="org.apache.commons.collections" componentType="osgi.bundle"/>
> <cs:dependency name="org.apache.commons.logging" componentType="osgi.bundle"/>
> <cs:dependency name="org.apache.shiro.core" componentType="osgi.bundle"/>
> <cs:dependency name="org.apache.shiro.web" componentType="osgi.bundle"/>
> <cs:dependency name="slf4j.api" componentType="osgi.bundle"/>
> <cs:dependency name="slf4j.jcl" componentType="osgi.bundle"/>
> <cs:dependency name="slf4j.simple" componentType="osgi.bundle"/>
> </cs:dependencies>
> </cs:cspec>
>
>
> test_rcp.mspec:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <mspec
> xmlns="http://www.eclipse.org/buckminster/MetaData-1.0"
> name="Target Platform MSPEC"
> materializer="p2"
> installLocation="${targetPlatformPath}"
> url="test_rcp.cquery">
> <property key="target.arch" value="*" />
> <property key="target.os" value="*" />
> <property key="target.ws" value="*" />
> </mspec>
>
>
> initial.rmap:
>
> <rm:rmap xmlns:rm="http://www.eclipse.org/buckminster/RMap-1.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
> xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
>>
> <rm:searchPath name="buckminster">
> <rm:provider componentTypes="buckminster" readerType="local">
> <rm:uri format="file://{0}/../{1}">
> <bc:propertyRef key="workspace.root" />
> <bc:propertyRef key="buckminster.component"/>
> </rm:uri>
> </rm:provider>
> </rm:searchPath>
>
> <rm:locator searchPathRef="buckminster" pattern="^test_rcp_components" failOnError="true" />
> <rm:redirect href="platform.rmap" />
> </rm:rmap>
>
>
> platform.rmap:
>
> <rm:rmap xmlns:rm="http://www.eclipse.org/buckminster/RMap-1.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
> xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
>>
> <rm:property key="eclipse.release" value="indigo"/>
>
> <rm:searchPath name="org.eclipse.platform">
> <rm:provider
> resolutionFilter="(eclipse.release=indigo)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/eclipse/updates/3.7/?importType=binary"/>
> </rm:provider>
> <rm:provider
> resolutionFilter="(eclipse.release=helios)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/eclipse/updates/3.6/?importType=binary"/>
> </rm:provider>
> <rm:provider
> resolutionFilter="(eclipse.release=galileo)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/eclipse/updates/3.5/?importType=binary"/>
> </rm:provider>
> </rm:searchPath>
>
> <rm:searchPath name="org.eclipse">
> <rm:provider
> resolutionFilter="(eclipse.release=indigo)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/releases/indigo/?importType=binary"/>
> </rm:provider>
> <rm:provider
> resolutionFilter="(eclipse.release=helios)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/releases/helios/?importType=binary"/>
> </rm:provider>
> <rm:provider
> resolutionFilter="(eclipse.release=galileo)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/releases/galileo/?importType=binary"/>
> </rm:provider>
> </rm:searchPath>
>
> <rm:searchPath name="org.eclipse.emf.cdo">
> <rm:provider
> resolutionFilter="(eclipse.release=helios)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/modeling/emf/cdo/updates/releases/3.0/?importType=binary"/>
> </rm:provider>
>
> <rm:provider
> resolutionFilter="(eclipse.release=indigo)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/modeling/emf/cdo/updates/releases/4.0/?importType=binary"/>
> </rm:provider>
> </rm:searchPath>
>
> <rm:searchPath name="net4j.sourceforge.net">
> <rm:provider
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://net4j.sourceforge.net/update/?importType=binary"/>
> </rm:provider>
> </rm:searchPath>
>
> <rm:searchPath name="maven">
> <rm:provider
> xsi:type="mp:MavenProvider"
> readerType="maven2"
> componentTypes="maven,osgi.bundle"
> mutable="false"
> source="false"
> >
> <rm:uri format="http://repo1.maven.org/maven2"/>
> <mp:mappings>
> <mp:entry artifactId="shiro-core" groupId="org.apache.shiro" name="org.apache.shiro.core" />
> <mp:entry artifactId="shiro-web" groupId="org.apache.shiro" name="org.apache.shiro.web" />
> <mp:entry artifactId="slf4j-api" groupId="org.slf4j" name="slf4j.api" />
> <mp:entry artifactId="slf4j-jcl" groupId="org.slf4j" name="slf4j.jcl" />
> <mp:entry artifactId="slf4j-simple" groupId="org.slf4j" name="slf4j.simple" />
> </mp:mappings>
> </rm:provider>
> </rm:searchPath>
>
> <rm:searchPath name="orbit">
> <rm:provider
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/repository/?importType=binary"/>
> </rm:provider>
> </rm:searchPath>
>
> <rm:locator searchPathRef="maven" pattern="^org\.apache\.shiro(\..+)?" failOnError="true" />
> <rm:locator searchPathRef="maven" pattern="^slf4j(\..+)?" failOnError="true" />
> <rm:locator searchPathRef="org.eclipse.emf.cdo" pattern="^org.eclipse.emf.cdo(\..+)?" failOnError="true" />
> <rm:locator searchPathRef="org.eclipse.emf.cdo" pattern="^org.eclipse.net4j(\..+)?" failOnError="true" />
> <rm:locator searchPathRef="net4j.sourceforge.net" pattern="^org.eclipse.net4j(\..+)?" failOnError="true" />
> <rm:locator searchPathRef="net4j.sourceforge.net" pattern="^com.mysql.jdbc(\..+)?" failOnError="true" />
> <rm:locator searchPathRef="org.eclipse.platform" failOnError="false" />
> <rm:locator searchPathRef="org.eclipse" failOnError="true" />
> <!--rm:locator searchPathRef="orbit" failOnError="true" /-->
> </rm:rmap>
>
>
>
Re: Buckminster does not materialize the source for all plugins [message #720581 is a reply to message #720577] Tue, 30 August 2011 21:28 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Thomas Hallgren wrote on Tue, 30 August 2011 13:37
You get errors indicating failure to find the org.apache.commons.logging.source bundle using the 'local' readerType in
searchPath 'local'. I can't understand how that would happen given the cquery/rmaps that you attached.

- thomas


Not sure what errors you refer to.

If you mean the error from "using the TP" to build, then yes, the build uses a local reader and the (previously created) TP only to build and the error is that the org.apache.commons.logging.source bundle is not found by the local reader (as buckminster never mentions the search in the TP). I could present the buckminster config for the feature build, too if necessary, as the configuration files here are only for the hudson job that builds the TP. The other hudson job just uses the (previously built) TP to build a feature (so far unsucessfully).

What I don't understand is why the TP created by the configuration attached lacks some source plugins (org.apache.commons.logging.source is not the only one) for certain plugins.

I am really stuck here, as my build does not work complaining about the missing source plugin and I have no idea how to fix that.
Re: Buckminster does not materialize the source for all plugins [message #720723 is a reply to message #720581] Wed, 31 August 2011 06:40 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2011-08-30 23:28, Lothar Werzinger wrote:
> Thomas Hallgren wrote on Tue, 30 August 2011 13:37
>> You get errors indicating failure to find the org.apache.commons.logging.source bundle using the 'local' readerType in
>> searchPath 'local'. I can't understand how that would happen given the cquery/rmaps that you attached.
>>
>> - thomas
>
>
> Not sure what errors you refer to.
>
> If you mean the error from "using the TP" to build, then yes, the build uses a local reader and the (previously created)
> TP only to build and the error is that the org.apache.commons.logging.source bundle is not found by the local reader (as
> buckminster never mentions the search in the TP). I could present the buckminster config for the feature build, too if
> necessary, as the configuration files here are only for the hudson job that builds the TP. The other hudson job just
> uses the (previously built) TP to build a feature (so far unsucessfully).
>
You referred to another forum thread. I meant the errors in that thread. They don't seem correlated with the buckminster
files that you present here so I have no idea what I'm looking at or what problems that are caused by what files.

> What I don't understand is why the TP created by the configuration attached lacks some source plugins
> (org.apache.commons.logging.source is not the only one) for certain plugins.
>
> I am really stuck here, as my build does not work complaining about the missing source plugin and I have no idea how to
> fix that.
>
Are you using the 'buckminster.download.source=true' when you materialize the target platform?
Have you verified that the repositories actually contain the sources that you are missing?

- thomas
Re: Buckminster does not materialize the source for all plugins [message #721008 is a reply to message #720723] Wed, 31 August 2011 16:47 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Thomas Hallgren wrote on Tue, 30 August 2011 23:40

On 2011-08-30 23:28, Lothar Werzinger wrote:
> I am really stuck here, as my build does not work complaining about the missing source plugin and I have no idea how to
> fix that.
>
Are you using the 'buckminster.download.source=true' when you materialize the target platform?
Have you verified that the repositories actually contain the sources that you are missing?

- thomas


I have attached a zip file containing two hudson jobs.
The first one creates the target platform and the second one tries to build a site.p2 action on a feature.
The jobs are self contained and should allow you to reproduce my problem.

After building the TP you can go to
test_tp/lastSuccessfulBuild/artifact/targetPlatform/plugins/
and you'll see that these org.apache.commons.logging plugins are part of the TP:

org.apache.commons.logging.source_1.0.4.v201101211617.jar	53908	 view
org.apache.commons.logging_1.0.4.v201101211617.jar		45405	 view
org.apache.commons.logging_1.1.1.v201101211721.jar		68101	 view


The test_build job will fail and the console log should look like this:
Started by upstream project "test_tp" build number 1
Cleaning the workspace because project is configured to clean the workspace before each build.
[workspace] $ /bin/sh -xe /tmp/hudson4776558603229827342.sh
+ rm -rf /var/lib/hudson/jobs/test_build/workspace/.metadata/
+ rm -rf /var/lib/hudson/jobs/test_build/workspace/mmt/
+ mkdir -p mmt/plugins mmt/features
+ rsync --delete -rv ../biz.tradescape.mmt.cdoserver.feature/ /var/lib/hudson/jobs/test_build/workspace/mmt/features/biz.tradescape.mmt.cdoserver.feature/
sending incremental file list
created directory /var/lib/hudson/jobs/test_build/workspace/mmt/features/biz.tradescape.mmt.cdoserver.feature
./
.project
build.properties
feature.xml

sent 1897 bytes  received 72 bytes  3938.00 bytes/sec
total size is 1687  speedup is 0.86
[workspace] $ java -Dbuckminster.output.root=/var/lib/hudson/jobs/test_build/workspace/buckminster.output -Dbuckminster.temp.root=/var/lib/hudson/jobs/test_build/workspace/buckminster.temp -Xmx256m -jar /var/lib/hudson/tools/Buckminster_3.6/buckminster/plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar -application org.eclipse.buckminster.cmdline.headless -data /var/lib/hudson/jobs/test_build/workspace --loglevel info -S /var/lib/hudson/jobs/test_build/workspace/commands.txt
INFO:  setpref 'targetPlatformPath=/var/lib/hudson/jobs/test_tp/builds/2011-08-31_09-15-35/archive//targetPlatform'
INFO:  resolve '../mmt-tools.cquery'
ERROR   [0006] : No suitable provider for component org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721] was found in resourceMap file:/var/lib/hudson/jobs/test_build/mmt-tools.rmap
  ERROR   [0006] : No suitable provider for component org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721] was found in searchPath local
    ERROR   [0006] : Resolution attempt ended with exception: Provider local(file:////var/lib/hudson/jobs/test_build/workspace/mmt/plugins/org.apache.commons.logging.source/): Missing CSpec source required by component type osgi.bundle
      ERROR   Provider local(file:////var/lib/hudson/jobs/test_build/workspace/mmt/plugins/org.apache.commons.logging.source/): Missing CSpec source required by component type osgi.bundle
    ERROR   [0006] : Rejecting provider local(file:///{0}/mmt/features/{1}/[file:////var/lib/hudson/jobs/test_build/workspace/mmt/features/org.apache.commons.logging.source/]): Components of type osgi.bundle are not supported
INFO:  TAG-ID 0006 = Query for biz.tradescape.mmt.cdoserver.feature:eclipse.feature, path: biz.tradescape.mmt.cdoserver.feature:eclipse.feature$1.0.0.qualifier -> org.eclipse.net4j:eclipse.feature$4.0.0.v20110608-1440

[DEBUG] Skipping watched dependency update for build: test_build #1 due to result: FAILURE
Finished: FAILURE


What's really puzzling is why the org.apache.commons.logging_1.0.4 get's materialized in the first place, as when I use the "Plug-in Dependencies" view in PDE it's not referenced at all, only org.apache.commons.logging_1.1.1 is:
index.php/fa/3835/0/
index.php/fa/3836/0/

Re: Buckminster does not materialize the source for all plugins [message #721085 is a reply to message #721008] Wed, 31 August 2011 20:35 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
One thing that you could try is to keep your rmap cleaner. Use only indigo and 3.7 for instance. If you want to base a
product on Helios and 3.6, you could do that too of course but I think trying to do both is asking for trouble.

- thomas


On 2011-08-31 18:47, Lothar Werzinger wrote:
> Thomas Hallgren wrote on Tue, 30 August 2011 23:40
>> On 2011-08-30 23:28, Lothar Werzinger wrote:
>>> I am really stuck here, as my build does not work complaining about the missing source plugin and I have no idea how to
>>> fix that.
>>>
>> Are you using the 'buckminster.download.source=true' when you materialize the target platform?
>> Have you verified that the repositories actually contain the sources that you are missing?
>>
>> - thomas
>
>
> I have attached a zip file containing two hudson jobs.
> The first one creates the target platform and the second one tries to build a site.p2 action on a feature.
> The jobs are self contained and should allow you to reproduce my problem.
>
> After building the TP you can go to
> test_tp/lastSuccessfulBuild/artifact/targetPlatform/plugins/
> and you'll see that these org.apache.commons.logging plugins are part of the TP:
>
>
> org.apache.commons.logging.source_1.0.4.v201101211617.jar 53908 view
> org.apache.commons.logging_1.0.4.v201101211617.jar 45405 view
> org.apache.commons.logging_1.1.1.v201101211721.jar 68101 view
>
>
> The test_build job will fail and the console log should look like this:
>
> Started by upstream project "test_tp" build number 1
> Cleaning the workspace because project is configured to clean the workspace before each build.
> [workspace] $ /bin/sh -xe /tmp/hudson4776558603229827342.sh
> + rm -rf /var/lib/hudson/jobs/test_build/workspace/.metadata/
> + rm -rf /var/lib/hudson/jobs/test_build/workspace/mmt/
> + mkdir -p mmt/plugins mmt/features
> + rsync --delete -rv ../biz.tradescape.mmt.cdoserver.feature/ /var/lib/hudson/jobs/test_build/workspace/mmt/features/biz.tradescape.mmt.cdoserver.feature/
> sending incremental file list
> created directory /var/lib/hudson/jobs/test_build/workspace/mmt/features/biz.tradescape.mmt.cdoserver.feature
> /
> project
> build.properties
> feature.xml
>
> sent 1897 bytes received 72 bytes 3938.00 bytes/sec
> total size is 1687 speedup is 0.86
> [workspace] $ java -Dbuckminster.output.root=/var/lib/hudson/jobs/test_build/workspace/buckminster.output -Dbuckminster.temp.root=/var/lib/hudson/jobs/test_build/workspace/buckminster.temp -Xmx256m -jar /var/lib/hudson/tools/Buckminster_3.6/buckminster/plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar -application org.eclipse.buckminster.cmdline.headless -data /var/lib/hudson/jobs/test_build/workspace --loglevel info -S /var/lib/hudson/jobs/test_build/workspace/commands.txt
> INFO: setpref 'targetPlatformPath=/var/lib/hudson/jobs/test_tp/builds/2011-08-31_09-15-35/archive//targetPlatform'
> INFO: resolve '../mmt-tools.cquery'
> ERROR [0006] : No suitable provider for component org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721] was found in resourceMap file:/var/lib/hudson/jobs/test_build/mmt-tools.rmap
> ERROR [0006] : No suitable provider for component org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721] was found in searchPath local
> ERROR [0006] : Resolution attempt ended with exception: Provider local(file:////var/lib/hudson/jobs/test_build/workspace/mmt/plugins/org.apache.commons.logging.source/): Missing CSpec source required by component type osgi.bundle
> ERROR Provider local(file:////var/lib/hudson/jobs/test_build/workspace/mmt/plugins/org.apache.commons.logging.source/): Missing CSpec source required by component type osgi.bundle
> ERROR [0006] : Rejecting provider local(file:///{0}/mmt/features/{1}/[file:////var/lib/hudson/jobs/test_build/workspace/mmt/features/org.apache.commons.logging.source/]): Components of type osgi.bundle are not supported
> INFO: TAG-ID 0006 = Query for biz.tradescape.mmt.cdoserver.feature:eclipse.feature, path: biz.tradescape.mmt.cdoserver.feature:eclipse.feature$1.0.0.qualifier -> org.eclipse.net4j:eclipse.feature$4.0.0.v20110608-1440
>
> [DEBUG] Skipping watched dependency update for build: test_build #1 due to result: FAILURE
> Finished: FAILURE
>
>
> What's really puzzling is why the org.apache.commons.logging_1.0.4 get's materialized in the first place, as when I use the "Plug-in Dependencies" view in PDE it's not referenced at all, only org.apache.commons.logging_1.1.1 is:
>
>
>
>
Re: Buckminster does not materialize the source for all plugins [message #721095 is a reply to message #721085] Wed, 31 August 2011 21:10 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
The failing build I am referring to is using indigo (via the filter mechanism), but I can try to remove the currently unused entries.

Edit:
As expected removing the unused entries in the rmap did not change (improve) the behaviour.

Can you please try to reproduce the problem with the jobs attached to the previous post? I tried many tweaks to the buckminster configuration (including a version override for the logging plugin), but nothing fixes the problem.

[Updated on: Wed, 31 August 2011 21:33]

Report message to a moderator

Re: Buckminster does not materialize the source for all plugins [message #721110 is a reply to message #721095] Wed, 31 August 2011 22:08 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Lothar Werzinger wrote on Wed, 31 August 2011 14:10
Can you please try to reproduce the problem with the jobs attached to the previous post? I tried many tweaks to the buckminster configuration (including a version override for the logging plugin), but nothing fixes the problem.


Attached:
Updated hudson jobs where the rmap is pruned.
Re: Buckminster does not materialize the source for all plugins [message #721199 is a reply to message #721110] Thu, 01 September 2011 07:23 Go to previous messageGo to next message
Philipp Nanz is currently offline Philipp Nanz
Messages: 46
Registered: February 2010
Member
In your platform.rmap, all your searchPaths are configured with source="false" and mutable="false". Try setting source to true everywhere and mutable to true on the maven provider (thats where the conversion is needed to be done as far as I understand).

Edit: Just tried out your example in IDE (Bucky 3.6), now I'm getting:

WARNING [0018] : Component request org.apache.commons.logging:osgi.bundle/[1.0.4.v201101211617,1.0.4.v201101211617] is inconflict with request org.apache.commons.logging:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721]
WARNING [0169] : Component request org.junit.source:osgi.bundle/[3.8.2.v3_8_2_v20100427-1100,3.8.2.v3_8_2_v20100427-1100] is inconflict with request org.junit.source:osgi.bundle/[4.8.2.v4_8_2_v20110321-1705,4.8.2.v4_8_2_v20110321-1705]
WARNING [0170] : Component request org.junit:osgi.bundle/[4.8.2.v4_8_2_v20110321-1705,4.8.2.v4_8_2_v20110321-1705] is inconflict with request org.junit:osgi.bundle/[3.8.2.v3_8_2_v20100427-1100,3.8.2.v3_8_2_v20100427-1100]
WARNING [0013] : Component request org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721](&(buckminster.download.source=true)(!(eclipse.p2.optional=false))) is inconflict with request org.apache.commons.logging.source:osgi.bundle/[1.0.4.v201101211617,1.0.4.v201101211617](&(buckminster.download.source=true)(!(eclipse.p2.optional=false)))
WARNING [0148] : Component request org.apache.lucene:osgi.bundle/[2.9.1.v201101211721,2.9.1.v201101211721] is inconflict with request org.apache.lucene:osgi.bundle/[1.9.1.v201101211617,1.9.1.v201101211617]
WARNING [0148] : Component request org.apache.lucene:osgi.bundle/[2.9.1.v201101211721,2.9.1.v201101211721] is inconflict with request org.apache.lucene:osgi.bundle/[1.9.0,2.0.0)
Unable to rename C:\Users\Philipp\Desktop\tp\plugins\org.apache.shiro.core.source_1.1.0.jar to C:\Users\Philipp\Desktop\tp\plugins\oldbundle-5378045911788511414.jar
Unable to rename C:\Users\Philipp\Desktop\tp\plugins\slf4j.jcl.source_1.6.2.jar to C:\Users\Philipp\Desktop\tp\plugins\oldbundle-2629178138742164099.jar
Unable to rename C:\Users\Philipp\Desktop\tp\plugins\slf4j.simple.source_1.6.2.jar to C:\Users\Philipp\Desktop\tp\plugins\oldbundle-1210845328529074811.jar
Unable to rename C:\Users\Philipp\Desktop\tp\plugins\org.apache.shiro.web.source_1.1.0.jar to C:\Users\Philipp\Desktop\tp\plugins\oldbundle-164527732072670517.jar
Unable to rename C:\Users\Philipp\Desktop\tp\plugins\slf4j.api.source_1.6.2.jar to C:\Users\Philipp\Desktop\tp\plugins\oldbundle-5948274677258636701.jar


Edit 2: The warnings seem to be harmless. Both versions are being materialized but I still only see org.apache.commons.logging.source_1.0.4.v201101211617 in the TP path (resolving is still running though, and I have to go now).

Edit 3: It would be interesting to know where the 1.1.1 version is coming from. To me it looks like the source repo (may it be p2 or maven), does not have proper source associated with it.

[Updated on: Thu, 01 September 2011 07:41]

Report message to a moderator

Re: Buckminster does not materialize the source for all plugins [message #721405 is a reply to message #721199] Thu, 01 September 2011 16:46 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Philipp Nanz wrote on Thu, 01 September 2011 00:23
In your platform.rmap, all your searchPaths are configured with source="false" and mutable="false". Try setting source to true everywhere and mutable to true on the maven provider (thats where the conversion is needed to be done as far as I understand).


As far as I know source="true" and mutable="true" is only used when one wants to build from source, not for materializing a target platform out of existing bundles.

Philipp Nanz wrote on Thu, 01 September 2011 00:23

Edit 2: The warnings seem to be harmless. Both versions are being materialized but I still only see org.apache.commons.logging.source_1.0.4.v201101211617 in the TP path (resolving is still running though, and I have to go now).


That is exactly my problem. Only 1.0.4 get's a source download, 1.1.1 doesn't.

Philipp Nanz wrote on Thu, 01 September 2011 00:23

Edit 3: It would be interesting to know where the 1.1.1 version is coming from. To me it looks like the source repo (may it be p2 or maven), does not have proper source associated with it.


Like I said in a previous post, the 1.0.4 is the more mysterious one, as it's not referenced by other plugins.

I would not care that it's there if buckminster would also download the source for the 1.1.1, but it doesn't.


Re: Buckminster does not materialize the source for all plugins [message #721420 is a reply to message #721405] Thu, 01 September 2011 17:49 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
There must be a way to create a valid working target platform out of the official Indigo repositories. If anyone knows how to fix this problem, please speak up. Thanks!

P.S.
Is there a way to find out why buckminster picks the 1.0.4 logging when PDE shows that it's not referenced by any other bundle? Maybe that would give a clue to what's wrong here.

[Updated on: Thu, 01 September 2011 17:51]

Report message to a moderator

Re: Buckminster does not materialize the source for all plugins [message #721463 is a reply to message #721420] Thu, 01 September 2011 19:52 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
Hi Lothar,

On 2011-09-01 19:49, Lothar Werzinger wrote:
> There must be a way to create a valid working target platform out of the official Indigo repositories. If anyone knows
> how to fix this problem, please speak up. Thanks!

We create target platforms for Buckminster, b3, and Geppetto. b3 is perhaps the most complex one and also the only one
that brings in both versions of the org.apache.commons.logging bundle. We don't see this problem though. We get source
bundles for both versions.

I'll try to find some time to try your setup over the weekend.

- thomas
Re: Buckminster does not materialize the source for all plugins [message #721464 is a reply to message #721405] Thu, 01 September 2011 19:54 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2011-09-01 18:46, Lothar Werzinger wrote:
> Philipp Nanz wrote on Thu, 01 September 2011 00:23
>> In your platform.rmap, all your searchPaths are configured with source="false" and mutable="false". Try setting source
>> to true everywhere and mutable to true on the maven provider (thats where the conversion is needed to be done as far
>> as I understand).
>
>
> As far as I know source="true" and mutable="true" is only used when one wants to build from source, not for
> materializing a target platform out of existing bundles.
>
Yes, your understanding is correct. You must never use source="true" when populating your TP. Even if the jars in
question contains source, they are still considered binary bundles in this context.

- thomas
Re: Buckminster does not materialize the source for all plugins [message #721477 is a reply to message #721463] Thu, 01 September 2011 21:10 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Thomas Hallgren wrote on Thu, 01 September 2011 12:52

Hi Lothar,

On 2011-09-01 19:49, Lothar Werzinger wrote:
> There must be a way to create a valid working target platform out of the official Indigo repositories. If anyone knows
> how to fix this problem, please speak up. Thanks!

We create target platforms for Buckminster, b3, and Geppetto. b3 is perhaps the most complex one and also the only one
that brings in both versions of the org.apache.commons.logging bundle. We don't see this problem though. We get source
bundles for both versions.


That's exactly what I need, to build a complex TP (with EMF, CDO, BIRT, RAP and even more things in the future).
Most examples like the famous mail example just need RCP and my experience so far is that while the easy configurations are usually working I always seem to run into problems with the complicated ones.

The fact that only one of the org.apache.commons.logging bundles is missing the source is what puzzles me most. As said earlier I could care less if there are two versions of the plugin in the TP as long as it does not create build problems later on.

Thomas Hallgren wrote on Thu, 01 September 2011 12:52

I'll try to find some time to try your setup over the weekend.

- thomas


That would be great! That is highly appreciated.
Thanks in advance!
Re: Buckminster does not materialize the source for all plugins [message #722491 is a reply to message #721477] Tue, 06 September 2011 00:12 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Thomas Hallgren wrote on Thu, 01 September 2011 12:52

I'll try to find some time to try your setup over the weekend.

- thomas


Did you have a chance to look into the issue? Any luck finding the cause?
Re: Buckminster does not materialize the source for all plugins [message #722548 is a reply to message #722491] Tue, 06 September 2011 06:31 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2011-09-06 02:12, Lothar Werzinger wrote:
> Thomas Hallgren wrote on Thu, 01 September 2011 12:52
>> I'll try to find some time to try your setup over the weekend.
>>
>> - thomas
>
>
> Did you have a chance to look into the issue? Any luck finding the cause?
>
Sorry, didn't find any time. Things are really busy right now. I haven't forgotten it though.

- thomas
Re: Buckminster does not materialize the source for all plugins [message #724477 is a reply to message #720522] Mon, 12 September 2011 12:19 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
Hi Lothar,

I found the cause of this problem and fixed it. You should get rid of the problem if you update to the most recent
Buckminster. More info here:

Bug 357060 - Generated conflicting source dependencies are sometimes left out
https://bugs.eclipse.org/bugs/show_bug.cgi?id=357060

Regards,
Thomas Hallgren

On 2011-08-30 20:51, Lothar Werzinger wrote:
> I am trying to find out why buckminster does not materialize the source for all plugins. This is a problem is discovered
> and described in http://www.eclipse.org/forums/index.php/t/237023/.
>
> As you can see buckminster materializes two versions of org.apache.commons.logging
> (1.0.4 and 1.1.1), but only the source for one of them and that leads to the subsequent build failure.
>
> Any help to fix this problem is highly appreciated.
>
>
> Validating what buckminster did materialize:
>
> $ find targetPlatform -name "*org.apache.commons.logging*"
>
> targetPlatform/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar
> targetPlatform/plugins/org.apache.commons.logging.source_1.0.4.v201101211617.jar
> targetPlatform/plugins/org.apache.commons.logging_1.0.4.v201101211617.jar
>
>
>
> Here's my buckminster configuration I use:
>
> test_rcp.cquery:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <cq:componentQuery xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0" resourceMap="initial.rmap">
> <cq:rootRequest name="test_rcp_components" componentType="buckminster"/>
> <cq:advisorNode namePattern=".*" useTargetPlatform="true" useWorkspace="false"/>
> <cq:property key="target.arch" value="*"/>
> <cq:property key="target.os" value="*"/>
> <cq:property key="target.ws" value="*"/>
> <cq:property key="buckminster.download.source" value="true"/>
> <cq:property key="buckminster.convert.source" value="true"/>
> </cq:componentQuery>
>
>
> test_rcp_components/buckminster.cspec:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <cs:cspec xmlns:cs="http://www.eclipse.org/buckminster/CSpec-1.0"
> name="test_rcp_components"
> shortDesc="test_rcp_components"
> version="1.0.0"
> versionType="OSGi">
>
> <cs:dependencies>
> <cs:dependency name="org.eclipse.platform" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.equinox.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.equinox.p2.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.emf.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.emf.cdo.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.net4j.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.net4j.db.feature.group" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.ocl.core.sdk" componentType="eclipse.feature"/>
> <cs:dependency name="org.eclipse.birt" componentType="eclipse.feature"/>
> <cs:dependency name="com.mysql.jdbc" componentType="osgi.bundle"/>
> <cs:dependency name="org.eclipse.net4j.db.mysql" componentType="osgi.bundle"/>
> <cs:dependency name="org.apache.commons.beanutils" componentType="osgi.bundle"/>
> <cs:dependency name="org.apache.commons.collections" componentType="osgi.bundle"/>
> <cs:dependency name="org.apache.commons.logging" componentType="osgi.bundle"/>
> <cs:dependency name="org.apache.shiro.core" componentType="osgi.bundle"/>
> <cs:dependency name="org.apache.shiro.web" componentType="osgi.bundle"/>
> <cs:dependency name="slf4j.api" componentType="osgi.bundle"/>
> <cs:dependency name="slf4j.jcl" componentType="osgi.bundle"/>
> <cs:dependency name="slf4j.simple" componentType="osgi.bundle"/>
> </cs:dependencies>
> </cs:cspec>
>
>
> test_rcp.mspec:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <mspec
> xmlns="http://www.eclipse.org/buckminster/MetaData-1.0"
> name="Target Platform MSPEC"
> materializer="p2"
> installLocation="${targetPlatformPath}"
> url="test_rcp.cquery">
> <property key="target.arch" value="*" />
> <property key="target.os" value="*" />
> <property key="target.ws" value="*" />
> </mspec>
>
>
> initial.rmap:
>
> <rm:rmap xmlns:rm="http://www.eclipse.org/buckminster/RMap-1.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
> xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
>>
> <rm:searchPath name="buckminster">
> <rm:provider componentTypes="buckminster" readerType="local">
> <rm:uri format="file://{0}/../{1}">
> <bc:propertyRef key="workspace.root" />
> <bc:propertyRef key="buckminster.component"/>
> </rm:uri>
> </rm:provider>
> </rm:searchPath>
>
> <rm:locator searchPathRef="buckminster" pattern="^test_rcp_components" failOnError="true" />
> <rm:redirect href="platform.rmap" />
> </rm:rmap>
>
>
> platform.rmap:
>
> <rm:rmap xmlns:rm="http://www.eclipse.org/buckminster/RMap-1.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
> xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
>>
> <rm:property key="eclipse.release" value="indigo"/>
>
> <rm:searchPath name="org.eclipse.platform">
> <rm:provider
> resolutionFilter="(eclipse.release=indigo)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/eclipse/updates/3.7/?importType=binary"/>
> </rm:provider>
> <rm:provider
> resolutionFilter="(eclipse.release=helios)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/eclipse/updates/3.6/?importType=binary"/>
> </rm:provider>
> <rm:provider
> resolutionFilter="(eclipse.release=galileo)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/eclipse/updates/3.5/?importType=binary"/>
> </rm:provider>
> </rm:searchPath>
>
> <rm:searchPath name="org.eclipse">
> <rm:provider
> resolutionFilter="(eclipse.release=indigo)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/releases/indigo/?importType=binary"/>
> </rm:provider>
> <rm:provider
> resolutionFilter="(eclipse.release=helios)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/releases/helios/?importType=binary"/>
> </rm:provider>
> <rm:provider
> resolutionFilter="(eclipse.release=galileo)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/releases/galileo/?importType=binary"/>
> </rm:provider>
> </rm:searchPath>
>
> <rm:searchPath name="org.eclipse.emf.cdo">
> <rm:provider
> resolutionFilter="(eclipse.release=helios)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/modeling/emf/cdo/updates/releases/3.0/?importType=binary"/>
> </rm:provider>
>
> <rm:provider
> resolutionFilter="(eclipse.release=indigo)"
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/modeling/emf/cdo/updates/releases/4.0/?importType=binary"/>
> </rm:provider>
> </rm:searchPath>
>
> <rm:searchPath name="net4j.sourceforge.net">
> <rm:provider
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://net4j.sourceforge.net/update/?importType=binary"/>
> </rm:provider>
> </rm:searchPath>
>
> <rm:searchPath name="maven">
> <rm:provider
> xsi:type="mp:MavenProvider"
> readerType="maven2"
> componentTypes="maven,osgi.bundle"
> mutable="false"
> source="false"
> >
> <rm:uri format="http://repo1.maven.org/maven2"/>
> <mp:mappings>
> <mp:entry artifactId="shiro-core" groupId="org.apache.shiro" name="org.apache.shiro.core" />
> <mp:entry artifactId="shiro-web" groupId="org.apache.shiro" name="org.apache.shiro.web" />
> <mp:entry artifactId="slf4j-api" groupId="org.slf4j" name="slf4j.api" />
> <mp:entry artifactId="slf4j-jcl" groupId="org.slf4j" name="slf4j.jcl" />
> <mp:entry artifactId="slf4j-simple" groupId="org.slf4j" name="slf4j.simple" />
> </mp:mappings>
> </rm:provider>
> </rm:searchPath>
>
> <rm:searchPath name="orbit">
> <rm:provider
> componentTypes="osgi.bundle,eclipse.feature"
> readerType="p2"
> source="false"
> mutable="false"
> >
> <rm:uri format="http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/repository/?importType=binary"/>
> </rm:provider>
> </rm:searchPath>
>
> <rm:locator searchPathRef="maven" pattern="^org\.apache\.shiro(\..+)?" failOnError="true" />
> <rm:locator searchPathRef="maven" pattern="^slf4j(\..+)?" failOnError="true" />
> <rm:locator searchPathRef="org.eclipse.emf.cdo" pattern="^org.eclipse.emf.cdo(\..+)?" failOnError="true" />
> <rm:locator searchPathRef="org.eclipse.emf.cdo" pattern="^org.eclipse.net4j(\..+)?" failOnError="true" />
> <rm:locator searchPathRef="net4j.sourceforge.net" pattern="^org.eclipse.net4j(\..+)?" failOnError="true" />
> <rm:locator searchPathRef="net4j.sourceforge.net" pattern="^com.mysql.jdbc(\..+)?" failOnError="true" />
> <rm:locator searchPathRef="org.eclipse.platform" failOnError="false" />
> <rm:locator searchPathRef="org.eclipse" failOnError="true" />
> <!--rm:locator searchPathRef="orbit" failOnError="true" /-->
> </rm:rmap>
>
>
>
Re: Buckminster does not materialize the source for all plugins [message #724686 is a reply to message #724477] Mon, 12 September 2011 20:06 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Thomas Hallgren wrote on Mon, 12 September 2011 05:19
Hi Lothar,

I found the cause of this problem and fixed it. You should get rid of the problem if you update to the most recent
Buckminster. More info here:

Bug 357060 - Generated conflicting source dependencies are sometimes left out
https://bugs.eclipse.org/bugs/show_bug.cgi?id=357060

Regards,
Thomas Hallgren


That's great news. Will there be a new release? I have my hands full trying the b3 aggregator as you suggested Wink and I would rather not have to build buckminster from source as an extra potential source of trouble.

Edit:
I checked https://hudson.eclipse.org/hudson/job/buckminster-head/, but it seems not to create any consumable artifacts.

[Updated on: Mon, 12 September 2011 22:04]

Report message to a moderator

Re: Buckminster does not materialize the source for all plugins [message #724747 is a reply to message #724686] Tue, 13 September 2011 04:30 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Lothar Werzinger wrote on Mon, 12 September 2011 13:06

I checked https://hudson.eclipse.org/hudson/job/buckminster-head/, but it seems not to create any consumable artifacts.


I tried to build buckminster myself (org.eclipse.buckminster.site.eclipse.headless and org.eclipse.buckminster.site.external); hudson job (buckminster_latest) config file is attached.

Now when I try to use the built buckminster from hudson via the automatic installer (installer configuration is attached, too), then it fails to install.

What is the trick to build and create p2 sites that work like the default http://download.eclipse.org/tools/buckminster/headless-3.6 and don't produce errors on install?

Here's the log snippet from the installation:
Unpacking http://download.eclipse.org/tools/buckminster/products/director_latest.zip to /var/lib/hudson/tools/Buckminster_git on Hudson
[Buckminster_git] $ /var/lib/hudson/tools/Buckminster_git/director/director -d /var/lib/hudson/tools/Buckminster_git/buckminster -p Buckminster -r "http://localhost:8080/job/buckminster_latest/lastSuccessfulBuild/artifact/external.p2/, http://localhost:8080/job/buckminster_latest/lastSuccessfulBuild/artifact/headless.p2/" -installIU "org.eclipse.equinox.p2.director.feature.feature.group, org.eclipse.buckminster.emma.headless.feature.feature.group, org.eclipse.buckminster.pde.headless.feature.feature.group, org.eclipse.buckminster.subclipse.headless.feature.feature.group, org.eclipse.buckminster.maven.headless.feature.feature.group, org.eclipse.buckminster.cmdline.product, org.eclipse.buckminster.core.headless.feature.feature.group, org.eclipse.buckminster.git.headless.feature.feature.group, org.eclipse.buckminster.cvs.headless.feature.feature.group"
Installing org.eclipse.equinox.p2.director.feature.feature.group 1.4.0.201109122116.
Installing org.eclipse.buckminster.emma.headless.feature.feature.group 0.9.0.201109122116.
Installing org.eclipse.buckminster.pde.headless.feature.feature.group 1.4.0.201109122116.
Installing org.eclipse.buckminster.subclipse.headless.feature.feature.group 1.4.0.201109122116.
Installing org.eclipse.buckminster.maven.headless.feature.feature.group 1.4.0.201109122116.
Installing org.eclipse.buckminster.cmdline.product 1.4.0.201109122116-13-cLZaeg31221_233227.
Installing org.eclipse.buckminster.core.headless.feature.feature.group 1.4.0.201109122116.
Installing org.eclipse.buckminster.git.headless.feature.feature.group 1.4.0.201109122116.
Installing org.eclipse.buckminster.cvs.headless.feature.feature.group 1.4.0.201109122116.
Installation failed.
Cannot complete the install because one or more required items could not be found.
 Software being installed: Buckminster 1.4.0.201109122116-13-cLZaeg31221_233227 (org.eclipse.buckminster.cmdline.product 1.4.0.201109122116-13-cLZaeg31221_233227)
 Missing requirement for filter properties ~= $0: org.eclipse.buckminster.cmdline.product.executable.gtk.linux.x86_64 1.4.0.201109122116-13-cLZaeg31221_233227 requires 'org.eclipse.equinox.launcher.gtk.linux.x86_64 0.0.0' but it could not be found
 Cannot satisfy dependency:
  From: Buckminster 1.4.0.201109122116-13-cLZaeg31221_233227 (org.eclipse.buckminster.cmdline.product 1.4.0.201109122116-13-cLZaeg31221_233227)
  To: toolingorg.eclipse.buckminster.cmdline.product.application [1.4.0.201109122116-13-cLZaeg31221_233227]
 Cannot satisfy dependency:
  From: toolingorg.eclipse.buckminster.cmdline.product.application 1.4.0.201109122116-13-cLZaeg31221_233227
  To: org.eclipse.buckminster.cmdline.product.executable.gtk.linux.x86_64 [1.4.0.201109122116-13-cLZaeg31221_233227]
Application failed, log file location: /var/lib/hudson/tools/Buckminster_git/director/configuration/1315887452373.log
FATAL: java.io.IOException: Command returned status 13
java.lang.RuntimeException: java.io.IOException: Command returned status 13
	at hudson.plugins.buckminster.EclipseBuckminsterBuilder.perform(EclipseBuckminsterBuilder.java:177)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:630)
	at hudson.model.Build$RunnerImpl.build(Build.java:175)
	at hudson.model.Build$RunnerImpl.doRun(Build.java:137)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:429)
	at hudson.model.Run.run(Run.java:1367)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:145)
Caused by: java.io.IOException: Command returned status 13
	at hudson.plugins.buckminster.BuckminsterInstallation$BuckminsterInstaller.executeScript(BuckminsterInstallation.java:319)
	at hudson.plugins.buckminster.BuckminsterInstallation$BuckminsterInstaller.performInstallation(BuckminsterInstallation.java:218)
	at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61)
	at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:99)
	at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:149)
	at hudson.plugins.buckminster.BuckminsterInstallation.forNode(BuckminsterInstallation.java:84)
	at hudson.plugins.buckminster.EclipseBuckminsterBuilder.perform(EclipseBuckminsterBuilder.java:163)
	... 9 more

Re: Buckminster does not materialize the source for all plugins [message #724765 is a reply to message #724686] Tue, 13 September 2011 06:07 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2011-09-12 22:06, Lothar Werzinger wrote:
> Thomas Hallgren wrote on Mon, 12 September 2011 05:19
>> Hi Lothar,
>>
>> I found the cause of this problem and fixed it. You should get rid of the problem if you update to the most recent
>> Buckminster. More info here:
>>
>> Bug 357060 - Generated conflicting source dependencies are sometimes left out
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=357060
>>
>> Regards,
>> Thomas Hallgren
>
>
> That's great news. Will there be a new release?

This fix has already been pushed to our update sites. So as I wrote earlier, you should get rid of the problem by just
updating to the most recent Buckminster.

- thomas
Re: Buckminster does not materialize the source for all plugins [message #724767 is a reply to message #724747] Tue, 13 September 2011 06:10 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2011-09-13 06:30, Lothar Werzinger wrote:
> What is the trick to build and create p2 sites that work like the default http://download.eclipse.org/tools/buckminster/headless-3.6 and don't produce errors on install?
>
Use Buckminster-3.7 at all times.

- thomas
Re: Buckminster does not materialize the source for all plugins [message #724771 is a reply to message #724767] Tue, 13 September 2011 06:40 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Thomas Hallgren wrote on Mon, 12 September 2011 23:10
On 2011-09-13 06:30, Lothar Werzinger wrote:
> What is the trick to build and create p2 sites that work like the default http://download.eclipse.org/tools/buckminster/headless-3.6 and don't produce errors on install?
>
Use Buckminster-3.7 at all times.

- thomas


The hudson buckminster plugin only supports 3.5 and 3.6. That and the latest fix you made were why I decided to build it myself, but as outlined I had problems with the created p2 sites.
Re: Buckminster does not materialize the source for all plugins [message #724795 is a reply to message #724771] Tue, 13 September 2011 07:32 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2011-09-13 08:40, Lothar Werzinger wrote:
> Thomas Hallgren wrote on Mon, 12 September 2011 23:10
>> On 2011-09-13 06:30, Lothar Werzinger wrote:
>> > What is the trick to build and create p2 sites that work like the default
>> http://download.eclipse.org/tools/buckminster/headless-3.6 and don't produce errors on install?
>> >
>> Use Buckminster-3.7 at all times.
>>
>> - thomas
>
>
> The hudson buckminster plugin only supports 3.5 and 3.6. That and the latest fix you made were why I decided to build it
> myself, but as outlined I had problems with the created p2 sites.

That's not true. We use both Jenkins and Hudson with Buckminster 3.7.

- thomas
Re: Buckminster does not materialize the source for all plugins [message #724924 is a reply to message #724795] Tue, 13 September 2011 14:02 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Thomas Hallgren wrote on Tue, 13 September 2011 00:32
On 2011-09-13 08:40, Lothar Werzinger wrote:
> Thomas Hallgren wrote on Mon, 12 September 2011 23:10
>> On 2011-09-13 06:30, Lothar Werzinger wrote:
>> > What is the trick to build and create p2 sites that work like the default
>> http://download.eclipse.org/tools/buckminster/headless-3.6 and don't produce errors on install?
>> >
>> Use Buckminster-3.7 at all times.
>>
>> - thomas
>
>
> The hudson buckminster plugin only supports 3.5 and 3.6. That and the latest fix you made were why I decided to build it
> myself, but as outlined I had problems with the created p2 sites.

That's not true. We use both Jenkins and Hudson with Buckminster 3.7.

- thomas


Maybe (*), but that's not my problem here, as the released 3.7 won't have your fix int it, and the eclipse automated build seems not to produce any consumable p2 sites.

What I need is either a p2 site from the eclipse automated build from GIT where I can install from (to get the latest fix) or some advice how to build buckminster myself in a way that it will be installable without error. That's what I asked for in my previous post.


*)
The hudson plugin currently has only options to install 3.5 and 3.6 and the author has confirmed that in an email. In order to install my built version I had to hand edit some JSON file (was attached in a previous post). I assume I could do a similar edit for 3.7, but that would still not get the the fix I am eager to test.
Re: Buckminster does not materialize the source for all plugins [message #724930 is a reply to message #724924] Tue, 13 September 2011 14:11 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2011-09-13 16:02, Lothar Werzinger wrote:

> Maybe (*), but that's not my problem here, as the released 3.7 won't have your
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=357060 int it

Yes it has.

- thomas
Re: Buckminster does not materialize the source for all plugins [message #724939 is a reply to message #724930] Tue, 13 September 2011 14:44 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Thomas Hallgren wrote on Tue, 13 September 2011 07:11
On 2011-09-13 16:02, Lothar Werzinger wrote:

> Maybe (*), but that's not my problem here, as the released 3.7 won't have your
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=357060 int it

Yes it has.

- thomas


Oh, I was not aware of that. I was under the impression that it contains a stable release that does not change that frequently. I will try it.
Btw. does http://download.eclipse.org/tools/buckminster/headless-3.7
contains always the latest from git or just selected backported fixes?

It would still be nice to know why the built buckminster from git did not install, though.
Re: Buckminster does not materialize the source for all plugins [message #724952 is a reply to message #724939] Tue, 13 September 2011 15:03 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2011-09-13 16:44, Lothar Werzinger wrote:
> Thomas Hallgren wrote on Tue, 13 September 2011 07:11
>> On 2011-09-13 16:02, Lothar Werzinger wrote:
>>
>> > Maybe (*), but that's not my problem here, as the released 3.7 won't have your
>> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=357060 int it
>>
>> Yes it has.
>>
>> - thomas
>
>
> Oh, I was not aware of that. I was under the impression that it contains a stable release that does not change that
> frequently. I will try it.
> Btw. does http://download.eclipse.org/tools/buckminster/headless-3.7
> contains always the latest from git or just selected backported fixes?
>
> It would still be nice to know why the built buckminster from git did not install, though.
>
Hard to say. One difference against our own build is that you never built the workspace properly. We use the command
sequence:
import
build
perform

Also, the build.properties from the org.eclipse.buckminster.releng project should be fed to each build step with the -P
option. You can look at the 'promote.bmscript' file in the releng project as a reference.

- thomas
Re: Buckminster does not materialize the source for all plugins [message #724959 is a reply to message #724952] Tue, 13 September 2011 15:24 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Thomas Hallgren wrote on Tue, 13 September 2011 08:03
On 2011-09-13 16:44, Lothar Werzinger wrote:
> It would still be nice to know why the built buckminster from git did not install, though.
>
Hard to say. One difference against our own build is that you never built the workspace properly. We use the command
sequence:
import
build
perform

Also, the build.properties from the org.eclipse.buckminster.releng project should be fed to each build step with the -P
option. You can look at the 'promote.bmscript' file in the releng project as a reference.

- thomas


Thanks, I'll try.

Maybe it would be helpful if you could publish a working hudson config.xml that builds p2 site(s) on the wiki for those who want or need to build themselves.
Re: Buckminster does not materialize the source for all plugins [message #724987 is a reply to message #724765] Tue, 13 September 2011 16:54 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Thomas Hallgren wrote on Mon, 12 September 2011 23:07
On 2011-09-12 22:06, Lothar Werzinger wrote:
> Thomas Hallgren wrote on Mon, 12 September 2011 05:19
>> Hi Lothar,
>>
>> I found the cause of this problem and fixed it. You should get rid of the problem if you update to the most recent
>> Buckminster. More info here:
>>
>> Bug 357060 - Generated conflicting source dependencies are sometimes left out
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=357060
>>
>> Regards,
>> Thomas Hallgren
>
>
> That's great news. Will there be a new release?

This fix has already been pushed to our update sites. So as I wrote earlier, you should get rid of the problem by just
updating to the most recent Buckminster.

- thomas


I just tried with http://download.eclipse.org/tools/buckminster/headless-3.7, but I still don't get org.apache.commons.logging.source 1.1.1 in my TP.
No component named org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721] is known to Buckminster

Full console log attached.
Re: Buckminster does not materialize the source for all plugins [message #724995 is a reply to message #724987] Tue, 13 September 2011 17:23 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2011-09-13 18:54, Lothar Werzinger wrote:
> I just tried with http://download.eclipse.org/tools/buckminster/headless-3.7, but I still don't get org.apache.commons.logging.source 1.1.1 in my TP.
>
> No component named org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721] is known to Buckminster
>
> Full console log attached.

That's probably because you don't have the orbit update site enabled in your rmap. That's the only place where that
source can be found.

- thomas
Re: Buckminster does not materialize the source for all plugins [message #725002 is a reply to message #724995] Tue, 13 September 2011 17:51 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Thomas Hallgren wrote on Tue, 13 September 2011 10:23
On 2011-09-13 18:54, Lothar Werzinger wrote:
> I just tried with http://download.eclipse.org/tools/buckminster/headless-3.7, but I still don't get org.apache.commons.logging.source 1.1.1 in my TP.
>
> No component named org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721] is known to Buckminster
>
> Full console log attached.

That's probably because you don't have the orbit update site enabled in your rmap. That's the only place where that
source can be found.

- thomas


Ahh, strange the 1.0.4 source bundle is available, as is the 1.1.1 binary bundle.
I'll try to add orbit and see how that goes.
Re: Buckminster does not materialize the source for all plugins [message #725061 is a reply to message #725002] Tue, 13 September 2011 20:23 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
This whole thing seems to become the never ending story Sad

I added the orbit repository but I still get the
No component named org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721] is known to Buckminster

error.

I also wonder if the Artifact repository out of sync messages are harmful and why they get generated.
Artifact repository out of sync. Overwriting /var/lib/hudson/jobs/test/workspace/bm-workspace/tp-full/plugins/org.h2.source_1.1.117.v201105142352.jar
Artifact repository out of sync. Overwriting /var/lib/hudson/jobs/test/workspace/bm-workspace/tp-full/plugins/org.apache.derby.source_10.5.1.1_201105231903.jar
Artifact repository out of sync. Overwriting /var/lib/hudson/jobs/test/workspace/bm-workspace/tp-full/plugins/org.eclipse.emf.cdo.server.net4j.source_4.0.0.v20110528-1118.jar
Artifact repository out of sync. Overwriting /var/lib/hudson/jobs/test/workspace/bm-workspace/tp-full/plugins/org.eclipse.team.cvs.ui.source_3.3.400.I20110510-0800.jar
Artifact repository out of sync. Overwriting /var/lib/hudson/jobs/test/workspace/bm-workspace/tp-full/plugins/org.eclipse.equinox.supplement.source_1.4.0.v20110502.jar
Artifact repository out of sync. Overwriting /var/lib/hudson/jobs/test/workspace/bm-workspace/tp-full/plugins/org.eclipse.equinox.transforms.hook.source_1.0.300.v20100719.jar
Artifact repository out of sync. Overwriting /var/lib/hudson/jobs/test/workspace/bm-workspace/tp-full/plugins/org.eclipse.equinox.p2.installer.source_1.0.300.v20110502-1955.jar
Artifact repository out of sync. Overwriting /var/lib/hudson/jobs/test/workspace/bm-workspace/tp-full/plugins/org.eclipse.equinox.useradmin.source_1.1.300.v20110413.jar
Artifact repository out of sync. Overwriting /var/lib/hudson/jobs/test/workspace/bm-workspace/tp-full/plugins/org.eclipse.rap.ui.cheatsheets.source_1.4.0.20110614-2335.jar
Artifact repository out of sync. Overwriting /var/lib/hudson/jobs/test/workspace/bm-workspace/tp-full/plugins/org.eclipse.emf.rap.edit.ui.source_2.7.0.v20110606-0949.jar
Artifact repository out of sync. Overwriting /var/lib/hudson/jobs/test/workspace/bm-workspace/tp-full/plugins/org.eclipse.ocl.source_3.1.0.v20110606-1427.jar


Full console log is attached.
Re: Buckminster does not materialize the source for all plugins [message #725069 is a reply to message #725061] Tue, 13 September 2011 20:46 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2011-09-13 22:23, Lothar Werzinger wrote:
> This whole thing seems to become the never ending story :(
>
> I added the http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/ but I still get the
>
> No component named org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721] is known to Buckminster
>
That's very odd. I just tried your cquery/rmap with orbit enabled, and I get that source included.


> I also wonder if the Artifact repository out of sync messages are harmful and why they get generated.
>
They generally mean that the artifacts.xml lacks some jars that apparently are present. This typically happens when a
materialization is interrupted. The cure is to simply clear the TP completely and start over.

- thomas
Re: Buckminster does not materialize the source for all plugins [message #725083 is a reply to message #725069] Tue, 13 September 2011 21:51 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Thomas Hallgren wrote on Tue, 13 September 2011 13:46

On 2011-09-13 22:23, Lothar Werzinger wrote:
> This whole thing seems to become the never ending story Sad
>
> I added the http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/ but I still get the
>
> No component named org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721] is known to Buckminster
>
That's very odd. I just tried your cquery/rmap with orbit enabled, and I get that source included.


Hmm, not here:
org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721](&(buckminster.download.source=true)(!(eclipse.p2.optional=false))): Rejecting provider p2(http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/?importType=binary[http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/?importType=binary]): No component match was found
org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721](&(buckminster.download.source=true)(!(eclipse.p2.optional=false))): No provider was found that could resolve the request


What Orbit update site are you using? Could you attach the rmap you are using?

Thomas Hallgren wrote on Tue, 13 September 2011 13:46

> I also wonder if the Artifact repository out of sync messages are harmful and why they get generated.
>
They generally mean that the artifacts.xml lacks some jars that apparently are present. This typically happens when a
materialization is interrupted. The cure is to simply clear the TP completely and start over.

- thomas


Strange, my build always starts with an empty TP
WARN:  Target platform directory 'bm-workspace/tp-full/' does not exist and will be created
Re: Buckminster does not materialize the source for all plugins [message #725158 is a reply to message #725083] Wed, 14 September 2011 05:57 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
Your repository URL is incorrect. Try using:

http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/repository/

You can remove the ?importType=binary part. That's an old relic for the now deprectated 'eclipse.import' reader type. It
has no meaning for the 'p2' reader.

- thomas


On 2011-09-13 23:51, Lothar Werzinger wrote:
> Thomas Hallgren wrote on Tue, 13 September 2011 13:46
>> On 2011-09-13 22:23, Lothar Werzinger wrote:
>> > This whole thing seems to become the never ending story :(
>> >
>> > I added the http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/ but I still get the
>> >
>> > No component named org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721] is known
>> to Buckminster
>> >
>> That's very odd. I just tried your cquery/rmap with orbit enabled, and I get that source included.
>
>
> Hmm, not here:
>
> org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721](&(buckminster.download.source=true)(!(eclipse.p2.optional=false))):
> Rejecting provider
> p2(http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/?importType=binary[http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/?importType=binary]):
> No component match was found
> org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721](&(buckminster.download.source=true)(!(eclipse.p2.optional=false))):
> No provider was found that could resolve the request
>
>
> What Orbit update site are you using? Could you attach the rmap you are using?
>
> Thomas Hallgren wrote on Tue, 13 September 2011 13:46
>> > I also wonder if the Artifact repository out of sync messages are harmful and why they get generated.
>> >
>> They generally mean that the artifacts.xml lacks some jars that apparently are present. This typically happens when a
>> materialization is interrupted. The cure is to simply clear the TP completely and start over.
>>
>> - thomas
>
>
> Strange, my build always starts with an empty TP
> WARN: Target platform directory 'bm-workspace/tp-full/' does not exist and will be created
Re: Buckminster does not materialize the source for all plugins [message #725406 is a reply to message #725158] Wed, 14 September 2011 17:20 Go to previous messageGo to next message
Lothar Werzinger is currently offline Lothar Werzinger
Messages: 153
Registered: July 2009
Location: Bay Area
Senior Member
Thomas Hallgren wrote on Tue, 13 September 2011 22:57
Your repository URL is incorrect. Try using:

http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/repository/

You can remove the ?importType=binary part. That's an old relic for the now deprectated 'eclipse.import' reader type. It
has no meaning for the 'p2' reader.

- thomas


Thanks, that got me going. The p2 site now gets created (and by visual inspection looks complete - I will do a more thorough check) but the job still fails

INFO:  perform 'biz.tradescape.mmt.targetplatform#site.p2'
INFO:  [start org.eclipse.rcp:eclipse.feature$3.7.0.v20110216-9DB5Fm1FpBGy_AaVz-mFamgY#feature.jar]
INFO:  [end org.eclipse.rcp:eclipse.feature$3.7.0.v20110216-9DB5Fm1FpBGy_AaVz-mFamgY#feature.jar]

...

INFO:  [start biz.tradescape.mmt.targetplatform:eclipse.feature$1.0.0.qualifier#site.p2]
CSpec org.junit:osgi.bundle$3.8.2.v3_8_2_v20100427-1100 has no  action, group, or local artifact named bundle.jars



Any ideas why that error occurs?
Is my assumption that I can (successfully) call #site.p2 on the same feature I queried for right before to materialize is too naive and not valid?


Edit:
I did a more thorough check:
Although the site seems to contain the features and plugins, the metadata is not correct and thus the site is unusable.

[Updated on: Wed, 14 September 2011 18:32]

Report message to a moderator

Re: Buckminster does not materialize the source for all plugins [message #727079 is a reply to message #725406] Tue, 20 September 2011 11:22 Go to previous message
Matthew Webber is currently offline Matthew Webber
Messages: 198
Registered: December 2010
Senior Member
>> CSpec org.junit:osgi.bundle$3.8.2.v3_8_2_v20100427-1100 has no action, group, or local artifact named bundle.jars
>> Any ideas why that error occurs?

There is an earlier thread in this forum on exactly that issue. See http://www.eclipse.org/forums/index.php/t/198120/

There is an open bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=353438

Hope that helps
Matthew
Previous Topic:[solved] Change site.p2 output path
Next Topic:Additional p2 repositoriy managing actors
Goto Forum:
  


Current Time: Sat Oct 25 23:46:14 GMT 2014

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

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