You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vxquery.apache.org by Vinayak Borkar <vb...@yahoo.com> on 2009/09/29 10:17:18 UTC
VXQuery Website
Guys,
We need to put up the VXQuery website. Do you know what technologies we
could use to get that up? I know there is a wiki we could use. Is there
a different way we could build the site using traditional html?
Thanks,
Vinayak
Re: VXQuery Website
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Mon, Oct 5, 2009 at 8:35 AM, Vinayak Borkar <vb...@yahoo.com> wrote:
> I was thinking of moving away entirely from code generation using any
> out-of-band code generators. Instead, we could use Java annotations to
> generate the thinks we need, so we stay within Java-land as much as
> possible.
>
> Thoughts?
I am generally happy with annotations. However, they can become a
problem for performance. I try to use them at compile time, whereever
possible. Which brings us back to source code generation ... :-)
Jochen
--
Germanys national anthem is the most boring in the world - how telling!
Re: VXQuery Website
Posted by Vinayak Borkar <vb...@yahoo.com>.
Jochen,
I agree with you that XSLT for the task is overkill and excessively
complicated.
The kind of code generated is fairly simple.
I was thinking of moving away entirely from code generation using any
out-of-band code generators. Instead, we could use Java annotations to
generate the thinks we need, so we stay within Java-land as much as
possible.
Thoughts?
Vinayak
Jochen Wiedmann wrote:
> Hi, Vinayak,
>
> first of all, in the medium term, I personally find XSLT much too
> complicated. IMO, using a template system like FreeMarker or even a
> fully blown source generator framework like OpenArchitectureWare would
> be a much better solution. But that's for the medium term.
>
> For XSLT, there are a number of options:
>
> - Use the maven-antrun-plugin, in other words Ant. The easiest way to do so
> would be to move the generation stuff to a separate build.xml,
> which is configurated
> through some properties and invoke that from both the current build.xml and
> the Maven POM. This is the best solution as long as both Maven and Ant are
> in use.
> - Use the xml-maven-plugin, which is basically the Maven replacement for Ant's
> xslt task.
>
> Jochen
>
>
> On Sun, Oct 4, 2009 at 5:45 PM, Vinayak Borkar <vb...@yahoo.com> wrote:
>> Jochen,
>>
>> Do you know how we could use maven and continue to generate the .java files
>> currently generated by XSLT?
>>
>> Thanks,
>> Vinayak
>>
>>
>> Jochen Wiedmann wrote:
>>> On Sun, Oct 4, 2009 at 12:52 PM, Till Westmann <ti...@westmann.org> wrote:
>>>
>>>> Is this something we could achieve during this week?
>>> The build.xml is a little bit complex. I wouldn't expect to have a
>>> complete migration in one go. A partial migration is more than
>>> realistic.
>>>
>>>
>>>
>>>> Also, what would be the best thing for me to do to help (and not to step
>>>> on
>>>> your feet)?
>>> If you feel that you have some Maven know how (or even just if you'd
>>> like to learn it): Feel free to create an initial pom.xml to play
>>> with. Just make sure that you commit from time to time (and check for
>>> updates on the other hand).
>>>
>>> Jochen
>>>
>>>
>>>
>>
>
>
>
Re: VXQuery Website
Posted by Jochen Wiedmann <jo...@gmail.com>.
Hi, Vinayak,
first of all, in the medium term, I personally find XSLT much too
complicated. IMO, using a template system like FreeMarker or even a
fully blown source generator framework like OpenArchitectureWare would
be a much better solution. But that's for the medium term.
For XSLT, there are a number of options:
- Use the maven-antrun-plugin, in other words Ant. The easiest way to do so
would be to move the generation stuff to a separate build.xml,
which is configurated
through some properties and invoke that from both the current build.xml and
the Maven POM. This is the best solution as long as both Maven and Ant are
in use.
- Use the xml-maven-plugin, which is basically the Maven replacement for Ant's
xslt task.
Jochen
On Sun, Oct 4, 2009 at 5:45 PM, Vinayak Borkar <vb...@yahoo.com> wrote:
> Jochen,
>
> Do you know how we could use maven and continue to generate the .java files
> currently generated by XSLT?
>
> Thanks,
> Vinayak
>
>
> Jochen Wiedmann wrote:
>>
>> On Sun, Oct 4, 2009 at 12:52 PM, Till Westmann <ti...@westmann.org> wrote:
>>
>>> Is this something we could achieve during this week?
>>
>> The build.xml is a little bit complex. I wouldn't expect to have a
>> complete migration in one go. A partial migration is more than
>> realistic.
>>
>>
>>
>>> Also, what would be the best thing for me to do to help (and not to step
>>> on
>>> your feet)?
>>
>> If you feel that you have some Maven know how (or even just if you'd
>> like to learn it): Feel free to create an initial pom.xml to play
>> with. Just make sure that you commit from time to time (and check for
>> updates on the other hand).
>>
>> Jochen
>>
>>
>>
>
>
--
Germanys national anthem is the most boring in the world - how telling!
Re: VXQuery Website
Posted by Vinayak Borkar <vb...@yahoo.com>.
Jochen,
Do you know how we could use maven and continue to generate the .java
files currently generated by XSLT?
Thanks,
Vinayak
Jochen Wiedmann wrote:
> On Sun, Oct 4, 2009 at 12:52 PM, Till Westmann <ti...@westmann.org> wrote:
>
>> Is this something we could achieve during this week?
>
> The build.xml is a little bit complex. I wouldn't expect to have a
> complete migration in one go. A partial migration is more than
> realistic.
>
>
>
>> Also, what would be the best thing for me to do to help (and not to step on
>> your feet)?
>
> If you feel that you have some Maven know how (or even just if you'd
> like to learn it): Feel free to create an initial pom.xml to play
> with. Just make sure that you commit from time to time (and check for
> updates on the other hand).
>
> Jochen
>
>
>
Re: VXQuery Website
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Sun, Oct 4, 2009 at 12:52 PM, Till Westmann <ti...@westmann.org> wrote:
> Is this something we could achieve during this week?
The build.xml is a little bit complex. I wouldn't expect to have a
complete migration in one go. A partial migration is more than
realistic.
> Also, what would be the best thing for me to do to help (and not to step on
> your feet)?
If you feel that you have some Maven know how (or even just if you'd
like to learn it): Feel free to create an initial pom.xml to play
with. Just make sure that you commit from time to time (and check for
updates on the other hand).
Jochen
--
Germanys national anthem is the most boring in the world - how telling!
Re: VXQuery Website
Posted by Till Westmann <ti...@westmann.org>.
Hi Jochen,
that sounds really good.
Right now I especially like the part about the initial site, but I'm
quite sure that I'll come to appreciate the build system as well.
Do you have an idea how much effort it would be to get the project
into a state where we can build with maven?
Is this something we could achieve during this week? (I'm wondering
about this week, because I think that it would be good to show a sign
of life - both to attract more contribution and also for the next
status report.)
Is that feasible/realistic?
Also, what would be the best thing for me to do to help (and not to
step on your feet)?
Thanks,
Till
On Oct 3, 2009, at 6:21 PM, Vinayak Borkar wrote:
> Jochen,
>
> It would be great to use Maven as the build system. Please go ahead
> and make the changes :)
>
> Thanks for volunteering.
>
> Vinayak
>
> Jochen Wiedmann wrote:
>> Hi, Vinyak,
>> I *strongly* recommend to switch to Maven as the build system. This
>> will give you an initial site for free. Anything else can easily be
>> added. Another advantage will be that you get a build system which
>> adheres to the Apache policies automatically. (Don't underestimate,
>> it
>> can become quite burdensome to publish a release otherwise.)
>> I'd volunteer to change the sources accordingly, or at least to do
>> the
>> initial changes that are required to build the project using Maven.
>> Jochen
>> On Tue, Sep 29, 2009 at 10:17 AM, Vinayak Borkar <vb...@yahoo.com>
>> wrote:
>>> Guys,
>>>
>>>
>>> We need to put up the VXQuery website. Do you know what
>>> technologies we
>>> could use to get that up? I know there is a wiki we could use. Is
>>> there a
>>> different way we could build the site using traditional html?
>>>
>>> Thanks,
>>> Vinayak
>>>
Re: VXQuery Website
Posted by Vinayak Borkar <vb...@yahoo.com>.
Jochen,
It would be great to use Maven as the build system. Please go ahead and
make the changes :)
Thanks for volunteering.
Vinayak
Jochen Wiedmann wrote:
> Hi, Vinyak,
>
> I *strongly* recommend to switch to Maven as the build system. This
> will give you an initial site for free. Anything else can easily be
> added. Another advantage will be that you get a build system which
> adheres to the Apache policies automatically. (Don't underestimate, it
> can become quite burdensome to publish a release otherwise.)
>
> I'd volunteer to change the sources accordingly, or at least to do the
> initial changes that are required to build the project using Maven.
>
> Jochen
>
>
> On Tue, Sep 29, 2009 at 10:17 AM, Vinayak Borkar <vb...@yahoo.com> wrote:
>> Guys,
>>
>>
>> We need to put up the VXQuery website. Do you know what technologies we
>> could use to get that up? I know there is a wiki we could use. Is there a
>> different way we could build the site using traditional html?
>>
>> Thanks,
>> Vinayak
>>
>
>
>
Re: VXQuery Website
Posted by Jochen Wiedmann <jo...@gmail.com>.
Hi, Vinyak,
I *strongly* recommend to switch to Maven as the build system. This
will give you an initial site for free. Anything else can easily be
added. Another advantage will be that you get a build system which
adheres to the Apache policies automatically. (Don't underestimate, it
can become quite burdensome to publish a release otherwise.)
I'd volunteer to change the sources accordingly, or at least to do the
initial changes that are required to build the project using Maven.
Jochen
On Tue, Sep 29, 2009 at 10:17 AM, Vinayak Borkar <vb...@yahoo.com> wrote:
> Guys,
>
>
> We need to put up the VXQuery website. Do you know what technologies we
> could use to get that up? I know there is a wiki we could use. Is there a
> different way we could build the site using traditional html?
>
> Thanks,
> Vinayak
>
--
Germanys national anthem is the most boring in the world - how telling!