[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)
4 weeks, 1 day
[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
4 months
[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ]
Ondrej Dockal resolved JBIDE-25050.
-----------------------------------
Resolution: Done
> Prepare windows image with hyperv
> ---------------------------------
>
> Key: JBIDE-25050
> URL: https://issues.jboss.org/browse/JBIDE-25050
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.5.1.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Labels: jenkins
> Fix For: 4.11.0.Final
>
> Attachments: error.log
>
>
> Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label.
> * Provision win10-x64-jbds (as some changes were made to jbds script)
> * Install manually HyperV in fresh windows image
> * Add new virtual switch
> * Set env. variable HYPERV_VIRTUAL_SWITCH
> * Add user into Hyper-V Administrators group
> * Test whether cdk can be run on the slave
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-25050 at 2/28/19 2:14 PM:
----------------------------------------------------------------
As we moved to Upshift, hyperv seems to be a go on windows 10. Thus I am creating new snapshot that should fulfill our needs.
Specifics:
* I have added HYPERV_VS virtual switch
* Setting env. variable: MINISHIFT_HYPERV_VIRTUAL_SWITCH = Default Switch
* Hudson user is added to Hyperv administrators groups
was (Author: odockal):
As we moved to Upshift, hyperv seems to be a go on windows 10. Thus I am creating new snapshot that should fulfill our needs.
Specifics:
* I have added HYPERV_VS virtual switch
* Setting env. variable: MINISHIFT_HYPERV_VIRTUAL_SWITCH = HYPERV_VS
* Hudson user is added to Hyperv administrators groups
> Prepare windows image with hyperv
> ---------------------------------
>
> Key: JBIDE-25050
> URL: https://issues.jboss.org/browse/JBIDE-25050
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.5.1.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Labels: jenkins
> Fix For: 4.11.0.Final
>
> Attachments: error.log
>
>
> Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label.
> * Provision win10-x64-jbds (as some changes were made to jbds script)
> * Install manually HyperV in fresh windows image
> * Add new virtual switch
> * Set env. variable HYPERV_VIRTUAL_SWITCH
> * Add user into Hyper-V Administrators group
> * Test whether cdk can be run on the slave
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25050:
---------------------------------------
As we moved to Upshift, hyperv seems to be a go on windows 10. Thus I am creating new snapshot that should fulfill our needs.
Specifics:
* I have added HYPERV_VS virtual switch
* Setting env. variable: MINISHIFT_HYPERV_VIRTUAL_SWITCH = HYPERV_VS
* Hudson user is added to Hyperv administrators groups
> Prepare windows image with hyperv
> ---------------------------------
>
> Key: JBIDE-25050
> URL: https://issues.jboss.org/browse/JBIDE-25050
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.5.1.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Labels: jenkins
> Fix For: 4.11.0.Final
>
> Attachments: error.log
>
>
> Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label.
> * Provision win10-x64-jbds (as some changes were made to jbds script)
> * Install manually HyperV in fresh windows image
> * Add new virtual switch
> * Set env. variable HYPERV_VIRTUAL_SWITCH
> * Add user into Hyper-V Administrators group
> * Test whether cdk can be run on the slave
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBDS-4735) Central projects Wizard sometimes fails to open
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBDS-4735?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4735:
-----------------------------
Fix Version/s: 12.11.0.GA
(was: 12.11.0.AM1)
> Central projects Wizard sometimes fails to open
> -----------------------------------------------
>
> Key: JBDS-4735
> URL: https://issues.jboss.org/browse/JBDS-4735
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 12.9.0.GA
> Environment: manually Fedora 28, automation
> Reporter: Vojtech Prusa
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 12.11.0.GA
>
> Attachments: central.tar.gz, image-2018-10-17-09-24-31-555.png, screenshot-1.png
>
>
> There is "openInIDE" used in 3 places in "main.min.js" in central source code*. When the central reloads and works normally, "openInIDE" is a function (probably defined in Java code or somewhere out of the "main.min.js" file) with following implementation:
> function openInIDE() {
> var result = callJava(1, '9aee3b4a3f3b40ed26f47d66375b25e3', Array.prototype.slice.call(arguments));
> if (typeof result == 'string' && result.indexOf('org.eclipse.swt.browser.error') == 0) {
> var error = new Error(result.substring(29));
> throw error;
> }
> return result;
> }
> After the issue appears, "typedef openInIDE" is undefined, which causes probably the issues.
> *Additional information to the 3 places, where "openInIDE" appears - it appears in 2 functions:
> - registerButtonClicks() - here is the "openInIDE" needed for loading and displaying the central correctly
> - delegateToIDE(a, b) - here is the "openInIDE" needed for opening the wizard to the quickstart
> OLDER DESCRIPTION (does not describes the issue enough, but I decided to keep it for more details about the issue):
> ----------------------------------------------------------------------------------------------------------------------
> Sometimes central examples wizards fail to load and modal dialog is shown instead (screen attached).
> Nothing in Error log view.
> Restarting devstudio solves the issue.
> Adding screen and central tar of:
> devstudio-12.9.0.GA-v20180928-1629-B3448/workspaces/workspace/.metadata/.plugins/org.jboss.tools.central/central
> Addition info:
> Considering that central itests fails for this sometimes fresh installation without restart may cause this. Although it happen again after running devstudio for some time and restarting Central view.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-25814) Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-25814?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25814:
-------------------------------
Fix Version/s: 4.11.0.Final
(was: 4.11.0.AM1)
> Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25814
> URL: https://issues.jboss.org/browse/JBIDE-25814
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.3.AM2
> Reporter: Andre Dietisheim
> Assignee: Josef Kopriva
> Priority: Major
> Labels: server_adapter_wizard
> Fix For: 4.11.0.Final
>
>
> steps:
> # ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online)
> # EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application
> # ASSERT: Connection selection page pops up
> # EXEC: select your 2nd connection, get to the next page. But then, cancel the wizard, dont get any further.
> # EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter
> # ASSERT: Connection selection page pops up
> Result:
> the connection selection page has the 1st connection selected, not the one that we used most recently.
> (If you use the application wizard again, you'll notice how it is using the 2nd connection, the one that we used most recently)
> Bonus: some wizards even inspect the currently selected element in the OpenShift Explorer and deduce what they need. The server adapter wizard could inspect the resource that's selected and infer the connection from it.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months