[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 month
[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, 1 week
[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19532:
-------------------------------------
I've been digging code for quite a while today but can't see any reason for the strange behavior. Even assuming your OS will return the underlying folder path rather than teh symlink path, it should still be validating it.
We may need to add this one to the list of things to verify together via a code-trace.
> "Edit Server Runtime Environment" Dialog configuration validation is broken
> ---------------------------------------------------------------------------
>
> Key: JBIDE-19532
> URL: https://issues.jboss.org/browse/JBIDE-19532
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.Beta1
>
> Attachments: data-folder-config.png, Edit Server Runtime Environment _102.png, JBIDE-19532.png
>
>
> If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start.
> {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist.
> at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213)
> at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 6 months
[JBoss JIRA] (JBIDE-19637) Runtime download not working from New Server dialog
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19637:
-------------------------------------
[~mmalina] We may need to try to set up a day when we can trace through several bugs at once. Let's schedule a day next week where we can make this happen. I'm sorry if I'll be causing you more work, but I simply don't have access to a Mac to do this debugging. =/
> Runtime download not working from New Server dialog
> ---------------------------------------------------
>
> Key: JBIDE-19637
> URL: https://issues.jboss.org/browse/JBIDE-19637
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything.
> If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work.
> This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 6 months
[JBoss JIRA] (JBIDE-19738) Failed runtime download offers no error message
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19738?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19738:
-------------------------------------
I'm not able to replicate this. My methodology is as follows:
1) enable internet ;)
2) window -> prefs -> jboss runtime detection
3) download
4) Select jboss fsw 6, press next
5) type in credentials
6) accept license, press next
7) disable internet
8) type in proper directories etc
9) perform finish
10) observe error "Host not found" shows up.
In general it seems that any exception or status object returned by InternalURLTransport.download(etc) is displayed as an error dialog by the download-runtimes logic.
So if your usecase isn't showing such an error dialog, the error must be occurring at a different time or for a different reason. But i can't imagine what those reasons are, and my traces through aren't providing any more information or obvious locations where errors are being ignored.
Any more info is definitely appreciated.
> Failed runtime download offers no error message
> -----------------------------------------------
>
> Key: JBIDE-19738
> URL: https://issues.jboss.org/browse/JBIDE-19738
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.3.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> While verifying JBIDE-19571 the runtime download failed and there was no error whatsoever. The download of FSW 6.0 almost started, but after a few seconds on the progress bar an error window showed up for a moment and then disappeared again and the download window was gone, too. After this, there was no error in the error view or the workspace log.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 6 months
[JBoss JIRA] (JBIDE-19742) Change color of B in batch Icon
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19742?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-19742:
-------------------------------------
!NewBatchIcon.png! looks much better IMHO. +1 to apply
> Change color of B in batch Icon
> -------------------------------
>
> Key: JBIDE-19742
> URL: https://issues.jboss.org/browse/JBIDE-19742
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: batch
> Affects Versions: 4.3.0.Alpha2
> Reporter: Fred Bricon
> Assignee: Daniel Azarov
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
> Attachments: NewBatchIcon.png
>
>
> My brains keeps processing the red B of !https://raw.githubusercontent.com/jbosstools/jbosstools-javaee/03d08a6ffea565dca1207dc37d8ff1d213f4ab28/batch/plugins/org.jboss.tools.batch.ui/images/batch_icon16.png! as an error marker every time I see it.
> Could we please use another color? Blue or dark Green, nothing too bright.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 6 months
[JBoss JIRA] (JBIDE-19748) No error or message is displayed when a project namespace has no templates
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-19748:
-------------------------------------
Summary: No error or message is displayed when a project namespace has no templates
Key: JBIDE-19748
URL: https://issues.jboss.org/browse/JBIDE-19748
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Jeff Cantrill
Assignee: Jeff Cantrill
The following error when no templates are in a project namespace:
org.eclipse.core.runtime.AssertionFailedException: null argument:
at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:583)
at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1001)
at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:700)
at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1349)
at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:353)
at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:906)
at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:617)
at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:815)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791)
at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:611)
at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1541)
at org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:790)
at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1525)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1462)
at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:366)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1423)
at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1517)
at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:292)
at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1701)
at org.jboss.tools.openshift.internal.ui.wizard.application.ResourcesDetailsPage.createTemplatesViewer(ResourcesDetailsPage.java:66)
at org.jboss.tools.openshift.internal.ui.wizard.application.ResourcesDetailsPage.doCreateControls(ResourcesDetailsPage.java:48)
at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage.createControl(AbstractOpenShiftWizardPage.java:70)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
at org.eclipse.jface.window.Window.create(Window.java:430)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.createWizardDialog(WizardUtils.java:53)
at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.openWizard(WizardUtils.java:74)
at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.openWizard(WizardUtils.java:67)
at org.jboss.tools.openshift.internal.ui.command.NewApplicationHandler.execute(NewApplicationHandler.java:36)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
... 38 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 6 months