February 2017 - jbosstools-issues

[JBoss JIRA] (JBTIS-1041) Incorrect MD5 for devstudio-integration-stack-10.1.0.CR2-fuse-tooling-installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1041?page=com.atlassian.jira.plugin... ] Paul Leacu reassigned JBTIS-1041: --------------------------------- Assignee: Paul Leacu > Incorrect MD5 for devstudio-integration-stack-10.1.0.CR2-fuse-tooling-installer > ------------------------------------------------------------------------------- > > Key: JBTIS-1041 > URL: https://issues.jboss.org/browse/JBTIS-1041 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.1.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > > https://devstudio.redhat.com/10.0/staging/updates/integration-stack/10.1.... > contains > {code} > a2157f40c1acce24c76f0b8de64b5dfb > {code} > but the correct MD5 is > {code} > 12c5a0acc988d2fc88cc57f8cb5a5eb3 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1040) Update the logic for checking all available quickstarts in RH Central

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1040?page=com.atlassian.jira.plugin... ] Paul Leacu reassigned JBTIS-1040: --------------------------------- Assignee: Paul Leacu > Update the logic for checking all available quickstarts in RH Central > --------------------------------------------------------------------- > > Key: JBTIS-1040 > URL: https://issues.jboss.org/browse/JBTIS-1040 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.1.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > There is again a problem with the Fuse quickstart. Currently, the quickstart is available only if we enable Early Access in RH Central. At the first sight it looks like the behavior is hard coded. > Please update the logic for checking all available quickstarts so that it will detect Fuse quickstart without just checking if the Early Access is enabled or not. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4273) Problem installing Teiid from IS discovery site - possible use constraint violation from slf4j / slf4j-api

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-4273?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-4273: ----------------------------------------- Hi [~lvalach] please wait till tomorrow. There will be new build of Integration Stack which should contain the new Teiid Designer. > Problem installing Teiid from IS discovery site - possible use constraint violation from slf4j / slf4j-api > ---------------------------------------------------------------------------------------------------------- > > Key: JBDS-4273 > URL: https://issues.jboss.org/browse/JBDS-4273 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, rpm > Affects Versions: 10.3.0.GA > Environment: RHEL7, RHSCL 2.4 Alpha 1.1, rh-eclipse46-devstudio.x86_64 10.3-0.20170206.0203.el7 > Integration Stack Discovery site: http://download.jboss.org/jbosstools/neon/integration/updates/integration... > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 10.3.0.GA > > Attachments: home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt > > > [~lvalach] said: {quote} > Hi Nick, > I tested installation of stuff from central as you described. I am not finished yet, but here is what I found. > -install latest integration stack bits from IS > -JBoss Fule Development - OK > -JBoss Business P. and Rules D. - OK > -JBoss Integration and SOA D. - OK > -JBoss Data Virtualization D. (IS early acess) > -there is problem with slf4j > -IS contains Teiid 11.0.1.CR1-v20170117-222 which should be fixed > -there are error like this: > {code} > !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences". > !STACK 0 > java.lang.LinkageError: loader constraint violation: when resolving method > "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader > (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, > org/slf4j/LoggerFactory, and the class loader > (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, > org/slf4j/impl/StaticLoggerBinder, have different > Class objects for the type org/slf4j/ILoggerFactory > used in the signature{code} > -install everything from Central (including PMD and Findbugs, and early access stuff. NOTE: newer versions of the Integration Stack connectors should already be installed from the step above) > -I installed everything using Central-Software/update, *no remediation action* was needed. > -Eclipse started but with many errors. So I have to find out which feature causes the problem.{quote} > [~nickboldt] said: > {quote} > loader constraint violation == two different versions of slf4j in the installed plugins > check in :~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 vs. in /opt/rh/ > Problem appears to be in *org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory*. {quote} > [~lvalach] said: > {quote} > {code} > cd ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 > find . -iname *slf4j* > ./configuration/org.eclipse.osgi/1293/0/.cp/lib/slf4j-api-1.6.1.jar > {code} > The output for /opt/rh/ is quite long but I can say that it contains slf4j.api_1.7.4.jar > {quote} > [~nickboldt] said: > {quote} > So, we may have a conflict between slf4j and slf4j-api, which both use the same bundle names, but expose packages differently. > Unclear which IS project is causing this problem as I thought we'd fixed both SY and TD already. > * https://issues.jboss.org/browse/SWITCHYARD-2976 > * https://issues.jboss.org/browse/TEIIDDES-2999 > {quote} > [~lvalach] said: > {quote} > I tried to install Jboss Data Virtualization Developement from [IS discovery site|http://download.jboss.org/jbosstools/neon/integration/updates/integr...] again. > Whole log: > [^rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt] > Slf4j files in ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/ > [^home_eclipse.txt] > Slf4j files in /opt/rh/ > [^opt_rh.txt] > The problem is caused by Teiid Designer and Teiid Designer Runtime. > Teiid DataTools Connectivity and Teiid Runtime Clients don't cause problem. > IS repository contains SwitchYard 2.3.0.CR1-v20170120-1347-B20 which works properly. > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23886) Delete Resource: when deleting a resource we should say what resource type is deleted

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23886?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23886: ------------------------------------------ merged into master > Delete Resource: when deleting a resource we should say what resource type is deleted > ------------------------------------------------------------------------------------- > > Key: JBIDE-23886 > URL: https://issues.jboss.org/browse/JBIDE-23886 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.Final > > > When deleting a single resource, we're telling the user that we're deleting a resource. It would be valuable information to tell the user what kind of resource this actually is. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22140) jboss-web.xml validate problem in JBDS 8.0.0.GA.

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22140?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22140: --------------------------------------- ok, great, so yes, it's still reproducible. > jboss-web.xml validate problem in JBDS 8.0.0.GA. > ------------------------------------------------ > > Key: JBIDE-22140 > URL: https://issues.jboss.org/browse/JBIDE-22140 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final > Reporter: xu zhang > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > Create "jboss-web.xml" from article "https://access.redhat.com/solutions/159753" in JBDS 8.0.0, error shows: > ~~~ > No grammar constraints (DTD or XML Schema) referenced in the document. > ~~~ > Customer wants JBDS to validate "jboss-web.xml" correctly. > Please let us know if it will be resolved in the next release/patch. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1008. ------------------------------------ Verified with JBTIS TP 4.4.1.Final > Provide OpenShift 3 support feature in Integration Stack Target Platform > ------------------------------------------------------------------------ > > Key: JBTIS-1008 > URL: https://issues.jboss.org/browse/JBTIS-1008 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.1.Final-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Fix For: 4.4.1.Final-TP > > Attachments: IncludeWhateverPluginFromRemoteRepoFixjavax.cryptoIssue.png, screenshot-1.png > > > My goal is to be able to leverage OpenShift 3 and CDK integration. > I think that the required feature is org.jboss.tools.openshift.feature > [~adietish]Can you confirm that it is the right feature? > *Reason:* Leverage OpenShift 3 and CDK integration. > *Project page/sources:* > *Version:* 3.3.1 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .devstudiois > *Include in JBDS:* Yes (DevtsudioIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22140) jboss-web.xml validate problem in JBDS 8.0.0.GA.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22140?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22140: ------------------------------------ [~mmalina] no we just wanted to know if it's still valid as it has been reported for JBDS 8.0 > jboss-web.xml validate problem in JBDS 8.0.0.GA. > ------------------------------------------------ > > Key: JBIDE-22140 > URL: https://issues.jboss.org/browse/JBIDE-22140 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final > Reporter: xu zhang > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > Create "jboss-web.xml" from article "https://access.redhat.com/solutions/159753" in JBDS 8.0.0, error shows: > ~~~ > No grammar constraints (DTD or XML Schema) referenced in the document. > ~~~ > Customer wants JBDS to validate "jboss-web.xml" correctly. > Please let us know if it will be resolved in the next release/patch. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-991) Correct build timestamp as part of the generated discovery plugins.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-991?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-991. ----------------------------------- Verified with Devstudio IS 10.1.0.CR2 with the following discovery plugin {code} com.jboss.jbds.central.discovery.integration-stack_10.1.0.CR2-v20170207-0337-B275.jar {code} > Correct build timestamp as part of the generated discovery plugins. > ------------------------------------------------------------------- > > Key: JBTIS-991 > URL: https://issues.jboss.org/browse/JBTIS-991 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.1.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 10.1.0.GA > > > This: > com.jboss.jbds.central.discovery.integration-stack_10.0.0.GA-v20130101-0001-B246.jar > Should have a correct build timnestamp embedded within it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4274) Fix marketplace categories for devstudio and jbosstools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4274?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4274: ---------------------------------- So, to confirm you want: {code} Application Server Database Development Web, XML, Java EE and OSGi Enterprise Development Mobile and Device Development J2EE Development Platform{code} and no mention of *Linux Tools* (I had TWO proposals). Correct, [~jeffmaury]? > Fix marketplace categories for devstudio and jbosstools > ------------------------------------------------------- > > Key: JBDS-4274 > URL: https://issues.jboss.org/browse/JBDS-4274 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: marketplace > Affects Versions: 10.3.0.GA > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 10.3.0.GA > > > After a recent change to the Eclipse Marketplace, we can only select up to 5 categories. This affects how we're discovered when someone searches for Marketplace listings. > Here's what we currently use for JBoss Tools: > {code}Application Server > Database Development > General Purpose Tools > IDE > J2EE Development Platform{code} > And here's what we have for Devstudio - the same 5 categories: > {code}Application Server > Database Development > General Purpose Tools > IDE > J2EE Development Platform{code} > And for Devstudio IS: > {code} > Database Development > IDE > SOA Development > Tools{code} > Maybe we want to remove > {code}General Purpose Tools, and > IDE{code} > and use instead: > {code}Web, XML, Java EE and OSGi Enterprise Development, and > Mobile and Device Development{code} > Or should we include {code}Linux Tools{code} since we have > Docker/Vagrant stuff now too? > For Integration Stack, we could drop "IDE" and "Tools" and use instead: > {code} > Business Intelligence, Reporting and Charting > Database Development > Database Persistence > SOA Development > Web Services{code} > What do you think? > Here's the current full list of categories from which to choose: > {code}Application Development Frameworks > Application Management > Application Server > BIRT > Build and Deploy > Business Intelligence, Reporting and Charting > Code Management > Collaboration > Database > Database Development > Database Persistence > Documentation > Eclipse Kura > Eclipse SmartHome > EclipseRT Target Platform Components > Editor > Entertainment > General Purpose Tools > Graphics > IDE > Internet of Things (IoT) > J2EE Development Platform > J2ME > Languages > Linux Tools > Logging > Mobile and Device Development > Modeling > Modeling Tools > Mylyn Connectors > Network > Other > Process > Profiling > Programming Languages > Reporting > Rich Client Applications > SCM > Search > SOA Development > Source Code Analyzer > Systems Development > Team Development > Testing > Tools > UI > UML > Web > Web Services > Web, XML, Java EE and OSGi Enterprise Development > XML{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1041) Incorrect MD5 for devstudio-integration-stack-10.1.0.CR2-fuse-tooling-installer

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1041: ---------------------------------------- Summary: Incorrect MD5 for devstudio-integration-stack-10.1.0.CR2-fuse-tooling-installer Key: JBTIS-1041 URL: https://issues.jboss.org/browse/JBTIS-1041 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 10.1.0.CR1 Reporter: Andrej Podhradsky Priority: Critical https://devstudio.redhat.com/10.0/staging/updates/integration-stack/10.1.... contains {code} a2157f40c1acce24c76f0b8de64b5dfb {code} but the correct MD5 is {code} 12c5a0acc988d2fc88cc57f8cb5a5eb3 {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017