[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
18 hours, 23 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-26643) Page "CDI Facets settings" page is not present in the "CDI Web Project" wizard when CDI 2.0 is used
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26643?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26643:
-------------------------------
Fix Version/s: 4.12.0.Final
(was: 4.12.0.AM1)
> Page "CDI Facets settings" page is not present in the "CDI Web Project" wizard when CDI 2.0 is used
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26643
> URL: https://issues.jboss.org/browse/JBIDE-26643
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.11.0.Final
> Environment: OS X 10.14.5
> Reporter: Zbyněk Červinka
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.12.0.Final
>
> Attachments: page_missing_on_cdi_2_0.png
>
>
> Page captured on the "page_missing_on_cdi_2_0.png" img in Attachment is not present in the "CDI Web Project" wizard when CDI 2.0 is used. It is present when CDI 1.0, 1.1 or 1.2 is used and it should be either present for all CDI versions or not present at any CDI version (the wizard should be consistent and if there is not reason for that it should be the same for all versions).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
1 month, 1 week
[JBoss JIRA] (JBIDE-26712) WildFly quickstart 'jts' contains errors after import into Red Hat CodeReady Studio in the 'jboss-ejb3.xml' file
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-26712?page=com.atlassian.jira.plug... ]
Zbyněk Červinka commented on JBIDE-26712:
-----------------------------------------
h1. *Update on this issue - WildFly version 18.0.1.Final:*
After todays testing in Red Hat CodeReady Studio I have found *{color:#DE350B}the same 2 errors{color}* as mentioned in the *Description* of this issue.
h2. Version of the Red Hat CodeReady Studio:
Version: 12.14.0.GA
Build id: GA-v20200227-0726-B6011
Build date: 20200227-0726
> WildFly quickstart 'jts' contains errors after import into Red Hat CodeReady Studio in the 'jboss-ejb3.xml' file
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26712
> URL: https://issues.redhat.com/browse/JBIDE-26712
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.12.0.AM1
> Environment: OS X 10.14.5
> Reporter: Zbyněk Červinka
> Priority: Major
> Fix For: 4.15.x
>
> Attachments: Problems view.png, Project Explorer.png
>
>
> h1. *The "jboss-ejb3.xml" file in the WildFly "jts" quickstart contains the following 2 errors:*
> * cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected.
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-j8-WF-new/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> h2. Red Hat CodeReady Studio version: 12.12.0.GA
> h2. WildFly version: 17.0.0.Final
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-26711) WildFly quickstart 'jaxws-retail' shows errors after import
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-26711?page=com.atlassian.jira.plug... ]
Zbyněk Červinka commented on JBIDE-26711:
-----------------------------------------
h1. *Update on this issue - WildFly version 18.0.1.Final:*
After todays testing in Red Hat CodeReady Studio I have found the following errors in the Problems view:
* Customer cannot be resolved to a type
* DiscountRequest cannot be resolved to a type
* DiscountResponse cannot be resolved to a type
* ProfileMgmt cannot be resolved to a type
* The import org.jboss.quickstarts.ws.jaxws.samples.retail.profile.Customer cannot be resolved
* The import org.jboss.quickstarts.ws.jaxws.samples.retail.profile.DiscountRequest cannot be resolved
* The import org.jboss.quickstarts.ws.jaxws.samples.retail.profile.DiscountResponse cannot be resolved
* The import org.jboss.quickstarts.ws.jaxws.samples.retail.profile.ProfileMgmt cannot be resolved
* Type mismatch: cannot convert from ProfileMgmt to ProfileMgmt
h2. Picture of the Problems view with current 17 errors for WildFly 18:
!Snímek obrazovky 2020-02-28 v 14.33.40.png|thumbnail!
h2. Version of the Red Hat CodeReady Studio:
Version: 12.14.0.GA
Build id: GA-v20200227-0726-B6011
Build date: 20200227-0726
> WildFly quickstart 'jaxws-retail' shows errors after import
> -----------------------------------------------------------
>
> Key: JBIDE-26711
> URL: https://issues.redhat.com/browse/JBIDE-26711
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.12.0.AM1
> Environment: OS X 10.14.5
> Reporter: Zbyněk Červinka
> Priority: Major
> Fix For: 4.15.x
>
> Attachments: Problems view.png, Project Explorer.png, Snímek obrazovky 2020-02-28 v 14.33.40.png, problems_view_WF_18.png
>
>
> h1. WildFly "jaxws-retail" quickstart contains the following errors:
> * Missing artifact com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.16-jbossorg-1 pom.xml
> * Missing artifact org.slf4j:slf4j-api:jar:1.7.22.jbossorg-1
> * Missing artifact com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.16-jbossorg-1
> * The container 'Maven Dependencies' references non existing library '/mnt/hudson_workspace/workspace/examples.wildfly.it.weekly/jdk/jdk11/label/fedora30/jbosstools-integration-tests/tests/org.jboss.tools.examples.ui.bot.test/target/repository/org/slf4j/slf4j-api/1.7.22.jbossorg-1/slf4j-api-1.7.22.jbossorg-1.jar'
> * The project cannot be built until build path errors are resolved
> h2. Red Hat CodeReady Studio version: 12.12.0.GA
> h2. WildFly version: 17.0.0.Final
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-26711) WildFly quickstart 'jaxws-retail' shows errors after import
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-26711?page=com.atlassian.jira.plug... ]
Zbyněk Červinka updated JBIDE-26711:
------------------------------------
Attachment: Snímek obrazovky 2020-02-28 v 14.33.40.png
> WildFly quickstart 'jaxws-retail' shows errors after import
> -----------------------------------------------------------
>
> Key: JBIDE-26711
> URL: https://issues.redhat.com/browse/JBIDE-26711
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.12.0.AM1
> Environment: OS X 10.14.5
> Reporter: Zbyněk Červinka
> Priority: Major
> Fix For: 4.15.x
>
> Attachments: Problems view.png, Project Explorer.png, Snímek obrazovky 2020-02-28 v 14.33.40.png, problems_view_WF_18.png
>
>
> h1. WildFly "jaxws-retail" quickstart contains the following errors:
> * Missing artifact com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.16-jbossorg-1 pom.xml
> * Missing artifact org.slf4j:slf4j-api:jar:1.7.22.jbossorg-1
> * Missing artifact com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.16-jbossorg-1
> * The container 'Maven Dependencies' references non existing library '/mnt/hudson_workspace/workspace/examples.wildfly.it.weekly/jdk/jdk11/label/fedora30/jbosstools-integration-tests/tests/org.jboss.tools.examples.ui.bot.test/target/repository/org/slf4j/slf4j-api/1.7.22.jbossorg-1/slf4j-api-1.7.22.jbossorg-1.jar'
> * The project cannot be built until build path errors are resolved
> h2. Red Hat CodeReady Studio version: 12.12.0.GA
> h2. WildFly version: 17.0.0.Final
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-26708) WildFly quickstart 'messaging-clustering-singleton' shows errors after import
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-26708?page=com.atlassian.jira.plug... ]
Zbyněk Červinka edited comment on JBIDE-26708 at 2/28/20 8:06 AM:
------------------------------------------------------------------
h1. *Update on this issue - WildFly version 18.0.1.Final:*
After testing in Red Hat CodeReady Studio I have found the same 3 errors as mentioned in the Description of this issue.
The error message differs a little bit in the version of the *{color:#DE350B}jar{color}*. See the following updated error messages with highlighted version change:
* Referenced file contains errors (jar:file:/Applications/codereadystudio/studio/codereadystudio.app/Contents/Eclipse/plugins/{color:#DE350B}org.jboss.tools.as.catalog_3.9.0.v20200224-1753.jar{color}!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd).
* Referenced file contains errors (jar:file:/Applications/codereadystudio/studio/codereadystudio.app/Contents/Eclipse/plugins/{color:#DE350B}org.jboss.tools.as.catalog_3.9.0.v20200224-1753.jar{color}!/schema/xsd/jboss-ejb3-2_0.xsd).
* Referenced file contains errors (jar:file:/Applications/codereadystudio/studio/codereadystudio.app/Contents/Eclipse/plugins/{color:#DE350B}org.jboss.tools.as.catalog_3.9.0.v20200224-1753.jar{color}!/schema/xsd/jboss-ejb3-spec-2_0.xsd).
h2. Version of the Red Hat CodeReady Studio:
Version: 12.14.0.GA
Build id: GA-v20200227-0726-B6011
Build date: 20200227-0726
was (Author: zcervink):
h1. *Update on this issue - WildFly version 18.0.1.Final:*
After testing in Red Hat CodeReady Studio I have found the same 3 errors as mentioned in the Description of this issue.
The error message differs a little bit in the version of the *{color:#DE350B}jar{color}*. See the following updated error messages with highlighted version change:
* Referenced file contains errors (jar:file:/Applications/codereadystudio/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.9.0.v20200224-1753.jar!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd).
* Referenced file contains errors (jar:file:/Applications/codereadystudio/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.9.0.v20200224-1753.jar!/schema/xsd/jboss-ejb3-2_0.xsd).
* Referenced file contains errors (jar:file:/Applications/codereadystudio/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.9.0.v20200224-1753.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd).
h2. Version of the Red Hat CodeReady Studio:
Version: 12.14.0.GA
Build id: GA-v20200227-0726-B6011
Build date: 20200227-0726
> WildFly quickstart 'messaging-clustering-singleton' shows errors after import
> -----------------------------------------------------------------------------
>
> Key: JBIDE-26708
> URL: https://issues.redhat.com/browse/JBIDE-26708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.12.0.AM1
> Environment: OS X 10.14.5
> Reporter: Zbyněk Červinka
> Priority: Major
> Fix For: 4.15.x
>
> Attachments: Problems view.png, Project explorer.png, jboss-ejb3.xml file.png
>
>
> h1. WF quickstart 'messaging-clustering-singleton' shows 3 errors in the jboss-ejb3.xml file after import:
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-j8-wf/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-j8-wf/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-j8-wf/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months