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 148578 - [65cat] Latest Development Build Update Center down
Summary: [65cat] Latest Development Build Update Center down
Status: RESOLVED FIXED
Alias: None
Product: updatecenters
Classification: Unclassified
Component: Dev (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: rnovak
URL:
Keywords:
: 148596 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-09-28 12:37 UTC by big_al
Modified: 2008-10-03 13:19 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
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 big_al 2008-09-28 12:37:43 UTC 
[ BUILD # : 200809271401 ]
[ JDK VERSION : 1.6.0_07 ]

The "Latest Development Build" update center is unavailable. The
following message is received upon Reloading the Catalog:

Unable to connect to the Latest Development Build because of
java.io.FileNotFoundException:
http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/lastStableBui
ld/artifact/nbbuild/nbms/updates.xml.gz
Comment 1 Jaromir Uhrik 2008-09-29 08:08:18 UTC 
Confirming the problem. Passing to AUC component.
Comment 2 rnovak 2008-09-29 16:34:51 UTC 
The problem is caused by the fact, that there wasn't stable NBMs build for long time. Link lastStableBuild now points to
the build that was already removed. Development should fix the problematic modules.
Comment 3 Jesse Glick 2008-09-29 17:47:25 UTC 
Standa is supposed to be fixing the build.

The root issue is I think a bug in Hudson:

https://hudson.dev.java.net/nonav/issues/show_bug.cgi?id=2417
Comment 4 Jesse Glick 2008-09-30 14:22:02 UTC 
All issues with the previous builds that I know of are resolved in sources. I have manually triggered a request for a
new build, so check back in a couple of hours...
Comment 5 Jesse Glick 2008-09-30 21:40:48 UTC 
Seems to be fixed now.
Comment 6 Jiri Kovalsky 2008-10-03 13:19:33 UTC 
*** Issue 148596 has been marked as a duplicate of this issue. ***