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.
[build: 200501241900] 1. Create new project from blueprints solutions 2. Build this project 3. go to files tab => you can see ${build.ear.classes.dir} directory
Bug, yes, and should be fixed for FCS but I would ask why a P2 bug? What is the customer impact other that a cosmetic ui folder name?
it's related to a missing properties in project properties. I haven't tried yet, but I guess that such a webmodule is not able to be built correctly as a part of an ear archive. I will handle it.
P2 it is because: - all examples from BP catalog are affected by this - as Marek mentioned: if user add some of these examples to enterprise application, this enterprise application can't be successfully built (steps to reproduce: 1. create new cdcatalog project (Samples | Blueprints | Web Tier... -> Displaying and Navigating ...) 2. create new empty Enterprise app 3. add cdcatalog project to that enterprise app 4. build whole enterprise app => build failed )
Created attachment 19958 [details] output window
Property ${build.ear.web.dir} is uninitialized too.
This requires adding some properties into blueprints catalog project files.
fix for Beta? should not be hard to modify the catalog and add this missing entry (s?) in project.properties file for each catalog project.
[20050208] already fixed - the missing properties are now present in bluprints examples bundled with netbeans. nb project files (https://bpcatalog.dev.java.net/source/browse/bpcatalog/tools/netbeans-module/resources/) has already been updated and zipped in j2ee/external/blueprints-solutions-catalog.zip
v. 200502142300