Created attachment 78170 [details]
Example EJB project

David, please provide evaluation

Petr, are you aware of 'undeploy' task being added in 6.5? If no pass back to me and I will have a look. Thanks.

Which target do you use to build app?

I always run clean before a build hence the problem - seems be an issue with the clean target? If you manually clean,
you can build:

(alias:jbidev.gfesb):TravelReservationService/ReservationPartnerServices -> nbant clean dist
Buildfile: build.xml

-create-private-props:
     [echo] JBI/QE pre-init patch: generating
/Volumes/Work/qe/jdev/paths/jbidev/jbi/shasta/e2e/nb/TravelReservationService/ReservationPartnerServices/nbproject/private/private.properties

BUILD FAILED
/Volumes/Work/qe/jdev/paths/jbidev/jbi/shasta/e2e/nb/TravelReservationService/ReservationPartnerServices/nbproject/build-impl.xml:567:
Problem: failed to create task or type nbundeploy
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.


Total time: 0 seconds
(alias:jbidev.gfesb):TravelReservationService/ReservationPartnerServices -> rm -rf dist build && nbant dist
Buildfile: build.xml

-create-private-props:
     [echo] JBI/QE pre-init patch: generating
/Volumes/Work/qe/jdev/paths/jbidev/jbi/shasta/e2e/nb/TravelReservationService/ReservationPartnerServices/nbproject/private/private.properties

-pre-pre-compile:
    [mkdir] Created dir:
/Volumes/Work/qe/jdev/paths/jbidev/jbi/shasta/e2e/nb/TravelReservationService/ReservationPartnerServices/build/jar

-copy-meta-inf:
     [copy] Copying 10 files to
/Volumes/Work/qe/jdev/paths/jbidev/jbi/shasta/e2e/nb/TravelReservationService/ReservationPartnerServices/build/jar/META-INF

-do-compile:
    [javac] Compiling 11 source files to
/Volumes/Work/qe/jdev/paths/jbidev/jbi/shasta/e2e/nb/TravelReservationService/ReservationPartnerServices/build/jar
     [copy] Copying 6 files to
/Volumes/Work/qe/jdev/paths/jbidev/jbi/shasta/e2e/nb/TravelReservationService/ReservationPartnerServices/build/jar

-do-dist-without-manifest:
    [mkdir] Created dir:
/Volumes/Work/qe/jdev/paths/jbidev/jbi/shasta/e2e/nb/TravelReservationService/ReservationPartnerServices/dist
      [jar] Building jar:
/Volumes/Work/qe/jdev/paths/jbidev/jbi/shasta/e2e/nb/TravelReservationService/ReservationPartnerServices/dist/ReservationPartnerServices.jar

BUILD SUCCESSFUL
Total time: 1 second

Ian, David
what is nbant actually? I tested both from command line with ant and from the IDE - it works? Could it be configuration
issue? There is new nbundeploy however it obviosly works within IDE and in pure CL this won't be executed.

Thanks,
P.

nbant is a QE environment alias:

-> alias nbant
${netbeans_ant}
-> echo $netbeans_ant
/Volumes/Work/qe/jdev/paths/jbidev/jbi/cmn/tools/pkg/ant.170/bin/ant -noinput -logger
org.apache.tools.ant.NoBannerLogger
-Dnetbeans.home=/Volumes/Work/qe/gfesbv21/netbeans.app/Contents/Resources/netbeans/platform9
-Dnetbeans.user=/Volumes/Work/qe/netbeans/userdir.gfesbv21 -Dfrom.commandline=true -Dallow.build.with.error=false
-Djava.awt.headless=true

This issue seems only a command line problem and seems to be localized to the clean target. In command line mode, how
does the nbundeploy task get declared?

Ian, why do you set netbeans.home in your nbant? There is a nbundeploy task which is called from clean target and which
purpose is to undeploy app from app server before clean is called (to prevent issues that app server is locking some
files which clean consequently cannot remove). But this task should be run only when Ant is executed within NetBeans.
And whether Ant script is run within NetBeans is driven by presence of netbeans.home property. Removing that property
from your nbant should resolve your problems.

Hi Petr,

The netbeans.home property is required by other projects e.g. CompApp when running in command line mode e.g.

    <target name="-init-taskdefs" if="from.commandline">
        <path id="ant.task.classpath">
            <pathelement location="${soa.module.install.dir}/org-netbeans-modules-compapp-projects-jbi.jar"/>
            <pathelement location="${soa.module.install.dir}/org-netbeans-modules-compapp-manager-jbi.jar"/>
            <pathelement location="${soa.module.install.dir}/org-netbeans-soa-libs-xmlbeans.jar"/>
            <pathelement location="${soa.module.install.dir}/ext/jbi/jbi-admin-common.jar"/>
            <pathelement location="${soa.module.install.dir}/../ant/nblib/org-netbeans-modules-compapp-projects-jbi.jar"/>
            <pathelement location="${netbeans.home}/lib/org-openide-util.jar"/>
            <pathelement location="${netbeans.home}/lib/org-openide-modules.jar"/>
            <pathelement location="${netbeans.home}/modules/org-openide-options.jar"/>
            <pathelement location="${netbeans.home}/modules/org-openide-text.jar"/>
            <pathelement location="${netbeans.home}/modules/org-openide-loaders.jar"/>
            <pathelement location="${netbeans.home}/modules/org-openide-nodes.jar"/>
            <pathelement location="${netbeans.home}/modules/org-openide-dialogs.jar"/>
            <pathelement location="${netbeans.home}/core/org-openide-filesystems.jar"/>
            <pathelement location="${ide.module.install.dir}/ext/xerces-2.8.0.jar"/>
            <pathelement location="${ide.module.install.dir}/ext/xml-commons-dom-ranges-1.0.b2.jar"/>
            <pathelement location="${ide.module.install.dir}/org-netbeans-modules-xml-retriever.jar"/>
            <pathelement location="${ide.module.install.dir}/org-netbeans-modules-xml-schema-model.jar"/>
            <pathelement location="${ide.module.install.dir}/org-netbeans-modules-xml-wsdl-model.jar"/>
            <pathelement location="${ide.module.install.dir}/org-netbeans-modules-xml-xam.jar"/>
            <pathelement location="${ide.module.install.dir}/org-netbeans-modules-xml-text.jar"/>
            <pathelement location="${ide.module.install.dir}/org-netbeans-modules-editor.jar"/>
            <pathelement location="${ide.module.install.dir}/org-netbeans-modules-editor-lib.jar"/>
            <pathelement location="${ide.module.install.dir}/org-netbeans-modules-editor-util.jar"/>
            <pathelement location="${ide.module.install.dir}/org-netbeans-modules-projectapi.jar"/>
            <pathelement location="${ide.module.install.dir}/org-netbeans-modules-classfile.jar"/>
            <pathelement location="${ide.module.install.dir}/org-apache-xml-resolver.jar"/>
            <pathelement location="${xml.module.install.dir}/org-netbeans-modules-xml-wsdl-extensions.jar"/>
            <pathelement location="${ide.module.install.dir}/ext/jaxb/api/jaxb-api.jar"/>
            <pathelement location="${ide.module.install.dir}/ext/jaxb/jaxb-impl.jar"/>
            <pathelement location="${ide.module.install.dir}/ext/jaxb/activation.jar"/>
            <pathelement location="${enterprise.module.install.dir}/org-netbeans-modules-j2eeserver.jar"/>
            <pathelement location="${enterprise.module.install.dir}/ext/jsr88javax.jar"/>
        </path>

Without it, the taskdef fails.

Could we not make this change?

    <target name="undeploy-clean" depends="init" if="netbeans.home" unless="from.commandline">
        <nbundeploy failOnError="false" startServer="false"/>
    </target>

Would this work?

I'm not sure where the xml fragments come from, but perhaps this addition would help as well...

<pathelement location="${enterprise.module.install.dir}/../ant/nblib/org-netbeans-modules-j2ee-ant.jar"/>

unless="from.commandline" on undeploy-clean should work as well.

Or you could run your task conditionally to presence of task's class. Something like:

 <condition property="run-undeploy-clean">
   <available classname="org.netbeans.your.UndeployClass"/>
 </condition>

Since Ant 1.7 there is even condition "typefound" but I think we still supports Ant 1.6.5.

Just for record I'm adding bits from offline discussion:

Primary purpose of netbeans.home property is to distinguish whether Ant script is run from IDE or from command line and
that concept should stay as is. We should not further spread "from.commandline" property.

Suggested short term solutions: you are in control of your project type and build scripts so you should be able to alter
your build scripts and use different property than netbeans.home. There is no need to use exactly that property name,
right? That would be first thing I would explore and it should allow you to get rid of from.commandLine property as well.

Long term goal: build scripts generated by project type should never refer directly to jars in NB installation. They
should introduce a Java Library which should be added to project's classpath and that allows user to decide if they want
to use global version of the library from IDE or make sharable one which is stored alongside the project and stored in
VCS so that project is buildable from command line and works for any team member regardless of IDE they are using.

Problem with fixing EJB build script is that there are very likely other project types which would have to be fixed
accordingly and from that point of view it is not a good fix.

If above suggested solution does not work we will resume this discussion.

.

*** This issue has been marked as a duplicate of 162215 ***

Closing ...