You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Will Glass-Husain <wg...@gmail.com> on 2007/10/07 03:02:06 UTC
Re: XmlGen Ant Task
Hi,
Philippe sent me a personal note about this, since I am nominally the Texen
leader. (listed on JIRA).
I finally had a chance to look at XMLGen. I second Nathan's comments of a
few weeks ago. Looks like a cool utility, adds nice features to Texen.
It's great to see Philippe's enthusiasm and interest in Texen. I'd be
supportive of adding it in to Texen eventually.
I think the stumbling block is not technical but community. Texen is a
semi-dormant project. It's used by other libraries (notably Torque) so we
keep it around. If we add code into the project with a developer who ends
up being absent, it's a hassle for the rest of us.
So, Philippe -- interested in joining the Texen community? Suggest a few
patches, add unit tests, clean the project up. (There's about 8 open issues
right now). Answer any questions that come up on velocity-user. Do that
for a while and I'll support adding XMLGen into Texen on the assumption that
we'll be able to actively support it.
Thanks again for sharing this with the rest of us. In the meantime I'm glad
to see it's on the Powered by Velocity page.
Best, WILL
On 9/20/07, Nathan Bubna <nb...@gmail.com> wrote:
>
> On 9/20/07, Philippe Collignon <ph...@starobject.com> wrote:
> > Hi,
> >
> > I have just released an Ant task to generate code from XML files
> > and Velocity templates called XmlGen.
> >
> > http://xmlgen.sourceforge.net
> >
> > XmlGen makes XML nodes available to the Velocity template.
> > You can access XML elements by name, get their attributes value,
> > select some nodes with an XPath expression or loop on an element list
> ...
> >
> > XmlGen is and extension of Velocity Texen Ant Task.
>
> The documentation for this looks great! How does this compare to
> other xml-generation/transformation Velocity projects (namely DVSL and
> Anakia). Not that there isn't room for more, there always is; i'm
> just curious how you think it compares.
>
> > Could anybody tell me if this could take part as a contribution
> > to velocity project ? Who should I contact ? What are the
> > requirements ?
>
> If it's a large codebase or is intended to be a separate project (as
> opposed to an enhancement to an existing project), then it would have
> to go through the incubator:
> http://apache.org/foundation/how-it-works.html#incubator
>
> If it could be refactored to be just a patch(es) to enhance Texen,
> then i think you would just need to open a JIRA issue and attach the
> files there. Of course, then there's the question of eventually
> getting you commit access so that you can work on it directly, so we
> don't always have to commit your patches for you. For that to happen,
> we'd want to see evidence that you'll stick around (not just dump code
> once and disappear) and help out on the mailing lists. So, more than
> anything it's a matter of seeing comittment over time (we're talking
> months, not weeks). The reason for the high standard is that
> abandoned code becomes a weight on the rest of the project(s) and that
> commit access to one Velocity project means access to all of them.
>
> In any case, you should definitely announce your project on these
> lists (as you've done), add some links to it on the wiki (like the
> PoweredBy page and anywhere else that seems relevant), and generally
> promote connection between XmlGen and Velocity.
>
> > Philippe
> >
> > --
> >
> >
> > Philippe Collignon
> > IT Consultant
> > Starobject S.A.
> > Rue Principale, 56
> > L-5367 Schuttrange
> > Luxembourg
> > +352621312040
> > philippe.collignon@starobject.com
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> > For additional commands, e-mail: dev-help@velocity.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com
Re: XmlGen Ant Task
Posted by Will Glass-Husain <wg...@gmail.com>.
Hey, that's terrific. Ask questions on the list as you need to. Let the
rest of us know how we can help out.
WILL
On 10/8/07, Philippe Collignon <ph...@starobject.com> wrote:
>
> Hello,
>
> You are right, the stumbling block is community. I'll first download
> the source of Texen and look at Jira issues to see how I can help.
> XmlGen can live on its side for now.
>
> Regards,
> Philippe
>
> Will Glass-Husain wrote:
> > Hi,
> >
> > Philippe sent me a personal note about this, since I am nominally the
> Texen
> > leader. (listed on JIRA).
> >
> > I finally had a chance to look at XMLGen. I second Nathan's comments of
> a
> > few weeks ago. Looks like a cool utility, adds nice features to Texen.
> > It's great to see Philippe's enthusiasm and interest in Texen. I'd be
> > supportive of adding it in to Texen eventually.
> >
> > I think the stumbling block is not technical but community. Texen is a
> > semi-dormant project. It's used by other libraries (notably Torque) so
> we
> > keep it around. If we add code into the project with a developer who
> ends
> > up being absent, it's a hassle for the rest of us.
> >
> > So, Philippe -- interested in joining the Texen community? Suggest a
> few
> > patches, add unit tests, clean the project up. (There's about 8 open
> issues
> > right now). Answer any questions that come up on velocity-user. Do
> that
> > for a while and I'll support adding XMLGen into Texen on the assumption
> that
> > we'll be able to actively support it.
> >
> > Thanks again for sharing this with the rest of us. In the meantime I'm
> glad
> > to see it's on the Powered by Velocity page.
> >
> > Best, WILL
> >
> >
> >
> >
> >
> > On 9/20/07, Nathan Bubna <nb...@gmail.com> wrote:
> >
> >> On 9/20/07, Philippe Collignon <ph...@starobject.com> wrote:
> >>
> >>> Hi,
> >>>
> >>> I have just released an Ant task to generate code from XML files
> >>> and Velocity templates called XmlGen.
> >>>
> >>> http://xmlgen.sourceforge.net
> >>>
> >>> XmlGen makes XML nodes available to the Velocity template.
> >>> You can access XML elements by name, get their attributes value,
> >>> select some nodes with an XPath expression or loop on an element list
> >>>
> >> ...
> >>
> >>> XmlGen is and extension of Velocity Texen Ant Task.
> >>>
> >> The documentation for this looks great! How does this compare to
> >> other xml-generation/transformation Velocity projects (namely DVSL and
> >> Anakia). Not that there isn't room for more, there always is; i'm
> >> just curious how you think it compares.
> >>
> >>
> >>> Could anybody tell me if this could take part as a contribution
> >>> to velocity project ? Who should I contact ? What are the
> >>> requirements ?
> >>>
> >> If it's a large codebase or is intended to be a separate project (as
> >> opposed to an enhancement to an existing project), then it would have
> >> to go through the incubator:
> >> http://apache.org/foundation/how-it-works.html#incubator
> >>
> >> If it could be refactored to be just a patch(es) to enhance Texen,
> >> then i think you would just need to open a JIRA issue and attach the
> >> files there. Of course, then there's the question of eventually
> >> getting you commit access so that you can work on it directly, so we
> >> don't always have to commit your patches for you. For that to happen,
> >> we'd want to see evidence that you'll stick around (not just dump code
> >> once and disappear) and help out on the mailing lists. So, more than
> >> anything it's a matter of seeing comittment over time (we're talking
> >> months, not weeks). The reason for the high standard is that
> >> abandoned code becomes a weight on the rest of the project(s) and that
> >> commit access to one Velocity project means access to all of them.
> >>
> >> In any case, you should definitely announce your project on these
> >> lists (as you've done), add some links to it on the wiki (like the
> >> PoweredBy page and anywhere else that seems relevant), and generally
> >> promote connection between XmlGen and Velocity.
> >>
> >>
> >>> Philippe
> >>>
> >>> --
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> >>> For additional commands, e-mail: dev-help@velocity.apache.org
> >>>
> >>>
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> >> For additional commands, e-mail: dev-help@velocity.apache.org
> >>
> >>
> >>
> >
> >
> >
>
>
> --
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com
Re: XmlGen Ant Task
Posted by Philippe Collignon <ph...@starobject.com>.
Hello,
You are right, the stumbling block is community. I'll first download
the source of Texen and look at Jira issues to see how I can help.
XmlGen can live on its side for now.
Regards,
Philippe
Will Glass-Husain wrote:
> Hi,
>
> Philippe sent me a personal note about this, since I am nominally the Texen
> leader. (listed on JIRA).
>
> I finally had a chance to look at XMLGen. I second Nathan's comments of a
> few weeks ago. Looks like a cool utility, adds nice features to Texen.
> It's great to see Philippe's enthusiasm and interest in Texen. I'd be
> supportive of adding it in to Texen eventually.
>
> I think the stumbling block is not technical but community. Texen is a
> semi-dormant project. It's used by other libraries (notably Torque) so we
> keep it around. If we add code into the project with a developer who ends
> up being absent, it's a hassle for the rest of us.
>
> So, Philippe -- interested in joining the Texen community? Suggest a few
> patches, add unit tests, clean the project up. (There's about 8 open issues
> right now). Answer any questions that come up on velocity-user. Do that
> for a while and I'll support adding XMLGen into Texen on the assumption that
> we'll be able to actively support it.
>
> Thanks again for sharing this with the rest of us. In the meantime I'm glad
> to see it's on the Powered by Velocity page.
>
> Best, WILL
>
>
>
>
>
> On 9/20/07, Nathan Bubna <nb...@gmail.com> wrote:
>
>> On 9/20/07, Philippe Collignon <ph...@starobject.com> wrote:
>>
>>> Hi,
>>>
>>> I have just released an Ant task to generate code from XML files
>>> and Velocity templates called XmlGen.
>>>
>>> http://xmlgen.sourceforge.net
>>>
>>> XmlGen makes XML nodes available to the Velocity template.
>>> You can access XML elements by name, get their attributes value,
>>> select some nodes with an XPath expression or loop on an element list
>>>
>> ...
>>
>>> XmlGen is and extension of Velocity Texen Ant Task.
>>>
>> The documentation for this looks great! How does this compare to
>> other xml-generation/transformation Velocity projects (namely DVSL and
>> Anakia). Not that there isn't room for more, there always is; i'm
>> just curious how you think it compares.
>>
>>
>>> Could anybody tell me if this could take part as a contribution
>>> to velocity project ? Who should I contact ? What are the
>>> requirements ?
>>>
>> If it's a large codebase or is intended to be a separate project (as
>> opposed to an enhancement to an existing project), then it would have
>> to go through the incubator:
>> http://apache.org/foundation/how-it-works.html#incubator
>>
>> If it could be refactored to be just a patch(es) to enhance Texen,
>> then i think you would just need to open a JIRA issue and attach the
>> files there. Of course, then there's the question of eventually
>> getting you commit access so that you can work on it directly, so we
>> don't always have to commit your patches for you. For that to happen,
>> we'd want to see evidence that you'll stick around (not just dump code
>> once and disappear) and help out on the mailing lists. So, more than
>> anything it's a matter of seeing comittment over time (we're talking
>> months, not weeks). The reason for the high standard is that
>> abandoned code becomes a weight on the rest of the project(s) and that
>> commit access to one Velocity project means access to all of them.
>>
>> In any case, you should definitely announce your project on these
>> lists (as you've done), add some links to it on the wiki (like the
>> PoweredBy page and anywhere else that seems relevant), and generally
>> promote connection between XmlGen and Velocity.
>>
>>
>>> Philippe
>>>
>>> --
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>>> For additional commands, e-mail: dev-help@velocity.apache.org
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
>> For additional commands, e-mail: dev-help@velocity.apache.org
>>
>>
>>
>
>
>
--
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org