December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-12141) Application wizard: Provide support for creating OpenShift Instant Applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12141?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12141: ------------------------------------- Labels: application_wizard (was: ) > Application wizard: Provide support for creating OpenShift Instant Applications > ------------------------------------------------------------------------------- > > Key: JBIDE-12141 > URL: https://issues.jboss.org/browse/JBIDE-12141 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Labels: application_wizard > Fix For: LATER > > > Currently available Instant applications on OpenShift (at the mmt just experimental): > * Kitchensink Example > * WordPress > * Drupal > * Ruby on Rails > Here's a screencast that shows how Drupal and Wordpress can be deployed to OpenShift in a few clicks via the Web UI: http://www.youtube.com/watch?v=3Nn5yh5YKio -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12141) Application wizard: Provide support for creating OpenShift Instant Applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12141?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12141: ------------------------------------- Assignee: (was: Andre Dietisheim) > Application wizard: Provide support for creating OpenShift Instant Applications > ------------------------------------------------------------------------------- > > Key: JBIDE-12141 > URL: https://issues.jboss.org/browse/JBIDE-12141 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Stefan Bunciak > Labels: application_wizard > Fix For: LATER > > > Currently available Instant applications on OpenShift (at the mmt just experimental): > * Kitchensink Example > * WordPress > * Drupal > * Ruby on Rails > Here's a screencast that shows how Drupal and Wordpress can be deployed to OpenShift in a few clicks via the Web UI: http://www.youtube.com/watch?v=3Nn5yh5YKio -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12141) Application wizard: Provide support for creating OpenShift Instant Applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12141?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12141: ------------------------------------- Estimated Difficulty: High > Application wizard: Provide support for creating OpenShift Instant Applications > ------------------------------------------------------------------------------- > > Key: JBIDE-12141 > URL: https://issues.jboss.org/browse/JBIDE-12141 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Stefan Bunciak > Labels: application_wizard > Fix For: LATER > > > Currently available Instant applications on OpenShift (at the mmt just experimental): > * Kitchensink Example > * WordPress > * Drupal > * Ruby on Rails > Here's a screencast that shows how Drupal and Wordpress can be deployed to OpenShift in a few clicks via the Web UI: http://www.youtube.com/watch?v=3Nn5yh5YKio -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12013) Application wizard, Embedding wizard: disallow all non-scalable cartridges for scalable applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12013?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12013: ------------------------------------- Assignee: (was: Andre Dietisheim) > Application wizard, Embedding wizard: disallow all non-scalable cartridges for scalable applications > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-12013 > URL: https://issues.jboss.org/browse/JBIDE-12013 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta3 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: LATER > > Attachments: can-only-embed-mysql-and-jenkins.png, can-only-embed-mysql-and-jenkins.png > > > # EXEC: open the *New OpenShift Application* wizard > # EXEC: check *enable scaling* > # EXEC: check *phpmysql* embedded cartridge > # EXEC: hit *Finish* > Result: > You get the following error: > !can-only-embed-mysql-and-jenkins.png! > Only *mysql*, *mongodb*, *postgres* and *jenkins-client* may be embedded to scalable apps! > IMHO we should not hardcode any list of allowed embeddable cartridges since this list would get outdated very quickly. The backend should allow us to query such a list. Since there's no cartridge metadata yet, we currently have a local embedding strategy. This should get enhanced to disallow certrain cartridges for scalable applications -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12013) Application wizard, Embedding wizard: disallow all non-scalable cartridges for scalable applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12013?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12013: ------------------------------------- Labels: application_wizard embed_wizard (was: ) Estimated Difficulty: High > Application wizard, Embedding wizard: disallow all non-scalable cartridges for scalable applications > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-12013 > URL: https://issues.jboss.org/browse/JBIDE-12013 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta3 > Reporter: Andre Dietisheim > Priority: Minor > Labels: application_wizard, embed_wizard > Fix For: LATER > > Attachments: can-only-embed-mysql-and-jenkins.png, can-only-embed-mysql-and-jenkins.png > > > # EXEC: open the *New OpenShift Application* wizard > # EXEC: check *enable scaling* > # EXEC: check *phpmysql* embedded cartridge > # EXEC: hit *Finish* > Result: > You get the following error: > !can-only-embed-mysql-and-jenkins.png! > Only *mysql*, *mongodb*, *postgres* and *jenkins-client* may be embedded to scalable apps! > IMHO we should not hardcode any list of allowed embeddable cartridges since this list would get outdated very quickly. The backend should allow us to query such a list. Since there's no cartridge metadata yet, we currently have a local embedding strategy. This should get enhanced to disallow certrain cartridges for scalable applications -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12143) Create core plugin

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12143?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12143: ------------------------------------- Assignee: (was: Andre Dietisheim) > Create core plugin > ------------------ > > Key: JBIDE-12143 > URL: https://issues.jboss.org/browse/JBIDE-12143 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Andre Dietisheim > Fix For: LATER > > > We currently only have a *org.jboss.tools.openshift.express.ui* plugin which holds core and ui components. We should factor the core components out and put them into their own plugin *org.jboss.tools.openshift.express.core* -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12143) Create core plugin

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12143?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12143: ------------------------------------- Estimated Difficulty: Medium > Create core plugin > ------------------ > > Key: JBIDE-12143 > URL: https://issues.jboss.org/browse/JBIDE-12143 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Andre Dietisheim > Fix For: LATER > > > We currently only have a *org.jboss.tools.openshift.express.ui* plugin which holds core and ui components. We should factor the core components out and put them into their own plugin *org.jboss.tools.openshift.express.core* -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12144) EGitUtils#push is throwing an exception if push fails. It should use the same semantics as EGit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12144?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12144: ------------------------------------- Assignee: (was: Andre Dietisheim) > EGitUtils#push is throwing an exception if push fails. It should use the same semantics as EGit > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-12144 > URL: https://issues.jboss.org/browse/JBIDE-12144 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Andre Dietisheim > Priority: Minor > Labels: cleanup > Fix For: LATER > > > EgitUtils#push throws an exception if the push failed because of ex. "non fastforward push". > {code} > private static PushOperationResult push(Repository repository, RemoteConfig remoteConfig, boolean force, IProgressMonitor monitor) throws CoreException { > ... > PushOperationResult pushResult = op.getOperationResult(); > if (hasFailedEntries(pushResult)) { > throw new CoreException( > EGitCoreActivator.createErrorStatus( > NLS.bind("Could not push repository {0}: {1}", > repository.toString(), getErrors(pushResult)) > , null)); > } > return pushResult; > {code} > EGit is not throwing an exception in this case. You simply get the failure in the PushResult object you'll have to look at. > EGitUtils#push is thus changing the API semantics of EGit and it shouldn't. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12144) EGitUtils#push is throwing an exception if push fails. It should use the same semantics as EGit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12144?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12144: ------------------------------------- Estimated Difficulty: Low > EGitUtils#push is throwing an exception if push fails. It should use the same semantics as EGit > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-12144 > URL: https://issues.jboss.org/browse/JBIDE-12144 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Andre Dietisheim > Priority: Minor > Labels: cleanup > Fix For: LATER > > > EgitUtils#push throws an exception if the push failed because of ex. "non fastforward push". > {code} > private static PushOperationResult push(Repository repository, RemoteConfig remoteConfig, boolean force, IProgressMonitor monitor) throws CoreException { > ... > PushOperationResult pushResult = op.getOperationResult(); > if (hasFailedEntries(pushResult)) { > throw new CoreException( > EGitCoreActivator.createErrorStatus( > NLS.bind("Could not push repository {0}: {1}", > repository.toString(), getErrors(pushResult)) > , null)); > } > return pushResult; > {code} > EGit is not throwing an exception in this case. You simply get the failure in the PushResult object you'll have to look at. > EGitUtils#push is thus changing the API semantics of EGit and it shouldn't. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11839) Appliaction wizard: if openshift project has .project in its root it should be imported as an eclipse project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11839?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11839: ------------------------------------- Summary: Appliaction wizard: if openshift project has .project in its root it should be imported as an eclipse project (was: if openshift project has .project in its root it should be imported as an eclipse project) > Appliaction wizard: if openshift project has .project in its root it should be imported as an eclipse project > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-11839 > URL: https://issues.jboss.org/browse/JBIDE-11839 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Minor > Fix For: LATER > > > we currently import either pom or general project - if users commit their .project file we should honor that. -- 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, 3 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