[JBoss JIRA] (JBIDE-26230) Implement Tycho build
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26230?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-26230:
-------------------------------------
[~dbocharov] did a great job implementing this and did it surprisingly quickly. He took our ideas, added his own, and really stretched himself to get this done. We all appreciate it a lot.
> Implement Tycho build
> ---------------------
>
> Key: JBIDE-26230
> URL: https://issues.jboss.org/browse/JBIDE-26230
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-server-protocol
> Affects Versions: 4.9.0.AM1
> Reporter: Jeff MAURY
> Assignee: Dmitrii Bocharov
> Fix For: 4.9.0.Final
>
>
> Switch the Maven build to Tycho for:
> * centralized management of dependencies
> * unit tests in OSGI env
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
by Catherine Robson (JIRA)
[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ]
Catherine Robson commented on JBDS-4730:
----------------------------------------
[~nickboldt] We'll help you out with this, but we need some brand assets to land first before we can. I'm working out how we can track the brand work on the product logos and CodeReady assets, and once those are good we can generate new images that you need for the splash screen, install header, etc.
> [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4730
> URL: https://issues.jboss.org/browse/JBDS-4730
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer
> Affects Versions: 12.9.0.AM3
> Reporter: Nick Boldt
> Priority: Blocker
> Fix For: 12.10.0.AM1
>
>
> Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "Red Hat CodeReady Studio".
> As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/
> We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-26303) ZipException below FileSet.checkType (thrown in ZipFile.read)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26303?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26303:
-------------------------------
Fix Version/s: 4.10.x
(was: 4.9.0.Final)
> ZipException below FileSet.checkType (thrown in ZipFile.read)
> -------------------------------------------------------------
>
> Key: JBIDE-26303
> URL: https://issues.jboss.org/browse/JBIDE-26303
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Reporter: Automated Error Reporting Bot
> Assignee: Jeff MAURY
> Fix For: 4.10.x
>
>
> The following problem was reported via the automated error reporting:
> Message: invalid LOC header (bad signature)
> {noformat}
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(null:-2)
> at java.util.zip.ZipFile.access$1400(null:-1)
> at java.util.zip.ZipFile$ZipFileInputStream.read(null:-1)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(null:-1)
> at java.util.zip.InflaterInputStream.read(null:-1)
> at java.io.BufferedInputStream.fill(null:-1)
> at java.io.BufferedInputStream.read1(null:-1)
> at java.io.BufferedInputStream.read(null:-1)
> at org.eclipse.jdt.internal.compiler.util.Util.getInputStreamAsByteArray(Util.java:525)
> at org.eclipse.jdt.internal.compiler.util.Util.getZipEntryByteContent(Util.java:691)
> at org.eclipse.jdt.internal.core.ClassFile.getJarBinaryTypeInfo(ClassFile.java:359)
> at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:290)
> at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:284)
> at org.eclipse.jdt.internal.core.ClassFile.buildStructure(ClassFile.java:93)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:259)
> at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
> at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:287)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
> at org.eclipse.jdt.internal.core.BinaryType.isAnnotation(BinaryType.java:738)
> at org.jboss.tools.jsf.jsf2.bean.scanner.FileSet.checkType(FileSet.java:80)
> at org.jboss.tools.jsf.jsf2.bean.scanner.FileSet.add(FileSet.java:50)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.buildJars(JSF2ProjectBuilder.java:228)
> at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:138)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder.buildExtensionModels(KbBuilder.java:212)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:133)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.10.0.v20180427-1454 |
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.13.0.v20180512-1138 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.14.0.v20180417-0825 |
> | org.eclipse.debug.core | 3.11.0.v20170605-1534 | 3.11.0.v20170605-1534 |
> | org.eclipse.debug.ui | 3.12.50.v20170920-1329 | 3.12.50.v20170920-1329 |
> | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.14.0.v20180611-0500 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.14.0.v20180528-0519 |
> | org.eclipse.jdt.ui | 3.12.2.v20160929-0804 | 3.12.2.v20160929-0804 |
> | org.eclipse.jst.common.project.facet.core | 1.4.500.v201508121553 | 1.5.0.v201710021614 |
> | org.eclipse.m2e.core | 1.7.0.20160603-1933 | 1.8.3.20180227-2137 |
> | org.eclipse.m2e.core.ui | 1.7.0.20160603-1933 | 1.8.2.20171007-0217 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.701.v201707142105 |
> | org.fusesource.ide.camel.model.service.core | 8.0.0.Final-v20161003-0720-B128 | 10.3.0.v20180406-2149 |
> | org.fusesource.ide.projecttemplates | 8.0.0.Final-v20161003-0720-B128 | 10.3.0.v20180409-0833 |
> | org.jboss.tools.common.el.core | 3.8.4.v20170316-1803 | 3.9.3.v20180215-2018 |
> | org.jboss.tools.common.validation | 3.8.4.v20170316-1803 | 3.9.3.v20180215-2018 |
> | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.300.v20180614-0303 |
> | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.9.0.v20180614-0303 |
> Operating Systems:
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://aer.ctrlflow.com/redhat/reviewers/#!/problems/5729a808e4b0a5...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26160:
-------------------------------
Fix Version/s: 4.9.0.Final
(was: 4.9.x)
> Server Adapter: erroneously stays in [Debugging] when you kill the pod
> ----------------------------------------------------------------------
>
> Key: JBIDE-26160
> URL: https://issues.jboss.org/browse/JBIDE-26160
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: server_adapter
> Fix For: 4.9.0.Final
>
>
> steps:
> # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it
> # ASSERT: server adapter is created
> # EXEC: start the server adapter in Debugging
> # ASSERT: sever adapter is in *[Debugging, Synchronized]* state
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped
> Result:
> The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode.
> Expected result:
> Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25000:
-------------------------------
Fix Version/s: 4.9.0.Final
(was: 4.9.x)
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.9.0.Final
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
> ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-26159) Server adapter: debugging is not stopped if you delete the pod
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26159?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26159:
-------------------------------
Fix Version/s: 4.9.0.Final
(was: 4.9.x)
> Server adapter: debugging is not stopped if you delete the pod
> --------------------------------------------------------------
>
> Key: JBIDE-26159
> URL: https://issues.jboss.org/browse/JBIDE-26159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Priority: Minor
> Labels: port_forwarding, server_adapter
> Fix For: 4.9.0.Final
>
>
> steps:
> Screencast: https://youtu.be/XMA--S9zj6s
> # EXEC: create an application (via ex. nodejs-mongo-persistent template)
> # ASSERT: pod for service is running
> # EXEC: select pod and pick "Port Forwarding..." and start the forwarding
> # ASSERT: forwarding is running
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> Result:
> The port forwarding is still running.
> In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed).
> PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-25586) OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25586?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-25586:
------------------------------------
Tested on FC27 and OpenJDK 9.0.4. This is now ok, I can connect to CDK. Resolving.
> OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK
> ----------------------------------------------------------------
>
> Key: JBIDE-25586
> URL: https://issues.jboss.org/browse/JBIDE-25586
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.2.Final
> Environment: FC27
> OpenJDK 9.0.1
> CDK v3.3.0-rc.1-1
> eclipse.buildId=11.2.0.GA-v20180115-0516-B1866
> java.version=9.0.1
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: cdk, connection
> Fix For: 4.9.0.Final
>
>
> But, connecting to online openshift instance works.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-25586) OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25586?page=com.atlassian.jira.plugi... ]
Jeff MAURY resolved JBIDE-25586.
--------------------------------
Resolution: Cannot Reproduce
> OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK
> ----------------------------------------------------------------
>
> Key: JBIDE-25586
> URL: https://issues.jboss.org/browse/JBIDE-25586
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.2.Final
> Environment: FC27
> OpenJDK 9.0.1
> CDK v3.3.0-rc.1-1
> eclipse.buildId=11.2.0.GA-v20180115-0516-B1866
> java.version=9.0.1
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: cdk, connection
> Fix For: 4.9.0.Final
>
>
> But, connecting to online openshift instance works.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months