[ https://jira.jboss.org/jira/browse/JBIDE-4443?page=com.atlassian.jira.plu... ] Jeff Wexler updated JBIDE-4443: ------------------------------- Description: EAR Seam project running with Seam 2.1.2.CR ok. Changed Seam runtime in Seam Settings of Properties for the project from jboss-seam-2.1.2.CR2 to jboss-seam-2.1.2.GA. After starting JBoss AS, [ServletContextListener] Welcome to Seam 2.1.2.CR2 is still written to the log instead of the new seam version. By the way, this was also the case when upgraded from Seam 2.1.1.GA to Seam 2.1.2.CR2. I ended up creating a new Seam Project with the 2.1.2.GA setting and then manually copied the files into the new project from the old Seam 2.1.1.GA project in Eclipse in order to force the upgrade. Looks like this still necessary for 2.1.2.CR2 to 2.1.2.GA due to this bug. was: EAR Seam project running with Seam 2.1.2.CR ok. Changed Seam runtime in Seam Settings of Properties for the project from jboss-seam-2.1.2.CR2 to jboss-seam-2.1.2.GA. After starting JBoss AS, [ServletContextListener] Welcome to Seam 2.1.2.CR2 is still written to the log instead of the new seam version. By the way, this was also the case when upgraded from Seam 2.1.1.GA to Seam 2.1.2.GA. I ended up creating a new Seam Project with the 2.1.2.GA setting and then manually copied the files into the new project from the old Seam 2.1.1 project in Eclipse in order to force the upgrade. Looks like this still necessary for 2.1.2.CR2 to 2.1.2.GA due to this bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4443?page=com.atlassian.jira.plu... ] Max Rydahl Andersen resolved JBIDE-4443. ---------------------------------------- Resolution: Rejected Open Project preferences > Facets > change seam version here and we will do our best attempt on updating libs. The proper solution for this is though to remove the need for us to handle any libs and delegate it to something like ivy or maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira