[
https://issues.apache.org/jira/browse/ORCHESTRA-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786813#action_12786813
]
Leonardo Uribe commented on ORCHESTRA-45:
-----------------------------------------
Actually, in orchestra we have in trunk 3 modules:
core
core12
core20
It follows the same strategy as tomahawk core12. In fact, there is no a full
branch as in myfaces core or trinidad, just a submodule that takes all code
that does not change from its previous version and add the files that changes
and compiles everything.
In jsf 2.0 there are two points to take into account:
- TagHandler hierarchy changes
- New Wrappers.
The second is not critical but the first one is, so if you use orchestra12 with
jsf 2.0, all associated code related with ConverterTagHandler will not work.
Note also that for release any jar file we need at least one pom.xml file (we
can't use maven profiles to execute the same module multiple times without
create multiple poms). Also, each version has a different set of dependencies.
The good about the solution committed is that if you fix something in core not
related to ConverterTagHandler class or new wrappers, with just one commit it
will be on core12 and core20.
The only drawback about this strategy is the information related to svn. Since
you create new files in core12 and core20, to look the full history of a file
you have to look the file on each module.
> Support for JSF 2.0
> -------------------
>
> Key: ORCHESTRA-45
> URL: https://issues.apache.org/jira/browse/ORCHESTRA-45
> Project: MyFaces Orchestra
> Issue Type: Improvement
> Components: FrameworkAdapter
> Affects Versions: 1.3.1
> Reporter: Martin Marinschek
> Assignee: Leonardo Uribe
> Fix For: 1.4
>
> Attachments: jsf20upgrade.patch
>
>
> Orchestra should support JSF 2.0. The supplied patch changes the decorators
> in Orchestra to allow this, however, the patch is not backwards compatible
> with the 1.2/1.1 version (and contrary to supporting both 1.1 and 1.2 in one
> version, this is not possible with 2.0 anymore, as the interfaces have new
> methods which in turn have parameters/return types which are only available
> in JSF 2.0). The question will be how we will be able to continue. I see two
> options:
> a) a branch, and two independent releases
> b) adding a common JSF 1.2 compatibility library, which would allow to a
> certain extent to mimick basic JSF 2.0 infrastructure (it would not try to
> reimplement features from 2.0, however)
> I will also post this question to the MyFaces mailing-list, and we will see
> how to proceed from here.
> regards,
> Martin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
