May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22355) JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22355?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22355: ------------------------------------ If we're adding new features/plugins to support something upstream, eg., OpenShift v3.2 or EAP 7.1, those features could be Alpha while the rest of the openshift project is Final. Once those features are ready for release, they could be merged from topic branch into master, and then they'd be considered safe enough to be included, built, and supported. Thus, if code is in master, it's supported. If it's not ready to be supported, it shouldn't be in master. See also https://www.infoq.com/presentations/Facebook-Release-Process That way whatever we decide to call it, with or without a BUILD_ALIAS, as prefix or suffix, I can simply pull the latest CI, built from master Thursday night, and turn that into a staged build on Friday for QE to test. That build can then be released to /development/ or /stable/ on the following Mon, and demoed on Tues. I don't understand what you mean by "examples on a timeline". If you feel my example (a - g) above was exactly the same as we do things now, that's because regardless of whether we use BUILD_ALIAS or not, that's how things work for resolving remote vs. local. > JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2 > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22355 > URL: https://issues.jboss.org/browse/JBIDE-22355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > Build qualifiers, parent pom version, and version of parent pom referenced by components are still Alpha1. > All those should be moved to Alpha2 (they should be moved just when branching/releasing actually) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22355) JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22355?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22355: --------------------------------------------- I have a really hard time following your logic. Can you give examples on a timeline instead ? I'm not really grokking what is new/different in your explanation/thought experiment. one thing though: saying being agile = always final is really not applicable for us since we do not control the full stack nor can we (unless we start having mulitple parallel branches across the component tree) always be final in the sense of osgi versioning. > JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2 > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22355 > URL: https://issues.jboss.org/browse/JBIDE-22355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > Build qualifiers, parent pom version, and version of parent pom referenced by components are still Alpha1. > All those should be moved to Alpha2 (they should be moved just when branching/releasing actually) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22311) Adopt Tycho 0.25 for JBT and downstream projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22311?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22311: ------------------------------------ * Discovery problem was network fail resolving ant-contrib. Fixed in JBIDE-22373. * BPEL problem was issue with BUILD_NUMBER not being defined because BPEL doesn't use a profile for Jenkins builds that differs from local builds. Solved with {code}mvn clean install -DtychoVersion=0.25.0 -DjbossTychoPluginsVersion=0.25.0-SNAPSHOT -DBUILD_NUMBER=99{code} * Seam ... not sure. Tried to kick a new build and seems Jenkins or Github are having a day. #stalled. http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Adopt Tycho 0.25 for JBT and downstream projects > ------------------------------------------------ > > Key: JBIDE-22311 > URL: https://issues.jboss.org/browse/JBIDE-22311 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > In order to take advantage of several improvements in Tycho ( https://wiki.eclipse.org/Tycho/Release_Notes/0.25 ), we should consider adopting its 0.25 release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22249) Do the CQ dance for m2e/m2e-wtp

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22249?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22249: -------------------------------- Story Points: 10 (was: 5) > Do the CQ dance for m2e/m2e-wtp > ------------------------------- > > Key: JBIDE-22249 > URL: https://issues.jboss.org/browse/JBIDE-22249 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: maven, upstream > Affects Versions: 4.4.x > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha2 > > > Need to create all relevant CQs for the Neon release of m2e/m2e-wtp. > So awesome. Hopefully this year should be less of a headache as the process has been simplified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21648) Add EAP 7 GA to stacks.yaml

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21648?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-21648. --------------------------------- Resolution: Done fixed > Add EAP 7 GA to stacks.yaml > --------------------------- > > Key: JBIDE-21648 > URL: https://issues.jboss.org/browse/JBIDE-21648 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection, server > Reporter: Fred Bricon > Assignee: Rafael Benevides > Fix For: 4.3.2.Final > > > EAP 7 GA should be available from download runtime wizard. This means it should be added to stacks.yaml. > GA to be available in April 2016. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22354) Remediation page showing up because of Mylyn Wikitext

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22354?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22354: ------------------------------------ Or, maybe we can just go back to an older Mylyn wikitext feature? https://github.com/jbosstools/jbosstools-target-platforms/pull/211 > Remediation page showing up because of Mylyn Wikitext > ----------------------------------------------------- > > Key: JBIDE-22354 > URL: https://issues.jboss.org/browse/JBIDE-22354 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.4.0.Alpha2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > Take an Eclipse JavaScript M7, and try to install all JBoss Tools from http://download.jboss.org/jbosstools/neon/snapshots/updates/ > It shows a remediation page because JBoss Tools ships an asciidoc feature which is in different version that the one upstream. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22354) Remediation page showing up because of Mylyn Wikitext

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22354?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22354 at 5/17/16 2:48 PM: ------------------------------------------------------------- Or, maybe we can just go back to an older Mylyn wikitext feature? https://github.com/jbosstools/jbosstools-target-platforms/pull/211 WDYT, [~mickael_istria] ? was (Author: nickboldt): Or, maybe we can just go back to an older Mylyn wikitext feature? https://github.com/jbosstools/jbosstools-target-platforms/pull/211 > Remediation page showing up because of Mylyn Wikitext > ----------------------------------------------------- > > Key: JBIDE-22354 > URL: https://issues.jboss.org/browse/JBIDE-22354 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.4.0.Alpha2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > Take an Eclipse JavaScript M7, and try to install all JBoss Tools from http://download.jboss.org/jbosstools/neon/snapshots/updates/ > It shows a remediation page because JBoss Tools ships an asciidoc feature which is in different version that the one upstream. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher refresh view but collapse tree items to project level

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22361: -------------------------------- Story Points: 5 > OpenShift Explorer: Watcher refresh view but collapse tree items to project level > --------------------------------------------------------------------------------- > > Key: JBIDE-22361 > URL: https://issues.jboss.org/browse/JBIDE-22361 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Once I create a new EAP 6.4 application there is eap-app-1-build pod in running state. Once watcher should update resources automatically, tree items are collapsed to project level (if service was visible, it is not anymore, only connection with its project). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22354) Remediation page showing up because of Mylyn Wikitext

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22354?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22354: ---------------------------------- Assignee: Nick Boldt > Remediation page showing up because of Mylyn Wikitext > ----------------------------------------------------- > > Key: JBIDE-22354 > URL: https://issues.jboss.org/browse/JBIDE-22354 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.4.0.Alpha2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > Take an Eclipse JavaScript M7, and try to install all JBoss Tools from http://download.jboss.org/jbosstools/neon/snapshots/updates/ > It shows a remediation page because JBoss Tools ships an asciidoc feature which is in different version that the one upstream. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-654: ---------------------------------- DevStudio provides multiple stand-alone installers so that only users who want the overhead of pulling in EAP are burdened by it. In the IS case I agree with Lars in that it makes more sense to provide a standalone installer that provides JBDS/JBDSIS but *not* fuse runtime (for example). That gives us a manageable (under 1Gb) download and users can then decide/ download the runtime of their choice as a second step. > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2016