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: | [codehaus] Support for filtering Java sources | ||
---|---|---|---|
Product: | projects | Reporter: | Jaromir Uhrik <juhrik> |
Component: | Maven | Assignee: | Milos Kleint <mkleint> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jaromir Uhrik
2008-12-03 15:44:04 UTC
not to be addressed any time soon, considered to be a corner case. resolving later NetBeans.org Migration: changing resolution from LATER to WONTFIX Consider reopening and addressing this scenario. Daniel's legitimate scenario with a second generate-sources step: src/main/java/<source templates> --generate-sources--> target/filteredsrc/main/java/<filtered sources> --generate-sources--> target/generated-sources/java/<final source to be compiled> As a developer which files would you edit? Wait. Instead let us ask, which files would you NOT want to edit? You would NOT want to edit the target/filteredsrc files or the target/generated-sources files because NetBeans will clobber any changes you make the next time you build. Yet, by hiding the source templates in src/main/java and showing the filtered and final sources in the project tree, NetBeans encourages a developer in this scenario to do just that. In this case, NetBeans should show the source templates because those are the files that the developer should edit. (Another legitimate use case for Daniel's setup, by the way, is if you want to use a dynamic string in an annotation value: a version number, for example.) (Also, the filtered and generated source files should be read-only by default, but they are editable by default.) v7.3 RC1 |