January 2017 - jbosstools-issues - Jboss List Archives

[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] (ERT-196) Opening a volume in Docker explorer silently fails [EBZ#493863]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-196?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-196. ------------------------------- Fix Version/s: Neon.3 (4.6) Resolution: Done > Opening a volume in Docker explorer silently fails [EBZ#493863] > --------------------------------------------------------------- > > Key: ERT-196 > URL: https://issues.jboss.org/browse/ERT-196 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > Fix For: Neon (4.6) M5, Neon.3 (4.6) > > > When displaying containers, Docker explorer allows Show in explorer on volumes but the folder/file may not be a local one. Command should enabled on the existence of the local resource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4259) Could not resolve module: org.eclipse.recommenders

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4259?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-4259. ------------------------------ Resolution: Done > Could not resolve module: org.eclipse.recommenders > -------------------------------------------------- > > Key: JBDS-4259 > URL: https://issues.jboss.org/browse/JBDS-4259 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.3.0.GA > Environment: RHEL7, RHSCL 2.4 alpha 1.0 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.3.0.GA > > Attachments: rh-eclipse46-devstudio10.3.log.20170131-1103.txt > > > I got errors during start of Devstudio 10.3-0.20170131.0115.el7. There are errors like this: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.recommenders.apidocs.rcp [1085] > Unresolved requirement: Import-Package: com.google.common.annotations; version="[15.0.0,16.0.0)" > {code} > Log: [^rh-eclipse46-devstudio10.3.log.20170131-1103.txt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-196) Opening a volume in Docker explorer silently fails [EBZ#493863]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-196?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-196: --------------------------------- Assignee: Jeff Johnston > Opening a volume in Docker explorer silently fails [EBZ#493863] > --------------------------------------------------------------- > > Key: ERT-196 > URL: https://issues.jboss.org/browse/ERT-196 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > Fix For: Neon (4.6) M5 > > > When displaying containers, Docker explorer allows Show in explorer on volumes but the folder/file may not be a local one. Command should enabled on the existence of the local resource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-196) Opening a volume in Docker explorer silently fails [EBZ#493863]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-196?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-196: ------------------------------ Sprint: devex #126 January 2017 > Opening a volume in Docker explorer silently fails [EBZ#493863] > --------------------------------------------------------------- > > Key: ERT-196 > URL: https://issues.jboss.org/browse/ERT-196 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > Fix For: Neon (4.6) M5 > > > When displaying containers, Docker explorer allows Show in explorer on volumes but the folder/file may not be a local one. Command should enabled on the existence of the local resource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23677) write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23677?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23677: ------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version) > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23677 > URL: https://issues.jboss.org/browse/JBIDE-23677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, foundation > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.3.Final > > > Wrong version of foundation.core detected. Should be 4.4.3, not 4.4.2. > https://github.com/jbosstools/jbosstools-base/blob/master/foundation/plug... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23677) write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23677?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23677: ------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version) > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23677 > URL: https://issues.jboss.org/browse/JBIDE-23677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, foundation > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.3.Final > > > Wrong version of foundation.core detected. Should be 4.4.3, not 4.4.2. > https://github.com/jbosstools/jbosstools-base/blob/master/foundation/plug... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23677) write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23677?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23677: ------------------------------------ Assign to Fred for review and merge of PR. If you change the value of the default.value in the src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties, you can see what errors are reported to break the build. Only values that will be accepted for parent pom 4.4.3.AM2 are 4.4.3.AM2 or 4.4.3.AM2.Final. You can verify this by setting those values or can break the build by setting 4.4.4.foo or 4.4.2.bar, etc. > write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version) > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23677 > URL: https://issues.jboss.org/browse/JBIDE-23677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, foundation > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.3.AM2 > > > Wrong version of foundation.core detected. Should be 4.4.3, not 4.4.2. > https://github.com/jbosstools/jbosstools-base/blob/master/foundation/plug... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 January 2017