March 2013 - jbosstools-issues - Jboss List Archives

[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.2.Final (was: 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 > Priority: Critical > Fix For: 4.0.2.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] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13869: ---------------------------------------- Fix Version/s: 4.0.2.Final 4.1.0.Alpha2 Description: Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild everything again. Possible options: 1) Create new testsuite that depends on all other testsuites and run them in surefire test. 2) use something else than surefire to run the already built testsuites. Priority: Critical (was: Major) Assignee: Mickael Istria Component/s: Build/Releng Michael, can you do a spike on this ? > Find a way to run testsuite against existing builds but with different TP without requiring publishing > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13869 > URL: https://issues.jboss.org/browse/JBIDE-13869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.0.2.Final, 4.1.0.Alpha2 > > > Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild everything again. > Possible options: > 1) Create new testsuite that depends on all other testsuites and run them in surefire test. > 2) use something else than surefire to run the already built testsuites. -- 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-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-13869: ------------------------------------------- Summary: Find a way to run testsuite against existing builds but with different TP without requiring publishing Key: JBIDE-13869 URL: https://issues.jboss.org/browse/JBIDE-13869 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Max Rydahl Andersen -- 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-13868) Project Archives incorrectly loading saved .packages

by Rafael Sisto (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13868?page=com.atlassian.jira.plugi... ] Rafael Sisto updated JBIDE-13868: --------------------------------- Attachment: loaded packages.png This is how the loaded .packages looks like. It should load also the war and jar files... > Project Archives incorrectly loading saved .packages > ---------------------------------------------------- > > Key: JBIDE-13868 > URL: https://issues.jboss.org/browse/JBIDE-13868 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Affects Versions: 4.0.0.Final > Environment: Eclipse juno 32 bit > Reporter: Rafael Sisto > Assignee: Rob Stryker > Attachments: .packages, loaded packages.png > > > After creating a project archive from the Project Archives window, consisting of a war file, a jar file and EarContent folder it creates the ear successfully. > After restarting eclipse (or closing and opening the project) the Project Archive does not load the jar and war archives, only the EarContent fileset. > Testing a little further, adding only a jar archive and a fileset works, but when adding the second jar (war in this case), the project archives loads only the fileset, discarding both jars. -- 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-13868) Project Archives incorrectly loading saved .packages

by Rafael Sisto (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13868?page=com.atlassian.jira.plugi... ] Rafael Sisto updated JBIDE-13868: --------------------------------- Attachment: .packages This is the generated .packages file. > Project Archives incorrectly loading saved .packages > ---------------------------------------------------- > > Key: JBIDE-13868 > URL: https://issues.jboss.org/browse/JBIDE-13868 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Affects Versions: 4.0.0.Final > Environment: Eclipse juno 32 bit > Reporter: Rafael Sisto > Assignee: Rob Stryker > Attachments: .packages > > > After creating a project archive from the Project Archives window, consisting of a war file, a jar file and EarContent folder it creates the ear successfully. > After restarting eclipse (or closing and opening the project) the Project Archive does not load the jar and war archives, only the EarContent fileset. > Testing a little further, adding only a jar archive and a fileset works, but when adding the second jar (war in this case), the project archives loads only the fileset, discarding both jars. -- 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-13868) Project Archives incorrectly loading saved .packages

by Rafael Sisto (JIRA)

Rafael Sisto created JBIDE-13868: ------------------------------------ Summary: Project Archives incorrectly loading saved .packages Key: JBIDE-13868 URL: https://issues.jboss.org/browse/JBIDE-13868 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Archives Affects Versions: 4.0.0.Final Environment: Eclipse juno 32 bit Reporter: Rafael Sisto Assignee: Rob Stryker After creating a project archive from the Project Archives window, consisting of a war file, a jar file and EarContent folder it creates the ear successfully. After restarting eclipse (or closing and opening the project) the Project Archive does not load the jar and war archives, only the EarContent fileset. Testing a little further, adding only a jar archive and a fileset works, but when adding the second jar (war in this case), the project archives loads only the fileset, discarding both jars. -- 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 Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13865?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-13865: ----------------------------------------------- The wrong code appeared after fix to JBIDE-10225 in December 2011. > 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] (JBIDE-13867) openshift-java-client: remove ICartridge#getLogLocation which is not needed any more

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13867?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13867: ------------------------------------------ pushed to client master and using the latest client lib in the client bundle > openshift-java-client: remove ICartridge#getLogLocation which is not needed any more > ------------------------------------------------------------------------------------ > > Key: JBIDE-13867 > URL: https://issues.jboss.org/browse/JBIDE-13867 > 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.0.Alpha2 > > > The ICartridge interface still has #getLogLocation which is still from the times when we hard subclasses of the cartridges. We dont need this anymore and should remove it / clean it up. -- 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-13867) openshift-java-client: remove ICartridge#getLogLocation which is not needed any more

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-13867: ---------------------------------------- Summary: openshift-java-client: remove ICartridge#getLogLocation which is not needed any more Key: JBIDE-13867 URL: https://issues.jboss.org/browse/JBIDE-13867 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.0.Alpha2 The ICartridge interface still has #getLogLocation which is still from the times when we hard subclasses of the cartridges. We dont need this anymore and should remove it / clean it up. -- 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: ------------------------------------- Description: We currently still have hard coded (standalone) cartridges in our integration tests (not the client code which is not depending on specific cartridges). If we want to have the OpenShift team running our integration test we have to remove those. This is because they may replace existing by new cartridges and therefore can't run our integration tests against new DEVENVs (ex. a dev pinged me and told me he was working on upgrading the php cartridge to a higher version). (was: We currently still have hard coded (standalone) cartr) > 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) cartridges in our integration tests (not the client code which is not depending on specific cartridges). If we want to have the OpenShift team running our integration test we have to remove those. This is because they may replace existing by new cartridges and therefore can't run our integration tests against new DEVENVs (ex. a dev pinged me and told me he was working on upgrading the php cartridge to a higher version). -- 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