[
https://issues.jboss.org/browse/WELD-984?page=com.atlassian.jira.plugin.s...
]
Geoffrey De Smet edited comment on WELD-984 at 10/4/11 12:01 PM:
-----------------------------------------------------------------
@Max Spring hardly has them.
Maybe it's because they do a good amount of effort to take the pain away from the
users: they detect which appserver-version it is and do the specific stuff then. They even
detect the jdk version for certain things. Weld-servlet already has a bit of code like
this, to enable servlet injection, but there's still a lot of stuff that needs to be
done by the users to make a war portable.
was (Author: ge0ffrey):
@Max Spring hardly has them.
Maybe it's because they do a good amount of effort to take the pain away from the
users (so the detect which appserver-version it is and do the specific stuff there). They
even detect the jdk version for certain things.
Weld should not require application server specific changes to a war
--------------------------------------------------------------------
Key: WELD-984
URL:
https://issues.jboss.org/browse/WELD-984
Project: Weld
Issue Type: Feature Request
Reporter: Geoffrey De Smet
It should especially not require different content in the same file: that makes it almost
impossible to solve.
"Maven profiles" are NOT a solution: you should only build once during a
release (and on hudson for every commit).
The build output shouldn't differ based on the profile or build platform (strong
maven guideline).
Furthermore, it should be possible to do exploded war deployments straight from the IDE
to different appservers (jboss 7, jetty, tomcat) without having to run maven.
Similar for arquillian tests.
See dependent issues for the specific things that cause problems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira