[JBoss JIRA] (JBIDE-22235) NullPointerException in BarrierProgressWaitJob.canceling
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22235?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-22235:
--------------------------------
Story Points: 1
> NullPointerException in BarrierProgressWaitJob.canceling
> --------------------------------------------------------
>
> Key: JBIDE-22235
> URL: https://issues.jboss.org/browse/JBIDE-22235
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.foundation.core.jobs.BarrierProgressWaitJob.canceling(BarrierProgressWaitJob.java:143)
> at org.eclipse.core.internal.jobs.InternalJob.cancel(InternalJob.java:185)
> at org.eclipse.core.runtime.jobs.Job.cancel(Job.java:220)
> at org.jboss.tools.foundation.core.jobs.BarrierProgressWaitJob.monitorSafeJoin(BarrierProgressWaitJob.java:135)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.download(URLTransportUtility.java:330)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.download(URLTransportUtility.java:319)
> at org.jboss.tools.foundation.core.ecf.internal.URLTransportCache.downloadAndCache(URLTransportCache.java:177)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:186)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:88)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:244)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.loadProperties(VersionPropertiesProvider.java:271)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getValue(VersionPropertiesProvider.java:151)
> at org.jboss.tools.project.examples.internal.ProjectExampleJsonProvider.getExamplesUrl(ProjectExampleJsonProvider.java:141)
> at org.jboss.tools.project.examples.internal.ProjectExampleJsonProvider.getExamples(ProjectExampleJsonProvider.java:55)
> at org.jboss.tools.project.examples.internal.ProjectExampleManager.getExamples(ProjectExampleManager.java:60)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$RefreshQuickstartsJob.run(GettingStartedHtmlPage.java:102)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.jboss.tools.central | 2.0.1.Final-v20160401-1059-B103 | 2.0.1.Final-v20160401-1059-B103 |
> | org.jboss.tools.foundation.core | 1.2.1.Final-v20160408-2358-B112 | 1.2.1.Final-v20160408-2358-B112 |
> | org.jboss.tools.project.examples | 3.0.1.Final-v20160401-1059-B103 | 3.0.1.Final-v20160401-1059-B103 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571a1ed7e4b0e9dd9c...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Lars Heinemann commented on JBTIS-654:
--------------------------------------
I am against bundling a runtime. That simply makes no sense when we also provide a simple link in the wizard which lets the user download any specific version of the runtime. That will also couple the tooling again to a fixed runtime version which we don't want to have.
Additionally the runtime would add another ~700 Megabyte to the installer which will make it a huge download. I wouldn't recommend that.
Keep in mind when talking about different versions of the installer that someone has to test each version. That will be a lot of extra effort for the QE team.
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-654:
----------------------------------
[~bfitzpat] - that makes sense to me but we would need to proceed carefully. Random thoughts:
* We can't get the Fuse Tooling production build (and the JBDSIS build by extension) caught on the Fuse Runtime (we need to preserve the ability to release autonomously).
* The stand-alone IS installer today is just shy of 1Gb - do we have an idea what the toal aggregate size would be if we add the Fuse runtime?
* If we add the Fuse runtime should we consider a Fuse stand-alone installer (not JBDSIS - just Fuse)?
* Should we do both - an aggregate JBDSIS stand-alone installer which includes Fuse Tooling (and the rest of the stack) and a separate Fuse stand-alone isntaller containg just Fuse Tooling and runtime?
* Any changes to the JBDS installer mechanism would have to occur in 10.x (Neon) if we find something that needs changes there.
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22237) Property table is not updated when resource is selected and edited
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22237?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-22237:
----------------------------------
Affects Version/s: 4.3.1.Beta2
(was: 4.4.0.Alpha1)
> Property table is not updated when resource is selected and edited
> ------------------------------------------------------------------
>
> Key: JBIDE-22237
> URL: https://issues.jboss.org/browse/JBIDE-22237
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
>
> When an entry is selected in a properties tab for an openshift resource and the resources changes, you can no longer edit/update that resource until its refreshed. For example while implementing scaling, I can select a dc, scale it up, but then receive an error when I immediately try to scale it down because the resource version is out of sync.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3282:
---------------------------------
Fix Version/s: 10.0.0.Alpha1
(was: 9.1.0.GA)
> Screencasts: OpenShift v3
> -------------------------
>
> Key: JBDS-3282
> URL: https://issues.jboss.org/browse/JBDS-3282
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, openshift, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: screencast
> Fix For: 10.0.0.Alpha1
>
>
> A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift.
> Including:
> - OpenShift's new web UI
> - OpenShift Explorer in the context of v3
> - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user
> - an overview of Docker, depends on how 'containers" become visible to our end-user
> and all the typical start, stop, add, delete/remove, view logs, set env vars, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3738) Getting Started / Readme for new users after Dev Platform install is complete
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3738?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3738:
---------------------------------
Fix Version/s: 10.0.0.Alpha1
(was: 9.1.0.GA)
> Getting Started / Readme for new users after Dev Platform install is complete
> -----------------------------------------------------------------------------
>
> Key: JBDS-3738
> URL: https://issues.jboss.org/browse/JBDS-3738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Assignee: Misha Ali
> Priority: Blocker
> Labels: Havoc
> Fix For: 10.0.0.Alpha1
>
>
> Per discussion today, we need some sort of README / Getting Started Guide for new CDK users.
> This could be a link from the last page of the Dev Platform installer to a remote HTML page, but we could also include a copy of that HTML page in the c:\devplatform folder so people can refer to it offline.
> Need to decide where to locate the page online. If the doc can be available before April 12, it could potentially be included in the output of the installer for offline use too.
> URL: http://developers.redhat.com/devstudio-preview
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months