August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18188) Mobile Palette: provide a way to filter palette group, show only palette groups which libraries defined on the current html page

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-18188: ------------------------------------- Summary: Mobile Palette: provide a way to filter palette group, show only palette groups which libraries defined on the current html page Key: JBIDE-18188 URL: https://issues.jboss.org/browse/JBIDE-18188 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml/html source editing Affects Versions: 4.3.x Reporter: Daniel Azarov -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18188) Mobile Palette: provide a way to filter palette group, show only palette groups which libraries defined on the current html page

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18188?page=com.atlassian.jira.plugi... ] Daniel Azarov reassigned JBIDE-18188: ------------------------------------- Assignee: Daniel Azarov > Mobile Palette: provide a way to filter palette group, show only palette groups which libraries defined on the current html page > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18188 > URL: https://issues.jboss.org/browse/JBIDE-18188 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.x > Reporter: Daniel Azarov > Assignee: Daniel Azarov > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3131) ensure the website urls for installing from central continues to work for both devstudio domains

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3131?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3131 at 8/29/14 6:45 PM: ----------------------------------------------------------- [~maxandersen] We can either leave https://github.com/nickboldt/jbosstools-website/blob/master/_layouts/down... unchanged here, or else we need: * if connector collection being installed is JBDS IS 7 ** then use the old devstudio.redhat.com URL * else ** use devstudio.redhat.com URL THEN we can switch the URL hardcoded in https://github.com/jbosstools/jbosstools-central/pull/281 and we'll be golden. was (Author: nickboldt): [~maxandersen] We can either leave https://github.com/nickboldt/jbosstools-website/blob/master/_layouts/down... unchanged here, or else we need: * if connector collection being installed is JBDS IS 7 **then use the old devstudio.redhat.com URL * else ** use devstudio.redhat.com URL THEN we can switch the URL hardcoded in https://github.com/jbosstools/jbosstools-central/pull/281 and we'll be golden. > ensure the website urls for installing from central continues to work for both devstudio domains > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3131 > URL: https://issues.jboss.org/browse/JBDS-3131 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: central, website > Reporter: Max Rydahl Andersen > Fix For: 8.0.0.CR1 > > > with devstudio.jboss.com being replace by devstudio.redhat.com we need central to continue to understand both when url is dragged to it and we can't just hard code the use of redhat.com into the website since that will make the urls invalid for JBDS 7. > https://github.com/jbosstools/jbosstools-website/pull/197 and https://github.com/jbosstools/jbosstools-central/pull/281 are incomplete versions of this that hardcodes devstudio.redhat.com - we need to support both. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3131) ensure the website urls for installing from central continues to work for both devstudio domains

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3131?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3131: ---------------------------------- [~maxandersen] We can either leave https://github.com/nickboldt/jbosstools-website/blob/master/_layouts/down... unchanged here, or else we need: * if connector collection being installed is JBDS IS 7 **then use the old devstudio.redhat.com URL * else ** use devstudio.redhat.com URL THEN we can switch the URL hardcoded in https://github.com/jbosstools/jbosstools-central/pull/281 and we'll be golden. > ensure the website urls for installing from central continues to work for both devstudio domains > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3131 > URL: https://issues.jboss.org/browse/JBDS-3131 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: central, website > Reporter: Max Rydahl Andersen > Fix For: 8.0.0.CR1 > > > with devstudio.jboss.com being replace by devstudio.redhat.com we need central to continue to understand both when url is dragged to it and we can't just hard code the use of redhat.com into the website since that will make the urls invalid for JBDS 7. > https://github.com/jbosstools/jbosstools-website/pull/197 and https://github.com/jbosstools/jbosstools-central/pull/281 are incomplete versions of this that hardcodes devstudio.redhat.com - we need to support both. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18150) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Aerogear]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18150?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18150: ------------------------------------ https://github.com/jbosstools/jbosstools-aerogear/tree/jbosstools-4.2.x exists. [~gercan] Can this JIRA be closed? > For JBIDE 4.2.0.CR1: Code Freeze + Branch [Aerogear] > ---------------------------------------------------- > > Key: JBIDE-18150 > URL: https://issues.jboss.org/browse/JBIDE-18150 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [Aerogear]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1 > [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch; > {code} > git fetch origin master > git checkout FETCH_HEAD > git checkout -b jbosstools-4.2.x > git push origin jbosstools-4.2.x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and > * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. 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.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3009) use devstudio.redhat.com instead of devstudio.jboss.com in hardcoded URLs within JBDS (eg., Central discovery, updates)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3009?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reassigned JBDS-3009: ----------------------------------------- Assignee: Max Rydahl Andersen (was: Nick Boldt) > use devstudio.redhat.com instead of devstudio.jboss.com in hardcoded URLs within JBDS (eg., Central discovery, updates) > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3009 > URL: https://issues.jboss.org/browse/JBDS-3009 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 8.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 8.0.0.CR1 > > Attachments: ssl-enabled-for-filemgmt-but-at-what-cost.png > > > use devstudio.redhat.com instead of devstudio.jboss.com in hardcoded URLs within JBDS (eg., Central discovery, updates) > Affected files: *.xml, *.inf, etc. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3131) ensure the website urls for installing from central continues to work for both devstudio domains

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBDS-3131: ----------------------------------------- Summary: ensure the website urls for installing from central continues to work for both devstudio domains Key: JBDS-3131 URL: https://issues.jboss.org/browse/JBDS-3131 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: central, website Reporter: Max Rydahl Andersen Fix For: 8.0.0.CR1 with devstudio.jboss.com being replace by devstudio.redhat.com we need central to continue to understand both when url is dragged to it and we can't just hard code the use of redhat.com into the website since that will make the urls invalid for JBDS 7. https://github.com/jbosstools/jbosstools-website/pull/197 and https://github.com/jbosstools/jbosstools-central/pull/281 are incomplete versions of this that hardcodes devstudio.redhat.com - we need to support both. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3130) [RFE] Add tooling to manage openshift databases

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3130?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3130: ------------------------------------------- So you are asking to easily get the ssh command and/or open a shell/terminal to it ? Not to setup a database connection and do portforwarding for you to browse the data ? > [RFE] Add tooling to manage openshift databases > ----------------------------------------------- > > Key: JBDS-3130 > URL: https://issues.jboss.org/browse/JBDS-3130 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 7.1.1.GA > Environment: All > Reporter: Tim Williams > Assignee: Max Rydahl Andersen > Priority: Minor > > In OpenShift, a scaled application will have numerous 'gears', each running a copy of the developer's code. If the developer is running a database, there will be only one gear containing this database. > To export/import/backup/restore the database, a user must ssh to the specific gear that holds the database cartridge. The only current way to do this in JBDS is to print all the environment variables and look for the following: > $OPENSHIFT_MYSQL_DB_GEAR_UUID > $OPENSHIFT_MYSQL_DB_GEAR_DNS > You can then use these values in a terminal to ssh to the database gear: > $ ssh $OPENSHIFT_MYSQL_DB_GEAR_UUID@$OPENSHIFT_MYSQL_DB_GEAR_DNS > It would be helpful to have some kind of tooling to either ssh into this gear directly through JBDS, or at least print the ssh command (above) using the environment variables from the gear. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3127) For JBDS 8.0.0.CR1: Code Freeze + Branch

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3127?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen closed JBDS-3127. ------------------------------------- Resolution: Duplicate Issue this looks like 100% duplicate of JBDS-3126 > For JBDS 8.0.0.CR1: Code Freeze + Branch > ---------------------------------------- > > Key: JBDS-3127 > URL: https://issues.jboss.org/browse/JBDS-3127 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: installer > Reporter: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 8.0.0.CR1 > > > For JBDS 8.0.0.CR1: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1 > [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch; > {code} > git fetch origin master > git checkout FETCH_HEAD > git checkout -b jbosstools-4.2.x > git push origin jbosstools-4.2.x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and > * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. 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.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18156) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Hibernate]

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18156?page=com.atlassian.jira.plugi... ] Koen Aers closed JBIDE-18156. ----------------------------- > For JBIDE 4.2.0.CR1: Code Freeze + Branch [Hibernate] > ----------------------------------------------------- > > Key: JBIDE-18156 > URL: https://issues.jboss.org/browse/JBIDE-18156 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Mickael Istria > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [Hibernate]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1 > [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch; > {code} > git fetch origin master > git checkout FETCH_HEAD > git checkout -b jbosstools-4.2.x > git push origin jbosstools-4.2.x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and > * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. 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 Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 2014