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.
Need separate XSL templates for generating target content for build, deploy and debug (and possibly other) targets in build-impl.xsl for - Classic Library Projects w/ DEPLOY deployment strategy - Extension Library Projects w/ DEPLOY deployment strategy - Classic Library JARs w/ DEPLOY deployment strategy - Extension Library JARs w/ DEPLOY deployment strategy - Raw JARs w/ exp file + sig file w/ DEPLOY deployment strategy - Raw JARs w/ BUNDLE deployment strategy - Non-javacard projects with exp file + sig file w/ DEPLOY deployment strategy - Non-javacard projects w/ BUNDLE deployment strategy - Classic Library Projects w/ BUNDLE deployment strategy (?) - Extension Library Project w/ BUNDLE deployment strategy (?)
Started as of changeset 2230f4f7c9ab. We now have basic support for: - Unpacking JAR files into build.classes.dir - Building and deploying dependent projects before deploying the current project - Cleaning dependent projects Open issues: - If, in a Classic Library, I set a dependency on ant.jar with a deployment strategy of INCLUDE_IN_PROJECT_CLASSES, the build script unbundles it correctly - output is: Un-JAR-ing dependency ant.jar (type:RAW_JAR, deployment strategy INCLUDE_IN_PROJECT_CLASSES) Expanding: C:\apache-ant-1.7.1\lib\ant.jar into C:\Documents and Settings\Administrator\Local Settings\Temp\ClassicLibrary2\build however, in fact, the classes do not appear in the packaged .cap file, although the un-jaring happens before building. Either something is deleting and re-creating ${build.classes.dir}, or the packager is ignoring it, or something else. There are several problems with this: 1. The packager should be rejecting the classes as having the wrong magic number (49 for JDK-5 instead of 50 for JDK-6) 2. They should be in the resulting .cap file and are not 3. The packager (or something) should be rejecting a Classic project with multiple packages - There is currently no support (build fails) for deploying classic/extension library jar files (no associated project). Need instructions on what the Ant calls for this should look like.
*** Issue 170643 has been marked as a duplicate of this issue. ***