[JBoss JIRA] (JBIDE-12121) 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:
-------------------------------------
Fix Version/s: 4.1.x
(was: 4.1.0.Beta2)
> 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.1.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, 10 months
[JBoss JIRA] (JBIDE-13303) errors in error log when navigating openshift explorer and no connection setup
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13303?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13303:
-------------------------------------
Fix Version/s: 4.1.x
(was: 4.1.0.Beta2)
> errors in error log when navigating openshift explorer and no connection setup
> ------------------------------------------------------------------------------
>
> Key: JBIDE-13303
> URL: https://issues.jboss.org/browse/JBIDE-13303
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.x
>
>
> Open openshift explorer with properties view and no connection open and no network attached.
> com.openshift.client.OpenShiftEndpointException: Could not request /api: java.net.UnknownHostException: openshift.redhat.com
> at com.openshift.internal.client.RestService.request(RestService.java:103)
> at com.openshift.internal.client.RestService.request(RestService.java:91)
> at com.openshift.internal.client.RestService.request(RestService.java:72)
> at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34)
> at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:135)
> at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:104)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199)
> at org.jboss.tools.openshift.express.internal.ui.property.UserPropertySource$1.run(UserPropertySource.java:112)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: java.net.UnknownHostException: openshift.redhat.com
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:194)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:99)
> at com.openshift.internal.client.RestService.request(RestService.java:139)
> at com.openshift.internal.client.RestService.request(RestService.java:97)
> ... 9 more
> Caused by: java.net.UnknownHostException: openshift.redhat.com
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1491)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1485)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:177)
> ... 12 more
> Caused by: java.net.UnknownHostException: openshift.redhat.com
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432)
> at java.net.Socket.connect(Socket.java:529)
> at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:570)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:158)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:523)
> at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:272)
> at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:329)
> at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:172)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911)
> at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:158)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:94)
> ... 11 more
--
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, 10 months
[JBoss JIRA] (JBIDE-13862) Deploying project should be automatically added to OpenShift Server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13862?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13862:
-------------------------------------
Fix Version/s: 4.1.x
(was: 4.1.0.Beta2)
> Deploying project should be automatically added to OpenShift Server adapter
> ---------------------------------------------------------------------------
>
> Key: JBIDE-13862
> URL: https://issues.jboss.org/browse/JBIDE-13862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.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, 10 months
[JBoss JIRA] (JBIDE-13862) Deploying project should be automatically added to OpenShift Server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13862?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13862:
------------------------------------------
postponed to 4.1.x since we ran out of time for this non-critical issue.
> Deploying project should be automatically added to OpenShift Server adapter
> ---------------------------------------------------------------------------
>
> Key: JBIDE-13862
> URL: https://issues.jboss.org/browse/JBIDE-13862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.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, 10 months
[JBoss JIRA] (JBIDE-14582) VJET context menu in OpenShift Explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14582?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-14582.
--------------------------------------
Resolution: Won't Fix
resolving as WONT_FIX since there's nothing we can do about it in OpenShift.
> VJET context menu in OpenShift Explorer
> ---------------------------------------
>
> Key: JBIDE-14582
> URL: https://issues.jboss.org/browse/JBIDE-14582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta2
>
> Attachments: openshift_vjet.png
>
>
> After installing Eclipse VJET from JBoss Central:
> !openshift_vjet.png|thumbnail!
> steps to reproduce:
> # ASSERT: make sure you have VJET installed
> # ASSERT: make sure you have OpenShift Exlorer openened
> # ASSERT: make sure you dont have ANY item selected in OpenShift
> # EXEC: open up context menu
> Result:
> !openshift_vjet.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, 10 months
[JBoss JIRA] (JBIDE-14582) VJET context menu in OpenShift Explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14582?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14582:
------------------------------------------
The VJET context menu is not appearing if you select an item in OpenShift Explorer. IMHO there's not much we can do about it, it's an issue in VJET where they show context menu items regardless of the view we're in if nothing is selected. We could file this against VJET in eclipse bugzilla.
> VJET context menu in OpenShift Explorer
> ---------------------------------------
>
> Key: JBIDE-14582
> URL: https://issues.jboss.org/browse/JBIDE-14582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta2
>
> Attachments: openshift_vjet.png
>
>
> After installing Eclipse VJET from JBoss Central:
> !openshift_vjet.png|thumbnail!
> steps to reproduce:
> # ASSERT: make sure you have VJET installed
> # ASSERT: make sure you have OpenShift Exlorer openened
> # ASSERT: make sure you dont have ANY item selected in OpenShift
> # EXEC: open up context menu
> Result:
> !openshift_vjet.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, 10 months