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.
Summary: | When freeform project classpath is edited via properties view it destroys paths containing properties | ||
---|---|---|---|
Product: | java | Reporter: | bwl <bwl> |
Component: | Freeform | Assignee: | jrojcek <jrojcek> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | Keywords: | UI |
Priority: | P4 | ||
Version: | 4.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
bwl
2005-01-13 23:26:57 UTC
If you have a hand-edited freeform project.xml, avoid using the GUI customizer for the areas you have edited by hand. Generally the GUI customizer (intentionally) supports only a subset of the capabilities of the project.xml syntax. I appreciate that, but in this case it seems to me that the GUI customizer is altering path elements that the user hasn't asked it to do anything to. Also, in a team situation it is highly unlikely that all team members would be aware of the detail of the implementation of a freeform project (i.e. that some parts can only be edited successfully by hand) - so it would be helpful if the customizer in some way indicated it to them. Maybe the classpath customizer should simply be disabled if the classpath contains any property values? Tomas, moving java project specific issues to you for now. Jano, what do you tkink about it? It is possible to design a UI to at least mark the classpath roots which contain properties. I am not sure by editing, UI for editing classpath root containing property will be probably very ugly. Should be addressed in the NetBeans 4.2. There are several complains about it. *** This issue has been marked as a duplicate of 50409 *** |