[xwiki-devs] XWiki Application Merger Maven Plugin
Hi Guys I updated my Maven Plugin that takes Code / Content of Pages and Objects and places it into the XML files which then can be packed up into a XAR. The plugin uses the same File Name Pattern as the IntelliJ Plugin for the Content Files: - Page: <Page Name>.<Extension> - Object: <Page Name>.<Class Space>.<Class Name>.<Object Number>.<Property Name>.<Extension> The Content Files can contain anything like Velocity, Groovy, JavaScript, CSS etc. There can be multiple Content Files per target XML file but the XML file must be present in the source directory. If there is not Content File the XML file will be written to the target file w/o transformation otherwise any Page Content or Object Property will be replaced with the content of the Content File. The XML files can be taken straight from an export or from the source application w/o any adjustments. Let me know if that would be of some help for XWiki. -Andy
On Sun, Jan 10, 2010 at 01:09, Andreas Schaefer <[email protected]> wrote:
Hi Guys
I updated my Maven Plugin that takes Code / Content of Pages and Objects and places it into the XML files which then can be packed up into a XAR.
The plugin uses the same File Name Pattern as the IntelliJ Plugin for the Content Files:
- Page: <Page Name>.<Extension>
- Object: <Page Name>.<Class Space>.<Class Name>.<Object Number>.<Property Name>.<Extension>
The Content Files can contain anything like Velocity, Groovy, JavaScript, CSS etc. There can be multiple Content Files per target XML file but the XML file must be present in the source directory. If there is not Content File the XML file will be written to the target file w/o transformation otherwise any Page Content or Object Property will be replaced with the content of the Content File. The XML files can be taken straight from an export or from the source application w/o any adjustments.
Let me know if that would be of some help for XWiki.
Seems very useful for groovy application (thinking of l10n app for example). It's a good candidate for http://svn.xwiki.org/svnroot/xwiki/contrib/projects/ unless you already have everything you need to manage it ?
-Andy _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
Isn't this an extension of the existing plugin who's authors are the xwiki team? paul Le 11-janv.-10 à 11:18, Thomas Mortagne a écrit :
On Sun, Jan 10, 2010 at 01:09, Andreas Schaefer <[email protected]> wrote:
Hi Guys
I updated my Maven Plugin that takes Code / Content of Pages and Objects and places it into the XML files which then can be packed up into a XAR.
The plugin uses the same File Name Pattern as the IntelliJ Plugin for the Content Files:
- Page: <Page Name>.<Extension>
- Object: <Page Name>.<Class Space>.<Class Name>.<Object Number>.<Property Name>.<Extension>
The Content Files can contain anything like Velocity, Groovy, JavaScript, CSS etc. There can be multiple Content Files per target XML file but the XML file must be present in the source directory. If there is not Content File the XML file will be written to the target file w/o transformation otherwise any Page Content or Object Property will be replaced with the content of the Content File. The XML files can be taken straight from an export or from the source application w/o any adjustments.
Let me know if that would be of some help for XWiki.
Seems very useful for groovy application (thinking of l10n app for example).
It's a good candidate for http://svn.xwiki.org/svnroot/xwiki/contrib/projects/ unless you already have everything you need to manage it ?
-Andy _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi Paul I am not quite sure which plugin you are referring to. This Maven Plugin is the Maven version of the IntelliJ plugin I wrote with more or less the same purpose. I would use the IntelliJ plugin during development and the Maven Plugin when I want to test a release or release the application. Cheers - Andy On Jan 11, 2010, at 2:43 AM, Paul Libbrecht wrote:
Isn't this an extension of the existing plugin who's authors are the xwiki team?
paul
Le 11-janv.-10 à 11:18, Thomas Mortagne a écrit :
On Sun, Jan 10, 2010 at 01:09, Andreas Schaefer <[email protected]> wrote:
Hi Guys
I updated my Maven Plugin that takes Code / Content of Pages and Objects and places it into the XML files which then can be packed up into a XAR.
The plugin uses the same File Name Pattern as the IntelliJ Plugin for the Content Files:
- Page: <Page Name>.<Extension>
- Object: <Page Name>.<Class Space>.<Class Name>.<Object Number>.<Property Name>.<Extension>
The Content Files can contain anything like Velocity, Groovy, JavaScript, CSS etc. There can be multiple Content Files per target XML file but the XML file must be present in the source directory. If there is not Content File the XML file will be written to the target file w/o transformation otherwise any Page Content or Object Property will be replaced with the content of the Content File. The XML files can be taken straight from an export or from the source application w/o any adjustments.
Let me know if that would be of some help for XWiki.
Seems very useful for groovy application (thinking of l10n app for example).
It's a good candidate for http://svn.xwiki.org/svnroot/xwiki/contrib/projects/ unless you already have everything you need to manage it ?
-Andy _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Le 11-janv.-10 à 17:26, Andreas Schaefer a écrit :
I am not quite sure which plugin you are referring to. This Maven Plugin is the Maven version of the IntelliJ plugin I wrote with more or less the same purpose.
I know that. Is it not a complement or a patch to the maven xar plugin? I would have thought so.
I would use the IntelliJ plugin during development and the Maven Plugin when I want to test a release or release the application.
sure. paul
Hi Paul Yes, it could be. This could become another goal on the XAR plugin I would think. I have no problem to contribute that code to XWiki. Question to contributors: Should this Plugin remain standalone or added as another goal to the XAR plugin ? The plugin can be seen as a preparation step for XAR plugin where the content is kept separate from XML file so that IDEs language support can be used. Thanks - Andy BTW I am just wondering why the default export (Admin -> Export) is exporting the content XML encoded and not within a CDATA construct. A CDATA construct would make the content or code easier to read but it would prevent the user from using "]]>" within the content. On Jan 11, 2010, at 2:43 PM, Paul Libbrecht wrote:
Le 11-janv.-10 à 17:26, Andreas Schaefer a écrit :
I am not quite sure which plugin you are referring to. This Maven Plugin is the Maven version of the IntelliJ plugin I wrote with more or less the same purpose.
I know that. Is it not a complement or a patch to the maven xar plugin? I would have thought so.
I would use the IntelliJ plugin during development and the Maven Plugin when I want to test a release or release the application.
sure.
paul _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Tue, Jan 12, 2010 at 00:40, Andreas Schaefer <[email protected]> wrote:
Hi Paul
Yes, it could be. This could become another goal on the XAR plugin I would think. I have no problem to contribute that code to XWiki.
Question to contributors:
Should this Plugin remain standalone or added as another goal to the XAR plugin ?
The plugin can be seen as a preparation step for XAR plugin where the content is kept separate from XML file so that IDEs language support can be used.
Thanks - Andy
BTW I am just wondering why the default export (Admin -> Export) is exporting the content XML encoded and not within a CDATA construct. A CDATA construct would make the content or code easier to read but it would prevent the user from using "]]>" within the content.
I think the first reason would be that the code is using a XML writer and let it handle escaping the way it want and did not tough a lot about that. Also if CDATA make impossible to put any data (are you sure ?) it would be a blocker for me anyway.
On Jan 11, 2010, at 2:43 PM, Paul Libbrecht wrote:
Le 11-janv.-10 à 17:26, Andreas Schaefer a écrit :
I am not quite sure which plugin you are referring to. This Maven Plugin is the Maven version of the IntelliJ plugin I wrote with more or less the same purpose.
I know that. Is it not a complement or a patch to the maven xar plugin? I would have thought so.
I would use the IntelliJ plugin during development and the Maven Plugin when I want to test a release or release the application.
sure.
paul _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
Le 12-janv.-10 à 11:13, Thomas Mortagne a écrit :
Should this Plugin remain standalone or added as another goal to the XAR plugin ?
I licensing is appropriate (all LGPL right) I would vote for a xar plugin extension. What do the XAR plugin writers think?
The plugin can be seen as a preparation step for XAR plugin where the content is kept separate from XML file so that IDEs language support can be used.
BTW I am just wondering why the default export (Admin -> Export) is exporting the content XML encoded and not within a CDATA construct. A CDATA construct would make the content or code easier to read but it would prevent the user from using "]]>" within the content.
I think the first reason would be that the code is using a XML writer and let it handle escaping the way it want and did not tough a lot about that. Also if CDATA make impossible to put any data (are you sure ?) it would be a blocker for me anyway.
why not the following: - if the content contains ]]> use the normal procedure - if the content does not (99% of the cases) use a CDATA XML-wise it's equivalent. paul
Hi I uploaded the Source Code for the XWiki Content Merger Maven Plugin onto this JIRA ticket: http://jira.xwiki.org/jira/browse/XE-590 Please let me know if there is anything I can do to promote this maven plugin. I used it to deploy my GBlog from the local dev box onto my production server without any problems and without having lost, missed or screwed up anything. Cheers - Andy On Jan 12, 2010, at 2:34 AM, Paul Libbrecht wrote:
Le 12-janv.-10 à 11:13, Thomas Mortagne a écrit :
Should this Plugin remain standalone or added as another goal to the XAR plugin ?
I licensing is appropriate (all LGPL right) I would vote for a xar plugin extension.
What do the XAR plugin writers think?
The plugin can be seen as a preparation step for XAR plugin where the content is kept separate from XML file so that IDEs language support can be used.
BTW I am just wondering why the default export (Admin -> Export) is exporting the content XML encoded and not within a CDATA construct. A CDATA construct would make the content or code easier to read but it would prevent the user from using "]]>" within the content.
I think the first reason would be that the code is using a XML writer and let it handle escaping the way it want and did not tough a lot about that. Also if CDATA make impossible to put any data (are you sure ?) it would be a blocker for me anyway.
why not the following: - if the content contains ]]> use the normal procedure - if the content does not (99% of the cases) use a CDATA XML-wise it's equivalent.
paul _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (3)
-
Andreas Schaefer -
Paul Libbrecht -
Thomas Mortagne