[
https://issues.jboss.org/browse/FORGE-378?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on FORGE-378:
-------------------------------------------
I agree with [~agoncal] that it should be possible to control JAVAEE separately from
CONTAINER.
I kinda see it as CONTAINER will specify the defaults for things like JAVAEE if user have
not explicitly set it.
With respect to referencing JavaEE api's instead of Java EE BOM then that was at least
with Java EE 6 problematic since the referenced jars were incomplete thus making test runs
using these jars impossible.
This issue should be fixed in Java EE 7
(
http://developinjava.com/2013/06/java-ee-7-fixes-java-ee-6s-absent-code/) but still, some
of the spec jars require specific container content (i.e. JPA) thus something like using
JBoss BOM still are necessary.
Also reason for using BOM's is so you don't have to update all your projects
individual dependency versions and just use properties provided by the BOM.
Add "environments" as a first class construct
---------------------------------------------
Key: FORGE-378
URL:
https://issues.jboss.org/browse/FORGE-378
Project: Forge
Issue Type: Feature Request
Components: UI - Shell, Usability
Reporter: Pete Muir
For example:
{code}
set environment JBOSS_AS7 --version 7.1.0.Final
{code}
Where JBOSS_AS7 is a built in profile that contains necessary info on various versions of
JBoss AS 7.
For example, the persistence plugin could read from this, changing
{code}
persistence setup --provider HIBERNATE --container JBOSS_AS7
{code}
to
{code}
persistence setup
{code}
Or, when setting up CDI, this would remove the need to ask ask which API to use (always
use the Java EE BOM with JBoss AS), and as the metadata builds, remove the need to ask the
version of the spec BOM to use.
Lot's of other places where this could provide better defaulting, or remove the need
to ask questions.
This also seems fairly consistent with the Forge approach - good understanding of the
project in question.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira