[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-8967) fetch drools upstream from nexus via maven & unpack into local update site

[Nick Boldt (JIRA)]

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

Nick Boldt resolved JBIDE-8967.
-------------------------------

    Resolution: Won't Fix


Can't remember the benefit to doing this. Current solution for getting upstream Drools works fine, so I'm closing this Won't Fix.

> fetch drools upstream from nexus via maven & unpack into local update site
> --------------------------------------------------------------------------
>
>                 Key: JBIDE-8967
>                 URL: https://issues.jboss.org/browse/JBIDE-8967
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>    Affects Versions: 3.3.0.M2
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 3.3.x
>
>
> Per sample in https://svn.devel.redhat.com/repos/jboss-soa/trunk/soa-p/pom.xml, we can now pull drools artifacts from https://repository.jboss.org/nexus/content/groups/public/org/drools/org.drools.updatesite/5.2.0-SNAPSHOT/ via maven dep resolution, unpack them to a local folder, composite them via a generated composite*.xml pair, and generate downstream update site using a purely maven solution (without shell hacks).
> This would also mean that nightly update sites would become maven artifacts for consumption, rather than pure p2 sites, bridging both worlds.
> In theory, anyway.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira