July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22673 at 7/22/16 4:26 PM: ------------------------------------------------------------- PRs to move to 0.26.0-SNAPSHOT in maven-plugins, parent pom, target-platforms and discovery (to be applied in next sprint!): https://github.com/jbosstools/jbosstools-maven-plugins/pull/57/files?w=1 https://github.com/jbosstools/jbosstools-build/pull/229/files?w=1 https://github.com/jbosstools/jbosstools-target-platforms/pull/226?w=1 https://github.com/jbosstools/jbosstools-discovery/pull/334/files?w=1 Once those are all built (maven clean install -U), you can then verify it works with: {code} export JAVA_HOME=/opt/sun-java2-8.0/ echo $JAVA_HOME cd ~/tru/jbosstools-target-platforms ~/tru/jbosstools-build-ci/util/verifyTarget.sh -x -b `pwd` -p jbosstools ~/tru/jbosstools-build-ci/util/verifyTarget.sh -x -b `pwd` -p jbdevstudio cd ~/tru/jbosstools-discovery ~/tru/jbosstools-build-ci/util/verifyTarget.sh -x -b `pwd` -p jbtcentral -u http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... {code} So, yeah, the problem is that with provisional APIs (0.x) there's no guarantee that 0.26 and 0.25 will play nicely together. Solution: we move to 0.26, as you suggested. The above PRs let us move to 0.26.0-SNAPSHOT however, if we want to move up sooner. was (Author: nickboldt): PRs to move to 0.26.0-SNAPSHOT in maven-plugins, parent pom and discovery (to be applied in next sprint!): https://github.com/jbosstools/jbosstools-maven-plugins/pull/57/files?w=1 https://github.com/jbosstools/jbosstools-build/pull/229/files?w=1 https://github.com/jbosstools/jbosstools-target-platforms/pull/226?w=1 https://github.com/jbosstools/jbosstools-discovery/pull/334/files?w=1 Once those are all built (maven clean install -U), you can then verify it works with: {code} export JAVA_HOME=/opt/sun-java2-8.0/ echo $JAVA_HOME cd ~/tru/jbosstools-target-platforms ~/tru/jbosstools-build-ci/util/verifyTarget.sh -x -b `pwd` -p jbosstools ~/tru/jbosstools-build-ci/util/verifyTarget.sh -x -b `pwd` -p jbdevstudio cd ~/tru/jbosstools-discovery ~/tru/jbosstools-build-ci/util/verifyTarget.sh -x -b `pwd` -p jbtcentral -u http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... {code} So, yeah, the problem is that with provisional APIs (0.x) there's no guarantee that 0.26 and 0.25 will play nicely together. Solution: we move to 0.26, as you suggested. The above PRs let us move to 0.26.0-SNAPSHOT however, if we want to move up sooner. > Need better duplicate IU detection when validating target platforms > ------------------------------------------------------------------- > > Key: JBIDE-22673 > URL: https://issues.jboss.org/browse/JBIDE-22673 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform, upstream > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > Attachments: verify-log.txt > > > As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not. > {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...? > Or add a whitelist?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22673: ------------------------------------ PRs to move to 0.26.0-SNAPSHOT in maven-plugins, parent pom and discovery (to be applied in next sprint!): https://github.com/jbosstools/jbosstools-maven-plugins/pull/57/files?w=1 https://github.com/jbosstools/jbosstools-build/pull/229/files?w=1 https://github.com/jbosstools/jbosstools-target-platforms/pull/226?w=1 https://github.com/jbosstools/jbosstools-discovery/pull/334/files?w=1 Once those are all built (maven clean install -U), you can then verify it works with: {code} export JAVA_HOME=/opt/sun-java2-8.0/ echo $JAVA_HOME cd ~/tru/jbosstools-target-platforms ~/tru/jbosstools-build-ci/util/verifyTarget.sh -x -b `pwd` -p jbosstools ~/tru/jbosstools-build-ci/util/verifyTarget.sh -x -b `pwd` -p jbdevstudio cd ~/tru/jbosstools-discovery ~/tru/jbosstools-build-ci/util/verifyTarget.sh -x -b `pwd` -p jbtcentral -u http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... {code} So, yeah, the problem is that with provisional APIs (0.x) there's no guarantee that 0.26 and 0.25 will play nicely together. Solution: we move to 0.26, as you suggested. The above PRs let us move to 0.26.0-SNAPSHOT however, if we want to move up sooner. > Need better duplicate IU detection when validating target platforms > ------------------------------------------------------------------- > > Key: JBIDE-22673 > URL: https://issues.jboss.org/browse/JBIDE-22673 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform, upstream > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.1.AM3 > > Attachments: verify-log.txt > > > As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not. > {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...? > Or add a whitelist?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22673: ------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.x) > Need better duplicate IU detection when validating target platforms > ------------------------------------------------------------------- > > Key: JBIDE-22673 > URL: https://issues.jboss.org/browse/JBIDE-22673 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform, upstream > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.1.AM3 > > Attachments: verify-log.txt > > > As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not. > {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...? > Or add a whitelist?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22673: ---------------------------------- Assignee: Nick Boldt (was: Mickael Istria) > Need better duplicate IU detection when validating target platforms > ------------------------------------------------------------------- > > Key: JBIDE-22673 > URL: https://issues.jboss.org/browse/JBIDE-22673 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform, upstream > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > Attachments: verify-log.txt > > > As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not. > {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...? > Or add a whitelist?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22701) ConsoleLineTracker not working anymore

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22701?page=com.atlassian.jira.plugi... ] Daniel Dekany commented on JBIDE-22701: --------------------------------------- Nope, it was a quite big oversight on my part... I have re-added and fixed it. See https://github.com/jbosstools/jbosstools-freemarker/pull/72 > ConsoleLineTracker not working anymore > -------------------------------------- > > Key: JBIDE-22701 > URL: https://issues.jboss.org/browse/JBIDE-22701 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: freemarker > Reporter: Daniel Dekany > Assignee: Alexey Kazakov > Fix For: 4.4.1.AM2 > > > No links are created for exception FreeMarker error messages on the console, because the message format of FreeMarker was changed long ago. > -Because we use the row/col info returned by FM for a while.- -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22701) ConsoleLineTracker not working anymore

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22701?page=com.atlassian.jira.plugi... ] Daniel Dekany updated JBIDE-22701: ---------------------------------- Description: No links are created for exception FreeMarker error messages on the console, because the message format of FreeMarker was changed long ago. -Because we use the row/col info returned by FM for a while.- was:Because we use the row/col info returned by FM for a while. > ConsoleLineTracker not working anymore > -------------------------------------- > > Key: JBIDE-22701 > URL: https://issues.jboss.org/browse/JBIDE-22701 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: freemarker > Reporter: Daniel Dekany > Assignee: Alexey Kazakov > Fix For: 4.4.1.AM2 > > > No links are created for exception FreeMarker error messages on the console, because the message format of FreeMarker was changed long ago. > -Because we use the row/col info returned by FM for a while.- -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22701) ConsoleLineTracker not working anymore

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22701?page=com.atlassian.jira.plugi... ] Daniel Dekany updated JBIDE-22701: ---------------------------------- Summary: ConsoleLineTracker not working anymore (was: ConsoleLineTracker is not needed anymore) > ConsoleLineTracker not working anymore > -------------------------------------- > > Key: JBIDE-22701 > URL: https://issues.jboss.org/browse/JBIDE-22701 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: freemarker > Reporter: Daniel Dekany > Assignee: Alexey Kazakov > Fix For: 4.4.1.AM2 > > > Because we use the row/col info returned by FM for a while. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22757 at 7/22/16 2:48 PM: ------------------------------------------------------------- PR for reddeer: https://github.com/jboss-reddeer/reddeer/pull/1424 PR for browsersim-standalone: https://github.com/jbosstools/jbosstools-browsersim/pull/87 PR for integration-stack: https://github.com/jbosstools/jbosstools-integration-stack/pull/516 Fix for maven-plugins: https://github.com/jbosstools/jbosstools-maven-plugins/commit/c64344ffe83... was (Author: nickboldt): PR for reddeer: https://github.com/jboss-reddeer/reddeer/pull/1424 PR for browsersim-standalone: https://github.com/jbosstools/jbosstools-browsersim/pull/87 PR for integration-stack: https://github.com/jbosstools/jbosstools-integration-stack/pull/516 > jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug) > ----------------------------------------------------------------- > > Key: JBIDE-22757 > URL: https://issues.jboss.org/browse/JBIDE-22757 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.1.AM2 > > Attachments: buildID-broken.png > > > Due to an upstream bug in Jenkins [1], [2], BUILD_ID now = BUILD_NUMBER. > [1] https://issues.jenkins-ci.org/browse/JENKINS-26520 > [2] https://issues.jenkins-ci.org/browse/JENKINS-26626 > So instead of timestamped build folders, we're seeing things like this: > !buildID-broken.png|thumbnail! > Workaround until fixed in Jenkins: > {code}BUILD_ID=`date -u +%Y-%m-%d_%H-%M-%S`{code} > Or, try using BUILD_TIMESTAMP instead? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3961) CDK installation failed with progress bar stuck in 99%

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3961?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-3961 at 7/22/16 1:17 PM: -------------------------------------------------------------- I can replicate this issue and going to fix it today. was (Author: dgolovin): I could replicate this. > CDK installation failed with progress bar stuck in 99% > ------------------------------------------------------ > > Key: JBDS-3961 > URL: https://issues.jboss.org/browse/JBDS-3961 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Environment: h3. Operating System: > Windows 10 Pro 64 Bit > h3. Devstudio version > Devstudio 1.0 GA > Reporter: Budh Ram Gurung > Assignee: Denis Golovin > Labels: cdk > Fix For: 10.1.0.AM2, 10.1.0.AM3 > > Attachments: dev_studio_installation.PNG, install.log > > > I was trying the "devstudio 1.0 GA build" ("development-suite-1.0.0-GA-bundle-installer.exe") and unable to get CDK installation after gone through the steps of authentication, vagrant, cygwin, jboss dev studio installations. > Observations: > CDK installation stuck in 99% with "failed" mark. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22757 at 7/22/16 1:00 PM: ------------------------------------------------------------- PR for reddeer: https://github.com/jboss-reddeer/reddeer/pull/1424 PR for browsersim-standalone: https://github.com/jbosstools/jbosstools-browsersim/pull/87 PR for integration-stack: https://github.com/jbosstools/jbosstools-integration-stack/pull/516 was (Author: nickboldt): PR for reddeer: https://github.com/jboss-reddeer/reddeer/pull/1424 PR for browsersim-standalone: https://github.com/jbosstools/jbosstools-browsersim/pull/87 > jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug) > ----------------------------------------------------------------- > > Key: JBIDE-22757 > URL: https://issues.jboss.org/browse/JBIDE-22757 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.1.AM2 > > Attachments: buildID-broken.png > > > Due to an upstream bug in Jenkins [1], [2], BUILD_ID now = BUILD_NUMBER. > [1] https://issues.jenkins-ci.org/browse/JENKINS-26520 > [2] https://issues.jenkins-ci.org/browse/JENKINS-26626 > So instead of timestamped build folders, we're seeing things like this: > !buildID-broken.png|thumbnail! > Workaround until fixed in Jenkins: > {code}BUILD_ID=`date -u +%Y-%m-%d_%H-%M-%S`{code} > Or, try using BUILD_TIMESTAMP instead? -- 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 July 2016