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 197368 - Add support of «Play! Framework» projects
Summary: Add support of «Play! Framework» projects
Status: NEW
Alias: None
Product: ide
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.0
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Assignee: issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-03 20:44 UTC by errandir
Modified: 2011-05-13 12:45 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
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 errandir 2011-04-03 20:44:35 UTC 
«Package does not exist» hint near import of empty package in free-form project.


Directory tree:

/app
  /package1
    Class1.java
  /package2


Class1.java

package package1;
import package2.*; // An error hint here
public class Class1 {}


Reproducing:

1. Install «Play! Framework»
2. Create new project (e.g. "$ play new NewApp")
3. Prepare for netbeans ("$ play netbeansify NewApp")
4. Open project in NetBeans
   Voilà...
Comment 1 Jan Lahoda 2011-04-05 08:25:36 UTC 
The command line compiler will produce the very same error message. Package is considered to be existent only if it contains at least one class. So sorry, but this is not a valid bug.
Comment 2 errandir 2011-04-05 18:49:14 UTC 
So, this is an issue of «Play! Framework», therefore there should be special handling or support of Play projects, because Play runs that code fine.
Comment 3 Tomas Zezula 2011-04-06 08:03:58 UTC 
Nothing in common with freeform project.

BTW according to  Java Language Specification the code in this issue is compiler error. It compiles probably because of a bug in ejc or someone generates some code into the empty package before it's compiled.

<cite>
7.4.3 Observability of a Package
A package is observable if and only if either:
A compilation unit containing a declaration of the package is observable.
A subpackage of the package is observable.

Also see section 7.4.1 of JLS
</cite>
Comment 4 Fyrespray 2011-05-13 12:45:46 UTC 
netbeansify configures the directory structure you are going to need to use for play.  All play projects will have models so the initial empty model packages will soon fill up with code and the red bars will go away.

Have to agree that it is not a bug.