[
https://issues.jboss.org/browse/JBDS-3291?page=com.atlassian.jira.plugin....
]
Fred Bricon commented on JBDS-3291:
-----------------------------------
Not sure what we can do there. Maybe we could, for each artifact id show a list of
potential candidate modules, base on the name, or list all if no matching can be done.
something vaguely similar to the dependency conversion mechanism
http://docs.jboss.org/tools/whatsnew/maven/maven-news-4.0.0.Beta1.html.
But admittedly, the whole thing is really fuzzy to me at this point
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)