266727 – Publishing metadata and custom build.xml

Bug 266727 - Publishing metadata and custom build.xml

Summary: Publishing metadata and custom build.xml

Status:	NEW

Alias:	None

Product:	PDE
Classification:	Eclipse Project
Component:	Build (show other bugs)
Version:	3.5
Hardware:	PC Windows XP

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	pde-build-inbox
QA Contact:

URL:
Whiteboard:	stalebug
Keywords:

Depends on:
Blocks:

Reported:	2009-03-02 13:17 EST by Andrew Niefer
Modified:	2022-11-15 12:31 EST (History)
CC List:	0 users

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 Andrew Niefer

2009-03-02 13:17:17 EST

With bug 249406 we can now publish to a p2 repo from the gather.bin.parts target.

Projects using custom=true will obviously not get this and they will have problems if they try to run with p2 publishing.

We can either require them to update their build.xml, which is what has always happened with new functionality in the past.

Or if we were really nice we could publish the built bundle as a binary bundle.

Comment 1 Lars Vogel

2018-12-03 09:11:02 EST

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.

Comment 2 Lars Vogel

2018-12-03 09:13:06 EST

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.

Comment 3 Eclipse Genie

2020-11-24 11:48:24 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 Eclipse Genie

2022-11-15 12:31:43 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.