You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Eric Helfrich <eh...@gmail.com> on 2007/02/16 23:29:32 UTC
Xdoclet plugin and multi module projects
Has anyone been able to get this to work correctly? Hibernate doclet
and ejbdoclet do not work correctly -- ejb doclet generates all files
in the generated sources directory of the first project it runs.
Hibernate doclet does not seem to find the source files at all when
run from a parent project which defines the plugin - -but works fine
if generate-sources is run on the sub project. Any ideas?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Xdoclet plugin and multi module projects
Posted by Eric Helfrich <eh...@gmail.com>.
I realize the suggestion was meant to be helpful -- I think it has to do
with properties being immutable in ant and xdoclet1 being dependent on ant.
I am working with a substantial base of code and to attempt to reorg it
efficiently at this point would be difficult. XD2 doesn't rely on ant --
but I haven't been successful in getting it set up. I may put a bit more
effort into it now. In the meantime another solution would be to call out
to an ant task using ant run and have that task run in its own process.
That is my fallback if xd2 isn't ready yet.
On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
>
> The suggestion was not as what is best, but rather what is possible right
> now as I have also encountered the same issue you where facing. Maybe XD2
> fixes this?
>
>
>
> On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> >
> > I don't think that putting everything that gets xdocleted in a common
> jar
> > is
> > an ideal solution -- one of the reasons for breaking you code up into
> > projects is to separate functionality -- and one of the reasons to use
> > Maven
> > is to support that flexibility -- not limit it. Thanks for the
> suggestion
> > though.
> >
> > On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
> > >
> > > Why, the ejbs will be in the common-jar and they can be added the same
> > > way.
> > >
> > > On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> > > >
> > > > Yes it would work -- and is probably better from a resource point of
> > > view
> > > > anyway. On the other hand, that won't work for the ejbdoclet
> issues.
> > > >
> > > > On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
> > > > >
> > > > > Just add a common jar as the 1st module, and add that jar to your
> > > legacy
> > > > > code. Would that work?
> > > > >
> > > > >
> > > > >
> > > > > On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> > > > > >
> > > > > > that would work -- except I am pulling in a legacy build system
> > here
> > > > > > and would rather not have to start moving code around at that
> > level
> > > > > >
> > > > > >
> > > > > > On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
> > > > > > > I use hibernate doclet, and it acts the same for me.
> > > > > > > I just have my 1st module is my common-jar that gets added to
> > all
> > > my
> > > > > > modules
> > > > > > > anyways. Works fine even though it is strange...
> > > > > > >
> > > > > > >
> > > > > > > On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> > > > > > > >
> > > > > > > > Has anyone been able to get this to work
> correctly? Hibernate
> > > > > doclet
> > > > > > > > and ejbdoclet do not work correctly -- ejb doclet generates
> > all
> > > > > files
> > > > > > > > in the generated sources directory of the first project it
> > runs.
> > > > > > > > Hibernate doclet does not seem to find the source files at
> all
> > > > when
> > > > > > > > run from a parent project which defines the plugin - -but
> > works
> > > > fine
> > > > > > > > if generate-sources is run on the sub project. Any ideas?
> > > > > > > >
> > > > > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > ---
> > > > > > > Thanks,
> > > > > > > Mick Knutson
> > > > > > >
> > > > > > > http://www.baselogic.com
> > > > > > > http://www.blincmagazine.com
> > > > > > > http://www.djmick.com
> > > > > > > http://www. . /djmick_dot_com
> > > > > > > http://www.thumpradio.com
> > > > > > > ---
> > > > > > >
> > > > > >
> > > > > >
> > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > ---
> > > > > Thanks,
> > > > > Mick Knutson
> > > > >
> > > > > http://www.baselogic.com
> > > > > http://www.blincmagazine.com
> > > > > http://www.djmick.com
> > > > > http://www. . /djmick_dot_com
> > > > > http://www.thumpradio.com
> > > > > ---
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > ---
> > > Thanks,
> > > Mick Knutson
> > >
> > > http://www.baselogic.com
> > > http://www.blincmagazine.com
> > > http://www.djmick.com
> > > http://www. . /djmick_dot_com
> > > http://www.thumpradio.com
> > > ---
> > >
> >
>
>
>
> --
> ---
> Thanks,
> Mick Knutson
>
> http://www.baselogic.com
> http://www.blincmagazine.com
> http://www.djmick.com
> http://www. . /djmick_dot_com
> http://www.thumpradio.com
> ---
>
Re: Xdoclet plugin and multi module projects
Posted by Mick Knutson <mi...@gmail.com>.
The suggestion was not as what is best, but rather what is possible right
now as I have also encountered the same issue you where facing. Maybe XD2
fixes this?
On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
>
> I don't think that putting everything that gets xdocleted in a common jar
> is
> an ideal solution -- one of the reasons for breaking you code up into
> projects is to separate functionality -- and one of the reasons to use
> Maven
> is to support that flexibility -- not limit it. Thanks for the suggestion
> though.
>
> On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
> >
> > Why, the ejbs will be in the common-jar and they can be added the same
> > way.
> >
> > On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> > >
> > > Yes it would work -- and is probably better from a resource point of
> > view
> > > anyway. On the other hand, that won't work for the ejbdoclet issues.
> > >
> > > On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
> > > >
> > > > Just add a common jar as the 1st module, and add that jar to your
> > legacy
> > > > code. Would that work?
> > > >
> > > >
> > > >
> > > > On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> > > > >
> > > > > that would work -- except I am pulling in a legacy build system
> here
> > > > > and would rather not have to start moving code around at that
> level
> > > > >
> > > > >
> > > > > On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
> > > > > > I use hibernate doclet, and it acts the same for me.
> > > > > > I just have my 1st module is my common-jar that gets added to
> all
> > my
> > > > > modules
> > > > > > anyways. Works fine even though it is strange...
> > > > > >
> > > > > >
> > > > > > On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> > > > > > >
> > > > > > > Has anyone been able to get this to work correctly? Hibernate
> > > > doclet
> > > > > > > and ejbdoclet do not work correctly -- ejb doclet generates
> all
> > > > files
> > > > > > > in the generated sources directory of the first project it
> runs.
> > > > > > > Hibernate doclet does not seem to find the source files at all
> > > when
> > > > > > > run from a parent project which defines the plugin - -but
> works
> > > fine
> > > > > > > if generate-sources is run on the sub project. Any ideas?
> > > > > > >
> > > > > > >
> > > >
> ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > ---
> > > > > > Thanks,
> > > > > > Mick Knutson
> > > > > >
> > > > > > http://www.baselogic.com
> > > > > > http://www.blincmagazine.com
> > > > > > http://www.djmick.com
> > > > > > http://www.myspace.com/djmick_dot_com
> > > > > > http://www.thumpradio.com
> > > > > > ---
> > > > > >
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > ---
> > > > Thanks,
> > > > Mick Knutson
> > > >
> > > > http://www.baselogic.com
> > > > http://www.blincmagazine.com
> > > > http://www.djmick.com
> > > > http://www.myspace.com/djmick_dot_com
> > > > http://www.thumpradio.com
> > > > ---
> > > >
> > >
> >
> >
> >
> > --
> > ---
> > Thanks,
> > Mick Knutson
> >
> > http://www.baselogic.com
> > http://www.blincmagazine.com
> > http://www.djmick.com
> > http://www.myspace.com/djmick_dot_com
> > http://www.thumpradio.com
> > ---
> >
>
--
---
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---
Re: Xdoclet plugin and multi module projects
Posted by Eric Helfrich <eh...@gmail.com>.
I don't think that putting everything that gets xdocleted in a common jar is
an ideal solution -- one of the reasons for breaking you code up into
projects is to separate functionality -- and one of the reasons to use Maven
is to support that flexibility -- not limit it. Thanks for the suggestion
though.
On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
>
> Why, the ejbs will be in the common-jar and they can be added the same
> way.
>
> On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> >
> > Yes it would work -- and is probably better from a resource point of
> view
> > anyway. On the other hand, that won't work for the ejbdoclet issues.
> >
> > On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
> > >
> > > Just add a common jar as the 1st module, and add that jar to your
> legacy
> > > code. Would that work?
> > >
> > >
> > >
> > > On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> > > >
> > > > that would work -- except I am pulling in a legacy build system here
> > > > and would rather not have to start moving code around at that level
> > > >
> > > >
> > > > On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
> > > > > I use hibernate doclet, and it acts the same for me.
> > > > > I just have my 1st module is my common-jar that gets added to all
> my
> > > > modules
> > > > > anyways. Works fine even though it is strange...
> > > > >
> > > > >
> > > > > On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> > > > > >
> > > > > > Has anyone been able to get this to work correctly? Hibernate
> > > doclet
> > > > > > and ejbdoclet do not work correctly -- ejb doclet generates all
> > > files
> > > > > > in the generated sources directory of the first project it runs.
> > > > > > Hibernate doclet does not seem to find the source files at all
> > when
> > > > > > run from a parent project which defines the plugin - -but works
> > fine
> > > > > > if generate-sources is run on the sub project. Any ideas?
> > > > > >
> > > > > >
> > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > ---
> > > > > Thanks,
> > > > > Mick Knutson
> > > > >
> > > > > http://www.baselogic.com
> > > > > http://www.blincmagazine.com
> > > > > http://www.djmick.com
> > > > > http://www.myspace.com/djmick_dot_com
> > > > > http://www.thumpradio.com
> > > > > ---
> > > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > ---
> > > Thanks,
> > > Mick Knutson
> > >
> > > http://www.baselogic.com
> > > http://www.blincmagazine.com
> > > http://www.djmick.com
> > > http://www.myspace.com/djmick_dot_com
> > > http://www.thumpradio.com
> > > ---
> > >
> >
>
>
>
> --
> ---
> Thanks,
> Mick Knutson
>
> http://www.baselogic.com
> http://www.blincmagazine.com
> http://www.djmick.com
> http://www.myspace.com/djmick_dot_com
> http://www.thumpradio.com
> ---
>
Re: Xdoclet plugin and multi module projects
Posted by Mick Knutson <mi...@gmail.com>.
Why, the ejbs will be in the common-jar and they can be added the same way.
On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
>
> Yes it would work -- and is probably better from a resource point of view
> anyway. On the other hand, that won't work for the ejbdoclet issues.
>
> On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
> >
> > Just add a common jar as the 1st module, and add that jar to your legacy
> > code. Would that work?
> >
> >
> >
> > On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> > >
> > > that would work -- except I am pulling in a legacy build system here
> > > and would rather not have to start moving code around at that level
> > >
> > >
> > > On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
> > > > I use hibernate doclet, and it acts the same for me.
> > > > I just have my 1st module is my common-jar that gets added to all my
> > > modules
> > > > anyways. Works fine even though it is strange...
> > > >
> > > >
> > > > On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> > > > >
> > > > > Has anyone been able to get this to work correctly? Hibernate
> > doclet
> > > > > and ejbdoclet do not work correctly -- ejb doclet generates all
> > files
> > > > > in the generated sources directory of the first project it runs.
> > > > > Hibernate doclet does not seem to find the source files at all
> when
> > > > > run from a parent project which defines the plugin - -but works
> fine
> > > > > if generate-sources is run on the sub project. Any ideas?
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > ---
> > > > Thanks,
> > > > Mick Knutson
> > > >
> > > > http://www.baselogic.com
> > > > http://www.blincmagazine.com
> > > > http://www.djmick.com
> > > > http://www.myspace.com/djmick_dot_com
> > > > http://www.thumpradio.com
> > > > ---
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > --
> > ---
> > Thanks,
> > Mick Knutson
> >
> > http://www.baselogic.com
> > http://www.blincmagazine.com
> > http://www.djmick.com
> > http://www.myspace.com/djmick_dot_com
> > http://www.thumpradio.com
> > ---
> >
>
--
---
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---
Re: Xdoclet plugin and multi module projects
Posted by Eric Helfrich <eh...@gmail.com>.
Yes it would work -- and is probably better from a resource point of view
anyway. On the other hand, that won't work for the ejbdoclet issues.
On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
>
> Just add a common jar as the 1st module, and add that jar to your legacy
> code. Would that work?
>
>
>
> On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> >
> > that would work -- except I am pulling in a legacy build system here
> > and would rather not have to start moving code around at that level
> >
> >
> > On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
> > > I use hibernate doclet, and it acts the same for me.
> > > I just have my 1st module is my common-jar that gets added to all my
> > modules
> > > anyways. Works fine even though it is strange...
> > >
> > >
> > > On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> > > >
> > > > Has anyone been able to get this to work correctly? Hibernate
> doclet
> > > > and ejbdoclet do not work correctly -- ejb doclet generates all
> files
> > > > in the generated sources directory of the first project it runs.
> > > > Hibernate doclet does not seem to find the source files at all when
> > > > run from a parent project which defines the plugin - -but works fine
> > > > if generate-sources is run on the sub project. Any ideas?
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > ---
> > > Thanks,
> > > Mick Knutson
> > >
> > > http://www.baselogic.com
> > > http://www.blincmagazine.com
> > > http://www.djmick.com
> > > http://www.myspace.com/djmick_dot_com
> > > http://www.thumpradio.com
> > > ---
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> ---
> Thanks,
> Mick Knutson
>
> http://www.baselogic.com
> http://www.blincmagazine.com
> http://www.djmick.com
> http://www.myspace.com/djmick_dot_com
> http://www.thumpradio.com
> ---
>
Re: Xdoclet plugin and multi module projects
Posted by Mick Knutson <mi...@gmail.com>.
Just add a common jar as the 1st module, and add that jar to your legacy
code. Would that work?
On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
>
> that would work -- except I am pulling in a legacy build system here
> and would rather not have to start moving code around at that level
>
>
> On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
> > I use hibernate doclet, and it acts the same for me.
> > I just have my 1st module is my common-jar that gets added to all my
> modules
> > anyways. Works fine even though it is strange...
> >
> >
> > On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> > >
> > > Has anyone been able to get this to work correctly? Hibernate doclet
> > > and ejbdoclet do not work correctly -- ejb doclet generates all files
> > > in the generated sources directory of the first project it runs.
> > > Hibernate doclet does not seem to find the source files at all when
> > > run from a parent project which defines the plugin - -but works fine
> > > if generate-sources is run on the sub project. Any ideas?
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > --
> > ---
> > Thanks,
> > Mick Knutson
> >
> > http://www.baselogic.com
> > http://www.blincmagazine.com
> > http://www.djmick.com
> > http://www.myspace.com/djmick_dot_com
> > http://www.thumpradio.com
> > ---
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
---
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---
Re: Xdoclet plugin and multi module projects
Posted by Eric Helfrich <eh...@gmail.com>.
that would work -- except I am pulling in a legacy build system here
and would rather not have to start moving code around at that level
On 2/16/07, Mick Knutson <mi...@gmail.com> wrote:
> I use hibernate doclet, and it acts the same for me.
> I just have my 1st module is my common-jar that gets added to all my modules
> anyways. Works fine even though it is strange...
>
>
> On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
> >
> > Has anyone been able to get this to work correctly? Hibernate doclet
> > and ejbdoclet do not work correctly -- ejb doclet generates all files
> > in the generated sources directory of the first project it runs.
> > Hibernate doclet does not seem to find the source files at all when
> > run from a parent project which defines the plugin - -but works fine
> > if generate-sources is run on the sub project. Any ideas?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> ---
> Thanks,
> Mick Knutson
>
> http://www.baselogic.com
> http://www.blincmagazine.com
> http://www.djmick.com
> http://www.myspace.com/djmick_dot_com
> http://www.thumpradio.com
> ---
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Xdoclet plugin and multi module projects
Posted by Mick Knutson <mi...@gmail.com>.
I use hibernate doclet, and it acts the same for me.
I just have my 1st module is my common-jar that gets added to all my modules
anyways. Works fine even though it is strange...
On 2/16/07, Eric Helfrich <eh...@gmail.com> wrote:
>
> Has anyone been able to get this to work correctly? Hibernate doclet
> and ejbdoclet do not work correctly -- ejb doclet generates all files
> in the generated sources directory of the first project it runs.
> Hibernate doclet does not seem to find the source files at all when
> run from a parent project which defines the plugin - -but works fine
> if generate-sources is run on the sub project. Any ideas?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
---
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---