[JBoss JIRA] (JBIDE-23317) Create and use Oxygen.0.M7 target platform
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23317?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23317:
-------------------------------------
reddeer needs code updates and a new version. The open-perspective dialog has changed button text.
> Create and use Oxygen.0.M7 target platform
> ------------------------------------------
>
> Key: JBIDE-23317
> URL: https://issues.jboss.org/browse/JBIDE-23317
> Project: Tools (JBoss Tools)
> Issue Type: Component Upgrade
> Components: target-platform
> Affects Versions: 4.4.1.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.5.0.AM1
>
> Attachments: duplicate-plugins.jbt.tp.470.M7.txt, p2diff.M5vsM7.txt, p2diff.M5vsM7_ignore_versions.txt, p2diff.M5vsM7_ignore_versions_sorted.txt, p2diff.M5vsM7_ignore_versions_summary.txt, p2diff.M5vsM7_summary.txt
>
>
> Once available on Feb 02/2017, we should create a new 4.70.0.AM1-SNAPSHOT target platform containing Oxygen.0.M5 bits.
> https://wiki.eclipse.org/index.php?title=Oxygen/Simultaneous_Release_Plan...
> Story points: 21 (fibonacci)
> jbt tp,
> jbds tp,
> central tp;
> jbt-build-sites,
> jbds site build;
> update install/matrix jobs to use new Eclipse JEE/platform binary;
> mailing list announcements
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24378) intermittent test failure due to ResolverProjectNature2 ?
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24378?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-24378:
------------------------------------
No it i on purpose that ResolverProjectNature2 does not implement ELResolver. The test checks that only 2 resolvers are returned because it does not implement that interface.
> intermittent test failure due to ResolverProjectNature2 ?
> ---------------------------------------------------------
>
> Key: JBIDE-24378
> URL: https://issues.jboss.org/browse/JBIDE-24378
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 4.5.0.AM1
>
>
> Some jbosstools-base builds are failing (after 40 min timeout is elapsed) with this error:
> {code}
> 03:39:52 [INFO] org.jboss.tools.common.el.core.test ................ FAILURE [40:00 min]
> 03:39:52 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.jboss.tools.common.el.core.test: An unexpected error occured while launching the test runtime (return code 143). See log for details. -> [Help 1]
> !MESSAGE org.jboss.tools.common.el.core.test.resolver.ResolverProjectNature2 must be instance of org.jboss.tools.common.el.core.resolver.ELResolver{code}
> Yet it doesn't appear this 2nd project nature contributes any actual tests.
> Best I can find is:
> ELResolverFactory1 -> ResolverProjectNature1 (but not 2)
> So... where in https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... does this project nature actually contribute anything to tests?
> Could we just remove it?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24482) CDK server adapter: creates a connection with erroneous "Image Registry URL"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24482?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24482:
-------------------------------------
Steps to Reproduce:
# ASSERT: have a CDK3/minishift server adapter
# ASSERT: make sure that you *DONT* have a connection to CDK3/minishift in the OpenShift Explorer
# EXEC: launch CDK3/minishift server adapter
# ASSERT: in OpenShift explorer: a new connection to the CDK3/minishift is created
# EXEC: in OpenShift explorer: pick "Edit Connection..."
# ASSERT: connection wizard pops up
# EXEC: hit "Advanced >>" and inspect "Image Registry URL"
Result:
!image-2017-05-17-22-07-43-235.png!
The image registry URL that is unveiled is clearly wrong. It is https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/
Expected result:
the correct value for the docker registry can be fetched from minishift by doing (in cmd-line):
{code}
./minishift openshift registry
{code}
In the current state of CDK3/minishift, where the docker registry is not publicly reachable the value that is reported is an internal IP:
{code}
172.30.1.1:5000
{code}
was:
# ASSERT: have a CDK3/minishift server adapter
# ASSERT: make sure that you *DONT* have a connection to CDK3/minishift in the OpenShift Explorer
# EXEC: launch CDK3/minishift server adapter
# ASSERT: in OpenShift explorer: a new connection to the CDK3/minishift is created
# EXEC: in OpenShift explorer: pick "Edit Connection..."
# ASSERT: connection wizard pops up
# EXEC: hit "Advanced >>" and inspect "Image Registry URL"
Result:
!image-2017-05-17-22-07-43-235.png!
The image registry URL that is unveiled is clearly wrong. It is https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/
> CDK server adapter: creates a connection with erroneous "Image Registry URL"
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24482
> URL: https://issues.jboss.org/browse/JBIDE-24482
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Attachments: image-2017-05-17-22-07-43-235.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24492) Details for custom template are not shown until "Next" is pressed.
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-24492:
----------------------------------
Summary: Details for custom template are not shown until "Next" is pressed.
Key: JBIDE-24492
URL: https://issues.jboss.org/browse/JBIDE-24492
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.4.Final
Reporter: Radim Hopp
Assignee: Andre Dietisheim
Almost certainly a regression caused by JBIDE-23473.
I know that validation is now bound to pressing "Next" button, but this prevents from showing user the defined resources on first page of wizard in "Details" section. Maybe showing them on second page would solve the problem?
Screencast: https://youtu.be/uGAmL_sMIXc
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBTIS-1112) BPEL version was downgraded from 1.3.200 to 1.3.3
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1112?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1112:
-----------------------------------
*ugh* - you're right - I'll bump it up to 1.3.300 - it will take a few
hours to respin
On Mon, May 22, 2017 at 8:38 AM, Andrej Podhradsky (JIRA) <issues(a)jboss.org>
> BPEL version was downgraded from 1.3.200 to 1.3.3
> -------------------------------------------------
>
> Key: JBTIS-1112
> URL: https://issues.jboss.org/browse/JBTIS-1112
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: BPEL, distribution
> Affects Versions: 10.3.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 10.3.0.GA
>
>
> BPEL version was downgraded from 1.3.200 to 1.3.3. Namely, the feature org.jboss.tools.bpel.feature
> | Devstudio IS 10.3.0.CR2 | 1.3.200.Final-v20160331-1749-B19 |
> | Devstudio IS 10.3.0.GA | 1.3.3.Final-v20170329-1943-B12 |
> I didn't find any difference except the version definition.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBTIS-1112) BPEL version was downgraded from 1.3.200 to 1.3.3
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1112?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky commented on JBTIS-1112:
------------------------------------------
So far I have not found any problem. The only one issue is that we provide an older version in the new build and a user can see something like this when installing it into Devstudio IS 10.2.0.GA
{code}
Your original request has been modified.
"BPMN2 Modeler - jBPM Runtime Extension Feature" is already installed, so an update will be performed instead.
"BPMN2 Modeler - Diagram Editor" is already installed, so an update will be performed instead.
"JBoss BPEL Editor" will be ignored because a newer version is already installed.
{code}
It is only a warning but it doesn't look good ;-)
> BPEL version was downgraded from 1.3.200 to 1.3.3
> -------------------------------------------------
>
> Key: JBTIS-1112
> URL: https://issues.jboss.org/browse/JBTIS-1112
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: BPEL, distribution
> Affects Versions: 10.3.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 10.3.0.GA
>
>
> BPEL version was downgraded from 1.3.200 to 1.3.3. Namely, the feature org.jboss.tools.bpel.feature
> | Devstudio IS 10.3.0.CR2 | 1.3.200.Final-v20160331-1749-B19 |
> | Devstudio IS 10.3.0.GA | 1.3.3.Final-v20170329-1943-B12 |
> I didn't find any difference except the version definition.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months