Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313640 - publish.bin.parts target in the pde generated plugin build.xml overwrites the META-INF/MANIFEST in plugin root
Summary: publish.bin.parts target in the pde generated plugin build.xml overwrites the...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 4.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-19 20:36 EDT by Sheryl CLA
Modified: 2019-11-26 08:18 EST (History)
1 user (show)

See Also:


Attachments
Build configuration build.properties (10.32 KB, text/plain)
2010-05-19 20:38 EDT, Sheryl CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sheryl CLA 2010-05-19 20:36:46 EDT
Build Identifier: 3.6.0 I20100312-1448

I'm running a headless PDE build with 3.6 M6. I have 2 issues:

1. In publish.bin.parts target in the pde generated build.xml of a plugin, there is a task :
        <eclipse.versionReplacer path="${build.result.folder}" version="<version>"/>

This overwrites the plugin META-INF/MANIFEST because ${build.result.folder} is equal to ${basedir}. As a result, the next build doesn't pick up a new qualifier for the plugin version.

If I set the customBuildCallbacks property in the plugin build.properties, the task changes to:
        <eclipse.versionReplacer path="${build.result.folder}/<plugin id>_<version>" version="<version>"/>

This works because the replacement is done not in the src folder, but in a different folder.
        
2. Also, the clean target of plugin build.xml doesn't delete this folder: 

        <mkdir dir="${build.result.folder}/<plugin id>_<version>"/>


The workaround I have is to delete all the plugins after a build and re-fetch. This adds to the build time.

Reproducible: Always

Steps to Reproduce:
1. Run a eclipse headless PDE build using an ant task -        
 <exec executable="java" errorproperty="result.code">
            <arg line="-jar ${eclipse.base}/plugins/org.eclipse.equinox.launcher_1.1.0.v20100307.jar -application org.eclipse.ant.core.antRunner -buildfile ${eclipse.base}/plugins/org.eclipse.pde.build_3.6.0.v20100311-1400/scripts/build.xml
                -DforceContextQualifier=104
                -Dbuilder=${build.config.dir}
                -DbuildDirectory=${buildDirectory}"/>
        </exec>

2. After the build completes, the plugin MANIFEST has changed.
Comment 1 Sheryl CLA 2010-05-19 20:38:49 EDT
Created attachment 169253 [details]
Build configuration build.properties
Comment 2 Helge Böhme CLA 2017-12-04 14:49:09 EST
Bug is still open with 4.7.1a!
Comment 3 Eclipse Genie CLA 2019-11-25 15:28:47 EST
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.
Comment 4 Helge Böhme CLA 2019-11-26 08:18:47 EST
I can still reproduce this with Eclipse 2019-09 R (4.13.0).
My current workaround is to have customBuildCallbacks property.