Community
Participate
Working Groups
Product builds are based on a .product file. Currently the plug-in/feature containing this file needs to exist on disk before the fetch phase so that we can generate the container feature that will be used to drive the build. We should come up with a way to do an early fetch for this one plug-in/feature so that the user does not have to do it manually.
It would be good to have a fix for that for eclipse con.
As a temporary fix, modify customTargets.xml step postSetup as follows:- <target name="postSetup"> <antcall target="getBaseComponents" /> <ant antfile="${genericTargets}" target="fetchElement"> <property name="type" value="feature"/> <property name="id" value="org.feature.containing.product.file" /> </ant> </target> Note: This line is there in customTargets.xml by default under postSetup <antcall target="getBaseComponents" /> Prince Singh Drishti Soft Solutions Pvt Ltd
Can we not just use the maps file for this? i.e. look in the map file for a line matching the plugin/feature and check it out? I'm sure there is a good reason why this won't work, I'm just wondering what it is.
I don't know when it changed, but a ".product" file no longer needs to be in a feature or plug-in. It also works when you place the product file next to (inside) your local builder. Thus, when the builder is bootstrapped, your product files are automatically included. For example, I invoke the builder in the following way: <target name="main" depends="init"> <dirname file="${ant.file.build-gyrex-1.0.x}" property="builder"/> <property file="${builder}/build.properties"/> <ant antfile="${eclipse.pdebuild.scripts}/productBuild/productBuild.xml" /> </target> The build.properties contains the following definition: product=${builder}/gyrex-techpreview.product
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. Please reopen, if you plan to provide a fix.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
