[JBoss JIRA] (JBIDE-25289) Create a jenkins job which will take care of CDK download/setup/start instead of setting it up in multiple jobs
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-25289:
-------------------------------------
Summary: Create a jenkins job which will take care of CDK download/setup/start instead of setting it up in multiple jobs
Key: JBIDE-25289
URL: https://issues.jboss.org/browse/JBIDE-25289
Project: Tools (JBoss Tools)
Issue Type: Task
Components: integration-tests
Affects Versions: 4.5.1.Final
Reporter: Ondrej Dockal
Assignee: Ondrej Dockal
Fix For: 4.5.x
Every job that uses CDK needs to utilize some steps using execute shell build steps that sets up CDK and prepare it to be used by integration tests (OS or CDK itests).
Much easier would be to have one job, that would take care of all necessary steps required to clean up/ download/ set up and/or run CDK.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25287) Jolokia Connection errors are swallowed
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25287?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-25287:
------------------------------------
Steps to Reproduce:
(hope that the other bug [JBIDE-25288] triggering an error in Jolokia will be fixed soon but currently to reproduce you can: )
- deploy a FIS application
- create a server adapter
- try to start the JMX connection
videos to help:
- https://www.youtube.com/watch?v=Ko4mNaQsCvI&t=3s
- https://www.youtube.com/watch?v=lwN3qSWz6NY&t=16s (it will fail while starting the first steps on this one)
was:
(hope that the other bug triggering an error in Jolokia will be fixed soon but currently to reproduce you can:)
- deploy a FIS application
- create a server adapter
- try to start the JMX connection
videos to help:
- https://www.youtube.com/watch?v=Ko4mNaQsCvI&t=3s
- https://www.youtube.com/watch?v=lwN3qSWz6NY&t=16s (it will fail while starting the first steps on this one)
> Jolokia Connection errors are swallowed
> ---------------------------------------
>
> Key: JBIDE-25287
> URL: https://issues.jboss.org/browse/JBIDE-25287
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Affects Versions: 4.5.0.Final, 4.5.1.AM3
> Reporter: Aurélien Pupier
> Labels: jmx, jolokia, openshift
> Attachments: image-2017-10-24-13-30-30-715.png
>
>
> even if it is better than before as we don't have a ClassCastException (see [JBIDE-23869]), as mentioned in [my last comment|https://issues.jboss.org/browse/JBIDE-23869?focusedCommentId=1346...] the error reported by Jolokia when deployed on OpenShift is still swallowed.
> I have another use case for which I have:
> !image-2017-10-24-13-30-30-715.png|thumbnail!
> with stack in log
> {noformat}
> !ENTRY org.jboss.tools.jmx.core 4 0 2017-10-24 13:27:33.523
> !MESSAGE An error occurred while opening the connection.
> !STACK 0
> java.io.IOException: Remote error status=404 (Invalid status of type java.lang.String('Failure') received)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:326)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:115)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.jolokia.client.exception.J4pRemoteException: Invalid status of type java.lang.String('Failure') received
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:67)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:313)
> ... 4 more
> {noformat}
> although when using a Rest client i have this error which contains far more information:
> {noformat}
> {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "pods "camel-ose-springboot-xml-3-t99hx" not found",
> "reason": "NotFound",
> "details": {
> "name": "camel-ose-springboot-xml-3-t99hx",
> "kind": "pods"
> },
> "code": 404
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25288) JMX Connection on OpenShift server adapter are not updated on pod updates
by Aurélien Pupier (JIRA)
Aurélien Pupier created JBIDE-25288:
---------------------------------------
Summary: JMX Connection on OpenShift server adapter are not updated on pod updates
Key: JBIDE-25288
URL: https://issues.jboss.org/browse/JBIDE-25288
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx, openshift
Affects Versions: 4.5.1.AM3, 4.5.0.Final
Reporter: Aurélien Pupier
OpenShift Server Adapters are handling pod updates except for JMX Connection.
The connection url contains the pod name but it is never updated when the pod name is updated on the OpenShift instance.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25287) Jolokia Connection errors are swallowed
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25287?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-25287:
------------------------------------
Description:
even if it is better than before as we don't have a ClassCastException (see [JBIDE-23869]), as mentioned in [my last comment|https://issues.jboss.org/browse/JBIDE-23869?focusedCommentId=1346...] the error reported by Jolokia when deployed on OpenShift is still swallowed.
I have another use case for which I have:
!image-2017-10-24-13-30-30-715.png|thumbnail!
with stack in log
{noformat}
!ENTRY org.jboss.tools.jmx.core 4 0 2017-10-24 13:27:33.523
!MESSAGE An error occurred while opening the connection.
!STACK 0
java.io.IOException: Remote error status=404 (Invalid status of type java.lang.String('Failure') received)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:326)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:115)
at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
Caused by: org.jolokia.client.exception.J4pRemoteException: Invalid status of type java.lang.String('Failure') received
at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:67)
at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:313)
... 4 more
{noformat}
although when using a Rest client i have this error which contains far more information:
{noformat}
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "pods "camel-ose-springboot-xml-3-t99hx" not found",
"reason": "NotFound",
"details": {
"name": "camel-ose-springboot-xml-3-t99hx",
"kind": "pods"
},
"code": 404
}
{noformat}
was:
even if it is better than before as we don't have a ClassCastException (see [JBIDE-23869]), as mentioned in my last comment the error reported by Jolokia when deployed on OpenShift is still swallowed.
I have another use case for which I have:
!image-2017-10-24-13-30-30-715.png|thumbnail!
with stack in log
{noformat}
!ENTRY org.jboss.tools.jmx.core 4 0 2017-10-24 13:27:33.523
!MESSAGE An error occurred while opening the connection.
!STACK 0
java.io.IOException: Remote error status=404 (Invalid status of type java.lang.String('Failure') received)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:326)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:115)
at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
Caused by: org.jolokia.client.exception.J4pRemoteException: Invalid status of type java.lang.String('Failure') received
at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:67)
at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:313)
... 4 more
{noformat}
although when using a Rest client i have this error which contains far more information:
{noformat}
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "pods "camel-ose-springboot-xml-3-t99hx" not found",
"reason": "NotFound",
"details": {
"name": "camel-ose-springboot-xml-3-t99hx",
"kind": "pods"
},
"code": 404
}
{noformat}
> Jolokia Connection errors are swallowed
> ---------------------------------------
>
> Key: JBIDE-25287
> URL: https://issues.jboss.org/browse/JBIDE-25287
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.5.0.Final, 4.5.1.AM3
> Reporter: Aurélien Pupier
> Labels: jmx, jolokia, openshift
> Attachments: image-2017-10-24-13-30-30-715.png
>
>
> even if it is better than before as we don't have a ClassCastException (see [JBIDE-23869]), as mentioned in [my last comment|https://issues.jboss.org/browse/JBIDE-23869?focusedCommentId=1346...] the error reported by Jolokia when deployed on OpenShift is still swallowed.
> I have another use case for which I have:
> !image-2017-10-24-13-30-30-715.png|thumbnail!
> with stack in log
> {noformat}
> !ENTRY org.jboss.tools.jmx.core 4 0 2017-10-24 13:27:33.523
> !MESSAGE An error occurred while opening the connection.
> !STACK 0
> java.io.IOException: Remote error status=404 (Invalid status of type java.lang.String('Failure') received)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:326)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:115)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.jolokia.client.exception.J4pRemoteException: Invalid status of type java.lang.String('Failure') received
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:67)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:313)
> ... 4 more
> {noformat}
> although when using a Rest client i have this error which contains far more information:
> {noformat}
> {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "pods "camel-ose-springboot-xml-3-t99hx" not found",
> "reason": "NotFound",
> "details": {
> "name": "camel-ose-springboot-xml-3-t99hx",
> "kind": "pods"
> },
> "code": 404
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25287) Jolokia Connection errors are swallowed
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25287?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-25287:
------------------------------------
Component/s: jmx
openshift
> Jolokia Connection errors are swallowed
> ---------------------------------------
>
> Key: JBIDE-25287
> URL: https://issues.jboss.org/browse/JBIDE-25287
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Affects Versions: 4.5.0.Final, 4.5.1.AM3
> Reporter: Aurélien Pupier
> Labels: jmx, jolokia, openshift
> Attachments: image-2017-10-24-13-30-30-715.png
>
>
> even if it is better than before as we don't have a ClassCastException (see [JBIDE-23869]), as mentioned in [my last comment|https://issues.jboss.org/browse/JBIDE-23869?focusedCommentId=1346...] the error reported by Jolokia when deployed on OpenShift is still swallowed.
> I have another use case for which I have:
> !image-2017-10-24-13-30-30-715.png|thumbnail!
> with stack in log
> {noformat}
> !ENTRY org.jboss.tools.jmx.core 4 0 2017-10-24 13:27:33.523
> !MESSAGE An error occurred while opening the connection.
> !STACK 0
> java.io.IOException: Remote error status=404 (Invalid status of type java.lang.String('Failure') received)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:326)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:115)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.jolokia.client.exception.J4pRemoteException: Invalid status of type java.lang.String('Failure') received
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:67)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:313)
> ... 4 more
> {noformat}
> although when using a Rest client i have this error which contains far more information:
> {noformat}
> {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "pods "camel-ose-springboot-xml-3-t99hx" not found",
> "reason": "NotFound",
> "details": {
> "name": "camel-ose-springboot-xml-3-t99hx",
> "kind": "pods"
> },
> "code": 404
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25287) Jolokia Connection errors are swallowed
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25287?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-25287:
------------------------------------
Labels: jmx jolokia openshift (was: )
> Jolokia Connection errors are swallowed
> ---------------------------------------
>
> Key: JBIDE-25287
> URL: https://issues.jboss.org/browse/JBIDE-25287
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Affects Versions: 4.5.0.Final, 4.5.1.AM3
> Reporter: Aurélien Pupier
> Labels: jmx, jolokia, openshift
> Attachments: image-2017-10-24-13-30-30-715.png
>
>
> even if it is better than before as we don't have a ClassCastException (see [JBIDE-23869]), as mentioned in [my last comment|https://issues.jboss.org/browse/JBIDE-23869?focusedCommentId=1346...] the error reported by Jolokia when deployed on OpenShift is still swallowed.
> I have another use case for which I have:
> !image-2017-10-24-13-30-30-715.png|thumbnail!
> with stack in log
> {noformat}
> !ENTRY org.jboss.tools.jmx.core 4 0 2017-10-24 13:27:33.523
> !MESSAGE An error occurred while opening the connection.
> !STACK 0
> java.io.IOException: Remote error status=404 (Invalid status of type java.lang.String('Failure') received)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:326)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:115)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.jolokia.client.exception.J4pRemoteException: Invalid status of type java.lang.String('Failure') received
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:67)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:313)
> ... 4 more
> {noformat}
> although when using a Rest client i have this error which contains far more information:
> {noformat}
> {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "pods "camel-ose-springboot-xml-3-t99hx" not found",
> "reason": "NotFound",
> "details": {
> "name": "camel-ose-springboot-xml-3-t99hx",
> "kind": "pods"
> },
> "code": 404
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25287) Jolokia Connection errors are swallowed
by Aurélien Pupier (JIRA)
Aurélien Pupier created JBIDE-25287:
---------------------------------------
Summary: Jolokia Connection errors are swallowed
Key: JBIDE-25287
URL: https://issues.jboss.org/browse/JBIDE-25287
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.5.1.AM3, 4.5.0.Final
Reporter: Aurélien Pupier
Attachments: image-2017-10-24-13-30-30-715.png
even if it is better than before as we don't have a ClassCastException (see [JBIDE-23869]), as mentioned in my last comment the error reported by Jolokia when deployed on OpenShift is still swallowed.
I have another use case for which I have:
!image-2017-10-24-13-30-30-715.png|thumbnail!
with stack in log
{noformat}
!ENTRY org.jboss.tools.jmx.core 4 0 2017-10-24 13:27:33.523
!MESSAGE An error occurred while opening the connection.
!STACK 0
java.io.IOException: Remote error status=404 (Invalid status of type java.lang.String('Failure') received)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:326)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:115)
at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
Caused by: org.jolokia.client.exception.J4pRemoteException: Invalid status of type java.lang.String('Failure') received
at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:67)
at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:313)
... 4 more
{noformat}
although when using a Rest client i have this error which contains far more information:
{noformat}
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "pods "camel-ose-springboot-xml-3-t99hx" not found",
"reason": "NotFound",
"details": {
"name": "camel-ose-springboot-xml-3-t99hx",
"kind": "pods"
},
"code": 404
}
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-24778) Creating application from Eclipse project which already defines a Git repo should reuse the URL
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24778?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24778:
------------------------------------------
[~dbocharov] [~jeffmaury] at some point in the earlier development - when [~fbricon] was still in the team - we discussed being able to do compatibility guesses (ex. if the local project has a javascript nature there's no way that you can use a wildfly (aka java-) image with it. While there are limited capabilities in those guesses they would still be useful. Nevertheless, thing have not been implemented since this was in the cathegory "nice to have".
> Creating application from Eclipse project which already defines a Git repo should reuse the URL
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-24778
> URL: https://issues.jboss.org/browse/JBIDE-24778
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Mickael Istria
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.1.Final
>
> Attachments: ImageOrProject.png
>
>
> I'm trying to connect an existing Eclipse project to OpenShift.
> The project is connected to GitHub ( https://github.com/mickaelistria/demo-dotnet.git )
> The OpenShift application I'm using uses a dotnet-core:2.0 image.
> Once I've selected the openshift project, the Eclipse project and the application image; I'm driven to a wizard page asking me for some details about the application, including the Git repo URL.
> I would expect the repo URL to be prepopulated with the Git repo URL of my Eclipse project
> Instead, the URL was the one of the image example: https://github.com/redhat-developer/s2i-dotnetcore-ex.git
> If this is an issue in the .NET Core 2.0 image, please tell me and I'll open a bug for it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBDS-4578) devstudio rpm should depend on upstream org.eclipse.jpt
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4578?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4578.
------------------------------
Verified in 11.1-0.20171024.0823. Duplicities have been removed. Closing.
> devstudio rpm should depend on upstream org.eclipse.jpt
> -------------------------------------------------------
>
> Key: JBDS-4578
> URL: https://issues.jboss.org/browse/JBDS-4578
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: rpm
> Affects Versions: 11.1.0.AM3
> Environment: rh-eclipse47-devstudio.x86_64 - 11.1-0.20171005.1344.el7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 11.1.0.GA
>
> Attachments: list_of_conflicts.txt, rh-eclipse47.log.20171006-1218_strict.txt
>
>
> The /opt/rh/rh-eclipse47 folder contains couples of *org.eclipse.jpt.** plugins with same x.y.z but different timestamps. It causes BundleExceptions. It seems to be the same problem as JBDS-4567.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-24778) Creating application from Eclipse project which already defines a Git repo should reuse the URL
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24778?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-24778:
------------------------------------
If you have a way to determine that the project is not compatible with the image, then use the URL from the image otherwise use the URL from the project git report but it's likely that the build will fail
> Creating application from Eclipse project which already defines a Git repo should reuse the URL
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-24778
> URL: https://issues.jboss.org/browse/JBIDE-24778
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Mickael Istria
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.1.Final
>
> Attachments: ImageOrProject.png
>
>
> I'm trying to connect an existing Eclipse project to OpenShift.
> The project is connected to GitHub ( https://github.com/mickaelistria/demo-dotnet.git )
> The OpenShift application I'm using uses a dotnet-core:2.0 image.
> Once I've selected the openshift project, the Eclipse project and the application image; I'm driven to a wizard page asking me for some details about the application, including the Git repo URL.
> I would expect the repo URL to be prepopulated with the Git repo URL of my Eclipse project
> Instead, the URL was the one of the image example: https://github.com/redhat-developer/s2i-dotnetcore-ex.git
> If this is an issue in the .NET Core 2.0 image, please tell me and I'll open a bug for it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months