Re: [pde-build-dev] Setting plugin qualifiers with PDE Build 3.3

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

I believe that that is to handle case
where there might be several foo bundles inthe build.  In that case
there would be a different qualifier for each version and the enteries
would be differentiated by the three segment version number following the
symbolic name.  For example, 

com.ibm.foo,1.0.0=v20070625
com.ibm.foo,2.0.0=v20070720

If the version number is 0.0.0 then
it is essentially any version of that bundle. 

Andrew and/or Pascal should confirm
this.
Jeff

David Olsen <David.Olsen@xxxxxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

07/20/2007 05:17 PM

Please respond to
"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>

To	"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
cc
Subject	Re: [pde-build-dev] Setting plugin qualifiers with PDE Build 3.3

It looks like the key in pluginVersions.properties and featureVersions.properties
has changed from just the plugin or feature ID to instead be the ID followed
by ",0.0.0".  Where we used to have to write out
        com.ibm.foo=v20070720 
we now need to write out 
        com.ibm.foo,0.0.0=v20070720

I have no idea what purpose the ",0.0.0" serves, but I have made
that change to our build tools and it now seems to work with PDE Build
3.3.

Andrew Niefer <aniefer@xxxxxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

07/18/2007 09:59

Please respond to
"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>

To	"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
cc
Subject	Re: [pde-build-dev] Setting plugin qualifiers with PDE Build 3.3

David, 

The only change I can see in this area is the addition of a property named
"packagerAsNormalizer" which came from https://bugs.eclipse.org/bugs/show_bug.cgi?id=185976.

If this property is not set or we are not running as the packager, the
value is set to "true" 

Qualifier replacement won't happen if the value is not true.  I don't
know if this is the problem for you, but I can't think of anything else
right now. 

- 
-Andrew

David Olsen <David.Olsen@xxxxxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

07/17/2007 05:35 PM

Please respond to
"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>

To	pde-build-dev@xxxxxxxxxxx
cc
Subject	[pde-build-dev] Setting plugin qualifiers with PDE Build 3.3

Last October in a message to pde-build-dev Andrew Niefer wrote:

The map files are concatentated together into the directory.txt file.  This
file is the input into the FetchScriptGenerator.

The FetchScriptGenerator outputs two files: pluginVersions.properties and
featureVersions.properties.
It is these two files that the BuildScriptGenerator uses to replace the
qualifiers.  So your BIRT versions tools should update these files
instead of the directory.txt

In some of our builds we have been doing exactly that, modifying pluginVersions.properties
and featureVersions.properties to give plugins and features the qualifiers
that we want them to have.  (The source is not in CVS, so we can't
use the typical map files and tags processing to set the qualifiers.  And
we want different plugins to have different qualifiers, so setting forceContextQualifier
in build.properties won't work.) 

When we switched to PDE Build 3.3, that stopped working.  PDE Build
is still creating pluginVersions.properties and featureVersions.properties.
 But those files are empty, and PDE Build seems to be ignoring any
properties we put in them. 

How can we get this to work again with PDE Build 3.3?

_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev
_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev
_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev