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

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBTIS-102 at 7/8/13 6:17 PM:
----------------------------------------------------------

When I install FuseIDE from https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/SOA-Team/view/Fuse_6/job/Fuse-Tooling/42/artifact/sources/site/target/org.fusesource.ide.updatesite-7.2.0-SNAPSHOT.zip I end up with all 11 of those plugins on disk, because they're already included the update site.

Therefore if you wanted them in a JBTIS TP site, you could build an update site that contains only those 11 plugins (using a category.xml which lists <bundle>s instead of <feature>s) and then point your TP at that site. (Ref: http://fusesource.com/issues/browse/ECLIPSE-941)

We could consider hosting them (and their sources) in Locus but it seems duplicative when we can just generate an update site using upstream Maven deps.

Here's how to pull a maven dep into a p2 update site: https://github.com/jbosstools/jbosstools-locus/pull/13

The magic is here:

{code:title=https://github.com/jbosstools/jbosstools-locus/pull/13/files#L1R30}
 +          <pomDependencies>consider</pomDependencies> 
{code}

Note that for the case of org.apache.servicemix.bundles.aopalliance 1.0_3, it's trivial to add the bundle.

For org.apache.aries.blueprint, many <dependency> jars are needed. If you guys like this approach, then I'd ask [~pleacu] to do some of the heavy lifting here, based on the above simple example pom.xml . category.xml changes.


                
      was (Author: nickboldt):
    When I install FuseIDE from https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/SOA-Team/view/Fuse_6/job/Fuse-Tooling/42/artifact/sources/site/target/org.fusesource.ide.updatesite-7.2.0-SNAPSHOT.zip I end up with all 11 of those plugins on disk, because they're already included the update site.

Therefore if you wanted them in a JBTIS TP site, you could build an update site that contains only those 11 plugins (using a category.xml which lists <bundle>s instead of <feature>s) and then point your TP at that site. (Ref: http://fusesource.com/issues/browse/ECLIPSE-941)

We could consider hosting them (and their sources) in Locus but it seems duplicative when we can just generate an update site using upstream Maven deps.




                  
> 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