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.
Product Version: NetBeans IDE Dev (Build 200801160000) Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb) full installer cant deploy any sample Building jar: ....\SynchronousSample6\SynchronousSample6Application\dist\SynchronousSample6Application.zip run-jbi-deploy: ...\SynchronousSample6\SynchronousSample6Application\nbproject\build-impl.xml:211: null BUILD FAILED (total time: 0 seconds) looks like the problem is old OpenESB version
In NetBeans 6.1 (trunk) installers we now bundle GlassFish V2 UR1 (b09d) and Open ESB V2 Preview4 (openesb_as9_fcs, build 071210_2 (latestSDK) - the same that Java EE 5 SDK Update 4 bundles). We can also take OpenESB build from "main" (lives along with openesb_as9_fcs at the OpenESB builds storage system) - but its not clear what is the right build.
*** Issue 125399 has been marked as a duplicate of this issue. ***
Yes, this is caused by old version of OpenESB. According to Mark, http://nog.sfbay.sun.com/kits/openesb/main/latest/glassfish/ always has the current open-esb build plus GlassFish 9.1_01 b09d-fcs
jqian, really a wontfix issue?? I am a little bit surprised. Maybe I should just update the OpenESB to that version in NetBeans 6.1 installers? If I am not mistaken, this latest link points to the latest build, not the latest "stable" build.. I don`t think that using such build is OK in NetBeans milestones (upcoming 6.1M1) and even more so in 6.1 release. Is there a link to the latest stable build that is workable with the current trunk and GF V2 UR1 b09d?
needs to be fixed with correct openesb package
Jun, please re-direct this issue to installer team and point Dima the location of the right openesb package. Thanks.
Per Hong's request, reopen and change component to installer.
The fix has been integrated. Please check the trunk NetBeans builds (staring with 200801190000) ASAP, both NBI installers (any of Windows/Linux/ Solaris) and native mac (MacOSX). Now latest available builds of JBI core runtime and JBI components are taken. As the fix, we put the latest JBI core runtime to appserver dir and install it using the following command just before usual JBI components installation: java -jar <appserver-install-root>/jbi-core-installer.jar <appserver-install-root> install http://installer.netbeans.org/source/browse/installer/infra/build/build.xml?r1=1.95&r2=1.96 http://installer.netbeans.org/source/browse/installer/infra/build/products/openesb/build.properties?r1=1.14&r2=1.15 http://installer.netbeans.org/source/browse/installer/components/products/openesb/src/org/netbeans/installer/products/ openesb/Bundle.properties?r1=1.2&r2=1.4 http://installer.netbeans.org/source/browse/installer/components/products/openesb/src/org/netbeans/installer/products/ openesb/ConfigurationLogic.java?r1=1.7&r2=1.10 http://installer.netbeans.org/source/browse/installer/mac/build.sh?r1=1.14&r2=1.15 http://installer.netbeans.org/source/browse/installer/mac/build.xml?r1=1.42&r2=1.43 http://installer.netbeans.org/source/browse/installer/mac/openesb/build.xml?r1=1.3&r2=1.4 http://installer.netbeans.org/source/browse/installer/mac/openesb/pkg/scripts/postflight?r1=1.4&r2=1.6 (plus JBICORE_LOCATION has been added to run-mac-installer.sh)
verified on Build 200801222102