[JBoss JIRA] (JBIDE-13435) remove uml2, zest & graphiti from JBT Juno and Kepler target platforms (move into JBTIS target platform(s)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13435?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13435:
----------------------------------
Release Notes Docs Status: Not Required
> remove uml2, zest & graphiti from JBT Juno and Kepler target platforms (move into JBTIS target platform(s)
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13435
> URL: https://issues.jboss.org/browse/JBIDE-13435
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
>
> {quote}
> UML2 4.0 is not in your TP, though if I recall correctly (and they haven't removed the requirement) Teiid Designer requires UML2. Should it be added to your TP? I suspect you're resolving that dependency because it's already included in the JBT target platform [5] ? If that's the case then I believe it should be removed from ours and added to yours instead.
> Graphiti 0.9 is in both your TP and the JBT one [5], yet I don't think anything in JBT requires it. It was most likely added to support something in the SOA-P/BRMS tooling space before you started having your own TP. It too should probably be removed from ours in favour of it being in yours - no need to be in both.
> {quote}
> -- [~nickboldt]
> {quote}
> You're correct about uml2 and teiid - we're currently loading that directly from our aggregate site.xml (along with zest needed by esb). I would assume those two would be better served in the base tp as well - I'll let Rob comment. {quote}
> -- [~pleacu]
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13550) Remove JBoss Maven JPA, JSF, JAX-RS features from the JBT4/JBDS6 update sites, installers
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13550?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13550:
----------------------------------
Release Notes Docs Status: Not Required
> Remove JBoss Maven JPA, JSF, JAX-RS features from the JBT4/JBDS6 update sites, installers
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-13550
> URL: https://issues.jboss.org/browse/JBIDE-13550
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: Build/Releng
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Labels: respin-a
> Fix For: 4.0.1.Final
>
>
> The JBoss Maven JPA, JSF, JAX-RS being migrated over m2e-wtp, the plugins and features have been removed from the git repo.
> We need to make sure the the JBT4/JBDS6 update sites, installers are curated as well.
> *Waiting on Juno SR2 release in a couple weeks*
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13537) Unable to create EAP6.1 server [4.0.1 maintenance]
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13537?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13537:
----------------------------------
Release Notes Docs Status: Not Yet Documented
Affects: Release Notes
> Unable to create EAP6.1 server [4.0.1 maintenance]
> ---------------------------------------------------
>
> Key: JBIDE-13537
> URL: https://issues.jboss.org/browse/JBIDE-13537
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers, runtime-detection
> Affects Versions: 4.1.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.0.1.Final
>
> Attachments: New Server Runtime Environment _002.png, New Server Runtime Environment _003.png
>
>
> EAP6.1 is detected via runtime detection but nothing happens when I click OK to create runtime. Also manually adding it through Runtime Enviroment -> add -> EAP6.x does not work.
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13577) refactor & clean up jbosstools-target-platforms repo
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13577?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13577:
----------------------------------
Release Notes Docs Status: Not Required
> refactor & clean up jbosstools-target-platforms repo
> ----------------------------------------------------
>
> Key: JBIDE-13577
> URL: https://issues.jboss.org/browse/JBIDE-13577
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.0.0.Final, 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.0.0.Final, 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2
>
>
> Rename branches as follows:
> 4.2.0 -> 4.20.x (currently contains 4.20.6)
> 4.2.1 -> 4.21.x (currently contains 4.21.4)
> (new) -> 4.22.x (soon will contain 4.22.0)
> 4.3.0 -> master (currently contains 4.30.3)
> Also, purge any large binaries that are causing the repo to be >50M in size.
> When Kepler R is released (Eclipse 4.3.0.Final) we can branch a 4.30.x branch and work on the new 4.31.x target platforms (Kepler SR1) in the master branch.
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13600) new mechanism for deciding automatically if JBT & JBDS aggregate jobs should fire
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13600?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13600:
----------------------------------
Release Notes Docs Status: Not Required
> new mechanism for deciding automatically if JBT & JBDS aggregate jobs should fire
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-13600
> URL: https://issues.jboss.org/browse/JBIDE-13600
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, updatesite
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2
>
>
> We need a series of jobs for 4.0.x, 4.1.x, and master which will:
> * install a comma-separated list of IUs (.feature.groups) from a composite site into a pre-existing Eclipse installation, then
> * diff whether the fresh installation differs from a previously cached install manifest (list of features/plugins)
> * if the install footprint is different from before, the composite site contains new content and we should fire a downstream job to produce a new aggregate site
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-13588) Openshift tools in JBT 4 require org.eclipse.egit.core [1.2.0, 2.3.0), but the version of EGit in Juno SR2 is 2.3.0.201302130906
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13588?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13588:
----------------------------------
Release Notes Docs Status: Not Required
> Openshift tools in JBT 4 require org.eclipse.egit.core [1.2.0,2.3.0), but the version of EGit in Juno SR2 is 2.3.0.201302130906
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13588
> URL: https://issues.jboss.org/browse/JBIDE-13588
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.1.Final
> Reporter: Nick Boldt
> Assignee: Andre Dietisheim
> Fix For: 4.0.1.Final
>
>
> Need to extend the upper bound in MANIFEST.MF and/or feature.xml files so Openshift tools in JBT 4 can depend on EGit <=2.3, not <2.3.
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stable_branch.component--openshift/116/console}
> [ERROR] Software being installed: org.jboss.tools.openshift.egit.test 2.4.0.qualifier
> [ERROR] Missing requirement: org.jboss.tools.openshift.egit.core 2.4.0.Final-v20130218-1429-B116 requires 'bundle org.eclipse.egit.core [1.2.0,2.3.0)' but it could not be found
> [ERROR] Cannot satisfy dependency: org.jboss.tools.openshift.egit.test 2.4.0.qualifier depends on: bundle org.jboss.tools.openshift.egit.core 1.0.0
> {code}
--
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
12 years, 8 months