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

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

Hi Martin,

Thank you for the clue. While it doesn't work with the original error,
it should help when I package all support plugins in a separate
feature.

However, while trying to play around with the problem using pde tools.
I happened upon a function that mirrors what I did in the update site.
The function is generating ant build file for feature (pde tools ->
Create ant build file), and I guess this is what building via
updatesite is based on. However, the ant build file for individual
plugin is slightly different between generating on feature.xml,
compared to those generating on individual plugin.

>From feature.xml:

                <path id="@dot.classpath">
			<pathelement path="../org.apache.commons.lang/@dot"/>
			<pathelement
path="${build.result.folder}/../org.apache.commons.lang_2.1.0.200805271048/@dot"/>
			<pathelement path="${build.result.folder}/../TestA/bin"/>
			<pathelement path="${build.result.folder}/../TestA_1.0.0/bin"/>
			<pathelement path="${build.result.folder}/../TestA/@dot"/>
			<pathelement path="${build.result.folder}/../TestA_1.0.0/@dot"/>
		</path>

>From plugin:

                <path id="@dot.classpath">
			<pathelement path="../org.apache.commons.lang"/>
			<pathelement path="../org.apache.commons.lang/@dot"/>
			<pathelement path="../TestA/bin"/>
			<pathelement path="../TestA/@dot"/>
		</path>

Most of the different is because the feature one expected a zip file
is created on each of its included plugin. However, this one is
missing from the ant file for org.apache.commons.lang when generate
via feature.xml :
        <pathelement path="../org.apache.commons.lang"/>

I copied it over the the first ant, and it compiled and works. I would
need to talk to PDE team about this, but just want to report this in
orbit as well.

Cheers,

On Tue, May 27, 2008 at 2:00 AM,  <orbit-dev-request@xxxxxxxxxxx> wrote:
> Date: Mon, 26 May 2008 10:30:46 +0200
> From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
> Subject: RE: [orbit-dev] RE: Problem with building feature when
>        feature useorbit'splug-ins (Andrew Niefer)
> To: "Orbit Developer discussion" <orbit-dev@xxxxxxxxxxx>
> Message-ID:
>        <460801A4097E3D4CA04CC64EE648584805D955E8@xxxxxxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain;       charset="us-ascii"
>
> 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
>>
>
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orbit-dev
>
>
> End of orbit-dev Digest, Vol 21, Issue 18
> *****************************************
>



-- 
Dennis Nguyen (Uy Dung Nguyen)
http://www.linkedin.com/in/dennisn08

Software Developer
Kestral Computing Pty Ltd