You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by di...@multitask.com.au on 2003/01/04 04:11:41 UTC
Re: 2 qs about Xdoclet plugin
Tim Stephenson <Ti...@TechnologyOneCorp.com> wrote on 04/01/2003
09:47:46 AM:
> Hi,
>
> I have just got the xdoclet 1.2b2 plugin installed and runnning and had
a
> couple of questions about it.
>
> 1. The plugin reports a NoClassDefFound unless I modify the classpath of
> each doclet to include the relevant module jar. For example in the ejb
> doclet I needed to add:
> <pathelement
path="${plugin.getDependencyPath('xdoclet+ejb-module')}"/>
> And I also needed to add the appropriate dependency to the plugin's
> project.xml
Sounds about right. There are quite a few problems with the xdoclet plugin
in cvs. I'd be happy to apply a patch that you sent through.
> Since Ara said the plugin.jelly is generated could it be a problem in
the
> template (xdoclet+xdoclet-module appears in every goal instead of being
> substituted with the relevant modeule)?
No idea on that one. Ara?
> 2. With the webdoclet I cannot work out how to generate my struts
config. U
> have the following property which appears to be what is required:
>
> maven.xdoclet.webdoclet.strutsconfigxml.0=true
>
> Any body have any ideas?
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
RE: 2 qs about Xdoclet plugin
Posted by di...@multitask.com.au.
I'm happy to remove the plugin from Maven's CVS.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
Aslak Hellesoy <as...@netcom.no> wrote on 05/01/2003 03:33:30 AM:
>
>
> > -----Original Message-----
> > From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> > Sent: 4. januar 2003 17:01
> > To: Turbine Maven Users List
> > Subject: RE: 2 qs about Xdoclet plugin
> >
> >
> > Aslak Hellesoy <as...@netcom.no> wrote on 05/01/2003 01:16:27
AM:
> >
> > >
> > > Please send patches to the XDoclet plugin to XDoclet
> > > http://opensource.atlassian.com/projects/xdoclet and _not_ to the
Maven
> > > team. The reason being that the jelly script is in fact generated by
> > XDoclet
> > > itself. IIRC, we agreed before xmas that it should be the XDoclet
team's
> > > responsibility to maintain the plugin.
> >
> > That's not what Ara wanted:
> >
> > http://www.mail-archive.com/turbine-maven-user@jakarta.apache.org/
> > msg02312.html
> >
>
> With "Ouch don't do that!" I believe Ara was referring to the sentence
"-So
> you can remove the XDoclet plugin from Maven's CVS", but not to the
previous
> sentences in the same paragraph. Please read it again. (And Ara, correct
me
> if I'm wrong).
>
> The people who maintain the XDoclet Maven plugin (currently Ara and I)
have
> to be XDoclet committers, because the jelly script is generated by
XDoclet
> itself (by looking at the XDoclet sources and using a special XDoclet
> template), so it just can't be moved to Maven's CVS. Well, it can, but
it
> would require anybody bulding the plugin to have XDoclet's sources
> handy. -Which makes things very complicated, and I doubt anybody would
want
> it that way.
>
> So the XDoclet team maintains the XDoclet template that generates the
jelly
> script. -And wraps up the maven plugin as a jar file. When people find
> errors, they tell us, we modify the template and generate a new plugin.
>
> Ara suggests we provide the Maven team with updated plugins every time
> XDoclet is released. I think this would make life more complicated for
both
> the XDoclet team and the Maven team, and I disapprove with Ara's
suggestion.
>
> The only drawback I can see with keeping everything in XDoclet's CVS and
> distro (and nothing in Maven) is that the plugin will have to be
installed
> manually. -But AFAIK, automatic downloading and installation of plugins
is a
> planned feature in Maven. When/if this is implemented, this drawback
will
> vanish. And in the meanwhile I think people can live with a manual
> installation of the plugin. After all it's just a matter of copying the
> plugin jar file from the XDoclet distro to Maven's plugin directory.
>
> What do you think?
>
> Aslak
>
> >
> >
> > --
> > dIon Gillard, Multitask Consulting
> > Blog: http://www.freeroller.net/page/dion/Weblog
> > Work: http://www.multitask.com.au
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> > <ma...@jakarta.apache.org>
> >
>
>
> --
> To unsubscribe, e-mail: <mailto:turbine-maven-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:turbine-maven-user-
> help@jakarta.apache.org>
>
> ForwardSourceID:NT0009E7DE
RE: 2 qs about Xdoclet plugin
Posted by Ara Abrahamian <ar...@yahoo.com>.
> > That's not what Ara wanted:
> >
> > http://www.mail-archive.com/turbine-maven-user@jakarta.apache.org/
> > msg02312.html
> >
>
> With "Ouch don't do that!" I believe Ara was referring to the sentence
"-
> So
> you can remove the XDoclet plugin from Maven's CVS", but not to the
> previous
> sentences in the same paragraph. Please read it again. (And Ara,
correct
> me
> if I'm wrong).
You're right.
> Ara suggests we provide the Maven team with updated plugins every time
> XDoclet is released. I think this would make life more complicated for
> both
> the XDoclet team and the Maven team, and I disapprove with Ara's
> suggestion.
>
> The only drawback I can see with keeping everything in XDoclet's CVS
and
> distro (and nothing in Maven) is that the plugin will have to be
installed
> manually. -But AFAIK, automatic downloading and installation of
plugins is
> a
> planned feature in Maven. When/if this is implemented, this drawback
will
> vanish. And in the meanwhile I think people can live with a manual
> installation of the plugin. After all it's just a matter of copying
the
> plugin jar file from the XDoclet distro to Maven's plugin directory.
>
> What do you think?
Imho until the auto-install is implemented we should provide the updated
plugin after each release. Jars for ibiblio too.
So dIon would you please update the jars and xdoclet plugin for b2? I
know Matt has sent you some b2 files, but they where pre-final snapshots
actually. Please download the latest xdoclet binary distro and update
them.
Ara.
RE: 2 qs about Xdoclet plugin
Posted by Aslak Hellesoy <as...@netcom.no>.
> -----Original Message-----
> From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> Sent: 4. januar 2003 17:01
> To: Turbine Maven Users List
> Subject: RE: 2 qs about Xdoclet plugin
>
>
> Aslak Hellesoy <as...@netcom.no> wrote on 05/01/2003 01:16:27 AM:
>
> >
> > Please send patches to the XDoclet plugin to XDoclet
> > http://opensource.atlassian.com/projects/xdoclet and _not_ to the Maven
> > team. The reason being that the jelly script is in fact generated by
> XDoclet
> > itself. IIRC, we agreed before xmas that it should be the XDoclet team's
> > responsibility to maintain the plugin.
>
> That's not what Ara wanted:
>
> http://www.mail-archive.com/turbine-maven-user@jakarta.apache.org/
> msg02312.html
>
With "Ouch don't do that!" I believe Ara was referring to the sentence "-So
you can remove the XDoclet plugin from Maven's CVS", but not to the previous
sentences in the same paragraph. Please read it again. (And Ara, correct me
if I'm wrong).
The people who maintain the XDoclet Maven plugin (currently Ara and I) have
to be XDoclet committers, because the jelly script is generated by XDoclet
itself (by looking at the XDoclet sources and using a special XDoclet
template), so it just can't be moved to Maven's CVS. Well, it can, but it
would require anybody bulding the plugin to have XDoclet's sources
handy. -Which makes things very complicated, and I doubt anybody would want
it that way.
So the XDoclet team maintains the XDoclet template that generates the jelly
script. -And wraps up the maven plugin as a jar file. When people find
errors, they tell us, we modify the template and generate a new plugin.
Ara suggests we provide the Maven team with updated plugins every time
XDoclet is released. I think this would make life more complicated for both
the XDoclet team and the Maven team, and I disapprove with Ara's suggestion.
The only drawback I can see with keeping everything in XDoclet's CVS and
distro (and nothing in Maven) is that the plugin will have to be installed
manually. -But AFAIK, automatic downloading and installation of plugins is a
planned feature in Maven. When/if this is implemented, this drawback will
vanish. And in the meanwhile I think people can live with a manual
installation of the plugin. After all it's just a matter of copying the
plugin jar file from the XDoclet distro to Maven's plugin directory.
What do you think?
Aslak
>
>
> --
> dIon Gillard, Multitask Consulting
> Blog: http://www.freeroller.net/page/dion/Weblog
> Work: http://www.multitask.com.au
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
RE: 2 qs about Xdoclet plugin
Posted by di...@multitask.com.au.
Aslak Hellesoy <as...@netcom.no> wrote on 05/01/2003 01:16:27 AM:
>
> Please send patches to the XDoclet plugin to XDoclet
> http://opensource.atlassian.com/projects/xdoclet and _not_ to the Maven
> team. The reason being that the jelly script is in fact generated by
XDoclet
> itself. IIRC, we agreed before xmas that it should be the XDoclet team's
> responsibility to maintain the plugin.
That's not what Ara wanted:
http://www.mail-archive.com/turbine-maven-user@jakarta.apache.org/msg02312.html
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
RE: 2 qs about Xdoclet plugin
Posted by Aslak Hellesoy <as...@netcom.no>.
> -----Original Message-----
> From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> Sent: 4. januar 2003 04:12
> To: Turbine Maven Users List
> Subject: Re: 2 qs about Xdoclet plugin
>
>
> Tim Stephenson <Ti...@TechnologyOneCorp.com> wrote on 04/01/2003
> 09:47:46 AM:
>
> > Hi,
> >
> > I have just got the xdoclet 1.2b2 plugin installed and runnning and had
> a
> > couple of questions about it.
> >
> > 1. The plugin reports a NoClassDefFound unless I modify the classpath of
> > each doclet to include the relevant module jar. For example in the ejb
> > doclet I needed to add:
> > <pathelement
> path="${plugin.getDependencyPath('xdoclet+ejb-module')}"/>
> > And I also needed to add the appropriate dependency to the plugin's
> > project.xml
>
> Sounds about right. There are quite a few problems with the
> xdoclet plugin
> in cvs. I'd be happy to apply a patch that you sent through.
>
Please send patches to the XDoclet plugin to XDoclet
http://opensource.atlassian.com/projects/xdoclet and _not_ to the Maven
team. The reason being that the jelly script is in fact generated by XDoclet
itself. IIRC, we agreed before xmas that it should be the XDoclet team's
responsibility to maintain the plugin.
> > Since Ara said the plugin.jelly is generated could it be a problem in
> the
> > template (xdoclet+xdoclet-module appears in every goal instead of being
> > substituted with the relevant modeule)?
> No idea on that one. Ara?
>
xdoclet+xdoclet-module contains some generic code needed by all modules.
If you hack the jelly script to fix a bug, just post a diff to XDoclet's
JIRA, and we'll apply your changes.
Cheers,
Aslak
> > 2. With the webdoclet I cannot work out how to generate my struts
> config. U
> > have the following property which appears to be what is required:
> >
> > maven.xdoclet.webdoclet.strutsconfigxml.0=true
> >
> > Any body have any ideas?
> --
> dIon Gillard, Multitask Consulting
> Blog: http://www.freeroller.net/page/dion/Weblog
> Work: http://www.multitask.com.au
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>