December 2014 - jbosstools-issues

[JBoss JIRA] (JBTIS-350) Missing BPEL source plugins

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-350?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-350: ----------------------------------------- If you install org.jboss.tools.bpel.feature you will get all bpel bundles (15), but if you install org.jboss.tools.bpel.source.feature you will get only org.jboss.tools.bpel.runtimes.source. This is quite useless feature. Note that all the other source features install appropriate source bundles. > Missing BPEL source plugins > --------------------------- > > Key: JBTIS-350 > URL: https://issues.jboss.org/browse/JBTIS-350 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > After installing all components included in Beta1 there are only the following souce plugins for BPEL > org.jboss.tools.bpel.runtimes.source_1.2.101.Final-v20140108-1353-B1045.jar > org.switchyard.tools.ui.bpel.source_2.0.0.v20141011-0508-H499-Alpha3.jar > but there are much more BPEL plugins such as > org.eclipse.bpel.ui, org.eclipse.bpel.ui.validator -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18692) Jenkins build for jbosstools-incubator-ripple

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18692?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18692: ------------------------------------- [~mickael_istria] it would be great to have all files from the pkg/hosted folder directly at the root of the zip > Jenkins build for jbosstools-incubator-ripple > --------------------------------------------- > > Key: JBIDE-18692 > URL: https://issues.jboss.org/browse/JBIDE-18692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > We need a jenkins job to build for jbosstools-incubator-ripple, and have it > invoking "./configure && jake" and distribute the builds to Nexus so that cordovasim can start using ripple from this repo. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3208: -------------------------------------- Snaphots/ folder should have the same layout as /staging/ and others (with composites referencing central, TP and so on). > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > {code} > download.jboss.org > <earlyaccess,updates,discovery>/mars > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/mars/stable is a pointer back into updates/mars) > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > and > {code} > devstudio.redhat.com > <earlyaccess,updates,discovery>/9.0 > /snapshots > /staging > /development > /stable (updates/9.0/stable is a pointer back into updates/9.0) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3208: -------------------------------------- {quote}/stable (updates/mars/stable is a pointer back into updates/mars){quote} Do we really want updates/mars to contain anything at all? And if we want it to be a p2 repo, I believe it's easier to have update/mars referencing updates/mars/stable. > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > {code} > download.jboss.org > <earlyaccess,updates,discovery>/mars > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/mars/stable is a pointer back into updates/mars) > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > and > {code} > devstudio.redhat.com > <earlyaccess,updates,discovery>/9.0 > /snapshots > /staging > /development > /stable (updates/9.0/stable is a pointer back into updates/9.0) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18559) when no updates available the full but empty p2 install UI is still shown

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18559?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18559: ----------------------------------- Affects Version/s: 4.2.0.Final > when no updates available the full but empty p2 install UI is still shown > ------------------------------------------------------------------------- > > Key: JBIDE-18559 > URL: https://issues.jboss.org/browse/JBIDE-18559 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > run check for updates from central with no updates available. > P2 ui with two step wizards is shown with no content. > Would have expected something like a simple "No updates found" instead. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18559) when no updates available the full but empty p2 install UI is still shown

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18559?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18559: ----------------------------------- Priority: Minor (was: Major) > when no updates available the full but empty p2 install UI is still shown > ------------------------------------------------------------------------- > > Key: JBIDE-18559 > URL: https://issues.jboss.org/browse/JBIDE-18559 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > run check for updates from central with no updates available. > P2 ui with two step wizards is shown with no content. > Would have expected something like a simple "No updates found" instead. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18558) Improve usability of up-to-date Central items

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18558?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18558: ----------------------------------- Summary: Improve usability of up-to-date Central items (was: cannot update already installed connector) > Improve usability of up-to-date Central items > --------------------------------------------- > > Key: JBIDE-18558 > URL: https://issues.jboss.org/browse/JBIDE-18558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.2.1.Final > > > Install hybrid tools. > restart eclipse. > enable show installed, click hybrid tools. > Install/update is greyed out. > why can I not run update ? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18558) Improve usability of up-to-date Central items

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18558?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18558: ----------------------------------- Issue Type: Enhancement (was: Bug) > Improve usability of up-to-date Central items > --------------------------------------------- > > Key: JBIDE-18558 > URL: https://issues.jboss.org/browse/JBIDE-18558 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.2.1.Final > > > Install hybrid tools. > restart eclipse. > enable show installed, click hybrid tools. > Install/update is greyed out. > why can I not run update ? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18558) Improve usability of up-to-date Central items

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18558?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18558: ----------------------------------- Priority: Minor (was: Major) > Improve usability of up-to-date Central items > --------------------------------------------- > > Key: JBIDE-18558 > URL: https://issues.jboss.org/browse/JBIDE-18558 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: respin-a > Fix For: 4.2.1.Final > > > Install hybrid tools. > restart eclipse. > enable show installed, click hybrid tools. > Install/update is greyed out. > why can I not run update ? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3240) Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBDS-3240?page=com.atlassian.jira.plugin.... ] Marek Novotny commented on JBDS-3240: ------------------------------------- [~fbricon] I may overlook that option, but I haven't setup any runtime. So I guess it should be the latest greatest archetype in that case too or why it use the oldest? > Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central > -------------------------------------------------------------------- > > Key: JBDS-3240 > URL: https://issues.jboss.org/browse/JBDS-3240 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Reporter: Marek Novotny > Assignee: Fred Bricon > Fix For: 8.0.1.GA > > > JBDS 8 aka JBoss Central provide by default old EAP/WFK archetype and not the latest 6.3.0.GA/2.6.0.Final by default. > For instance I click on HTML5 project in Start from Scratch in JBoss Central: > it launches wizard dialog where the archetype is org.jboss.tools.example.html5:jboss-as-kitchensink-html5-mobile:1.0.4.Final-redhat-wfk-2 version -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2014