[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] (JBDS-4555) Unknown category error in Red Hat Central - Integration Stack connectors don't show Supported status
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4555?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4555:
-----------------------------
Labels: releasework (was: )
> Unknown category error in Red Hat Central - Integration Stack connectors don't show Supported status
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4555
> URL: https://issues.jboss.org/browse/JBDS-4555
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 11.1.0.AM2
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 11.1.0.GA
>
> Attachments: categories.png
>
>
> I installed devstudio 11.1.0.AM2 B1060 and went to central's Updates/Software tab and immediately got these errors:
> Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.switchyard' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar
> Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.soa' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar
> Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.bpr' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25314) CDK integration tests for propagation of values to launch configuration
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25314?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25314:
----------------------------------
Labels: cdk (was: )
> CDK integration tests for propagation of values to launch configuration
> -----------------------------------------------------------------------
>
> Key: JBIDE-25314
> URL: https://issues.jboss.org/browse/JBIDE-25314
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Labels: cdk
>
> Check propagation of values of CDK server configuration into these launch config's part: Main Tab: Name, Location of minishift binary, Arguments (hypervisor and profile name), Environment Tab: Environment variables check (minishift home, minishift username and path). Also, this check can be done after CDK server adapter is created via wizard, and when CDK server editor is changed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25314) CDK integration tests for propagation of values to launch configuration
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25314?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25314:
----------------------------------
Story Points: 13
> CDK integration tests for propagation of values to launch configuration
> -----------------------------------------------------------------------
>
> Key: JBIDE-25314
> URL: https://issues.jboss.org/browse/JBIDE-25314
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
>
> Check propagation of values of CDK server configuration into these launch config's part: Main Tab: Name, Location of minishift binary, Arguments (hypervisor and profile name), Environment Tab: Environment variables check (minishift home, minishift username and path). Also, this check can be done after CDK server adapter is created via wizard, and when CDK server editor is changed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25314) CDK integration tests for propagation of values to launch configuration
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25314?page=com.atlassian.jira.plugi... ]
Ondrej Dockal reassigned JBIDE-25314:
-------------------------------------
Assignee: Ondrej Dockal
> CDK integration tests for propagation of values to launch configuration
> -----------------------------------------------------------------------
>
> Key: JBIDE-25314
> URL: https://issues.jboss.org/browse/JBIDE-25314
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
>
> Check propagation of values of CDK server configuration into these launch config's part: Main Tab: Name, Location of minishift binary, Arguments (hypervisor and profile name), Environment Tab: Environment variables check (minishift home, minishift username and path). Also, this check can be done after CDK server adapter is created via wizard, and when CDK server editor is changed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25314) CDK integration tests for propagation of values to launch configuration
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25314?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25314:
----------------------------------
Description: Check propagation of values of CDK server configuration into these launch config's part: Main Tab: Name, Location of minishift binary, Arguments (hypervisor and profile name), Environment Tab: Environment variables check (minishift home, minishift username and path). Also, this check can be done after CDK server adapter is created via wizard, and when CDK server editor is changed. (was: Check propagation of values of CDK server configuration into these launch config's part: Main Tab: Name, Location of minishift binary, Arguments (hypervisor and profile name), Environment Tab: Environment variables check (minishift home, minishift username and path.))
> CDK integration tests for propagation of values to launch configuration
> -----------------------------------------------------------------------
>
> Key: JBIDE-25314
> URL: https://issues.jboss.org/browse/JBIDE-25314
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Priority: Critical
>
> Check propagation of values of CDK server configuration into these launch config's part: Main Tab: Name, Location of minishift binary, Arguments (hypervisor and profile name), Environment Tab: Environment variables check (minishift home, minishift username and path). Also, this check can be done after CDK server adapter is created via wizard, and when CDK server editor is changed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25314) CDK integration tests for propagation of values to launch configuration
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-25314:
-------------------------------------
Summary: CDK integration tests for propagation of values to launch configuration
Key: JBIDE-25314
URL: https://issues.jboss.org/browse/JBIDE-25314
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: integration-tests
Affects Versions: 4.5.1.Final
Reporter: Ondrej Dockal
Priority: Critical
Check propagation of values of CDK server configuration into these launch config's part: Main Tab: Name, Location of minishift binary, Arguments (hypervisor and profile name), Environment Tab: Environment variables check (minishift home, minishift username and path.)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months