[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, 4 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, 4 weeks
[JBoss JIRA] (JBIDE-18495) Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18495?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18495:
-----------------------------------
Fix Version/s: 4.2.x
(was: 4.2.3.Final)
> Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18495
> URL: https://issues.jboss.org/browse/JBIDE-18495
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.CR1
> Java 1.7 - OpenJDK
> RHEL 6
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Fix For: 4.2.x
>
> Attachments: Screenshot.png
>
>
> Steps to recreate issue:
> * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap
> * Install JBDS8.0.CR1
> * Import-> Existing Maven Projects the "jts" quickstart
> These errors are raised (see attached screenshot):
> No marketplace entries found to handle Connector org.eclipse.m2e.wtp.jpa.internal.configurator.wtp in Eclipse. Please see Help for more information.
> No marketplace entries found to handle null in Eclipse. Please see Help for more information.
> No marketplace entries found to handle maven-ejb-plugin:2.3:ejb in Eclipse. Please see Help for more information.
> No marketplace entries found to handle /jboss-jts-application-component-2/pom.xml in Eclipse. Please see Help for more information.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 6 months
[JBoss JIRA] (JBIDE-18452) XULRunner 1.9 is not supported for linux with GTK3, WIndows and Mac OS X 64-bit
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18452?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18452:
-----------------------------------
Fix Version/s: 4.3.x
(was: 4.2.1.Final)
> XULRunner 1.9 is not supported for linux with GTK3, WIndows and Mac OS X 64-bit
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18452
> URL: https://issues.jboss.org/browse/JBIDE-18452
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Final
> Reporter: Denis Golovin
> Fix For: 4.3.x
>
>
> Current version of VPE provides full functionality (JSF and HTML4/HTML5 preview/editing) only on 32 bit Windows and Mac OS X.
> Full functionality on Linux with SWT GTK2 with limitations. XULRunner based VPE and WebKit based HTML5 preview cannot be used at the same time because of libraries conflicts.
> Eclipse with SWT/GTK 2 can use only XULRunner base VPE for JSF and HTML Preview without full HTM5 support, or WebKit based preview with full HTML5 support, but without JSF visual editing.
> Eclipse with SWT/GTK3 can use only WebKit based preview implementation.
> Windows 64-bit has XULRunner feature that can be installed, but it is not officially supported yet, so only HTML preview based on IE is supported by default.
> Mac OS 64 bit is not supported.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 6 months