Bug 295700

Comment 1 Neil Mising name 2009-11-20 14:01:12 EST

(In reply to comment #0)

Sun Java 1.7 is on the computers with XP and W7.
Sun Java 1.6 is on the computer with Vista.

Comment 2 Walter Harley 2009-11-20 14:21:45 EST

I'm sorry to hear you're having such problems.  However, I don't think they have anything to do with the Java Development Tooling (JDT) project, Annotation Processing Tooling (APT) component, which is how you categorized this bug.  I'm afraid that the JDT/APT team doesn't have any way of helping in this case.

Since this is clearly either a transient situation or something to do with your machine or network configuration (or else Eclipse would never have made it past version 3.5), could you post your question to one of the Eclipse newsgroups or IRC channels?  You're more likely to get timely and helpful support there.

Comment 3 Neil Mising name 2009-11-22 05:49:58 EST

Regarding your comment and closing #295700

As far as JDT or APT when filing the bug the site said something like if
you don't know just guess.  If this should have been somewhere else it
could have been transferred.

As far as "...this is clearly either a transient situation or something to
do with your machine or network configuration ..."
This is not a "transient situation" nor is it a problem the "machine"
(this was tried on 3 different machines, this was in the original comment
when the bug was filed) nor the "network configuration" (booting into
Ubuntu 9.10 it works OK).

The problem appears to be with Windows.  If most of the devs at Eclipse
are using Linux to be consistent a Windows problem may be overlooked.

Doing a search for "tampered" brought up about 14 that are still open:
287099, 258859, 263298, 293521, 216684, 255518, 198950, 272051, 293528,
257706, 278260, 236360, 231204 and

290648         nor         P3         Linu         webtools.releng-inbox@eclip...         REOP                 Eclipse
3.5.1 cannot install web development tools
Moving to releng

290648 was reopened and moved to releng, whatever that is.
290648 was on Linux.

Since 295700 was specific to Windows and not Linux 290648 may be a
different issue.

Perhaps you should consider reopening 295700 and moving it to "releng" or
wherever it would be appropriate.

I did some reading on some of the other bugs and nested signed jars could
be a problem.  Also under Windows sometime files that are downloaded are
given the date when downloaded and might conflict with the date the jar
was made.

Thanks
Neil

Comment 4 Walter Harley 2009-11-22 17:23:05 EST

(In reply to comment #3)
> As far as "...this is clearly either a transient situation or something to
> do with your machine or network configuration ..."
> This is not a "transient situation" nor is it a problem the "machine"
> (this was tried on 3 different machines, this was in the original comment
> when the bug was filed) nor the "network configuration" (booting into
> Ubuntu 9.10 it works OK).

The information that it works when booting into Ubuntu was not in your earlier report.  Based on the information you provided, it is easy for me to believe that either (a) your experiments were all close in time and you happened to be hitting some transient problem with the Eclipse web server, or else (b) your different Windows-based operating systems all shared some problematic configuration feature.  BTW, you did not state that the operating systems were on different physical machines.


> The problem appears to be with Windows.  If most of the devs at Eclipse
> are using Linux to be consistent a Windows problem may be overlooked.

Actually, the vast majority of Eclipse devs use Windows.  But additionally, there are tens or hundreds of thousands of developers using Eclipse regularly.  Something as basic as Help -> Install New Software cannot be broken for all users as badly as you describe, without escaping early notice.  Thus, it seems reasonable to suppose that the problem is being exposed by some subtlety of your configuration or system.


> Perhaps you should consider reopening 295700 and moving it to "releng" or
> wherever it would be appropriate.

"releng" is the Eclipse release engineering team, that is, the team responsible for maintaining the build process.

Regarding reopening the bug: you can do that better than I.  Eclipse is an open-source community project.  I don't work for Eclipse; I'm a part-time volunteer who maintains one very small component of the Eclipse Java compiler (JDT/APT).  When bugs come my way and it's clear that the reporter made a reasonable effort at categorization I'm happy to fine-tune, but when they're totally unrelated I don't have the time or energy to do all the work myself.  I closed this bug because it didn't have anything remotely to do with JDT/APT and it seemed unlikely that pursuing it in Bugzilla was your best hope of getting an answer; instead I suggested what seemed like better approaches.  If you disagree, please feel free to reopen and recategorize it as you see fit.


Taking a step back, you might want to consider downloading the J2EE version of Eclipse from the get-go, rather than downloading a more minimal version and then using Help -> Install New Software to get the features you're looking for.  Just a different idea to try, to see if it works around whatever is causing your problem.