[JBoss JIRA] Created: (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance
by Jim Tyrrell (JIRA)
Console not showing up when staritng a EAP/SOA-P Instance
---------------------------------------------------------
Key: JBDS-983
URL: https://jira.jboss.org/jira/browse/JBDS-983
Project: JBoss Developer Studio
Issue Type: Feature Request
Affects Versions: 3.0.0.M4
Reporter: Jim Tyrrell
For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1 week, 2 days
[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
1 month, 1 week
[JBoss JIRA] (JBTIS-543) Add missing JBDS TP bits to JBDS IS update site zip
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-543?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBTIS-543:
-----------------------------
Project: JBoss Tools Integration Stack (was: Developer Studio (JBoss Developer Studio))
Key: JBTIS-543 (was: JBDS-3565)
Workflow: GIT Pull Request workflow (was: CDW v1)
Status: Open (was: New)
Docs QE Status: (was: NEW)
Component/s: distribution
(was: build)
Affects Version/s: 9.0.0.Alpha1
(was: 9.1.0.Beta1)
Fix Version/s: 9.0.0.Alpha1
(was: 9.1.0.Beta2)
> Add missing JBDS TP bits to JBDS IS update site zip
> ---------------------------------------------------
>
> Key: JBTIS-543
> URL: https://issues.jboss.org/browse/JBTIS-543
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 9.0.0.Alpha1
> Environment: Customer Support Portal
> Reporter: Mustafa Musaji
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha1
>
>
> Offline ZIP installation allows for JBDSIS tooling to be installed when there is no internet connection available. These zips for the JBDSIS and early access tooling is available from the CSP, however, some dependencies for this tooling is only available on the Target Platform zip.
> This TP zip is only available on the jboss.org site https://devstudio.jboss.com/9.0/stable/updates/ and not on the customer portal.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20998) Application wizard: Validation error description in Resource Labels page is cut off
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20998?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-20998 at 12/30/15 6:14 PM:
-------------------------------------------------------------------------
I would suggest:
1. Complete rules for valid label/value may be put to tooltips for the input label widgets.
2. Error description should be concise. It may be nice to point out the specific problem. Examples:
Label is not valid. Symbol '@' is not allowed.
Label is not valid. Total length cannot be more than 253.
was (Author: scabanovich):
I would suggest:
1. Complete rules for valid label may be put to the tooltip for the input label widget.
2. Error description should be concise. It may be nice to point out the specific problem. Examples:
Label is not valid. Symbol '@' is not allowed.
Label is not valid. Total length cannot be more than 253.
> Application wizard: Validation error description in Resource Labels page is cut off
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-20998
> URL: https://issues.jboss.org/browse/JBIDE-20998
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Final
> Reporter: Marián Labuda
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.Beta2
>
> Attachments: resource_label_complete.png, resource_label_incomplete.png
>
>
> In Resource Label dialog there is a validation error description about correct format of a label. But the validation error description is cut off. On first sight it does not look like like cut off, but after resizing a shell more text is showed. See following image of cut off description:
> !resource_label_incomplete.png!
> And following image contains full description after resizing to "long enough" width:
> !resource_label_complete.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20998) Application wizard: Validation error description in Resource Labels page is cut off
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20998?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-20998:
-----------------------------------------------
I would suggest:
1. Complete rules for valid label may be put to the tooltip for the input label widget.
2. Error description should be concise. It may be nice to point out the specific problem. Examples:
Label is not valid. Symbol '@' is not allowed.
Label is not valid. Total length cannot be more than 253.
> Application wizard: Validation error description in Resource Labels page is cut off
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-20998
> URL: https://issues.jboss.org/browse/JBIDE-20998
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Final
> Reporter: Marián Labuda
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.Beta2
>
> Attachments: resource_label_complete.png, resource_label_incomplete.png
>
>
> In Resource Label dialog there is a validation error description about correct format of a label. But the validation error description is cut off. On first sight it does not look like like cut off, but after resizing a shell more text is showed. See following image of cut off description:
> !resource_label_incomplete.png!
> And following image contains full description after resizing to "long enough" width:
> !resource_label_complete.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years