myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Rivera (JIRA)" <>
Subject [jira] Commented: (MYFACES-1907) update myfaces-archetype-jsfcomponents to use myfaces-builder-plugin
Date Thu, 18 Sep 2008 03:57:44 GMT


Paul Rivera commented on MYFACES-1907:

Do you mean myfaces-builder-plugin 1.0.1?  Version 1.0.0 doesn't seem to exist and it is also
not in

I've attached a new patch (myfaces-archetype-jsfcomponents-MyFaces12-3.patch).  This uses
myfaces-builder-plugin 1.0.1.

Although, I had to add componentClass12.vm and tagClass12.vm to this archetype since myfaces-builder-plugin
1.0.1 still does not have them in its resources\META-INF folder unlike myfaces-builder-plugin
1.0.2-SNAPSHOT.  If these template files are not included, your build will fail.

Maybe we can modify this archetype again when myfaces-builder-plugin 1.0.2 is available.

> update myfaces-archetype-jsfcomponents to use myfaces-builder-plugin
> --------------------------------------------------------------------
>                 Key: MYFACES-1907
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Improvement
>            Reporter: Paul Rivera
>            Priority: Minor
>         Attachments: myfaces-archetype-jsfcomponents-MyFaces12-2.patch, myfaces-archetype-jsfcomponents-MyFaces12-3.patch,
myfaces-jsfcomponents-archetype-MyFaces12.patch, myfaces-jsfcomponents-archetype.patch
> myfaces-archetype-jsfcomponents needs to be updated to use myfaces-builder-plugin in
component authoring instead of the manual process.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message