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 37271 - Trying to download jellytools.nbm also selects core_fr.nbm
Summary: Trying to download jellytools.nbm also selects core_fr.nbm
Status: RESOLVED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-17 11:46 UTC by Jesse Glick
Modified: 2004-12-21 17:37 UTC (History)
1 user (show)

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 Jesse Glick 2003-11-17 11:46:59 UTC
I am using a dev build w/

org.netbeans.core.windows/2 [2.0 031116]

When I select the Test Tools module category on
dev alpha AU, it includes the expected modules
(XTest, JemmySupport, Test Tools, JellyTools, and
Jemmy) but also Core - Windows (fr)!

Why? Probably because jellytools and testtools
have a dep on o.n.c.windows/1, and translatedfiles
still includes localizations for /1. (Which I will
file separately.)

But AU should know that I already have
o.n.c.windows/2 and thus I cannot download these
modules at all - adding o.n.c.windows/1 would only
cause a conflict. They should be treated as
modules with unsatisfiable dependencies.

Cf.

www/www/updates/alpha/dev_1.6_.xml
Comment 1 Jesse Glick 2003-11-17 11:55:05 UTC
See also issue #37272, issue #37273, issue #37274.
Comment 2 Jesse Glick 2003-11-20 18:20:22 UTC
With issue #37273 fixed, less important.
Comment 3 Marian Mirilovic 2003-12-01 10:48:43 UTC
reassigne to Jirka - new owner of autoupdate
Comment 4 Jiri Rechtacek 2003-12-12 16:58:44 UTC
will be investigated and fixed in 3.6
Comment 5 Marian Mirilovic 2004-12-21 09:46:22 UTC
I guess this won't be fixed for NB4.0 , please evaluate again.
Comment 6 Jiri Rechtacek 2004-12-21 16:25:30 UTC
I don't know what should be fixed in AU module. It's not reproducible
with current active catalogs nor with alpha/1.6 catalog. Close as
worksforme.
Comment 7 Jesse Glick 2004-12-21 17:37:39 UTC
I'm sure it's not reproducible with current catalogs because the bug
was triggered by a certain circumstance which I described in the
original report. If necessary you can retrieve the update XML file
from CVS history with that timestamp.

Generally, I think AU is not written correctly to handle major release
versions, and there are surely various bugs in this area. I do not
know of any unit tests which check this kind of behavior, so it is
quite likely broken.