July 2015 - jbosstools-issues - Jboss List Archives

[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: ---------------------------------------- Yeah, I'm on it, but the Marketplace UI isn't very efficient... > 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 > 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] (JBIDE-20185) create just one marketplace entry for jboss tools

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20185?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20185: --------------------------------------------- [~mickael_istria] can we get it to use the Luna so we at least don't loose the install and star stats gathered for luna ? > 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 > 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] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20171: --------------------------------------------- what is your suggestion for the next build - how will they get this info ? how did we do it in the past ? can't the mojo have a fallback to get the minimal info needed ? > 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-20170) WebTools server adapter installer installs only a subset of what should be installed

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20170?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20170: --------------------------------------------- this issue is for QE to close by testing and verifying and have test in place for this for each release. > WebTools server adapter installer installs only a subset of what should be installed > ------------------------------------------------------------------------------------ > > Key: JBIDE-20170 > URL: https://issues.jboss.org/browse/JBIDE-20170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, server, updatesite, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.0.Beta2 > > > Steps to repro: > {code}1. open clean Eclipse JEE > 2. open Servers view > 3. click 'No servers are avail... click to create new server..." > 4. click "Download additional server adapters" > (Site used to resolve IUs is http://download.jboss.org/jbosstools/updates/webtools/mars/ which symlinks to http://download.jboss.org/jbosstools/mars/development/updates/core/ ) > 5. wait while the stuff loads. select "JBoss AS Server Adapter" or whatever it was called > 6. wait as metadata loads again > 7. click Next, accept license, etc. restart when prompted > {code} > Feature that should have been installed: > {code:title=https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/category.xml#L99-L103} > <feature id="org.jboss.ide.eclipse.as.feature"> > <category name="org.eclipse.wst.server.core.serverAdapter"/> > </feature> > {code} > Feature that instead gets installed: > {code}org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_3.1.0.Beta1-v20150612-2158-B25{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20024) Problems with new Eclipse Marketplace

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20024?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen edited comment on JBIDE-20024 at 7/6/15 5:34 AM: --------------------------------------------------------------------- Yes, only talked about merging jboss tools entries into one and developer studio (core) into one. Combining them would be completely unheard of and not work. But thanks for asking to verify. I've created JBDS-3479 and JBIDE-20185 for these, leaving the still existing issues on this issue. [edited: had bad link to JBDS issue before] was (Author: maxandersen): Yes, only talked about merging jboss tools entries into one and developer studio (core) into one. Combining them would be completely unheard of and not work. But thanks for asking to verify. I've created JBDS-3470 and JBIDE-20185 for these, leaving the still existing issues on this issue. > Problems with new Eclipse Marketplace > ------------------------------------- > > Key: JBIDE-20024 > URL: https://issues.jboss.org/browse/JBIDE-20024 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > Attachments: spring-marketplace-different-updates.png > > > New Eclipse Marketplace problems: > * all features can't be optional - must have at least one required one - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469864 > * default config shows all versions of Eclipse, not latest (have to update Luna entries to show ONLY Luna compatibility) - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469869 > * "Add new solution version" doesn't work - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469865 > * Need an api to load IUs / copy from one solution to another - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469867 > * 'Edit Solution' shows the same grey footnote text dozens of times - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469862 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20187) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20187?page=com.atlassian.jira.plugi... ] Misha Ali commented on JBIDE-20187: ----------------------------------- Fixed, sorry about that, and thanks, Max. > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20187 > URL: https://issues.jboss.org/browse/JBIDE-20187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Misha Ali > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > << internal link removed >> Error is available here: http://pastebin.com/3XKt9x5i > Please let me know if any further information is required for this bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20187) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20187?page=com.atlassian.jira.plugi... ] Misha Ali updated JBIDE-20187: ------------------------------ Description: I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. Steps to reproduce: 1. Follow the steps here: https://access.redhat.com/articles/1367643 Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux The step where a groovy script is run results in the following output, which ends with an error: << internal link removed >> Error is available here: Please let me know if any further information is required for this bug. was: I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. Steps to reproduce: 1. Follow the steps here: https://access.redhat.com/articles/1367643 Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux The step where a groovy script is run results in the following output, which ends with an error: http://pastebin.test.redhat.com/294840 Please let me know if any further information is required for this bug. > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20187 > URL: https://issues.jboss.org/browse/JBIDE-20187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Misha Ali > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > << internal link removed >> Error is available here: > Please let me know if any further information is required for this bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20187) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20187?page=com.atlassian.jira.plugi... ] Misha Ali updated JBIDE-20187: ------------------------------ Description: I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. Steps to reproduce: 1. Follow the steps here: https://access.redhat.com/articles/1367643 Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux The step where a groovy script is run results in the following output, which ends with an error: << internal link removed >> Error is available here: http://pastebin.com/3XKt9x5i Please let me know if any further information is required for this bug. was: I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. Steps to reproduce: 1. Follow the steps here: https://access.redhat.com/articles/1367643 Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux The step where a groovy script is run results in the following output, which ends with an error: << internal link removed >> Error is available here: Please let me know if any further information is required for this bug. > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20187 > URL: https://issues.jboss.org/browse/JBIDE-20187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Misha Ali > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > << internal link removed >> Error is available here: http://pastebin.com/3XKt9x5i > Please let me know if any further information is required for this bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20187) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20187?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-20187: ---------------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-20187 (was: JBDS-3480) Issue Type: Bug (was: Feature Request) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Affects Version/s: (was: 9.0.0.Beta1) Docs QE Status: (was: NEW) > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20187 > URL: https://issues.jboss.org/browse/JBIDE-20187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Misha Ali > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > http://pastebin.test.redhat.com/294840 > Please let me know if any further information is required for this bug. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20187) "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20187?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-20187: ---------------------------------------- Component/s: central > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"" error appears when trying to run script to work offline > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20187 > URL: https://issues.jboss.org/browse/JBIDE-20187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Misha Ali > > I'm trying to test the Working Offline instructions for JBDS 9.0 Beta1 and coming across an odd error. I've checked with Len and Martin and they are also encountering this error and have recommended filing a bug. > Steps to reproduce: > 1. Follow the steps here: https://access.redhat.com/articles/1367643 > Details: JBDS Beta1, Groovy version 2.4.3 JVM: 1.7.0_79 Vendor: Oracle Corporation OS: Linux > The step where a groovy script is run results in the following output, which ends with an error: > http://pastebin.test.redhat.com/294840 > Please let me know if any further information is required for this bug. -- 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