Issue created https://jira.jboss.org/jira/browse/JBIDE-4195
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4225944#4225944
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4225944
___
I have committed changes to versions 3.0.1 and 3.1.0.
(see JIRA issue
https://jira.jboss.org/jira/browse/JBIDE-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel)
Kragoth, please try your project with next nightly build for JBoss Tools 3.0.1.
View the original post :
I have reproduced the problem by creating an annotation type in Java sources
and annotating it:
@Deprecated
public @interface MyAnnotation {
}
Please check if you have annotation types. If this is the case, try this
workaround: move annotation types to a separate project, build a jar of it,
Web project should be dependent on EJB project.
Open properties dialog for web project.
Select section Java EE Module dependencies.
Check in the list EJB project.
When dependency is created, it is saved in
/.settings/org.eclipse.wst.common.component file as
dependent-module
It looks like you have set all required references, but nevertheless, could you
please check once more
1) In web project, file .settings\org.jboss.tools.seam.core.prefs contains lines
seam.ear.project=%ear project name%
seam.ejb.project=%ejb project name%
2) In ear project, file
Please, create an issue in jira.jboss.org for JBoss Tools project, and attach
the project.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4194386#4194386
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4194386
You can dnd your actual tld to the palette and put in the dialog
'Richfaces-3.2.0' for the new group name. After that open 'Show/Hide' dialog
and mark the old 'Richfaces' group as hidden.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4143825#4143825
Reply to
what we should do with our existing
org.jboss.tools.jst.web.xml project files
Before JBoss Tools 2.0.1, if this file gets wrong because of wrong absolute
paths, the solution was to remove it, remove line org.jboss.tools.jsf.jsfnature
in .project file, restart Eclipse and execute JBoss
