[
https://jira.jboss.org/jira/browse/JBRULES-1733?page=com.atlassian.jira.p...
]
Faron Dutton commented on JBRULES-1733:
---------------------------------------
Every system is different, which is the point of this issue. Setting the execution
environment in Eclipse just states that the project requires a version of the JDK at or
above the specified value. For example, specifying J2SE-1.5 informs Eclipse that the
compiler must be set to produce either 1.5 or 1.6 (currently) bytecode and that the
requisite libraries must be available. It does not say where these libraries must reside
and it does not fail if the user chooses something different from the project's
developers. By not specifying the execution environment, you are saying that any will do.
This causes the project to fail is the user's default JRE is older that the one
needed, which is what happened to me. I usually keep my default set to J2SE-1.4 so that
the code I write is backward compatible and explicitly set the execution environment on
every project. I have a copy of each targeted J2SE environment for this purpose and for
testing.
Set execution environment in project's build path.
--------------------------------------------------
Key: JBRULES-1733
URL:
https://jira.jboss.org/jira/browse/JBRULES-1733
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: All
Affects Versions: FUTURE
Environment: Eclipse IDE
Reporter: Faron Dutton
Assignee: Kris Verlaenen
Priority: Minor
Currently, each Drools project relies on the default Eclipse JRE container, which varies
from one developer to another. Configuring the execution environment in a project's
classpath will remove the need for a developer to alter the classpath on checkout.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira