Bug 282958 - PDE/Build should use <requires> to compute build path
Summary: PDE/Build should use <requires> to compute build path
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-09 01:50 EDT by Ian Bull CLA
Modified: 2022-11-19 20:32 EST (History)
0 users

See Also:


Attachments
Sample Builder (13.54 KB, application/x-zip-compressed)
2009-07-09 01:50 EDT, Ian Bull CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Bull CLA 2009-07-09 01:50:21 EDT
Created attachment 141158 [details]
Sample Builder

This is similar to Bug 177247, but with a slight twist.

I have two features and two plugins
Foo (feature)
 A (bundle)

Bar (feature)
 B (bundle)

A has a dependency on B.

Now I want to build feature Foo (by itself).  Bar (and B) are in my builder, but not built yet.  I have added a <requires / import> from Foo to Bar.  However, when I build Foo, I get a compile error because the classes in B cannot be resolved.  The classpath looks like it's being set properly, but the Bar bundles are just not being built.

Does it make sense to build these bundles (but not package them) because of the requirement from Foo to Bar?

I have attached a sample builder to show you what I mean.
Comment 1 Lars Vogel CLA 2018-12-03 09:12:08 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 CLA 2018-12-03 09:13:37 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 CLA 2020-11-28 13:17:32 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 CLA 2022-11-19 20:32:25 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.