November 2015 - jbosstools-issues

[JBoss JIRA] (JBTIS-531) Bouncy Castle causes full source TP build failure.

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-531: -------------------------------- Summary: Bouncy Castle causes full source TP build failure. Key: JBTIS-531 URL: https://issues.jboss.org/browse/JBTIS-531 Project: JBoss Tools Integration Stack Issue Type: Bug Components: target-platform Affects Versions: 9.0.0.Alpha2, 8.0.4.CR2 Reporter: Paul Leacu Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle. Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build: {code} mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install ... [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618 [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found {code} you may also see this error: {code} [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618 [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found {code} Both of these plugins can be found (in stub form) here: http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP. WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21049) Add "wildfly-messaging-activemq-deployment_1_0.xsd" to xml catalog

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21049?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21049: ----------------------------------- Component/s: server > Add "wildfly-messaging-activemq-deployment_1_0.xsd" to xml catalog > ------------------------------------------------------------------ > > Key: JBIDE-21049 > URL: https://issues.jboss.org/browse/JBIDE-21049 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.3.0.Final > Reporter: Wolfgang Knauf > Priority: Minor > > WildFly 10 introduced a new schema "wildfly-messaging-activemq-deployment_1_0.xsd" for configuration of e.g. an ActiveMQ queue as part of a deployable archive, e.g. an EAR file (a file with the extension "...-jms.xml"). > This schema file is missing in the XSD catalog. > Here is a sample xml instance: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <messaging-deployment xmlns="urn:jboss:messaging-activemq-deployment:1.0"> > <server> > <jms-destinations> > <jms-queue name="MessageBeanQueue"> > <entry name="jms/queue/MessageBeanQueue"/> > </jms-queue> > </jms-destinations> > </server> > </messaging-deployment> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21049) Add "wildfly-messaging-activemq-deployment_1_0.xsd" to xml catalog

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21049?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21049: -------------------------------------- Assignee: Rob Stryker > Add "wildfly-messaging-activemq-deployment_1_0.xsd" to xml catalog > ------------------------------------------------------------------ > > Key: JBIDE-21049 > URL: https://issues.jboss.org/browse/JBIDE-21049 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.3.0.Final > Reporter: Wolfgang Knauf > Assignee: Rob Stryker > Priority: Minor > > WildFly 10 introduced a new schema "wildfly-messaging-activemq-deployment_1_0.xsd" for configuration of e.g. an ActiveMQ queue as part of a deployable archive, e.g. an EAR file (a file with the extension "...-jms.xml"). > This schema file is missing in the XSD catalog. > Here is a sample xml instance: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <messaging-deployment xmlns="urn:jboss:messaging-activemq-deployment:1.0"> > <server> > <jms-destinations> > <jms-queue name="MessageBeanQueue"> > <entry name="jms/queue/MessageBeanQueue"/> > </jms-queue> > </jms-destinations> > </server> > </messaging-deployment> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21035) Build with Tycho 0.24.0

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21035?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21035: ---------------------------------------- +1 > Build with Tycho 0.24.0 > ----------------------- > > Key: JBIDE-21035 > URL: https://issues.jboss.org/browse/JBIDE-21035 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > {quote} > Tycho milestone 0.24.0 has been released and is available from maven central. > See the release notes [1] for details of enhancements and bug fixes in this release. > Thanks to: > Alexander Kurtakov > Lars Vogel > Mickael Istria > Mikolaj Izdebski > who contributed patches for this release. > And thanks and to everyone who helped us with testing the staged version. > Regards, > Tycho team > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21035) Build with Tycho 0.24.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21035?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21035: ------------------------------------ Should we also do that for 4.3.x branch as replacement for PR #208? > Build with Tycho 0.24.0 > ----------------------- > > Key: JBIDE-21035 > URL: https://issues.jboss.org/browse/JBIDE-21035 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > {quote} > Tycho milestone 0.24.0 has been released and is available from maven central. > See the release notes [1] for details of enhancements and bug fixes in this release. > Thanks to: > Alexander Kurtakov > Lars Vogel > Mickael Istria > Mikolaj Izdebski > who contributed patches for this release. > And thanks and to everyone who helped us with testing the staged version. > Regards, > Tycho team > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21035) Build with Tycho 0.24.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21035?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21035: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/208, https://github.com/jbosstools/jbosstools-build/pull/209 (was: https://github.com/jbosstools/jbosstools-build/pull/207, https://github.com/jbosstools/jbosstools-build/pull/208, https://github.com/jbosstools/jbosstools-build/pull/209) > Build with Tycho 0.24.0 > ----------------------- > > Key: JBIDE-21035 > URL: https://issues.jboss.org/browse/JBIDE-21035 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > {quote} > Tycho milestone 0.24.0 has been released and is available from maven central. > See the release notes [1] for details of enhancements and bug fixes in this release. > Thanks to: > Alexander Kurtakov > Lars Vogel > Mickael Istria > Mikolaj Izdebski > who contributed patches for this release. > And thanks and to everyone who helped us with testing the staged version. > Regards, > Tycho team > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 (Beta)

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-21038: --------------------------------------- The issue is always reproducible in a distribution with GTK3 3.18. It can cause Eclipse to freeze in some cases (starting the Git Commit Dialog wizard, for instance). > Software/Update page is not working on Fedora 23 (Beta) > ------------------------------------------------------- > > Key: JBIDE-21038 > URL: https://issues.jboss.org/browse/JBIDE-21038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0.GA > Reporter: Radim Hopp > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%. > java version "1.8.0_65" > gtk3 version 3.18.2 > jstack: http://pastebin.com/a7U02yjt > Everything is fine with GTK2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21049) Add "wildfly-messaging-activemq-deployment_1_0.xsd" to xml catalog

by Wolfgang Knauf (JIRA)

Wolfgang Knauf created JBIDE-21049: -------------------------------------- Summary: Add "wildfly-messaging-activemq-deployment_1_0.xsd" to xml catalog Key: JBIDE-21049 URL: https://issues.jboss.org/browse/JBIDE-21049 Project: Tools (JBoss Tools) Issue Type: Enhancement Affects Versions: 4.3.0.Final Reporter: Wolfgang Knauf Priority: Minor WildFly 10 introduced a new schema "wildfly-messaging-activemq-deployment_1_0.xsd" for configuration of e.g. an ActiveMQ queue as part of a deployable archive, e.g. an EAR file (a file with the extension "...-jms.xml"). This schema file is missing in the XSD catalog. Here is a sample xml instance: {code:xml} <?xml version="1.0" encoding="UTF-8"?> <messaging-deployment xmlns="urn:jboss:messaging-activemq-deployment:1.0"> <server> <jms-destinations> <jms-queue name="MessageBeanQueue"> <entry name="jms/queue/MessageBeanQueue"/> </jms-queue> </jms-destinations> </server> </messaging-deployment> {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-498) improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-498?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-498. ---------------------------- Fix Version/s: 9.0.0.Beta1 Resolution: Done I think we've squeezed all we can out of this Jira. Please file new ones as needed. Updated rsync.sh /updates invocations to add --del > improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning > ----------------------------------------------------------------------------------------- > > Key: JBTIS-498 > URL: https://issues.jboss.org/browse/JBTIS-498 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 9.0.0.Beta1 > > Attachments: IS-updated-composite-sites-development.png, IS-updated-composite-sites-staging.png, JBDSIS-sites-contain-Alpha2-TP-and-Beta1-TP.png > > > Would it be possible to change your publishing process so that you're not dumping dozens of old jars into the same folder? Surely you aren't staging ALL these? (We only stage to QE once or twice per milestone... CR1, CR1a.) > Have a look here: > http://download.jboss.org/jbosstools/mars/staging/updates/integration-sta... > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discov... > And contrast that with the way the JBT & JBDS discovery jars are done: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... > https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce... > (using rsync.sh, you get automated build folder cleanup every time you publish a new build, or you can force cleanup it with this job [1]). > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-cleanup/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21048) Download Runtimes should not require constantly typing credentials for each download

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-21048: ----------------------------------- Summary: Download Runtimes should not require constantly typing credentials for each download Key: JBIDE-21048 URL: https://issues.jboss.org/browse/JBIDE-21048 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime-detection, server Affects Versions: 4.3.0.Final Reporter: Rob Stryker Download runtimes, when used for downloading EAP / JPP / Fuse runtimes, requires typing in credentials and verifying them. This can be made simpler for the user, either by persisting the credentials directly or by referencing the (possible) credentialing framework (JBIDE-21043) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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