[ https://issues.jboss.org/browse/WELD-984?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen commented on WELD-984: ------------------------------------------ I agree with all of these - but these constraints are more problems of the appservers and not so much Weld specific are they ? -- 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

[ https://issues.jboss.org/browse/WELD-984?page=com.atlassian.jira.plugin.s... ] Geoffrey De Smet commented on WELD-984: --------------------------------------- @Max Spring doesn't have 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. -- 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

[ https://issues.jboss.org/browse/WELD-984?page=com.atlassian.jira.plugin.s... ] Geoffrey De Smet updated WELD-984: ---------------------------------- Description: 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), because you can only deploy 1 variant to nexus under a certain GAV. 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. was: 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