We want our projects for debugging to have assertions on. Since
assertions are controlled at runtime and are off by default, this has
no effect on the performance of our customers' applications.
- Blake Sullivan
On Oct 11, 2009, at 10:05 PM, Maria Kaval wrote:
[Gary K] Default is "-ea" to enable assertions
[Maria] Do we want to enable assertions on by default? I would think
we want the defaults to be as performant as possible, but then
developers can turn on assertions if they wish. Is there a
guideline for what the default values should be?
Maria
-----Original Message-----
From: Gary Kind (JIRA) [mailto:d...@myfaces.apache.org]
Sent: Thursday, October 08, 2009 12:56 PM
To: dev@myfaces.apache.org
Subject: [jira] Created: (TRINIDAD-1590) maven-jdev-plugin: added
ability to set JVM Java Options. Default is "-ea" to enable assertions
maven-jdev-plugin: added ability to set JVM Java Options. Default is
"-ea" to enable assertions
-----------------------------------------------------------------------------------------------
Key: TRINIDAD-1590
URL: https://issues.apache.org/jira/browse/TRINIDAD-1590
Project: MyFaces Trinidad
Issue Type: New Feature
Affects Versions: 1.2.10-plugins
Reporter: Gary Kind
In Jdeveloper under Project Properties -> Run/Debug/Profile, edit a
selected profile and you will see a Java Options input text field to
the right of the selected JVM. An attribute has been added to the
maven-jdev-plugin to set these Java Options. Here is a sample of
how it would be set in a maven pom.xml file:
<plugin>
<groupId>org.apache.myfaces.trinidadbuild</groupId>
<artifactId>maven-jdev-plugin</artifactId>
<configuration>
<javaOptions>-ea</javaOptions>
<projectHasTests>${jdev.project.has.tests}</projectHasTests>
<testSourceRoots>
<file>${project.basedir}/src/test</file>
</testSourceRoots>
</configuration>
</plugin>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
