Problem with p2 and version qualifiers [message #20085] |
Sat, 06 September 2008 23:27  |
Eclipse User |
|
|
|
Originally posted by: wbeckwith.gmail.com
I'm build a feature and I have the follwoignp2 properties defined in the
builder's build.properties file:
# P2 Properties
generate.p2.metadata = true
p2.metadata.repo.name = ${itko.repo.name}
p2.metadata.repo = ${itko.repo}
p2.artifact.repo.name = ${itko.repo.name}
p2.artifact.repo = ${itko.repo}
p2.flavor = tooling
p2.publish.artifacts = true
p2.root.name = iTKO Lisa
p2.root.version = 1.0.0.qualifier
When doing the build my plug-ins and features with a version of
1.0.0.qualifier will get the "qualifier" substituted during the build,
but the p2.root.version property does not and always ends up as
1.0.0.qualifier. How do I need to change things so that this is
dynamically updated during the build?
Wb
|
|
|
|
|
Re: Problem with p2 and version qualifiers [message #20398 is a reply to message #20381] |
Tue, 09 September 2008 15:43  |
Eclipse User |
|
|
|
Wendell,
Unfortunately you will need to use the workaround for now. Build does
not currently have support to replace qualifiers that are used in the p2
calls.
There is https://bugs.eclipse.org/bugs/show_bug.cgi?id=246060 which is
related to this, I added a note there about p2.root.version.
If you are using a .product file and want the version replaced there,
there is a workaround in the example on my blog
( http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html).
-Andrew
Wendell Beckwith wrote:
> That's a suggestion/workaround if was to change the version from
> 1.0.0.qualifier to 1.0.0.${qualifier} and pass "-Dqualifer=myqualifier".
> First I'd have to compute the qualifier and then inject it into the pde
> build command invocation and 2nd pde build normally takes care of this.
> PDE build is doing the right thing for the feature and plug-ins, it just
> doesn't seem to be doing the right thing when building the p2 repo. So
> I'm trying to see if my setup is in error or if pde build has a bug.
>
> Wb
>
> Ketan Padegaonkar wrote:
>> I'm setting quite some properties via: -Dproperty.name=property.value
>> when invoking pdeBuild.xml.
>>
>> You could inject the qualifier in the same way.
>>
>> -- Ketan
>>
>> Wendell Beckwith wrote:
>>> I'm build a feature and I have the follwoignp2 properties defined in
>>> the builder's build.properties file:
>>>
>>> # P2 Properties
>>> generate.p2.metadata = true
>>> p2.metadata.repo.name = ${itko.repo.name}
>>> p2.metadata.repo = ${itko.repo}
>>> p2.artifact.repo.name = ${itko.repo.name}
>>> p2.artifact.repo = ${itko.repo}
>>> p2.flavor = tooling
>>> p2.publish.artifacts = true
>>> p2.root.name = iTKO Lisa
>>> p2.root.version = 1.0.0.qualifier
>>>
>>> When doing the build my plug-ins and features with a version of
>>> 1.0.0.qualifier will get the "qualifier" substituted during the
>>> build, but the p2.root.version property does not and always ends up
>>> as 1.0.0.qualifier. How do I need to change things so that this is
>>> dynamically updated during the build?
>>>
>>> Wb
|
|
|
Re: Problem with p2 and version qualifiers [message #579327 is a reply to message #20085] |
Tue, 09 September 2008 14:40  |
Eclipse User |
|
|
|
I'm setting quite some properties via: -Dproperty.name=property.value
when invoking pdeBuild.xml.
You could inject the qualifier in the same way.
-- Ketan
Wendell Beckwith wrote:
> I'm build a feature and I have the follwoignp2 properties defined in the
> builder's build.properties file:
>
> # P2 Properties
> generate.p2.metadata = true
> p2.metadata.repo.name = ${itko.repo.name}
> p2.metadata.repo = ${itko.repo}
> p2.artifact.repo.name = ${itko.repo.name}
> p2.artifact.repo = ${itko.repo}
> p2.flavor = tooling
> p2.publish.artifacts = true
> p2.root.name = iTKO Lisa
> p2.root.version = 1.0.0.qualifier
>
> When doing the build my plug-ins and features with a version of
> 1.0.0.qualifier will get the "qualifier" substituted during the build,
> but the p2.root.version property does not and always ends up as
> 1.0.0.qualifier. How do I need to change things so that this is
> dynamically updated during the build?
>
> Wb
|
|
|
Re: Problem with p2 and version qualifiers [message #579404 is a reply to message #20351] |
Tue, 09 September 2008 14:54  |
Eclipse User |
|
|
|
Originally posted by: wbeckwith.gmail.com
That's a suggestion/workaround if was to change the version from
1.0.0.qualifier to 1.0.0.${qualifier} and pass "-Dqualifer=myqualifier".
First I'd have to compute the qualifier and then inject it into the
pde build command invocation and 2nd pde build normally takes care of
this. PDE build is doing the right thing for the feature and plug-ins,
it just doesn't seem to be doing the right thing when building the p2
repo. So I'm trying to see if my setup is in error or if pde build has
a bug.
Wb
Ketan Padegaonkar wrote:
> I'm setting quite some properties via: -Dproperty.name=property.value
> when invoking pdeBuild.xml.
>
> You could inject the qualifier in the same way.
>
> -- Ketan
>
> Wendell Beckwith wrote:
>> I'm build a feature and I have the follwoignp2 properties defined in
>> the builder's build.properties file:
>>
>> # P2 Properties
>> generate.p2.metadata = true
>> p2.metadata.repo.name = ${itko.repo.name}
>> p2.metadata.repo = ${itko.repo}
>> p2.artifact.repo.name = ${itko.repo.name}
>> p2.artifact.repo = ${itko.repo}
>> p2.flavor = tooling
>> p2.publish.artifacts = true
>> p2.root.name = iTKO Lisa
>> p2.root.version = 1.0.0.qualifier
>>
>> When doing the build my plug-ins and features with a version of
>> 1.0.0.qualifier will get the "qualifier" substituted during the build,
>> but the p2.root.version property does not and always ends up as
>> 1.0.0.qualifier. How do I need to change things so that this is
>> dynamically updated during the build?
>>
>> Wb
|
|
|
Re: Problem with p2 and version qualifiers [message #579443 is a reply to message #20381] |
Tue, 09 September 2008 15:43  |
Eclipse User |
|
|
|
Wendell,
Unfortunately you will need to use the workaround for now. Build does
not currently have support to replace qualifiers that are used in the p2
calls.
There is https://bugs.eclipse.org/bugs/show_bug.cgi?id=246060 which is
related to this, I added a note there about p2.root.version.
If you are using a .product file and want the version replaced there,
there is a workaround in the example on my blog
( http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html).
-Andrew
Wendell Beckwith wrote:
> That's a suggestion/workaround if was to change the version from
> 1.0.0.qualifier to 1.0.0.${qualifier} and pass "-Dqualifer=myqualifier".
> First I'd have to compute the qualifier and then inject it into the pde
> build command invocation and 2nd pde build normally takes care of this.
> PDE build is doing the right thing for the feature and plug-ins, it just
> doesn't seem to be doing the right thing when building the p2 repo. So
> I'm trying to see if my setup is in error or if pde build has a bug.
>
> Wb
>
> Ketan Padegaonkar wrote:
>> I'm setting quite some properties via: -Dproperty.name=property.value
>> when invoking pdeBuild.xml.
>>
>> You could inject the qualifier in the same way.
>>
>> -- Ketan
>>
>> Wendell Beckwith wrote:
>>> I'm build a feature and I have the follwoignp2 properties defined in
>>> the builder's build.properties file:
>>>
>>> # P2 Properties
>>> generate.p2.metadata = true
>>> p2.metadata.repo.name = ${itko.repo.name}
>>> p2.metadata.repo = ${itko.repo}
>>> p2.artifact.repo.name = ${itko.repo.name}
>>> p2.artifact.repo = ${itko.repo}
>>> p2.flavor = tooling
>>> p2.publish.artifacts = true
>>> p2.root.name = iTKO Lisa
>>> p2.root.version = 1.0.0.qualifier
>>>
>>> When doing the build my plug-ins and features with a version of
>>> 1.0.0.qualifier will get the "qualifier" substituted during the
>>> build, but the p2.root.version property does not and always ends up
>>> as 1.0.0.qualifier. How do I need to change things so that this is
>>> dynamically updated during the build?
>>>
>>> Wb
|
|
|
Powered by
FUDForum. Page generated in 0.06038 seconds