January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9762) Openshift Express: add #getUrl and #getGitUri to Application

by Andre Dietisheim (JIRA)

Openshift Express: add #getUrl and #getGitUri to Application ------------------------------------------------------------ Key: JBIDE-9762 URL: https://issues.jboss.org/browse/JBIDE-9762 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M4 Currently there's no way to find out about the url an openshift application is reachable at. We could offer this on the Application class with a method #getUrl. There's also no way currently to find out in what repo this application is reachable. We could offer this via a #getGitUri method on the Application class. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
6
0 / 0

[JBoss JIRA] (JBIDE-9925) rename all occurrences of "Openshift" in code, javadoc, comment, xml etc. to "OpenShift"

by Andre Dietisheim (Created) (JIRA)

rename all occurrences of "Openshift" in code, javadoc, comment, xml etc. to "OpenShift" ---------------------------------------------------------------------------------------- Key: JBIDE-9925 URL: https://issues.jboss.org/browse/JBIDE-9925 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M4 The correct name of OpenShift is spelled with 2 capital letters in O and S: "Openshift". We used the wrong spelling with a small "s" so far. We need to correct this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9781) Openshift Express: User#createDomain should be available so that you may create a domain initially

by Andre Dietisheim (JIRA)

Openshift Express: User#createDomain should be available so that you may create a domain initially -------------------------------------------------------------------------------------------------- Key: JBIDE-9781 URL: https://issues.jboss.org/browse/JBIDE-9781 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M4 The current usage scheme of the openshift express client is the following: {code} User user = new User(username, password); IDomain domain = user.createDomain(name); IApplication application = user.createApplication(name, cartridge); ... {code} there's currently no User#createDomain(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9813) Openshift Express: implement IDomain#setNamespace

by Andre Dietisheim (JIRA)

Openshift Express: implement IDomain#setNamespace ------------------------------------------------- Key: JBIDE-9813 URL: https://issues.jboss.org/browse/JBIDE-9813 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M4 Currently there's no way in IDomain to change the namespace. You'd have to go for the service: IOpenshiftService#changeDomain. Since my implementation tries to hide the service and provide transparent access on behalf of an object graph (User, Domain, Application, SShPublicKey, etc.) we need a way to change the namespace of the domain on the IDomain object. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9819) Openshift Express: provide existing system settings

by Andre Dietisheim (JIRA)

Openshift Express: provide existing system settings --------------------------------------------------- Key: JBIDE-9819 URL: https://issues.jboss.org/browse/JBIDE-9819 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Andre Dietisheim The current jboss tooling for openshift express does not read the settings that the rhc tooling would have created. We need to close this gap. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
4
0 / 0

[JBoss JIRA] (JBIDE-9841) Openshift Express: rename org.jboss.ide.eclipse.as.openshift.* plugins to org.jboss.tools.openshift.*

by Andre Dietisheim (Created) (JIRA)

Openshift Express: rename org.jboss.ide.eclipse.as.openshift.* plugins to org.jboss.tools.openshift.* ----------------------------------------------------------------------------------------------------- Key: JBIDE-9841 URL: https://issues.jboss.org/browse/JBIDE-9841 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M4 the are currently 3 plugins for openshift: * org.jboss.ide.eclipse.as.openshift.core: REST client * org.jboss.ide.eclipse.as.openshift.test: tests for the REST client * org.jboss.ide.eclipse.as.openshift.ui: UI, mainly a wizard to create a server adapter and deal with openshift apps and domains They all shall renamed to org.jboss.tools.openshift.* -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
4
0 / 0

[JBoss JIRA] (JBDS-1884) JBDS links to old Getting Started Guide in 5.0.0

by Nick Boldt (Created) (JIRA)

JBDS links to old Getting Started Guide in 5.0.0 ------------------------------------------------ Key: JBDS-1884 URL: https://issues.jboss.org/browse/JBDS-1884 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: documentation, Welcome Affects Versions: 4.1.1.M2, 5.0.0.M4 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.1.1.Final, 5.0.0.M4 Fire up JBDS. Help > Welcome > Getting Started > Gettng Started with JBoss Developer Studio Note that the content looks like http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html/Getting... rather than the 4.1 or 5.0 docs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
3
0 / 0

[JBoss JIRA] (JBIDE-10215) Archetypes should have cheatsheets like the project examples

by Burr Sutter (Created) (JIRA)

Archetypes should have cheatsheets like the project examples ------------------------------------------------------------ Key: JBIDE-10215 URL: https://issues.jboss.org/browse/JBIDE-10215 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Reporter: Burr Sutter Assignee: Fred Bricon Attachments: Screen Shot 2011-11-22 at 11.06.56 AM.png In a recent usability exercise, the cheatsheets were popular. Can we add them to the key archetypes that are found on File New (JBoss Perspective) and on JBoss Central? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

8
8
0 / 0

[JBoss JIRA] Created: (JBIDE-9057) Update the maven plugins' manifests to use m2e 0.13/1.0

by Fred Bricon (JIRA)

Update the maven plugins' manifests to use m2e 0.13/1.0 ------------------------------------------------------- Key: JBIDE-9057 URL: https://issues.jboss.org/browse/JBIDE-9057 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 3.2.1.Final Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 3.2.2 We need to provide integration for m2e 0.13/1.0 in JBT 3.2.x. That means backporting the current code from trunk to the 3.2.X branch. According to Snjezana, there are no dependencies on new code/features from JBT 3.3.0, so it should be pretty straightforward. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
6
0 / 0

[JBoss JIRA] (JBIDE-10430) Regression for JBossAS 7.1: configured runtime not selectable

by Juergen Zimmermann (Created) (JIRA)

Regression for JBossAS 7.1: configured runtime not selectable ------------------------------------------------------------- Key: JBIDE-10430 URL: https://issues.jboss.org/browse/JBIDE-10430 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Reporter: Juergen Zimmermann Assignee: Rob Stryker I tried to upgrade from M4 to jbosstools-3.3_stable_branch.aggregate-Update-2011-12-09_00-34-40-H51 which I downloaded from http://downloads.jboss.org/jbosstools/builds/nightly/core/3.3.indigo/2011.... However, I got 2 problems: a) The targeted runtime of an EJB project is visible, but the according JARs are *NOT* appended to the classpath resp. buildpath. b) In a utility project I cannot add the server library although the server itself is configured. I'll attach 3 screenshots: 1) 1_M4_ok shows the regular behavior when using M4. 2) 2_M5_targeted_runtime_not_in_classpath shows that the server runtime is configured, but the according jars are not part of the buildpath in an ejb project. 3) 3_M5_no_selectable_runtime_for_utility_project shows that adding a server library doesn't work because the configured server runtime is not listed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

10
12
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 January 2012