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 154486 - [codehaus] netbeans does not recognize generated webapp / resources folder
Summary: [codehaus] netbeans does not recognize generated webapp / resources folder
Status: RESOLVED DUPLICATE of bug 198650
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-03 15:48 UTC by Jaromir Uhrik
Modified: 2012-06-05 16:53 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jaromir Uhrik 2008-12-03 15:48:44 UTC
This issue was originally reported by Marcelo Romulo Fernandes in 16/Jul/08 at codehaus.org - see more details at
http://jira.codehaus.org/browse/MEVENIDE-650
Environment: windows xp sp2 jdk sun 1.6.0_07 netbeans 6.1 mevenide2 3.1

===========
Description:
===========
Mevenide recognizes generated sources directory at target/generated-sources/java and shows it at "netbeans project tab"
(it was discussed earlier at http://jira.codehaus.org/browse/MEVENIDE-561)
Why mevenide does not recognize generated webapp directory at target/generated-sources/webapp and generated resources
directory at target/generated-sources/resources in the same way?
If generated webapp directory is recognized, my application will "undestand" my generated faces-config.xml (jsf
descriptor) and open it or the backing bean when I "crtl" click my bean backing at facelets/jsp files.
Today, it works only if the faces-config.xml is located at default webapp folder.
Thanks in advance.
Comment 1 Milos Kleint 2009-01-03 12:20:12 UTC
the recognition of sources is only based on the target/generated-source folder location. To differenciate between
sources, resources, web resources, one had to be able to consult the pom file. But that's been impossible so far as the
information about generated source roots is not available statically and one has to perform a build to figure them out.
Comment 2 Antonin Nebuzelsky 2010-07-30 15:17:03 UTC
Reassigning to default owner.
Comment 3 Milos Kleint 2012-06-05 09:38:19 UTC

*** This bug has been marked as a duplicate of bug 198650 ***