September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23203) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [LiveReload]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23203?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-23203: ------------------------------------- Resolution: (was: Done) Assignee: Xavier Coulon (was: Jeff MAURY) reopening to bump component version to fix JBDS-4055 before codefreeze > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [LiveReload] > -------------------------------------------------------------------- > > Key: JBIDE-23203 > URL: https://issues.jboss.org/browse/JBIDE-23203 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [LiveReload]: Please perform the following tasks: > 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.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.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 LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[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 updated JBIDE-22626: ------------------------------------- Attachment: ImageStreamTags.jpg [~jeffmaury][~jcantrill] i've started to investigate this problem from scratch after reading OS documentation about working with Dokcer images in OS. I've reset all my changes and tested master. 1) I 'mvn clean install' aloha project 2) Built a docker image for cdk docker connection 3) add a 0.1 tag to the image 4) Deployed image to OS with pushing to registry DC and Image stream were created. Image stream has 0.1 tag. DC has: {code:json} triggers: - type: "ConfigChange" - type: ImageChange imageChangeParams: automatic: true containerNames: - aloha from: kind: ImageStreamTag namespace: sample-project name: 'aloha:0.1' lastTriggeredImage: '172.30.74.175:5000/sample-project/aloha@sha256:964d13ef4d3cd1ccc548f48a1e60a388a0fa99cba54c735c95cd5b79d08fbc31' {code} 5) i changed a bit the sources of aloha and repeated all previous steps but not added tag 0.2, which is now the :latest Image stream has now 2 tags and that's right. However DC didn't change, as it is stated in this JIRA description. However, [here it is said|https://docs.openshift.com/enterprise/latest/dev_guide/deployments.h...], that {panel:title=Image Change Trigger} With the above example, when the latest tag value of the origin-ruby-sample image stream changes and the new image value differs from the current image specified in the deployment configuration’s helloworld container, a new deployment is created using the new image for the helloworld container. {panel} The tag in the Image Stream changed, image value is different (it can be see from web console, when viewing image stream tags [^ImageStreamTags.jpg]). [~jcantrill] do you have any guesses why wasn't it trigerred? > 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

1
0
0 / 0

[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 updated JBIDE-22626: ------------------------------------- Description: 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... was: 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. > 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 > > > 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

1
0
0 / 0

[JBoss JIRA] (JBDS-4057) cdk fails, online install

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4057?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-4057: --------------------------------- Component/s: platform-installer (was: installer) > cdk fails, online install > ------------------------- > > Key: JBDS-4057 > URL: https://issues.jboss.org/browse/JBDS-4057 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Misha Ali > > I'm testing the online installer on a win 8 VM. The username is administrator, so we shouldn't face the space in the user name issue. > I've run the online installer thrice now and every component has installed, but CDK fails with no useful error message or log. I don't know if this can be replicated, but I will add the VM I'm using in an internal comment for testing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23203) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [LiveReload]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23203?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-23203. --------------------------------- Resolution: Done PR merged but component version remained to {{1.4.1}} since no change was done so far in the 4.4.2 stream. > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [LiveReload] > -------------------------------------------------------------------- > > Key: JBIDE-23203 > URL: https://issues.jboss.org/browse/JBIDE-23203 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [LiveReload]: Please perform the following tasks: > 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.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.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 LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23199) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Webservices]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23199?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-23199: ---------------------------------- Assignee: Jeff MAURY (was: Xavier Coulon) > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Webservices] > --------------------------------------------------------------------- > > Key: JBIDE-23199 > URL: https://issues.jboss.org/browse/JBIDE-23199 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Webservices]: Please perform the following tasks: > 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.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.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 Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4054) publish rpms + metadata to /latest/ locations so they can be easily installed by QE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4054?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4054: ----------------------------- Parent: (was: JBDS-3982) Issue Type: Task (was: Sub-task) > publish rpms + metadata to /latest/ locations so they can be easily installed by QE > ----------------------------------------------------------------------------------- > > Key: JBDS-4054 > URL: https://issues.jboss.org/browse/JBDS-4054 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, rpm > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM1 > > Attachments: rh-eclipse46-devstudio.repo > > > Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg., > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l... > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_10.0.neo... > * https://devstudio.redhat.com/10.0/staging/builds/devstudio-10.1.0.GA-buil... > * https://devstudio.redhat.com/static/10.0/stable/builds/devstudio-10.1.0.G... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-422) tycho-extras:compare-version-with-baselines does not work for features [EBZ#502009]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-422: --------------------------------------- Summary: tycho-extras:compare-version-with-baselines does not work for features [EBZ#502009] Key: ERT-422 URL: https://issues.jboss.org/browse/ERT-422 Project: Eclipse Release Train Issue Type: Task Components: Tycho Reporter: Friendly Jira Robot When a feature is compared to baselines, if the source feature is generated during the build, the check fail for the source feature because the baseline artifact is compared to the wrong artifact (the binary one and not the source one) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4059: ---------------------------------- {code} rh-eclipse46-devstudio-1.0-1.20160920.1303.el7.x86_64: /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/components/libmozgnome.so: unresolved symbols found: libORBit-2.so.0 => not found libgnomevfs-2.so.0 => not found libnotify.so.1 => not found rh-eclipse46-devstudio-1.0-1.20160920.1303.el7.x86_64: /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/components/libnkgnomevfs.so: unresolved symbols found: libgnomevfs-2.so.0 => not found libORBit-2.so.0 => not found rh-eclipse46-devstudio-1.0-1.20160920.1303.el7.x86_64: /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/xpidl: unresolved symbols found: libIDL-2.so.0 => not found rh-eclipse46-eclipse-swt-4.6.1-2.2.el7.x86_64: /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/plugins/org.eclipse.swt.gtk.linux.x86_64_3.105.1.v20160920-1429/libswt-awt-gtk-4626.so: unresolved symbols found: libjawt.so => not found {code} Never assume something is obvious! Better to be explicit and state what I need to do than to assume I'm an expert in RPM packaging. (This is my first-ever rpm build.) :D {code} for so in libORBit-2 libgnomevfs-2 libnotify libIDL-2; do dnf -b provides */${so}.so.* | egrep "el7.x86_64" | uniq | tail -1 | sed -e "s#$[^:]\+$ : .\+#\1#"; done # or for so in libORBit-2 libgnomevfs-2 libnotify libIDL-2; do yum whatprovides */${so}.so.* | egrep "el7.x86_64" | uniq | tail -1 | sed -e "s#$[^:]\+$ : .\+#\1#"; done # need all 4 of these: ORBit2-2.14.19-13.el7.x86_64 gnome-vfs2-2.24.4-14.el7.x86_64 libnotify-0.7.5-8.el7.x86_64 libIDL-0.8.14-8.el7.x86_64 yum whatprovides */libjawt.so | egrep "el7.*x86_64" | egrep -v "Filename|debug|1\.6" | uniq | sed -e "s#$[^:]\+$ : .\+#\1#" > /tmp/list; cat /tmp/list | sort | uniq # need one or more of these: java-1.7.0-openjdk-headless-1:1.7.0.91-2.6.2.3.el7.x86_64 java-1.8.0-openjdk-1:1.8.0.65-3.b17.el7.x86_64 java-1.8.0-openjdk-devel-1:1.8.0.65-3.b17.el7.x86_64 {code} [~mat.booth] [~rgrunber] Should we add these package deps to the spec file for rh-eclipse46-devstudio, or rh-eclipse46-base ? > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23212: ------------------------------------ Workaround: {code} rm -fr ~/.m2/repository/.{cache,meta}/ mvn clean verify -DskipTests{code} {code} [INFO] central.maven.examples.site ........................ SUCCESS [ 9.547 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 14:34 min {code} > when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho, > Fix For: 4.4.2.AM1 > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2016