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 226266 - Move SDK to NB repository
Summary: Move SDK to NB repository
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 7.4
Hardware: All All
: P1 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-18 11:16 UTC by Petr Hejl
Modified: 2015-06-16 12:49 UTC (History)
5 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

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 Petr Hejl 2013-02-18 11:16:21 UTC 
As recent problems with (just) 2 branches have shown the SDK development is far from being ideal. It looks to me that NetBeans is the primary customer of the SDK and the SDK is changed primarily for NetBeans. Not surprisingly - the NB has always been the first platform supporting new releases of GF.

So it seems logical to just have the SDK as a nbm module in the NB repository. Just having it as nbm and in the repository does not prevent it to
- be solely JDK dependent
- be jar only which others could use

I believe this would also limit number of regressions and merge conflicts.
Comment 1 TomasKraus 2013-02-18 12:15:34 UTC 
This is something that should be discussed on highest level, not just inside NetBeans team. SDK is shared between Eclipse and NetBeans and may be used by other IDEs in the future. I'm planing to make it some kind of GlassFish client library in the future, not just separate NetBeans module.

Yes, NetBeans is primary customer during this stage of developemnt but it's not the only one.
Comment 2 Petr Hejl 2013-02-18 12:38:55 UTC 
(In reply to comment #1)
> This is something that should be discussed on highest level, not just inside
> NetBeans team. SDK is shared between Eclipse and NetBeans and may be used by
> other IDEs in the future. I'm planing to make it some kind of GlassFish client
> library in the future, not just separate NetBeans module.
As written above having it a nbm does not prevent anything of this.

Alternative would be to have it part of the GF itself, being part of the GF repository and GF builds.

> Yes, NetBeans is primary customer during this stage of developemnt but it's not
> the only one.
Comment 3 Petr Hejl 2015-06-16 12:49:27 UTC 
This has been already resolved.