[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
[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
[JBoss JIRA] (JBIDE-19992) Open Properties view on double click of elemet in batch diagram
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19992?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-19992:
-----------------------------------------------
Double click is already implemented on Flow elements, it opens sub-diagram for that flow. Simple click on a diagram element selects it and, if Properties View is already opened, the selected element is shown in it. There is also context menu action 'Show in Properties View' that opens and activates the view. Provided all that, do we really need this enhancement?
> Open Properties view on double click of elemet in batch diagram
> ---------------------------------------------------------------
>
> Key: JBIDE-19992
> URL: https://issues.jboss.org/browse/JBIDE-19992
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: batch
> Affects Versions: 4.3.0.Beta1
> Reporter: Lucia Jelinkova
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Beta2
>
>
> In batch editor diagram tab, it would be nice if after double click on some element (e.g. step) corrensponding Properties view would be open and activated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months
[JBoss JIRA] (JBIDE-19992) Open Properties view on double click of elemet in batch diagram
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19992?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-19992 at 6/30/15 7:03 PM:
------------------------------------------------------------------------
Double click is already implemented on Flow elements for another purpose, it opens sub-diagram for that flow. Simple click on a diagram element selects it and, if Properties View is already opened, the selected element is shown in it. There is also context menu action 'Show in Properties View' that opens and activates the view. Provided all that, do we really need this enhancement?
was (Author: scabanovich):
Double click is already implemented on Flow elements, it opens sub-diagram for that flow. Simple click on a diagram element selects it and, if Properties View is already opened, the selected element is shown in it. There is also context menu action 'Show in Properties View' that opens and activates the view. Provided all that, do we really need this enhancement?
> Open Properties view on double click of elemet in batch diagram
> ---------------------------------------------------------------
>
> Key: JBIDE-19992
> URL: https://issues.jboss.org/browse/JBIDE-19992
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: batch
> Affects Versions: 4.3.0.Beta1
> Reporter: Lucia Jelinkova
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Beta2
>
>
> In batch editor diagram tab, it would be nice if after double click on some element (e.g. step) corrensponding Properties view would be open and activated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months
[JBoss JIRA] (JBIDE-19991) Add possibility "Show in Properties" to batch diagram validation message dialog
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19991?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-19991:
-----------------------------------------------
Content for this dialog is set internally in ValidationMarkerPresentation and there is no opening for custom extensions.
> Add possibility "Show in Properties" to batch diagram validation message dialog
> -------------------------------------------------------------------------------
>
> Key: JBIDE-19991
> URL: https://issues.jboss.org/browse/JBIDE-19991
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: batch
> Affects Versions: 4.3.0.Beta1
> Reporter: Lucia Jelinkova
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Beta2
>
> Attachments: validation.png
>
>
> There is possibility "Show in source" but since you can edit some properties in Properties view, it makes sense to add also "Show in Properties view".
> !validation.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months
[JBoss JIRA] (JBIDE-20173) Clean up UI errors in case RSE is not installed
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-20173:
-----------------------------------
Summary: Clean up UI errors in case RSE is not installed
Key: JBIDE-20173
URL: https://issues.jboss.org/browse/JBIDE-20173
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server
Affects Versions: 4.3.0.Beta1
Reporter: Rob Stryker
In an environment where RSE is not available, the UI fails in multiple fashions. It allows you to create RSE servers, even though it shouldn't. If there's a previously-existing RSE server, the server editor will fail to load with NPE. There is also no warning in the editor anywhere indicating that the server is incompatible with current profile.
Also, start / debug / etc should fail indicating profile is unavailable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months
[JBoss JIRA] (JBIDE-20016) Explorer: As a user I want to be able to create projects for OpenShift v3 connections
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20016?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-20016:
----------------------------------
Summary: Explorer: As a user I want to be able to create projects for OpenShift v3 connections (was: Explorer: As a user I want to be able to create and delete projects for OpenShift v3 connections)
> Explorer: As a user I want to be able to create projects for OpenShift v3 connections
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-20016
> URL: https://issues.jboss.org/browse/JBIDE-20016
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: explorer, openshift_v3
> Fix For: 4.3.0.Beta2
>
>
> Currently there is no other way to create a new project for OpenShift v3 then via openshift CLI. It would be nice to have New - Project context menu for v3 connections.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months
[JBoss JIRA] (JBIDE-20172) Explorer: As a user I want to be able to delete projects for OpenShift v3 connections
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-20172:
-------------------------------------
Summary: Explorer: As a user I want to be able to delete projects for OpenShift v3 connections
Key: JBIDE-20172
URL: https://issues.jboss.org/browse/JBIDE-20172
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Jeff Cantrill
Assignee: Jeff Cantrill
Priority: Critical
Fix For: 4.3.0.Beta2
Currently there is no other way to create a new project for OpenShift v3 then via openshift CLI. It would be nice to have New - Project context menu for v3 connections.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months