July 2016 - 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] (JBIDE-22433) Properties: Add Storage tab

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22433?page=com.atlassian.jira.plugi... ] Dmitry Bocharov updated JBIDE-22433: ------------------------------------ Description: We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties. Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides. Using persistent volumes: # https://blog.openshift.com/experimenting-with-persistent-volumes/ # https://docs.openshift.com/enterprise/3.0/dev_guide/persistent_volumes.html Briefly: to see how persistent volume claims work, add the following json as a resource to the project: {code:title=Persistent Volume Claim Object Definition} { "apiVersion": "v1", "kind": "PersistentVolumeClaim", "metadata": { "name": "claim1" }, "spec": { "accessModes": [ "ReadWriteOnce" ], "resources": { "requests": { "storage": "5Gi" } } } } {code} was: We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties. Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides. > Properties: Add Storage tab > --------------------------- > > Key: JBIDE-22433 > URL: https://issues.jboss.org/browse/JBIDE-22433 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Assignee: Dmitry Bocharov > Labels: new_and_noteworthy, openshift_v3, properties > Fix For: 4.4.1.AM3 > > Attachments: storage from web console.png > > > We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties. > Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides. > Using persistent volumes: > # https://blog.openshift.com/experimenting-with-persistent-volumes/ > # https://docs.openshift.com/enterprise/3.0/dev_guide/persistent_volumes.html > Briefly: to see how persistent volume claims work, add the following json as a resource to the project: > {code:title=Persistent Volume Claim Object Definition} > { > "apiVersion": "v1", > "kind": "PersistentVolumeClaim", > "metadata": { > "name": "claim1" > }, > "spec": { > "accessModes": [ "ReadWriteOnce" ], > "resources": { > "requests": { > "storage": "5Gi" > } > } > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22433) Properties: Add Storage tab

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22433?page=com.atlassian.jira.plugi... ] Dmitry Bocharov updated JBIDE-22433: ------------------------------------ Description: We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties. Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides. Using persistent volumes: # https://blog.openshift.com/experimenting-with-persistent-volumes/ # https://docs.openshift.com/enterprise/3.0/dev_guide/persistent_volumes.html Briefly: to see how persistent volume claims work, add the following json as a resource to the project: {code:title=Persistent Volume Claim Object Definition} { "apiVersion": "v1", "kind": "PersistentVolumeClaim", "metadata": { "name": "claim1" }, "spec": { "accessModes": [ "ReadWriteOnce" ], "resources": { "requests": { "storage": "1Gi" } } } } {code} was: We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties. Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides. Using persistent volumes: # https://blog.openshift.com/experimenting-with-persistent-volumes/ # https://docs.openshift.com/enterprise/3.0/dev_guide/persistent_volumes.html Briefly: to see how persistent volume claims work, add the following json as a resource to the project: {code:title=Persistent Volume Claim Object Definition} { "apiVersion": "v1", "kind": "PersistentVolumeClaim", "metadata": { "name": "claim1" }, "spec": { "accessModes": [ "ReadWriteOnce" ], "resources": { "requests": { "storage": "5Gi" } } } } {code} > Properties: Add Storage tab > --------------------------- > > Key: JBIDE-22433 > URL: https://issues.jboss.org/browse/JBIDE-22433 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Assignee: Dmitry Bocharov > Labels: new_and_noteworthy, openshift_v3, properties > Fix For: 4.4.1.AM3 > > Attachments: storage from web console.png > > > We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties. > Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides. > Using persistent volumes: > # https://blog.openshift.com/experimenting-with-persistent-volumes/ > # https://docs.openshift.com/enterprise/3.0/dev_guide/persistent_volumes.html > Briefly: to see how persistent volume claims work, add the following json as a resource to the project: > {code:title=Persistent Volume Claim Object Definition} > { > "apiVersion": "v1", > "kind": "PersistentVolumeClaim", > "metadata": { > "name": "claim1" > }, > "spec": { > "accessModes": [ "ReadWriteOnce" ], > "resources": { > "requests": { > "storage": "1Gi" > } > } > } > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik commented on JBDS-3951: ----------------------------------------- Actually from my perspective this can be closed. I don't need _VBoxManage_ anymore. That said, I think it still makes sense to add it. A proper VirtualBox install adds these as well and allows you to use the various VBoxManage tools from the terminal. > Installer needs to add the VirtualBox install directory to the PATH > ------------------------------------------------------------------- > > Key: JBDS-3951 > URL: https://issues.jboss.org/browse/JBDS-3951 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.1.0.AM3 > > > The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found. > As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22859) Clean up class org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22859?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-22859. ------------------------------- Resolution: Done > Clean up class org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor > ---------------------------------------------------------------------- > > Key: JBIDE-22859 > URL: https://issues.jboss.org/browse/JBIDE-22859 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.AM2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3614) DevSuite Installer Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3614?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3614: -------------------------------- Summary: DevSuite Installer Installer (was: Developer Platform Installer) > DevSuite Installer Installer > ---------------------------- > > Key: JBDS-3614 > URL: https://issues.jboss.org/browse/JBDS-3614 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.1.0.AM3 > > > Make installer that has: > VirtualBox > Vagrant > Cygwin > CDK > (custom VagrantFile?) > (docker client?) > OpenJDK > Red Hat Developer Studio 9.1 > (with or without JBoss EAP ? - EAP 7 not available) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22859) Clean up class org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor

by Koen Aers (JIRA)

Koen Aers created JBIDE-22859: --------------------------------- Summary: Clean up class org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor Key: JBIDE-22859 URL: https://issues.jboss.org/browse/JBIDE-22859 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Affects Versions: 4.4.1.AM2 Reporter: Koen Aers -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22859) Clean up class org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22859?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-22859: --------------------------------- Assignee: Koen Aers > Clean up class org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor > ---------------------------------------------------------------------- > > Key: JBIDE-22859 > URL: https://issues.jboss.org/browse/JBIDE-22859 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.AM2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.1.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 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 July 2016