You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Sonnek, Ryan" <Ry...@bpc.com> on 2003/05/06 20:09:12 UTC
b9 with xdoclet
Looking through the FAQ on maven's site, the link to integrate xdoclet is
not available. Does anyone have pointers on how to start using xdoclet with
maven? Searching through the mailing list archive there are lots of posts,
but little sample code.
Thanks.
Ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: b9 with xdoclet
Posted by Matt Johnson <jo...@whitesmiths.com.au>.
Maven has not yet had a full version release. The b9 means precisely
that - beta software. I think it's very important to work off a current
cvs build (or at least, last working - not always the same thing :-) and
to take a grain of salt with every dose of maven. As this is a build
tool, rather than a production-critical component, I have no problem
using the bleeding edge.
I've just converted a 535-line ant build file into a 17-line maven.xml
and 33 properties, along with a project.xml with 25 dependencies. It
wasn't clear-cut, I ran into some bugs, and it took me a lot longer than
I expected, but... I'm much happier with the process than I was with our
bloated ant build. I have yet to explore some of our other needs,
including the reactor and a continuous build process, but I'm fairly
confident that we can reduce the complexity of our builds using maven.
Maven has a very bright future. I'm sure the reason it's a tlp has
nothing to do with its beta status, but rather with its perceived future
role in development projects. It can be frustrating trying to locate
the source of problems at present, and if I had the experience and time,
I would try to contribute to this area of maven. Let's just hope this,
and some of the other rough edges, can be improved before the first
non-beta release.
Matt
Brill Pappin wrote:
>I agree... I love the idea, and the integration, but I've got too many
>problems doing simple things... I'm surprised its a top level project.
>
>Currently I can do the same thing simply with Ant.
>
>My own preference for all this, is to make Maven an Ant task so the project
>info and dependency info can be managed. in fact, I'd suggest separating it
>out, so the project task and the dependency download tasks as separate.
>(maven has done a lot of the setup work for this, so it would be much easier
>to do).
>
>On the other hand, I'm starting to get real annoyed with the scattered
>dependencies of the Jakarta libs, and although Maven is designed to combat
>it, IMO its making it worse.
>
>I've gone as far as trying to set up a single build tree that checks out all
>commons libs and compiles them, under on tree, to make local dependency
>updates easier to handle.
>
>- Brill Pappin
>
>----- Original Message -----
>From: "Greg Zoller" <gr...@codaware.com>
>To: "Maven Users List" <us...@maven.apache.org>
>Sent: Thursday, May 08, 2003 12:23 PM
>Subject: Re: b9 with xdoclet
>
>
>
>
>>I couldn't agree more about the diagnostics!
>>
>>I'm actually quite concerned that maven is not yet ready to be a
>>"top-level" Apache project.
>>It's exactly what we need for a proj mgmt/build tool, but the log file
>>is full of errors (mostly
>>Jelly, but some Java exceptions too).
>>
>>Believe me, this isn't flame-bait. I've put my money where my mouth
>>is. I've assigned
>>staff (i.e. paid money) to have a couple people look into these problems
>>but after several
>>days no dice. It's pretty complicated trying to debug 3 tools
>>simultaneously (jelly, maven,
>>and xdoclet).
>>
>>We've also had a lot of problems with maven and xdoclet, two tools that
>>seem naturally
>>made for each other. Without some beefed-up logging, I'm not sure how
>>to determine
>>whether these problems are related to maven, jelly, xdoclet, or
>>something else.
>>
>>The main problem is that nobody (Jelly, maven, ...) logs what file is
>>being parsed that's
>>causing the errors! Hard to believe. I'm not pointing a finger of
>>blame at maven at all,
>>but as the "lead" application maven should know what files are being
>>parsed and
>>when, and be able to log this information). This is the first step
>>towards being able to
>>debug these problems and harden the environment.
>>
>>Unfortunately for now, I've lost too much development time on this. I
>>really wanted to
>>move our project to maven, but we can't get xdoclet struts generation
>>working. So for
>>now we'll stay on Ant. I really hope someone can address these errors
>>that maven
>>logs. We're eager to use the tool when its ready.
>>
>>Greg Zoller, CTO
>>Codaware, Inc.
>>
>>
>>Matt Johnson wrote:
>>
>>
>>
>>>The XDoclet team publish the maven-xdoclet plugin
>>>(http://xdoclet.sf.net/maven-plugin.html).
>>>
>>>Although I've found very few samples out there, and maven is hopeless
>>>when it comes to diagnostics, it's fairly easy to translate from ant.
>>>Configuration is handled in properties, and you can check the
>>>plugin.jelly for which properties are available.
>>>
>>>Be careful, as some properties have incorrect capitalisation (such as
>>>maven.xdoclet.ejbdoclet.jboss.0.Version), so search the plugin.jelly
>>>if you're having no success. This is apparently a side-effect of the
>>>way the plugin is built (it's actually built dynamically).
>>>
>>>'luck,
>>>
>>>
>>>Matt
>>>
>>>Sonnek, Ryan wrote:
>>>
>>>
>>>
>>>>Looking through the FAQ on maven's site, the link to integrate
>>>>xdoclet is
>>>>not available. Does anyone have pointers on how to start using
>>>>xdoclet with
>>>>maven? Searching through the mailing list archive there are lots of
>>>>posts,
>>>>but little sample code.
>>>>Thanks.
>>>>Ryan
>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: b9 with xdoclet
Posted by di...@multitask.com.au.
Brill,
what are your problems doing simple things? Are they filed as bugs in the
bug tracker?
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
"Brill Pappin" <br...@stabilia.com> wrote on 09/05/2003 02:50:39 AM:
> I agree... I love the idea, and the integration, but I've got too many
> problems doing simple things... I'm surprised its a top level project.
>
> Currently I can do the same thing simply with Ant.
>
> My own preference for all this, is to make Maven an Ant task so the
project
> info and dependency info can be managed. in fact, I'd suggest separating
it
> out, so the project task and the dependency download tasks as separate.
> (maven has done a lot of the setup work for this, so it would be much
easier
> to do).
>
> On the other hand, I'm starting to get real annoyed with the scattered
> dependencies of the Jakarta libs, and although Maven is designed to
combat
> it, IMO its making it worse.
>
> I've gone as far as trying to set up a single build tree that checks out
all
> commons libs and compiles them, under on tree, to make local dependency
> updates easier to handle.
>
> - Brill Pappin
>
> ----- Original Message -----
> From: "Greg Zoller" <gr...@codaware.com>
> To: "Maven Users List" <us...@maven.apache.org>
> Sent: Thursday, May 08, 2003 12:23 PM
> Subject: Re: b9 with xdoclet
>
>
> > I couldn't agree more about the diagnostics!
> >
> > I'm actually quite concerned that maven is not yet ready to be a
> > "top-level" Apache project.
> > It's exactly what we need for a proj mgmt/build tool, but the log file
> > is full of errors (mostly
> > Jelly, but some Java exceptions too).
> >
> > Believe me, this isn't flame-bait. I've put my money where my mouth
> > is. I've assigned
> > staff (i.e. paid money) to have a couple people look into these
problems
> > but after several
> > days no dice. It's pretty complicated trying to debug 3 tools
> > simultaneously (jelly, maven,
> > and xdoclet).
> >
> > We've also had a lot of problems with maven and xdoclet, two tools
that
> > seem naturally
> > made for each other. Without some beefed-up logging, I'm not sure how
> > to determine
> > whether these problems are related to maven, jelly, xdoclet, or
> > something else.
> >
> > The main problem is that nobody (Jelly, maven, ...) logs what file is
> > being parsed that's
> > causing the errors! Hard to believe. I'm not pointing a finger of
> > blame at maven at all,
> > but as the "lead" application maven should know what files are being
> > parsed and
> > when, and be able to log this information). This is the first step
> > towards being able to
> > debug these problems and harden the environment.
> >
> > Unfortunately for now, I've lost too much development time on this. I
> > really wanted to
> > move our project to maven, but we can't get xdoclet struts generation
> > working. So for
> > now we'll stay on Ant. I really hope someone can address these errors
> > that maven
> > logs. We're eager to use the tool when its ready.
> >
> > Greg Zoller, CTO
> > Codaware, Inc.
> >
> >
> > Matt Johnson wrote:
> >
> > > The XDoclet team publish the maven-xdoclet plugin
> > > (http://xdoclet.sf.net/maven-plugin.html).
> > >
> > > Although I've found very few samples out there, and maven is
hopeless
> > > when it comes to diagnostics, it's fairly easy to translate from
ant.
> > > Configuration is handled in properties, and you can check the
> > > plugin.jelly for which properties are available.
> > >
> > > Be careful, as some properties have incorrect capitalisation (such
as
> > > maven.xdoclet.ejbdoclet.jboss.0.Version), so search the plugin.jelly
> > > if you're having no success. This is apparently a side-effect of
the
> > > way the plugin is built (it's actually built dynamically).
> > >
> > > 'luck,
> > >
> > >
> > > Matt
> > >
> > > Sonnek, Ryan wrote:
> > >
> > >> Looking through the FAQ on maven's site, the link to integrate
> > >> xdoclet is
> > >> not available. Does anyone have pointers on how to start using
> > >> xdoclet with
> > >> maven? Searching through the mailing list archive there are lots
of
> > >> posts,
> > >> but little sample code.
> > >> Thanks.
> > >> Ryan
> > >>
> > >>
---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: users-help@maven.apache.org
> > >>
> > >>
> > >>
> > >
> > >
> > >
---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: b9 with xdoclet
Posted by Brill Pappin <br...@stabilia.com>.
I agree... I love the idea, and the integration, but I've got too many
problems doing simple things... I'm surprised its a top level project.
Currently I can do the same thing simply with Ant.
My own preference for all this, is to make Maven an Ant task so the project
info and dependency info can be managed. in fact, I'd suggest separating it
out, so the project task and the dependency download tasks as separate.
(maven has done a lot of the setup work for this, so it would be much easier
to do).
On the other hand, I'm starting to get real annoyed with the scattered
dependencies of the Jakarta libs, and although Maven is designed to combat
it, IMO its making it worse.
I've gone as far as trying to set up a single build tree that checks out all
commons libs and compiles them, under on tree, to make local dependency
updates easier to handle.
- Brill Pappin
----- Original Message -----
From: "Greg Zoller" <gr...@codaware.com>
To: "Maven Users List" <us...@maven.apache.org>
Sent: Thursday, May 08, 2003 12:23 PM
Subject: Re: b9 with xdoclet
> I couldn't agree more about the diagnostics!
>
> I'm actually quite concerned that maven is not yet ready to be a
> "top-level" Apache project.
> It's exactly what we need for a proj mgmt/build tool, but the log file
> is full of errors (mostly
> Jelly, but some Java exceptions too).
>
> Believe me, this isn't flame-bait. I've put my money where my mouth
> is. I've assigned
> staff (i.e. paid money) to have a couple people look into these problems
> but after several
> days no dice. It's pretty complicated trying to debug 3 tools
> simultaneously (jelly, maven,
> and xdoclet).
>
> We've also had a lot of problems with maven and xdoclet, two tools that
> seem naturally
> made for each other. Without some beefed-up logging, I'm not sure how
> to determine
> whether these problems are related to maven, jelly, xdoclet, or
> something else.
>
> The main problem is that nobody (Jelly, maven, ...) logs what file is
> being parsed that's
> causing the errors! Hard to believe. I'm not pointing a finger of
> blame at maven at all,
> but as the "lead" application maven should know what files are being
> parsed and
> when, and be able to log this information). This is the first step
> towards being able to
> debug these problems and harden the environment.
>
> Unfortunately for now, I've lost too much development time on this. I
> really wanted to
> move our project to maven, but we can't get xdoclet struts generation
> working. So for
> now we'll stay on Ant. I really hope someone can address these errors
> that maven
> logs. We're eager to use the tool when its ready.
>
> Greg Zoller, CTO
> Codaware, Inc.
>
>
> Matt Johnson wrote:
>
> > The XDoclet team publish the maven-xdoclet plugin
> > (http://xdoclet.sf.net/maven-plugin.html).
> >
> > Although I've found very few samples out there, and maven is hopeless
> > when it comes to diagnostics, it's fairly easy to translate from ant.
> > Configuration is handled in properties, and you can check the
> > plugin.jelly for which properties are available.
> >
> > Be careful, as some properties have incorrect capitalisation (such as
> > maven.xdoclet.ejbdoclet.jboss.0.Version), so search the plugin.jelly
> > if you're having no success. This is apparently a side-effect of the
> > way the plugin is built (it's actually built dynamically).
> >
> > 'luck,
> >
> >
> > Matt
> >
> > Sonnek, Ryan wrote:
> >
> >> Looking through the FAQ on maven's site, the link to integrate
> >> xdoclet is
> >> not available. Does anyone have pointers on how to start using
> >> xdoclet with
> >> maven? Searching through the mailing list archive there are lots of
> >> posts,
> >> but little sample code.
> >> Thanks.
> >> Ryan
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: b9 with xdoclet
Posted by Konstantin Priblouda <kp...@yahoo.com>.
--- Greg Zoller <gr...@codaware.com> wrote:
> I couldn't agree more about the diagnostics!
>
> I'm actually quite concerned that maven is not yet
> ready to be a
> "top-level" Apache project.
> It's exactly what we need for a proj mgmt/build
> tool, but the log file
> is full of errors (mostly
> Jelly, but some Java exceptions too).
>
> Believe me, this isn't flame-bait. I've put my
> money where my mouth
> is. I've assigned
> staff (i.e. paid money) to have a couple people look
> into these problems
> but after several
> days no dice. It's pretty complicated trying to
> debug 3 tools
> simultaneously (jelly, maven,
> and xdoclet).
>
> We've also had a lot of problems with maven and
> xdoclet, two tools that
> seem naturally
> made for each other. Without some beefed-up
> logging, I'm not sure how
> to determine
> whether these problems are related to maven, jelly,
> xdoclet, or
> something else.
>
> The main problem is that nobody (Jelly, maven, ...)
> logs what file is
> being parsed that's
> causing the errors! Hard to believe. I'm not
> pointing a finger of
> blame at maven at all,
> but as the "lead" application maven should know what
> files are being
> parsed and
> when, and be able to log this information). This is
> the first step
> towards being able to
> debug these problems and harden the environment.
>
> Unfortunately for now, I've lost too much
> development time on this. I
> really wanted to
> move our project to maven, but we can't get xdoclet
> struts generation
> working. So for
> now we'll stay on Ant. I really hope someone can
> address these errors
> that maven
> logs. We're eager to use the tool when its ready.
as xdoclet committer I can only agree, that
improvements are needed to maven integration.
I was able to put maven/xdoclet combo into
productivity, and I live completely off CVS for both
pieces.
I can swear for sure that:
hibernate mappiings and webwork stuff work like charm.
But I do not use struts at all for more than a
year - so I'm not current on status of this module.
You can raise your probems in xdoclet JIRA,
and I will look at it ( or aslak )
regards,
=====
Konstantin Priblouda ( ko5tik ) Freelance Software developer
< http://www.pribluda.de > < play java games -> http://www.yook.de >
< render charts online -> http://www.pribluda.de/povray/ >
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: b9 with xdoclet
Posted by Greg Zoller <gr...@codaware.com>.
I couldn't agree more about the diagnostics!
I'm actually quite concerned that maven is not yet ready to be a
"top-level" Apache project.
It's exactly what we need for a proj mgmt/build tool, but the log file
is full of errors (mostly
Jelly, but some Java exceptions too).
Believe me, this isn't flame-bait. I've put my money where my mouth
is. I've assigned
staff (i.e. paid money) to have a couple people look into these problems
but after several
days no dice. It's pretty complicated trying to debug 3 tools
simultaneously (jelly, maven,
and xdoclet).
We've also had a lot of problems with maven and xdoclet, two tools that
seem naturally
made for each other. Without some beefed-up logging, I'm not sure how
to determine
whether these problems are related to maven, jelly, xdoclet, or
something else.
The main problem is that nobody (Jelly, maven, ...) logs what file is
being parsed that's
causing the errors! Hard to believe. I'm not pointing a finger of
blame at maven at all,
but as the "lead" application maven should know what files are being
parsed and
when, and be able to log this information). This is the first step
towards being able to
debug these problems and harden the environment.
Unfortunately for now, I've lost too much development time on this. I
really wanted to
move our project to maven, but we can't get xdoclet struts generation
working. So for
now we'll stay on Ant. I really hope someone can address these errors
that maven
logs. We're eager to use the tool when its ready.
Greg Zoller, CTO
Codaware, Inc.
Matt Johnson wrote:
> The XDoclet team publish the maven-xdoclet plugin
> (http://xdoclet.sf.net/maven-plugin.html).
>
> Although I've found very few samples out there, and maven is hopeless
> when it comes to diagnostics, it's fairly easy to translate from ant.
> Configuration is handled in properties, and you can check the
> plugin.jelly for which properties are available.
>
> Be careful, as some properties have incorrect capitalisation (such as
> maven.xdoclet.ejbdoclet.jboss.0.Version), so search the plugin.jelly
> if you're having no success. This is apparently a side-effect of the
> way the plugin is built (it's actually built dynamically).
>
> 'luck,
>
>
> Matt
>
> Sonnek, Ryan wrote:
>
>> Looking through the FAQ on maven's site, the link to integrate
>> xdoclet is
>> not available. Does anyone have pointers on how to start using
>> xdoclet with
>> maven? Searching through the mailing list archive there are lots of
>> posts,
>> but little sample code.
>> Thanks.
>> Ryan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: b9 with xdoclet
Posted by Matt Johnson <jo...@whitesmiths.com.au>.
The XDoclet team publish the maven-xdoclet plugin
(http://xdoclet.sf.net/maven-plugin.html).
Although I've found very few samples out there, and maven is hopeless
when it comes to diagnostics, it's fairly easy to translate from ant.
Configuration is handled in properties, and you can check the
plugin.jelly for which properties are available.
Be careful, as some properties have incorrect capitalisation (such as
maven.xdoclet.ejbdoclet.jboss.0.Version), so search the plugin.jelly if
you're having no success. This is apparently a side-effect of the way
the plugin is built (it's actually built dynamically).
'luck,
Matt
Sonnek, Ryan wrote:
>Looking through the FAQ on maven's site, the link to integrate xdoclet is
>not available. Does anyone have pointers on how to start using xdoclet with
>maven? Searching through the mailing list archive there are lots of posts,
>but little sample code.
>
>Thanks.
>Ryan
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: b9 with xdoclet
Posted by Konstantin Priblouda <kp...@yahoo.com>.
--- "Sonnek, Ryan" <Ry...@bpc.com> wrote:
> Looking through the FAQ on maven's site, the link to
> integrate xdoclet is
> not available. Does anyone have pointers on how to
> start using xdoclet with
> maven? Searching through the mailing list archive
> there are lots of posts,
> but little sample code.
Aussuming you have setup maven properly, you have to
check out xdoclet sources, and then build them.
Normal xdoclet build process will install xdoclet
plugin and necessary jars into repository.
Then in maven.xml you can say:
<preGoal name="java:compile">
<attainGoal name="xdoclet:webdoclet"/>
</preGoal>
Of course you may need some properties to set up
invocation ( path to your sources etc. ) - best
documentation is plugin.jelly ( though it's pretty big
- about 10K lines , and automatically generated. )
regards,
=====
Konstantin Priblouda ( ko5tik ) Freelance Software developer
< http://www.pribluda.de > < play java games -> http://www.yook.de >
< render charts online -> http://www.pribluda.de/povray/ >
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org