[jbosstools-issues] [JBoss JIRA] (JBDS-3044) Align installation default path with installer filename

Martin Malina (JIRA) issues at jboss.org
Wed May 28 14:01:17 EDT 2014


    [ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971388#comment-12971388 ] 

Martin Malina commented on JBDS-3044:
-------------------------------------

To clarify, I did a fresh install of JBDS on Mac and now the longest is 218 + path to install dir.
Furthermore, there are 19 files whose path is longer than 200 (+ path to install dir again).
It's these:
{code}
nattura:jbdevstudio-length-test rasp$ find . |awk '{ print length($0) " " $0 ; }'|egrep '^2[0-9][0-9]'
214 ./studio/features/org.jboss.ide.eclipse.as.archives.integration.feature_3.0.0.Beta2-v20140523-2300-B47/META-INF/maven/org.jboss.tools.as.features/org.jboss.ide.eclipse.as.archives.integration.feature/pom.properties
207 ./studio/features/org.jboss.ide.eclipse.as.archives.integration.feature_3.0.0.Beta2-v20140523-2300-B47/META-INF/maven/org.jboss.tools.as.features/org.jboss.ide.eclipse.as.archives.integration.feature/pom.xml
204 ./studio/features/org.jboss.ide.eclipse.as.jmx.integration.feature_3.0.0.Beta2-v20140523-2300-B47/META-INF/maven/org.jboss.tools.as.features/org.jboss.ide.eclipse.as.jmx.integration.feature/pom.properties
203 ./studio/features/org.jboss.ide.eclipse.as.server.rse.integration.feature_3.0.0.Beta2-v20140523-2300-B47/META-INF/maven/org.jboss.tools.as.features/org.jboss.ide.eclipse.as.server.rse.integration.feature
218 ./studio/features/org.jboss.ide.eclipse.as.server.rse.integration.feature_3.0.0.Beta2-v20140523-2300-B47/META-INF/maven/org.jboss.tools.as.features/org.jboss.ide.eclipse.as.server.rse.integration.feature/pom.properties
211 ./studio/features/org.jboss.ide.eclipse.as.server.rse.integration.feature_3.0.0.Beta2-v20140523-2300-B47/META-INF/maven/org.jboss.tools.as.features/org.jboss.ide.eclipse.as.server.rse.integration.feature/pom.xml
208 ./studio/features/org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_3.0.0.Beta2-v20140523-2300-B47/META-INF/maven/org.jboss.tools.as.features/org.jboss.ide.eclipse.as.serverAdapter.wtp.feature/pom.properties
201 ./studio/features/org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_3.0.0.Beta2-v20140523-2300-B47/META-INF/maven/org.jboss.tools.as.features/org.jboss.ide.eclipse.as.serverAdapter.wtp.feature/pom.xml
214 ./studio/features/org.jboss.tools.foundation.security.linux.feature_1.1.0.Beta2-v20140523-1102-B28/META-INF/maven/org.jboss.tools.foundation.features/org.jboss.tools.foundation.security.linux.feature/pom.properties
207 ./studio/features/org.jboss.tools.foundation.security.linux.feature_1.1.0.Beta2-v20140523-1102-B28/META-INF/maven/org.jboss.tools.foundation.features/org.jboss.tools.foundation.security.linux.feature/pom.xml
203 ./studio/features/org.jboss.tools.maven.project.examples.feature_1.6.0.Beta2-v20140523-1339-B48/META-INF/maven/org.jboss.tools.maven.features/org.jboss.tools.maven.project.examples.feature/pom.properties
200 ./studio/features/org.jboss.tools.openshift.egit.integration.feature_2.6.0.Beta2-v20140523-1909-B25/META-INF/maven/org.jboss.tools.openshift.features/org.jboss.tools.openshift.egit.integration.feature
215 ./studio/features/org.jboss.tools.openshift.egit.integration.feature_2.6.0.Beta2-v20140523-1909-B25/META-INF/maven/org.jboss.tools.openshift.features/org.jboss.tools.openshift.egit.integration.feature/pom.properties
208 ./studio/features/org.jboss.tools.openshift.egit.integration.feature_2.6.0.Beta2-v20140523-1909-B25/META-INF/maven/org.jboss.tools.openshift.features/org.jboss.tools.openshift.egit.integration.feature/pom.xml
200 ./studio/features/org.jboss.tools.runtime.seam.detector.feature_3.6.0.Beta2-v20140523-2306-B31/META-INF/maven/org.jboss.tools.seam.features/org.jboss.tools.runtime.seam.detector.feature/pom.properties
200 ./studio/plugins/org.jboss.tools.forge.runtime_1.4.144.Beta2-v20140523-1507-B33/forge-distribution-1.4.4.Final/modules/org/jboss/shrinkwrap/descriptors/main/shrinkwrap-descriptors-api-1.1.0-beta-1.jar
201 ./studio/plugins/org.jboss.tools.forge.runtime_1.4.144.Beta2-v20140523-1507-B33/forge-distribution-1.4.4.Final/modules/org/jboss/shrinkwrap/descriptors/main/shrinkwrap-descriptors-impl-1.1.0-beta-1.jar
200 ./studio/plugins/org.jboss.tools.forge.runtime_1.4.144.Beta2-v20140523-1507-B33/forge-distribution-1.4.4.Final/modules/org/jboss/shrinkwrap/descriptors/main/shrinkwrap-descriptors-spi-1.1.0-beta-1.jar
207 ./studio/plugins/org.jboss.tools.forge.runtime_1.4.144.Beta2-v20140523-1507-B33/forge-distribution-1.4.4.Final/modules/sun/jdk/main/service-loader-resources/META-INF/services/javax.script.ScriptEngineFactory
{code}

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


More information about the jbosstools-issues mailing list