openjdk team mailing list archive

[Bug Watch Updater <981037@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=789154.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2012-02-09T23:36:22+00:00 Mike wrote:

Description of problem:

The latest version of javac produces error messages that no longer
display the full path of the file containing the errors.  This means
that the error message no longer unambiguously identifies the offending
file as soon as there is a collision in the leaf file names in a java
project.

Version-Release number of selected component (if applicable):

java-1.6.0-openjdk-devel-1.6.0.0-63.1.11.fc16.*

How reproducible:

Always.

Steps to Reproduce:
1. mkdir tmp; echo "bar" > tmp/foo.java
2. javac tmp/foo.java
  
Actual results:

foo.java:1: reached end of file while parsing
bar
^
1 error

Expected results:

tmp/foo.java:1: reached end of file while parsing
bar
^
1 error

Additional info:

java-1.6.0-openjdk-devel-1.6.0.0-59.1.10.3.fc16.* produces the expected
result above, so for now, yum downgrade allows me to work around this
problem.  Not a long term solution of course.  A better workaround would
be if there is a command line option to restore the full path, but I was
unable to find any.

There are two reasons this is really a bug and not just a cosmetic
issue.

1. I have to deal with some medium-to-large Java projects where the leaf file names are far from unique.  Indeed there are some places where there is a directory containing subdirectories which in turn contain files with standardized identical names (50+ and growing of them).  The old error message unambiguously identified the broken file.  The new one leaves me guessing.
Changing the naming convention is outside my area of responsibility, its `other people's code'.

2. This kills any possibility for an editor to parse the error messages
and bring up the offending source/line.  Please understand that not
everybody uses eclipse!

IMHO the best solution to this problem is to revert the change.

See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638805

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/0

------------------------------------------------------------------------
On 2012-03-27T20:13:09+00:00 Deepak wrote:

Assigning to Pavel.

Pavel, I looked into the issue and it looks like it is being caused due to this patch:
http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2011-March/013178.html

Can you please take a look when you have time?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/1

------------------------------------------------------------------------
On 2012-03-28T12:51:26+00:00 Andrew wrote:

Hmmm, as I recall, that patch was introduced specifically to fix this
problem.  But indeed, testing with 1.11 suggests it doesn't.

I'll check if removing the patch makes HEAD's behave match 7.  If so,
I'll commit the change.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/2

------------------------------------------------------------------------
On 2012-03-28T16:34:55+00:00 Andrew wrote:

Indeed, removing the patch does give the same behaviour as in previous
releases, including not only 1.10, but 1.9 and 1.8.  I was under the
impression that this patch was added because 1.10 (to which it was going
to be backported, but seemingly never was) changed the behaviour,
compared to other releases.  But these results suggest not.

Let's see what Pavel has to say.  I think there was a TCK issue
involved, which may since have been excluded, so some of this may have
to happen internally.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/3

------------------------------------------------------------------------
On 2012-03-29T09:38:44+00:00 Andrew wrote:

For the benefit of public users, Pavel confirmed that the TCK issues
surrounding this patch have been resolved through other means so the
patch can be dropped.

Pavel, can you remove the patch from HEAD and the 1.11 branch?  I'll
approve on the mailing list.  Thanks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/4

------------------------------------------------------------------------
On 2012-03-29T12:02:05+00:00 Pavel wrote:

Of course, I'll do it. Thank you.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/5

------------------------------------------------------------------------
On 2012-03-29T14:20:02+00:00 Andrew wrote:

Thanks Pavel.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/6


** Changed in: openjdk-6 (Fedora)
       Status: Unknown => Fix Released

** Changed in: openjdk-6 (Fedora)
   Importance: Unknown => Medium

** Bug watch added: Debian Bug tracker #638805
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638805

-- 
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-6 in Ubuntu.
https://bugs.launchpad.net/bugs/981037

Title:
  The javac executable doesn't produce full paths for files on error

Status in openjdk-6 package in Ubuntu:
  Fix Released
Status in openjdk-6 source package in Precise:
  Fix Released
Status in openjdk-6 package in Fedora:
  Fix Released

Bug description:
  It's the exact same "bug" that's reported over here:
  https://bugzilla.redhat.com/show_bug.cgi?id=789154

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: openjdk-6-jdk 6b24-1.11.1-4ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0.1-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 13 21:23:39 2012
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openjdk-6
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/+subscriptions