[
https://issues.apache.org/jira/browse/TRINIDAD-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001279#comment-13001279
]
Leonardo Uribe commented on TRINIDAD-1409:
------------------------------------------
It simply generate a myfaces-metadata.xml combining the information on
trinidad-build xml files, the metadata from myfaces-api jar and any annotation
available on trinidad-api source code. I would like to have a replacement from
trinidad plugin, but I understand maybe this is a "big jump" that could
introduce bugs. Personally I think this is something that it is worth to do it,
because myfaces-builder-plugin code is stable and well tested and that strategy
is one of the things that makes myfaces core easier to maintain in the long
term. Long time ago I did some work related to that, creating template files to
generate the same files trinidad plugin does, but with velocity, so I think it
is possible (really it does not requires too much effort) to migrate existing
trinidad components, but before that we need a patch like the one proposed here
to "open" the alternative. I have never committed the code, because in that
time we didn't tested myfaces-builder-plugin too much (only a few versions were
available).
In few words, the advantage of have this feature is allow do things like create
trinidad components using myfaces-builder-plugin strategy, but allow keep using
trinidad plugin.
> Add myfaces-builder-annotations to trinidad trunk 1.2.x, so trinidad jars
> could have myfaces-metadata.xml, making possible use builder plugin on
> trinidad sandbox
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TRINIDAD-1409
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1409
> Project: MyFaces Trinidad
> Issue Type: Task
> Components: Build, Components
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Attachments: TRINIDAD-1409-v1-maven-faces-plugin.patch,
> TRINIDAD-1409-v1-trinidad.patch,
> TRINIDAD-1409-v2-myfaces-builder-plugin.patch, TRINIDAD-1409-v2-trinidad.patch
>
>
> The first step to use myfaces-builder-plugin on trinidad is add annotations
> on trinidad code and try use it on trinidad-sanbox. Please note that the
> change proposed here does not change the generation procedure using trinidad
> maven-faces-plugin (includes component classes, tag classes and xml config
> files), just add the necessary information to generate myfaces-metadata.xml
> file, making it easier in the future to change the build procedure.
> To do that, the idea is change maven-faces-plugin, adding builder plugin
> annotations when generating component files and add the necessary information
> to non generated component files.
> I'll add the advance on this work here, but before commit something it is
> better ask trinidad community about it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
