[jbosstools-issues] [JBoss JIRA] (JBIDE-13467) integration-tests site won't build after reractoring: "Missing requirement: org.jboss.tools.maven.configurators.tests 1.5.0.Alpha1-v20130124-1009-B213 requires 'bundle org.jboss.tools.maven.jpa 0.0.0' but it could not be found"

[Fred Bricon (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-13467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Bricon resolved JBIDE-13467.
---------------------------------

    Resolution: Done


Changing status to resolved as tests pass : https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_All/job/jbosstools-central_master/lastCompletedBuild/testReport/ 

The zest issue is irrelevant here and has its own JIRA : JBIDE-13594
                
> integration-tests site won't build after reractoring: "Missing requirement: org.jboss.tools.maven.configurators.tests 1.5.0.Alpha1-v20130124-1009-B213 requires 'bundle org.jboss.tools.maven.jpa 0.0.0' but it could not be found"
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13467
>                 URL: https://issues.jboss.org/browse/JBIDE-13467
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: testing
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Fred Bricon
>             Fix For: 4.1.0.Alpha1
>
>
> [ERROR]   Missing requirement: org.jboss.tools.maven.configurators.tests 1.5.0.Alpha1-v20130124-1009-B213 requires 'bundle org.jboss.tools.maven.jpa 0.0.0' but it could not be found
> Cause is JBIDE-13048 -- org.jboss.tools.maven.jpa is now org.eclipse.m2e.wtp.jpa.
> Will need to update tests to use new namespace.
> Note similar refactoring for jaxrs and jsf.

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