[JBoss JIRA] (JBIDE-24515) org.jboss.tools.browsersim.ui requires jetty 9.4.0, but 9.4.5 is in Oxygen.0.M7
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24515?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-24515:
----------------------------------
Assignee: Jeff MAURY
> org.jboss.tools.browsersim.ui requires jetty 9.4.0, but 9.4.5 is in Oxygen.0.M7
> -------------------------------------------------------------------------------
>
> Key: JBIDE-24515
> URL: https://issues.jboss.org/browse/JBIDE-24515
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.5.0.AM1
>
>
> org.jboss.tools.browsersim.ui requires jetty 9.4.0, but 9.4.5 is in Oxygen.0.M7
> {code}
> 17:55:11 [ERROR] Cannot resolve project dependencies:
> 17:55:11 [ERROR] Software being installed: com.jboss.devstudio.core.rpm.feature.feature.group 11.0.0.qualifier
> 17:55:11 [ERROR] Missing requirement: org.jboss.tools.browsersim.ui 3.8.4.v20170227-1025 requires 'bundle org.eclipse.jetty.server [9.4.0,9.4.1)' but it could not be found
> 17:55:11 [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.rpm.feature.feature.group 11.0.0.qualifier depends on: org.jboss.tools.browsersim.feature.feature.group 0.0.0
> 17:55:11 [ERROR] Cannot satisfy dependency: org.jboss.tools.browsersim.feature.feature.group 3.8.4.v20170227-1025 depends on: org.jboss.tools.browsersim.ui [3.8.4.v20170227-1025]
> {code}
> -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24515) org.jboss.tools.browsersim.ui requires jetty 9.4.0, but 9.4.5 is in Oxygen.0.M7
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24515?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24515:
-------------------------------
Fix Version/s: 4.5.0.AM1
> org.jboss.tools.browsersim.ui requires jetty 9.4.0, but 9.4.5 is in Oxygen.0.M7
> -------------------------------------------------------------------------------
>
> Key: JBIDE-24515
> URL: https://issues.jboss.org/browse/JBIDE-24515
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.5.0.AM1
>
>
> org.jboss.tools.browsersim.ui requires jetty 9.4.0, but 9.4.5 is in Oxygen.0.M7
> {code}
> 17:55:11 [ERROR] Cannot resolve project dependencies:
> 17:55:11 [ERROR] Software being installed: com.jboss.devstudio.core.rpm.feature.feature.group 11.0.0.qualifier
> 17:55:11 [ERROR] Missing requirement: org.jboss.tools.browsersim.ui 3.8.4.v20170227-1025 requires 'bundle org.eclipse.jetty.server [9.4.0,9.4.1)' but it could not be found
> 17:55:11 [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.rpm.feature.feature.group 11.0.0.qualifier depends on: org.jboss.tools.browsersim.feature.feature.group 0.0.0
> 17:55:11 [ERROR] Cannot satisfy dependency: org.jboss.tools.browsersim.feature.feature.group 3.8.4.v20170227-1025 depends on: org.jboss.tools.browsersim.ui [3.8.4.v20170227-1025]
> {code}
> -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24515) org.jboss.tools.browsersim.ui requires jetty 9.4.0, but 9.4.5 is in Oxygen.0.M7
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-24515:
----------------------------------
Summary: org.jboss.tools.browsersim.ui requires jetty 9.4.0, but 9.4.5 is in Oxygen.0.M7
Key: JBIDE-24515
URL: https://issues.jboss.org/browse/JBIDE-24515
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: browsersim
Affects Versions: 4.5.0.AM1
Reporter: Nick Boldt
org.jboss.tools.browsersim.ui requires jetty 9.4.0, but 9.4.5 is in Oxygen.0.M7
{code}
17:55:11 [ERROR] Cannot resolve project dependencies:
17:55:11 [ERROR] Software being installed: com.jboss.devstudio.core.rpm.feature.feature.group 11.0.0.qualifier
17:55:11 [ERROR] Missing requirement: org.jboss.tools.browsersim.ui 3.8.4.v20170227-1025 requires 'bundle org.eclipse.jetty.server [9.4.0,9.4.1)' but it could not be found
17:55:11 [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.rpm.feature.feature.group 11.0.0.qualifier depends on: org.jboss.tools.browsersim.feature.feature.group 0.0.0
17:55:11 [ERROR] Cannot satisfy dependency: org.jboss.tools.browsersim.feature.feature.group 3.8.4.v20170227-1025 depends on: org.jboss.tools.browsersim.ui [3.8.4.v20170227-1025]
{code}
-- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24401) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Discovery]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24401?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24401:
------------------------------------
Forgot to update 4.70.x TP to include TestNG 6.11. Fixed here:
https://github.com/jbosstools/jbosstools-target-platforms/pull/262
https://github.com/jbosstools/jbosstools-discovery/pull/358
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Discovery]
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-24401
> URL: https://issues.jboss.org/browse/JBIDE-24401
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central-update
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [Discovery]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-discovery at https://github.com/jbosstools/jbosstools-discovery
> Searching for commits present in master and missing from jbosstools-4.4.x
> Commit hash "3532f2" is the last common ancestor of master and jbosstools-4.4.x
> 3532f2 is 19 commits ago in branch jbosstools-4.4.x
> 3532f2 is 15 commits ago in branch master
> Commits missing from jbosstools-4.4.x that are in master:
> * missing: JBIDE-23834-remove-PMD-from-Central-until-it-can-be-fixed-upstream https://github.com/jbosstools/jbosstools-discovery/commit/83ea8e0fa6ab116...
> ** possible match: https://github.com/jbosstools/jbosstools-discovery/commit/e61a68ba5f87ee9...
> *** Inspect the difference between the two patches: http://sprunge.us/JNhE
> * missing: JBDS-4345-bump-to-11.0.0-in-master-branch https://github.com/jbosstools/jbosstools-discovery/commit/04b6f5dfb63e764...
> * missing: move-up-to-testng-6.11.0.201703011520-in-master-branch https://github.com/jbosstools/jbosstools-discovery/commit/5ffdf1baef5660a...
> * missing: remove-unnededed-mylyn-and-aspectj-ajdt-stuff https://github.com/jbosstools/jbosstools-discovery/commit/b67409a73fe2a11...
> * missing: JBIDE-23317-prepare-first-draft-of-Oxygen.0.M5-target-platform-needs-to-have-IU-versions-updated-so-don-t-merge-yet https://github.com/jbosstools/jbosstools-discovery/commit/53ea8422aed76d2...
> * missing: prepare-for-4.5.0.AM1-in-master https://github.com/jbosstools/jbosstools-discovery/commit/43f27ac24e8c9d9...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Discovery task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-23317) Create and use Oxygen.0.M7 target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23317?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23317:
------------------------------------
Updating TP to include Jetty 9.4.5:
https://github.com/jbosstools/jbosstools-target-platforms/pull/262
Re: Reddeer changes, see JBIDE-24124 and JBIDE-24284
> Create and use Oxygen.0.M7 target platform
> ------------------------------------------
>
> Key: JBIDE-23317
> URL: https://issues.jboss.org/browse/JBIDE-23317
> Project: Tools (JBoss Tools)
> Issue Type: Component Upgrade
> Components: target-platform
> Affects Versions: 4.4.1.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.5.0.AM1
>
> Attachments: duplicate-plugins.jbt.tp.470.M7.txt, p2diff.M5vsM7.txt, p2diff.M5vsM7_ignore_versions.txt, p2diff.M5vsM7_ignore_versions_sorted.txt, p2diff.M5vsM7_ignore_versions_summary.txt, p2diff.M5vsM7_summary.txt
>
>
> Once available on Feb 02/2017, we should create a new 4.70.0.AM1-SNAPSHOT target platform containing Oxygen.0.M5 bits.
> https://wiki.eclipse.org/index.php?title=Oxygen/Simultaneous_Release_Plan...
> Story points: 21 (fibonacci)
> jbt tp,
> jbds tp,
> central tp;
> jbt-build-sites,
> jbds site build;
> update install/matrix jobs to use new Eclipse JEE/platform binary;
> mailing list announcements
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24453) NoClassDefFoundError below CDKDockerUtility.<init> (thrown in DockerClientFactory.getClient)
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24453?page=com.atlassian.jira.plugi... ]
Jeff Johnston commented on JBIDE-24453:
---------------------------------------
Hi Andre,
I'm noticing two versions for Linux Tools Docker core being shown above. The error above occurs when docker client cannot load due to problems with "its" dependencies. If the user has two versions of docker tools installed, they need to uninstall one of them. Not sure why their system wasn't updated properly. Note, we had an issue with the original 2.3.0 Neon.3 release where docker-client was 3.6.8. We did a respin and back-levelled to 3.4.0 post Neon.3. Nick was aware of this and rebuilt, but perhaps the user has done something outside of normal.
> NoClassDefFoundError below CDKDockerUtility.<init> (thrown in DockerClientFactory.getClient)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-24453
> URL: https://issues.jboss.org/browse/JBIDE-24453
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> java.lang.NoClassDefFoundError: Could not initialize class com.spotify.docker.client.DefaultDockerClient
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:66)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252)
> at org.eclipse.linuxtools.internal.docker.core.DefaultTCPConnectionSettingsProvider.getConnectionSettings(DefaultTCPConnectionSettingsProvider.java:30)
> at org.eclipse.linuxtools.internal.docker.core.DefaultDockerConnectionSettingsFinder.getKnownConnectionSettings(DefaultDockerConnectionSettingsFinder.java:265)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.reloadConnections(DockerConnectionManager.java:60)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.<init>(DockerConnectionManager.java:50)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.getInstance(DockerConnectionManager.java:44)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.<init>(CDKDockerUtility.java:29)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:104)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:182)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:198)
> at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144)
> at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:155)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2191)
> at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1728)
> at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1077)
> at org.eclipse.ui.navigator.CommonViewer.setSelection(CommonViewer.java:370)
> at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:383)
> at org.eclipse.wst.server.ui.internal.cnf.ServerDecoratorsHandler$1.run(ServerDecoratorsHandler.java:58)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4203)
> The reporter(s) left the following comment(s):
> --- Anonymous wrote on 56e0: ---
> cannot select server in server view.
> Bundles:
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.jface | 3.12.2.v20170113-2113 | 3.12.2.v20170113-2113 |
> | org.eclipse.linuxtools.docker.core | 2.1.0.201612072123 | 2.3.0.201703072040 |
> | org.eclipse.swt | 3.105.3.v20170228-0512 | 3.105.3.v20170228-0512 |
> | org.eclipse.ui | 3.108.1.v20160929-1045 | 3.108.1.v20160929-1045 |
> | org.eclipse.ui.navigator | 3.6.101.v20161006-1120 | 3.6.101.v20161006-1120 |
> | org.eclipse.wst.server.ui | 1.5.307.v201611072017 | 1.5.307.v201611072017 |
> | org.jboss.tools.openshift.cdk.server | 3.3.2.v20170216-0102 | 3.3.2.v20170216-0102 |
> Operating Systems:
> | Linux | 3.12.67 | 3.16.0 |
> | MacOSX | 10.12.3 | 10.12.4 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/581a1e4ae4b0e3eea94... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24514) org.jboss.tools.tests version not bumped in master
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24514?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24514:
------------------------------------
PR pushed and build is running. Ran w/o tests locally and passed so figured it'd be safe.
https://github.com/jbosstools/jbosstools-base/pull/583
> org.jboss.tools.tests version not bumped in master
> --------------------------------------------------
>
> Key: JBIDE-24514
> URL: https://issues.jboss.org/browse/JBIDE-24514
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common, foundation
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.AM1
>
>
> This has been failing for several days. Does no one every compile locally and see these failures? Or check the server for failing builds? [~jeffmaury] [~rob.stryker]
> {code}
> 08:48:11 Caused by: org.apache.maven.plugin.MojoFailureException: Only qualifier changed for (org.jboss.tools.tests/3.7.3.v20170419-0633). Expected to have bigger x.y.z than what is available in baseline (3.7.3.v20170414-0943)
> 08:48:11 at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:178)
> 08:48:11 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> 08:48:11 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> 08:48:11 ... 20 more
> 08:48:11 Caused by: org.apache.maven.plugin.MojoFailureException: Only qualifier changed for (org.jboss.tools.tests/3.7.3.v20170419-0633). Expected to have bigger x.y.z than what is available in baseline (3.7.3.v20170414-0943)
> 08:48:11 at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:172)
> 08:48:11 ... 22 more{code}
> -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
> Working on a PR to fix this now.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24514) org.jboss.tools.tests version not bumped in master
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24514?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24514:
-------------------------------
Fix Version/s: 4.5.0.AM1
> org.jboss.tools.tests version not bumped in master
> --------------------------------------------------
>
> Key: JBIDE-24514
> URL: https://issues.jboss.org/browse/JBIDE-24514
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common, foundation
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Fix For: 4.5.0.AM1
>
>
> This has been failing for several days. Does no one every compile locally and see these failures? Or check the server for failing builds? [~jeffmaury] [~rob.stryker]
> {code}
> 08:48:11 Caused by: org.apache.maven.plugin.MojoFailureException: Only qualifier changed for (org.jboss.tools.tests/3.7.3.v20170419-0633). Expected to have bigger x.y.z than what is available in baseline (3.7.3.v20170414-0943)
> 08:48:11 at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:178)
> 08:48:11 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> 08:48:11 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> 08:48:11 ... 20 more
> 08:48:11 Caused by: org.apache.maven.plugin.MojoFailureException: Only qualifier changed for (org.jboss.tools.tests/3.7.3.v20170419-0633). Expected to have bigger x.y.z than what is available in baseline (3.7.3.v20170414-0943)
> 08:48:11 at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:172)
> 08:48:11 ... 22 more{code}
> -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
> Working on a PR to fix this now.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months