|
| Re: Question on Site Creation and Targets [message #385502 is a reply to message #385481] |
Mon, 25 May 2009 06:39   |
|
Chase wrote:
> Hello - I just started using buckminster and it has been relatively easy
> to get working so far. The one issue I have is related to why the
> plugins from the target platform are not stored in the resultant p2
> site. As an example, the org.springframework.context bundle is in my
> target platform. I execute buckminster site.p2 action from a feature
> project and the result is that the only action taken on this target
> platform bundle is:
> org.springframework.context:osgi.bundle$2.5.6.A#OSGi#target. fragments
>
> When I check the update site the bundle is not extracted to the plugins
> directory as an artifact. Is there a simple way to create either a
> seperate update site for a given target definition or to cause p2 to
> copy the plugins as artifacts into the update site?
>
It really should do that by default. Are you sure you look in the right place? I.e. the ${buckminster.output.root}<build
result for your project>/site.p2/plugins folder?
Does the feature include the plugin or list it as required?
Regards,
Thomas Hallgren
|
|
|
| Re: Question on Site Creation and Targets [message #385519 is a reply to message #385502] |
Thu, 28 May 2009 07:52 |
|
Hi Alex,
Could your problem be related to this?
Regards,
Thomas Hallgren
Chase Wolfinger wrote:
> `Hello Thomas - I figured out the issue - not sure if it is a bug.
> The issue is that the names of the jars in my target did not match
> the name expected by buckminster. The pattern set used by buckminster
> is with patternSet{ includes: [org.ops4j.pax.configmanager_0.2.2.jar]
> whereas the jar I downloaded from the ops4j.pax site is
> named pax-confman-propsloader-0.2.2.jar, So I am not sure if this
> is a bug or more of naming standard that needs to documented when
> using non eclipse bundles. It seems like the naming standard vary a
> bit
> (see http://www.springsource.com/repository/app/bundle/version/de tail?name=org.springframework.osgi.core&version=1.1.1.A
> < http://www.springsource.com/repository/app/bundle/version/de tail?name=org.springframework.osgi.core&version=1.1.1.A>)
>
>
> CHase
>
> On Mon, May 25, 2009 at 12:39 AM, Thomas Hallgren <thomas@tada.se
> <mailto:thomas@tada.se>> wrote:
>
> Chase wrote:
>
> Hello - I just started using buckminster and it has been
> relatively easy to get working so far. The one issue I have
> is related to why the plugins from the target platform are not
> stored in the resultant p2 site. As an example, the
> org.springframework.context bundle is in my target platform.
> I execute buckminster site.p2 action from a feature project
> and the result is that the only action taken on this target
> platform bundle is:
> org.springframework.context:osgi.bundle$2.5.6.A#OSGi#target. fragments
>
> When I check the update site the bundle is not extracted to
> the plugins directory as an artifact. Is there a simple way
> to create either a seperate update site for a given target
> definition or to cause p2 to copy the plugins as artifacts
> into the update site?
>
> It really should do that by default. Are you sure you look in the
> right place? I.e. the ${buckminster.output.root}<build result for
> your project>/site.p2/plugins folder?
>
> Does the feature include the plugin or list it as required?
>
> Regards,
> Thomas Hallgren
>
>
|
|
|
|
| Re: Question on Site Creation and Targets [message #385521 is a reply to message #385520] |
Thu, 28 May 2009 10:57 |
|
Hi Alex,
First thing must be to submit a bugzilla so that we can track this. We are busy fixing review docs, IP-logs etc. for
Buckminsters Galileo participation over the coming days so any help fixing the problem is very much appreciated.
Regards,
Thomas Hallgren
Alex Chatziparaskewas wrote:
> Hi Thomas
>
> Sounds like a match. I checked my target platform and I can only confirm
> that the 'bad' bundles downloaded from the springsource repository use
> the '-' while the 'good' ones use the '_'.
>
> Big question now: How to solve this?
>
> Regards
> Alex
>
> Thomas Hallgren wrote:
>
>> Hi Alex,
>> Could your problem be related to this?
>
>> Regards,
>> Thomas Hallgren
>
>> Chase Wolfinger wrote:
>>> `Hello Thomas - I figured out the issue - not sure if it is a bug.
>>> The issue is that the names of the jars in my target did not match
>>> the name expected by buckminster. The pattern set used by
>>> buckminster is with patternSet{ includes:
>>> [org.ops4j.pax.configmanager_0.2.2.jar] whereas the jar I downloaded
>>> from the ops4j.pax site is named
>>> pax-confman-propsloader-0.2.2.jar, So I am not sure if this is a
>>> bug or more of naming standard that needs to documented when using
>>> non eclipse bundles. It seems like the naming standard vary a bit (see
> http://www.springsource.com/repository/app/bundle/version/de tail?name=org.springframework.osgi.core&version=1.1.1.A
>
>>>
> < http://www.springsource.com/repository/app/bundle/version/de tail?name=org.springframework.osgi.core&version=1.1.1.A>)
>
>>>
>>>
>>> CHase
>>>
>>> On Mon, May 25, 2009 at 12:39 AM, Thomas Hallgren <thomas@tada.se
>>> <mailto:thomas@tada.se>> wrote:
>>>
>>> Chase wrote:
>>>
>>> Hello - I just started using buckminster and it has been
>>> relatively easy to get working so far. The one issue I have
>>> is related to why the plugins from the target platform are not
>>> stored in the resultant p2 site. As an example, the
>>> org.springframework.context bundle is in my target platform.
>>> I execute buckminster site.p2 action from a feature project
>>> and the result is that the only action taken on this target
>>> platform bundle is:
>>>
> org.springframework.context:osgi.bundle$2.5.6.A#OSGi#target. fragments
>>>
>>> When I check the update site the bundle is not extracted to
>>> the plugins directory as an artifact. Is there a simple way
>>> to create either a seperate update site for a given target
>>> definition or to cause p2 to copy the plugins as artifacts
>>> into the update site?
>>>
>>> It really should do that by default. Are you sure you look in the
>>> right place? I.e. the ${buckminster.output.root}<build result for
>>> your project>/site.p2/plugins folder?
>>>
>>> Does the feature include the plugin or list it as required?
>>>
>>> Regards,
>>> Thomas Hallgren
>>>
>>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03385 seconds
] 
Search
Help
Register
Login
Home
