[JBoss JIRA] (JBIDE-23927) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23927?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23927:
----------------------------------
Assignee: Gorkem Ercan
> For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid]
> -------------------------------------------------------------------------
>
> Key: JBIDE-23927
> URL: https://issues.jboss.org/browse/JBIDE-23927
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aerogear-hybrid
> Reporter: Jeff MAURY
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.AM1
>
>
> For JBIDE 4.4.4.AM1 [aerogear-hybrid]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1
>
> [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...]
>
> 1. Check out your existing *{color:orange}master{color}* branch:
>
> {code}
> git checkout master
> {code}
>
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.AM1-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 5. Close (do not resolve) this JIRA when done.
>
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
>
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23929) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [foundation]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-23929:
----------------------------------
Summary: For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [foundation]
Key: JBIDE-23929
URL: https://issues.jboss.org/browse/JBIDE-23929
Project: Tools (JBoss Tools)
Issue Type: Task
Components: foundation
Reporter: Jeff MAURY
Priority: Blocker
Fix For: 4.4.4.AM1
For JBIDE 4.4.4.AM1 [foundation]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1
[Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...]
1. Check out your existing *{color:orange}master{color}* branch:
{code}
git checkout master
{code}
2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.4.AM1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
{code}
git checkout master;
git pull origin master;
git checkout -b jbosstools-4.4.x;
git push origin jbosstools-4.4.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
{code}
mvn clean verify -Dtpc.version=4.60.2.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final
{code}
mvn clean verify -Dtpc.version=4.60.2.Final
{code}
5. Close (do not resolve) this JIRA when done.
6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23928) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [arquillian]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23928?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23928:
----------------------------------
Assignee: Snjezana Peco
> For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [arquillian]
> --------------------------------------------------------------------
>
> Key: JBIDE-23928
> URL: https://issues.jboss.org/browse/JBIDE-23928
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: arquillian
> Reporter: Jeff MAURY
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.AM1
>
>
> For JBIDE 4.4.4.AM1 [arquillian]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1
>
> [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...]
>
> 1. Check out your existing *{color:orange}master{color}* branch:
>
> {code}
> git checkout master
> {code}
>
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.AM1-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 5. Close (do not resolve) this JIRA when done.
>
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
>
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23926) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [arquillian]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-23926:
----------------------------------
Summary: For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [arquillian]
Key: JBIDE-23926
URL: https://issues.jboss.org/browse/JBIDE-23926
Project: Tools (JBoss Tools)
Issue Type: Task
Components: arquillian
Reporter: Jeff MAURY
Priority: Blocker
Fix For: 4.4.4.AM1
For JBIDE 4.4.4.AM1 [arquillian]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1
[Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...]
1. Check out your existing *{color:orange}master{color}* branch:
{code}
git checkout master
{code}
2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.4.AM1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
{code}
git checkout master;
git pull origin master;
git checkout -b jbosstools-4.4.x;
git push origin jbosstools-4.4.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
{code}
mvn clean verify -Dtpc.version=4.60.2.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final
{code}
mvn clean verify -Dtpc.version=4.60.2.Final
{code}
5. Close (do not resolve) this JIRA when done.
6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23925) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-23925:
----------------------------------
Summary: For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid]
Key: JBIDE-23925
URL: https://issues.jboss.org/browse/JBIDE-23925
Project: Tools (JBoss Tools)
Issue Type: Task
Components: aerogear-hybrid
Reporter: Jeff MAURY
Priority: Blocker
Fix For: 4.4.4.AM1
For JBIDE 4.4.4.AM1 [aerogear-hybrid]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1
[Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...]
1. Check out your existing *{color:orange}master{color}* branch:
{code}
git checkout master
{code}
2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.4.AM1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
{code}
git checkout master;
git pull origin master;
git checkout -b jbosstools-4.4.x;
git push origin jbosstools-4.4.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
{code}
mvn clean verify -Dtpc.version=4.60.2.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final
{code}
mvn clean verify -Dtpc.version=4.60.2.Final
{code}
5. Close (do not resolve) this JIRA when done.
6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23925) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23925?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23925:
----------------------------------
Assignee: Gorkem Ercan
> For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [aerogear-hybrid]
> -------------------------------------------------------------------------
>
> Key: JBIDE-23925
> URL: https://issues.jboss.org/browse/JBIDE-23925
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aerogear-hybrid
> Reporter: Jeff MAURY
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.AM1
>
>
> For JBIDE 4.4.4.AM1 [aerogear-hybrid]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1
>
> [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...]
>
> 1. Check out your existing *{color:orange}master{color}* branch:
>
> {code}
> git checkout master
> {code}
>
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.AM1-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 5. Close (do not resolve) this JIRA when done.
>
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
>
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23815) NPE in BuildConfigPropertySource.getResourcePropertyDescriptors
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23815?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23815 at 2/16/17 1:33 PM:
-------------------------------------------------------------------
we merged the PR for JBT that prevents the NPE. The NPE wont occurr but there are no "Source" properties being show either, because the openshift client library doesnt support it yet.
We now should have proper support for the build source type "Binary". I filed this to JBIDE-23924
was (Author: adietish):
we merged the PR for JBT that prevents the NPE.
We now should have proper support for the build source type "Binary".
> NPE in BuildConfigPropertySource.getResourcePropertyDescriptors
> ---------------------------------------------------------------
>
> Key: JBIDE-23815
> URL: https://issues.jboss.org/browse/JBIDE-23815
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.4.3.Final
>
> Attachments: buildconfig-properties.png, npe.webm, spring-boot-camel-template.png, test-ose.zip
>
>
> {noformat}
> !ENTRY org.eclipse.jface 4 2 2017-01-31 10:27:08.951
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.property.BuildConfigPropertySource.getResourcePropertyDescriptors(BuildConfigPropertySource.java:56)
> at org.jboss.tools.openshift.internal.ui.property.ResourcePropertySource.getPropertyDescriptors(ResourcePropertySource.java:62)
> at org.eclipse.ui.views.properties.PropertySheetEntry.computeMergedPropertyDescriptors(PropertySheetEntry.java:171)
> at org.eclipse.ui.views.properties.PropertySheetEntry.refreshChildEntries(PropertySheetEntry.java:506)
> at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:732)
> at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:980)
> at org.eclipse.ui.views.properties.PropertySheetPage.selectionChanged(PropertySheetPage.java:525)
> at org.jboss.tools.openshift.internal.ui.property.tabbed.OpenShiftResourcePropertySection$2.selectionChanged(OpenShiftResourcePropertySection.java:140)
> at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:155)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2191)
> at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1229)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1258)
> at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
> at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:405)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {noformat}
> here is the json available when I click "Edit" on the application:
> {noformat}
> {
> "metadata" : {
> "name" : "camel-ose-springboot-xml",
> "namespace" : "test1",
> "selfLink" : "/api/v1/namespaces/test1/services/camel-ose-springboot-xml",
> "uid" : "a28f19cd-e298-11e6-9637-525400ee9c8f",
> "resourceVersion" : "69156",
> "creationTimestamp" : "2017-01-25T00:53:07Z",
> "labels" : {
> "expose" : "true",
> "group" : "com.mycompany",
> "project" : "camel-ose-springboot-xml",
> "provider" : "fabric8",
> "version" : "1.0.0-SNAPSHOT"
> },
> "annotations" : {
> "fabric8.io/iconUrl" : "img/icons/camel.svg",
> "prometheus.io/port" : "9779",
> "prometheus.io/scrape" : "true"
> }
> },
> "spec" : {
> "ports" : [{
> "name" : "http",
> "protocol" : "TCP",
> "port" : 80,
> "targetPort" : 8080
> }],
> "selector" : {
> "group" : "com.mycompany",
> "project" : "camel-ose-springboot-xml",
> "provider" : "fabric8"
> },
> "portalIP" : "172.30.65.90",
> "clusterIP" : "172.30.65.90",
> "type" : "ClusterIP",
> "sessionAffinity" : "None"
> },
> "status" : {"loadBalancer" : {}},
> "kind" : "Service",
> "apiVersion" : "v1"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month