[JBoss JIRA] (JBTIS-905) Drools - PerspectiveTest is failing on Neon
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-905?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBTIS-905:
-----------------------------------------
Hi [~tomasdavidorg], I'm sorry, it seems that the issue was caused by me. The installer for RHDS-IS 10.0.0.Alpha1 is missing the jBPM feature.
Once I'm done with the fix, I will let you know if it is ok now.
> Drools - PerspectiveTest is failing on Neon
> -------------------------------------------
>
> Key: JBTIS-905
> URL: https://issues.jboss.org/browse/JBTIS-905
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: drools/ jBPM, QE
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andrej Podhradsky
> Assignee: Tomas David
> Fix For: 4.4.0.Alpha1
>
>
> *Error Message*
> Perspective jBPM isn't available
> *Stacktrace*
> {code}
> org.jboss.reddeer.eclipse.exception.EclipseLayerException: Perspective jBPM isn't available
> at org.jboss.reddeer.eclipse.ui.perspectives.AbstractPerspective.<init>(AbstractPerspective.java:41)
> at org.jboss.tools.drools.reddeer.perspective.JbpmPerspective.<init>(JbpmPerspective.java:11)
> at org.jboss.tools.drools.ui.bot.test.smoke.PerspectiveTest.openJbpmPerspectiveTest(PerspectiveTest.java:25)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-22626:
------------------------------------------
[~mlabuda], yes, this is exactly the scenario i described above. My question was about the way of modifying the tag in DC.
I supposed it to be updated by itself. because it is in the trigger part, which is described in the documentation. But [~jcantrill] said that it doesn't work like this. A new deployment is launched only when DC contains :latest tag and we push a new image.
So i think in this JIRA i will just set this tag line to a new tag.
> Updating deployed docker image on OpenShift does not work
> ---------------------------------------------------------
>
> Key: JBIDE-22626
> URL: https://issues.jboss.org/browse/JBIDE-22626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.4.2.AM1
>
> Attachments: ImageStreamTags.jpg
>
>
> In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok.
> But if user deploys image with tag e.g. :0.8 to OpenShift, resources are created for this specific tag. When I am trying to Deploy to OS image with tag :0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag :0.8 and thus new deployment is not done.
> Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it.
> In order to add this version tag after semicolon, right-click on the image -> Add tag -> Re-type namespace/imagename + add ":0.8" e.g.
> Tagging Images: https://docs.openshift.com/enterprise/latest/dev_guide/managing_images.ht...
> Image Change Trigger: https://docs.openshift.com/enterprise/latest/dev_guide/deployments.html#i...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22896) JavaModelException below JdtUtils.findDeclaringNode (thrown in JavaElement.newNotPresentException)
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22896?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-22896:
----------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.2.AM1)
> JavaModelException below JdtUtils.findDeclaringNode (thrown in JavaElement.newNotPresentException)
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22896
> URL: https://issues.jboss.org/browse/JBIDE-22896
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Xavier Coulon
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: Failed to build or refresh the JAX-RS metamodel
> {noformat}
> org.eclipse.jdt.core.JavaModelException: submt(HttpServletRequest, int) [in PublicWS [in [Working copy] PublicWS.java [in be.fromprison.ws.endpoints [in src/main/java [in from-prison]]]]] does not exist
> at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:556)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:590)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
> at org.eclipse.jdt.internal.core.SourceRefElement.getSourceRange(SourceRefElement.java:218)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.findDeclaringNode(JdtUtils.java:494)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveAllAnnotations(JdtUtils.java:373)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResourceMethod$Builder.buildInResource(JaxrsResourceMethod.java:153)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:211)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:65)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:420)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:392)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:73)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.jdt.core | 3.11.0.xx-201604081629-e45 | 3.12.0.v_OTDT_r250_201606070956 |
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.ws.jaxrs.core | 1.8.1.Final-v20160331-0952-B76 | 1.9.1.v20160608-0648 |
> | org.jboss.tools.ws.jaxrs.ui | 1.8.1.Final-v20160331-0952-B76 | 1.9.0.Final-v20160610-0003-B1 |
> Operating Systems:
> | Linux | 3.10.0.13 | 4.6.3.fc24 |
> | MacOSX | 10.11.3 | 10.11.6 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571dd2b8e4b08bd809...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23055) Repeated toggling of JAX-RS support on project does not cause it to rebuild
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23055?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-23055:
----------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.2.AM1)
> Repeated toggling of JAX-RS support on project does not cause it to rebuild
> ---------------------------------------------------------------------------
>
> Key: JBIDE-23055
> URL: https://issues.jboss.org/browse/JBIDE-23055
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.4.1.AM3
> Reporter: Jan Richter
> Assignee: Xavier Coulon
> Fix For: 4.4.2.AM2
>
>
> When JAX-RS support is toggled in a project's preferences, clicking Apply will rebuild the project and JAX-RS services will (dis)/appear and validation is enabled/disabled.
> But if without closing the preferences I toggle JAX-RS support again and press Apply, nothing happens - the project is not built with the new settings.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22626:
---------------------------------------
I think it would be nice to have supported following use case:
1. There is a docker image aloha:1.0
2. Deploy image to OpenShift and push it to registry (check the checkbox in Deploy Image to OpenShift wizard)
3. Resource are created (DC, RC, IS, pods, service, route)
4. I perform change changes to docker file of aloha image, tag it as version 2.0
5. Deploy image aloha:2.0 via the Deploy image.
to this point everything is ok. Now I would just modify DC to replace old tag with the new one. Entries in IS are correct (there is a new tag for 2.0 image).
> Updating deployed docker image on OpenShift does not work
> ---------------------------------------------------------
>
> Key: JBIDE-22626
> URL: https://issues.jboss.org/browse/JBIDE-22626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.4.2.AM1
>
> Attachments: ImageStreamTags.jpg
>
>
> In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok.
> But if user deploys image with tag e.g. :0.8 to OpenShift, resources are created for this specific tag. When I am trying to Deploy to OS image with tag :0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag :0.8 and thus new deployment is not done.
> Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it.
> In order to add this version tag after semicolon, right-click on the image -> Add tag -> Re-type namespace/imagename + add ":0.8" e.g.
> Tagging Images: https://docs.openshift.com/enterprise/latest/dev_guide/managing_images.ht...
> Image Change Trigger: https://docs.openshift.com/enterprise/latest/dev_guide/deployments.html#i...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months