December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15655) Application Wizard: errors "you have to choose an application name" even though I have chose an existing app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15655?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15655: ------------------------------------- Summary: Application Wizard: errors "you have to choose an application name" even though I have chose an existing app (was: openshift import wizard: errors "you have to choose an application name" even though I have chose an existing app) > Application Wizard: errors "you have to choose an application name" even though I have chose an existing app > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-15655 > URL: https://issues.jboss.org/browse/JBIDE-15655 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: have-to-choose-application-name.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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15655) Application Wizard: errors "you have to choose an application name" even though I have chose an existing app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15655?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15655: ------------------------------------- Labels: application_wizard (was: ) > Application Wizard: errors "you have to choose an application name" even though I have chose an existing app > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-15655 > URL: https://issues.jboss.org/browse/JBIDE-15655 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard > Fix For: 4.2.x > > Attachments: have-to-choose-application-name.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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13862) server adapter wizard: When creating adapter manually, the deploying project should be added automatically

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13862?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13862: ------------------------------------- Labels: server_adapter_wizard (was: ) > server adapter wizard: When creating adapter manually, the deploying project should be added automatically > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13862 > URL: https://issues.jboss.org/browse/JBIDE-13862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Max Rydahl Andersen > Priority: Minor > Labels: server_adapter_wizard > Fix For: 4.2.x > > Attachments: server.png, server1.png, server2.png > > > Deploying project is automatically added to OpenShift Server adapter after application import: > * after application import contains the deploying project: !server.png|thumbnail! > When created manually via OpenShift Explorer (Application - Create Server Adapter), the deploying project is not automatically added, even though I'm selecting the deploying project: > * !server2.png|thumbnail! *->* !server1.png|thumbnail! -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16270) Server component on jbosstools-4.2.0.Alpha1x doesn't build

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16270?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-16270. ------------------------------------ Resolution: Done Yes, it's working well now and Alpha1 is on its way. Thanks. > Server component on jbosstools-4.2.0.Alpha1x doesn't build > ---------------------------------------------------------- > > Key: JBIDE-16270 > URL: https://issues.jboss.org/browse/JBIDE-16270 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, server > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Because of inconsistent version across pom files, jbosstools-server component doesn't build from branch jbosstools-4.2.0.Alpha1x. See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... for more details. The error should be reproducible locally with > {code} > $ cd jbosstools-server/ > $ git fetch jbosstools jbosstools-4.2.0.Alpha1x > $ git checkout FETCH_HEAD > # Clean local repo to make sure build doesn't rely on other unexpected stuff > $ rm -r ~/.m2/repository/org/jboss/tools/ > $ mvn clean verify > {code} > As soon as you've fixed that, please trigger a new build from jenkins: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13862) server adapter wizard: When creating adapter manually, the deploying project should be added automatically

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13862?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-13862: ---------------------------------------- Assignee: Rob Stryker (was: Max Rydahl Andersen) [~rob.stryker] I'm not aware of all implications in having a module or not. Can you please comment? > server adapter wizard: When creating adapter manually, the deploying project should be added automatically > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13862 > URL: https://issues.jboss.org/browse/JBIDE-13862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Rob Stryker > Priority: Minor > Labels: server_adapter_wizard > Fix For: 4.2.x > > Attachments: server.png, server1.png, server2.png > > > Deploying project is automatically added to OpenShift Server adapter after application import: > * after application import contains the deploying project: !server.png|thumbnail! > When created manually via OpenShift Explorer (Application - Create Server Adapter), the deploying project is not automatically added, even though I'm selecting the deploying project: > * !server2.png|thumbnail! *->* !server1.png|thumbnail! -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16270) Server component on jbosstools-4.2.0.Alpha1x doesn't build

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16270?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16270: ------------------------------------- A commit was made earlier today. Let's see if it helps. Was built locally. > Server component on jbosstools-4.2.0.Alpha1x doesn't build > ---------------------------------------------------------- > > Key: JBIDE-16270 > URL: https://issues.jboss.org/browse/JBIDE-16270 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, server > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Because of inconsistent version across pom files, jbosstools-server component doesn't build from branch jbosstools-4.2.0.Alpha1x. See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... for more details. The error should be reproducible locally with > {code} > $ cd jbosstools-server/ > $ git fetch jbosstools jbosstools-4.2.0.Alpha1x > $ git checkout FETCH_HEAD > # Clean local repo to make sure build doesn't rely on other unexpected stuff > $ rm -r ~/.m2/repository/org/jboss/tools/ > $ mvn clean verify > {code} > As soon as you've fixed that, please trigger a new build from jenkins: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16108) Preferences: Timeout preferences should not set system properties but operation specific timeout

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16108?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16108: ------------------------------------- Summary: Preferences: Timeout preferences should not set system properties but operation specific timeout (was: Eclipse Preferences: Timeout preferences should not set system properties but operation specific timeout) > Preferences: Timeout preferences should not set system properties but operation specific timeout > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-16108 > URL: https://issues.jboss.org/browse/JBIDE-16108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > > In JBIDE-16046 we introduced an Eclipse Preferences to set the openshift-java-clilent timeouts. These preferences currently set the lib specific system property which is not good. Consider the following usecase: > 1) User launches Eclipse and has system property set to 10000 (-D): Eclipse Preferences display 10000 > 2) User sets preference to 1234 > 3) restarts Ecllipse: Preferences display 1234 > 3) happens because we load the value from eclipse preferences and override the system property > We should keep both separate: System property and Eclipse preferences: > We use operation specific timeouts in all Eclipse code and make the Eclipse preferences provide some value for this. Leaving the system property alone. > We should also: > * add a checkbox for "[ ] use default" > * change openshift-java-client to differentiate "no value" (<0) and value set (>=0) > * remove current hard-coded safe default in openshift-java-client, replace it by system-property we already have). -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16108) Preferences: Timeout preferences should not set system properties but operation specific timeout

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16108?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16108: ------------------------------------- Labels: preferences (was: ) > Preferences: Timeout preferences should not set system properties but operation specific timeout > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-16108 > URL: https://issues.jboss.org/browse/JBIDE-16108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: preferences > Fix For: 4.2.x > > > In JBIDE-16046 we introduced an Eclipse Preferences to set the openshift-java-clilent timeouts. These preferences currently set the lib specific system property which is not good. Consider the following usecase: > 1) User launches Eclipse and has system property set to 10000 (-D): Eclipse Preferences display 10000 > 2) User sets preference to 1234 > 3) restarts Ecllipse: Preferences display 1234 > 3) happens because we load the value from eclipse preferences and override the system property > We should keep both separate: System property and Eclipse preferences: > We use operation specific timeouts in all Eclipse code and make the Eclipse preferences provide some value for this. Leaving the system property alone. > We should also: > * add a checkbox for "[ ] use default" > * change openshift-java-client to differentiate "no value" (<0) and value set (>=0) > * remove current hard-coded safe default in openshift-java-client, replace it by system-property we already have). -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15495) Server Adapter: publish locks the whole workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15495: ------------------------------------- Summary: Server Adapter: publish locks the whole workspace (was: OpenShift server adapter: publish locks the whole workspace) > Server Adapter: publish locks the whole workspace > ------------------------------------------------- > > Key: JBIDE-15495 > URL: https://issues.jboss.org/browse/JBIDE-15495 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Labels: openshift_server_adapter > Fix For: 4.2.x > > Attachments: Screen Shot 2013-09-17 at 10.42.43 AM.png > > > Have 2 projects in a workspace, one of them is an OpenShift application > Deploy some changes on OpenShift, and while the publication is performed (git push, then OS restarts the server), go to the second (unrelated) project and try to move a file from a package to another package in the same project. > The 'Publish' operation locked the whoel workspace, which means that the move operation needs to wait. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16129) Environment Variables wizard: Refresh should warn that it'll undo all changes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16129?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16129: ------------------------------------- Labels: env_var_wizard (was: ) > Environment Variables wizard: Refresh should warn that it'll undo all changes > ----------------------------------------------------------------------------- > > Key: JBIDE-16129 > URL: https://issues.jboss.org/browse/JBIDE-16129 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: env_var_wizard > Fix For: 4.2.x > > > In Edit Environment variables shell the Refresh button undo local changes - all changes upon local variables (removed/added/modified) are commited after click on Finish button. So if someone try to modify more environment variables and then "accidentally" click on Refresh button, then all local changes are disposed and variables are refreshed from server. There should be probably some warning before this action to let the user be sure about consequences of his action. -- 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, 4 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 December 2013