Getting back into it

Discussion:

Geoff Longman

2003-01-12 16:34:12 UTC

Whoo-ee, I have to say that this past holiday season was the worst on record for me.
Just before Christmas good friends of ours had a terrible accident and their little girl was quite badly burned.
It'll be a tough road ahead for their family but everything is relatively ok now.

Also, I had a bit of a health scare myself last week and on top of all that we have a baby due imminently.
Note: having a baby ids a good thing, it just added to the overall stress this holiday season!

So, forgive if I've been quite the last while. I'm easing back into the 'normal' things now...

Glad to see that the Apache thing is rolling along. Kudos to Andy et al!

Looking for something to do Tapestry-wise and I was wondering if anybody had any thoughts on
the structure for the code base in CVS.

Currently, everything is located under the top-level Tapestry folder. That incl the framework, vlib, clover, contrib, workbench, and the
mock opera :-) that Howard has built for testing.

Would it make sense, after the move, the package rename, the Gump build (don't really understand that) was done
if we examined the structure and split some of it out to the top level?

The current advantage is that one can check out 'Tapestry' and get everything at once. One disadvantage is that to examine, for example, the vlib using Spindle is quite difficult.

As I said, I realize there's still a lot of work to do before making these kind of changes. But I'm willing to play around with this.

Geoff

Geoffrey Longman
Intelligent Works Inc.

Howard M. Lewis Ship

2003-01-12 16:46:33 UTC

Permalink

Part of what you discuss may involve having multiple Tapestry modules. Not good or bad, just a statement.

Yes, and we may need to reorganize things further to reflect the standard Apache project layout ... if we want to get the synnergy thing going, we want to make Tapestry "friendly" to other Apache developers.

Renaming packages looks like a big delete-and-add to CVS, so that's a good time to also reorganize directory structure. We should brainstorm what that structure should look like.
----- Original Message -----
From: Geoff Longman
To: Tapestry Contrib
Cc: tapestry-dev-sSm70nXyYxXWkAFlN0MkGWD2FQJk+8+***@public.gmane.org
Sent: Sunday, January 12, 2003 11:34 AM
Subject: [Tapestry-contrib] Getting back into it

Whoo-ee, I have to say that this past holiday season was the worst on record for me.
Just before Christmas good friends of ours had a terrible accident and their little girl was quite badly burned.
It'll be a tough road ahead for their family but everything is relatively ok now.

Also, I had a bit of a health scare myself last week and on top of all that we have a baby due imminently.
Note: having a baby ids a good thing, it just added to the overall stress this holiday season!

So, forgive if I've been quite the last while. I'm easing back into the 'normal' things now...

Glad to see that the Apache thing is rolling along. Kudos to Andy et al!

Looking for something to do Tapestry-wise and I was wondering if anybody had any thoughts on
the structure for the code base in CVS.

Currently, everything is located under the top-level Tapestry folder. That incl the framework, vlib, clover, contrib, workbench, and the
mock opera :-) that Howard has built for testing.

Would it make sense, after the move, the package rename, the Gump build (don't really understand that) was done
if we examined the structure and split some of it out to the top level?

The current advantage is that one can check out 'Tapestry' and get everything at once. One disadvantage is that to examine, for example, the vlib using Spindle is quite difficult.

As I said, I realize there's still a lot of work to do before making these kind of changes. But I'm willing to play around with this.

Geoff

Geoffrey Longman
Intelligent Works Inc.

Geoff Longman

2003-01-12 16:50:25 UTC

Permalink

Yeah, the module idea works too. Although, I dunno how it would work in the Vlib case specifically as there are three folders at the same level, Vlib, VlibBeans, and VlibEAR.

I will browse around some jakarta projects to see how they have laid things out. Will post findings to the wiki.

Geoff
----- Original Message -----
From: Howard M. Lewis Ship
To: Geoff Longman ; Tapestry Contrib
Cc: tapestry-dev-sSm70nXyYxXWkAFlN0MkGWD2FQJk+8+***@public.gmane.org
Sent: Sunday, January 12, 2003 11:46 AM
Subject: Re: [Tapestry-contrib] Getting back into it

Part of what you discuss may involve having multiple Tapestry modules. Not good or bad, just a statement.

Yes, and we may need to reorganize things further to reflect the standard Apache project layout ... if we want to get the synnergy thing going, we want to make Tapestry "friendly" to other Apache developers.

Renaming packages looks like a big delete-and-add to CVS, so that's a good time to also reorganize directory structure. We should brainstorm what that structure should look like.
----- Original Message -----
From: Geoff Longman
To: Tapestry Contrib
Cc: tapestry-dev-sSm70nXyYxXWkAFlN0MkGWD2FQJk+8+***@public.gmane.org
Sent: Sunday, January 12, 2003 11:34 AM
Subject: [Tapestry-contrib] Getting back into it

Whoo-ee, I have to say that this past holiday season was the worst on record for me.
Just before Christmas good friends of ours had a terrible accident and their little girl was quite badly burned.
It'll be a tough road ahead for their family but everything is relatively ok now.

Also, I had a bit of a health scare myself last week and on top of all that we have a baby due imminently.
Note: having a baby ids a good thing, it just added to the overall stress this holiday season!

So, forgive if I've been quite the last while. I'm easing back into the 'normal' things now...

Glad to see that the Apache thing is rolling along. Kudos to Andy et al!

Looking for something to do Tapestry-wise and I was wondering if anybody had any thoughts on
the structure for the code base in CVS.

Currently, everything is located under the top-level Tapestry folder. That incl the framework, vlib, clover, contrib, workbench, and the
mock opera :-) that Howard has built for testing.

Would it make sense, after the move, the package rename, the Gump build (don't really understand that) was done
if we examined the structure and split some of it out to the top level?

The current advantage is that one can check out 'Tapestry' and get everything at once. One disadvantage is that to examine, for example, the vlib using Spindle is quite difficult.

As I said, I realize there's still a lot of work to do before making these kind of changes. But I'm willing to play around with this.

Geoff

Geoffrey Longman
Intelligent Works Inc.

Andrew C. Oliver

2003-01-12 22:07:03 UTC

Permalink

I really recommend Mavenizing to this effect. I bet dion would help
with that.. (http://jakarta.apache.org/maven)

Alternatively (and this is what POI does) if maven doesn't do what you
need Centipede (http://krysalis.org/centipede) and Forrest
(http://xml.apache.org/forrest) might help.

However it really depends on whether Maven works under gump...

Gump should be one of our top priorities (jakarta.apache.org/gump)
because it could do the builds and site publish for us...

-Andy

Post by Howard M. Lewis Ship
Part of what you discuss may involve having multiple Tapestry modules.
Not good or bad, just a statement.
Yes, and we may need to reorganize things further to reflect the
standard Apache project layout ... if we want to get the synnergy thing
going, we want to make Tapestry "friendly" to other Apache developers.
Renaming packages looks like a big delete-and-add to CVS, so that's a
good time to also reorganize directory structure. We should brainstorm
what that structure should look like.
----- Original Message -----
*Sent:* Sunday, January 12, 2003 11:34 AM
*Subject:* [Tapestry-contrib] Getting back into it
Whoo-ee, I have to say that this past holiday season was the worst
on record for me.
Just before Christmas good friends of ours had a terrible accident
and their little girl was quite badly burned.
It'll be a tough road ahead for their family but everything is relatively ok now.
Also, I had a bit of a health scare myself last week and on top of
all that we have a baby due imminently.
Note: having a baby ids a good thing, it just added to the overall
stress this holiday season!
So, forgive if I've been quite the last while. I'm easing back into
the 'normal' things now...
Glad to see that the Apache thing is rolling along. Kudos to Andy et al!
Looking for something to do Tapestry-wise and I was wondering if
anybody had any thoughts on
the structure for the code base in CVS.
Currently, everything is located under the top-level Tapestry
folder. That incl the framework, vlib, clover, contrib, workbench,
and the
mock opera :-) that Howard has built for testing.
Would it make sense, after the move, the package rename, the Gump
build (don't really understand that) was done
if we examined the structure and split some of it out to the top level?
The current advantage is that one can check out 'Tapestry' and get
everything at once. One disadvantage is that to examine, for
example, the vlib using Spindle is quite difficult.
As I said, I realize there's still a lot of work to do before making
these kind of changes. But I'm willing to play around with this.
Geoff
Geoffrey Longman
Intelligent Works Inc.

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

Andrew C. Oliver

2003-01-12 23:20:25 UTC

Permalink

my bad its jakarta.apache.org/turbine/maven

Post by Andrew C. Oliver
I really recommend Mavenizing to this effect. I bet dion would help
with that.. (http://jakarta.apache.org/maven)
Alternatively (and this is what POI does) if maven doesn't do what you
need Centipede (http://krysalis.org/centipede) and Forrest
(http://xml.apache.org/forrest) might help.
However it really depends on whether Maven works under gump...
Gump should be one of our top priorities (jakarta.apache.org/gump)
because it could do the builds and site publish for us...
-Andy

Post by Howard M. Lewis Ship
Part of what you discuss may involve having multiple Tapestry
modules. Not good or bad, just a statement.
Yes, and we may need to reorganize things further to reflect the
standard Apache project layout ... if we want to get the synnergy
thing going, we want to make Tapestry "friendly" to other Apache
developers.
Renaming packages looks like a big delete-and-add to CVS, so that's a
good time to also reorganize directory structure. We should
brainstorm what that structure should look like.
----- Original Message -----
*To:* Tapestry Contrib
*Sent:* Sunday, January 12, 2003 11:34 AM
*Subject:* [Tapestry-contrib] Getting back into it
Whoo-ee, I have to say that this past holiday season was the worst
on record for me.
Just before Christmas good friends of ours had a terrible accident
and their little girl was quite badly burned.
It'll be a tough road ahead for their family but everything is relatively ok now.
Also, I had a bit of a health scare myself last week and on top of
all that we have a baby due imminently.
Note: having a baby ids a good thing, it just added to the overall
stress this holiday season!
So, forgive if I've been quite the last while. I'm easing back into
the 'normal' things now...
Glad to see that the Apache thing is rolling along. Kudos to Andy et al!
Looking for something to do Tapestry-wise and I was wondering if
anybody had any thoughts on
the structure for the code base in CVS.
Currently, everything is located under the top-level Tapestry
folder. That incl the framework, vlib, clover, contrib, workbench,
and the
mock opera :-) that Howard has built for testing.
Would it make sense, after the move, the package rename, the Gump
build (don't really understand that) was done
if we examined the structure and split some of it out to the top level?
The current advantage is that one can check out 'Tapestry' and get
everything at once. One disadvantage is that to examine, for
example, the vlib using Spindle is quite difficult.
As I said, I realize there's still a lot of work to do before making
these kind of changes. But I'm willing to play around with this.
Geoff
Geoffrey Longman
Intelligent Works Inc.

-------------------------------------------------------
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Tapestry-contrib mailing list
https://lists.sourceforge.net/lists/listinfo/tapestry-contrib

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

Howard M. Lewis Ship

2003-01-12 16:48:34 UTC

Permalink

Where's my manners? Sorry to hear about these rough weeks for you, I hope eveything straightens out.
----- Original Message -----
From: Geoff Longman
To: Tapestry Contrib
Cc: tapestry-dev-sSm70nXyYxXWkAFlN0MkGWD2FQJk+8+***@public.gmane.org
Sent: Sunday, January 12, 2003 11:34 AM
Subject: [Tapestry-contrib] Getting back into it

Whoo-ee, I have to say that this past holiday season was the worst on record for me.
Just before Christmas good friends of ours had a terrible accident and their little girl was quite badly burned.
It'll be a tough road ahead for their family but everything is relatively ok now.

Also, I had a bit of a health scare myself last week and on top of all that we have a baby due imminently.
Note: having a baby ids a good thing, it just added to the overall stress this holiday season!

So, forgive if I've been quite the last while. I'm easing back into the 'normal' things now...

Glad to see that the Apache thing is rolling along. Kudos to Andy et al!

Looking for something to do Tapestry-wise and I was wondering if anybody had any thoughts on
the structure for the code base in CVS.

Currently, everything is located under the top-level Tapestry folder. That incl the framework, vlib, clover, contrib, workbench, and the
mock opera :-) that Howard has built for testing.

Would it make sense, after the move, the package rename, the Gump build (don't really understand that) was done
if we examined the structure and split some of it out to the top level?

The current advantage is that one can check out 'Tapestry' and get everything at once. One disadvantage is that to examine, for example, the vlib using Spindle is quite difficult.

As I said, I realize there's still a lot of work to do before making these kind of changes. But I'm willing to play around with this.

Geoff

Geoffrey Longman
Intelligent Works Inc.

Malcolm Edgar

2003-01-12 23:50:47 UTC

Permalink

Big +1 on the Marvenizing Tapestry.

Post by Geoff Longman
Subject: Re: [Tapestry-contrib] Getting back into it
Date: Sun, 12 Jan 2003 17:07:03 -0500
I really recommend Mavenizing to this effect. I bet dion would help with
that.. (http://jakarta.apache.org/maven)
Alternatively (and this is what POI does) if maven doesn't do what you need
Centipede (http://krysalis.org/centipede) and Forrest
(http://xml.apache.org/forrest) might help.
However it really depends on whether Maven works under gump...
Gump should be one of our top priorities (jakarta.apache.org/gump) because
it could do the builds and site publish for us...
-Andy

Post by Howard M. Lewis Ship
Part of what you discuss may involve having multiple Tapestry modules.
Not good or bad, just a statement.
Yes, and we may need to reorganize things further to reflect the
standard Apache project layout ... if we want to get the synnergy thing
going, we want to make Tapestry "friendly" to other Apache developers.
Renaming packages looks like a big delete-and-add to CVS, so that's a
good time to also reorganize directory structure. We should brainstorm
what that structure should look like.
----- Original Message -----
*To:* Tapestry Contrib
*Sent:* Sunday, January 12, 2003 11:34 AM
*Subject:* [Tapestry-contrib] Getting back into it
Whoo-ee, I have to say that this past holiday season was the worst
on record for me.
Just before Christmas good friends of ours had a terrible accident
and their little girl was quite badly burned.
It'll be a tough road ahead for their family but everything is
relatively ok now.
Also, I had a bit of a health scare myself last week and on top
of
all that we have a baby due imminently.
Note: having a baby ids a good thing, it just added to the overall
stress this holiday season!
So, forgive if I've been quite the last while. I'm easing back
into
the 'normal' things now...
Glad to see that the Apache thing is rolling along. Kudos to
Andy et al!
Looking for something to do Tapestry-wise and I was wondering if
anybody had any thoughts on
the structure for the code base in CVS.
Currently, everything is located under the top-level Tapestry
folder. That incl the framework, vlib, clover, contrib, workbench,
and the
mock opera :-) that Howard has built for testing.
Would it make sense, after the move, the package rename, the
Gump
build (don't really understand that) was done
if we examined the structure and split some of it out to the top
level?
The current advantage is that one can check out 'Tapestry' and
get
everything at once. One disadvantage is that to examine, for
example, the vlib using Spindle is quite difficult.
As I said, I realize there's still a lot of work to do before
making
these kind of changes. But I'm willing to play around with this.
Geoff
Geoffrey Longman
Intelligent Works Inc.

_________________________________________________________________
MSN 8: advanced junk mail protection and 2 months FREE*.
http://join.msn.com/?page=features/junkmail

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

Howard M. Lewis Ship

2003-01-13 12:09:20 UTC

Permalink

To help with Maven, here's some notes about how releases are currently
built. Some of these notes overlap details in the Contributor's Guide, so
you should check that out as well.

The master build file does all the work, reinvoking Ant in many
subdirectories and combining all the results.

I've seen a lot of projects that require you to set environment variables
and/or use a shell script wrapper. I don't get why.

The only thing external to the Tapestry workspace is the directories for a
couple of large, external tools: JBoss, FOP, Saxon and Clover.

JBoss is needed because we build demos that plug into JBoss in a turnkey
way. FOP is for DocBook to PDF. Saxon is for DocBook to HTML or DocBook to
Flow Objects (fed into FOP) ... I use Saxon because it is about 20x faster
than Xalan doing the same job. Clover is proprietary source code coverage
tool.

Getting Ant to use Saxon instead of Xalan requires a few command line
options that can be accomplished via the ANT_OPTS env variable:

ANT_OPTS=-Xmx256mb -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.cri
mson.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=o
rg.apache.crimson.jaxp.SAXParserFactoryImpl

The other three external tools (JBoss, FOP and Clover) are identified in the
build.properties file which must be placed into the config directory. This
file sets three properties needed by the many Ant build scripts:

jboss.dir
fop.dir
clover.dir

Each of these is the absolute path to the respective tool. It is important
to use FORWARD SLASHES ONLY or you will get build errors. I've enclosed a
copy that I use when I do builds.

Clover has kindly donated a copy of their tool to Tapestry; a copy of their
distribution is in the support directory.

The final piece of the puzzle is the disto build script. This is in the
support directory. I typically copy this out to a temporary directory. I
also copy my current build.properties file to the same directory.

The distro build script has two targets. "setup" uses anonymous CVS to grab
a fresh copy of the Tapestry workspace. It uses export, so that the CVS
directories are not exported. This takes about one minute.

"build" copies the build.properties file into the exported workspace and
invokes the "dist" target on the master build file. It then copies the
resulting distro files back up to the current directory. This takes about
nine minutes (on my new, blazing fast laptop, anyway).

Side note: Tapestry has, checked into the repository, copies of DocBook XML
and the DocBook XSL distros. It automatically unpacks these as needed
during the build. We may want to change things to make these addtiional,
external tools as well.

Side note: People have had compatibility issues when using Tapestry JARs
compiled by the 1.4 compiler, even in 1.3 compatibility mode. I currently
set my JAVA_HOME to a JDK 1.3 before doing the build to ensure maximum
compatibility.

Currently, three distro files are created: Tapestry-x.x-core.tar.gz is the
main distribution, containing the compiled JARs, external libraries (such as
OGNL and Log4J) and the source code (packaged into .jar files).

Tapestry-x.x.-doc.tar.gz contains all the documentation for Tapestry;
JavaDoc, Contributor's Guide, and the various manuals (in HTML and PDF).

Tapestry-Web-x.x.tar.gz contains an image of the Tapestry web site, which is
similar to the doc distro, but includes the Clover code coverage report.

Tapestry builds .tar.gz files currently because a) WinZip can open them fine
and b) they are smaller than the equivalent .zip files.

I'm sure there'll be some impedance using Maven, but since Tapestry is
already built to use straight Ant to perform full builds (albiet with a
couple of configuration gotchas) I hope it will not be too tricky.

----- Original Message -----
From: <dion-2ngoU/***@public.gmane.org>
To: "Andrew C. Oliver" <acoliver-1oDqGaOF3Lkdnm+***@public.gmane.org>
Cc: <tapestry-contrib-5NWGOfrQmneRv+***@public.gmane.org>;
<tapestry-dev-***@public.gmane.org>
Sent: Monday, January 13, 2003 4:07 AM
Subject: Re: [Tapestry-contrib] Getting back into it

Post by Andrew C. Oliver
I really recommend Mavenizing to this effect. I bet dion would help
with that.. (http://jakarta.apache.org/maven)

I'm happy to help with Mavenizing, if only for the docs part of the
process. We should also look and see if we can improve the docbook plugin
for Maven (as it's rarely used and a little buggy!), to handle the
existing formats.

Post by Andrew C. Oliver
Alternatively (and this is what POI does) if maven doesn't do what you
need Centipede (http://krysalis.org/centipede) and Forrest
(http://xml.apache.org/forrest) might help.
However it really depends on whether Maven works under gump...

Maven generates viable gump descriptors these days.

Post by Andrew C. Oliver
Gump should be one of our top priorities (jakarta.apache.org/gump)
because it could do the builds and site publish for us...

+1
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
--

<mailto:tapestry-dev-help-***@public.gmane.org>

Howard M. Lewis Ship

2003-01-13 12:45:38 UTC

Permalink

I just want to caution against one thing: Please do not reoganize the
source code directories yet. I know we want to organize the project
structure more like an Apache project and that's fine ... but to do so now
would cripple my ability to cleanly and safely merge in a huge number of
changes from my branch and Mind Bridge is in the same boat with his branch.

Once we put 2.3 to bed, we can merge in code changes into 2.4 and then we
can rename packages and reorganize overall structure.

----- Original Message -----
From: "Howard M. Lewis Ship" <hlship-***@public.gmane.org>
To: "Tapestry development" <tapestry-dev-***@public.gmane.org>
Cc: <tapestry-contrib-5NWGOfrQmneRv+***@public.gmane.org>;
<tapestry-dev-***@public.gmane.org>
Sent: Monday, January 13, 2003 7:09 AM
Subject: Re: [Tapestry-contrib] Getting back into it

Post by Howard M. Lewis Ship
To help with Maven, here's some notes about how releases are currently
built. Some of these notes overlap details in the Contributor's Guide, so
you should check that out as well.
The master build file does all the work, reinvoking Ant in many
subdirectories and combining all the results.
I've seen a lot of projects that require you to set environment variables
and/or use a shell script wrapper. I don't get why.
The only thing external to the Tapestry workspace is the directories for a
couple of large, external tools: JBoss, FOP, Saxon and Clover.
JBoss is needed because we build demos that plug into JBoss in a turnkey
way. FOP is for DocBook to PDF. Saxon is for DocBook to HTML or DocBook to
Flow Objects (fed into FOP) ... I use Saxon because it is about 20x faster
than Xalan doing the same job. Clover is proprietary source code coverage
tool.
Getting Ant to use Saxon instead of Xalan requires a few command line

ANT_OPTS=-Xmx256mb -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.cri
son.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=o

Post by Howard M. Lewis Ship
rg.apache.crimson.jaxp.SAXParserFactoryImpl
The other three external tools (JBoss, FOP and Clover) are identified in the
build.properties file which must be placed into the config directory.

This

Post by Howard M. Lewis Ship
jboss.dir
fop.dir
clover.dir
Each of these is the absolute path to the respective tool. It is important
to use FORWARD SLASHES ONLY or you will get build errors. I've enclosed a
copy that I use when I do builds.
Clover has kindly donated a copy of their tool to Tapestry; a copy of their
distribution is in the support directory.
The final piece of the puzzle is the disto build script. This is in the
support directory. I typically copy this out to a temporary directory. I
also copy my current build.properties file to the same directory.
The distro build script has two targets. "setup" uses anonymous CVS to grab
a fresh copy of the Tapestry workspace. It uses export, so that the CVS
directories are not exported. This takes about one minute.
"build" copies the build.properties file into the exported workspace and
invokes the "dist" target on the master build file. It then copies the
resulting distro files back up to the current directory. This takes about
nine minutes (on my new, blazing fast laptop, anyway).
Side note: Tapestry has, checked into the repository, copies of DocBook XML
and the DocBook XSL distros. It automatically unpacks these as needed
during the build. We may want to change things to make these addtiional,
external tools as well.
Side note: People have had compatibility issues when using Tapestry JARs
compiled by the 1.4 compiler, even in 1.3 compatibility mode. I currently
set my JAVA_HOME to a JDK 1.3 before doing the build to ensure maximum
compatibility.
Currently, three distro files are created: Tapestry-x.x-core.tar.gz is the
main distribution, containing the compiled JARs, external libraries (such as
OGNL and Log4J) and the source code (packaged into .jar files).
Tapestry-x.x.-doc.tar.gz contains all the documentation for Tapestry;
JavaDoc, Contributor's Guide, and the various manuals (in HTML and PDF).
Tapestry-Web-x.x.tar.gz contains an image of the Tapestry web site, which is
similar to the doc distro, but includes the Clover code coverage report.
Tapestry builds .tar.gz files currently because a) WinZip can open them fine
and b) they are smaller than the equivalent .zip files.
I'm sure there'll be some impedance using Maven, but since Tapestry is
already built to use straight Ant to perform full builds (albiet with a
couple of configuration gotchas) I hope it will not be too tricky.
----- Original Message -----
Sent: Monday, January 13, 2003 4:07 AM
Subject: Re: [Tapestry-contrib] Getting back into it

09:07:03

Post by Howard M. Lewis Ship

Post by Andrew C. Oliver
I really recommend Mavenizing to this effect. I bet dion would help
with that.. (http://jakarta.apache.org/maven)

Maven generates viable gump descriptors these days.

Post by Andrew C. Oliver
Gump should be one of our top priorities (jakarta.apache.org/gump)
because it could do the builds and site publish for us...

+1
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
--

Geoff Longman

2003-01-13 12:51:02 UTC

Permalink

Understood. I'm just going to research the change for now.

Geoff
----- Original Message -----
From: "Howard M. Lewis Ship" <hlship-***@public.gmane.org>
To: "Tapestry development" <tapestry-dev-***@public.gmane.org>
Cc: <tapestry-contrib-5NWGOfrQmneRv+***@public.gmane.org>;
<tapestry-dev-***@public.gmane.org>
Sent: Monday, January 13, 2003 7:45 AM
Subject: Maven .... Nightmare

Post by Howard M. Lewis Ship
I just want to caution against one thing: Please do not reoganize the
source code directories yet. I know we want to organize the project
structure more like an Apache project and that's fine ... but to do so now
would cripple my ability to cleanly and safely merge in a huge number of
changes from my branch and Mind Bridge is in the same boat with his branch.
Once we put 2.3 to bed, we can merge in code changes into 2.4 and then we
can rename packages and reorganize overall structure.
----- Original Message -----
Sent: Monday, January 13, 2003 7:09 AM
Subject: Re: [Tapestry-contrib] Getting back into it

DocBook

Post by Howard M. Lewis Ship
to

Post by Howard M. Lewis Ship
Flow Objects (fed into FOP) ... I use Saxon because it is about 20x faster
than Xalan doing the same job. Clover is proprietary source code coverage
tool.
Getting Ant to use Saxon instead of Xalan requires a few command line

ANT_OPTS=-Xmx256mb -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.cri
on.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=o

Post by Howard M. Lewis Ship

Post by Howard M. Lewis Ship
rg.apache.crimson.jaxp.SAXParserFactoryImpl
The other three external tools (JBoss, FOP and Clover) are identified in

the

Post by Howard M. Lewis Ship
build.properties file which must be placed into the config directory.

This

Post by Howard M. Lewis Ship
jboss.dir
fop.dir
clover.dir
Each of these is the absolute path to the respective tool. It is

important

Post by Howard M. Lewis Ship
to use FORWARD SLASHES ONLY or you will get build errors. I've enclosed a
copy that I use when I do builds.
Clover has kindly donated a copy of their tool to Tapestry; a copy of

their

Post by Howard M. Lewis Ship

Post by Howard M. Lewis Ship
also copy my current build.properties file to the same directory.
The distro build script has two targets. "setup" uses anonymous CVS to

grab

Post by Howard M. Lewis Ship
a fresh copy of the Tapestry workspace. It uses export, so that the CVS
directories are not exported. This takes about one minute.
"build" copies the build.properties file into the exported workspace and
invokes the "dist" target on the master build file. It then copies the
resulting distro files back up to the current directory. This takes about
nine minutes (on my new, blazing fast laptop, anyway).
Side note: Tapestry has, checked into the repository, copies of DocBook

XML

Post by Howard M. Lewis Ship
and the DocBook XSL distros. It automatically unpacks these as needed
during the build. We may want to change things to make these addtiional,
external tools as well.
Side note: People have had compatibility issues when using Tapestry JARs
compiled by the 1.4 compiler, even in 1.3 compatibility mode. I currently
set my JAVA_HOME to a JDK 1.3 before doing the build to ensure maximum
compatibility.
Currently, three distro files are created: Tapestry-x.x-core.tar.gz is

the

Post by Howard M. Lewis Ship
main distribution, containing the compiled JARs, external libraries

(such

Post by Howard M. Lewis Ship
as

Post by Howard M. Lewis Ship
OGNL and Log4J) and the source code (packaged into .jar files).
Tapestry-x.x.-doc.tar.gz contains all the documentation for Tapestry;
JavaDoc, Contributor's Guide, and the various manuals (in HTML and PDF).
Tapestry-Web-x.x.tar.gz contains an image of the Tapestry web site,

which

Post by Howard M. Lewis Ship
is

Post by Howard M. Lewis Ship
similar to the doc distro, but includes the Clover code coverage report.
Tapestry builds .tar.gz files currently because a) WinZip can open them

fine

Post by Howard M. Lewis Ship
and b) they are smaller than the equivalent .zip files.
I'm sure there'll be some impedance using Maven, but since Tapestry is
already built to use straight Ant to perform full builds (albiet with a
couple of configuration gotchas) I hope it will not be too tricky.
----- Original Message -----
Sent: Monday, January 13, 2003 4:07 AM
Subject: Re: [Tapestry-contrib] Getting back into it

09:07:03

Post by Howard M. Lewis Ship

Post by Andrew C. Oliver
I really recommend Mavenizing to this effect. I bet dion would help
with that.. (http://jakarta.apache.org/maven)

I'm happy to help with Mavenizing, if only for the docs part of the
process. We should also look and see if we can improve the docbook

plugin

Post by Howard M. Lewis Ship

for Maven (as it's rarely used and a little buggy!), to handle the
existing formats.

Maven generates viable gump descriptors these days.

Post by Andrew C. Oliver
Gump should be one of our top priorities (jakarta.apache.org/gump)
because it could do the builds and site publish for us...

+1
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
--

<mailto:tapestry-dev-help-***@public.gmane.org>
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en

Andrew C. Oliver

2003-01-13 12:59:09 UTC

Permalink

Okay...well if this is going to take awhile... you might want to:

A. check the web pages into CVS so my site script can check them out and
publish them

B. check the version of ant you're using into CVS and provide a shell
script to launch the build with that version of ant so that my site
script can check them out and publish them.

I'd like to get the website migrated over soon as I may not have as much
time shortly.

-Andy

ANT_OPTS=-Xmx256mb -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.cri
son.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=o

Post by Howard M. Lewis Ship
rg.apache.crimson.jaxp.SAXParserFactoryImpl
The other three external tools (JBoss, FOP and Clover) are identified in

the

Post by Howard M. Lewis Ship
build.properties file which must be placed into the config directory.

This

Post by Howard M. Lewis Ship
jboss.dir
fop.dir
clover.dir
Each of these is the absolute path to the respective tool. It is

important

their

Post by Howard M. Lewis Ship
distribution is in the support directory.
The final piece of the puzzle is the disto build script. This is in the
support directory. I typically copy this out to a temporary directory. I
also copy my current build.properties file to the same directory.
The distro build script has two targets. "setup" uses anonymous CVS to

grab

XML

the

Post by Howard M. Lewis Ship
main distribution, containing the compiled JARs, external libraries (such

Post by Howard M. Lewis Ship
similar to the doc distro, but includes the Clover code coverage report.
Tapestry builds .tar.gz files currently because a) WinZip can open them

fine

09:07:03

Post by Howard M. Lewis Ship

Post by Andrew C. Oliver
I really recommend Mavenizing to this effect. I bet dion would help
with that.. (http://jakarta.apache.org/maven)

I'm happy to help with Mavenizing, if only for the docs part of the
process. We should also look and see if we can improve the docbook

plugin

Post by Howard M. Lewis Ship

for Maven (as it's rarely used and a little buggy!), to handle the
existing formats.

Maven generates viable gump descriptors these days.

Post by Andrew C. Oliver
Gump should be one of our top priorities (jakarta.apache.org/gump)
because it could do the builds and site publish for us...

+1
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
--

-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Tapestry-contrib mailing list
https://lists.sourceforge.net/lists/listinfo/tapestry-contrib