[JBoss JIRA] (JBIDE-20976) Create and use Neon M3 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20976:
-------------------------------
Attachment: p2diff.jbosstools.txt
Updated JBT p2diff for revised PR: [^p2diff.jbosstools.txt]
{code}
p2diff-check.sh p2diff.jbosstools.txt
=== Summary ===
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... contains 778 unique IUs
file:///home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 780 unique IUs
+uk.co.spudsoft.birt.emitters.excel
-org.eclipse.jetty.util
-org.eclipse.jetty.servlet
-org.eclipse.jetty.server
-org.eclipse.jetty.security
-org.eclipse.jetty.osgi.boot
-org.eclipse.jetty.io
-org.eclipse.jetty.http
-org.eclipse.jetty.deploy
-org.eclipse.jetty.continuation
+org.eclipse.birt.report.engine.emitter.prototype.excel
+org.eclipse.birt.report.engine.emitter.odp
+org.eclipse.birt.report.engine.emitter.config.odt
+org.eclipse.birt.report.engine.emitter.config.ods
+org.eclipse.birt.report.engine.emitter.config.odp
+org.eclipse.birt.report.engine.emitter.config.excel
< uk.co.spudsoft.birt.emitters.excel [4.5.0.v201506092134]
> org.eclipse.jetty.util [9.3.5.v20151012]
> org.eclipse.jetty.servlet [9.3.5.v20151012]
> org.eclipse.jetty.server [9.3.5.v20151012]
> org.eclipse.jetty.security [9.3.5.v20151012]
> org.eclipse.jetty.osgi.boot [9.2.9.v20150224]
> org.eclipse.jetty.io [9.3.5.v20151012]
> org.eclipse.jetty.http [9.3.5.v20151012]
> org.eclipse.jetty.deploy [9.2.9.v20150224]
> org.eclipse.jetty.continuation [9.3.5.v20151012]
< org.eclipse.birt.report.engine.emitter.prototype.excel [4.5.0.v201506092134]
< org.eclipse.birt.report.engine.emitter.odp [4.5.0.v201506092134]
< org.eclipse.birt.report.engine.emitter.config.odt [4.5.0.v201506092134]
< org.eclipse.birt.report.engine.emitter.config.ods [4.5.0.v201506092134]
< org.eclipse.birt.report.engine.emitter.config.odp [4.5.0.v201506092134]
< org.eclipse.birt.report.engine.emitter.config.excel [4.5.0.v201506092134]
{code}
List & count (29) of all the jetty stuff in JBT TP:
{code}
$➔ find plugins/ | grep org.eclipse.jetty | grep 9. | grep -v pack.gz |sort| grep 9.*; find plugins/ | grep org.eclipse.jetty | grep 9. | grep -v pack.gz |wc -l
plugins/org.eclipse.jetty.client_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.continuation_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.continuation_9.3.5.v20151012.jar
plugins/org.eclipse.jetty.deploy_9.2.9.v20150224.jar
plugins/org.eclipse.jetty.http_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.http_9.3.5.v20151012.jar
plugins/org.eclipse.jetty.io_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.io_9.3.5.v20151012.jar
plugins/org.eclipse.jetty.osgi.boot_9.2.9.v20150224.jar
plugins/org.eclipse.jetty.proxy_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.rewrite_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.security_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.security_9.3.5.v20151012.jar
plugins/org.eclipse.jetty.server_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.server_9.3.5.v20151012.jar
plugins/org.eclipse.jetty.servlet_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.servlet_9.3.5.v20151012.jar
plugins/org.eclipse.jetty.servlets_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.util_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.util_9.3.5.v20151012.jar
plugins/org.eclipse.jetty.webapp_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.webapp_9.3.3.v20150827.jar
plugins/org.eclipse.jetty.websocket.api_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.websocket.client_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.websocket.common_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.websocket.server_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.websocket.servlet_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.xml_9.3.2.v20150730.jar
plugins/org.eclipse.jetty.xml_9.3.3.v20150827.jar
29
{code}
> Create and use Neon M3 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20976
> URL: https://issues.jboss.org/browse/JBIDE-20976
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: features_Mars.0-vs.1.vs.NeonM2.png.png, JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, p2diff.jbdevstudio_v2.txt, p2diff.jbosstools.txt, plugins_Mars.0-vs.1.vs.NeonM2.png, versionwatch-features.png, versionwatch-plugins.png
>
>
> Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS.
> Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer).
> Details in these logs:
> http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers...
> http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers...
> Affected IUs (now sorted alphabetically):
> {code}
> org.eclipse.core.runtime 3.11.1.v20150903-1804
> org.eclipse.egit 4.0.2.201509141540-r
> org.eclipse.egit.core 4.0.2.201509141540-r
> org.eclipse.egit.doc 4.0.2.201509141540-r
> org.eclipse.egit.ui 4.0.2.201509141540-r
> org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318
> org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318
> org.eclipse.jdt 3.11.1.v20150904-0015
> org.eclipse.jdt.doc.user 3.11.1.v20150819-1130
> org.eclipse.jetty.webapp 9.2.13.v20150730
> org.eclipse.jetty.xml 9.2.13.v20150730
> org.eclipse.jgit 4.0.2.201509141540-r
> org.eclipse.jgit.archive 4.0.2.201509141540-r
> org.eclipse.jst.common.frameworks 1.1.701.v201509021802
> org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356
> org.eclipse.jst.web_core.feature 3.7.1.v201509021802
> org.eclipse.jst.web_ui.feature 3.7.1.v201509021802
> org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443
> org.eclipse.pde 3.11.1.v20150904-0345
> org.eclipse.pde.doc.user 3.11.1.v20150903-1352
> org.eclipse.platform 4.5.1.v20150904-0015
> org.eclipse.platform.doc.user 4.5.1.v20150819-1130
> org.eclipse.rcp 4.5.1.v20150904-0015
> org.eclipse.sapphire 9.0.1.201509151939
> org.eclipse.sapphire.java 9.0.1.201509151939
> org.eclipse.sapphire.java.jdt 9.0.1.201509151939
> org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939
> org.eclipse.sapphire.modeling 9.0.1.201509151939
> org.eclipse.sapphire.modeling.xml 9.0.1.201509151939
> org.eclipse.sapphire.osgi 9.0.1.201509151939
> org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939
> org.eclipse.sapphire.platform 9.0.1.201509151939
> org.eclipse.sapphire.ui 9.0.1.201509151939
> org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939
> org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939
> org.eclipse.sapphire.workspace 9.0.1.201509151939
> org.eclipse.sapphire.workspace.ui 9.0.1.201509151939
> org.eclipse.swt 3.104.1.v20150825-0743
> org.eclipse.wst.common_core.feature 3.7.1.v201508262220
> org.eclipse.wst.common_ui.feature 3.7.1.v201508262220
> org.eclipse.wst.jsdt.feature 1.6.201.v201508262249
> org.eclipse.wst.server.core 1.7.0.v201508271522
> org.eclipse.wst.server.discovery 1.1.0.v201508271522
> org.eclipse.wst.server.ui 1.5.201.v201509022125
> org.eclipse.wst.server_core.feature 3.3.600.v201508271522
> org.eclipse.wst.server_ui.feature 3.3.600.v201509022125
> org.eclipse.wst.validation 1.2.700.v201508251749
> org.eclipse.wst.web_core.feature 3.7.1.v201508271605
> org.eclipse.wst.web_ui.feature 3.7.1.v201509022125
> org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926
> org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3560) Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3560:
--------------------------------------
[~koen.aers] could you please take a look if the affected code is used in Hibernate tooling?
> Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580)
> -------------------------------------------------------------------------
>
> Key: JBDS-3560
> URL: https://issues.jboss.org/browse/JBDS-3560
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 8.1.0.GA, 9.0.0.GA, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Attachments: apache-commons-collections-in-JBDS7,8,9,10.png, apache-commons-collections-in-JBDS7,8,9,10_refs1.png, apache-commons-collections-in-JBDS7,8,9,10_refs10.png, apache-commons-collections-in-JBDS7,8,9,10_refs7.png, apache-commons-collections-in-JBDS7,8,9,10_refs8-IS-fuse.png, apache-commons-collections-in-JBDS7,8,9,10_refs8.png, apache-commons-collections-in-JBDS7,8,9,10_refs9.png
>
>
> This is a container issue to wrap & track https://issues.apache.org/jira/browse/COLLECTIONS-580
> Problem is that JBDS 9 (and probably 8 and 10 too) include org.apache.commons.collections 3.2.0.v2013030210310, which is affected by COLLECTIONS-580 - Arbitrary remote code execution with InvokerTransformer
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3276) JBDS-IS Installer support
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBDS-3276:
----------------------------------
Greetings all watchers...
What do we collectively want to do with this Jira from here? The prototype JBDSIS standalone installer works well and does facilitate the installation of integration stack tooling (like Fuse Tooling or Teiid Designer). The latest user experience testing has shown that the latest batch of users didn't find the
existing install scenario that different from using the standalone installer. (They had more issues with quickstarts, etc than with the actual IS installation).
That being said - it does make things easier so I would say lets go with it. If we reach consensus on that then the following question need to be answered.
1. Should we have 2 standalone installers (one for JBDS and one for JBDSIS) or just 1?
My opinion is that we stay with 2. The JBDSIS installer is a superset of the JBDS installer and allows users to pick what they want. Also - given the
asynchronous release schedule of JBDS and JBDSIS (even if we try to sync as close as possible) - the JBDSIS installer still must be built from the IS
devstudio POM. We don't want the situation of the IS components appearing, disappearing and then appearing again. I think the doc/ QE impact is
manageable.
2. Should we restrict the JBDSIS component content to released plugins only or can it have early access content?
My opinion is that we stay with released content only. In theory if the installer was made available from a clearly marked EA URL then it's no different
than the user selecting 'Enable Early Access' - but it's probably safer to restrict the content to released IS components.
3. There are no blocker issues with this. I can create a separate Jira for the second screen-shot issue above (minor). The first has been addressed.
WDYT
> JBDS-IS Installer support
> -------------------------
>
> Key: JBDS-3276
> URL: https://issues.jboss.org/browse/JBDS-3276
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer, integration-platform, requirements
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Paul Leacu
> Fix For: 9.1.0.Beta1
>
> Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, EA.png, jbds-is-about.png, JBDSIS_installer_9.png, JBDSIS_installer_space.png, mirroringlog.txt, sai1.png
>
>
> As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21072) Application wizard: Server templates tree is not rendered
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21072?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-21072:
----------------------------------
Component/s: upstream
> Application wizard: Server templates tree is not rendered
> ---------------------------------------------------------
>
> Key: JBIDE-21072
> URL: https://issues.jboss.org/browse/JBIDE-21072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3, upstream
> Fix For: 4.3.1.Beta1
>
> Attachments: wizard.png
>
>
> When I select at first a local template then proceed to next wizard page in a New OpenShift Application wizard and hit back button then tree containing server templates is not rendered correctly. Only search text field is shown but the tree with templates is missing there.
> !wizard.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBTIS-267) Performance and memory issues in Switchyard projects using Maven.
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-267?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBTIS-267.
----------------------------
Resolution: Cannot Reproduce Bug
Referring to Mus' comment - increasing the memory:
"The customer case was resolved by increasing the memory when using a workspace with a large number of projects."
Also from Mus:
I still think SWITCHYARD-2051 needs to be resolved with an updated m2e which I believe will help the memory usage.
> Performance and memory issues in Switchyard projects using Maven.
> -----------------------------------------------------------------
>
> Key: JBTIS-267
> URL: https://issues.jboss.org/browse/JBTIS-267
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: switchyard
> Affects Versions: 7.0.1.GA
> Reporter: Mustafa Musaji
> Assignee: Brian Fitzpatrick
> Attachments: log
>
>
> Hitting memory issues when opening a workspace with a number of SY projects using Maven.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBTIS-267) Performance and memory issues in Switchyard projects using Maven.
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBTIS-267?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji commented on JBTIS-267:
--------------------------------------
Think you can close it. The customer case was resolved by increasing the memory when using a workspace with a large number of projects. I still think SWITCHYARD-2051 needs to be resolved with an updated m2e which I believe will help the memory usage.
> Performance and memory issues in Switchyard projects using Maven.
> -----------------------------------------------------------------
>
> Key: JBTIS-267
> URL: https://issues.jboss.org/browse/JBTIS-267
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: switchyard
> Affects Versions: 7.0.1.GA
> Reporter: Mustafa Musaji
> Assignee: Brian Fitzpatrick
> Attachments: log
>
>
> Hitting memory issues when opening a workspace with a number of SY projects using Maven.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21102) OpenShift Explorer: Build/Pod activity should be refreshed automatically
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21102?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21102:
------------------------------------------
[~jcantrill] merged and pushed this to upstream/master
> OpenShift Explorer: Build/Pod activity should be refreshed automatically
> ------------------------------------------------------------------------
>
> Key: JBIDE-21102
> URL: https://issues.jboss.org/browse/JBIDE-21102
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Fix For: 4.4.0.Alpha1
>
>
> Currently, when a build is running on openshift, users need to manually refresh the OpenShift Explorer view, to see when a build or a deployment finishes.
> We need to be able to let the explorer "watch" some specific project events (via websockets or some other method).
> As a workaround we might be able to trigger automatic refreshes of the viewer, every 5secs, when we detect a pod is in pending, building, deploying or some other status.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21102) OpenShift Explorer: Build/Pod activity should be refreshed automatically
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21102?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21102:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.Beta1)
> OpenShift Explorer: Build/Pod activity should be refreshed automatically
> ------------------------------------------------------------------------
>
> Key: JBIDE-21102
> URL: https://issues.jboss.org/browse/JBIDE-21102
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Fix For: 4.4.0.Alpha1
>
>
> Currently, when a build is running on openshift, users need to manually refresh the OpenShift Explorer view, to see when a build or a deployment finishes.
> We need to be able to let the explorer "watch" some specific project events (via websockets or some other method).
> As a workaround we might be able to trigger automatic refreshes of the viewer, every 5secs, when we detect a pod is in pending, building, deploying or some other status.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months