[orbit-dev] Problem with building feature when feature use orbit's plug-

["Dennis (Uy Dung) Nguyen" <dennis.nguyen.06@xxxxxxxxx>]

Hi all,

We are currently having problem doing a feature build, when some of
our plug-ins is using orbit's plug-ins. I had create some tests
project and figure out the problem's patterns. It goes like this:

* Project A depends on org.apache.commons.lang (import StringUtils in
class TestA)
* Project B depends on project A (import TestA) and
org.apache.commons.lang (import StringUtils in TestB)
* Feature TestFeature include both A and B, depending on
org.apache.commons.lang

Exporting TestFeature as deployable feature, or building it through an
update site, will result in compilation error, saying "Unable to
resolve org.apache" in either TestA/TestB .

The interesting thing is if I replace org.apache.commons.lang with a
different plugin (something I code), then the exporting and building
works as normal. This leads me to suspect there is something wrong
with the way orbit's plug-ins is packaged (or the way Eclipse building
treating those plugin). I had only tested with commons.lang, so not
sure if this also happens with other orbits packages.

Does anyone encounter similar problems ? Or have any hints on how to
fix this problem ?
If this is a totally new problem, then I would log a bug report

All hints are welcomed.
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