January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4237) Generate CVE vulnerability report for devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4237?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4237: ---------------------------------- Slip to 10.x and assign to Jeff. Not sure if we want to do anything with these reports other than keep them for baseline/reference. > Generate CVE vulnerability report for devstudio > ----------------------------------------------- > > Key: JBDS-4237 > URL: https://issues.jboss.org/browse/JBDS-4237 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, versionwatch > Affects Versions: 10.3.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 10.x > > Attachments: Screenshot_2017-01-10_18-58-03.png, Screenshot_2017-01-10_19-04-45.png > > > 0. download http://dl.bintray.com/jeremy-long/owasp/dependency-check-1.4.4-release.zip > 1. download latest CI build update site zip, target platform zip, central zip, etc. > 2. unpack update site zips > 3. unpack dep-check zip > 4. generate CVE report for each fetched zip: > {code} > ./dependency-check.sh --disableAssembly -s /path/to/update-site/plugins/ --project devstudio_check -o WORKSPACE/path/to/report/folder/ > {code} > Should use https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Dependency-Check+Plugin for better reporting and maybe even enable this on every project job (once moved to CCI Jenkins). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4233) Migrate jbosstools, devstudio, and release process jobs to Central CI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4233?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4233: ----------------------------- Fix Version/s: (was: 10.3.0.AM2) > Migrate jbosstools, devstudio, and release process jobs to Central CI > --------------------------------------------------------------------- > > Key: JBDS-4233 > URL: https://issues.jboss.org/browse/JBDS-4233 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: CCI-installed-plugins-Jenkins-1.609.3-1_list.txt > > > As Bos MW Jenkins is deprecated, it's time to migrate all the jbt 4.4.x and devstudio 10.x jobs to the new server infrastructure. Old jobs from jbt 4.3 / devstudio 9.x will not be migrated. > Installed plugins are not the same on Bos MW and CCI. We'll need to get more plugins installed on CCI to support devstudio jobs. > https://docs.google.com/spreadsheets/d/1WJV3bOdlY1unOH5i23v33V7dZKIqTbo1A... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4237) Generate CVE vulnerability report for devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4237?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4237: -------------------------------- Assignee: Jeff MAURY (was: Nick Boldt) > Generate CVE vulnerability report for devstudio > ----------------------------------------------- > > Key: JBDS-4237 > URL: https://issues.jboss.org/browse/JBDS-4237 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, versionwatch > Affects Versions: 10.3.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 10.x > > Attachments: Screenshot_2017-01-10_18-58-03.png, Screenshot_2017-01-10_19-04-45.png > > > 0. download http://dl.bintray.com/jeremy-long/owasp/dependency-check-1.4.4-release.zip > 1. download latest CI build update site zip, target platform zip, central zip, etc. > 2. unpack update site zips > 3. unpack dep-check zip > 4. generate CVE report for each fetched zip: > {code} > ./dependency-check.sh --disableAssembly -s /path/to/update-site/plugins/ --project devstudio_check -o WORKSPACE/path/to/report/folder/ > {code} > Should use https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Dependency-Check+Plugin for better reporting and maybe even enable this on every project job (once moved to CCI Jenkins). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23318) fork master branch into master and 4.4.x branches, so that master can be for oxygen and 4.4.x can be for Neon.2 and .3 work

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23318?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23318: ------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > fork master branch into master and 4.4.x branches, so that master can be for oxygen and 4.4.x can be for Neon.2 and .3 work > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23318 > URL: https://issues.jboss.org/browse/JBIDE-23318 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.4.x, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.Final, 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4237) Generate CVE vulnerability report for devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4237?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4237: ----------------------------- Fix Version/s: 10.x (was: 10.3.0.AM2) > Generate CVE vulnerability report for devstudio > ----------------------------------------------- > > Key: JBDS-4237 > URL: https://issues.jboss.org/browse/JBDS-4237 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, versionwatch > Affects Versions: 10.3.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.x > > Attachments: Screenshot_2017-01-10_18-58-03.png, Screenshot_2017-01-10_19-04-45.png > > > 0. download http://dl.bintray.com/jeremy-long/owasp/dependency-check-1.4.4-release.zip > 1. download latest CI build update site zip, target platform zip, central zip, etc. > 2. unpack update site zips > 3. unpack dep-check zip > 4. generate CVE report for each fetched zip: > {code} > ./dependency-check.sh --disableAssembly -s /path/to/update-site/plugins/ --project devstudio_check -o WORKSPACE/path/to/report/folder/ > {code} > Should use https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Dependency-Check+Plugin for better reporting and maybe even enable this on every project job (once moved to CCI Jenkins). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23738) create jbosstools rpm that only depends on eclipse-* bundles (and can run on Fedora 24/25)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23738?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23738: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.3.AM2) > create jbosstools rpm that only depends on eclipse-* bundles (and can run on Fedora 24/25) > ------------------------------------------------------------------------------------------ > > Key: JBIDE-23738 > URL: https://issues.jboss.org/browse/JBIDE-23738 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, rpm > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.x > > > Per trello card [1], we should consider having a jbosstools rpm. > Could put the source for this in https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/ or in jbdevstudio-product since it'll be a similar design to that one, including blacklists and dependencies. > [1] https://trello.com/c/YK6rdGRy/14-create-jbosstools-rpm-for-fedora-24-25 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) move to tycho 1.0 (was 0.27.0) :: mvn clean verify checks old features versions against baseline

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23212: ------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > move to tycho 1.0 (was 0.27.0) :: mvn clean verify checks old features versions against baseline > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho > Fix For: 4.4.3.Final > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4257: ----------------------------- Fix Version/s: 10.3.0.GA > rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46 > ------------------------------------------------------------------------------ > > Key: JBDS-4257 > URL: https://issues.jboss.org/browse/JBDS-4257 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.3.0.AM2 > Environment: RHEL7 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.3.0.GA > > Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png > > > I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46. > !yum_install_rh-eclipse46.png|thumbnail! > [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library. > He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages. > [^rh-eclipse46_provides.txt] > [^rh-eclipse46-devstudio_provides.txt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4257 at 1/30/17 4:32 PM: ----------------------------------------------------------- [~vkadlcik] Currently the RPM only installs two features: * com.jboss.devstudio.core.rpm.feature * com.jboss.devstudio.core.capabilities.feature But these drag in all the dependencies they need to complete the installation, including com.google.guava. I tried to remove/blacklist that plugin, but seemed that org.eclipse.m2e needed it (JBDS-4131); however, now that we depend on the org.eclipse.m2e RPM instead of the stuff in the devstudio update site, perhaps we can remove this too. https://github.com/jbdevstudio/jbdevstudio-product/pull/443 I've moved some more p2 deps out of the rpm (as they're now provided by RPM deps): https://github.com/jbdevstudio/jbdevstudio-product/commit/1d53969a727011d... (order of listed IUs fixed to be in alpha order so the diff looks larger than it might otherwise be) was (Author: nickboldt): [~vkadlcik] Currently the RPM only installs two features: * com.jboss.devstudio.core.rpm.feature * com.jboss.devstudio.core.capabilities.feature But these drag in all the dependencies they need to complete the installation, including com.google.guava. I tried to remove/blacklist that plugin, but seemed that org.eclipse.m2e needed it (JBDS-4131); however, now that we depend on the org.eclipse.m2e RPM instead of the stuff in the devstudio update site, perhaps we can remove this too. https://github.com/jbdevstudio/jbdevstudio-product/pull/443 How can I easily determine which requirements for devstudio have already been met by installed rpms? Or migrate p2 dependencies to rpm dependencies? > rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46 > ------------------------------------------------------------------------------ > > Key: JBDS-4257 > URL: https://issues.jboss.org/browse/JBDS-4257 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.3.0.AM2 > Environment: RHEL7 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.3.0.GA > > Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png > > > I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46. > !yum_install_rh-eclipse46.png|thumbnail! > [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library. > He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages. > [^rh-eclipse46_provides.txt] > [^rh-eclipse46-devstudio_provides.txt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4257: ---------------------------------- [~vkadlcik] Currently the RPM only installs two features: * com.jboss.devstudio.core.rpm.feature * com.jboss.devstudio.core.capabilities.feature But these drag in all the dependencies they need to complete the installation, including com.google.guava. I tried to remove/blacklist that plugin, but seemed that org.eclipse.m2e needed it (JBDS-4131); however, now that we depend on the org.eclipse.m2e RPM instead of the stuff in the devstudio update site, perhaps we can remove this too. https://github.com/jbdevstudio/jbdevstudio-product/pull/443 How can I easily determine which requirements for devstudio have already been met by installed rpms? Or migrate p2 dependencies to rpm dependencies? > rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46 > ------------------------------------------------------------------------------ > > Key: JBDS-4257 > URL: https://issues.jboss.org/browse/JBDS-4257 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.3.0.AM2 > Environment: RHEL7 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Minor > Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png > > > I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46. > !yum_install_rh-eclipse46.png|thumbnail! > [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library. > He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages. > [^rh-eclipse46_provides.txt] > [^rh-eclipse46-devstudio_provides.txt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2017