[JBoss JIRA] Created: (JBIDE-9500) AS7: org.jboss.ide.eclipse.as.management.as7 has inconsistent package naming
by Andre Dietisheim (JIRA)
AS7: org.jboss.ide.eclipse.as.management.as7 has inconsistent package naming
----------------------------------------------------------------------------
Key: JBIDE-9500
URL: https://issues.jboss.org/browse/JBIDE-9500
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS
Affects Versions: 3.3.0.M3
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.M3
The plugin org.jboss.ide.eclipse.as.management.as7 does not comply to the general eclipse rule where internal package are not exported whereas non-internal packages are exported. We need to correct this.
Furthermore the internal marker appears in the wrong location in the naming scheme. It is called org.jboss.ide.eclipse.as.management.as7.internal whereas it should be called org.jboss.ide.eclipse.as.internal.management.as7
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (JBIDE-9256) Content assist gets "stuck" on JSF1
by Val Blant (JIRA)
Content assist gets "stuck" on JSF1
-----------------------------------
Key: JBIDE-9256
URL: https://issues.jboss.org/browse/JBIDE-9256
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.2.0.Final
Reporter: Val Blant
Assignee: Alexey Kazakov
Here are the steps that caused the bug to manifest:
# Installed JBoss Tools into Eclipse from the update site
# Restarted Eclipse. Jboss Tools noticed my existing web project and hooked up to it.
# *At this point I had correctly working JSF2 content assist in my XHTML files*
# Used Git to switch to a JSF1 branch and used the same Eclipse workspace to work on that (Refreshed the workspace after the switch, w/o restarting Eclipse)
# Used Git again to switch back to JSF2 branch
At this point JBoss Tools no longer provided me with content assist for JSF2 tags. It kept giving suggestions for JSF1. Restarting Eclipse or cleaning the workspace had no effect.
In order to fix the problem I had to do the following:
# Close Eclipse
# Delete all _org.jboss.tools.*_ directories from _.metadata/.plugins_
# _eclipse -clean_
After that JBoss Tools provides proper JSF2 content assist again, so this looks like a caching bug.
My workspace is setup with:
* Eclipse Helios
* JBoss Tools 3.2.0.v20110215-1535-H41-GA
My JSF1 branch contains these libraries under _WEB-INF/lib_ and included in project build path:
* myfaces-api-1.2.4.jar
* myfaces-impl-1.2.4.jar
* jsf-facelets-1.1.14.jar
* richfaces-api-3.2.2.GA.jar
* richfaces-impl-3.2.2.GA.jar
* richfaces-ui-3.2.2.GA.jar
For JSF2 branch, the libraries are:
* jsf-api-2.1.2.jar
* jsf-impl-2.1.2.jar
* richfaces-core-api-4.0.0.Final.jar
* richfaces-core-impl-4.0.0.Final.jar
* richfaces-components-api-4.0.0.Final.jar
* richfaces-components-ui-4.0.0.Final.jar
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (JBIDE-830) JSF support: linked folders
by Petr Lindovsky (JIRA)
JSF support: linked folders
---------------------------
Key: JBIDE-830
URL: http://jira.jboss.com/jira/browse/JBIDE-830
Project: JBoss Tools
Issue Type: Bug
Affects Versions: 2.0.0.Beta3
Environment: Windows XP
Reporter: Petr Lindovsky
I have a Web project (originally developed in another IDE) where the META-INF and WEB-INF directories are located directly under the root of the project (e.g. next to src).
So I can't take the project root as the web content directory. To make this work with Europa, I created a new WebConent directory under the root and added folder links there pointing to the existing META-INF and WEB-INF. This now works in Europa.
Is it possible to add RedHat JSF support to this? This wizard doesn't seem to take this into account.
I created a project where you can see the problem: It works in Europa (you can use Export > WAR file and Run As > Run On Server) but I don't know hat to make it work with the RedHat JSF support.
(Note: I used absolute paths in the links in the project; in reality we used path variables to enable sharing.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month