March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13866) openshift-java-client: remove hard coded cartridges (ICartridge, ex. ICartridge.JBOSSAS_7) from tests

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-13866: ---------------------------------------- Summary: openshift-java-client: remove hard coded cartridges (ICartridge, ex. ICartridge.JBOSSAS_7) from tests Key: JBIDE-13866 URL: https://issues.jboss.org/browse/JBIDE-13866 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.1.0.Alpha2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.x We currently still have hard coded (standalone) cartr -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13866) openshift-java-client: remove hard coded (standalone) cartridges from tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13866?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13866: ------------------------------------- Summary: openshift-java-client: remove hard coded (standalone) cartridges from tests (was: openshift-java-client: remove hard coded cartridges (ICartridge, ex. ICartridge.JBOSSAS_7) from tests) > openshift-java-client: remove hard coded (standalone) cartridges from tests > --------------------------------------------------------------------------- > > Key: JBIDE-13866 > URL: https://issues.jboss.org/browse/JBIDE-13866 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.x > > > We currently still have hard coded (standalone) cartr -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13865) Class ProgressPart disposes system cursors

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13865?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13865: --------------------------------------------- +1 for this fix - I can't imagine when this code was ever correct; but i can see how juno/kepler would be affected more. > Class ProgressPart disposes system cursors > ------------------------------------------ > > Key: JBIDE-13865 > URL: https://issues.jboss.org/browse/JBIDE-13865 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > This causes https://issues.jboss.org/browse/JBDS-2503 > Only Add Custom Capabilities wizard creates progress monitor based on this class, so that the issue can be reproduced only by adding custom capabilities as described in JBDS-2503. > After wizard completes, it is impossible to work in Eclipse, because system wait cursor is disposed, and almost all jobs in Eclipse invoke that cursor. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2466) Links to target platform on JBDS builds download page are not valid and page is mentioning Eclipse Juno instead of Eclipse Kepler as TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2466?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2466. ---------------------------- Cleaned up and happier: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_tr... See also JBDS-2428, JBIDE-13452. > Links to target platform on JBDS builds download page are not valid and page is mentioning Eclipse Juno instead of Eclipse Kepler as TP > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2466 > URL: https://issues.jboss.org/browse/JBDS-2466 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.0.0.Alpha1 > Environment: http://www.qa.jboss.com/binaries/RHDS/builds/development/7.0.0.Alpha1.ins... > Reporter: Vlado Pakan > Assignee: Nick Boldt > Fix For: 7.0.0.Alpha2 > > Attachments: JBIDE13452_JBDS2466.remove.JBDS_VERSION_clean.up.results.html.patch.txt > > -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13865) Class ProgressPart disposes system cursors

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13865?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13865: ----------------------------------- Fix Version/s: 4.0.1.Final > Class ProgressPart disposes system cursors > ------------------------------------------ > > Key: JBIDE-13865 > URL: https://issues.jboss.org/browse/JBIDE-13865 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > This causes https://issues.jboss.org/browse/JBDS-2503 > Only Add Custom Capabilities wizard creates progress monitor based on this class, so that the issue can be reproduced only by adding custom capabilities as described in JBDS-2503. > After wizard completes, it is impossible to work in Eclipse, because system wait cursor is disposed, and almost all jobs in Eclipse invoke that cursor. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2503) JBoss EAP developer studio - Issue while adding custom capability

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-2503?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-2503: --------------------------------- Fix Version/s: 6.0.1.GA > JBoss EAP developer studio - Issue while adding custom capability > ----------------------------------------------------------------- > > Key: JBDS-2503 > URL: https://issues.jboss.org/browse/JBDS-2503 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jsf > Affects Versions: 6.0.0.GA > Environment: Windows > Reporter: Chandrashekhar Tupe > Assignee: Viacheslav Kabanovich > Fix For: 6.0.1.GA, 7.0.0.Alpha2 > > Attachments: logfile.txt > > > I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app. > Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid". > This happened to me twice and I had to create a new workspace and reconfigure everything from scratch. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13865) Class ProgressPart disposes system cursors

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13865?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13865: ----------------------------------- Priority: Critical (was: Major) > Class ProgressPart disposes system cursors > ------------------------------------------ > > Key: JBIDE-13865 > URL: https://issues.jboss.org/browse/JBIDE-13865 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > This causes https://issues.jboss.org/browse/JBDS-2503 > Only Add Custom Capabilities wizard creates progress monitor based on this class, so that the issue can be reproduced only by adding custom capabilities as described in JBDS-2503. > After wizard completes, it is impossible to work in Eclipse, because system wait cursor is disposed, and almost all jobs in Eclipse invoke that cursor. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2503) JBoss EAP developer studio - Issue while adding custom capability

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-2503?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-2503: --------------------------------- Priority: Critical (was: Major) > JBoss EAP developer studio - Issue while adding custom capability > ----------------------------------------------------------------- > > Key: JBDS-2503 > URL: https://issues.jboss.org/browse/JBDS-2503 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jsf > Affects Versions: 6.0.0.GA > Environment: Windows > Reporter: Chandrashekhar Tupe > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 6.0.1.GA, 7.0.0.Alpha2 > > Attachments: logfile.txt > > > I am evaluating JBoss EAP and developer studio. Created an enterprise application and wanted to add richface capability to the web app. > Via context menu clicked on add custom capabilities and selected richfaces 3.3 (no jars only file filters). Since I did not have web.xml it prompted em to add one and I canceled the operation. There after for any operation I get a dialogue "An internal error has occured" with details "Argument not valid". > This happened to me twice and I had to create a new workspace and reconfigure everything from scratch. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13452) investigate removing JBT_VERSION, JBDS_VERSION from parent pom

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13452?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13452. ------------------------------ Happiness is dependency on generated values instead of hard-coded ones. Closing. JBT_VERSION and JBDS_VERSION are dead, long live $\{project.version\} ! > investigate removing JBT_VERSION, JBDS_VERSION from parent pom > -------------------------------------------------------------- > > Key: JBIDE-13452 > URL: https://issues.jboss.org/browse/JBIDE-13452 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, target-platform, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION (min and max) from parent pom > Can we switch to using dynamic maven variables like project.version instead? > Moving forward, jobs will override/set the version of target platform used to build (min) and test (max), and developers will be required to decide when/if to move to a newer parent pom or target platform version(s) if needed. For projects that are released, jobs will run only when TP changes (ie., will watch the jbosstools-target-platforms repo for changes). -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2428) refactor JBDS build so it's not "updatesite" and "product" because URLs are confusing and non-intuitive

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2428?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2428: ----------------------------- Status: Closed (was: Pull Request Sent) Resolution: Done Jobs are now called devstudio.product_70 and devstudio.product_trunk. Folder structure mirrors that of JBT builds: * all/repo/ - exploded update site * installer/ - HTML page with links to installers, sources, update site zip + logs and other meta * logs/ - logs & other metadata So... that's better. Closing. > refactor JBDS build so it's not "updatesite" and "product" because URLs are confusing and non-intuitive > ------------------------------------------------------------------------------------------------------- > > Key: JBDS-2428 > URL: https://issues.jboss.org/browse/JBDS-2428 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, installer, updatesite > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Alpha2 > > > Results of a JBDS build end up here: > http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... > with these folders: > {code} > product/ (is actually an update site, not a product) > installer/ > logs/ > extras/ (should no longer appear but keeps coming back from an old cache from somewhere?!?) > extras*.zip* (should no longer appear but keeps coming back from an old cache from somewhere?!?) > all/ (duplicates contents of product/ folder; don't need both) > {code} > We should rename the job from .updatesite to .product, and rename product/ to site/, so we end up with this: > http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.1_stable... > instead of this: > http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_stable... > Should also remove the crufty leftovers (all, extras*) -- 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

13 years

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