Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pde-dev] how to generate container feature in pde build

yay it works!

thanks a lot Andrew!


Jacek


2010/9/22 Andrew Niefer <aniefer@xxxxxxxxxx>

There is probably a bug in the fetch, it really should just use the feature if it already exists in the buildDirectory.

You could name the generated feature "org.eclipse.pde.build.container.feature", that name is handled specially by the fetch and it won't try to fetch it.

-Andrew

Inactive hide details for Jacek Pospychała ---09/22/2010 11:12:34 AM---hi, I remember this was discussed already, but can't goJacek Pospychała ---09/22/2010 11:12:34 AM---hi, I remember this was discussed already, but can't google it so please help!


From:

Jacek Pospychała <jacek.pospychala@xxxxxxxxx>

To:

"Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx>

Date:

09/22/2010 11:12 AM

Subject:

[pde-dev] how to generate container feature in pde build

Sent by:

pde-dev-bounces@xxxxxxxxxxx




hi,
I remember this was discussed already, but can't google it so please help! :-)

I want to build two features in one pdebuild run.
Until now I was solving this by defining many calls in allElements target:

<target name="allElements">
        <ant antfile="${genericTargets}" target="${target}">
             <property name="type" value="${topLevelElementType1}" />
             <property name="id" value="${topLevelElementId1}" />
         </ant>
        <ant antfile="${genericTargets}" target="${target}">
             <property name="type" value="${topLevelElementType2}" />
             <property name="id" value="${topLevelElementId2}" />
         </ant>
    </target>

unfortunately, now I discovered the downside of this approach is that when using p2.gathering=true, the generated metadata contains only the last element :-(

The other way that I read of somewhere, was to generate container feature during the build. I tried

<target name="preSetup">
...
<eclipse.generateFeature featureId="tarara.container.feature" buildDirectory="${buildDirectory}" featuresList="topLevelElement1,topLevelElement2" />

I can see that feature is generated correctly. But later, during the fetch, pde build is failing to fetch top level feature:

fetchElement:
   [mkdir] Created dir: /disk2/hudson/jobs/org.mozilla.xulrunner.7_3/workspace/build/plugins
[eclipse.fetch] Missing directory entry: feature@xxxxxxxxxxxxxxx.feature.
[eclipse.fetch] feature@xxxxxxxxxxxxxxx.feature has not be fetched.

R36_RC4/plugins/org.eclipse.pde.build_3.6.0.v20100603/scripts/genericTargets.xml:59: The following error occurred while executing this line:
java.io.FileNotFoundException: /disk2/hudson/jobs/job/workspace/build/fetch_tararara.container.all.feature.xml (No such file or directory)


So feature is already there, and there's no need to fetch it. Altough topLevelElement1 and topLevelElement2 need to be fetched.
So what else I need to do? Use eclipse.fetch?

At last I can create container feature in CVS but this is lame :-)

thanks

Jacek
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev



_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev


GIF image

GIF image


Back to the top