January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-588) Investigate/fix missing validation button

by Eric Williams (JIRA)

[ https://issues.jboss.org/browse/ERT-588?page=com.atlassian.jira.plugin.sy... ] Eric Williams resolved ERT-588. ------------------------------- Resolution: Done > Investigate/fix missing validation button > ----------------------------------------- > > Key: ERT-588 > URL: https://issues.jboss.org/browse/ERT-588 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Eric Williams > Assignee: Eric Williams > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18654) run jdeps on our jars to see how dependent we are on api that might go away in Java 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18654?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18654: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.2.Final) > run jdeps on our jars to see how dependent we are on api that might go away in Java 9 > ------------------------------------------------------------------------------------- > > Key: JBIDE-18654 > URL: https://issues.jboss.org/browse/JBIDE-18654 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Fix For: 4.5.x > > > Java 9 JDK team have been pinging various teams to check if they got depedency on API that is scheduled to disappear in Java 9. > There is a tool called jdeps that we can use to check for this using the -jdkinternals flag. > https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool > The sooner the better we get this done as it is feedback to the Java 9 team. > If we can we should try run it on *all* jars, even eclipse ones to see what will be affected - but first of all jboss tools plugins. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25139) migrate PR build jobs on fusesource jenkins to dev-platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25139?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25139: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.2.Final) > migrate PR build jobs on fusesource jenkins to dev-platform > ----------------------------------------------------------- > > Key: JBIDE-25139 > URL: https://issues.jboss.org/browse/JBIDE-25139 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fusetools > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.x > > Attachments: all-three-PR-builders.png > > > I believe the current PR build job is this one: > https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... > [~lhein] [~aurelien.pupier] is that correct? > Yes, it is correct -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25315) Include Fuse CI job update for job configuration update

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25315?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25315: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.2.Final) > Include Fuse CI job update for job configuration update > ------------------------------------------------------- > > Key: JBIDE-25315 > URL: https://issues.jboss.org/browse/JBIDE-25315 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 4.5.x > > Attachments: image-2017-11-02-09-23-36-305.png > > > the CI jobs on Fuse Ci are often not synchronized with modifications done on other jboss tools project such as TARGET_PLATFORM version. > for instance today again: > !image-2017-11-02-09-23-36-305.png|thumbnail! > it would be useful to include the update of the FUSE CI jobs in the process to update the jobs -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25385) Upgrade to FreeMarker 2.3.27

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25385?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25385. --------------------------------- > Upgrade to FreeMarker 2.3.27 > ---------------------------- > > Key: JBIDE-25385 > URL: https://issues.jboss.org/browse/JBIDE-25385 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: freemarker > Reporter: Daniel Dekany > Assignee: Jeff MAURY > Fix For: 4.5.2.AM3 > > > Upgrade FreeMarker dependency to 2.3.27. PR coming soon... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24897 at 1/16/18 10:06 AM: -------------------------------------------------------------- [~jeffmaury] The issue building on windows [1] will be solved later today. Geetika needs to rebase her PR [2] to the latest changes in master. [1] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/i... [2] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/p... Also, I'm seeing itest failures in the latest builds [3]: [3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... So... code freeze is tomorrow. Are we ready to include fabric8 analytics in JBT and devstudio? Do we want a new Central connector too? Options for inclusion: * in JBT as an optional install? (if so, which category?) * in JBT as a default install? (if so, assume category = CoreTools, but maybe also MavenTools?) * in devstudio as optional install? (if so, which category?) * in devstudio as default install? (if so, assume category = CoreTools, but maybe also MavenTools? Will also add to the devstudio.rpm.feature so it's installed OOTB) * in Central as a new connector? (if so, need metadata to describe the feature, and an icon file. See examples here: https://github.com/jbosstools/jbosstools-discovery/blob/master/devstudio/... ) was (Author: nickboldt): [~jeffmaury] The issue building on windows [1] will be solved later today. Geetika needs to rebase her PR [2] to the latest changes in master. [1] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/i... [2] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/p... Also, I'm seeing itest failures in the latest builds [3]: [3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... So... code freeze is tomorrow. Are we ready to include fabric8 analytics in JBT and devstudio? Do we want a new Central connector too? Options for inclusion: * in JBT as an optional install? (if so, which category?) * in JBT as a default install? (if so, assume category = CoreTools, but maybe also MavenTools?) * in devstudio as optional install? (if so, which category?) * in devstudio as default install? (if so, assume category = CoreTools, but maybe also MavenTools? Will also add to the devstudio.rpm.feature so it's installed OOTB) * in Central as a new connector? (if so, need metadata to describe the feature, and an icon file. See examples here: https://github.com/jbosstools/jbosstools-discovery/blob/master/devstudio/... ) > add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24897 > URL: https://issues.jboss.org/browse/JBIDE-24897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.Final > > Attachments: fabric8-connector.png, stack analysis.mp4 > > > Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra] > Assuming we also want to create a Central connector to advertise this optional feature. > In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala] > Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin > Affected: > * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml) > * https://github.com/jbosstools/jbosstools-build-sites (category.xml) > * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24897 at 1/16/18 10:05 AM: -------------------------------------------------------------- [~jeffmaury] The issue building on windows [1] will be solved later today. Geetika needs to rebase her PR [2] to the latest changes in master. [1] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/i... [2] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/p... Also, I'm seeing itest failures in the latest builds [3]: [3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... So... code freeze is tomorrow. Are we ready to include fabric8 analytics in JBT and devstudio? Do we want a new Central connector too? Options for inclusion: * in JBT as an optional install? (if so, which category?) * in JBT as a default install? (if so, assume category = CoreTools, but maybe also MavenTools?) * in devstudio as optional install? (if so, which category?) * in devstudio as default install? (if so, assume category = CoreTools, but maybe also MavenTools? Will also add to the devstudio.rpm.feature so it's installed OOTB) * in Central as a new connector? (if so, need metadata to describe the feature, and an icon file. See examples here: https://github.com/jbosstools/jbosstools-discovery/blob/master/devstudio/... ) was (Author: nickboldt): [~jeffmaury] The issue building on windows [1] should now be solved. Can you take another look? [1] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/i... Also, I'm seeing itest failures in the latest builds [2]: [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... So... code freeze is tomorrow. Are we ready to include fabric8 analytics in JBT and devstudio? Do we want a new Central connector too? Options for inclusion: * in JBT as an optional install? (if so, which category?) * in JBT as a default install? (if so, assume category = CoreTools, but maybe also MavenTools?) * in devstudio as optional install? (if so, which category?) * in devstudio as default install? (if so, assume category = CoreTools, but maybe also MavenTools? Will also add to the devstudio.rpm.feature so it's installed OOTB) * in Central as a new connector? (if so, need metadata to describe the feature, and an icon file. See examples here: https://github.com/jbosstools/jbosstools-discovery/blob/master/devstudio/... ) > add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24897 > URL: https://issues.jboss.org/browse/JBIDE-24897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.Final > > Attachments: fabric8-connector.png, stack analysis.mp4 > > > Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra] > Assuming we also want to create a Central connector to advertise this optional feature. > In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala] > Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin > Affected: > * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml) > * https://github.com/jbosstools/jbosstools-build-sites (category.xml) > * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24897: ------------------------------------ [~jeffmaury] The issue building on windows [1] should now be solved. Can you take another look? [1] https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin/i... Also, I'm seeing itest failures in the latest builds [2]: [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... So... code freeze is tomorrow. Are we ready to include fabric8 analytics in JBT and devstudio? Do we want a new Central connector too? Options for inclusion: * in JBT as an optional install? (if so, which category?) * in JBT as a default install? (if so, assume category = CoreTools, but maybe also MavenTools?) * in devstudio as optional install? (if so, which category?) * in devstudio as default install? (if so, assume category = CoreTools, but maybe also MavenTools? Will also add to the devstudio.rpm.feature so it's installed OOTB) * in Central as a new connector? (if so, need metadata to describe the feature, and an icon file. See examples here: https://github.com/jbosstools/jbosstools-discovery/blob/master/devstudio/... ) > add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24897 > URL: https://issues.jboss.org/browse/JBIDE-24897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.Final > > Attachments: fabric8-connector.png, stack analysis.mp4 > > > Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra] > Assuming we also want to create a Central connector to advertise this optional feature. > In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala] > Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin > Affected: > * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml) > * https://github.com/jbosstools/jbosstools-build-sites (category.xml) > * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25100) freemarker plugin Maven built fails due to outdated versions

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25100?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25100. --------------------------------- I have built cloned repo from github, master branch with success. > freemarker plugin Maven built fails due to outdated versions > ------------------------------------------------------------ > > Key: JBIDE-25100 > URL: https://issues.jboss.org/browse/JBIDE-25100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Reporter: Daniel Dekany > Assignee: Jeff MAURY > Fix For: 4.5.2.AM1 > > > I have check out the master from Git, but couldn't build it. Not sure how (if at all) it succeeds on you build server. Anyway, these are the things I have changed to fix it (will send PR soon): > * Changed org.jboss.tools:parent:4.5.0.AM2-SNAPSHOT to 4.5.1.AM3-SNAPSHOT. (Otherwise it tried to download https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo..., which is HTTP 404. BTW, it still issues several warnings for not being able to retrieve the metadata, also directory of artifacts, like https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... give HTTP 500.) > > * Increased project version from 1.5.300 to 1.5.301 (or else Tycho said org.jboss.ide.eclipse.freemarker: Only qualifier changed for (o > rg.jboss.ide.eclipse.freemarker/1.5.300.v20170925-1612). "Expected to have bigger x.y.z than what is available in baseline (1.5.300.v20161214-1103)") -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25589) intermittent test failures in vpe

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25589?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25589: ------------------------------- Description: These 3 tests fail every other build: org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.norefreshTest https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... was: These 3 tests fail every other build: org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.norefreshTest > intermittent test failures in vpe > --------------------------------- > > Key: JBIDE-25589 > URL: https://issues.jboss.org/browse/JBIDE-25589 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.x > > Attachments: vpe-intermittent-test-failures.png > > > These 3 tests fail every other build: > org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest > org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest > org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.norefreshTest > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 January 2018