July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24641) update readme & root pom for Fuse Extras / SAP tooling to fix license, copyright

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24641?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24641: ---------------------------------- Assignee: Nick Boldt (was: Lars Heinemann) > update readme & root pom for Fuse Extras / SAP tooling to fix license, copyright > -------------------------------------------------------------------------------- > > 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: Nick Boldt > 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24642?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24642: ------------------------------- Component/s: website > 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 > Components: build, website > Reporter: Jesper Skov > Assignee: Nick Boldt > Fix For: LATER > > > 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-24641) update readme terms for Fuse Extras / SAP tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24641?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24641 at 7/4/17 2:13 PM: ------------------------------------------------------------ Fair enough. Then we should at least update the readme [1] so that the above is stated more clearly. [1] https://github.com/jbosstools/jbosstools-fuse-extras/blob/master/README.md Here's a couple PRs for review. https://github.com/jbosstools/jbosstools-fuse-extras/pull/65/files https://github.com/jbosstools/jbosstools-fuse/pull/1001/files Note that the first one includes a fix for the copyright holder/date, and the AGPL license statement in the root pom, which is evidently wrong and should be EPL: https://github.com/jbosstools/jbosstools-fuse-extras/pull/65/commits/acb0... was (Author: nickboldt): Fair enough. Then we should at least update the readme [1] so that the above is stated more clearly. [1] https://github.com/jbosstools/jbosstools-fuse-extras/blob/master/README.md Here's a couple PRs for review. https://github.com/jbosstools/jbosstools-fuse-extras/pull/65/files https://github.com/jbosstools/jbosstools-fuse/pull/1001/files > update readme 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 & root pom 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: ------------------------------- Summary: update readme & root pom for Fuse Extras / SAP tooling (was: update readme terms for Fuse Extras / SAP tooling) > update readme & root pom 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 & root pom for Fuse Extras / SAP tooling to fix license, copyright

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24641?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24641: ------------------------------- Summary: update readme & root pom for Fuse Extras / SAP tooling to fix license, copyright (was: update readme & root pom for Fuse Extras / SAP tooling) > update readme & root pom for Fuse Extras / SAP tooling to fix license, copyright > -------------------------------------------------------------------------------- > > 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 commented on JBIDE-24641: ------------------------------------ Fair enough. Then we should at least update the readme [1] so that the above is stated more clearly. [1] https://github.com/jbosstools/jbosstools-fuse-extras/blob/master/README.md Here's a couple PRs for review. https://github.com/jbosstools/jbosstools-fuse-extras/pull/65/files https://github.com/jbosstools/jbosstools-fuse/pull/1001/files > 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 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: ------------------------------- Summary: update readme terms for Fuse Extras / SAP tooling (was: update readme/license terms for Fuse Extras / SAP tooling) > update readme 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-24529) Some versions of N&N are inaccessible, e.g. 4.3.0.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24529?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24529 at 7/4/17 1:28 PM: ------------------------------------------------------------ Updated fix - only the .Final versions appear on the left nav (even if they're archived), and only the 4.x.y.* versions appear in the list of aggregated versions. !Screenshot_2017-07-04_13-25-49.png|thumbnail! Is that better? If so I will merge from master -> production. See http://tools.stage.jboss.org/documentation/whatsnew/jbosstools/4.4.4.Fina... was (Author: nickboldt): Updated fix - only the .Final versions appear on the left nav (even if they're archived), and only the 4.x.y.* versions appear in the list of aggregated versions. !Screenshot_2017-07-04_13-25-49.png|thumbnail! Is that better? If so I will merge from master -> production. > Some versions of N&N are inaccessible, e.g. 4.3.0.Final > ------------------------------------------------------- > > Key: JBIDE-24529 > URL: https://issues.jboss.org/browse/JBIDE-24529 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.x > > Attachments: Screenshot_2017-06-30_11-57-16.png, Screenshot_2017-07-04_13-25-49.png > > > JBIDE-23779 reduced the amount of versions available at https://tools.jboss.org/documentation/whatsnew/ > which is fine. > But I noticed, that some versions are now inaccessible. > If you go to https://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.4.Final.html you will see several versions in the left-hand menu. The oldest being 4.3.1.Final. Now what if I want to see 4.3.0.Final? I would try Previous Versions, but that's too old - that's an old page where the newest version is 4.2.0.Alpha2. > Currently the only way to find the 4.3.0.Final N&N is to go through the download page: > https://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Final.html > And then click the What's New link there which will take you to > https://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html > So I think we should make sure that pages such as https://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.4.Final.html contain all the relevant versions in the left-hand menu. I assume it's a matter of a list in a config file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24529) Some versions of N&N are inaccessible, e.g. 4.3.0.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24529?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24529: ------------------------------------ Updated fix - only the .Final versions appear on the left nav, and only the 4.x.y.* versions appear in the list of aggregated versions. !Screenshot_2017-07-04_13-25-49.png|thumbnail! Is that better? If so I will merge from master -> production. > Some versions of N&N are inaccessible, e.g. 4.3.0.Final > ------------------------------------------------------- > > Key: JBIDE-24529 > URL: https://issues.jboss.org/browse/JBIDE-24529 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.x > > Attachments: Screenshot_2017-06-30_11-57-16.png, Screenshot_2017-07-04_13-25-49.png > > > JBIDE-23779 reduced the amount of versions available at https://tools.jboss.org/documentation/whatsnew/ > which is fine. > But I noticed, that some versions are now inaccessible. > If you go to https://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.4.Final.html you will see several versions in the left-hand menu. The oldest being 4.3.1.Final. Now what if I want to see 4.3.0.Final? I would try Previous Versions, but that's too old - that's an old page where the newest version is 4.2.0.Alpha2. > Currently the only way to find the 4.3.0.Final N&N is to go through the download page: > https://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Final.html > And then click the What's New link there which will take you to > https://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html > So I think we should make sure that pages such as https://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.4.Final.html contain all the relevant versions in the left-hand menu. I assume it's a matter of a list in a config file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24529) Some versions of N&N are inaccessible, e.g. 4.3.0.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24529?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24529 at 7/4/17 1:27 PM: ------------------------------------------------------------ Updated fix - only the .Final versions appear on the left nav (even if they're archived), and only the 4.x.y.* versions appear in the list of aggregated versions. !Screenshot_2017-07-04_13-25-49.png|thumbnail! Is that better? If so I will merge from master -> production. was (Author: nickboldt): Updated fix - only the .Final versions appear on the left nav, and only the 4.x.y.* versions appear in the list of aggregated versions. !Screenshot_2017-07-04_13-25-49.png|thumbnail! Is that better? If so I will merge from master -> production. > Some versions of N&N are inaccessible, e.g. 4.3.0.Final > ------------------------------------------------------- > > Key: JBIDE-24529 > URL: https://issues.jboss.org/browse/JBIDE-24529 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.x > > Attachments: Screenshot_2017-06-30_11-57-16.png, Screenshot_2017-07-04_13-25-49.png > > > JBIDE-23779 reduced the amount of versions available at https://tools.jboss.org/documentation/whatsnew/ > which is fine. > But I noticed, that some versions are now inaccessible. > If you go to https://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.4.Final.html you will see several versions in the left-hand menu. The oldest being 4.3.1.Final. Now what if I want to see 4.3.0.Final? I would try Previous Versions, but that's too old - that's an old page where the newest version is 4.2.0.Alpha2. > Currently the only way to find the 4.3.0.Final N&N is to go through the download page: > https://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Final.html > And then click the What's New link there which will take you to > https://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html > So I think we should make sure that pages such as https://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.4.Final.html contain all the relevant versions in the left-hand menu. I assume it's a matter of a list in a config file. -- 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