-
Bug
-
Resolution: Done
-
Critical
-
3.3.0.Beta1-SOA
-
None
As discussed on today's call, it's time to move up from Drools 5.2 to something newer.
We pull Drools tooling from upstream:
https://repository.jboss.org/nexus/content/groups/public/org/drools/org.drools.updatesite/5.3.1.Final/
https://repository.jboss.org/nexus/content/groups/public/org/drools/org.drools.updatesite/5.4.0.Beta1/
via these jobs:
http://hudson.qa.jboss.com/hudson/job/jbosstools-drools-5.2_trunk/
http://hudson.qa.jboss.com/hudson/job/jbosstools-drools-5.2_stable_branch/
which publish to the staging area:
http://download.jboss.org/jbosstools/builds/staging/
Once there, it is composited into a site for JBoss Tools 3.3.trunk and 3.3.latest-stable-milestone:
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooling/trunk/
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooling/3.3.indigo/
Then, from the composite, we build the JBT aggregate update site:
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/soa-site/site.xml
And the JBDS site:
https://svn.jboss.org/repos/devstudio/trunk/product-soa/site/site.xml
- blocks
-
JBIDE-9727 Drools license terms could be consistent w/ rest of JBoss Tools - SOA Tooling site
-
- Resolved
-
- is blocked by
-
-
- Closed
-
