This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 73663 - Propagate abilities to other projects
Summary: Propagate abilities to other projects
Status: NEW
Alias: None
Product: javame
Classification: Unclassified
Component: Fragmentation (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Karol Harezlak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-16 15:20 UTC by ieising
Modified: 2009-10-01 13:24 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ieising 2006-03-16 15:20:05 UTC
Hi,

We're developing our MIDLets using our own libraries as well as others. This
means that our J2ME project has a dependency to our J2ME Library project, but
now we would like to be able to use the abilities we define in our MIDlet
project also in the library project, such that this library is recreated when
the MIDlet is compiled using the abilities set in the MIDlet project.

Iwan
Comment 1 Lukas Hasik 2006-06-23 14:34:57 UTC
moving to mobility component
Comment 2 Adam Sotona 2007-05-21 15:03:42 UTC
Relation between application projects, their configurations and library projects
and thier configurations is many-to-many.
The only way how to manage your proposal is to create a clone build of each
library for each application project configuration.
If you imagine application->library->library transition then the complexity of
this issue is incredibly growing.
Calculating also ability name conflicts results in building engine that exceeds
Ant limits.
I am closing it as WONTFIX due to too big price of the feature implementation.
Please reopen if you still think it is worth the price.
Comment 3 ieising 2007-07-01 19:29:55 UTC
I can see your point on the complexity and on the naming-clash issue, but here's an idea:

- When creating a new project and adding project dependencies to the project, there is an option to propagate the
abilities defined in the project to the library-project. When checked all abilities of the active configuration will be
propagated to the library-project which will then be build. When left unchecked (default), the current behavior will be
used.

- In case of naming-clashes the ability of the project has priority over the ability in the library-project.

This is a very clear and simple behavior and I think it is enough to only have this option in project -> library-project
relations, project -> library-project -> library-project will only go as far as the first library-project.

Believe me, the time I wasted because I had to change an ability or configuration which I'd forgot is tremendous.

Iwan