[
http://jira.jboss.com/jira/browse/JBIDE-1320?page=comments#action_12387683 ]
Max Andersen commented on JBIDE-1320:
-------------------------------------
0. At first we should target JEE servers that will support the same (or mostly the same)
project setup (e.g. Glassfish)
1. I was trying to edit the sam core plugin.xml to not list any runtimes in hope that all
runtimes that would support the jst.* facets would work with it...is that not possible ?
do we really have to list all runtimes specifically to enable support for it ?
2. If we do 0 these should be ok - somethngs might not work outofthebox, like the
datasource setup.
3. yup
4. if they are JEE servers ....
5. if they are JEE servers ...
6. test project just depends on the ear/war so shouldn't need adjustements.
What I would like for the first iteration is that we don't prevent users from
selecting a runtime that supports all the other parts of the requirements; so users at
least could be able to try it out and then adjust their projects for any server specific
setup.
Next phase would then be to look into handling some of these server specific things, but
to do that we need to break up the monolithic server facet delegate and seam-gen as it is
today.
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