[jbosstools-issues] [JBoss JIRA] (JBTIS-102) Need SpringFramework jars to build FUSE

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBTIS-102:
--------------------------------------

I think it makes total sense to use Locus in order to p2-ify some OSGi bundles (using trick from PR 13 with pomDependencies=consider and category.xml). The use-case is to replace dependency management in FuseIDE by a pure Target-Platform approach, and then remove it's Maven dependencies, so we shouldn't use FuseIDE repository to populate FuseIDE target-platform, FuseIDE should only have a target-platform, and consume Locus to get the various runtime bundles in a nice p2 way.

So +1 for moving all Spring Framework and Camel and so on jars to Locus (if they're not available as OSGi bundles from any other location).
                
> Need SpringFramework jars to build FUSE
> ---------------------------------------
>
>                 Key: JBTIS-102
>                 URL: https://issues.jboss.org/browse/JBTIS-102
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Fuse IDE, target-platform
>    Affects Versions: 4.1.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Paul Leacu
>
> [~pleacu] said:
> {quote}
> I'm attempting to get the fuseide to rely on jbosstools mirrors w/ real TP dependencies instead of including stuff on their own.  
> So - they include org.springframework plugins - I found 10 of them here:
>      http://download.jboss.org/jbosstools/updates/requirements/springide/3.2.0.201303060654-RELEASE/
> but I'm missing three:
>  
>  org.springframework.aspects
>  org.springframework.osgi.extender
>  org.springframework.osgi.extensions.annotations
> {quote}

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