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 128346 - No clear indication how to fix a project with a non-shared server
Summary: No clear indication how to fix a project with a non-shared server
Status: VERIFIED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: Web Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Hejl
URL:
Keywords: USABILITY
Depends on:
Blocks:
 
Reported: 2008-02-25 19:22 UTC by Petr Jiricka
Modified: 2008-05-13 17:25 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 Petr Jiricka 2008-02-25 19:22:44 UTC
1. Create a web project with the following settings:
  Project shared with others: yes
  Use local server installation registered in the IDE
  Framework: Visual Web JavaServer Faces

2. Exit the IDE, delete the nbproject/private directory (to simulate sharing with other users)
3. Run ant from the command line from the project dir

=> Compilation errors appear complaining that:

javax.faces does not exist
    [javac] import javax.faces.FacesException;


The correct behavior is that Ant should display an intelligible error message explaining to the user how the project
properties file should be corrected so the project is buildable from the command line. 

Workaround: start NetBeans, open this project in NetBeans and let NetBeans create the private directory. However, this
workaround is not acceptable, as we want this scenario to work on a continuous build machine (which may not have
NetBeans installed) and on the machines of other developers on the team, who may not use NetBeans as their IDE.
Also, from the error message the user can not tell that starting NetBeans will help.
Comment 1 David Konecny 2008-02-25 21:43:19 UTC
petr, search web.project/build-impl.xml for "<fail if="platform.invalid">" for how this was resolved for J2SE platofrm.
Comment 2 Petr Hejl 2008-02-26 11:59:05 UTC
Fixed in changeset c5bc94cebdef.
Comment 3 Dan Kolar 2008-05-13 17:25:22 UTC
v.