July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24643) NoStackTrace in StandardFileSystemPublishController.markModulePublished

by Automated Error Reporting Bot (JIRA)

Automated Error Reporting Bot created JBIDE-24643: ----------------------------------------------------- Summary: NoStackTrace in StandardFileSystemPublishController.markModulePublished Key: JBIDE-24643 URL: https://issues.jboss.org/browse/JBIDE-24643 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Reporter: Automated Error Reporting Bot The following problem was reported via the automated error reporting: Message: Unable to delete module com.ctrlflow.aer.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted. at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.markModulePublished(StandardFileSystemPublishController.java:584) at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.removeModule(StandardFileSystemPublishController.java:482) at org.jboss.tools.as.core.server.controllable.subsystems.internal.WildFlyFileSystemPublishController.removeModule(WildFlyFileSystemPublishController.java:36) at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.publishModule(StandardFileSystemPublishController.java:332) at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) The reporter(s) left the following comment(s): --- Aurélien Pupier wrote on a317: --- I created an openShift Server Adapter for a FIS project Bundles: | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.9.0.v20170322-0013 | | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.1.v20161107-2032 | | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 | | org.eclipse.debug.core | 3.10.100.v20160419-1720 | 3.10.100.v20160419-1720 | | org.eclipse.debug.ui | 3.11.202.v20161114-0338 | 3.11.202.v20161114-0338 | | org.eclipse.jdt.debug | 3.10.0.v20160418-1524 | 3.10.1.v20160811-0441 | | org.eclipse.jface | 3.12.1.v20160923-1528 | 3.12.1.v20160923-1528 | | org.eclipse.m2e.core | 1.7.0.20160603-1933 | 1.7.1.20161104-1805 | | org.eclipse.m2e.core.ui | 1.7.1.20161104-1805 | 1.7.1.20161104-1805 | | org.eclipse.m2e.wtp | 1.3.1.20160831-1005 | 1.3.1.20160831-1005 | | org.eclipse.m2e.wtp.overlay | 1.3.0.20160530-2310 | 1.3.2.20161026-1738 | | org.eclipse.swt | 3.105.2.v20161122-0613 | 3.105.2.v20161122-0613 | | org.eclipse.wst.server.core | 1.8.0.v201601132253 | 1.10.0.v201705172051 | | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 | | org.jboss.ide.eclipse.as.ui | 3.2.3.v20170123-1748 | 3.2.3.v20170123-1748 | | org.jboss.ide.eclipse.as.wtp.core | 3.2.1.v20160711-1757 | 3.3.0.v20170606-1714 | | org.jboss.tools.common.el.core | 3.8.4.v20170316-1803 | 3.8.4.v20170316-1803 | | org.jboss.tools.common.validation | 3.8.4.v20170316-1803 | 3.8.4.v20170316-1803 | | org.jboss.tools.jst.web.kb | 3.8.3.v20161214-1634 | 3.8.3.v20161214-1634 | | org.jboss.tools.openshift.core | 3.3.3.v20170405-1252 | 3.3.3.v20170405-1252 | Operating Systems: | Linux | 2.6.32.13 | 4.11.7 | | MacOSX | 10.10.5 | 10.12.5 | | 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/57a218b3e4b0fe642b1... 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24540) Remove Openshift 2 tooling

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24540?page=com.atlassian.jira.plugi... ] Pavol Pitonak commented on JBIDE-24540: --------------------------------------- [~nickboldt] [~rhopp] Is there any OpenShift v2 documentation that need to be removed/updated? > Remove Openshift 2 tooling > -------------------------- > > Key: JBIDE-24540 > URL: https://issues.jboss.org/browse/JBIDE-24540 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > End of support of Openshift 2 was in December 2016 [1] > There was a mail thread back in November/December 2016, where Todd stated, that Devstudio 11 would be the right release for dropping Openshift 2 support from Tools/Devstudio [2][3]. > Should we get PM/PgM approval once again just to be sure we are OK with removing Openshift 2 tooling from Tools/Devstudio? > [1] https://access.redhat.com/support/policy/updates/openshift/ > [2] http://post-office.corp.redhat.com/archives/devtools-program/2016-Novembe... > [3] http://post-office.corp.redhat.com/archives/devtools-program/2016-Decembe... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24641) update readme/license terms for Fuse Extras / SAP tooling

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24641?page=com.atlassian.jira.plugi... ] Lars Heinemann commented on JBIDE-24641: ---------------------------------------- As far as I remember the reason for putting the SAP tooling into a separate repo was that we wanted to exclude code which makes use of non-opensource code. (means usage of classes which are part of closed source libs like the SAP connector ones). The closed source libraries are to be downloaded from the SAP customer account manually. I don't see why we should add the SAP license text into our repo? We are just using their classes, we are not providing their libraries. > update readme/license terms for Fuse Extras / SAP tooling > --------------------------------------------------------- > > Key: JBIDE-24641 > URL: https://issues.jboss.org/browse/JBIDE-24641 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.AM2 > > > Had another look into the sources of https://github.com/jbosstools/jbosstools-fuse-extras and the ONLY license mention I see that isn't EPL is this: > {quote} > Copyright (C) 2010 FuseSource, Corp. All rights reserved. > http://fusesource.com > The software in this package is published under the terms of the AGPL license > a copy of which has been included with this distribution in the license.txt file.{quote} -- https://github.com/jbosstools/jbosstools-fuse-extras/blob/master/pom.xml#... > But there's no license.txt file, and the LICENSE file is a copy of the EPL, not a *GPL license. > So... can someone ( [~lhein] ? [~aurelien.pupier] ?) point me to where the non-EPL sources actually are, or where non-EPL stuff is downloaded? If not, I'll update this root pom to replace Copyright FuseSource with the usual Red Hat copyright 2017, with FuseSource as an initial contributor. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24642) Please include sha256 checksums in announcements

by Jesper Skov (JIRA)

Jesper Skov created JBIDE-24642: ----------------------------------- Summary: Please include sha256 checksums in announcements Key: JBIDE-24642 URL: https://issues.jboss.org/browse/JBIDE-24642 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Jesper Skov I would like to be able to verify checksums on downloaded JBoss artifacts - both EAP and eclipse-related binaries. Or even better, verify a signature. Today, when I want to use a JBossTools release, I would download http://download.jboss.org/jbosstools/static/oxygen/development/updates/co... And my only opportunity to verify the file is by downloading the sha256 file that lies next to it: http://download.jboss.org/jbosstools/static/oxygen/development/updates/co... If a hacker manages to replace the updatesite archive with compromised files, I assume they will have the brains to also update the checksum file next to it. So the current checksum can really only be used to verify the integrity of the downloaded file. Not that its contents is untampered. If the jar-files in the archive were signed, it would be less of an issue... Signed artifacts would be best. But would probably take some effort to put in place. A simpler remedy would be to include the checksums in the announcement. This would give an additional factor of security for those who care about that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24519) Ensure SAP tooling is available from within JBT/devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24519?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24519 at 7/2/17 4:35 PM: ------------------------------------------------------------ Issue w/ license & readme moved to separate JIRA, so I can resolve this.See JBIDE-24641 was (Author: nickboldt): Issue w/ license & readme moved to separate JIRA: https://issues.jboss.org/browse/JBIDE-24641 > Ensure SAP tooling is available from within JBT/devstudio > ---------------------------------------------------------- > > Key: JBIDE-24519 > URL: https://issues.jboss.org/browse/JBIDE-24519 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Need to make sure that whatever magic happens today in the IS for supporting the SAP Tooling gets migrated to JBT/devstudio. > {quote} > Github = https://github.com/jbosstools/jbosstools-fuse-extras > CCI PR Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > CCI Update SIte Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > Update Site CI: http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-f... > SAP data layer: http://fuse-sap.mw.lab.eng.bos.redhat.com/repositories/fuse-sap-data-laye... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24641) update readme/license terms for Fuse Extras / SAP tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24641?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24641: ---------------------------------- Assignee: Lars Heinemann > update readme/license terms for Fuse Extras / SAP tooling > --------------------------------------------------------- > > Key: JBIDE-24641 > URL: https://issues.jboss.org/browse/JBIDE-24641 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.AM2 > > > Had another look into the sources of https://github.com/jbosstools/jbosstools-fuse-extras and the ONLY license mention I see that isn't EPL is this: > {quote} > Copyright (C) 2010 FuseSource, Corp. All rights reserved. > http://fusesource.com > The software in this package is published under the terms of the AGPL license > a copy of which has been included with this distribution in the license.txt file.{quote} -- https://github.com/jbosstools/jbosstools-fuse-extras/blob/master/pom.xml#... > But there's no license.txt file, and the LICENSE file is a copy of the EPL, not a *GPL license. > So... can someone ( [~lhein] ? [~aurelien.pupier] ?) point me to where the non-EPL sources actually are, or where non-EPL stuff is downloaded? If not, I'll update this root pom to replace Copyright FuseSource with the usual Red Hat copyright 2017, with FuseSource as an initial contributor. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24641) update readme/license terms for Fuse Extras / SAP tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24641?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24641: ------------------------------- Fix Version/s: 4.5.0.AM2 > update readme/license terms for Fuse Extras / SAP tooling > --------------------------------------------------------- > > Key: JBIDE-24641 > URL: https://issues.jboss.org/browse/JBIDE-24641 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.AM2 > > > Had another look into the sources of https://github.com/jbosstools/jbosstools-fuse-extras and the ONLY license mention I see that isn't EPL is this: > {quote} > Copyright (C) 2010 FuseSource, Corp. All rights reserved. > http://fusesource.com > The software in this package is published under the terms of the AGPL license > a copy of which has been included with this distribution in the license.txt file.{quote} -- https://github.com/jbosstools/jbosstools-fuse-extras/blob/master/pom.xml#... > But there's no license.txt file, and the LICENSE file is a copy of the EPL, not a *GPL license. > So... can someone ( [~lhein] ? [~aurelien.pupier] ?) point me to where the non-EPL sources actually are, or where non-EPL stuff is downloaded? If not, I'll update this root pom to replace Copyright FuseSource with the usual Red Hat copyright 2017, with FuseSource as an initial contributor. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24519) Ensure SAP tooling is available from within JBT/devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24519?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24519 at 7/2/17 4:34 PM: ------------------------------------------------------------ Issue w/ license & readme moved to separate JIRA: https://issues.jboss.org/browse/JBIDE-24641 was (Author: nickboldt): Had another look into the sources of https://github.com/jbosstools/jbosstools-fuse-extras and the ONLY license mention I see that isn't EPL is this: {quote} Copyright (C) 2010 FuseSource, Corp. All rights reserved. http://fusesource.com The software in this package is published under the terms of the AGPL license a copy of which has been included with this distribution in the license.txt file.{quote} -- https://github.com/jbosstools/jbosstools-fuse-extras/blob/master/pom.xml#... But there's no license.txt file, and the LICENSE file is a copy of the EPL, not a *GPL license. So... can someone ( [~lhein] ? [~aurelien.pupier] ?) point me to where the non-EPL sources actually are, or where non-EPL stuff is downloaded? If not, I'll update this root pom to replace Copyright FuseSource with the usual Red Hat copyright 2017, with FuseSource as an initial contributor. > Ensure SAP tooling is available from within JBT/devstudio > ---------------------------------------------------------- > > Key: JBIDE-24519 > URL: https://issues.jboss.org/browse/JBIDE-24519 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Need to make sure that whatever magic happens today in the IS for supporting the SAP Tooling gets migrated to JBT/devstudio. > {quote} > Github = https://github.com/jbosstools/jbosstools-fuse-extras > CCI PR Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > CCI Update SIte Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > Update Site CI: http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-f... > SAP data layer: http://fuse-sap.mw.lab.eng.bos.redhat.com/repositories/fuse-sap-data-laye... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24641) update readme/license terms for Fuse Extras / SAP tooling

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24641: ---------------------------------- Summary: update readme/license terms for Fuse Extras / SAP tooling Key: JBIDE-24641 URL: https://issues.jboss.org/browse/JBIDE-24641 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build, fuse-tooling Affects Versions: 4.5.0.AM2 Reporter: Nick Boldt Had another look into the sources of https://github.com/jbosstools/jbosstools-fuse-extras and the ONLY license mention I see that isn't EPL is this: {quote} Copyright (C) 2010 FuseSource, Corp. All rights reserved. http://fusesource.com The software in this package is published under the terms of the AGPL license a copy of which has been included with this distribution in the license.txt file.{quote} -- https://github.com/jbosstools/jbosstools-fuse-extras/blob/master/pom.xml#... But there's no license.txt file, and the LICENSE file is a copy of the EPL, not a *GPL license. So... can someone ( [~lhein] ? [~aurelien.pupier] ?) point me to where the non-EPL sources actually are, or where non-EPL stuff is downloaded? If not, I'll update this root pom to replace Copyright FuseSource with the usual Red Hat copyright 2017, with FuseSource as an initial contributor. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24540) Remove Openshift 2 tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24540?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24540 at 7/2/17 4:31 PM: ------------------------------------------------------------ I've removed the features from the OOTB installation of JBT and devstudio (CoreTools / Abridged categories, installer contents): * https://github.com/jbosstools/jbosstools-build-sites/commits/master * https://github.com/jbdevstudio/jbdevstudio-product/commit/a5385915ef320d0... And I've marked the Openshift v2 tooling connectors in Central as deprecated. * https://github.com/jbosstools/jbosstools-discovery/commit/6460ca486f94d1d... I've also marked the features themselves deprecated: https://github.com/jbosstools/jbosstools-openshift/pull/1522 [~jeffmaury] [~rpdavis] anything else you'd like done here? was (Author: nickboldt): I've removed the features from the OOTB installation of JBT and devstudio (CoreTools / Abridged categories, installer contents): *https://github.com/jbosstools/jbosstools-build-sites/commits/master * https://github.com/jbdevstudio/jbdevstudio-product/commit/a5385915ef320d0... And I've marked the Openshift v2 tooling connectors in Central as deprecated. * https://github.com/jbosstools/jbosstools-discovery/commit/6460ca486f94d1d... I've also marked the features themselves deprecated: https://github.com/jbosstools/jbosstools-openshift/pull/1522 [~jeffmaury] [~rpdavis] anything else you'd like done here? > Remove Openshift 2 tooling > -------------------------- > > Key: JBIDE-24540 > URL: https://issues.jboss.org/browse/JBIDE-24540 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > End of support of Openshift 2 was in December 2016 [1] > There was a mail thread back in November/December 2016, where Todd stated, that Devstudio 11 would be the right release for dropping Openshift 2 support from Tools/Devstudio [2][3]. > Should we get PM/PgM approval once again just to be sure we are OK with removing Openshift 2 tooling from Tools/Devstudio? > [1] https://access.redhat.com/support/policy/updates/openshift/ > [2] http://post-office.corp.redhat.com/archives/devtools-program/2016-Novembe... > [3] http://post-office.corp.redhat.com/archives/devtools-program/2016-Decembe... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2017