October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25118) improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6

by Mat Booth (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25118?page=com.atlassian.jira.plugi... ] Mat Booth commented on JBIDE-25118: ----------------------------------- * Desktop file sanity: Always waive * Elflint/Binary stripping: Usually it's because there is some unstripped or oddly built native binary in a test suite that's used to test IDE debugging functions, but seeing this error in any other case indicates a packaging error that should be fixed. I would probably leave these for manual inspection. * RPM requires/provides: Maybe leave these for manual inspection -- they usually happen due to changes in a package in response to a bug, I'm not sure how you'd programmatically give a sensible reason for the waiver. * Shell syntax: This specific case is always a false positive that could always be waived -- IMO it's probably a bug in rpmdiff mistaking tcl scripts for shell scripts. * Execshield: This may only be waived by the security response team, so may as well ignore it An extra one: * RPM changelog: https://errata.devel.redhat.com/rpmdiff/show/182461?result_id=5039897 -- Alway waive with the reason I gave there "This change is ok because package was resynchronised with the Fedora upstream" -- it turned out to be a non-trivial exercise to merge upstream and downstream changelogs without violating some arbitrary constraint that RPM imposes about changelog entry ordering, so when importing from Fedora, the changelog is simply overwritten. I don't think anyone cares because all history is still in git anyway. > improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6 > ---------------------------------------------------------------------------------------- > > Key: JBIDE-25118 > URL: https://issues.jboss.org/browse/JBIDE-25118 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, rpm > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: release > Fix For: 4.5.1.Final > > > {quote} > It sounds like we could add these check types to my script: > > * desktop-file-sanity (always waive?) > * IP v6 (always waive using existing waiver details, eg., https://errata.devel.redhat.com/rpmdiff/show/182126?result_id=5028358 > Yep, yep. > > * patches (waive if %autopatch) > And if the only other complaints are "patch not applied" (I'm not sure if this check may throw different kinds of error){quote} > So, the next time we have an errata with the above types of issues, I can update this script [1] to add those use cases. > [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/errata... > cc: [~mat.booth] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25147) Fix missing shell text in ws.reddeer DynamicWebProjectWizard constructor

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-25147: ---------------------------------- Summary: Fix missing shell text in ws.reddeer DynamicWebProjectWizard constructor Key: JBIDE-25147 URL: https://issues.jboss.org/browse/JBIDE-25147 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-tests, webservices Affects Versions: 4.5.1.AM2 Reporter: Pavol Srna Assignee: Pavol Srna Fix For: 4.5.1.AM3 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16161) Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16161: ---------------------------------------- Since https://bugs.eclipse.org/bugs/show_bug.cgi?id=424104 is now fixed; ehen https://bugs.eclipse.org/bugs/show_bug.cgi?id=313553 is fixed and Tycho uses it, then dependency resolution from p2 (hence Tycho) should include dependencies also according to Provide/Require-Capability. > Tycho tests against Luna have extra dependency on org.eclipse.e4.rcp (need to be cleaned) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-16161 > URL: https://issues.jboss.org/browse/JBIDE-16161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 4.2.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin. > The easiest way is to add the org.eclipse.e4.rcp feature to the main build. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25118) improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25118?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25118: ------------------------------- Fix Version/s: 4.5.1.Final (was: 4.5.x) > improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6 > ---------------------------------------------------------------------------------------- > > Key: JBIDE-25118 > URL: https://issues.jboss.org/browse/JBIDE-25118 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, rpm > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: release > Fix For: 4.5.1.Final > > > {quote} > It sounds like we could add these check types to my script: > > * desktop-file-sanity (always waive?) > * IP v6 (always waive using existing waiver details, eg., https://errata.devel.redhat.com/rpmdiff/show/182126?result_id=5028358 > Yep, yep. > > * patches (waive if %autopatch) > And if the only other complaints are "patch not applied" (I'm not sure if this check may throw different kinds of error){quote} > So, the next time we have an errata with the above types of issues, I can update this script [1] to add those use cases. > [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/errata... > cc: [~mat.booth] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25118) improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25118?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25118: ------------------------------------ Working on a fix now. What about these types of NEEDS INSPECTION items? False positive? Install some rpms and check something on disk locally? Other processing needed to verify? * Desktop file sanity: https://errata.devel.redhat.com/rpmdiff/show/182459?result_id=5040039 * Elflint: https://errata.devel.redhat.com/rpmdiff/show/182459?result_id=5040040 * Binary stripping: https://errata.devel.redhat.com/rpmdiff/show/182459?result_id=5040060 * RPM requires/provides: https://errata.devel.redhat.com/rpmdiff/show/182407?result_id=5038024 * Shell Syntax: https://errata.devel.redhat.com/rpmdiff/show/182112?result_id=5027919 * Execshield: https://errata.devel.redhat.com/rpmdiff/show/182196?result_id=5030668 > improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6 > ---------------------------------------------------------------------------------------- > > Key: JBIDE-25118 > URL: https://issues.jboss.org/browse/JBIDE-25118 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, rpm > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: release > Fix For: 4.5.1.Final > > > {quote} > It sounds like we could add these check types to my script: > > * desktop-file-sanity (always waive?) > * IP v6 (always waive using existing waiver details, eg., https://errata.devel.redhat.com/rpmdiff/show/182126?result_id=5028358 > Yep, yep. > > * patches (waive if %autopatch) > And if the only other complaints are "patch not applied" (I'm not sure if this check may throw different kinds of error){quote} > So, the next time we have an errata with the above types of issues, I can update this script [1] to add those use cases. > [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/errata... > cc: [~mat.booth] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25146) Eclipse annotation processing not enabled by default can result in errors

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25146?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-25146: --------------------------------------- [~jeffmaury], can you take a look? See the discussion in JBEAP-7667. According to the EAP team this is a bug in our tooling (or in Eclipse itself). > Eclipse annotation processing not enabled by default can result in errors > ------------------------------------------------------------------------- > > Key: JBIDE-25146 > URL: https://issues.jboss.org/browse/JBIDE-25146 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.5.0.Final > Reporter: Sande Gilda > Assignee: Jeff MAURY > > Some of the quickstarts fail with "java.lang.IllegalArgumentException" and "implementation not found" errors. The workaround was to add this property to the project POM file: > {code} > <properties> >  > <m2e.apt.activation>jdt_apt</m2e.apt.activation> > </properties> > {code} > These quickstarts needed this workaround: > * ejb-security-context-propagation/pom.xml > * ejb-security-interceptors/pom.xml > * kitchensink-ml/pom.xml > * kitchensink-ml-ear/pom.xml > * logging-tools/pom.xml > Since most of the quickstarts use annotations, it's not clear to me what is different about these other than some use bundles. > See these bugs for more information about the issue: > * https://bugzilla.redhat.com/show_bug.cgi?id=1182606#c2 > * https://bugzilla.redhat.com/show_bug.cgi?id=1183013 > * https://bugzilla.redhat.com/show_bug.cgi?id=1191984 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25146) Eclipse annotation processing not enabled by default can result in errors

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25146?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-25146: ---------------------------------- Affects Version/s: 4.5.0.Final > Eclipse annotation processing not enabled by default can result in errors > ------------------------------------------------------------------------- > > Key: JBIDE-25146 > URL: https://issues.jboss.org/browse/JBIDE-25146 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.5.0.Final > Reporter: Sande Gilda > Assignee: Martin Malina > > Some of the quickstarts fail with "java.lang.IllegalArgumentException" and "implementation not found" errors. The workaround was to add this property to the project POM file: > {code} > <properties> >  > <m2e.apt.activation>jdt_apt</m2e.apt.activation> > </properties> > {code} > These quickstarts needed this workaround: > * ejb-security-context-propagation/pom.xml > * ejb-security-interceptors/pom.xml > * kitchensink-ml/pom.xml > * kitchensink-ml-ear/pom.xml > * logging-tools/pom.xml > Since most of the quickstarts use annotations, it's not clear to me what is different about these other than some use bundles. > See these bugs for more information about the issue: > * https://bugzilla.redhat.com/show_bug.cgi?id=1182606#c2 > * https://bugzilla.redhat.com/show_bug.cgi?id=1183013 > * https://bugzilla.redhat.com/show_bug.cgi?id=1191984 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25146) Eclipse annotation processing not enabled by default can result in errors

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25146?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-25146: ------------------------------------- Assignee: Jeff MAURY (was: Martin Malina) > Eclipse annotation processing not enabled by default can result in errors > ------------------------------------------------------------------------- > > Key: JBIDE-25146 > URL: https://issues.jboss.org/browse/JBIDE-25146 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.5.0.Final > Reporter: Sande Gilda > Assignee: Jeff MAURY > > Some of the quickstarts fail with "java.lang.IllegalArgumentException" and "implementation not found" errors. The workaround was to add this property to the project POM file: > {code} > <properties> >  > <m2e.apt.activation>jdt_apt</m2e.apt.activation> > </properties> > {code} > These quickstarts needed this workaround: > * ejb-security-context-propagation/pom.xml > * ejb-security-interceptors/pom.xml > * kitchensink-ml/pom.xml > * kitchensink-ml-ear/pom.xml > * logging-tools/pom.xml > Since most of the quickstarts use annotations, it's not clear to me what is different about these other than some use bundles. > See these bugs for more information about the issue: > * https://bugzilla.redhat.com/show_bug.cgi?id=1182606#c2 > * https://bugzilla.redhat.com/show_bug.cgi?id=1183013 > * https://bugzilla.redhat.com/show_bug.cgi?id=1191984 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25146) Eclipse annotation processing not enabled by default can result in errors

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25146?page=com.atlassian.jira.plugi... ] Sande Gilda updated JBIDE-25146: -------------------------------- Project: Tools (JBoss Tools) (was: JBoss Developer Studio Integration Stack Planning) Key: JBIDE-25146 (was: JBDSISP-5) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) > Eclipse annotation processing not enabled by default can result in errors > ------------------------------------------------------------------------- > > Key: JBIDE-25146 > URL: https://issues.jboss.org/browse/JBIDE-25146 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Sande Gilda > Assignee: Martin Malina > > Some of the quickstarts fail with "java.lang.IllegalArgumentException" and "implementation not found" errors. The workaround was to add this property to the project POM file: > {code} > <properties> >  > <m2e.apt.activation>jdt_apt</m2e.apt.activation> > </properties> > {code} > These quickstarts needed this workaround: > * ejb-security-context-propagation/pom.xml > * ejb-security-interceptors/pom.xml > * kitchensink-ml/pom.xml > * kitchensink-ml-ear/pom.xml > * logging-tools/pom.xml > Since most of the quickstarts use annotations, it's not clear to me what is different about these other than some use bundles. > See these bugs for more information about the issue: > * https://bugzilla.redhat.com/show_bug.cgi?id=1182606#c2 > * https://bugzilla.redhat.com/show_bug.cgi?id=1183013 > * https://bugzilla.redhat.com/show_bug.cgi?id=1191984 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24951) Bootstrap OSIO login in JBossTools

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24951?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-24951. ------------------------------------ Resolution: Done done, nothing for QE to verify in this jira > Bootstrap OSIO login in JBossTools > ---------------------------------- > > Key: JBIDE-24951 > URL: https://issues.jboss.org/browse/JBIDE-24951 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: OSIO > Fix For: 4.5.1.AM3 > > > Bootstrap the OSIO login from JBossTools > * design document > * provide extension point for external (analytics) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 October 2017