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 172643 - Cannot build self contained Platform
Summary: Cannot build self contained Platform
Status: RESOLVED INVALID
Alias: None
Product: www
Classification: Unclassified
Component: Builds & Repositories (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: nbbuild-issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-21 08:19 UTC by emi
Modified: 2009-09-21 18:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description emi 2009-09-21 08:19:20 UTC
Hy,

I downloads the 6.7.1-fcs repository and tried to build the platform cluster alone.

In order to do this I exited nbbuild/cluster.properties and set cluster.config=platform

The build works, but it doesn't produce correct launchers.

I had to manually remove from the shell launcher (netbeans) the lines:

            -J-Dnetbeans.importclass=org.netbeans.upgrade.AutoUpgrade \
            -J-Dnetbeans.accept_license_class=org.netbeans.license.AcceptLicense \
            --branding nb \

On OSX I also removed the lines pointing to non-existing file
            '"-J-Xdock:icon=$progdir/../nb6.7/netbeans.icns"' \


Now, the build seems to work correctly (download and run on OSX
https://netbeans-romanian-l10n.s3.amazonaws.com/netbeans-ro-localize-6.7.1-fcs.zip for example).

The problem is that it doesn't seem to work on Windows since it has those AutoUpgrade/AcceptLicense parameters hardcoded.

Anything I am missing ? I haven't built the Platform alone for quite some time but it looks like a genuine bug.
Comment 1 Jesse Glick 2009-09-21 16:24:34 UTC
First of all, you do not need to edit anything to build the platform; simply run

  ant build-platform

Second, this target intentionally builds no launcher for the Platform - because it is a library, not a standalone
product. A suite built atop the platform can be configured to be an Application (rather than Collection of Add-on
Modules), in which case its build will create a product-specific launcher.
Comment 2 emi 2009-09-21 17:58:07 UTC
I understand -- so I have been misusing the build system, my bad. I did say that I didn't build a standalone Platform
for quite some time.

Two things are strange to me though:

1. The fact that the Platform is viewed as a library. I know that long ago NetBeans did provide a separate build with a
standalone Platform but that stopped. I thought it was because there were no people downloading the platform binary /
src. Now I see it's also a philosophical shift that happened.

2. The fact that I can't build a Platform base system right after a clone operation. So if I start with a fresh 6.7.1
mercurial clone I have to first build the Platform, then register the Platform in the IDE, then create a Suite in the
IDE, then build that.
Comment 3 Jesse Glick 2009-09-21 18:07:04 UTC
There ought to be Platform source & binary downloads somewhere on the netbeans.org website. (I don't know where offhand,
since of course I would not use them personally.)

No philosophical shift. You still need to write an actual app to use the Platform, no matter how you get it - the
Platform itself doesn't do anything. It is only a collection of modules of which you can use some subset within an
application (optionally adding in further prebuilt modules from the NetBeans IDE or some other source).

Not sure what you mean by "Platform base system". 'hg clone' followed by 'ant build-platform' creates the Platform. I
don't think anything has changed in this regard in years, other than the CVS -> Hg migration.
Comment 4 emi 2009-09-21 18:25:02 UTC
By 'Platform base system' I meant a Platform with a launcher.