Re: [pde-build-dev] problems with configs= option

[Andrew Niefer <aniefer@xxxxxxxxxx>]

Are you using a recent pde.build?  There
may be a bug in pde.build, We have also seen missing features when building
using the latest pde.build, but we have not yet identified what the problem
is.

If you have assemble.*.xml you can send,
they might be usefull to find the problem.

-Andrew

Leonardo Augusto Guimarães Garcia <lagarcia@xxxxxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

10/08/2007 04:59 PM

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

To	pde-build-dev@xxxxxxxxxxx
cc
Subject	[pde-build-dev] problems with configs= option

Hi,

I am trying to headless build a feature I am developing but I am getting
a strange behavior with configs option in build.properties. The feature
I am building has some restrictions on which architectures and operating
systems it can be installed. Its build.properties has the bin.includes
property correctly set.

If I don't set configs or if I set it to "*,*,*", the build process
successfully ends up and the zip file generated contains only the 
plug-ins' jars. On the other hand, if I set the configs to the list of
architectures and operating systems supported by my feature, the zip 
file generated contains the plug-ins' jars and the feature jar.

Is this the correct behavior, I mean, the feature jar will only be 
generated when configs point the build process to the exactly 
architectures/operating systems supported by my plug-in? Or is this a bug?

Best regards,

-- 
Leonardo Garcia
IDE Software Engineer - Linux on Cell
Linux Technology Center Brazil
Phone: +55-19-2132-2068 (T/L: 839-2068)
lagarcia@xxxxxxxxxx
_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev