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

[Andrew Niefer <aniefer@xxxxxxxxxx>]

If you have bundles to compile, there
is no real reason why you can't do it all in a normal build instead of
using the packager.

If the feature you are building does
not actually include the apache bundle (only requires it) then the apache
bundle would not have been downloaded as part of the fetch phase.  If
it does not otherwise exist in your baseLocation then that would be the
cause of the failure.

You could use a custom step to fetch
the apache bundle separately, there is an example here http://wiki.eclipse.org/PDEBuild#Fetching_the_.product_file_in_a_product_build.
 This would require a map file using GET.

-Andrew

"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
Sent by: orbit-dev-bounces@xxxxxxxxxxx

05/23/2008 04:49 AM

Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>

To	"Orbit Developer discussion" <orbit-dev@xxxxxxxxxxx>
cc
Subject	RE: [orbit-dev] Problem with building feature when feature use        orbit'splug-ins

Dennis,

when your feature is to include any pre-built bundle
(like the Orbit bundles), your builder needs to run
the Eclipse Packager or the pre-built stuff will not
turn up in your feature.

http://wiki.eclipse.org/Orbit_Builds#Orbit_Builds_for_Consumers

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: Freitag, 23. Mai 2008 10:04
> To: orbit-dev@xxxxxxxxxxx
> Subject: [orbit-dev] Problem with building feature when 
> feature use orbit'splug-ins
> 
> 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
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orbit-dev
> 
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev