November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21120) Why do we deploy TP zips to Nexus snapshots repo?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21120?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21120: ------------------------------- Description: Currently, we deploy our TP update sites to the JBoss Nexus snapshots repo. {code} Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... ... {code} But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: * eat disk space in Nexus * consume time/resources in Jenkins Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the jbosstools-targetplatform & jbosstools-discovery root pom to prevent this waste of time/space? was: Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: * eat disk space in Nexus * consume time/resources in Jenkins Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? > Why do we deploy TP zips to Nexus snapshots repo? > ------------------------------------------------- > > Key: JBIDE-21120 > URL: https://issues.jboss.org/browse/JBIDE-21120 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our TP update sites to the JBoss Nexus snapshots repo. > {code} > Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > ... > {code} > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the jbosstools-targetplatform & jbosstools-discovery root pom to prevent this waste of time/space? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21120) Why do we deploy TP zips to Nexus snapshots repo?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21120: ---------------------------------- Summary: Why do we deploy TP zips to Nexus snapshots repo? Key: JBIDE-21120 URL: https://issues.jboss.org/browse/JBIDE-21120 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, updatesite Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: * eat disk space in Nexus * consume time/resources in Jenkins Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21105) Remove BIRT?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21105: ------------------------------------ Patience. It's still building. :D > Remove BIRT? > ------------ > > Key: JBIDE-21105 > URL: https://issues.jboss.org/browse/JBIDE-21105 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, birt-wizard-new-library.png, birt-wizard-new-library__NEON.png, birt-wizards.png, birt-wizards__NEON.png, eclipse-after-birt.png, install-jboss-birt-sites.png, install-jboss-birt-sites__NEON.png, install-jboss-birt.png, install-jboss-birt__NEON.png > > > {quote} > (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there > (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site > (2015-11-17 11:43:21) nickboldt: because Birt needs it > (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars > (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ? > (2015-11-17 11:43:44) maxandersen: afaik birt is dead. > (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik. > (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4? > (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy. > (2015-11-17 11:44:38) akazakov: +1 > (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in. > (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/ > (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/ > {quote} > So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here: > http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201... > But we could also just use the old one from Mars.0: > http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201... > Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL. > *DISCUSS*. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21119) Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21119?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21119: ------------------------------- Description: Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 {quote} So, we need a new version of m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.50.x and 4.51.x TPs (for JBDS 9.1, not 9.0.1). was: Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 {quote} So, we need a new version of m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.60.x TPs. > Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21119 > URL: https://issues.jboss.org/browse/JBIDE-21119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > > Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 > {quote} > So, we need a new version of m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.50.x and 4.51.x TPs (for JBDS 9.1, not 9.0.1). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21119) Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21119?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21119: ------------------------------- Fix Version/s: 4.3.1.Beta1 (was: 4.4.0.Alpha1) > Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21119 > URL: https://issues.jboss.org/browse/JBIDE-21119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > > Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 > {quote} > So, we need a new version of m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.50.x and 4.51.x TPs (for JBDS 9.1, not 9.0.1). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21119) Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21119?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21119: ------------------------------- Affects Version/s: 4.3.0.Final > Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21119 > URL: https://issues.jboss.org/browse/JBIDE-21119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > > Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 > {quote} > So, we need a new version of m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.50.x and 4.51.x TPs (for JBDS 9.1, not 9.0.1). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21118) Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21118?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21118: ------------------------------- Affects Version/s: 4.4.0.Alpha1 > Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21118 > URL: https://issues.jboss.org/browse/JBIDE-21118 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 > {quote} > So, we need a new version of m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.60.x TPs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21119) Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21119: ---------------------------------- Summary: Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) Key: JBIDE-21119 URL: https://issues.jboss.org/browse/JBIDE-21119 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, target-platform, upstream Reporter: Nick Boldt Assignee: Fred Bricon Fix For: 4.4.0.Alpha1 Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 {quote} So, we need a new version of m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.60.x TPs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21118) Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21118: ---------------------------------- Summary: Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) Key: JBIDE-21118 URL: https://issues.jboss.org/browse/JBIDE-21118 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, target-platform, upstream Reporter: Nick Boldt Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 {quote} So, we need a new version of m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.60.x TPs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21118) Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21118?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21118: ---------------------------------- Assignee: Fred Bricon > Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21118 > URL: https://issues.jboss.org/browse/JBIDE-21118 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform, upstream > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 > {quote} > So, we need a new version of m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.60.x TPs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 November 2015