August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3985) Modify installation progress bar to include supplemental runtimes

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-3985?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBDS-3985: ---------------------------------- [~akazakov] - Hey Alexey - I'm not sure how to mark this JIRA as resolved and to get it into the AM3 sprint. Can you assist? Thkx > Modify installation progress bar to include supplemental runtimes > ----------------------------------------------------------------- > > Key: JBDS-3985 > URL: https://issues.jboss.org/browse/JBDS-3985 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.1.0.AM1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Minor > Attachments: x1.png, x2.png > > > At install time, if an additional runtime is specified it does not appear in the overall progress bar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22788) Create integration tests PR check job for javascript

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22788?page=com.atlassian.jira.plugi... ] Pavol Srna resolved JBIDE-22788. -------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.x) Resolution: Done > Create integration tests PR check job for javascript > ---------------------------------------------------- > > Key: JBIDE-22788 > URL: https://issues.jboss.org/browse/JBIDE-22788 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Pavol Srna > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22794) Create integration tests PR check job for nodejs

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22794?page=com.atlassian.jira.plugi... ] Pavol Srna resolved JBIDE-22794. -------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.x) Resolution: Done > Create integration tests PR check job for nodejs > ------------------------------------------------ > > Key: JBIDE-22794 > URL: https://issues.jboss.org/browse/JBIDE-22794 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Pavol Srna > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process should disallow inclusion of snapshots artifacts

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22446 at 8/4/16 9:42 AM: ------------------------------------------------------------ OK, so I've amended the parent pom again. NOW, we'll warn in the build log (but not fail the build) for AM3 builds. For Final/GA, we'll fail the build. https://github.com/jbosstools/jbosstools-build/commit/5697ee4e07ea66e88a5... This means that for Final/GA builds we need to branch and build from a different branch, such that we can differentiate "builds which may be released" from "builds which are just CI builds that we copy and release as is". This is kind of shitty IMHO because it means we have a different release process for CI->Alpha vs. CI->Final, but hey. Two steps toward agile, one step back to waterfall. :D was (Author: nickboldt): OK, so I've amended the parent pom again. NOW, we'll warn in the build log (but not fail the build) for AM3 builds. For Final/GA, we'll fail the build. This means that for Final/GA builds we need to branch and build from a different branch, such that we can differentiate "builds which may be released" from "builds which are just CI builds that we copy and release as is". This is kind of shitty IMHO because it means we have a different release process for CI->Alpha vs. CI->Final, but hey. Two steps toward agile, one step back to waterfall. :D > Release process should disallow inclusion of snapshots artifacts > ---------------------------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: build > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process should disallow inclusion of snapshots artifacts

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22446: ------------------------------------ OK, so I've amended the parent pom again. NOW, we'll warn in the build log (but not fail the build) for AM3 builds. For Final/GA, we'll fail the build. This means that for Final/GA builds we need to branch and build from a different branch, such that we can differentiate "builds which may be released" from "builds which are just CI builds that we copy and release as is". This is kind of shitty IMHO because it means we have a different release process for CI->Alpha vs. CI->Final, but hey. Two steps toward agile, one step back to waterfall. :D > Release process should disallow inclusion of snapshots artifacts > ---------------------------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: build > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22881) snapshot dependency found in aerogear

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22881: ---------------------------------- Summary: snapshot dependency found in aerogear Key: JBIDE-22881 URL: https://issues.jboss.org/browse/JBIDE-22881 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid, build Affects Versions: 4.4.1.AM3 Reporter: Nick Boldt {code} [ERROR] Found property thym.version = 2.0.0-SNAPSHOT-201605071736 [INFO] Found BUILD_ALIAS = AM3 (for buildAliasSearch = AM3|Final|GA) [WARNING] Rule 0: org.jboss.tools.releng.NoSnapshotsAllowed failed with message: When BUILD_ALIAS (AM3) matches /AM3|Final|GA/, cannot include SNAPSHOT dependencies. {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22881) snapshot dependency found in aerogear

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22881?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22881: ------------------------------- Priority: Blocker (was: Major) > snapshot dependency found in aerogear > ------------------------------------- > > Key: JBIDE-22881 > URL: https://issues.jboss.org/browse/JBIDE-22881 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Priority: Blocker > > {code} > [ERROR] Found property thym.version = 2.0.0-SNAPSHOT-201605071736 > [INFO] Found BUILD_ALIAS = AM3 (for buildAliasSearch = AM3|Final|GA) > [WARNING] Rule 0: org.jboss.tools.releng.NoSnapshotsAllowed failed with message: > When BUILD_ALIAS (AM3) matches /AM3|Final|GA/, cannot include SNAPSHOT dependencies. > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22796) Create integration tests PR check job for profiler

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22796?page=com.atlassian.jira.plugi... ] Pavol Srna resolved JBIDE-22796. -------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.x) Resolution: Won't Fix There are zero integration tests for profiler afaik. Closing as won't fix. > Create integration tests PR check job for profiler > -------------------------------------------------- > > Key: JBIDE-22796 > URL: https://issues.jboss.org/browse/JBIDE-22796 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Pavol Srna > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22765) In FTL file in editor are missing directives in code assistant

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22765?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-22765: ---------------------------------- Fix Version/s: 4.4.1.AM3 > In FTL file in editor are missing directives in code assistant > -------------------------------------------------------------- > > Key: JBIDE-22765 > URL: https://issues.jboss.org/browse/JBIDE-22765 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.4.1.AM2 > Environment: Fedora 24, x86_64, > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160715-2233-B5663 > Build date: 20160715-2233 > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.1.AM3 > > > In .ftl file when using <# and opening code assistant, there are missing directives: compress, nt and setting. I checked http://freemarker.org/docs/ref_directive_alphaidx.html for supported directives but did not find any reason we are missing those mentioned above. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22880) List of modules filtered by "deployed" is always empty on the ServerEditor Deployment tab

by Mikhail Kalkov (JIRA)

Mikhail Kalkov created JBIDE-22880: -------------------------------------- Summary: List of modules filtered by "deployed" is always empty on the ServerEditor Deployment tab Key: JBIDE-22880 URL: https://issues.jboss.org/browse/JBIDE-22880 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.4.0.Final, 4.2.3.Final Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. Reporter: Mikhail Kalkov Attachments: test-projects.zip It is impossible to select "filter by" dropdown or press "Refresh Table" on the deployment tab of ServerEditor in JBoss Developer Studio when anything is deployed. I think it should be possible to change filter configuration but do not edit the table itself. Otherwise, both "Refresh" button and some of filter options becomes useless. See Steps to Reproduce for more details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016