[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
19 hours, 6 minutes
[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)
3 weeks, 4 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
4 weeks
[JBoss JIRA] (JBIDE-21080) Explorer: "Import Application" context menu item is available for any tree item under an OpenShift 3 connection
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21080?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-21080.
---------------------------------
Resolution: Done
There you go : "Import Application" menu now restricted to connection, project and build configs.
> Explorer: "Import Application" context menu item is available for any tree item under an OpenShift 3 connection
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21080
> URL: https://issues.jboss.org/browse/JBIDE-21080
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Minor
> Labels: explorer, import_wizard, openshift_v3
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> There is a context menu item to import an existing OpenShift 3 application available on every tree item placed under OpenShift 3 connection. Even "folder" for any resource has it (e.g. Routes, Services) and any resource too (e.g. specific pod, service, replication controller).
> I think this is not good because it go against concept of *context* menu. We could have it for a project and build config (maybe also for a connection) that would be sufficient.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20990:
-------------------------------------
Initial PRs have been merged. Still need to fix Windows support though (currently hard codes vagrant path for linux in plugins/org.jboss.tools.openshift.cdk.server/src/org/jboss/tools/openshift/cdk/server/core/internal/CDKConstantUtility.java)
> Add "CDK Server" for start/stop for the CDK
> -------------------------------------------
>
> Key: JBIDE-20990
> URL: https://issues.jboss.org/browse/JBIDE-20990
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> We want to be able to start/stop CDK easily.
> Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start.
> note: the vagrant image might already be running so just need to be able to take care of that.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21155) fix test failures
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21155?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-21155:
----------------------------------------
Assignee: Andre Dietisheim
> fix test failures
> -----------------
>
> Key: JBIDE-21155
> URL: https://issues.jboss.org/browse/JBIDE-21155
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> {code}
> Tests in error:
> ConnectionPropertySourceTest.setup:29 » IllegalArgument
> ConnectionPropertySourceTest.setup:29 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerLabelProviderTest.getStyledTextForAConnection:188 » IllegalArgument
> OpenShiftExplorerLabelProviderTest.getStyledTextForAConnectionWithoutUserName:195 » IllegalArgument
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21155) fix test failures
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21155?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21155:
-------------------------------------
Fix Version/s: 4.3.1.Beta1
4.4.0.Alpha1
> fix test failures
> -----------------
>
> Key: JBIDE-21155
> URL: https://issues.jboss.org/browse/JBIDE-21155
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> {code}
> Tests in error:
> ConnectionPropertySourceTest.setup:29 » IllegalArgument
> ConnectionPropertySourceTest.setup:29 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerLabelProviderTest.getStyledTextForAConnection:188 » IllegalArgument
> OpenShiftExplorerLabelProviderTest.getStyledTextForAConnectionWithoutUserName:195 » IllegalArgument
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21155) fix test failures
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21155:
----------------------------------------
Summary: fix test failures
Key: JBIDE-21155
URL: https://issues.jboss.org/browse/JBIDE-21155
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Andre Dietisheim
{code}
Tests in error:
ConnectionPropertySourceTest.setup:29 » IllegalArgument
ConnectionPropertySourceTest.setup:29 » IllegalArgument
ConnectionPersistencyTest.setup:36 » IllegalArgument
ConnectionPersistencyTest.setup:36 » IllegalArgument
ConnectionPersistencyTest.setup:36 » IllegalArgument
ConnectionTest.setup:52 » IllegalArgument
ConnectionTest.setup:52 » IllegalArgument
ConnectionTest.setup:52 » IllegalArgument
ConnectionTest.setup:52 » IllegalArgument
ConnectionTest.setup:52 » IllegalArgument
ConnectionTest.setup:52 » IllegalArgument
ConnectionTest.setup:52 » IllegalArgument
ConnectionTest.setup:52 » IllegalArgument
ConnectionTest.setup:52 » IllegalArgument
ConnectionTest.setup:52 » IllegalArgument
OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
OpenShiftExplorerLabelProviderTest.getStyledTextForAConnection:188 » IllegalArgument
OpenShiftExplorerLabelProviderTest.getStyledTextForAConnectionWithoutUserName:195 » IllegalArgument
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years