Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 333195 - Flexible version numbers in Target Definition
Summary: Flexible version numbers in Target Definition
Status: CLOSED DUPLICATE of bug 273159
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-24 08:30 EST by Wim Jongman CLA
Modified: 2011-01-04 10:42 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Wim Jongman CLA 2010-12-24 08:30:14 EST 
Hi,

I have an automated build process that creates a P2 repo. If this build step is complete, another step is started that builds a product that is depends on that repo. 

I have created a target definition that points to the p2 repo. The features in the p2 have to be declared specifically.  Every time the repo is build, it renders the target defintion useless because the version numbers are changing.

Is it possible to make the version numbers flexible of the target definition points to a p2 repo? 
- I have tried some obvious hacks but the target definition xml seems to be very strict about the version number attribute. 

Is it possible to let the target definition consume all features without specifically selecting them?
Comment 1 Curtis Windatt CLA 2011-01-04 10:42:58 EST 
In the latest 3.7 builds we have the ability to update targets from the editor, that should help you keep your targets in synch.

You might be able to workaround this limitation by making your version 0.0.0  This is not officially supported though.

See bug 328660 and bug 273159

*** This bug has been marked as a duplicate of bug 273159 ***