September 2018 - 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)

3 weeks, 6 days

3
3
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

4 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

6 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-26389) NPE while "Searching Runtimes"

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-26389: ------------------------------------- Summary: NPE while "Searching Runtimes" Key: JBIDE-26389 URL: https://issues.jboss.org/browse/JBIDE-26389 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk, runtime-detection Affects Versions: 4.9.0.Final Reporter: Ondrej Dockal Assignee: Rob Stryker {code} eclipse.buildId=12.9.0.GA-v20180928-1629-B3448 java.version=1.8.0_181 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product com.jboss.devstudio.core.product Command-line arguments: -data file:/home/odockal/workspace1290GA/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product org.eclipse.core.jobs Error Sun Sep 30 20:56:59 CEST 2018 An internal error occurred during: "Searching runtimes...". java.lang.NullPointerException at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.folderWhiteListBin(UnifiedMinishiftRuntimeDetector.java:150) at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.getMinishiftBinary(UnifiedMinishiftRuntimeDetector.java:139) at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.folderContainsMinishiftBinary(UnifiedMinishiftRuntimeDetector.java:144) at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.minishiftHomeMatches(UnifiedMinishiftRuntimeDetector.java:180) at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.matches(UnifiedMinishiftRuntimeDetector.java:171) at org.jboss.tools.openshift.internal.cdk.server.core.detection.AbstractCDKRuntimeDetector.exists(AbstractCDKRuntimeDetector.java:111) at org.jboss.tools.runtime.core.internal.RuntimeDetector.exists(RuntimeDetector.java:68) at org.jboss.tools.runtime.core.util.RuntimeModelUtil.verifyRuntimeDefinitionCreated(RuntimeModelUtil.java:131) at org.jboss.tools.runtime.core.util.RuntimeModelUtil.verifyRuntimeDefinitionCreated(RuntimeModelUtil.java:122) at org.jboss.tools.runtime.core.util.RuntimeModelUtil.verifyRuntimeDefinitionCreated(RuntimeModelUtil.java:118) at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner.wouldOpenSearchRuntimePathDialog(RuntimeScanner.java:152) at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner.access$0(RuntimeScanner.java:129) at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:81) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-26358) Implement JMX integration tests

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26358?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26358: ---------------------------------- Fix Version/s: 4.10.0.AM1 > Implement JMX integration tests > ------------------------------- > > Key: JBIDE-26358 > URL: https://issues.jboss.org/browse/JBIDE-26358 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, jmx > Affects Versions: 4.9.0.AM3 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.9.0.Final, 4.10.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-26339) Update jboss-stacks/minishift.yaml to offer actual container runtime binaries

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26339?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26339: ---------------------------------- Fix Version/s: 4.10.0.AM1 (was: 4.9.0.Final) > Update jboss-stacks/minishift.yaml to offer actual container runtime binaries > ----------------------------------------------------------------------------- > > Key: JBIDE-26339 > URL: https://issues.jboss.org/browse/JBIDE-26339 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdk, qa > Affects Versions: 4.9.0.AM3 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.10.0.AM1 > > > Update offering of downloadable container runtimes in devstudio via jboss-stacks/minishift.yaml and bundled org.jboss.tools.openshift.cdk.server/resources/minishift.yaml. > * minishift 1.22 > * minishift 1.23 > * minishift 1.24 > * cdk 3.6.0 (after its official release) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-26388) TP: create target platform based on Eclipse 4.10 (Simrel 2018-12)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26388?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26388: ------------------------------- Story Points: 25 (was: 42) > TP: create target platform based on Eclipse 4.10 (Simrel 2018-12) > ----------------------------------------------------------------- > > Key: JBIDE-26388 > URL: https://issues.jboss.org/browse/JBIDE-26388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.10.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.10.0.AM1, 4.10.0.Final > > > In order to start Eclipse 4.10-based builds, we need an updated target platform. > Note that Eclipse 4.10 drops support for win32 and lin32 platforms, so poms will need to be updated accordingly. 32-bit is dead, long live 64-bit! > For sprint 156 / AM1: simrel M1 > For sprint 157 / AM1: simrel M2 > For sprint 158 / GA: simrel M3/RC1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-26388) TP: create target platform based on Eclipse 4.10 (Simrel 2018-12)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26388?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26388: ------------------------------- Affects Version/s: 4.10.0.AM1 (was: 4.9.0.Final) > TP: create target platform based on Eclipse 4.10 (Simrel 2018-12) > ----------------------------------------------------------------- > > Key: JBIDE-26388 > URL: https://issues.jboss.org/browse/JBIDE-26388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.10.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.10.0.AM1, 4.10.0.Final > > > In order to start Eclipse 4.10-based builds, we need an updated target platform. > Note that Eclipse 4.10 drops support for win32 and lin32 platforms, so poms will need to be updated accordingly. 32-bit is dead, long live 64-bit! > For sprint 156 / AM1: simrel M1 > For sprint 157 / AM1: simrel M2 > For sprint 158 / GA: simrel M3/RC1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-26388) TP: create target platform based on Eclipse 4.10 (Simrel 2018-12)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26388?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26388: ------------------------------- Fix Version/s: 4.10.0.AM1 > TP: create target platform based on Eclipse 4.10 (Simrel 2018-12) > ----------------------------------------------------------------- > > Key: JBIDE-26388 > URL: https://issues.jboss.org/browse/JBIDE-26388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.10.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.10.0.AM1, 4.10.0.Final > > > In order to start Eclipse 4.10-based builds, we need an updated target platform. > Note that Eclipse 4.10 drops support for win32 and lin32 platforms, so poms will need to be updated accordingly. 32-bit is dead, long live 64-bit! > For sprint 156 / AM1: simrel M1 > For sprint 157 / AM1: simrel M2 > For sprint 158 / GA: simrel M3/RC1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-26132) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [visual-page-editor-core]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26132?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-26132. -------------------------------- Resolution: Done > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [visual-page-editor-core] > ------------------------------------------------------------------------------------ > > Key: JBIDE-26132 > URL: https://issues.jboss.org/browse/JBIDE-26132 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: visual-page-editor-core > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [visual-page-editor-core]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for visual-page-editor-core task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

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 September 2018