6:33 p.m.
Support distribution defining "New Project" dependencies
--------------------------------------------------------
Key: JBIDE-4727
URL: https://jira.jboss.org/jira/browse/JBIDE-4727
Project: JBoss Tools
Issue Type: Feature Request
Components: Seam
Reporter: Pete Muir
Summary:
Move the responsibility for defining a "New Seam Project"'s dependencies
(libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to
define the dependencies. Use Maven POM profiles to support different use cases for Seam
projects.
Reason:
Currently JBoss Tools defines the project dependencies which causes issues very time Seam
changes either the dependency set of a new seam project, or the layout of libraries in the
distribution. Use Maven 2 POM format as it is already a well defined and understood model.
Use of Maven POM profiles can further increase the flexibility and support various use
cases for Seam (for example, Seam with jBPM or Seam with ICEFaces).
Details:
JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml,
ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the
dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite
modules of an EAR project. The standard Maven scopes are used: compile to indicate
compile/runtime dependencies of the project, test to indicate extra dependencies required
in the test project.
Maven profiles are used to define additional dependency sets for new seam projects,
allowing the user to optionally add extra dependencies to his project. To make this
extensible, and not require JBossTools to use a well-known list of profile ids, an xml
namespace will be used to add additional metadata to the profile. This allows JBossTools
to identify the possible profiles:
<profile>
<id>drools5</id>
<jbt:profile>
<jbt:description>Drools 5 support (Tech Preview)</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
<profile>
<id>ICEFaces</id>
<jbt:profile>
<jbt:description>ICEFaces</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
JBossTools can recognize the jbt:profile element, and use the jbt:description element to
as a descriptive element to present to the user:
[x] ICEFaces
[x] Drools 5 support (Tech Preview)
displayed in the New Seam Project Wizard.
We should allow for additional information to be placed in the POM and in the future
beyond dependency information. For example, additional configuration files to include in
the generated project, however this is not a critical feature.
We should also consider allowing JBoss Tools to retrieve the POMs from a Maven repository.
This would require a user to simply specify the version of Seam they require, and have
JBoss Tools download the seam-gen artifact containing all templates and resources.
--
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
7:48 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4727) Support distribution defining "New Project" dependencies
[
https://jira.jboss.org/jira/browse/JBIDE-4727?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4727:
---------------------------------------
Fix Version/s: 3.1.0.M3
3.1.0.M4
Assignee: Snjezana Peco
Support distribution defining "New Project" dependencies
--------------------------------------------------------
Key: JBIDE-4727
URL: https://jira.jboss.org/jira/browse/JBIDE-4727
Project: JBoss Tools
Issue Type: Feature Request
Components: Seam
Reporter: Pete Muir
Assignee: Snjezana Peco
Fix For: 3.1.0.M3, 3.1.0.M4
Summary:
Move the responsibility for defining a "New Seam Project"'s dependencies
(libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to
define the dependencies. Use Maven POM profiles to support different use cases for Seam
projects.
Reason:
Currently JBoss Tools defines the project dependencies which causes issues very time Seam
changes either the dependency set of a new seam project, or the layout of libraries in the
distribution. Use Maven 2 POM format as it is already a well defined and understood model.
Use of Maven POM profiles can further increase the flexibility and support various use
cases for Seam (for example, Seam with jBPM or Seam with ICEFaces).
Details:
JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml,
ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the
dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite
modules of an EAR project. The standard Maven scopes are used: compile to indicate
compile/runtime dependencies of the project, test to indicate extra dependencies required
in the test project.
Maven profiles are used to define additional dependency sets for new seam projects,
allowing the user to optionally add extra dependencies to his project. To make this
extensible, and not require JBossTools to use a well-known list of profile ids, an xml
namespace will be used to add additional metadata to the profile. This allows JBossTools
to identify the possible profiles:
<profile>
<id>drools5</id>
<jbt:profile>
<jbt:description>Drools 5 support (Tech Preview)</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
<profile>
<id>ICEFaces</id>
<jbt:profile>
<jbt:description>ICEFaces</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
JBossTools can recognize the jbt:profile element, and use the jbt:description element to
as a descriptive element to present to the user:
[x] ICEFaces
[x] Drools 5 support (Tech Preview)
displayed in the New Seam Project Wizard.
We should allow for additional information to be placed in the POM and in the future
beyond dependency information. For example, additional configuration files to include in
the generated project, however this is not a critical feature.
We should also consider allowing JBoss Tools to retrieve the POMs from a Maven
repository. This would require a user to simply specify the version of Seam they require,
and have JBoss Tools download the seam-gen artifact containing all templates and
resources.
--
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
7:55 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4727) Support distribution defining "New Project" dependencies
[
https://jira.jboss.org/jira/browse/JBIDE-4727?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4727:
--------------------------------------------
ive added snjezana for the maven part and alexey/dgolovin for the seam-gen part since this
overlaps greatly.
Not sure if the xml namespace parts are easily accessible to us in the m2eclipse pom.xml
understanding.
Are alternative xml namespaces commonly used in pom.xml ?
If there is an ICEFaces profile there should be a Richfaces too, but they should be
mutually exclusive or?
Also to consider is how these will play together with other facets, i.e. drools,
hibernate, jsf, jpa etc. which also would somehow coordinate with these to avoid
duplications/overlap.
Support distribution defining "New Project" dependencies
--------------------------------------------------------
Key: JBIDE-4727
URL: https://jira.jboss.org/jira/browse/JBIDE-4727
Project: JBoss Tools
Issue Type: Feature Request
Components: Seam
Reporter: Pete Muir
Assignee: Snjezana Peco
Fix For: 3.1.0.M3, 3.1.0.M4
Summary:
Move the responsibility for defining a "New Seam Project"'s dependencies
(libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to
define the dependencies. Use Maven POM profiles to support different use cases for Seam
projects.
Reason:
Currently JBoss Tools defines the project dependencies which causes issues very time Seam
changes either the dependency set of a new seam project, or the layout of libraries in the
distribution. Use Maven 2 POM format as it is already a well defined and understood model.
Use of Maven POM profiles can further increase the flexibility and support various use
cases for Seam (for example, Seam with jBPM or Seam with ICEFaces).
Details:
JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml,
ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the
dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite
modules of an EAR project. The standard Maven scopes are used: compile to indicate
compile/runtime dependencies of the project, test to indicate extra dependencies required
in the test project.
Maven profiles are used to define additional dependency sets for new seam projects,
allowing the user to optionally add extra dependencies to his project. To make this
extensible, and not require JBossTools to use a well-known list of profile ids, an xml
namespace will be used to add additional metadata to the profile. This allows JBossTools
to identify the possible profiles:
<profile>
<id>drools5</id>
<jbt:profile>
<jbt:description>Drools 5 support (Tech Preview)</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
<profile>
<id>ICEFaces</id>
<jbt:profile>
<jbt:description>ICEFaces</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
JBossTools can recognize the jbt:profile element, and use the jbt:description element to
as a descriptive element to present to the user:
[x] ICEFaces
[x] Drools 5 support (Tech Preview)
displayed in the New Seam Project Wizard.
We should allow for additional information to be placed in the POM and in the future
beyond dependency information. For example, additional configuration files to include in
the generated project, however this is not a critical feature.
We should also consider allowing JBoss Tools to retrieve the POMs from a Maven
repository. This would require a user to simply specify the version of Seam they require,
and have JBoss Tools download the seam-gen artifact containing all templates and
resources.
--
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
8:05 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4727) Support distribution defining "New Project" dependencies
[
https://jira.jboss.org/jira/browse/JBIDE-4727?page=com.atlassian.jira.plu...
]
Pete Muir commented on JBIDE-4727:
----------------------------------
Not sure if the xml namespace parts are easily accessible to
us in the m2eclipse pom.xml understanding.
Yes, I thought this would be the case as you probably view the POM metamodel.
Are alternative xml namespaces commonly used in pom.xml ?
No. I guess this is a feature request we should take to the Maven guys (support in maven
POM metamodel). Like I said, this is a phase 2 feature :-) We can do it with hardcoded ids
to start with.
If there is an ICEFaces profile there should be a Richfaces too, but
they should be mutually exclusive or?
Yes, we would have to start to include this info over time. Again, a good reason to push
this idea to phase 2 (when we hard code the ids it's not a problem as we can include
this matrix in JBT)
Also to consider is how these will play together with other facets,
i.e. drools, hibernate, jsf, jpa etc. which also would somehow
coordinate with these to avoid duplications/overlap.
Not quite sure what this means, but if it means other projects should support new project
dependencies, then I agree this is a good idea.
Support distribution defining "New Project" dependencies
--------------------------------------------------------
Key: JBIDE-4727
URL: https://jira.jboss.org/jira/browse/JBIDE-4727
Project: JBoss Tools
Issue Type: Feature Request
Components: Seam
Reporter: Pete Muir
Assignee: Snjezana Peco
Fix For: 3.1.0.M3, 3.1.0.M4
Summary:
Move the responsibility for defining a "New Seam Project"'s dependencies
(libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to
define the dependencies. Use Maven POM profiles to support different use cases for Seam
projects.
Reason:
Currently JBoss Tools defines the project dependencies which causes issues very time Seam
changes either the dependency set of a new seam project, or the layout of libraries in the
distribution. Use Maven 2 POM format as it is already a well defined and understood model.
Use of Maven POM profiles can further increase the flexibility and support various use
cases for Seam (for example, Seam with jBPM or Seam with ICEFaces).
Details:
JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml,
ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the
dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite
modules of an EAR project. The standard Maven scopes are used: compile to indicate
compile/runtime dependencies of the project, test to indicate extra dependencies required
in the test project.
Maven profiles are used to define additional dependency sets for new seam projects,
allowing the user to optionally add extra dependencies to his project. To make this
extensible, and not require JBossTools to use a well-known list of profile ids, an xml
namespace will be used to add additional metadata to the profile. This allows JBossTools
to identify the possible profiles:
<profile>
<id>drools5</id>
<jbt:profile>
<jbt:description>Drools 5 support (Tech Preview)</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
<profile>
<id>ICEFaces</id>
<jbt:profile>
<jbt:description>ICEFaces</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
JBossTools can recognize the jbt:profile element, and use the jbt:description element to
as a descriptive element to present to the user:
[x] ICEFaces
[x] Drools 5 support (Tech Preview)
displayed in the New Seam Project Wizard.
We should allow for additional information to be placed in the POM and in the future
beyond dependency information. For example, additional configuration files to include in
the generated project, however this is not a critical feature.
We should also consider allowing JBoss Tools to retrieve the POMs from a Maven
repository. This would require a user to simply specify the version of Seam they require,
and have JBoss Tools download the seam-gen artifact containing all templates and
resources.
--
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
5:36 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4727) Support distribution defining "New Project" dependencies
[
https://jira.jboss.org/jira/browse/JBIDE-4727?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4727:
---------------------------------------
Fix Version/s: (was: 3.1.0.M3)
slip to next version.
Support distribution defining "New Project" dependencies
--------------------------------------------------------
Key: JBIDE-4727
URL: https://jira.jboss.org/jira/browse/JBIDE-4727
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam
Reporter: Pete Muir
Assignee: Snjezana Peco
Fix For: 3.1.0.M4
Summary:
Move the responsibility for defining a "New Seam Project"'s dependencies
(libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to
define the dependencies. Use Maven POM profiles to support different use cases for Seam
projects.
Reason:
Currently JBoss Tools defines the project dependencies which causes issues very time Seam
changes either the dependency set of a new seam project, or the layout of libraries in the
distribution. Use Maven 2 POM format as it is already a well defined and understood model.
Use of Maven POM profiles can further increase the flexibility and support various use
cases for Seam (for example, Seam with jBPM or Seam with ICEFaces).
Details:
JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml,
ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the
dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite
modules of an EAR project. The standard Maven scopes are used: compile to indicate
compile/runtime dependencies of the project, test to indicate extra dependencies required
in the test project.
Maven profiles are used to define additional dependency sets for new seam projects,
allowing the user to optionally add extra dependencies to his project. To make this
extensible, and not require JBossTools to use a well-known list of profile ids, an xml
namespace will be used to add additional metadata to the profile. This allows JBossTools
to identify the possible profiles:
<profile>
<id>drools5</id>
<jbt:profile>
<jbt:description>Drools 5 support (Tech Preview)</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
<profile>
<id>ICEFaces</id>
<jbt:profile>
<jbt:description>ICEFaces</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
JBossTools can recognize the jbt:profile element, and use the jbt:description element to
as a descriptive element to present to the user:
[x] ICEFaces
[x] Drools 5 support (Tech Preview)
displayed in the New Seam Project Wizard.
We should allow for additional information to be placed in the POM and in the future
beyond dependency information. For example, additional configuration files to include in
the generated project, however this is not a critical feature.
We should also consider allowing JBoss Tools to retrieve the POMs from a Maven
repository. This would require a user to simply specify the version of Seam they require,
and have JBoss Tools download the seam-gen artifact containing all templates and
resources.
--
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
6:31 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4727) Support distribution defining "New Project" dependencies
[
https://jira.jboss.org/jira/browse/JBIDE-4727?page=com.atlassian.jira.plu...
]
Denis Golovin updated JBIDE-4727:
---------------------------------
Fix Version/s: 3.1.0.CR1
(was: 3.1.0.M4)
Support distribution defining "New Project" dependencies
--------------------------------------------------------
Key: JBIDE-4727
URL: https://jira.jboss.org/jira/browse/JBIDE-4727
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam
Reporter: Pete Muir
Assignee: Snjezana Peco
Fix For: 3.1.0.CR1
Summary:
Move the responsibility for defining a "New Seam Project"'s dependencies
(libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to
define the dependencies. Use Maven POM profiles to support different use cases for Seam
projects.
Reason:
Currently JBoss Tools defines the project dependencies which causes issues very time Seam
changes either the dependency set of a new seam project, or the layout of libraries in the
distribution. Use Maven 2 POM format as it is already a well defined and understood model.
Use of Maven POM profiles can further increase the flexibility and support various use
cases for Seam (for example, Seam with jBPM or Seam with ICEFaces).
Details:
JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml,
ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the
dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite
modules of an EAR project. The standard Maven scopes are used: compile to indicate
compile/runtime dependencies of the project, test to indicate extra dependencies required
in the test project.
Maven profiles are used to define additional dependency sets for new seam projects,
allowing the user to optionally add extra dependencies to his project. To make this
extensible, and not require JBossTools to use a well-known list of profile ids, an xml
namespace will be used to add additional metadata to the profile. This allows JBossTools
to identify the possible profiles:
<profile>
<id>drools5</id>
<jbt:profile>
<jbt:description>Drools 5 support (Tech Preview)</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
<profile>
<id>ICEFaces</id>
<jbt:profile>
<jbt:description>ICEFaces</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
JBossTools can recognize the jbt:profile element, and use the jbt:description element to
as a descriptive element to present to the user:
[x] ICEFaces
[x] Drools 5 support (Tech Preview)
displayed in the New Seam Project Wizard.
We should allow for additional information to be placed in the POM and in the future
beyond dependency information. For example, additional configuration files to include in
the generated project, however this is not a critical feature.
We should also consider allowing JBoss Tools to retrieve the POMs from a Maven
repository. This would require a user to simply specify the version of Seam they require,
and have JBoss Tools download the seam-gen artifact containing all templates and
resources.
--
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
3:28 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4727) Support distribution defining "New Project" dependencies
[
https://jira.jboss.org/jira/browse/JBIDE-4727?page=com.atlassian.jira.plu...
]
Snjezana Peco updated JBIDE-4727:
---------------------------------
Fix Version/s: 3.1.0.GA
(was: 3.1.0.CR1)
Support distribution defining "New Project" dependencies
--------------------------------------------------------
Key: JBIDE-4727
URL: https://jira.jboss.org/jira/browse/JBIDE-4727
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam
Reporter: Pete Muir
Assignee: Snjezana Peco
Fix For: 3.1.0.GA
Summary:
Move the responsibility for defining a "New Seam Project"'s dependencies
(libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to
define the dependencies. Use Maven POM profiles to support different use cases for Seam
projects.
Reason:
Currently JBoss Tools defines the project dependencies which causes issues very time Seam
changes either the dependency set of a new seam project, or the layout of libraries in the
distribution. Use Maven 2 POM format as it is already a well defined and understood model.
Use of Maven POM profiles can further increase the flexibility and support various use
cases for Seam (for example, Seam with jBPM or Seam with ICEFaces).
Details:
JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml,
ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the
dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite
modules of an EAR project. The standard Maven scopes are used: compile to indicate
compile/runtime dependencies of the project, test to indicate extra dependencies required
in the test project.
Maven profiles are used to define additional dependency sets for new seam projects,
allowing the user to optionally add extra dependencies to his project. To make this
extensible, and not require JBossTools to use a well-known list of profile ids, an xml
namespace will be used to add additional metadata to the profile. This allows JBossTools
to identify the possible profiles:
<profile>
<id>drools5</id>
<jbt:profile>
<jbt:description>Drools 5 support (Tech Preview)</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
<profile>
<id>ICEFaces</id>
<jbt:profile>
<jbt:description>ICEFaces</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
JBossTools can recognize the jbt:profile element, and use the jbt:description element to
as a descriptive element to present to the user:
[x] ICEFaces
[x] Drools 5 support (Tech Preview)
displayed in the New Seam Project Wizard.
We should allow for additional information to be placed in the POM and in the future
beyond dependency information. For example, additional configuration files to include in
the generated project, however this is not a critical feature.
We should also consider allowing JBoss Tools to retrieve the POMs from a Maven
repository. This would require a user to simply specify the version of Seam they require,
and have JBoss Tools download the seam-gen artifact containing all templates and
resources.
--
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
7:43 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4727) Support distribution defining "New Project" dependencies
[
https://jira.jboss.org/jira/browse/JBIDE-4727?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4727:
---------------------------------------
Fix Version/s: 3.2.next
(was: 3.1.0.CR2)
not happening for GA.
Support distribution defining "New Project" dependencies
--------------------------------------------------------
Key: JBIDE-4727
URL: https://jira.jboss.org/jira/browse/JBIDE-4727
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam
Reporter: Pete Muir
Assignee: Snjezana Peco
Fix For: 3.2.next
Summary:
Move the responsibility for defining a "New Seam Project"'s dependencies
(libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to
define the dependencies. Use Maven POM profiles to support different use cases for Seam
projects.
Reason:
Currently JBoss Tools defines the project dependencies which causes issues very time Seam
changes either the dependency set of a new seam project, or the layout of libraries in the
distribution. Use Maven 2 POM format as it is already a well defined and understood model.
Use of Maven POM profiles can further increase the flexibility and support various use
cases for Seam (for example, Seam with jBPM or Seam with ICEFaces).
Details:
JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml,
ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the
dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite
modules of an EAR project. The standard Maven scopes are used: compile to indicate
compile/runtime dependencies of the project, test to indicate extra dependencies required
in the test project.
Maven profiles are used to define additional dependency sets for new seam projects,
allowing the user to optionally add extra dependencies to his project. To make this
extensible, and not require JBossTools to use a well-known list of profile ids, an xml
namespace will be used to add additional metadata to the profile. This allows JBossTools
to identify the possible profiles:
<profile>
<id>drools5</id>
<jbt:profile>
<jbt:description>Drools 5 support (Tech Preview)</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
<profile>
<id>ICEFaces</id>
<jbt:profile>
<jbt:description>ICEFaces</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
JBossTools can recognize the jbt:profile element, and use the jbt:description element to
as a descriptive element to present to the user:
[x] ICEFaces
[x] Drools 5 support (Tech Preview)
displayed in the New Seam Project Wizard.
We should allow for additional information to be placed in the POM and in the future
beyond dependency information. For example, additional configuration files to include in
the generated project, however this is not a critical feature.
We should also consider allowing JBoss Tools to retrieve the POMs from a Maven
repository. This would require a user to simply specify the version of Seam they require,
and have JBoss Tools download the seam-gen artifact containing all templates and
resources.
--
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
1:32 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4727) Support distribution defining "New Project" dependencies
[
https://issues.jboss.org/browse/JBIDE-4727?page=com.atlassian.jira.plugin...
]
Snjezana Peco updated JBIDE-4727:
---------------------------------
Fix Version/s: 3.3.x
(was: 3.2.x)
An upstream issue.
Support distribution defining "New Project" dependencies
--------------------------------------------------------
Key: JBIDE-4727
URL: https://issues.jboss.org/browse/JBIDE-4727
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam
Reporter: Pete Muir
Assignee: Snjezana Peco
Fix For: 3.3.x
Summary:
Move the responsibility for defining a "New Seam Project"'s dependencies
(libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to
define the dependencies. Use Maven POM profiles to support different use cases for Seam
projects.
Reason:
Currently JBoss Tools defines the project dependencies which causes issues very time Seam
changes either the dependency set of a new seam project, or the layout of libraries in the
distribution. Use Maven 2 POM format as it is already a well defined and understood model.
Use of Maven POM profiles can further increase the flexibility and support various use
cases for Seam (for example, Seam with jBPM or Seam with ICEFaces).
Details:
JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml,
ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the
dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite
modules of an EAR project. The standard Maven scopes are used: compile to indicate
compile/runtime dependencies of the project, test to indicate extra dependencies required
in the test project.
Maven profiles are used to define additional dependency sets for new seam projects,
allowing the user to optionally add extra dependencies to his project. To make this
extensible, and not require JBossTools to use a well-known list of profile ids, an xml
namespace will be used to add additional metadata to the profile. This allows JBossTools
to identify the possible profiles:
<profile>
<id>drools5</id>
<jbt:profile>
<jbt:description>Drools 5 support (Tech Preview)</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
<profile>
<id>ICEFaces</id>
<jbt:profile>
<jbt:description>ICEFaces</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
JBossTools can recognize the jbt:profile element, and use the jbt:description element to
as a descriptive element to present to the user:
[x] ICEFaces
[x] Drools 5 support (Tech Preview)
displayed in the New Seam Project Wizard.
We should allow for additional information to be placed in the POM and in the future
beyond dependency information. For example, additional configuration files to include in
the generated project, however this is not a critical feature.
We should also consider allowing JBoss Tools to retrieve the POMs from a Maven
repository. This would require a user to simply specify the version of Seam they require,
and have JBoss Tools download the seam-gen artifact containing all templates and
resources.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:43 a.m.
New subject: [JBoss JIRA] (JBIDE-4727) Support distribution defining "New Project" dependencies
[
https://issues.jboss.org/browse/JBIDE-4727?page=com.atlassian.jira.plugin...
]
Fred Bricon resolved JBIDE-4727.
--------------------------------
Resolution: Out of Date
Closing as out-of-date. "New XXX Project" functionality is based on maven
archetypes, where the required dependencies can be fine-tuned depending on the targeted
runtime (AS vs EAP), without needin to change the Maven POM semantics.
Support distribution defining "New Project" dependencies
--------------------------------------------------------
Key: JBIDE-4727
URL: https://issues.jboss.org/browse/JBIDE-4727
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam 2
Reporter: Pete Muir
Assignee: Fred Bricon
Fix For: 3.3.x
Summary:
Move the responsibility for defining a "New Seam Project"'s dependencies
(libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to
define the dependencies. Use Maven POM profiles to support different use cases for Seam
projects.
Reason:
Currently JBoss Tools defines the project dependencies which causes issues very time Seam
changes either the dependency set of a new seam project, or the layout of libraries in the
distribution. Use Maven 2 POM format as it is already a well defined and understood model.
Use of Maven POM profiles can further increase the flexibility and support various use
cases for Seam (for example, Seam with jBPM or Seam with ICEFaces).
Details:
JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml,
ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the
dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite
modules of an EAR project. The standard Maven scopes are used: compile to indicate
compile/runtime dependencies of the project, test to indicate extra dependencies required
in the test project.
Maven profiles are used to define additional dependency sets for new seam projects,
allowing the user to optionally add extra dependencies to his project. To make this
extensible, and not require JBossTools to use a well-known list of profile ids, an xml
namespace will be used to add additional metadata to the profile. This allows JBossTools
to identify the possible profiles:
<profile>
<id>drools5</id>
<jbt:profile>
<jbt:description>Drools 5 support (Tech Preview)</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
<profile>
<id>ICEFaces</id>
<jbt:profile>
<jbt:description>ICEFaces</jbt:description>
</jbt:profile>
<!--Standard Maven elements -->
</profile>
JBossTools can recognize the jbt:profile element, and use the jbt:description element to
as a descriptive element to present to the user:
[x] ICEFaces
[x] Drools 5 support (Tech Preview)
displayed in the New Seam Project Wizard.
We should allow for additional information to be placed in the POM and in the future
beyond dependency information. For example, additional configuration files to include in
the generated project, however this is not a critical feature.
We should also consider allowing JBoss Tools to retrieve the POMs from a Maven
repository. This would require a user to simply specify the version of Seam they require,
and have JBoss Tools download the seam-gen artifact containing all templates and
resources.
--
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
4226
days inactive
5393
days old
jbosstools-issues@lists.jboss.org
9 comments
5 participants
participants (5)
-
Denis Golovin (JIRA) -
Fred Bricon (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Pete Muir (JIRA)
-
Snjezana Peco (JIRA)