[JBoss JIRA] (JBIDE-12571) Connection wizard: Eclipse preferences: allow users to define a default server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12571?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12571:
-------------------------------------
Labels: connection_wizard new_and_noteworthy (was: new_and_noteworthy)
> Connection wizard: Eclipse preferences: allow users to define a default server
> ------------------------------------------------------------------------------
>
> Key: JBIDE-12571
> URL: https://issues.jboss.org/browse/JBIDE-12571
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: connection_wizard, new_and_noteworthy
> Fix For: 4.2.x
>
> Attachments: 2012-09-10 13.10.bmml, 2012-09-10 13.10.bmml, 2012-09-10 13.10.png
>
>
> Add UI to the preferences that allows users to provide a default OpenShift server to connect to. In terms of widget we need a text-field for the server url and a checkbox that allows people to refer to the default server that is defined in the openshift configfurations (~/.openshift/express.conf and /etc/openshift/express.conf). If the checkbox is checked, the text-field is disabled, prefilled with the server that is present in the (rhc cli-tooling) openshift configuration. Once unchecked the user can enter a default server and override the openshift server that is configured in the configuration.
--
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, 7 months
[JBoss JIRA] (JBIDE-12620) openshift java client: should not load all applications when creating a new application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12620?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12620:
-------------------------------------
Labels: openshift-java-client (was: )
> openshift java client: should not load all applications when creating a new application
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-12620
> URL: https://issues.jboss.org/browse/JBIDE-12620
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: openshift-java-client
> Fix For: 4.2.x
>
>
> When creating a new application, the openshift-java-client would lookup if the application name already exist. When doing that it'll load the existing apps from the backend if they're not cached yet:
> {code:title=stacktrace when creating a new application}
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
> at com.openshift.internal.client.DomainResource.loadApplications(DomainResource.java:189)
> at com.openshift.internal.client.DomainResource.getApplications(DomainResource.java:179)
> at com.openshift.internal.client.DomainResource.getApplicationByName(DomainResource.java:141)
> at com.openshift.internal.client.DomainResource.hasApplicationByName(DomainResource.java:151)
> at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:126)
> at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:112)
> {code}
> {code:title=DomainResource looks applications up, to see if the name is already used. DomainResource#createApplication}
> if (hasApplicationByName(name)) {
> throw new OpenShiftException("Application with name \"{0}\" already exists.", name);
> }
> {code}
> {code:title=DomainResource#hasApplicationByName gets the available applications:}
> return getApplicationByName(name) != null;
> {code}
> {code:title=DomainResource#getApplicationByName}
> IApplication matchingApplication = null;
> for (IApplication application : getApplications()) {
> if (application.getName().equals(name)) {
> matchingApplication = application;
> break;
> }
> }
> return matchingApplication;
> {code}
> {code:title=DomainResource#getApplications would load the applications from the backend if they're not loaded yet}
> if (this.applications == null) {
> this.applications = loadApplications();
> }
> return CollectionUtils.toUnmodifiableCopy(applications);
> {code}
--
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, 7 months
[JBoss JIRA] (JBIDE-12571) Connection wizard: Eclipse preferences: allow users to define a default server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12571?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12571:
-------------------------------------
Summary: Connection wizard: Eclipse preferences: allow users to define a default server (was: Eclipse preferences: allow users to define a default server)
> Connection wizard: Eclipse preferences: allow users to define a default server
> ------------------------------------------------------------------------------
>
> Key: JBIDE-12571
> URL: https://issues.jboss.org/browse/JBIDE-12571
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
> Attachments: 2012-09-10 13.10.bmml, 2012-09-10 13.10.bmml, 2012-09-10 13.10.png
>
>
> Add UI to the preferences that allows users to provide a default OpenShift server to connect to. In terms of widget we need a text-field for the server url and a checkbox that allows people to refer to the default server that is defined in the openshift configfurations (~/.openshift/express.conf and /etc/openshift/express.conf). If the checkbox is checked, the text-field is disabled, prefilled with the server that is present in the (rhc cli-tooling) openshift configuration. Once unchecked the user can enter a default server and override the openshift server that is configured in the configuration.
--
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, 7 months
[JBoss JIRA] (JBIDE-12116) Port forwarding wizard: Cannot cancel Verifying SSH session job's dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12116?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12116:
-------------------------------------
Summary: Port forwarding wizard: Cannot cancel Verifying SSH session job's dialog (was: Cannot cancel Verifying SSH session job's dialog)
> Port forwarding wizard: Cannot cancel Verifying SSH session job's dialog
> ------------------------------------------------------------------------
>
> Key: JBIDE-12116
> URL: https://issues.jboss.org/browse/JBIDE-12116
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Lucia Jelinkova
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: dialog.jpg
>
>
> When the Port forwarding is invoked from Openshift Explorer for the first time a job is triggered (Verifying SSH session to retrieve Application's ports...) and a dialog is displayed. User can run the job on backgroud, show details and cancel the job. However, when Cancel is pressed the Port forwarding dialog is shown anyway.
> !dialog.jpg!
--
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, 7 months
[JBoss JIRA] (JBIDE-12121) Application wizard: the openshift profile is added to newly created maven projects, regardless of their packaging type
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12121?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12121:
-------------------------------------
Summary: Application wizard: the openshift profile is added to newly created maven projects, regardless of their packaging type (was: The openshift profile is added to newly created maven projects, regardless of their packaging type)
> Application wizard: the openshift profile is added to newly created maven projects, regardless of their packaging type
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12121
> URL: https://issues.jboss.org/browse/JBIDE-12121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
> Attachments: new-openarchetype-project-2.png, new-openarchetype-project.png
>
>
> I created a project using the org.openarchetypes:multi-javaee6-archetype:0.0.1-SNAPSHOT from http://open-archetypes.github.com/maven-repo/snapshots/archetype-catalog.xml (Maven > Archetypes > Add Remote Catalog)
> This creates a multi module project, containing a parent pom, an ear, war, ejb and utility projects. This openshift profile was added to the pom project :
> {code:xml}
> <profiles>
> <profile>
> <!-- When built in OpenShift the openshift profile will be used when invoking mvn. -->
> <!-- Use this profile for any OpenShift specific customization your app will need. -->
> <!-- By default that is to put the resulting archive into the deployments folder. -->
> <!-- http://maven.apache.org/guides/mini/guide-building-for-different-environm... -->
> <id>openshift</id>
> <build>
> <finalName>hello</finalName>
> <plugins>
> <plugin>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.1.1</version>
> <configuration>
> <outputDirectory>deployments</outputDirectory>
> <warName>ROOT</warName>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </profile>
> {code}
> Actually, it should :
> - check the packaging type of *all* the generated projects
> - if some EARs are found, then add the following to the parent pom (pay attention to the <pluginManagement> section) :
> {code:xml}
> <profile>
> <id>openshift</id>
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <artifactId>maven-ear-plugin</artifactId>
> <version>2.7</version>
> <configuration>
> <outputDirectory>deployments</outputDirectory>
> </configuration>
> </plugin>
> </plugins>
> </pluginManagement>
> </build>
> </profile>
> {code}
> - if there are no EARs but some WARs are found (count them), then add the following to the parent pom (pay attention to the <pluginManagement> section) :
> {code:xml}
> <profiles>
> <profile>
> <id>openshift</id>
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.2</version>
> <configuration>
> <outputDirectory>deployments</outputDirectory>
> <!-- Add warName ROOT ONLY if there's ONE War, otherwise, skip it -->
> <warName>ROOT</warName>
> </configuration>
> </plugin>
> </plugins>
> </pluginManagement>
> </build>
> </profile>
> {code}
> The finalName is irrelevant to openshift, only the warName counts.
--
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, 7 months
[JBoss JIRA] (JBIDE-12428) Explorer: fails to delete application on renamed domain
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12428?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12428:
-------------------------------------
Summary: Explorer: fails to delete application on renamed domain (was: OpenShift Explorer fails to delete application on renamed domain)
> Explorer: fails to delete application on renamed domain
> -------------------------------------------------------
>
> Key: JBIDE-12428
> URL: https://issues.jboss.org/browse/JBIDE-12428
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
>
> {code}
> com.openshift.client.NotFoundOpenShiftException: Could not find any OpenShift Express resource at "https://openshift.redhat.com/broker/rest/domains/bunciak/applications/java7"
> at com.openshift.internal.client.RestService.request(RestService.java:99)
> at com.openshift.internal.client.RestService.request(RestService.java:89)
> at com.openshift.internal.client.RestService.request(RestService.java:74)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
> at com.openshift.internal.client.ApplicationResource.destroy(ApplicationResource.java:238)
> at org.jboss.tools.openshift.express.internal.ui.action.DeleteApplicationAction$1.run(DeleteApplicationAction.java:90)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: com.openshift.internal.client.httpclient.NotFoundException: Could not find resource https://openshift.redhat.com/broker/rest/domains/bunciak/applications/java7
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:149)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.delete(UrlConnectionHttpClient.java:133)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.delete(UrlConnectionHttpClient.java:124)
> at com.openshift.internal.client.RestService.request(RestService.java:142)
> at com.openshift.internal.client.RestService.request(RestService.java:95)
> ... 6 more
> Caused by: java.io.FileNotFoundException: https://openshift.redhat.com/broker/rest/domains/bunciak/applications/java7
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1610)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:147)
> ... 10 more
> {code}
--
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, 7 months
[JBoss JIRA] (JBIDE-12118) Port forwarding, Tail files wizard: more specific auth error description
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12118?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12118:
-------------------------------------
Summary: Port forwarding, Tail files wizard: more specific auth error description (was: OpenShift: more specific auth error description)
> Port forwarding, Tail files wizard: more specific auth error description
> ------------------------------------------------------------------------
>
> Key: JBIDE-12118
> URL: https://issues.jboss.org/browse/JBIDE-12118
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Stefan Bunciak
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: port.png, tail.png
>
>
> Provide a uniform message in the Error dialogs like in JBIDE-11810, saying that user probably doesn't have ssh key listed in preferences.
> Current state:
> * Port forwarding, environment variables
> !port.png|thumbnail!
> * Tail files
> !tail.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, 7 months
[JBoss JIRA] (JBIDE-12117) Port forwarding wizard: Verifying SSH session job's dialog is displayed until the Port forwarding dialog is closed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12117?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12117:
-------------------------------------
Summary: Port forwarding wizard: Verifying SSH session job's dialog is displayed until the Port forwarding dialog is closed (was: Verifying SSH session job's dialog is displayed until the Port forwarding dialog is closed)
> Port forwarding wizard: Verifying SSH session job's dialog is displayed until the Port forwarding dialog is closed
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12117
> URL: https://issues.jboss.org/browse/JBIDE-12117
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Lucia Jelinkova
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: eclipse.jpg
>
>
> In Openshift Explorer, when I invoke the Port forwarding menu item, the Verifying SSH session job's dialog is displayed and won't close until the Port forwarding dialog is closed.
> !eclipse.jpg!
> Could it be changed so that when the job is finished the dialog is closed and Port forwarding dialog is shown?
--
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, 7 months