[jbosstools-issues] [JBoss JIRA] (JBDS-3291) Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
Mustafa Musaji (JIRA)
issues at jboss.org
Tue Dec 16 05:17:29 EST 2014
[ https://issues.jboss.org/browse/JBDS-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027868#comment-13027868 ]
Mustafa Musaji edited comment on JBDS-3291 at 12/16/14 5:17 AM:
----------------------------------------------------------------
Hi Max
Okay so not as simple as I first thought. This is going to need some thought and I think this should be more of a helper dialogue perhaps as opposed to a wizard or automated thing. Because we have to consider the following:
* Not all modules are 1:1 with artifacts, as some modules include multiple maven artifacts (CXF for example)
* Some modules do not contain any artifacts, and simply re-export package paths of others
* Some modules have well-known names but varying implementations, e.g. javax.servlet.api where we could change the maven artifact
* APIs such as javax.servlet.api do not have an official maven name
* Not all modules export all classes in the jars they contain
Perhaps [~fbricon] can add his thoughts as I know he's done a lot of the maven work on JBoss Tools?
Do you think this is something that's possible that will add value? I think it will and many of our users creating projects on JBDS would find it useful.
We may have to put a RFE for EAP to add some additional metadata for the modules somewhere for us to use?
Mus
was (Author: mmusaji):
Hi Max
Okay so not as simple as I first thought. This is going to need some thought and I think this should be more of a helper dialogue perhaps as opposed to a wizard or automated thing. Because we have to consider the following:
* Not all modules are 1:1 with artifacts, as some modules include multiple maven artifacts (CXF for example)
* Some modules do not contain any artifacts, and simply re-export package paths of others
* Some modules have well-known names but varying implementations, e.g. javax.servlet.api where we could change the maven artifact
* APIs such as javax.servlet.api do not have an official maven name
* Not all modules export all classes in the jars they contain
Perhaps [~fbricon] can add his thoughts as I know he's done a lot of the maven work on JBoss Tools?
Do you think this is something that's possible that will add value?
Mus
> Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project
> ---------------------------------------------------------------------------------------------------
>
> Key: JBDS-3291
> URL: https://issues.jboss.org/browse/JBDS-3291
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: integration, server
> Affects Versions: 8.0.0.GA
> Reporter: Mustafa Musaji
> Assignee: Max Rydahl Andersen
>
> If you have a POM for a project that defines the following
> {code}
> <project>
> ...
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.bom</groupId>
> <artifactId>eap6-supported-artifacts</artifactId>
> <version>6.3.1.GA</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> </dependencies>
> </dependencyManagement>
> ...
> <dependencies>
> <dependency>
> <groupId>commons-beanutils</groupId>
> <artifactId>commons-beanutils</artifactId>
> <scope>provided</scope>
> </dependency>
> </dependencies>
> </project>
> {code}
> The tooling should create a jboss-deployment-structure.xml that contains the "org.apache.commons.beanutils" dependency automatically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jbosstools-issues
mailing list