[JBoss JIRA] (JBIDE-21452) Server Adapter wizard: Should use deployments-dir as specified (in a label) in the image
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21452?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21452:
--------------------------------
Labels: new_and_noteworthy openshift_v3 server_adapter_wizard (was: openshift_v3 server_adapter_wizard)
> 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: new_and_noteworthy, 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-21481) [server adapter] Allow publishing of wtp-style projects
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21481?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21481:
--------------------------------
Labels: new_and_noteworthy openshift_v3 server_adapter (was: openshift_v3 server_adapter)
> [server adapter] Allow publishing of wtp-style projects
> -------------------------------------------------------
>
> Key: JBIDE-21481
> URL: https://issues.jboss.org/browse/JBIDE-21481
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, server
> Affects Versions: 4.3.1.Beta1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: new_and_noteworthy, openshift_v3, server_adapter
> Fix For: 4.3.1.Beta2
>
>
> The openshift server adapter as currently coded simply copies the magic project into a hidden metadata location and executes an rsync. This won't work for any project iwth a custom wtp-style layout and mappings available, including maven projects created via m2ewtp.
> This jira targets an initial implementation of a zipped publish of wtp-style projects, both as the magic project or as an added module to be deployed along-side the magic project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3586) Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71
by Omair Majid (JIRA)
[ https://issues.jboss.org/browse/JBDS-3586?page=com.atlassian.jira.plugin.... ]
Omair Majid commented on JBDS-3586:
-----------------------------------
Hi, I am an OpenJDK developer. If this is an OpenJDK bug, I would like to fix it. Can you please tell me how to reproduce this? Where can I get 9.1.0.Beta2 from? I just installed 9.1.0.Beta1 but I can't find an "Integration Stack" entry in Help -> Install New Software... menu.
> Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71
> --------------------------------------------------------------------------------------
>
> Key: JBDS-3586
> URL: https://issues.jboss.org/browse/JBDS-3586
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, updatesite
> Affects Versions: 9.1.0.Beta2
> Reporter: Jan Richter
> Priority: Critical
>
> Trying to install IS from central early access, I'm getting the following error:
> {noformat}
> An error occurred while collecting items to be installed
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
> Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.13.0.v20150818-1354.
> Unpacking fails because intermediate file is empty: /tmp/work8606338891825741513/p2.optimizers.incoming8698731202719996837.jar
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21580) TernError: No type found at the given position when invoking Open On for taglib definition
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21580?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-21580:
-----------------------------------------
The issue is reported to tern.java project:
https://github.com/angelozerr/tern.java/issues/392 - TernException occures when trying to open hiperlink in JSP
> TernError: No type found at the given position when invoking Open On for taglib definition
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21580
> URL: https://issues.jboss.org/browse/JBIDE-21580
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, upstream
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2-v20160122-0528-B256 + Mobile Tooling + AngularJS
> Oracle Java 1.8
> Fedora 22 64 bit
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> 1. Create JSF 1.2 project
> 2. Open inputUserName.jsp in VPE
> 3. Hover over <%@ taglib uri="http://java.sun.com/jsf/core"
> 4. Press Ctrl
> ERROR:
> {noformat}
> tern.TernException: TernError: No type found at the given position.
> at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43)
> at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: tern.TernException: TernError: No type found at the given position.
> at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86)
> at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163)
> at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127)
> at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42)
> ... 2 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21439) Add JSON Editor to JBDS/JBT Target Platform
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21439?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21439:
-----------------------------------
Priority: Critical (was: Major)
> Add JSON Editor to JBDS/JBT Target Platform
> -------------------------------------------
>
> Key: JBIDE-21439
> URL: https://issues.jboss.org/browse/JBIDE-21439
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Reporter: Alexey Kazakov
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> Missing description. Need update site from which to fetch IUs, and a list of which IUs to add.
> Also need to know what to do with the JSON editor once it's in the TP... will it be installed OOTB like YAML editor in JBIDE-21377? Or will it be a new Central connector?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months