July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3479) create just one marketplace entry for developer studio

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3479?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3479: -------------------------------------- It's axtually the Luna one that was meant to be changed, after some earlier issues, it's actually the Luna one that got renamed and hosts all versions. > create just one marketplace entry for developer studio > ------------------------------------------------------ > > Key: JBDS-3479 > URL: https://issues.jboss.org/browse/JBDS-3479 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 9.0.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 9.0.0.Beta2 > > > As discussed on JBIDE-20024 it now makes sense to have just one developer studio entry on markteplace. > To avoid full states rename Red Hat JBoss Developer Studio (Kepler): http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kep... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3479) create just one marketplace entry for developer studio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3479?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3479: ----------------------------- Description: As discussed on JBIDE-20024 it now makes sense to have just one developer studio entry on markteplace. To avoid full states rename Red Hat JBoss Developer Studio (Luna): http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-lun... was: As discussed on JBIDE-20024 it now makes sense to have just one developer studio entry on markteplace. To avoid full states rename Red Hat JBoss Developer Studio (Kepler): http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kep... > create just one marketplace entry for developer studio > ------------------------------------------------------ > > Key: JBDS-3479 > URL: https://issues.jboss.org/browse/JBDS-3479 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 9.0.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 9.0.0.Beta2 > > > As discussed on JBIDE-20024 it now makes sense to have just one developer studio entry on markteplace. > To avoid full states rename Red Hat JBoss Developer Studio (Luna): http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-lun... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3479) create just one marketplace entry for developer studio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3479?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3479: ----------------------------- Comment: was deleted (was: [~maxandersen] [~mickael_istria] JBIDE-20185 says to rename the JBT Luna entry, but this one requests the JBDS Kepler entry be renamed. Intentional or typo? Should the JBDS Luna one be renamed? Please clarify.) > create just one marketplace entry for developer studio > ------------------------------------------------------ > > Key: JBDS-3479 > URL: https://issues.jboss.org/browse/JBDS-3479 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 9.0.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 9.0.0.Beta2 > > > As discussed on JBIDE-20024 it now makes sense to have just one developer studio entry on markteplace. > To avoid full states rename Red Hat JBoss Developer Studio (Luna): http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-lun... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20185) create just one marketplace entry for jboss tools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20185?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20185: ------------------------------------ On https://marketplace.eclipse.org/content/jboss-tools/edit I see descriptions for only JBT 4.3 and 4.2. Should we add descriptions for the older versions too? > create just one marketplace entry for jboss tools > ------------------------------------------------- > > Key: JBIDE-20185 > URL: https://issues.jboss.org/browse/JBIDE-20185 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Beta2 > > > As discussed on JBIDE-20024 it now makes sense to have just one jboss tools entry on markteplace. > To avoid full loss of stats the entry to rename is JBoss Tools (Luna): http://marketplace.eclipse.org/content/jboss-tools-luna/metrics since it has the highest count by far currently. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3479) create just one marketplace entry for developer studio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3479?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3479: ---------------------------------- [~maxandersen] [~mickael_istria] JBIDE-20185 says to rename the JBT Luna entry, but this one requests the JBDS Kepler entry be renamed. Intentional or typo? Should the JBDS Luna one be renamed? Please clarify. > create just one marketplace entry for developer studio > ------------------------------------------------------ > > Key: JBDS-3479 > URL: https://issues.jboss.org/browse/JBDS-3479 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 9.0.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 9.0.0.Beta2 > > > As discussed on JBIDE-20024 it now makes sense to have just one developer studio entry on markteplace. > To avoid full states rename Red Hat JBoss Developer Studio (Kepler): http://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-kep... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19826) Red Hat moved - affects license notices

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19826?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19826: ------------------------------------ PR is merged. Here's how to use the new license feature: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > Red Hat moved - affects license notices > --------------------------------------- > > Key: JBIDE-19826 > URL: https://issues.jboss.org/browse/JBIDE-19826 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Beta2 > > > [~fontana] pointed out in a mail thread that Red Hat address moved thus our current feature license text/snippet should be updated: > "Red Hat, Inc. licenses these features and plugins to you under certain > open source licenses (or aggregations of such licenses), which in a > particular case may include the Eclipse Public License, the GNU Lesser > General Public License, and/or certain other open source licenses. For > precise licensing details, consult the corresponding source code, or > contact Red Hat, Attn: General Counsel, 100 East Davie St., Raleigh NC 27601 USA. > " -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11436) Migrate to use of o.j.t.foundation.license feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11436?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-11436 at 7/6/15 10:47 AM: ------------------------------------------------------------- These PRs are merged: * Base: https://github.com/jbosstools/jbosstools-base/pull/420 * devdoc: https://github.com/jbosstools/jbosstools-devdoc/pull/52 So, now we can move forward migrating all the projects to use the new license feature. Instructions for migrating to use the new license feature: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... was (Author: nickboldt): These PRs are merged: * Base: https://github.com/jbosstools/jbosstools-base/pull/420 * devdoc: https://github.com/jbosstools/jbosstools-devdoc/pull/52 So, now we can move forward migrating all the projects to use the new license feature. > Migrate to use of o.j.t.foundation.license feature > -------------------------------------------------- > > Key: JBIDE-11436 > URL: https://issues.jboss.org/browse/JBIDE-11436 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: wrong-feature-name-shown-in-p2-install-UI-when-using-license-features.png, wrong-feature-name-shown-when-using-license-features.png > > > See http://relengofthenerds.blogspot.fr/2011/01/implementing-shared-licenses-... for explanation -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11436) Migrate to use of o.j.t.foundation.license feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11436?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11436: ------------------------------------ These PRs are merged: * Base: https://github.com/jbosstools/jbosstools-base/pull/420 * devdoc: https://github.com/jbosstools/jbosstools-devdoc/pull/52 So, now we can move forward migrating all the projects to use the new license feature. > Migrate to use of o.j.t.foundation.license feature > -------------------------------------------------- > > Key: JBIDE-11436 > URL: https://issues.jboss.org/browse/JBIDE-11436 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: wrong-feature-name-shown-in-p2-install-UI-when-using-license-features.png, wrong-feature-name-shown-when-using-license-features.png > > > See http://relengofthenerds.blogspot.fr/2011/01/implementing-shared-licenses-... for explanation -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20171: ------------------------------------ Who is "they" ? Who is "we"? All this started with your need to turn buildinfo.json into a tagging script. The mojo could *ignore* the situation where no SHA is found in the MANIFEST.MF (but a SHA is found in buildinfo.json), if you feel that's safe enough. Today, it compares them, and since they don't match, the build *intentionally* fails. You asked for this feature in JBIDE-19467 & I implemented it here: https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6... Today, the buildinfo.json for JBT builds contains all the SHAs for all the projects EXCEPT Xulrunner, which hasn't been built in >2 yrs, and therefore shouldn't need to be tagged. If you agree that a non-moving project like Xulrunner doesn't need jbosstools-4.3.0.* tags cluttering it up, then we're done here. Or, if you disagree, then we have two options: a) rebuild Xulrunner to shove Eclipse-SourceReferences into its MANIFEST.MF files b) update the mojo to ignore the case where there's a SHA in buildinfo.json but no SHA in Eclipse-SourceReferences in MANIFEST.MF, rather than failing the build for this case. Since you said above {quote} im fine our tools catches issues and we fix them based on that. {quote} Therefore I assume you DO NOT want the mojo changed, but would rather rebuild Xulrunner. Or we just don't worry about tagging Xulrunner and the problem goes away. :D > buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA > ------------------------------------------------------------------- > > Key: JBIDE-20171 > URL: https://issues.jboss.org/browse/JBIDE-20171 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta2 > > > Since the addition of a check that verifies exactly this condition: > https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6... > I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json. > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console} > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files! > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json > [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences > [ERROR] commitId . > [ERROR] If you have locally built projects which are aggregated here, > [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch. > [ERROR] Or, use -DskipCheckSHAs=true to bypass this check. > [ERROR] -> [Help 1]{code} > This happened after I put a buildinfo.json file here: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > I've since moved the file here to temporarily work around the build failure: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20185) create just one marketplace entry for jboss tools

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20185?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20185: ---------------------------------------- It's mostly done. https://marketplace.eclipse.org/content/jboss-tools exists and references all active versions. I'm adding a note on other entries to mark them deprecated. In the meantime, feel free to review the entry description. > create just one marketplace entry for jboss tools > ------------------------------------------------- > > Key: JBIDE-20185 > URL: https://issues.jboss.org/browse/JBIDE-20185 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Beta2 > > > As discussed on JBIDE-20024 it now makes sense to have just one jboss tools entry on markteplace. > To avoid full loss of stats the entry to rename is JBoss Tools (Luna): http://marketplace.eclipse.org/content/jboss-tools-luna/metrics since it has the highest count by far currently. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 2015