[JBoss JIRA] (JBTIS-27) migrate soa/brms tooling tests from jbosstools-integration-tests to new repo jbosstools-integration-stack-itests
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-27?page=com.atlassian.jira.plugin.s... ]
Andrej Podhradsky closed JBTIS-27.
----------------------------------
Done a long time ago... so I'm closing this issue
> migrate soa/brms tooling tests from jbosstools-integration-tests to new repo jbosstools-integration-stack-itests
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-27
> URL: https://issues.jboss.org/browse/JBTIS-27
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, testing
> Affects Versions: 4.0.0
> Reporter: Nick Boldt
> Assignee: Andrej Podhradsky
> Fix For: 4.1.3.Final
>
>
> Currently, we have 3 update sites being built which include tests, from various repos.
> The most notable of these is jbosstools-integration-tests, which includes UI and integration tests (and framework code) for both the core and (JBT) the SOA/BRMS (JBTIS) projects. Additionally, the individual JBT and JBTIS project also publish test features/plugins to their respective update sites.
> These test features are then composited, then aggregated into these sites:
> http://download.jboss.org/jbosstools/updates/nightly/coretests/
> http://download.jboss.org/jbosstools/updates/nightly/soatests/
> http://download.jboss.org/jbosstools/updates/nightly/integrationtests/
> Unfortunately, because of conflicting dependencies and version levels (soa is still on Juno, whereas core is on Kepler) not all tests can run against a single target platform/stack.
> Therefore, I propose we move the SOA/BRMS (JBTIS) tests into a new github repo:
> *jbosstools-integration-stack-itests*
> This would allow those tests to be build/run/published against the upstream JBTIS target platform and projects' test code, as well as incorporating shared code from the upstream core projects' tests (and framework code) published here:
> http://download.jboss.org/jbosstools/updates/nightly/coretests/4.0.juno/
> New update sites would presumably be here:
> http://download.jboss.org/jbosstools/updates/nightly/integration-stack/ (need to migrate the build code and refactor the destination folder - see JBTIS-28)
> http://download.jboss.org/jbosstools/updates/nightly/integration-stack-it...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-25) SwitchYard 0.5.0 requires Guvnor 5.4, but 5.3 is on the 3.3.x nightly site
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-25?page=com.atlassian.jira.plugin.s... ]
Andrej Podhradsky closed JBTIS-25.
----------------------------------
Closed as outdated
> SwitchYard 0.5.0 requires Guvnor 5.4, but 5.3 is on the 3.3.x nightly site
> --------------------------------------------------------------------------
>
> Key: JBTIS-25
> URL: https://issues.jboss.org/browse/JBTIS-25
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: switchyard
> Reporter: Nick Boldt
> Assignee: Rob Cernich
> Fix For: 4.0.0
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> (2012-05-31 11:49:50) nboldt: rcernich: can you install your stuff into a clean eclipse instance from here? http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/3.3.x.Ni...
> (2012-05-31 11:50:19) nboldt: rcernich: contains SY 0.5.0.v20120530-0222-H91-CI
> (2012-05-31 11:50:41) nboldt: should be able to resolve ALL your upstream needs, from eclipse.org, m2e, jboss.org, etc.
> (2012-05-31 11:50:12) rcernich: nboldt: pretty sure
> (2012-05-31 11:50:42) rcernich: nboldt: dependencies are mostly limited to m2e, emf, wtp
> (2012-05-31 11:50:57) rcernich: nboldt: jboss m2e is optional
> (2012-05-31 11:51:16) rcernich: nboldt: we have some features waiting in the wings for guvnor integration
> (2012-05-31 11:51:26) rcernich: nboldt: but that requires guvnor 5.4 tools
> (2012-05-31 12:33:50) nboldt: rcernich: looks like we're pulling 5.3.2 into SOA Tooling https://hudson.qa.jboss.com/hudson/view/SOA-Team/view/SOATools-3.3.0/job/...
> (2012-05-31 12:35:16) nboldt: if you need 5.4 droolsjbpm stuff in soa tooling site so it's available when installing switchyard 0.5.0, then ... this is a problem and you need to get Doug on it.
> (2012-05-31 12:36:15) nboldt: https://repository.jboss.org/nexus/content/groups/public/org/drools/org.d... is out
> If I understand the issue, you want to include SY 0.5.0 in SOATools 3.3.0.Beta3, but that requires Guvnor 5.4.0.Final, which is not as yet being aggregated.
> Integrate http://download.jboss.org/drools/release/5.4.0.Final/org.drools.updatesite/ into the staging composite site [1] for SOA Tooling 3.3.x.Nightly instead of the 5.3.2 bits.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-29) Migrate runtime detection plugins for SOA Tooling to their respective projects
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-29?page=com.atlassian.jira.plugin.s... ]
Andrej Podhradsky closed JBTIS-29.
----------------------------------
Done a long time ago... I'm closing this issue
> Migrate runtime detection plugins for SOA Tooling to their respective projects
> ------------------------------------------------------------------------------
>
> Key: JBTIS-29
> URL: https://issues.jboss.org/browse/JBTIS-29
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, drools/ jBPM, ESB, jBPM3, releng, runtime-soa
> Affects Versions: 4.0.0
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Fix For: 4.0.0
>
>
> You'll no doubt want a new feature wrapper for each of these plugins, as they'll need to be installable from their respective projects' sites:
> * org.jboss.tools.runtime.drools.detector
> * org.jboss.tools.runtime.esb.detector
> * org.jboss.tools.runtime.jbpm.detector
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21134) Move easymport plugins from playground component
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21134?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21134:
----------------------------------------
Only org.jboss.tools.easymport.jee bundle content are to be moved. One will probably go to jee-tools (servlet project detector), another to datatools (JPA project detector) and the other one to webservices (jax-rs project detector).
> Move easymport plugins from playground component
> ------------------------------------------------
>
> Key: JBIDE-21134
> URL: https://issues.jboss.org/browse/JBIDE-21134
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: easymport
> Affects Versions: 4.4.0.Alpha1
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Fix For: 4.4.0.Alpha2
>
>
> Easymport is in the default installation of JBDS so it might be time to move it from playground component?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months