March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19038) Arquillian should not be in JBT EA catalog

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19038?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19038: --------------------------------- Attachment: JBDS_810_GA.png And - the icon is also missing in JBDS 8.1.0.GA > Arquillian should not be in JBT EA catalog > ------------------------------------------ > > Key: JBIDE-19038 > URL: https://issues.jboss.org/browse/JBIDE-19038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.2.Final > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.2.3.Final > > Attachments: JBDS_810_GA.png > > > In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-420) Enable support for a remote SAP tooling update site URL

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-420: -------------------------------- Summary: Enable support for a remote SAP tooling update site URL Key: JBTIS-420 URL: https://issues.jboss.org/browse/JBTIS-420 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: distribution Affects Versions: 8.0.1.GA Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 8.0.2.GA Update the ide-config properties to establish the following: jboss.site.integration-stack-extras.url|jbosstools|4.2=http://download.jb... jboss.site.integration-stack-extras.url|devstudio|8=https://devstudio.red... Also update the SAP POM accordingly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18966) Attempting to install components through Central only includes Android and JRebel

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18966?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-18966. -------------------------------- Fixed a long time ago - closing now. > Attempting to install components through Central only includes Android and JRebel > --------------------------------------------------------------------------------- > > Key: JBIDE-18966 > URL: https://issues.jboss.org/browse/JBIDE-18966 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.2.1.Final > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 4.2.1.Final > > Attachments: Central.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18833) luna nightly are not being updated preventing QE to do easy testing of committed code

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18833?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-18833. -------------------------------- > luna nightly are not being updated preventing QE to do easy testing of committed code > ------------------------------------------------------------------------------------- > > Key: JBIDE-18833 > URL: https://issues.jboss.org/browse/JBIDE-18833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.2.1.Final > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ composite*.xml was updated 26-nov but latest build there is from 28-oct-2014 (29 days ago) > I could not spot updates in https://github.com/jbdevstudio/jbdevstudio-ci related to this. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18833) luna nightly are not being updated preventing QE to do easy testing of committed code

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18833?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-18833: -------------------------------------- Clsoing this as the nightly builds have been OK for a long time. Max - re-open if you want to. > luna nightly are not being updated preventing QE to do easy testing of committed code > ------------------------------------------------------------------------------------- > > Key: JBIDE-18833 > URL: https://issues.jboss.org/browse/JBIDE-18833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.2.1.Final > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ composite*.xml was updated 26-nov but latest build there is from 28-oct-2014 (29 days ago) > I could not spot updates in https://github.com/jbdevstudio/jbdevstudio-ci related to this. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12352) Remote management connection to servers cannot be established with IPv6

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12352?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-12352: ---------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) (was: 4.2.3.Beta1) > Remote management connection to servers cannot be established with IPv6 > ----------------------------------------------------------------------- > > Key: JBIDE-12352 > URL: https://issues.jboss.org/browse/JBIDE-12352 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.1.Final > Environment: JBDS 5.0.1 > Fedora 17 32bit > OpenJDK 1.6 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > After creating JBIDE-12351 for JMX connection, I found out that the connection cannot be established at all - even when you don't try to connect via JMX. > When you set up a remote as7/eap6 server accessible over IPv6 and start the server, the remote connection will fail with this error: > {code} > Jul 20, 2012 3:14:57 PM org.xnio.Xnio <clinit> > INFO: XNIO Version 3.0.3.GA > Jul 20, 2012 3:14:57 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.0.3.GA > Jul 20, 2012 3:14:57 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 3.2.7.GA > Jul 20, 2012 3:15:46 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > Jul 20, 2012 3:15:46 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > Jul 20, 2012 3:15:51 PM org.xnio.Xnio <clinit> > INFO: XNIO Version 3.0.4.GA-redhat-1 > Jul 20, 2012 3:15:51 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1 > Jul 20, 2012 3:15:51 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 3.2.8.GA-redhat-1 > Jul 20, 2012 3:15:52 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-416) Need to doc split of SOA Development between release and early access

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-416?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-416: -------------------------------- Assignee: Misha Ali (was: Paul Leacu) > Need to doc split of SOA Development between release and early access > --------------------------------------------------------------------- > > Key: JBTIS-416 > URL: https://issues.jboss.org/browse/JBTIS-416 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.1.GA, 4.2.1.Final > Reporter: Paul Leacu > Assignee: Misha Ali > Attachments: ss0.png, ss1.png > > > Component categorization for the SOA Development tooling falls in both the released and Early Access update sites. B*MS tooling is now being productized and Fuse Tooling/ SwitchYard are in 'Early Access'. This situation is temporary (until Fuse Tooling/SwitchYard are GA). > To address this issue I've done the following: > JBDSIS 8.0.1.GA: > site-ga: (released) > JBoss Business Process and Rules Development > *All features available > JBoss Data Virtualization Development > *All features available > JBoss Integration and SOA Development > *All features except Fuse Tooling and SwitchYard > JBoss SOA 5.x Development > *All features available > > site-ea: (early access) > JBoss Fuse Development > *All features available > JBoss Integration and SOA Development > *Fuse Tooling and SwitchYard only available > To simplify the user experience, Early Access will contain only features which are early access. Released (production) features will appear in the primary update window. > The community JBTIS install will do something similar. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-416) Need to doc split of SOA Development between release and early access

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-416?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-416: ---------------------------------- I think the doc should say something like: The SOA development tooling is comprised of both released and early access components. Consequently, "JBoss Integration and SOA Development" will appear - as designed - in both the standard released update selection window and in the early access window of the JBoss Central and p2 installers. Note that if you enable early access then that SOA Development component collection will override the released component set in Central. ref ss0.png SImply de-select the "Enable Early Access" checkbox to reveal the released SOA development tooling selection. ss1.png > Need to doc split of SOA Development between release and early access > --------------------------------------------------------------------- > > Key: JBTIS-416 > URL: https://issues.jboss.org/browse/JBTIS-416 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.1.GA, 4.2.1.Final > Reporter: Paul Leacu > Assignee: Misha Ali > Attachments: ss0.png, ss1.png > > > Component categorization for the SOA Development tooling falls in both the released and Early Access update sites. B*MS tooling is now being productized and Fuse Tooling/ SwitchYard are in 'Early Access'. This situation is temporary (until Fuse Tooling/SwitchYard are GA). > To address this issue I've done the following: > JBDSIS 8.0.1.GA: > site-ga: (released) > JBoss Business Process and Rules Development > *All features available > JBoss Data Virtualization Development > *All features available > JBoss Integration and SOA Development > *All features except Fuse Tooling and SwitchYard > JBoss SOA 5.x Development > *All features available > > site-ea: (early access) > JBoss Fuse Development > *All features available > JBoss Integration and SOA Development > *Fuse Tooling and SwitchYard only available > To simplify the user experience, Early Access will contain only features which are early access. Released (production) features will appear in the primary update window. > The community JBTIS install will do something similar. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-416) Need to doc split of SOA Development between release and early access

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-416?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-416: ----------------------------- Attachment: ss0.png > Need to doc split of SOA Development between release and early access > --------------------------------------------------------------------- > > Key: JBTIS-416 > URL: https://issues.jboss.org/browse/JBTIS-416 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.1.GA, 4.2.1.Final > Reporter: Paul Leacu > Assignee: Paul Leacu > Attachments: ss0.png, ss1.png > > > Component categorization for the SOA Development tooling falls in both the released and Early Access update sites. B*MS tooling is now being productized and Fuse Tooling/ SwitchYard are in 'Early Access'. This situation is temporary (until Fuse Tooling/SwitchYard are GA). > To address this issue I've done the following: > JBDSIS 8.0.1.GA: > site-ga: (released) > JBoss Business Process and Rules Development > *All features available > JBoss Data Virtualization Development > *All features available > JBoss Integration and SOA Development > *All features except Fuse Tooling and SwitchYard > JBoss SOA 5.x Development > *All features available > > site-ea: (early access) > JBoss Fuse Development > *All features available > JBoss Integration and SOA Development > *Fuse Tooling and SwitchYard only available > To simplify the user experience, Early Access will contain only features which are early access. Released (production) features will appear in the primary update window. > The community JBTIS install will do something similar. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18128) JBoss Tools 4.2 (for Luna) doesn't deploy all .class

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-18128. ------------------------------------ > JBoss Tools 4.2 (for Luna) doesn't deploy all .class > ---------------------------------------------------- > > Key: JBIDE-18128 > URL: https://issues.jboss.org/browse/JBIDE-18128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server > Affects Versions: 4.2.0.Beta3 > Reporter: fede pia > Assignee: Fred Bricon > Fix For: 4.2.2.Final > > Attachments: 2014-09-04 error.png, 2014-09-04 output.txt, integration-wildfly-branch.zip, jboss-test.zip, TestJboss-2014-09-03.zip > > > The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException. > I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random. > For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean > As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1. > I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2015