[JBoss JIRA] (JBIDE-21452) Server Adapter wizard: Should use deployments-dir as specified (in a label) in the image
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21452?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21452:
------------------------------------------
turns out that the labels are present in the rest service/imageStreamTags for images that were built on OpenShift. Using this for now, we'll have to find another solution for non-built images (deploy docker images) later.
> Server Adapter wizard: Should use deployments-dir as specified (in a label) in the image
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-21452
> URL: https://issues.jboss.org/browse/JBIDE-21452
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.3.1.Beta2
>
>
> The server adapter is currently using a hard-coded deployments dir */op/app-root/src* that the user can manually edit in the wizard though.
> The images now specify the deployments-dir in a label (see CLOUD-243)
> {code}
> com.redhat.deployments-dir
> {code}
> We should use this instead of the hard-coded one.
> Latest docker image eap64-openshift (1.2) features the beforementioned label
> ("Labels": { ... "com.redhat.deployments-dir": "/opt/eap/standalone/deployments", ... })
> {code}
> -bash-4.2$ docker inspect registry.access.redhat.com/jboss-eap-6/eap64-openshift:1.2
> [
> {
> "Id": "cd9c11961578733a25875fb51fc94d71135cc52eb270cd58213fe99000b2ce9e",
> "Parent": "a805aea5fb4758b2977ab4fb191f074b41d9bf751b35e0aa0e45e7d70e111134",
> "Comment": "",
> "Created": "2015-12-10T18:32:11.797022Z",
> "Container": "",
> "ContainerConfig": {
> "Hostname": "",
> "Domainname": "",
> "User": "",
> "AttachStdin": false,
> "AttachStdout": false,
> "AttachStderr": false,
> "ExposedPorts": null,
> "PublishService": "",
> "Tty": false,
> "OpenStdin": false,
> "StdinOnce": false,
> "Env": null,
> "Cmd": null,
> "Image": "",
> "Volumes": null,
> "VolumeDriver": "",
> "WorkingDir": "",
> "Entrypoint": null,
> "NetworkDisabled": false,
> "MacAddress": "",
> "OnBuild": null,
> "Labels": null
> },
> "DockerVersion": "1.7.1",
> "Author": "",
> "Config": {
> "Hostname": "",
> "Domainname": "",
> "User": "185",
> "AttachStdin": false,
> "AttachStdout": false,
> "AttachStderr": false,
> "ExposedPorts": {
> "8080/tcp": {},
> "8443/tcp": {},
> "8778/tcp": {}
> },
> "PublishService": "",
> "Tty": false,
> "OpenStdin": false,
> "StdinOnce": false,
> "Env": [
> "container=docker",
> "PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin",
> "JBOSS_IMAGE_NAME=jboss-eap-6/eap64-openshift",
> "JBOSS_IMAGE_VERSION=1.2",
> "JBOSS_IMAGE_RELEASE=14",
> "HOME=/home/jboss",
> "JAVA_TOOL_OPTIONS=-Duser.home=/home/jboss -Duser.name=jboss",
> "JAVA_HOME=/usr/lib/jvm/java-1.8.0",
> "JAVA_VENDOR=openjdk",
> "JAVA_VERSION=1.8.0",
> "LAUNCH_JBOSS_IN_BACKGROUND=true",
> "JBOSS_PRODUCT=eap",
> "JBOSS_EAP_VERSION=6.4.4.GA",
> "JBOSS_HOME=/opt/eap",
> "STI_BUILDER=jee",
> "JBOSS_MODULES_SYSTEM_PKGS=org.jboss.logmanager"
> ],
> "Cmd": [
> "/opt/eap/bin/openshift-launch.sh"
> ],
> "Image": "a805aea5fb4758b2977ab4fb191f074b41d9bf751b35e0aa0e45e7d70e111134",
> "Volumes": {
> "/run": {}
> },
> "VolumeDriver": "",
> "WorkingDir": "/home/jboss",
> "Entrypoint": null,
> "NetworkDisabled": false,
> "MacAddress": "",
> "OnBuild": [],
> "Labels": {
> "Architecture": "x86_64",
> "Authoritative_Registry": "registry.access.redhat.com",
> "BZComponent": "jboss-eap-6-eap64-openshift-docker",
> "Build_Host": "rcm-img-docker01.build.eng.bos.redhat.com",
> "Name": "jboss-eap-6/eap64-openshift",
> "Release": "14",
> "Vendor": "Red Hat, Inc.",
> "Version": "1.2",
> "architecture": "x86_64",
> "build-date": "2015-12-10T18:15:59.014349Z",
> "com.redhat.deployments-dir": "/opt/eap/standalone/deployments",
> "com.redhat.dev-mode": "DEBUG:true",
> "com.redhat.dev-mode.port": "DEBUG_PORT:8787",
> "io.k8s.description": "Platform for building and running JavaEE applications on JBoss EAP 6.4",
> "io.k8s.display-name": "JBoss EAP 6.4",
> "io.openshift.expose-services": "8080:http",
> "io.openshift.s2i.scripts-url": "image:///usr/local/s2i",
> "io.openshift.tags": "builder,javaee,eap,eap6",
> "org.jboss.deployments-dir": "/opt/eap/standalone/deployments",
> "vcs-ref": "f0b51e70cc004d21458ca15b1f2087ba5a6af1f7",
> "vcs-type": "git"
> }
> },
> "Architecture": "amd64",
> "Os": "linux",
> "Size": 511678587,
> "VirtualSize": 1206983884,
> "GraphDriver": {
> "Name": "devicemapper",
> "Data": {
> "DeviceId": "43096",
> "DeviceName": "docker-253:0-268481993-cd9c11961578733a25875fb51fc94d71135cc52eb270cd58213fe99000b2ce9e",
> "DeviceSize": "10737418240"
> }
> }
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21452) Server Adapter wizard: Should use deployments-dir as specified (in a label) in the image
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21452?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21452:
------------------------------------------
merged into jbosstools-4.3.x
> Server Adapter wizard: Should use deployments-dir as specified (in a label) in the image
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-21452
> URL: https://issues.jboss.org/browse/JBIDE-21452
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.3.1.Beta2
>
>
> The server adapter is currently using a hard-coded deployments dir */op/app-root/src* that the user can manually edit in the wizard though.
> The images now specify the deployments-dir in a label (see CLOUD-243)
> {code}
> com.redhat.deployments-dir
> {code}
> We should use this instead of the hard-coded one.
> Latest docker image eap64-openshift (1.2) features the beforementioned label
> ("Labels": { ... "com.redhat.deployments-dir": "/opt/eap/standalone/deployments", ... })
> {code}
> -bash-4.2$ docker inspect registry.access.redhat.com/jboss-eap-6/eap64-openshift:1.2
> [
> {
> "Id": "cd9c11961578733a25875fb51fc94d71135cc52eb270cd58213fe99000b2ce9e",
> "Parent": "a805aea5fb4758b2977ab4fb191f074b41d9bf751b35e0aa0e45e7d70e111134",
> "Comment": "",
> "Created": "2015-12-10T18:32:11.797022Z",
> "Container": "",
> "ContainerConfig": {
> "Hostname": "",
> "Domainname": "",
> "User": "",
> "AttachStdin": false,
> "AttachStdout": false,
> "AttachStderr": false,
> "ExposedPorts": null,
> "PublishService": "",
> "Tty": false,
> "OpenStdin": false,
> "StdinOnce": false,
> "Env": null,
> "Cmd": null,
> "Image": "",
> "Volumes": null,
> "VolumeDriver": "",
> "WorkingDir": "",
> "Entrypoint": null,
> "NetworkDisabled": false,
> "MacAddress": "",
> "OnBuild": null,
> "Labels": null
> },
> "DockerVersion": "1.7.1",
> "Author": "",
> "Config": {
> "Hostname": "",
> "Domainname": "",
> "User": "185",
> "AttachStdin": false,
> "AttachStdout": false,
> "AttachStderr": false,
> "ExposedPorts": {
> "8080/tcp": {},
> "8443/tcp": {},
> "8778/tcp": {}
> },
> "PublishService": "",
> "Tty": false,
> "OpenStdin": false,
> "StdinOnce": false,
> "Env": [
> "container=docker",
> "PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin",
> "JBOSS_IMAGE_NAME=jboss-eap-6/eap64-openshift",
> "JBOSS_IMAGE_VERSION=1.2",
> "JBOSS_IMAGE_RELEASE=14",
> "HOME=/home/jboss",
> "JAVA_TOOL_OPTIONS=-Duser.home=/home/jboss -Duser.name=jboss",
> "JAVA_HOME=/usr/lib/jvm/java-1.8.0",
> "JAVA_VENDOR=openjdk",
> "JAVA_VERSION=1.8.0",
> "LAUNCH_JBOSS_IN_BACKGROUND=true",
> "JBOSS_PRODUCT=eap",
> "JBOSS_EAP_VERSION=6.4.4.GA",
> "JBOSS_HOME=/opt/eap",
> "STI_BUILDER=jee",
> "JBOSS_MODULES_SYSTEM_PKGS=org.jboss.logmanager"
> ],
> "Cmd": [
> "/opt/eap/bin/openshift-launch.sh"
> ],
> "Image": "a805aea5fb4758b2977ab4fb191f074b41d9bf751b35e0aa0e45e7d70e111134",
> "Volumes": {
> "/run": {}
> },
> "VolumeDriver": "",
> "WorkingDir": "/home/jboss",
> "Entrypoint": null,
> "NetworkDisabled": false,
> "MacAddress": "",
> "OnBuild": [],
> "Labels": {
> "Architecture": "x86_64",
> "Authoritative_Registry": "registry.access.redhat.com",
> "BZComponent": "jboss-eap-6-eap64-openshift-docker",
> "Build_Host": "rcm-img-docker01.build.eng.bos.redhat.com",
> "Name": "jboss-eap-6/eap64-openshift",
> "Release": "14",
> "Vendor": "Red Hat, Inc.",
> "Version": "1.2",
> "architecture": "x86_64",
> "build-date": "2015-12-10T18:15:59.014349Z",
> "com.redhat.deployments-dir": "/opt/eap/standalone/deployments",
> "com.redhat.dev-mode": "DEBUG:true",
> "com.redhat.dev-mode.port": "DEBUG_PORT:8787",
> "io.k8s.description": "Platform for building and running JavaEE applications on JBoss EAP 6.4",
> "io.k8s.display-name": "JBoss EAP 6.4",
> "io.openshift.expose-services": "8080:http",
> "io.openshift.s2i.scripts-url": "image:///usr/local/s2i",
> "io.openshift.tags": "builder,javaee,eap,eap6",
> "org.jboss.deployments-dir": "/opt/eap/standalone/deployments",
> "vcs-ref": "f0b51e70cc004d21458ca15b1f2087ba5a6af1f7",
> "vcs-type": "git"
> }
> },
> "Architecture": "amd64",
> "Os": "linux",
> "Size": 511678587,
> "VirtualSize": 1206983884,
> "GraphDriver": {
> "Name": "devicemapper",
> "Data": {
> "DeviceId": "43096",
> "DeviceName": "docker-253:0-268481993-cd9c11961578733a25875fb51fc94d71135cc52eb270cd58213fe99000b2ce9e",
> "DeviceSize": "10737418240"
> }
> }
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21510) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Central]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21510?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-21510.
------------------------------
Assignee: Fred Bricon
Resolution: Done
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Central]
> -----------------------------------------------------
>
> Key: JBIDE-21510
> URL: https://issues.jboss.org/browse/JBIDE-21510
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2 [Central]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), you do *not* need to do so again.
> Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
> {code}
> 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
> {code}
> mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta2x
> git push origin jbosstools-4.3.1.Beta2x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.CR1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
> * *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 Central 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)
10 years, 4 months
[JBoss JIRA] (JBIDE-21492) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Aerogear]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21492?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-21492.
------------------------------
Resolution: Done
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Aerogear]
> ------------------------------------------------------
>
> Key: JBIDE-21492
> URL: https://issues.jboss.org/browse/JBIDE-21492
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid, cordovasim
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2 [Aerogear]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), you do *not* need to do so again.
> Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
> {code}
> 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
> {code}
> mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta2x
> git push origin jbosstools-4.3.1.Beta2x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.CR1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
> * *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 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)
10 years, 4 months
[JBoss JIRA] (JBDS-3566) include AERI in JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-3566.
------------------------------
Resolution: Done
Merged.
> include AERI in JBDS
> --------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build, target-platform
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.1.0.Beta2, 10.0.0.Alpha1
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21497) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Server]
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21497?page=com.atlassian.jira.plugi... ]
Rob Stryker closed JBIDE-21497.
-------------------------------
Resolution: Done
done
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Server]
> ----------------------------------------------------
>
> Key: JBIDE-21497
> URL: https://issues.jboss.org/browse/JBIDE-21497
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2 [Server]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), you do *not* need to do so again.
> Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
> {code}
> 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
> {code}
> mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta2x
> git push origin jbosstools-4.3.1.Beta2x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.CR1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
> * *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] 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 Server 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)
10 years, 4 months
[JBoss JIRA] (JBIDE-21341) Credentials: Allow to show password even if you choose to save it
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21341?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21341:
--------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.1.Beta2)
> Credentials: Allow to show password even if you choose to save it
> -----------------------------------------------------------------
>
> Key: JBIDE-21341
> URL: https://issues.jboss.org/browse/JBIDE-21341
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.1.CR1
>
>
> When you add credentials for access.redhat.com account to be used with CDK adapter, you can choose to only save your username and enter password each time. In that case when that happens, you can choose to show the password as you type (i.e. no ****). I think to be consistent you should allow the same when you're creating the credentials and enter the password there.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21302) Removing user from credentials framework while not authenticated to secure storage should not work
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21302?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21302:
--------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.1.Beta2)
> Removing user from credentials framework while not authenticated to secure storage should not work
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21302
> URL: https://issues.jboss.org/browse/JBIDE-21302
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Environment: JBDS 9.0.0.Beta1-v20151210-1836-B183
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> Removing credentials (which are stored in secure storage) using
> CredentialPreferencePage without being authenticated to secure storage (see steps to reproduce on how to do that) seems to delete the credentials, but after eclipse restart, the credentials are still there. I would prefer message saying something like "Unable to delete credentials stored in secure storage without atuhenticating to secure storage".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21170) Virtualbox could not be found by CDK adapter
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21170?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21170:
--------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.1.Beta2)
> Virtualbox could not be found by CDK adapter
> --------------------------------------------
>
> Key: JBIDE-21170
> URL: https://issues.jboss.org/browse/JBIDE-21170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> After I set up a CDK server adapter and fixed the wrong path to vagrant in the launch config, I then started the server adapter and got this:
> Server CDK Server Adapter at localhost failed to start.
> Console:
> {code}
> The provider 'virtualbox' that was requested to back the machine
> 'default' is reporting that it isn't usable on this system. The
> reason is shown below:
> Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
> Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
> this to be available on the PATH. If VirtualBox is installed, please find the
> `VBoxManage` binary and add it to the PATH environmental variable.
> {code}
> Along with this, there was an Unhandled event loop exception in the error view:
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
> at org.eclipse.swt.SWT.error(SWT.java:4491)
> at org.eclipse.swt.SWT.error(SWT.java:4406)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:520)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.updateEarlyAccess(GettingStartedHtmlPage.java:359)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.access$14(GettingStartedHtmlPage.java:342)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$6$1.run(GettingStartedHtmlPage.java:327)
> at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162)
> at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 23 more
> {code}
> In the command line, VBoxManage is accessible and it is located in /usr/local/bin/ and on my PATH.
> Max suggested I could try to start Eclipse from command line instead of double-clicking in Finder (which is the normal way to do it on Mac) and that helped.
> So for some reason when you start Eclipse using Eclipse.app from Finder, the PATH is incorrect.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months