May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3917) Verify target-platform PR by running compile/package (no tests) build for all modules

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3917?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3917: ----------------------------- > Verify target-platform PR by running compile/package (no tests) build for all modules > ------------------------------------------------------------------------------------- > > Key: JBDS-3917 > URL: https://issues.jboss.org/browse/JBDS-3917 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Enhancement > Components: build, target-platform > Affects Versions: 10.0.0.Alpha2 > Reporter: Denis Golovin > > Would be good to have this as part of TP PR Verification build. > Example of repository with git submodules https://github.com/dgolovin/devstudio-releng. > Example for possible full build https://github.com/dgolovin/jbosstools-dev. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3917) Verify target-platform PR by running compile/package (no tests) build for all modules

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3917: ----------------------------------- Summary: Verify target-platform PR by running compile/package (no tests) build for all modules Key: JBDS-3917 URL: https://issues.jboss.org/browse/JBDS-3917 Project: Red Hat Developer Studio (DevStudio) Issue Type: Enhancement Components: build, target-platform Affects Versions: 10.0.0.Alpha2 Reporter: Denis Golovin Would be good to have this as part of TP PR Verification build. Example of repository with git submodules https://github.com/dgolovin/devstudio-releng. Example for possible full build https://github.com/dgolovin/jbosstools-dev. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21066) update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?)

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21066?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-21066. ------------------------------- Verified with 4.4.0.Alpha3 nightly. > update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21066 > URL: https://issues.jboss.org/browse/JBIDE-21066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > Attachments: terminal.png, Terminal.webm, tm.term.view.png > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22443) Add to TP build a check that produced TP can be installed in target Eclipse version

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22443?page=com.atlassian.jira.plugi... ] Denis Golovin edited comment on JBIDE-22443 at 5/31/16 9:27 AM: ---------------------------------------------------------------- [~maxandersen] Right, that would be a good check. I actually run this sometimes locally to verify PRs for TP. Full DevStudio build takes around 15 minutes + download time for new TP bits. was (Author: dgolovin): [~maxandersen]Right, that would be a good check. I actually run this sometimes locally to verify PRs for TP. Full DevStudio build takes around 15 minutes + download time for new TP bits. > Add to TP build a check that produced TP can be installed in target Eclipse version > ----------------------------------------------------------------------------------- > > Key: JBIDE-22443 > URL: https://issues.jboss.org/browse/JBIDE-22443 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, target-platform > Reporter: Mickael Istria > > Recently, a change in TP (jetty 9.3.6) was introduced and everything built fine with it; until the very end of the build process: during install-tests. > This issue would *probably* have occured if trying to install all content of the TP into the target Eclipse IDE (using install-grinder or p2director or whatever installation). So it would be good to have inside the TP build (as a "verify" plugin in pom.xml) something that would try to find whether target Eclipse version and our TP are already compatible. > Technical notes: > * Trying to install all IUs from the release train site + our TP seems easier to implement > * We do not need to actually install the artifacts, just making the p2 request and getting whether the request managed to find a working plan without remediation seems enough. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21861) Include Docker & Vagrant tooling 2.0.0 in JBT 4.4.x TP

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21861?page=com.atlassian.jira.plugi... ] Jan Richter commented on JBIDE-21861: ------------------------------------- Verified for 4.4.x TP which is 4.60.0.Alpha3-SNAPSHOT. > Include Docker & Vagrant tooling 2.0.0 in JBT 4.4.x TP > ------------------------------------------------------ > > Key: JBIDE-21861 > URL: https://issues.jboss.org/browse/JBIDE-21861 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > Include Docker tooling 2.0.0 in Target Platform 4.60.x, targeting JBoss Tools 4.4.x -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21861) Include Docker & Vagrant tooling 2.0.0 in JBT 4.4.x TP

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21861?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-21861. ------------------------------- > Include Docker & Vagrant tooling 2.0.0 in JBT 4.4.x TP > ------------------------------------------------------ > > Key: JBIDE-21861 > URL: https://issues.jboss.org/browse/JBIDE-21861 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > Include Docker tooling 2.0.0 in Target Platform 4.60.x, targeting JBoss Tools 4.4.x -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22439: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha3) > Tests: include different checkers in our build or jenkins > --------------------------------------------------------- > > Key: JBIDE-22439 > URL: https://issues.jboss.org/browse/JBIDE-22439 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.x > > > We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten. > - PMC/Findbugs > - Code-format-Checkers > - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/]) > - ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21439) Add JSON Editor to JBDS/JBT Target Platform

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21439?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-21439. ------------------------------- Verifying the JSON editor is present in 4.60.0.Alpha1 and Alpha3-SNAPSHOT and it is not installed OOTB. > Add JSON Editor to JBDS/JBT Target Platform > ------------------------------------------- > > Key: JBIDE-21439 > URL: https://issues.jboss.org/browse/JBIDE-21439 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > Missing description. Need update site from which to fetch IUs, and a list of which IUs to add. > Also need to know what to do with the JSON editor once it's in the TP... will it be installed OOTB like YAML editor in JBIDE-21377? Or will it be a new Central connector? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22405) Docker New and Noteworthy for 4.4.0.Alpha2

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22405?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22405. --------------------------------- Changes are documented and pulled in master whatsnew > Docker New and Noteworthy for 4.4.0.Alpha2 > ------------------------------------------ > > Key: JBIDE-22405 > URL: https://issues.jboss.org/browse/JBIDE-22405 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Docker is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Docker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22200) Create and use Neon M7 target platform

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22200?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-22200. ------------------------------- Verified with 4.4.0.Alpha3 and devstudio 10.0.0.Alpha3. > Create and use Neon M7 target platform > -------------------------------------- > > Key: JBIDE-22200 > URL: https://issues.jboss.org/browse/JBIDE-22200 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha2 > > Attachments: p2diff_jbdevstudio_4.60.0.Alpha1-SNAPSHOT_latest.txt, p2diff_jbdevstudio_4.60.0.Alpha1-SNAPSHOT_summary_latest.txt, p2diff_jbosstools_4.60.0.Alpha1-SNAPSHOT_latest.txt, p2diff_jbosstools_4.60.0.Alpha1-SNAPSHOT_summary_latest.txt > > > Prepare TP to use Neon M6 or M7 bits, which will be available 03/18 to 03/25 or 04/29 to 05/06. Cloned from JBIDE-21386. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * update install/matrix jobs to use new Eclipse JEE/platform binary; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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