February 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3044) Align installation default path with installer filename

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3044 at 5/28/14 10:36 AM: ------------------------------------------------------------ Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2: {quote} {code} find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+" {code} shows 251 as the longest path on Mac so not really safe longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor but that is spring and it's data {quote} So we're already pushing the limit here for long paths on Windows / NTFS... Related (with some LOLs): http://blog.codinghorror.com/filesystem-paths-how-long-is-too-long/ There are ways to achieve more-than-260-char paths, but do we want to? was (Author: nickboldt): Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2: {quote} {code} find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+" {code} shows 251 as the longest path on Mac so not really safe longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor but that is spring and it's data {quote} So we're already pushing the limit here for long paths on Windows / NTFS... > Align installation default path with installer filename > ------------------------------------------------------- > > Key: JBDS-3044 > URL: https://issues.jboss.org/browse/JBDS-3044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Martin Malina > Assignee: Denis Golovin > Priority: Blocker > Labels: discuss > Fix For: 8.0.0.Beta3 > > > Now that Nick changed the installer filenames to jboss-devstudio in JBIDE-16871 (was jbdevstudio), shouldn't the default install path be changed similarly? Because it just went out of sync. > This question is open for discussion. Nick pointed out some reasons against this suggestion: > {quote} > Martin Malina Re: changing the installation folder, I'll hold off on that change for the moment for a few reasons: > a) Max is AFK, and will want to vet/veto this idea > b) long paths for Windows users (80% of our user base) = bad news, especially considering how long some file paths can get already within Eclipse workspaces > c) short paths for Windows (c:\jbdevstudio) & long paths for everyone else ~/jboss-devstudio) would be ill-advised from a documentation and cross-platform user experience > So, either we stick w/ jbdevstudio, or we shorten to devstudio (losing the "jb" branding fragment). If we move to "jboss-devstudio" we increase the path by only 4 characters. > Max Rydahl Andersen WDYT? > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

1 week, 5 days

2
2
0 / 0

[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-2719: ------------------------------------- [~nickboldt] I will need to test several different configurations to confirm my earlier guess. This is what I know so far. First I would ask that you test with the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts] as I am working to keep them up to date and error free as much as possible. This specific error can be seen in the [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] quickstart. The Travel and PetClinic will be kept as close to the original as possible (and I haven't had a chance to update them yet). With that in mind if I Build (with Eclipse/JBDS) [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] in JBDS 7.0.1 with Spring IDE 3.3 installed from JBoss Central, I get the aspectj error. However if I Build while in a standard Eclipse JEE install with JBDS and the stock Spring IDE/STS 3.4 installed, I do NOT get the aspectj error. In order to truly confirm that adding both "AspectJ Compiler" and "AspectJ Development Tools" will fix the error, I would need to test that on my JBDS 7.0.1/SpringIDE 3.3 set up. > Multiple Spring AOP problems when travel example is imported > ------------------------------------------------------------ > > Key: JBDS-2719 > URL: https://issues.jboss.org/browse/JBDS-2719 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, upstream > Affects Versions: 7.0.0.GA > Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > > There are Multiple Spring AOP Errors after travel example is imported: > {code} > Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5287) Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file.

by Svetlana Yasenovich (JIRA)

Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file. ------------------------------------------------------------------------- Key: JBIDE-5287 URL: https://jira.jboss.org/jira/browse/JBIDE-5287 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Environment: JBoss Developer Studio Version: 3.0.0.M4 Build id: v200911180352M Reporter: Svetlana Yasenovich Priority: Minor 1. Open .xhtml file. 2. click 'Ctrl+A' -> all code selected 3. click 'Ctrl+Shift+/' (Source->Add Block Comment) ->all code commented 4. click 'Ctrl+A' 5. click 'Ctrl+Shift+\' (Source->Remove Block Comment) -> nothing happened Expected Result : Remove Block Comment for all code -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

5 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-21797) Fails to start the CDK server when it's was already started from CLI

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21797?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21797: ------------------------------------- I initially had the wrong cdk vagrantfile selected in the server settings vs the one started in CLI. But Even after fixing that and making sure the cdk is the proper one, it still fails > Fails to start the CDK server when it's was already started from CLI > -------------------------------------------------------------------- > > Key: JBIDE-21797 > URL: https://issues.jboss.org/browse/JBIDE-21797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI > - once it's started, start the same CDK from the CDK server adapter > => the server should detect the CDK already started and should simply be put in started mode, instead it fails to start with > !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21793) Zero-click import of CDK

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21793?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21793: ------------------------------------- [~maxandersen] Um... care to comment on this? It seems this would require that we disable the runtime detection dialog on startup? That'd be a material change to the feature, and I'd like your +1 before pursuing. > Zero-click import of CDK > ------------------------ > > Key: JBIDE-21793 > URL: https://issues.jboss.org/browse/JBIDE-21793 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.3.1.Beta2 > Reporter: Pete Muir > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > When the installer with the CDK completes and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server. > We should try to import the CDK with no-clicks, and hide the detection dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21782) Adding EAP 7. ER6 server rises a warning on New runtime page

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21782?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21782: -------------------------------- Fix Version/s: 4.3.1.CR1 > Adding EAP 7. ER6 server rises a warning on New runtime page > ------------------------------------------------------------ > > Key: JBIDE-21782 > URL: https://issues.jboss.org/browse/JBIDE-21782 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > Screenshot: http://i.imgur.com/ObzrfQs.png > The warning is: > {noformat} > This server type expects a version of 6.1 but the server directory is of version 7.0.0.GA. This combination may cause critical errors. {noformat} > I guess it's because ER6 reports version "7.0.0.GA". > For example ER2 doesn't raise the warning (because it still reports as 7.0.0.Beta1). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21797) Fails to start the CDK server when it's was already started from CLI

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21797?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21797: ----------------------------------- Assignee: Rob Stryker > Fails to start the CDK server when it's was already started from CLI > -------------------------------------------------------------------- > > Key: JBIDE-21797 > URL: https://issues.jboss.org/browse/JBIDE-21797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI > - once it's started, start the same CDK from the CDK server adapter > => the server should detect the CDK already started, and should simply be put in started mode, instead it fails to start with > !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21797) Fails to start the CDK server when it's was already started from CLI

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21797?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21797: -------------------------------- Fix Version/s: 4.3.1.CR1 > Fails to start the CDK server when it's was already started from CLI > -------------------------------------------------------------------- > > Key: JBIDE-21797 > URL: https://issues.jboss.org/browse/JBIDE-21797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI > - once it's started, start the same CDK from the CDK server adapter > => the server should detect the CDK already started, and should simply be put in started mode, instead it fails to start with > !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21797) Fails to start the CDK server when it's was already started from CLI

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21797?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21797: -------------------------------- Description: - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI - once it's started, start the same CDK from the CDK server adapter => the server should detect the CDK already started and should simply be put in started mode, instead it fails to start with !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! was: - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI - once it's started, start the same CDK from the CDK server adapter => the server should detect the CDK already started, and should simply be put in started mode, instead it fails to start with !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! > Fails to start the CDK server when it's was already started from CLI > -------------------------------------------------------------------- > > Key: JBIDE-21797 > URL: https://issues.jboss.org/browse/JBIDE-21797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI > - once it's started, start the same CDK from the CDK server adapter > => the server should detect the CDK already started and should simply be put in started mode, instead it fails to start with > !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21797) Fails to start the CDK server when it's was already started from CLI

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21797: ----------------------------------- Summary: Fails to start the CDK server when it's was already started from CLI Key: JBIDE-21797 URL: https://issues.jboss.org/browse/JBIDE-21797 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Affects Versions: 4.3.1.CR1 Reporter: Fred Bricon - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI - once it's started, start the same CDK from the CDK server adapter => the server should detect the CDK already started, and should simply be put in started mode, instead it fails to start with !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 February 2016