[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 week, 3 days
Corpsoft Solutions
by Aya Ya
https://corpsoft.io/service-category/web-development-in-charlotte-north-c... offers web development services based on a deep understanding of the client's digital processes and business goals in Charlotte, North Carolina,. Over the years, the team has established itself as a reliable partner capable of supporting a project from idea to full launch. The company's specialists use proven approaches to minimizing risks, ensuring stable results and high return on investment
1 week, 3 days
[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
[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 month, 3 weeks