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.
Don't use hardcoded platform cluster name, use {nb.cluster.platform.dir) instead.
Vladimir, please make changes in Sierra and in NB trunk
The hardcoded clusters are at least in these files: ./bpel.samples/resources/BluePrint3/BluePrint3/build.xml ./bpel.samples/resources/BluePrint3/BluePrint3/nbproject/build-impl.xml ./bpel.samples/resources/BluePrint3/BluePrint3Application/build.xml ./bpel.samples/resources/BluePrint4/BluePrint4/build.xml ./bpel.samples/resources/BluePrint4/BluePrint4/nbproject/build-impl.xml ./bpel.samples/resources/BluePrint4/BluePrint4Application/build.xml ./bpel.samples/resources/TravelReservationService/TravelReservationServiceApplication/build.xml ./bpel.samples/resources/TravelReservationService/TravelReservationService/build.xml ./bpel.samples/resources/TravelReservationService/TravelReservationService/nbproject/build-impl.xml ./bpel.samples/resources/BluePrint1/BluePrint1Application/build.xml ./bpel.samples/resources/BluePrint1/BluePrint1/build.xml ./bpel.samples/resources/BluePrint1/BluePrint1/nbproject/build-impl.xml ./bpel.samples/resources/SynchronousSample/SynchronousSample/build.xml ./bpel.samples/resources/SynchronousSample/SynchronousSample/nbproject/build-impl.xml ./bpel.samples/resources/SynchronousSample/SynchronousSampleApplication/build.xml ./bpel.samples/resources/AsynchronousSample/AsynchronousSample/build.xml ./bpel.samples/resources/AsynchronousSample/AsynchronousSample/nbproject/build-impl.xml ./bpel.samples/resources/AsynchronousSample/AsynchronousSampleApplication/build.xml ./bpel.samples/resources/BluePrint5/BluePrint5Application/build.xml ./bpel.samples/resources/BluePrint5/BluePrint5/build.xml ./bpel.samples/resources/BluePrint5/BluePrint5/nbproject/build-impl.xml ./bpel.samples/resources/BluePrint2/BluePrint2Application/build.xml ./bpel.samples/resources/BluePrint2/BluePrint2/build.xml ./bpel.samples/resources/BluePrint2/BluePrint2/nbproject/build-impl.xml ./bpel.project/src/org/netbeans/modules/bpel/project/resources/build.xsl ./bpel.project/src/org/netbeans/modules/bpel/project/resources/build-impl.xsl
If I use {nb.cluster.platform.dir} or ${nb.cluster.platform.dir} instead of platform10 in SOA Synchronous sample (BPEL project: build.xml and build-impl.xml), and build it from *command line*, I get exception: Caused by: java.lang.NoClassDefFoundError: org/openide/util/LookupListener at o.n.m.bpel.project.anttasks.cli.CliBpelCatalogModel.collectCatalogXmlRecursively(CliBpelCatalogModel.java:177) at o.n.m.bpel.project.anttasks.cli.CliBpelCatalogModel.getModelSource(CliBpelCatalogModel.java:105) at o.n.m.bpel.project.anttasks.cli.CliBpelCatalogModel.getBPELModel(CliBpelCatalogModel.java:272) at o.n.m.bpel.project.anttasks.cli.CliValidateBpelProjectDelegate.validateFile(CliValidateBpelProjectDelegate.java:152) at o.n.m.bpel.project.anttasks.cli.CliValidateBpelProjectDelegate.processSourceDir(CliValidateBpelProjectDelegate.java:187) at o.n.m.bpel.project.anttasks.cli.CliValidateBpelProjectDelegate.processSourceDir(CliValidateBpelProjectDelegate.java:183) at o.n.m.bpel.project.anttasks.cli.CliValidateBpelProjectDelegate.execute(CliValidateBpelProjectDelegate.java:131) ... 21 more I guess, that ${nb.cluster.platform.dir) is not set, therefore LookupListener class from platform10 can not be found. jrechtacek, what is the best way to resolve it? Should we set a value as parameter in build script: ant -Dnb.cluster.platform.dir=platform10 Why hardcoded value platform10 is too bad? Why do you take care of platform10 only, not ide11, soa2, xml2?
SOA modules are not included into NetBeans 6.8, so it doesn't make sense to touch too old BPEL modules. Sierra build is based on NetBeans 6.7.1, where the cluster names are ide11, platform10 and all samples are up-to-date with them. No need changes in Sierra. I'm considering this issue as Won't fix.
I haven't changed platform10 -> platform11 yet, I'm changing it right now. I don't know a best way, anyway my goal is make a change-set when changing the cluster version as small as possible. The cluster version may change while each NB release and it's danger to hold old version in own scripts.
closed: see my last comment.
This issue is consider closed. Consistency with other cluster names is more critical.