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.

Bug 152155

Summary:	Run target configurations
Product:	java	Reporter:	jalexoid <jalexoid>
Component:	Project	Assignee:	Tomas Zezula <tzezula>
Status:	NEW ---
Severity:	blocker
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
URL:	http://jalexoid.blogspot.com/2008/11/netbeans-65-vs-eclipse-34-ganymede-on.html
Issue Type:	ENHANCEMENT	Exception Reporter:

Description jalexoid 2008-11-02 15:20:35 UTC

Custom run target creation in build.xml by means of a dialog.
Simple elements such as:
   - java executable location (if not default)
   - environment variables
   - Java VM parameters (-XX and standard params)
   - classpath
   - VM properties
   - Mail class
   - parameters

Overriding the default test target, to use other unit testing frameworks.


* Unfortunately aside from proposing some enhancements I am under contract obligations, that forbid me to contribute any
code.

Comment 1 jalexoid 2008-12-30 14:44:14 UTC

Out of the list below the features missing are:
   - java executable location (if not default)
   - environment variables
   - classpath (for adding/removing additional entries like entries in bootclasspath for a particular run configuration)

And still an issue with running non jUnit classes in Test packages folder.

Comment 2 Jesse Glick 2009-01-06 01:52:05 UTC

Should be possible to override JDK and run CP in a run configuration, though currently the GUI does not provide these
options. Environment variables for the spawned program could be easily supported in build-impl.xml too.