On 04-02-2009 15:03, Alexey Kazakov wrote:It depends on project. Our examples for Seam 2.0 seem to work well with Seam 2.1. But some custom projects could behave unexpectedly.Max Rydahl Andersen wrote:Ok, so the current version update ui is sufficient - it warns about other files might need changing, right ?Our editors will use XSD that is declared in XML. It doesn't depend on Facet or jars.
It would be nice feature but... there could be a problem to change Seam version and to have correct project then.Our tooling would still work, right ? the editor will look at the actual used XSD instead of the targeted version for the project correct ?
For example if user wants to update Seam from 2.0 to 2.1 it's not enough just to change Facet version.
We should at least update XSD's URIs.
But if user wants to change 2.0 to 1.2 then in order to have working project we should change a lot of things.
/max
Can we handle it?
Snjezana Peco wrote:Hi,
We could add yet another quick fix (Change Seam Version) that would serve to get the Project Facets property page. The user would be able to change seam facet version and Seam settings.
Do you agree?
Snjeza
Ok. after installing Seam 2.0.2, i see my installation. But what this mean? This example can't be run with 2.1.1 ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206744#4206744 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206744