#1000434
  • Created on
    2011-06-08 07:52
  • Reported by
    Erwan Loisant
  • Status
    Fixed
  • Priority
    Low (4)
  • Assigned to
    Mirco Dotta
  • Milestone
    Helium
  • Plan Level
    -
  • Permission type
    None
  • Due Date
    -

Attachments

More than one dot in the filename cause the file to be seen as Java

OS: Ubuntu Linux 11.04
Eclipse: 3.6.2 (M20110210-1200)
Scala IDE: 2.0.0.201106012319-beta5-28-7dd4324

Steps to reproduce:
  • Create a new Scala project
  • Create a file named "a.b.scala"
=> The file is seen as a Java file, but should be seen as a Scala file.

This happen for any file with more than one dot in the filename; e.g. there will be no problem with a_b.scala but a.b.scala will not be recognized.
User picture
  on 2011-06-17 14:26 *
By Iulian Dragos
Priority changed from Normal (3) to Low (4)
User picture
  on 2011-06-17 14:26 *
By Iulian Dragos
Milestone set to 2.0
User picture
  on 2011-07-12 07:30 *
By Iulian Dragos
Component changed from Eclipse to JDT integration
User picture
  on 2011-07-21 09:29 *
By Mirco Dotta
Eclipse version changed from Helios to Helios
Assigned to changed from login to Mirco Dotta
User picture
  on 2011-07-21 09:29 *
By Mirco Dotta
Status changed from New to Accepted
User picture
  on 2011-07-22 21:40 *
By Mirco Dotta
I narrowed down this issue, it is actually a bug in AJDT equinox bundle (org.eclipse.contribution.weaving.jdt_2.1.3-*-1300.jar). The problem is that in the implementation of CompilationUnitProviderAspect.aj, `findExtension` looks for the first index of '.' (dot), not the last one. Therefore, naming a file X.Y.scala will prevent the IDE from opening the correct Scala editor because the wrong suffix is extracted from the file name (no scala editor is associated to Y.scala).

I opened a bug in the AJDT project, explaining the issue and it has immediately been fixed!
https://bugs.eclipse.org/bugs/show_bug.cgi?id=352871

Though, I'll have to see if we can integrate the fix immediately or we have to wait for their next release (2.1.4), as we might not want to depend on a development branch.
User picture
  on 2011-07-25 07:33 *
By Mirco Dotta
CompilationUnit is instantiated by PackageFragment#getCompilationUnit(String). If you need to debug, set a breakpoint on `new CompilationUnit(...)`.
User picture
  on 2011-07-28 10:13 *
By Mirco Dotta
I confirm that by using the latest AJDT build this bug is fixed. Though, I have to see how we can integrate it in our build process since this will affect the produced JDT Weaving package (and I'm not sure if there might be problem with Spring Weaving).
User picture
  on 2011-07-28 11:59 *
By Mirco Dotta
Priority changed from Low (4) to High (2)
User picture
  on 2011-09-18 22:06 *
By
Any sense when this fix will percolate through into the nightlies? play-scala application development in Eclipse is kind of dead in the water until then.
User picture
  on 2011-09-20 16:35 *
By Mirco Dotta
The issue with supporting Play! in Eclipse comes from ticket #1000495, which has no easy solution at the moment.
User picture
  on 2011-10-04 09:37 *
By Iulian Dragos
Priority changed from High (2) to Low (4)
User picture
  on 2011-10-27 14:44 *
By Iulian Dragos
Milestone changed from 2.0 to 2.1
User picture
  on 2012-01-11 15:43 *
By skyluc
Status changed from Accepted to Fixed
Marking as fixed.

The fix has been integrated in Scala IDE when fixing the weaving problems for #1000780.