[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4443) Project seam properties change to new seam version error. Old seam version listed in JBoss AS log.

[Alexey Kazakov (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Kazakov updated JBIDE-4443:
----------------------------------

       Issue Type: Feature Request  (was: Bug)
    Fix Version/s: LATER
         Assignee: Alexey Kazakov


Seam Runtime is used only in Seam Wizards (New Seam Action/Conversation/...). It doesn't affect project's libs.

> Project seam properties change to new seam version error. Old seam version listed in JBoss AS log.
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-4443
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4443
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: Seam
>    Affects Versions: 3.0.1.GA
>         Environment: Upgrade from Seam 2.1.2.CR2 to 2.1.2.GA.  JBoss AS 5.1.0.GA. Eclipse 3.4.2 Build Id: M20090211-1700. JBoss Tools 3.0.1.GA. Windows 2003 Server.
>            Reporter: Jeff Wexler
>            Assignee: Alexey Kazakov
>             Fix For: LATER
>
>
> 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.

-- 
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