September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15529) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [JST]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15529?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-15529: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [JST] > -------------------------------------------------- > > Key: JBIDE-15529 > URL: https://issues.jboss.org/browse/JBIDE-15529 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha2 > > > For JBIDE 4.1.1.Alpha2 [JST]: Please perform the following tasks: > 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2 > 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:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.1.Alpha2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2; > {code} > mvn clean verify -Dtpc.version=4.31.0.Alpha2 > {code} > 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch; > {code} > git checkout jbosstools-4.1.x > git pull origin jbosstools-4.1.x > git checkout -b jbosstools-4.1.1.Alpha2x > git push origin jbosstools-4.1.1.Alpha2x > {code} > 5. Close (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 JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15551) "Are you sure that you want to delete Application"-dialog shows oververbose output

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15551?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15551: ------------------------------------- Attachment: verbose-delete-application-dialog.png > "Are you sure that you want to delete Application"-dialog shows oververbose output > ---------------------------------------------------------------------------------- > > Key: JBIDE-15551 > URL: https://issues.jboss.org/browse/JBIDE-15551 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Alpha2, 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > Attachments: verbose-delete-application-dialog.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15551) "Are you sure that you want to delete Application"-dialog shows oververbose output

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15551?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15551: ------------------------------------- Steps to Reproduce: # ASSERT: make sure that you have a connection and an application listed in OpenShift Explorer # EXEC: select your application (only 1) and pick from context menu *Delete Applciation(s)* Result: !verbose-delete-application-dialog.png! Expected: Only the name, not the full listing of the application is expected. was: # ASSERT: make sure that you have a connection and an application listed in OpenShift Explorer # EXEC: select your application and pick from context menu *Delete Applciation(s)* Result: !verbose-delete-application-dialog.png! Expected: Only the name, not the full listing of the application is expected. > "Are you sure that you want to delete Application"-dialog shows oververbose output > ---------------------------------------------------------------------------------- > > Key: JBIDE-15551 > URL: https://issues.jboss.org/browse/JBIDE-15551 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Alpha2, 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15551) "Are you sure that you want to delete Application"-dialog shows oververbose output

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-15551: ---------------------------------------- Summary: "Are you sure that you want to delete Application"-dialog shows oververbose output Key: JBIDE-15551 URL: https://issues.jboss.org/browse/JBIDE-15551 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.1.Alpha2, 4.2.0.Alpha1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-171) Don't override other connectors in discovery.xml

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-171: ---------------------------------- So - the current discovery solution establishes a new generated/merged JBDSIS directory.xml file containing both JBDSIS and JBDS Core content in a single file. The Jenkins job needed to generate that xml file is JBDSIS-aggregate-disc. No content is lost as long as the previous entry URLs are preserved in the merged/new directory xml file. If this is cool with everyone, I'll close this Jira tomorrow... If not - you know what to do... :) > Don't override other connectors in discovery.xml > ------------------------------------------------ > > Key: JBTIS-171 > URL: https://issues.jboss.org/browse/JBTIS-171 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > > Currently this is in discovery plugin: > siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}" > > And instructions to test it says: > -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1 > This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together. > I suggest you use your own specific site url instead, something like: > siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}" > Then the base connectors will still work. > We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of: > in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}" > in stack: > siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15389) User should be able have its custom tail-command persisted so that he doesnt have to re-type it every time.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15389?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15389: ------------------------------------------ created a PR for master: https://github.com/jbosstools/jbosstools-openshift/pull/231 Merged and pushed it upstream/master > User should be able have its custom tail-command persisted so that he doesnt have to re-type it every time. > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15389 > URL: https://issues.jboss.org/browse/JBIDE-15389 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1 > > Attachments: tail-files.png > > > When doing tail-files for an app the user gets the tail-command in a dialog. He then can provide his very own cmd. > !tail-files.png! > Unfortunately whatever he's providing is not persisted. He has to re-type it every time he wants to tail the files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15389) User should be able have its custom tail-command persisted so that he doesnt have to re-type it every time.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15389?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15389: ------------------------------------------ merged PR upstream/jbosstools-4.1.x > User should be able have its custom tail-command persisted so that he doesnt have to re-type it every time. > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15389 > URL: https://issues.jboss.org/browse/JBIDE-15389 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1 > > Attachments: tail-files.png > > > When doing tail-files for an app the user gets the tail-command in a dialog. He then can provide his very own cmd. > !tail-files.png! > Unfortunately whatever he's providing is not persisted. He has to re-type it every time he wants to tail the files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2767: ----------------------------- Fix Version/s: 7.1.0.Alpha2 (was: 7.1.0.Beta1) > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha2 > > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2767: ---------------------------------- Based on [~rob.stryker]'s PR review, applied in 4.1.x and master branches. > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15484) Provide support for scaled app when tailing log files

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15484?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15484: ---------------------------------- Fix Version/s: 4.1.1.Beta1 (was: 4.1.1.Alpha2) > Provide support for scaled app when tailing log files > ----------------------------------------------------- > > Key: JBIDE-15484 > URL: https://issues.jboss.org/browse/JBIDE-15484 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > > Seems like it's simply a matter of adding a '--gears' parameter in the ssh command when the application is scalable. > The dialog could provide a checkbox (enabled by default) to let the user choose whether she wants to grab all logs or just those on the HA-Proxy > See [~lincolnthree]'s blog post on the subject: http://ocpsoft.org/jboss/openshift-pro-tip-scaling-tail-server-logs-on-al... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 2013