May 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17167) rse.ui source bundle not available in locally-built TP

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17167?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-17167: --------------------------------------- Mickael, multiple is not working in eclipse it complains some artifacts are not resolved. It is most likely eclipse issue, but I haven't reported it. I use local build of TP with sources. > rse.ui source bundle not available in locally-built TP > ------------------------------------------------------ > > Key: JBIDE-17167 > URL: https://issues.jboss.org/browse/JBIDE-17167 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Fix For: 4.2.0.Beta2 > > > Cannot find a source bundle for rse.ui using locally-built TP and the flags for include source. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17167) rse.ui source bundle not available in locally-built TP

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17167?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-17167: --------------------------------------- Rob, I was using .target file in eclipse. > rse.ui source bundle not available in locally-built TP > ------------------------------------------------------ > > Key: JBIDE-17167 > URL: https://issues.jboss.org/browse/JBIDE-17167 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Fix For: 4.2.0.Beta2 > > > Cannot find a source bundle for rse.ui using locally-built TP and the flags for include source. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17209) only product for mylyn integration is JBossAS Server

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17209?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17209: ----------------------------------- Fix Version/s: 4.2.0.Beta2 > only product for mylyn integration is JBossAS Server > ---------------------------------------------------- > > Key: JBIDE-17209 > URL: https://issues.jboss.org/browse/JBIDE-17209 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, common/jst/core, server > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 4.2.0.Beta2 > > > Using "report bug or enhancement" JBoss Tools shows up but then after that a list of "products" is shown and it just list JBossAS Server. > I would have expected Developer Studio too at least, and a few more key components. > Note: this might not be something base should add, but put it into central or jbds product makes sense I think. > -- Configuration Details -- > Product: Eclipse 4.4.0.20140301-1817 (org.eclipse.epp.package.jee.product) > Installed Features: > org.jboss.ide.eclipse.as.feature 3.0.0.Beta2-v20140421-1626-B483 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10116) Issues that affect AS7/EAP integration to tools

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10116?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-10116: ------------------------------------- This is for the most part an open-ended tracking issue. Any critical issues that affect a project/product application server will receive an additional jira in tools to keep track of it's schedule, so it is not correct for this issue to have a 'fix version' continuously punted. The issue will remain open for tracking purposes only. > Issues that affect AS7/EAP integration to tools > ----------------------------------------------- > > Key: JBIDE-10116 > URL: https://issues.jboss.org/browse/JBIDE-10116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Labels: f2f2012 > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10116) Issues that affect AS7/EAP integration to tools

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10116?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-10116: -------------------------------- Fix Version/s: (was: 4.2.0.Beta2) > Issues that affect AS7/EAP integration to tools > ----------------------------------------------- > > Key: JBIDE-10116 > URL: https://issues.jboss.org/browse/JBIDE-10116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Labels: f2f2012 > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17167) rse.ui source bundle not available in locally-built TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17167?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17167: ---------------------------------------- [~dgolovin] See https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... , the target-platform to use in IDE is *multiple*. [~rawb] When building locally, the target-to-repo mojo should show warnings for missing sources (cf https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... ). Can you try to build with the -X flag to enable log and check whether you have some more info about rse.ui. Note that as a workaround, you can still tweak the target platform from the preferences to add just this bundle from another source. > rse.ui source bundle not available in locally-built TP > ------------------------------------------------------ > > Key: JBIDE-17167 > URL: https://issues.jboss.org/browse/JBIDE-17167 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Fix For: 4.2.0.Beta2 > > > Cannot find a source bundle for rse.ui using locally-built TP and the flags for include source. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16764) Remote EAP 6.3 does not accept password

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16764?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-16764. --------------------------------- Resolution: Cannot Reproduce Bug Closing as fixed in ER2. No changes to JBT required. > Remote EAP 6.3 does not accept password > --------------------------------------- > > Key: JBIDE-16764 > URL: https://issues.jboss.org/browse/JBIDE-16764 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Beta2 > > > This will have to be a known issue for JBDS 7.1.1, investigate for next 7.1 update. > Something must have changed in EAP 6.3 and now the remote server does not accept the password and fails to connect to the server. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16764) Remote EAP 6.3 does not accept password

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16764?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16764: ------------------------------------- The core of the issue was this: 15:28:50,012 TRACE [org.jboss.remoting.remote.server] (Remoting "localhost:MANAGEMENT" task-2) Server sending authentication rejected (javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched URI: remoting/localhost; expecting: remote/localhost) The internal bugzilla marks this as fixed in EAP 6.3.0.ER2. > Remote EAP 6.3 does not accept password > --------------------------------------- > > Key: JBIDE-16764 > URL: https://issues.jboss.org/browse/JBIDE-16764 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Beta2 > > > This will have to be a known issue for JBDS 7.1.1, investigate for next 7.1 update. > Something must have changed in EAP 6.3 and now the remote server does not accept the password and fails to connect to the server. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17211) Inform users which deployment scanner's interval they're setting

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17211?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17211. --------------------------------- Fix Version/s: 4.2.0.Beta2 (was: 4.2.0.CR1) Resolution: Done I've made a commit which changes a few subtle things: 1) The scanner interval and scanner timeout now live UNDER "Add missing scanners" and above "Remove added scanners". 2) The two labels for scanner interval and timeout are now indented, to make clear these are settings only on the added scanners 3) The two labels now say "Added scanner timeout" and "Added scanenr interval" 4) I noticed that if you unchecked "Add missing blahblah" and then did a ctrl+z, the checkbox was not re-checked. This is because the wrong default value was assumed. This has been fixed. > Inform users which deployment scanner's interval they're setting > ---------------------------------------------------------------- > > Key: JBIDE-17211 > URL: https://issues.jboss.org/browse/JBIDE-17211 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.Beta2 > > > You asked for a new JIRA in JBIDE-15287 so here you go :) > It is possible to change the interval for the custom deployment scanners that the tools add. > But the UI doesn't state this, so it seems that in fact we alter the interval even for the default deployment scanner which we don't. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17072) Users should be warned when opening Launch config from unsaved server editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17072?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17072. --------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta2) Resolution: Done The patch has been accepted upstream and I believe will be available for beta3 or cr1, depending on when we upgrade our tp. > Users should be warned when opening Launch config from unsaved server editor > ---------------------------------------------------------------------------- > > Key: JBIDE-17072 > URL: https://issues.jboss.org/browse/JBIDE-17072 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > Could we ask the users to save their Server Editor when they click "Open launch configuration"? In some cases the functionality of the launch config dialog is affected by changes in Server Editor. > For example take Deploy only server. > With JBIDE-7515, it is now possible to set up a launch/shutdown script. > But for that you first need to uncheck the checkbox "Server is externally managed". Once you do that, you have to save the editor and only then click on the launch config. If you don't realize you need to save, you could be surprised that you still can't edit the startup/shutdown fields. > (I will open another JIRA to change that particular workflow, but this JIRA will be still relevant for other cases.) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 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 May 2014