Home » Archived » Buckminster » Materializing multiple versions of a plugin
|
| Re: Materializing multiple versions of a plugin [message #375826 is a reply to message #375822] |
Fri, 02 May 2008 06:57   |
|
Hi Oisin,
this is an unwanted limitation in Buckminster. Perhaps its OK to report
a conflict as a default behavior but it should be configurable. Can you
please enter an enhancement request for this in our bugzilla?
Regards,
Thomas Hallgren
Oisin Hurley wrote:
> In the Eclipse STP build, I need to materialize two versions of the javax.wsdl
> plugin from Orbit - 1.5.1 for STP and 1.4.0 for parts of WTP upon which STP
> depends.
>
> Watching the build log, I see:
>
> javax.wsdl:osgi.bundle/[1.5.0,1.6.0)#OSGi: Found match
> 1.5.1.v200803061910
>
> a little later I see
>
> [java] WARN: Component request javax.wsdl:osgi.bundle/[1.5.0,1.6.0)#OSGi is
> inconflict with request javax.wsdl:osgi.bundle/[1.4.0,1.5.0)#OSGi
>
> and finally, I get compilation failures in the STP code that
> uses javax.wsdl.
>
> When I check the workspace/plugins, I see an exploded javax.wsdl
> directory, which contains the 1.4.0 jar only.
>
> I'm using the eclipse.import reader to pull the orbit bundles map
> file.
>
> How can I materialize both of these bundles and complete the
> build?
>
> best regards
> Oisin
>
|
|
| |
| Re: Materializing multiple versions of a plugin [message #375829 is a reply to message #375826] |
Fri, 02 May 2008 12:48 |
 Filip Hrbek
Messages: 233
Registered: July 2009 |
Senior Member |
|
|
Hi Thomas and Oisin,
I have similar problem, but the difference is that Buckminster does
materialization of two different versions of the same component for me.
I can see a warning in the log, however both versions are visible in the
bom tree and both are materialized:
Component request junit/[3.8.1,3.9.0.a)#Triplet is inconflict with
request junit/[3.7,3.8.0.a)#Triplet
The components are of type 'maven'.
How to test it: Try to resolve & materialize this cquery (a small RCP
demo application built by buckminster):
http://eclipsesvn.cloudsmith.com/com.cloudsmith.demo/trunk/c om.cloudsmith.presentation2.feature/buckminster/com.cloudsmi th.presentation2.feature.cquery
I got another problem when I wanted to skip the 'junit' completely. I
added an advisor node telling buckminster to skip the component. The bom
looked ok. However, materialization fails on this:
Component commons-httpclient$3.0.1#Triplet has no declared dependency to
component junit
Am I doing anything wrong? If not, should I post these as separate issues?
Thanks,
Filip
Thomas Hallgren napsal(a):
> Hi Oisin,
> this is an unwanted limitation in Buckminster. Perhaps its OK to report
> a conflict as a default behavior but it should be configurable. Can you
> please enter an enhancement request for this in our bugzilla?
>
> Regards,
> Thomas Hallgren
>
> Oisin Hurley wrote:
>> In the Eclipse STP build, I need to materialize two versions of the
>> javax.wsdl
>> plugin from Orbit - 1.5.1 for STP and 1.4.0 for parts of WTP upon
>> which STP
>> depends.
>>
>> Watching the build log, I see:
>>
>> javax.wsdl:osgi.bundle/[1.5.0,1.6.0)#OSGi: Found match
>> 1.5.1.v200803061910
>>
>> a little later I see
>>
>> [java] WARN: Component request
>> javax.wsdl:osgi.bundle/[1.5.0,1.6.0)#OSGi is
>> inconflict with request javax.wsdl:osgi.bundle/[1.4.0,1.5.0)#OSGi
>>
>> and finally, I get compilation failures in the STP code that
>> uses javax.wsdl.
>>
>> When I check the workspace/plugins, I see an exploded javax.wsdl
>> directory, which contains the 1.4.0 jar only.
>>
>> I'm using the eclipse.import reader to pull the orbit bundles map
>> file.
>>
>> How can I materialize both of these bundles and complete the
>> build?
>>
>> best regards
>> Oisin
>>
|
|
|
| Re: Materializing multiple versions of a plugin [message #375830 is a reply to message #375829] |
Fri, 02 May 2008 17:01 |
|
Hi Filip,
Please add the information regarding multiple versions to the bugzilla
that Oising entered. The skipping junit thing sounds like another issue
so it deserves a separate bugzilla entry.
Regards,
Thomas Hallgren
Filip Hrbek wrote:
> Hi Thomas and Oisin,
>
> I have similar problem, but the difference is that Buckminster does
> materialization of two different versions of the same component for me.
> I can see a warning in the log, however both versions are visible in the
> bom tree and both are materialized:
>
> Component request junit/[3.8.1,3.9.0.a)#Triplet is inconflict with
> request junit/[3.7,3.8.0.a)#Triplet
>
> The components are of type 'maven'.
>
> How to test it: Try to resolve & materialize this cquery (a small RCP
> demo application built by buckminster):
>
> http://eclipsesvn.cloudsmith.com/com.cloudsmith.demo/trunk/c om.cloudsmith.presentation2.feature/buckminster/com.cloudsmi th.presentation2.feature.cquery
>
>
>
> I got another problem when I wanted to skip the 'junit' completely. I
> added an advisor node telling buckminster to skip the component. The bom
> looked ok. However, materialization fails on this:
>
> Component commons-httpclient$3.0.1#Triplet has no declared dependency to
> component junit
>
> Am I doing anything wrong? If not, should I post these as separate issues?
>
> Thanks,
> Filip
>
>
>
> Thomas Hallgren napsal(a):
>> Hi Oisin,
>> this is an unwanted limitation in Buckminster. Perhaps its OK to
>> report a conflict as a default behavior but it should be configurable.
>> Can you please enter an enhancement request for this in our bugzilla?
>>
>> Regards,
>> Thomas Hallgren
>>
>> Oisin Hurley wrote:
>>> In the Eclipse STP build, I need to materialize two versions of the
>>> javax.wsdl
>>> plugin from Orbit - 1.5.1 for STP and 1.4.0 for parts of WTP upon
>>> which STP
>>> depends.
>>>
>>> Watching the build log, I see:
>>>
>>> javax.wsdl:osgi.bundle/[1.5.0,1.6.0)#OSGi: Found match
>>> 1.5.1.v200803061910
>>>
>>> a little later I see
>>>
>>> [java] WARN: Component request
>>> javax.wsdl:osgi.bundle/[1.5.0,1.6.0)#OSGi is
>>> inconflict with request javax.wsdl:osgi.bundle/[1.4.0,1.5.0)#OSGi
>>>
>>> and finally, I get compilation failures in the STP code that
>>> uses javax.wsdl.
>>>
>>> When I check the workspace/plugins, I see an exploded javax.wsdl
>>> directory, which contains the 1.4.0 jar only.
>>>
>>> I'm using the eclipse.import reader to pull the orbit bundles map
>>> file.
>>>
>>> How can I materialize both of these bundles and complete the
>>> build?
>>>
>>> best regards
>>> Oisin
>>>
|
|
|
Goto Forum:
Current Time: Thu Apr 25 10:39:38 GMT 2024
Powered by FUDForum. Page generated in 0.03076 seconds |
] 
Search
Help
Register
Login
Home
