September 2015 - jbosstools-issues

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

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20818: ---------------------------------- Summary: 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 Priority: Blocker 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] (JBDS-3530) For JBDS 9.0.0.GA: Code Freeze + Branch

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3530: -------------------------------- Summary: For JBDS 9.0.0.GA: Code Freeze + Branch Key: JBDS-3530 URL: https://issues.jboss.org/browse/JBDS-3530 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: installer Reporter: Nick Boldt Priority: Blocker Fix For: 9.0.0.GA For JBDS 9.0.0.GA: 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...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20805: ---------------------------------- Summary: For JBIDE 4.3.0.Final: Code Freeze + Branch Key: JBIDE-20805 URL: https://issues.jboss.org/browse/JBIDE-20805 Project: Tools (JBoss Tools) Issue Type: Task Components: build Reporter: Nick Boldt Priority: Blocker Fix For: 4.3.0.Final For JBIDE 4.3.0.Final: 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...] See also: JBDS-3530 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20806: ---------------------------------- Summary: For JBIDE 4.3.0.Final: Code Freeze + Branch [Aerogear] Key: JBIDE-20806 URL: https://issues.jboss.org/browse/JBIDE-20806 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: aerogear-hybrid, cordovasim Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.0.Final [Aerogear]: 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 Aerogear 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-20749) Target Platform based on Eclipse Neon M1 (or later?)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20749?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20749: ------------------------------------ PR merged 12 hrs ago, but no one kicked a build, so I'm getting lots of failing install tests as I expected this was built 11 hrs ago. Kicked: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... >=459 > Target Platform based on Eclipse Neon M1 (or later?) > ---------------------------------------------------- > > Key: JBIDE-20749 > URL: https://issues.jboss.org/browse/JBIDE-20749 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Neon plan is here https://wiki.eclipse.org/Neon/Simultaneous_Release_Plan -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20775?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20775: -------------------------------------- Assignee: Gorkem Ercan (was: Ilya Buziuk) > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Aerogear] > ------------------------------------------------------------ > > Key: JBIDE-20775 > URL: https://issues.jboss.org/browse/JBIDE-20775 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Aerogear]: 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 Aerogear 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-20779) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20779?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20779: ------------------------------------ build (parent pom): done build-sites: done dl.jb.org: nothing to do devdoc: nothing to do (at least until we start WRITING new doc that's only for 4.4.x) build-ci: not done yet -- need to branch from 4.3.x to 4.4.x (master is still deprecated) & update/clone job(s) versionwatch: not done yet maven-plugins: leaving that for [~mickael_istria] to do > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20779 > URL: https://issues.jboss.org/browse/JBIDE-20779 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: 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 build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch 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-20600) document how to use Deploy to OpenShift

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20600?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-20600: -------------------------------------- Is this it? https://access.redhat.com/articles/1591013 > document how to use Deploy to OpenShift > --------------------------------------- > > Key: JBIDE-20600 > URL: https://issues.jboss.org/browse/JBIDE-20600 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.0.Final > > > Trying to use the Deploy to OpenShift dialog I found a few issues and i'm a bit stuck figuring out how it works. > What I did was trying to just take jboss/wildfly:latest and deploy to openshift. > First off, the first page of Deploy to openshift wont let me create a connection or project so I have as a user to have done that *before* starting the dialog. > Once I have done that the dialog is asking for a lot of questions but very little hints about what they are. > One example is "Add Route" on services ports page - that page can have multiple services so which does "Add Route" refer to and should it not need to know which port needed to use ? > But worst issue is that once all that is filled out then I do not seem to be able to get any logs or info on why wildfly is not started. > neither in webconsole nor in eclipse views. > Should there not be access to some console logs or similar to things created by a project ? > anyway - long description to point out we need some docs on how to actually use this if we cannot fix the UI before GA. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-504: ---------------------------------- Verified - highly impressive! \o/ > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20709) tools.jboss.org/features: Add OpenShift 3

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20709?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20709: ---------------------------------------- Just a reminder that we have ~ 10 days left before the release :) [~fbricon] us know if we have something preventing us to have this done by then. > tools.jboss.org/features: Add OpenShift 3 > ----------------------------------------- > > Key: JBIDE-20709 > URL: https://issues.jboss.org/browse/JBIDE-20709 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Fix For: 4.3.0.Final > > > We should add OpenShift 3 to http://tools.jboss.org/features/openshift.html -- 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