[JBoss JIRA] (JBTIS-1045) Drools plugin version doesn't match the appropriate bundle version
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1045?page=com.atlassian.jira.plugin... ]
Paul Leacu reassigned JBTIS-1045:
---------------------------------
Assignee: Paul Leacu
> Drools plugin version doesn't match the appropriate bundle version
> ------------------------------------------------------------------
>
> Key: JBTIS-1045
> URL: https://issues.jboss.org/browse/JBTIS-1045
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: drools/ jBPM
> Affects Versions: 4.4.1.Final
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
>
> JBTIS 4.4.1.Final / DevstudioIS 10.1.0.GA contains drools plugins in the following version
> {code}
> 6.5.1.Final-v20161109-054101-B1259
> {code}
> All related features and plugins also contain the above versions such as
> {code}
> org.drools.eclipse.feature_6.5.1.Final-v20161109-054101-B1259
> org.drools.eclipse_6.5.1.Final-v20161109-054101-B1259.jar
> {code}
> But if you unzip the drools plugin and look at its bundle version in MANIFEST file you will see
> {code}
> Bundle-Version: 6.5.0.20161109-054101
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (JBTIS-1150) Incorrect version of Drools plugins
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1150?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky commented on JBTIS-1150:
------------------------------------------
Hey [~pleacu] could you have a look at JBTIS-1045, please? There was a trick where the bundles pretend the correct version but in fact the version was incorrect.
> Incorrect version of Drools plugins
> -----------------------------------
>
> Key: JBTIS-1150
> URL: https://issues.jboss.org/browse/JBTIS-1150
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, drools/ jBPM
> Affects Versions: 4.5.0.CR2, 11.0.0.CR2
> Reporter: Andrej Podhradsky
> Assignee: Kris Verlaenen
>
> Drools plugins are in the following version
> {code}
> 7.0.1.Final
> {code}
> which doesn't follow our rules for versions (JBTIS-471)
> {code}
> x.y.z.BUILD_ALIAS-vYYYYMMDD-hhmm-B###
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (JBTIS-1150) Incorrect version of Drools plugins
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1150?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1150:
-----------------------------------
HEy [~KrisVerlaenen] - I can build again. The local build results look good:
i.e. org.drools.eclipse.feature_8.0.0.Final-v20170801-1309-B1.jar
This should be resolved for your 8.0 build. We'll keep it open to remind us until it's available. Thanks for looking into it.
> Incorrect version of Drools plugins
> -----------------------------------
>
> Key: JBTIS-1150
> URL: https://issues.jboss.org/browse/JBTIS-1150
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, drools/ jBPM
> Affects Versions: 4.5.0.CR2, 11.0.0.CR2
> Reporter: Andrej Podhradsky
> Assignee: Kris Verlaenen
>
> Drools plugins are in the following version
> {code}
> 7.0.1.Final
> {code}
> which doesn't follow our rules for versions (JBTIS-471)
> {code}
> x.y.z.BUILD_ALIAS-vYYYYMMDD-hhmm-B###
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (JBIDE-24501) Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24501?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24501:
-------------------------------------
Steps to Reproduce:
# ASSERT: have the CDK with the registry that's not publicly reachable
# ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git)
# ASSERT: have a connection to the docker daemon in the CDK3
# EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick *Docker Connection* to the docker daemon in the CDK
# EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..."
# EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard
# ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer
!image-2017-05-23-12-00-51-733.png!
# EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..."
# ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix
!image-2017-05-23-12-07-14-028.png!
# EXEC: hit "Next"
Result:
The deploy fails with 2 error dialogs, the wizard stays open.
One that tells you that the lookup failed and one that tells you about an NPE that happened:
!screenshot-1.png!
!image-2017-05-23-12-10-06-694.png!
In the Eclipse log you'll find the following:
{code}
java.lang.NullPointerException
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DockerConfigMetaData.env(DockerConfigMetaData.java:69)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:356)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
was:
# ASSERT: have the CDK with the registry that's not publicly reachable
# ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git)
# ASSERT: have a connection to the docker daemon in the CDK3
# EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick *Docker Connection* to the docker daemon in the CDK
# EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..."
# EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard
# ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer
!image-2017-05-23-12-00-51-733.png!
# EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..."
# ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix
!image-2017-05-23-12-07-14-028.png!
# EXEC: hit "Next"
Result:
The image name lookup fails, and 2 error dialogs show up: One that tells you that the lookup failed and one that tells you about an NPE that happened:
!image-2017-05-23-12-10-06-694.png!
!screenshot-1.png!
In the Eclipse log you'll find the following:
{code}
java.lang.NullPointerException
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DockerConfigMetaData.env(DockerConfigMetaData.java:69)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:356)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
> Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24501
> URL: https://issues.jboss.org/browse/JBIDE-24501
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.5.0.Final
>
> Attachments: image-2017-05-23-12-00-51-733.png, image-2017-05-23-12-07-14-028.png, image-2017-05-23-12-10-06-694.png, screenshot-1.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (JBIDE-24501) Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24501?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24501:
-------------------------------------
Steps to Reproduce:
# ASSERT: have the CDK with the registry that's not publicly reachable
# ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git)
# ASSERT: have a connection to the docker daemon in the CDK3
# EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick *Docker Connection* to the docker daemon in the CDK
# EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..."
# EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard
# ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer
!image-2017-05-23-12-00-51-733.png!
# EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..."
# ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix
!image-2017-05-23-12-07-14-028.png!
# EXEC: hit "Next"
Result:
The image name lookup fails, and 2 error dialogs show up: One that tells you that the lookup failed and one that tells you about an NPE that happened:
!image-2017-05-23-12-10-06-694.png!
!screenshot-1.png!
In the Eclipse log you'll find the following:
{code}
java.lang.NullPointerException
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DockerConfigMetaData.env(DockerConfigMetaData.java:69)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:356)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
was:
# ASSERT: have the CDK with the registry that's not publicly reachable
# ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git)
# ASSERT: have a connection to the docker daemon in the CDK3
# EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick *Docker Connection* to the docker daemon in the CDK
# EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..."
# EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard
# ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer
!image-2017-05-23-12-00-51-733.png!
# EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..."
# ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix
!image-2017-05-23-12-07-14-028.png!
# EXEC: hit "Next"
Result:
The image name lookup fails, and 2 error dialogs show up: One that tells you that the lookup failed and one that tells you about an NPE that happened:
!image-2017-05-23-12-10-06-694.png!
!screenshot-1.png!
In the Eclipse log you'll find the following:
{code}
java.lang.NullPointerException
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DockerConfigMetaData.env(DockerConfigMetaData.java:69)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:356)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
> Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24501
> URL: https://issues.jboss.org/browse/JBIDE-24501
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.5.0.Final
>
> Attachments: image-2017-05-23-12-00-51-733.png, image-2017-05-23-12-07-14-028.png, image-2017-05-23-12-10-06-694.png, screenshot-1.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (JBIDE-24501) Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24501?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24501:
-------------------------------------
Steps to Reproduce:
# ASSERT: have the CDK with the registry that's not publicly reachable
# ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git)
# ASSERT: have a connection to the docker daemon in the CDK3
# EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick *Docker Connection* to the docker daemon in the CDK
# EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..."
# EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard
# ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer
!image-2017-05-23-12-00-51-733.png!
# EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..."
# ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix
!image-2017-05-23-12-07-14-028.png!
# EXEC: hit "Next"
Result:
The image name lookup fails, and 2 error dialogs show up: One that tells you that the lookup failed and one that tells you about an NPE that happened:
!image-2017-05-23-12-10-06-694.png!
!screenshot-1.png!
In the Eclipse log you'll find the following:
{code}
java.lang.NullPointerException
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DockerConfigMetaData.env(DockerConfigMetaData.java:69)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:356)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
was:
# ASSERT: have the CDK with the registry that's not publicly reachable
# ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git)
# ASSERT: have a connection to the docker daemon in the CDK3
# EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick *Docker Connection* to the docker daemon in the CDK
# EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..."
# EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard
# ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer
!image-2017-05-23-12-00-51-733.png!
# EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..."
# ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix
!image-2017-05-23-12-07-14-028.png!
# EXEC: hit "Next"
Result:
The image name lookup fails, and 2 error dialogs show up: One that tells you that the lookup failed and one that tells you about an NPE that happened:
!image-2017-05-23-12-10-06-694.png!
In the Eclipse log you'll find the following:
{code}
java.lang.NullPointerException
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DockerConfigMetaData.env(DockerConfigMetaData.java:69)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:356)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
> Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24501
> URL: https://issues.jboss.org/browse/JBIDE-24501
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.5.0.Final
>
> Attachments: image-2017-05-23-12-00-51-733.png, image-2017-05-23-12-07-14-028.png, image-2017-05-23-12-10-06-694.png, screenshot-1.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (JBIDE-24780) Creatinng an OpenShift server adapter should suggest placing Web facet on related project(s)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24780?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-24780:
----------------------------------------
It's the case of a C# ASP.NET application created with aCute. The application isn't created with the Web facet simply because the C# tools don't depend on WTP. However, when trying to bind it to OpenShift (and not really before), adding the Web facet seemed useful. Hence why I suggest to create the Facet as part of the "connect to OpenShift application" workflow.
> Creatinng an OpenShift server adapter should suggest placing Web facet on related project(s)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-24780
> URL: https://issues.jboss.org/browse/JBIDE-24780
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Mickael Istria
> Fix For: 4.5.x
>
>
> I've created an OpenShift Application from Eclipse IDE providing it an Eclipse Project as input.
> Then I tried to create a server adapter for this project. It didn't work initially because the project isn't a Faceted Web project. I had to quit the OpenShift wizard, make the project a faceted one and restart the wizard.
> I would expect the wizard to create a server adapter to suggest and link to a way to make the project associated with the application a web project in Eclipse IDE so it's one less step to understand for users before it works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months