RE: [orbit-dev] RE: Problem with building feature when feature useorbit'

["Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>]

Hi Dennis,

your build.properties needs to include "runPackager=true"
See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=177216

David, and other Orbit build Wizards, I tried finding this
info in the Orbit FAQ but couldn't find it. I think this is
really one of the major points that people stumble over. 
I just fund this in my personal ML archive...

I don't feel ready to add this to the FAQ myself since I
don't feel I know enough of the packager story around this
but I'd appreciate if somebody could add it.

Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
 
 

> -----Original Message-----
> From: orbit-dev-bounces@xxxxxxxxxxx 
> [mailto:orbit-dev-bounces@xxxxxxxxxxx] On Behalf Of Dennis 
> (Uy Dung) Nguyen
> Sent: Sonntag, 25. Mai 2008 11:14
> To: orbit-dev@xxxxxxxxxxx
> Subject: [orbit-dev] RE: Problem with building feature when 
> feature useorbit'splug-ins (Andrew Niefer)
> 
> Hi Andrew and Martin,
> 
> Thank you for your promptly replies, but I believe my description of
> the problem has caused some misunderstanding, so I attached a zip file
> to demonstrate the problem more clearly. The file contains 5 project:
> commons.lang (2.1), testA, testB, TestFeature and
> TestFeatureUpdatesite. You can import them as existing project from an
> archive and build the update site to produce the error.
> 
> To Andrew,
> As you can see in the attached projects, commons.lang plugin is
> checked out and existed as a normal plugins in my workspace. So I
> don't think I need to fetch it again, nor I actually need it inside my
> feature.
> 
> To Martin,
> I am not sure what you mean with "Eclipse Packager". I may have to ask
> about this, as I do want to include some of orbit library in a support
> feature, just so it's more convenient for user to download and install
> our plugin.
> 
> However, our problem at the moment is not in building individual
> plugins, but it building them as a feature, or in update site.
> Building individually, my plugins are compiled and run without any
> complains. But when I build the feature in update site, the error
> happens, which seems to me that:
> 1. The update site build is actually try to compile my plugin source
> again, together but in different threads
> 2. One of those thread locks the class file in commons.lang, which
> makes the next thread, compile the next plugin but need commons.lang,
> report the unresolv error.
> 
> Does this seem to be the case to you ? And if it is, is there anyway
> for me to walk-around/fix it ?
> 
> Cheers,
> -- 
> Dennis Nguyen (Uy Dung Nguyen)
> http://www.linkedin.com/in/dennisn08
> 
> Software Developer
> Kestral Computing Pty Ltd
> E-mail: dennisn@xxxxxxxxxxxxxx
> Web: www.kestral.com.au
> 
> Phone: + 61 3 9450 2222
> Fax: + 61 3 9450 2299
> 
> 
> Proudly sponsoring 'Amie' - guide dog for the blind
>