September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20818) For JBIDE 4.3.0.Final: Code Freeze + Branch [Forge]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20818?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20818. ---------------------------------- Assignee: Koen Aers Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [Forge] > --------------------------------------------------- > > Key: JBIDE-20818 > URL: https://issues.jboss.org/browse/JBIDE-20818 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [Forge]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20809) For JBIDE 4.3.0.Final: Code Freeze + Branch [Integration Tests]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20809?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20809. ---------------------------------- Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [Integration Tests] > --------------------------------------------------------------- > > Key: JBIDE-20809 > URL: https://issues.jboss.org/browse/JBIDE-20809 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [Integration Tests]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20808) For JBIDE 4.3.0.Final: Code Freeze + Branch [VPE]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20808?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20808. ---------------------------------- Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [VPE] > ------------------------------------------------- > > Key: JBIDE-20808 > URL: https://issues.jboss.org/browse/JBIDE-20808 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [VPE]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20401) OpenShift tooling UI should include a link to user docs

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20401?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20401: ------------------------------------- This is fixed for CR1 users as the properties file is read on workspace startup > OpenShift tooling UI should include a link to user docs > ------------------------------------------------------- > > Key: JBIDE-20401 > URL: https://issues.jboss.org/browse/JBIDE-20401 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Assignee: Fred Bricon > Priority: Blocker > Labels: help_wanted > Fix For: 4.3.0.CR1 > > > Given the very different architecture of OpenShift v3 as compared to v2, we should provide users with a link to docs detailing the differences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20803: --------------------------------------------- lets take the issue aobut EA onto JBTIS-508 > script process for merging IS jars into JBT/JBDS discovery sites > ---------------------------------------------------------------- > > Key: JBIDE-20803 > URL: https://issues.jboss.org/browse/JBIDE-20803 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery, integration-platform > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Need to document and script how to get the IS jars into the JBT/JBDS discovery sites. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20793) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Central]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20793?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-20793. ------------------------------- Resolution: Done Sorry for that. fixed in https://github.com/jbosstools/jbosstools-central/commit/d5e4bffa1d92769d9... > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Central] > ----------------------------------------------------------- > > Key: JBIDE-20793 > URL: https://issues.jboss.org/browse/JBIDE-20793 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Central]: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugi... ] Paul Leacu commented on JBIDE-20803: ------------------------------------ Hey [~maxandersen] - I get that we don't want to flood the user with non-stable URLs so I agree with comment above about including snapshots. With the comment concerning the 4.2.3.Final discovery URL - where would the early access URLs go? The EA URLs will be added to their list but they only contain EA IUs. > script process for merging IS jars into JBT/JBDS discovery sites > ---------------------------------------------------------------- > > Key: JBIDE-20803 > URL: https://issues.jboss.org/browse/JBIDE-20803 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery, integration-platform > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Need to document and script how to get the IS jars into the JBT/JBDS discovery sites. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stacks updatsesites mixes discovery and earlyaccess causing inconsistent update mechanis,

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBTIS-508: -------------------------------------- Description: While reviewing JBIDE-20803 I noticed the following: {code] jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... {code} The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: But there are a few problems: 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. #1 is mainly just to reduce the number of updatesites actually necessary for users to work with #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. I would also have expected that the discovery site with the discoveyr plugins was kept *separate* from the actual updatesites to avoid any coupling between these. was: While reviewing JBIDE-20803 I noticed the following: {code] jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... {code} The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: But there are a few problems: 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. #1 is mainly just to reduce the number of updatesites actually necessary for users to work with #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > integration stacks updatsesites mixes discovery and earlyaccess causing inconsistent update mechanis, > ----------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code] > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discoveyr plugins was kept *separate* from the actual updatesites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20804) Flaky source lookup while debugging apps deployed on Wildfly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20804?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20804. --------------------------------- Resolution: Done Applied https://github.com/jbosstools/jbosstools-central/commit/9cd4000bcbe27ea17... to 4.3.x branch IT has been added to master only: https://github.com/jbosstools/jbosstools-central/commit/d3ea9d3e98dba4a8f... > Flaky source lookup while debugging apps deployed on Wildfly > ------------------------------------------------------------ > > Key: JBIDE-20804 > URL: https://issues.jboss.org/browse/JBIDE-20804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.CR2 > > > When debugging an application deployed on Wildfly, some sources can not be found even though a matching source jar exists in Maven Central. > - create an html5 app > - put a breakpoint on MemberService.listAllMembers() > - Debug As > Debug on Server (choose Wildfly 10) > - when the web page is displayed, the breakpoint is hit > - go down the stacktrace, source should be downloaded for each line > - reach io.undertow.server.handlers.PredicateHandler, no source can be found > The problem is caused by the class file being found in the wildfly-cli client jar. But it has no matching source jar containing the Predicate.java file. The same class exists in undertow-core.jar, which has a matching source jar. But the source lookup stopped once it found wildfly-cli.jar, regardless if an actual source could be found. It should keep looking until an actual source is found -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stacks updatsesites mixes discovery and earlyaccess causing inconsistent update mechanis,

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBTIS-508: ----------------------------------------- Summary: integration stacks updatsesites mixes discovery and earlyaccess causing inconsistent update mechanis, Key: JBTIS-508 URL: https://issues.jboss.org/browse/JBTIS-508 Project: JBoss Tools Integration Stack Issue Type: Bug Components: releng Reporter: Max Rydahl Andersen Priority: Blocker While reviewing JBIDE-20803 I noticed the following: {code] jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... {code} The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: But there are a few problems: 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. #1 is mainly just to reduce the number of updatesites actually necessary for users to work with #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 September 2015