| Creating separate zip files with feature and plugins [message #512779] |
Sun, 07 February 2010 09:50  |
Eclipse User |
|
|
|
Hi,
The modeling projects also make directly downloadable zips available which contain the SDK or runtime feature and all
their plugins. To create this zip I need to get the jar files for the main feature and all the subfeatures and plugins
and collect them in one zip file.
My question, is there a command I can use which has this 'api':
I pass in a feature/component id (for example org.eclipse.emf.teneo.hibernate.sdk)
and it generates two directories:
features: which contains the component/feature (org.eclipse.emf.teneo.hibernate.sdk) feature and all its subfeatures
plugins: which contains the plugins of these features
I thought/think about using the p2.site command and call it for each individual zip file I want to create, but then I
can't use the org.eclipse.emf.teneo.hibernate.sdk feature directly as the 'site' feature itself is not included in the
p2.site. So then I need to create additional site projects to generate these update sites which are used to create the
zip files. Which is not very difficult but I try to limit the number of needed projects a bit.
Is using the p2.site command the best way of doing this? Or are there other ways which do not require additional 'site'
projects?
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
|
| Re: Creating separate zip files with feature and plugins [message #512837 is a reply to message #512805] |
Mon, 08 February 2010 01:24  |
| Eclipse User |
|
|
|
Thanks, now for another detailed question regarding this :-):
I have a plugin and a feature which have the same id, I get this then when calling the site.p2 action:
[java] Found 12 warnings
[java] More then one version of component org.eclipse.emf.teneo.hibernate is known to Buckminster
Is there a way to tell buckminster to use the feature and not care about that there is a plugin with the same id?
gr. Martin
Thomas Hallgren wrote:
> Use the site.p2.zip action with the property
>
> site.include.top=true
>
> to have the top feature included in the repository.
>
> Regards,
> Thomas Hallgren
>
>
> On 02/07/2010 03:50 PM, Martin Taal wrote:
>> Hi,
>> The modeling projects also make directly downloadable zips available
>> which contain the SDK or runtime feature and all their plugins. To
>> create this zip I need to get the jar files for the main feature and all
>> the subfeatures and plugins and collect them in one zip file.
>>
>> My question, is there a command I can use which has this 'api':
>> I pass in a feature/component id (for example
>> org.eclipse.emf.teneo.hibernate.sdk)
>> and it generates two directories:
>> features: which contains the component/feature
>> (org.eclipse.emf.teneo.hibernate.sdk) feature and all its subfeatures
>> plugins: which contains the plugins of these features
>>
>> I thought/think about using the p2.site command and call it for each
>> individual zip file I want to create, but then I can't use the
>> org.eclipse.emf.teneo.hibernate.sdk feature directly as the 'site'
>> feature itself is not included in the p2.site. So then I need to create
>> additional site projects to generate these update sites which are used
>> to create the zip files. Which is not very difficult but I try to limit
>> the number of needed projects a bit.
>>
>> Is using the p2.site command the best way of doing this? Or are there
>> other ways which do not require additional 'site' projects?
>>
>
n
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
|
| Re: Creating separate zip files with feature and plugins [message #512849 is a reply to message #512847] |
Sun, 07 February 2010 22:08 |
| Eclipse User |
|
|
|
Hi Thomas,
I don't specify a component type in the perform command. Should I do that somewhere?
This is the command in ant-script:
<buckminster command="perform" workspace="${workspacePath}">
<cmdargs>
<arg value="org.eclipse.emf.teneo.hibernate#site.p2.zip" />
</cmdargs>
</buckminster>
(I copied the buckminster macrodef from the buckminster build).
gr. Martin
Thomas Hallgren wrote:
> On 02/08/2010 07:24 AM, Martin Taal wrote:
>> Thanks, now for another detailed question regarding this :-):
>> I have a plugin and a feature which have the same id, I get this then
>> when calling the site.p2 action:
>> [java] Found 12 warnings
>> [java] More then one version of component
>> org.eclipse.emf.teneo.hibernate is known to Buckminster
>>
>> Is there a way to tell buckminster to use the feature and not care about
>> that there is a plugin with the same id?
>>
> You should not need to tell buckminster this. A component is always (or,
> should always be) identified by both its name and its type.
>
> Would it be possible for you to debug where this happens (set a trap in
> AmbigousComponentException) and provide a stack trace?
>
> Regards,
> Thomas Hallgren
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
| Re: Creating separate zip files with feature and plugins [message #512863 is a reply to message #512849] |
Mon, 08 February 2010 03:52 |
| Eclipse User |
|
|
|
Hi Martin,
That explains it. Try using:
<arg value="org.eclipse.emf.teneo.hibernate:eclipse.feature#site.p2.zip " />
The perform command argument is in the form:
The BNF of the command is:
attribute_identifier:
component_identifier '#' attribute;
component_identifier:
component_name [ ':' component_type ] [ '#' component_version ]
Regards,
Thomas Hallgren
On 02/08/2010 09:06 AM, Martin Taal wrote:
> Hi Thomas,
> I don't specify a component type in the perform command. Should I do
> that somewhere?
>
> This is the command in ant-script:
> <buckminster command="perform" workspace="${workspacePath}">
> <cmdargs>
> <arg value="org.eclipse.emf.teneo.hibernate#site.p2.zip" />
> </cmdargs>
> </buckminster>
> (I copied the buckminster macrodef from the buckminster build).
>
> gr. Martin
>
> Thomas Hallgren wrote:
>> On 02/08/2010 07:24 AM, Martin Taal wrote:
>>> Thanks, now for another detailed question regarding this :-):
>>> I have a plugin and a feature which have the same id, I get this then
>>> when calling the site.p2 action:
>>> [java] Found 12 warnings
>>> [java] More then one version of component
>>> org.eclipse.emf.teneo.hibernate is known to Buckminster
>>>
>>> Is there a way to tell buckminster to use the feature and not care about
>>> that there is a plugin with the same id?
>>>
>> You should not need to tell buckminster this. A component is always
>> (or, should always be) identified by both its name and its type.
>>
>> Would it be possible for you to debug where this happens (set a trap
>> in AmbigousComponentException) and provide a stack trace?
>>
>> Regards,
>> Thomas Hallgren
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03887 seconds
Home