[jbosstools-issues] [JBoss JIRA] (JBIDE-12500) org.jboss.ide.eclipse.as.doc.user is not published on any update-site but is required by coretests site

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715053#comment-12715053 ] 

Martin Malina commented on JBIDE-12500:
---------------------------------------

This is quite inconvenient for our testing since we need recent builds of some of the plugins in the tests component. Right now we can work around this by building them locally every time.
                
> org.jboss.ide.eclipse.as.doc.user is not published on any update-site but is required by coretests site
> -------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-12500
>                 URL: https://issues.jboss.org/browse/JBIDE-12500
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>            Reporter: Mickael Istria
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 4.0.0.Alpha1
>
>
> When trying to build coretests site, we can see ( https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.coretests.aggregate/ ) that site cannot be built because it cannot resolve dependency from bundle  org.jboss.tools.as.test.core to bundle org.jboss.ide.eclipse.as.doc.user .
> Indeed, this org.jboss.ide.eclipse.as.doc.user bundle is not part of the AS update-site (that means it's not part of any of the feature published), so it it impossible for tests to resolve it while creating test site.
> It is working fine in the AS job since the bundle is available in the reactor.
> Fix is to add this org.jboss.ide.eclipse.as.doc.user bundle to a feature that is already published on as/site/category.xml .

--
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