|
Re: p2 materializer and buckminster components [message #494717 is a reply to message #494715] |
Mon, 02 November 2009 11:00 |
|
Hi Peter,
Do you have a p2 repository in your CVS? Or do you expect to find a jar there?
Regards,
Thomas Hallgren
On 11/02/2009 11:26 AM, Peter Kullmann wrote:
> Hi,
>
> I'm trying to materialize a target platform which is defined by a
> buckminster component called "target.swt". When trying to materialize in
> the wizard I'm getting the following error: An internal error occurred
> during: "p2 materializer".
>
>
> java.lang.IllegalArgumentException
> at java.net.URI.create(URI.java:842)
> at
> org.eclipse.buckminster.core.materializer.P2Materializer.mat erialize(P2Materializer.java:214)
>
> at
> org.eclipse.buckminster.core.materializer.MaterializerJob.ru n(MaterializerJob.java:70)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.net.URISyntaxException: Expected scheme name at index 0:
> :extssh:www.arenae.ch:/var/cvsroot,ch.arenae.releng/buckmins ter/target.swt
> at java.net.URI$Parser.fail(URI.java:2809)
> at java.net.URI$Parser.failExpecting(URI.java:2815)
> at java.net.URI$Parser.parse(URI.java:3007)
> at java.net.URI.<init>(URI.java:578)
> at java.net.URI.create(URI.java:840)
> ... 3 more
>
> It's pretty clear that p2 tries to get the buckminster component that
> defines my target from CVS. The relevant section from our map file is:
>
> <searchPath name="arenae-buckminster">
> <provider readerType="cvs" componentTypes="buckminster" mutable="false"
> source="false">
> <uri
> format=" :extssh:www.arenae.ch:/var/cvsroot,ch.arenae.releng/buckmins ter/{0} ">
>
> <bc:propertyRef key="buckminster.component" />
> </uri>
> </provider>
> </searchPath>
>
>
> Is there a workaround for this? I don't want to materialize "target.swt"
> itself, only the dependencies should be materialized.
>
> It works well if I have the "target.swt" buckminster component in the
> workspace.
>
>
> Thanks
> Peter
|
|
|
Re: p2 materializer and buckminster components [message #494725 is a reply to message #494717] |
Mon, 02 November 2009 11:36 |
Peter Kullmann Messages: 240 Registered: July 2009 |
Senior Member |
|
|
Hi Thomas,
There is no p2 repo in the CVS, it's just the source for the buckminster
component, ie a single file "buckminster.cspec". Buckminster can read it
and resolve its dependencies without problems.
Regards
Peter
Thomas Hallgren schrieb:
> Hi Peter,
> Do you have a p2 repository in your CVS? Or do you expect to find a jar
> there?
>
> Regards,
> Thomas Hallgren
>
>
> On 11/02/2009 11:26 AM, Peter Kullmann wrote:
>> Hi,
>>
>> I'm trying to materialize a target platform which is defined by a
>> buckminster component called "target.swt". When trying to materialize in
>> the wizard I'm getting the following error: An internal error occurred
>> during: "p2 materializer".
>>
>>
>> java.lang.IllegalArgumentException
>> at java.net.URI.create(URI.java:842)
>> at
>> org.eclipse.buckminster.core.materializer.P2Materializer.mat erialize(P2Materializer.java:214)
>>
>>
>> at
>> org.eclipse.buckminster.core.materializer.MaterializerJob.ru n(MaterializerJob.java:70)
>>
>>
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>> Caused by: java.net.URISyntaxException: Expected scheme name at index 0:
>> :extssh:www.arenae.ch:/var/cvsroot,ch.arenae.releng/buckmins ter/target.swt
>>
>> at java.net.URI$Parser.fail(URI.java:2809)
>> at java.net.URI$Parser.failExpecting(URI.java:2815)
>> at java.net.URI$Parser.parse(URI.java:3007)
>> at java.net.URI.<init>(URI.java:578)
>> at java.net.URI.create(URI.java:840)
>> ... 3 more
>>
>> It's pretty clear that p2 tries to get the buckminster component that
>> defines my target from CVS. The relevant section from our map file is:
>>
>> <searchPath name="arenae-buckminster">
>> <provider readerType="cvs" componentTypes="buckminster" mutable="false"
>> source="false">
>> <uri
>> format=" :extssh:www.arenae.ch:/var/cvsroot,ch.arenae.releng/buckmins ter/{0} ">
>>
>>
>> <bc:propertyRef key="buckminster.component" />
>> </uri>
>> </provider>
>> </searchPath>
>>
>>
>> Is there a workaround for this? I don't want to materialize "target.swt"
>> itself, only the dependencies should be materialized.
>>
>> It works well if I have the "target.swt" buckminster component in the
>> workspace.
>>
>>
>> Thanks
>> Peter
>
|
|
|
Re: p2 materializer and buckminster components [message #494730 is a reply to message #494725] |
Mon, 02 November 2009 12:04 |
|
Hi Peter,
OK. But a source directory is not something that you can put into your target platform. I suggest
that you add an node to your mspec that matches the top component (i.e. your buckminster.cspec)
exactly and either direct it to the workspace or simply skip the materialization of it (everything
it depends on will still be materialized).
Regards,
Thomas Hallgren
Peter Kullmann wrote:
> Hi Thomas,
>
> There is no p2 repo in the CVS, it's just the source for the buckminster
> component, ie a single file "buckminster.cspec". Buckminster can read it
> and resolve its dependencies without problems.
>
> Regards
> Peter
>
> Thomas Hallgren schrieb:
>> Hi Peter,
>> Do you have a p2 repository in your CVS? Or do you expect to find a
>> jar there?
>>
>> Regards,
>> Thomas Hallgren
>>
>>
>> On 11/02/2009 11:26 AM, Peter Kullmann wrote:
>>> Hi,
>>>
>>> I'm trying to materialize a target platform which is defined by a
>>> buckminster component called "target.swt". When trying to materialize in
>>> the wizard I'm getting the following error: An internal error occurred
>>> during: "p2 materializer".
>>>
>>>
>>> java.lang.IllegalArgumentException
>>> at java.net.URI.create(URI.java:842)
>>> at
>>> org.eclipse.buckminster.core.materializer.P2Materializer.mat erialize(P2Materializer.java:214)
>>>
>>>
>>> at
>>> org.eclipse.buckminster.core.materializer.MaterializerJob.ru n(MaterializerJob.java:70)
>>>
>>>
>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>> Caused by: java.net.URISyntaxException: Expected scheme name at index 0:
>>> :extssh:www.arenae.ch:/var/cvsroot,ch.arenae.releng/buckmins ter/target.swt
>>>
>>> at java.net.URI$Parser.fail(URI.java:2809)
>>> at java.net.URI$Parser.failExpecting(URI.java:2815)
>>> at java.net.URI$Parser.parse(URI.java:3007)
>>> at java.net.URI.<init>(URI.java:578)
>>> at java.net.URI.create(URI.java:840)
>>> ... 3 more
>>>
>>> It's pretty clear that p2 tries to get the buckminster component that
>>> defines my target from CVS. The relevant section from our map file is:
>>>
>>> <searchPath name="arenae-buckminster">
>>> <provider readerType="cvs" componentTypes="buckminster" mutable="false"
>>> source="false">
>>> <uri
>>> format=" :extssh:www.arenae.ch:/var/cvsroot,ch.arenae.releng/buckmins ter/{0} ">
>>>
>>>
>>> <bc:propertyRef key="buckminster.component" />
>>> </uri>
>>> </provider>
>>> </searchPath>
>>>
>>>
>>> Is there a workaround for this? I don't want to materialize "target.swt"
>>> itself, only the dependencies should be materialized.
>>>
>>> It works well if I have the "target.swt" buckminster component in the
>>> workspace.
>>>
>>>
>>> Thanks
>>> Peter
>>
|
|
|
Re: p2 materializer and buckminster components [message #494890 is a reply to message #494730] |
Tue, 03 November 2009 06:27 |
Peter Kullmann Messages: 240 Registered: July 2009 |
Senior Member |
|
|
Thanks Thomas, this worked very well.
Peter
Thomas Hallgren schrieb:
> Hi Peter,
> OK. But a source directory is not something that you can put into your
> target platform. I suggest that you add an node to your mspec that
> matches the top component (i.e. your buckminster.cspec) exactly and
> either direct it to the workspace or simply skip the materialization of
> it (everything it depends on will still be materialized).
>
> Regards,
> Thomas Hallgren
>
>
>
> Peter Kullmann wrote:
>> Hi Thomas,
>>
>> There is no p2 repo in the CVS, it's just the source for the
>> buckminster component, ie a single file "buckminster.cspec".
>> Buckminster can read it and resolve its dependencies without problems.
>>
>> Regards
>> Peter
>>
>> Thomas Hallgren schrieb:
>>> Hi Peter,
>>> Do you have a p2 repository in your CVS? Or do you expect to find a
>>> jar there?
>>>
>>> Regards,
>>> Thomas Hallgren
>>>
>>>
>>> On 11/02/2009 11:26 AM, Peter Kullmann wrote:
>>>> Hi,
>>>>
>>>> I'm trying to materialize a target platform which is defined by a
>>>> buckminster component called "target.swt". When trying to
>>>> materialize in
>>>> the wizard I'm getting the following error: An internal error occurred
>>>> during: "p2 materializer".
>>>>
>>>>
>>>> java.lang.IllegalArgumentException
>>>> at java.net.URI.create(URI.java:842)
>>>> at
>>>> org.eclipse.buckminster.core.materializer.P2Materializer.mat erialize(P2Materializer.java:214)
>>>>
>>>>
>>>> at
>>>> org.eclipse.buckminster.core.materializer.MaterializerJob.ru n(MaterializerJob.java:70)
>>>>
>>>>
>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>>> Caused by: java.net.URISyntaxException: Expected scheme name at
>>>> index 0:
>>>> :extssh:www.arenae.ch:/var/cvsroot,ch.arenae.releng/buckmins ter/target.swt
>>>>
>>>> at java.net.URI$Parser.fail(URI.java:2809)
>>>> at java.net.URI$Parser.failExpecting(URI.java:2815)
>>>> at java.net.URI$Parser.parse(URI.java:3007)
>>>> at java.net.URI.<init>(URI.java:578)
>>>> at java.net.URI.create(URI.java:840)
>>>> ... 3 more
>>>>
>>>> It's pretty clear that p2 tries to get the buckminster component that
>>>> defines my target from CVS. The relevant section from our map file is:
>>>>
>>>> <searchPath name="arenae-buckminster">
>>>> <provider readerType="cvs" componentTypes="buckminster" mutable="false"
>>>> source="false">
>>>> <uri
>>>> format=" :extssh:www.arenae.ch:/var/cvsroot,ch.arenae.releng/buckmins ter/{0} ">
>>>>
>>>>
>>>> <bc:propertyRef key="buckminster.component" />
>>>> </uri>
>>>> </provider>
>>>> </searchPath>
>>>>
>>>>
>>>> Is there a workaround for this? I don't want to materialize
>>>> "target.swt"
>>>> itself, only the dependencies should be materialized.
>>>>
>>>> It works well if I have the "target.swt" buckminster component in the
>>>> workspace.
>>>>
>>>>
>>>> Thanks
>>>> Peter
>>>
|
|
|
Powered by
FUDForum. Page generated in 7.58132 seconds