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 - Run target configurations
Summary: Run target configurations
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker with 1 vote (vote)
Assignee: Tomas Zezula
Depends on:
Reported: 2008-11-02 15:20 UTC by jalexoid
Modified: 2011-08-31 14:08 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
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
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.