[jbosstools-issues] [JBoss JIRA] (JBIDE-16998) Wrong bom version is shown at the last page of import wizard
Fred Bricon (JIRA)
issues at jboss.org
Thu Apr 3 08:59:13 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fred Bricon resolved JBIDE-16998.
---------------------------------
Resolution: Rejected
Last page shows the jboss-bom-enterprise version to use, when enterprise is set to true (i.e. if running on EAP)
You can check the gen'd pom contains the following comment :
{quote}
<version.jboss.bom>1.0.7.Final</version.jboss.bom>
<!-- Alternatively, comment out the above line, and un-comment the line
below to use version 1.0.4.Final-redhat-4 which is a release certified to
work with JBoss EAP 6. It requires you have access to the JBoss EAP 6
maven repository. -->
<!-- <version.jboss.bom>1.0.4.Final-redhat-4</version.jboss.bom>> -->
{quote}
> Wrong bom version is shown at the last page of import wizard
> ------------------------------------------------------------
>
> Key: JBIDE-16998
> URL: https://issues.jboss.org/browse/JBIDE-16998
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta1
> Reporter: Rastislav Wagner
> Priority: Minor
> Fix For: 4.2.0.Beta2
>
>
> When I'm importing central JavaEE6 project with AS7.1 as target runtime, wizard shows that 1.0.4.Final-redhat-4 jboss-bom will be used which is not true - for AS it should be jboss-bom 1.0.7.
> 1.0.7 is eventually used when you check pom.xml of imported project.
--
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
More information about the jbosstools-issues
mailing list