----- Original Message -----
From: "Jason van Zyl" <[EMAIL PROTECTED]>
To: "Turbine Maven Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, July 23, 2002 1:19 PM
Subject: Re: front page generation (logo an breadcrumbs etc)


> On Tue, 2002-07-23 at 13:10, Doug Lochart wrote:
> > Jason, Forgive me for overly picking your brain but I have a few more
> > questions.  I will try and be brief.
> >
> > I just looked at the Jelly on jakarta and I really like what I read.
> > However, using it (invoking it) still seems to be a mystery to me.  It
might
> > help if I see how Maven is using it.  Could you direct me to locations
in
> > the Maven source that might shine this light on Jelly and its use
within?
>
> src/bin/maven.[bat|sh] is where
>
> org.apache.maven.app.Maven is started. We boot up Jelly inside
> org.apache.maven.app.Maven. We set up the jelly contexts and process all
> our files from there.


Looking at Maven.java I see two places where runScript(...) is called.  Once
for initialization of the Maven Tag library, these tags look suspicously
like the Ant targets ... Ok I see (I Think) ... The other call to runScript
is for loading the project build file.  It looks like this file (maven.xml)
is the build script for Maven itself (is that right?).  Following the trace
though I don't see why it would be loaded at this point unless what I am
actually following is the entire build process.  I guess I am a bit confused
as to when main is invoked on App.java.  I dont know what forehead.conf is
but it looks like it sets up  parameters to launch the main in App.java when
maven.bat is run.

Let me step back a second, To invoke maven in b4 I simply called targets in
the core build files, I just realized that I have no clue how b5 is started
or how it operates.  In b4 I used delegators in an ant script, what is the
intended approach now?



>
> > Is Maven still using Ant?
>
> No. But you can still use Ant semantics. We are using Jelly for
> everything, but a plugin.jelly script can contain what would look like
> an ant build file.
>
> > Is Jelly being called from an Ant Task?
>
> No, we are using Jelly directly.
>
> >  The main
> > reason I am asking is that to get b4 to work with our setup I had to
modify
> > the <compile> core/build.xml target (basically turn it off).  We use
maven
> > for everything except compiling, suffice it to say that I cannot change
the
> > way things are so we cannot use the build aspect of Maven unless it is
more
> > open ended.  I don't expect Maven to bend to every projects whim so I
plan
> > to bend to it as far as I can but for now I still need to turn off
> > compilation (or override it, maybe in the form of an alternate plugin or
> > something).
>
> In b5 you don't have to use the the java plugin that comes with maven.
> You can make your own plugin to compile the way you like if that suits
> you. What do you need to configure?
>
Its not much of a configuration thing its a legacy set of applications that
were plunked into CVS awkwardly where each project generates from 1-8 Jars
and they have nasty interdependencies between them and no consistent
structure.  In maven:jar (b4) for example I needed more control over what
was being jar'd.  I also did not like the always retrieving the dependency
jars and sticking them in lib.repo before a build.  Sometimes I will be
working on 3 projects simultaneously and I may need to make temporary
changes to a project that I do not intend to commit.  We usually pull
projects from cvs under a root directpory and our ant scripts use releative
paths to handle dependencies.  There were a lot of obstacles that faced me
when I was tasked to see if Maven is a direction we want to go.  I love
Maven and want to use it to its full potential.  It does a lot for you even
without the build aspects.

BTW I read something about "reactor" that basically is a composite/container
patterned approach to mavenizing projects.  In my environment that is the
norm, several subprojects under one larger project and 1 or more lareger
projects collected into a form of a release.  I am doing all this now with
ant scripts.  It would be nice if reactor is what I think it is.


> > Any help or pointers to more documentation would be appreciative.
>
> I can answer your specific questions but there isn't much doco for the
> new stuff.

I was following the flow in App.java and Maven.java but then I got lost.  I
see methods called runGoals() and
attainGoals().  I looked in the maven.xml file and I see goal elements of
which many look like ant targets.  In fact I see several elements that look
like Ant tasks.  What is a goal?

Also a Jelly question.  I see the two calls to run scripts in Maven.java.
When the scripts is run, I see that the entire jelly script is decomposed
into a ScriptBlock (an array of different Tags that implement Script)  When
you run the root script they all run in order.  Say for the driver.jelly
file, when the script is run() what is the XMLOutput, where does it go or
get used by if its is used.  I guess my question boils down to what happens
to the contents of driver.jelly when its executed?

Is there any hidden/hard to find examples of Jelly somewhere?

Thanks Again for your time

Doug


>
> >
> > After writing this I think if I have any more questions concerning the
> > internals I will post them on the dev list.
>
> You can post them here, I'll answer them.
>
> > thanks
> >
> > Doug
> >
> >
> >
> >
> > ----- Original Message -----
> > From: "Jason van Zyl" <[EMAIL PROTECTED]>
> > To: "Turbine Maven Users List" <[EMAIL PROTECTED]>
> > Sent: Tuesday, July 23, 2002 12:04 PM
> > Subject: Re: front page generation (logo an breadcrumbs etc)
> >
> >
> > > On Tue, 2002-07-23 at 11:57, Doug Lochart wrote:
> > > > Thanks Jason.  I should have mentioned (my mistake) that I was using
> > version
> > > > b4.  I just tried building the latest CVS snapshot thinking that
<logo>
> > was
> > > > not working in b4.  I am now totally confused.  Everything in b5
seems
> > > > different.
> > >
> > > It is a lot different. Almost a completely different animal than b4.
> > >
> > > > I noticed several build errors within plugins and I do not see
> > > > the core/build.xml, docs/build.xml files anymore.
> > >
> > > The core plugin is gone and has been split into java/test/clean. Ant
> > > build files are no longer use as we are using Jelly scripts now.
> > >
> > > >  I have been looking over
> > > > the mailing list and I see that the docs online have not been
updated
> > yet.
> > >
> > > No. This is generally a problem where there are docs for the released
> > > version, b4, and docs that are current with CVS HEAD. I haven't update
> > > the docs yet for b5 but I am planning on making it possible to have
> > > several versions of documentation for a given project.
> > >
> > > > I just downloaded turbine-2 to look at the build script and that one
> > still
> > > > has the same type of delegators as b4 (all referencing
core/build.xml).
> > Is
> > > > there a project that is using b5?
> > >
> > > There are project-b5.xml descriptors that work with b5 for the turbine
> > > projects. There are no more delegator in b5 as well.
> > >
> > > > Did my build of b5 fail to distribute the
> > > > build.xml files under plugins?
> > > >
> > > > I wish I could get my head around Maven.  I would like to try and
> > > > participate in development but I feel at the bottom of an extremely
long
> > > > learning curve(not knowing Turbine, Velocity etc).
> > >
> > > We are trying to make Maven easy to use. Software that is simple to
use
> > > often has some trickery going on under the covers which isn't 100%
> > > obvious. The docs will catch up but we are furiously improving and
> > > altering bits and pieces everywhere so I know that it is frustrating
for
> > > people to get involved but that's the way it is right now.
> > >
> > > For people who want to improve Maven, the primary way of doing this is
> > > by writing plugins. In almost all cases improvements will be made in
the
> > > form of plugins. There are many examples now as everything is a
plugin.
> > > Maven is really a small core now with a satellite of plugins. For
people
> > > who want to delve deeper there is a lot to learn because Maven
provides
> > > a _lot_ for almost no initial work.
> > >
> > > > Do you have a suggestion
> > > > as to where I can start?  I feel that even if I don't participate
much,
> > > > knowing the ins and outs of the codebase would let me solve more of
my
> > > > issues on my own.
> > >
> > > I hope that you won't have to know the Maven code base in order to
solve
> > > your problems. I really hope that won't be the case when we release.
You
> > > should be able to do everything with a plugin. But if you want to know
> > > how Maven works now Jelly is a must. We're using it in all facets of
> > > Maven. When we need to augment Maven the modus operandi now is to make
a
> > > Jelly tag or to use a Java Bean and dynamically make it a Jelly tag
> > > using the jelly:define tag lib. Jelly Jelly Jelly.
> > >
> > > DVSL is also something to know as it is an easy way to produce reports
> > > and we use it a lot.
> > >
> > > The core of Maven is rapidly shrinking so hopefully when the release
> > > rolls the codebase will be more comprehensible.
> > >
> > > > thanks again sir for your expedient help!  It is much appreciated.
> > >
> > > No problem.
> > >
> > > > Doug
> > > >
> > > > ----- Original Message -----
> > > > From: "Jason van Zyl" <[EMAIL PROTECTED]>
> > > > To: "Turbine Maven Users List"
<[EMAIL PROTECTED]>
> > > > Sent: Tuesday, July 23, 2002 11:41 AM
> > > > Subject: RE: front page generation (logo an breadcrumbs etc)
> > > >
> > > >
> > > > > On Tue, 2002-07-23 at 10:29, Alef Arendsen wrote:
> > > > > > > I cannot seem to get Maven to replace the logo <img> with the
> > > > > > > gif file I specify in the project.xml.  I set both the
> > > > > > > project logo and the organization logo to be
> > > > > > > <logo>/images/new.gif</logo> and I still get the jakarta
> > > > > > > image.  Any suggestions on what I might be doing wrong?
> > > > > > I'm having the same problem. In site.dvsl it seems the property
> > > > pom.organization.logo isn't recognized or something
> > > > >
> > > > > I just fixed this in CVS. I'm now using the $mavenProject
reference in
> > > > > the DVSL report instead of the $pom reference which is a DVSL
node.
> > Try
> > > > > it now, should work for you.
> > > > >
> > > > > > >
> > > > > > > I also cannot figure out how (as on the Maven home page) to
> > > > > > > get the <div="breadcrumbs" .. area in the index.html to be
> > > > > > > created.  I call it The breadcrumbs area because when I view
> > > > > > > source on the Maven homepage I see the list of releated
> > > > > > > projects (Turbine, Turbine2 etc) in a div area named
> > > > > > > breadcrumbs.  I look at the source for index.html that is
> > > > > > > generated for me by Maven and I see the same section but
> > > > > > > there are no comments except for a blank space.  How do you
> > > > > > > populate this list?
> > > > > > As far as I know this isn't the breadcrumbs area. You can define
> > those
> > > > links in the navigation.xml in the xdocs directory in your module.
> > There's
> > > > two sections, links and the other one...
> > > > > >
> > > > > > alef
> > > > > >
> > > > > > --
> > > > > > To unsubscribe, e-mail:
> > > > <mailto:[EMAIL PROTECTED]>
> > > > > > For additional commands, e-mail:
> > > > <mailto:[EMAIL PROTECTED]>
> > > > > --
> > > > > jvz.
> > > > >
> > > > > Jason van Zyl
> > > > > [EMAIL PROTECTED]
> > > > > http://tambora.zenplex.org
> > > > >
> > > > > In short, man creates for himself a new religion of a rational
> > > > > and technical order to justify his work and to be justified in it.
> > > > >
> > > > >   -- Jacques Ellul, The Technological Society
> > > > >
> > > > >
> > > > > --
> > > > > To unsubscribe, e-mail:
> > > > <mailto:[EMAIL PROTECTED]>
> > > > > For additional commands, e-mail:
> > > > <mailto:[EMAIL PROTECTED]>
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > > > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > > --
> > > jvz.
> > >
> > > Jason van Zyl
> > > [EMAIL PROTECTED]
> > > http://tambora.zenplex.org
> > >
> > > In short, man creates for himself a new religion of a rational
> > > and technical order to justify his work and to be justified in it.
> > >
> > >   -- Jacques Ellul, The Technological Society
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
> --
> jvz.
>
> Jason van Zyl
> [EMAIL PROTECTED]
> http://tambora.zenplex.org
>
> In short, man creates for himself a new religion of a rational
> and technical order to justify his work and to be justified in it.
>
>   -- Jacques Ellul, The Technological Society
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to