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 50965 - Dev update center shows incorrect content in recent dev builds
Summary: Dev update center shows incorrect content in recent dev builds
Status: RESOLVED FIXED
Alias: None
Product: updatecenters
Classification: Unclassified
Component: AU Masters (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: nbbuild-issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-29 09:01 UTC by Jan Chalupa
Modified: 2005-08-24 10:04 UTC (History)
3 users (show)

See Also:
Issue Type: TASK
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 Jan Chalupa 2004-10-29 09:01:31 UTC 
Starting with build #200410271800 the dev Update
Center started showing a number of available
modules. Some of those modules are obsolete and
none of them have been tested with current 4.0
builds. Current trunk builds are being used by
users participating in the NB 4.0 beta testing.
Allowing them to download obsolete and
experimental modules from the UC is not a good idea.

Jirka, I think the change could have been
triggered by your recent integration:

--------------%<--------------
2004-10-27 15:13  jrechtacek

* increase in main trunk - links to dev UC (a link
to 40 (fcs) will be created on fcs branch)
	autoupdate/src/org/netbeans/modules/autoupdate/XMLAutoupdateType.java:
--------------%<--------------

Please take a look at it.
Comment 1 Jiri Rechtacek 2004-10-29 10:03:33 UTC 
Will be fixed both change of content of catalog and a change of link
to NB4.0 FCS catalog.
Comment 2 Jesse Glick 2004-10-29 18:01:08 UTC 
I noticed that some of the apisupport modules there were many months
old, but I wasn't sure what this meant.
Comment 3 rbalada 2004-11-01 10:33:35 UTC 
I need some guidance what should be on the Dev Update Center.

What I can do immediatelly is to delete local cache with months old
modules and then rebuild the catalog.

For further maintance, there must be an update in moduleconfig
daily-alpha-nbms in nbbuild/build.properties file to include only
wanted modules.

Another point (IMHO) is, the expectation that Development Update
Center should not contain experimental modules, because certain small
group should not get confused. Wouldn't it be easier to setup extra
Update Center for such group? Well it's after branching so it can be
safely resolved, but it could come in again in 3 months for 4.1
release and we'll need to resolve it much earlier than by branching.

Please help us update the content.
Comment 4 Jiri Rechtacek 2004-11-01 16:05:39 UTC 
FYI: the Url in NB4.0 (built on top of release40 branch) links to
newly created UC, catalog for 4.0 FCS, empty for now.

Checking in
ide/updatecenters/src/org/netbeans/modules/updatecenters/resources/Bundle.properties;
/cvs/ide/updatecenters/src/org/netbeans/modules/updatecenters/resources/Bundle.properties,v
 <--  Bundle.properties
new revision: 1.1.28.1; previous revision: 1.1
done
Comment 5 rbalada 2005-08-24 10:04:58 UTC 
Fixed