[
http://jira.jboss.com/jira/browse/JBIDE-1320?page=comments#action_12387799 ]
Denis Golovin commented on JBIDE-1320:
--------------------------------------
2. I looked through the code and found that template for ejb project has hardcoded
classpath container
org.jboss.ide.eclipse.as.classpath.core.runtime.ProjectRuntimeInitializer :( is there any
way to get that container for selected runtime. As example, Tomcat 6 has
org.eclipse.jst.server.core.container/org.eclipse.jst.server.tomcat.runtimeTarget path
forclasspath container, default adapter for JBoss AS
org.eclipse.jst.server.core.container/org.eclipse.jst.server.generic.runtimeTarget. So I
would obtain it from Dynamic web Project by first path segment
org.eclipse.jst.server.core.container, but there is no such segment in our JBoss adapter.
If we want just create project and it doesn't matter will it compiled without errors
and works after deployment, list is not necessary
seam facet is fixed onto our server adapter
-------------------------------------------
Key: JBIDE-1320
URL:
http://jira.jboss.com/jira/browse/JBIDE-1320
Project: JBoss Tools
Issue Type: Task
Components: Seam
Affects Versions: 2.0.0.CR1
Reporter: Max Andersen
Fix For: 2.0.0.GA, 2.0.1, 2.1
Is there anything that prevent us from removing that fixation ?
Users should be allowed to deploy to other servers...
Lets document here what needs to be done for this
--
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