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.
Deploying an ear project containing a ref to a java project will fail because "-run-deploy-am" target does not exist on the java project. This bug is the result of the enhancement made to the ear project build script to allow deployment of the am configuration data contained in a web or ejb module. However, the logic in the enhance build script fails to filter out the java project which does not have the "-run-deploy-am" target in its build script. Note that we do currently filter out appclient module. To fix this, instead of trying to filter out non-web or non-ejb project, the logic should be to only invoke the -run-deploy-am target if the project is either web or ejb.
This is a showstopper because users can no longer deploy an ear project containing ref to java projects.
Moving the issue to j2ee because it is a bug in the ear project.
Changes checked in to trunk: Checking in build-impl.xsl; /cvs/j2ee/earproject/src/org/netbeans/modules/j2ee/earproject/resources/build-impl.xsl,v <-- build-impl.xsl new revision: 1.22; previous revision: 1.21 done Diffs: Index: build-impl.xsl =================================================================== RCS file: /cvs/j2ee/earproject/src/org/netbeans/modules/j2ee/earproject/resource s/build-impl.xsl,v retrieving revision 1.21 retrieving revision 1.22 diff -r1.21 -r1.22 746c746 < <xsl:for-each select="$references/projdeps:reference[not(projdeps:id=' j2ee-module-car')]"> --- > <xsl:for-each select="$references/projdeps:reference[(projdeps:id='dis t-ear') or (projdeps:id='j2ee-module-car')]">
Yes, inclusion of web,ejb and appclient projects look good. The appclient changes become valid only if, as pointed out, dependent issue's fix gets addressed. Otherwise the change will be only for web and ejb project support.
Reviewed and agreed.
Fix checked into release551 branch.