You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship" <hl...@attbi.com> on 2003/03/11 01:51:32 UTC
Building Tapestry from CVS
Much of this detail is in the Contributor's Guide, I'm working to update it
fully refect the latest stuff.
You need to build.properties file in the config directory, specifying where
JBoss 3.0.4 (jboss.dir), Jetty 4.x (jetty.dir) and Clover (clover.dir) have
been installed.
You need the following in the Tapestry/ext-dist directory:
docbkx412.zip
docbook-xsl-1.59.2.zip
jcommon-0.6.5.jar
jdom-b8.jar
jfreechart-0.9.2.jar
junit.jar
The README there defines where to get most of those.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry
> -----Original Message-----
> From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> Sent: Monday, March 10, 2003 7:45 PM
> To: Tapestry development
> Subject: RE: Location of incubated downloads?
>
>
> Yep, but running
>
> ant dist
>
> Just gave me lots of compile errors.
>
> Ok, what is it that a user gets from a tapestry build - a
> single jar? A
> war file with demos? A runnable jetty installation?
>
> I'm trying to understand what the build produces for a user
> of tapestry. I
> get the part about a distribution being produced, but it's
> what's inside
> it that matters to me. i.e. users will need
> tapestry-framework.jar and
> ....
>
> Get me?
> --
> dIon Gillard, Multitask Consulting
> Blog: http://www.freeroller.net/page/dion/Weblog
> Work: http://www.multitask.com.au
>
>
> "Howard M. Lewis Ship" <hl...@attbi.com> wrote on 11/03/2003
> 11:19:10 AM:
>
> > Hm? Tapestry creates a -bin and a -src distribution.
> >
> > Each contains hundreds of files.
> >
> > Everything is built from the top-level build.xml. "ant dist" chugs
> along
> > for about eight minutes and produces Tapestry-xxx-bin.tar.gz and
> > Tapestry-xxx-src.tar.gz.
> >
> > --
> > Howard M. Lewis Ship
> > Creator, Tapestry: Java Web Components
> > http://jakarta.apache.org/proposals/tapestry
> >
> >
> >
> > > Maven can do the above. But there are probably easier ways of
> > > doing it.
> > >
> > > How many 'deliverables' are there from the ant build? Is
> it just one
> > > tapestry jar file, or are there other things produced as
> part of the
> > > build.
> > >
> > > I'll check tapestry out of cvs and see what I can do to help.
> > > --
> > > dIon Gillard, Multitask Consulting
> > > Blog: http://www.freeroller.net/page/dion/Weblog
> > > Work: http://www.multitask.com.au
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> tapestry-dev-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
RE: Building Tapestry from CVS
Posted by di...@multitask.com.au.
So how about I treat the framework jar as the 'main' deliverable for
Tapestry.
Do the unit tests in junit/ only refer to framework/ code?
I'm thinking that 'Tapestry' is actually a few different deliverables:
- framework jar with unit tests (incl coverage) and docs,
- Lots of examples/demos each a separate build, and
- Lots of contrib'ed code each a separate build.
Where the examples/demos/contrib code rely on framework jar. Is this
roughly right?
In Maven each of the separately buildable bits (example/demo, contrib etc)
is a 'project' with a descriptor.
Maven has some basic support for docbook (which would be good to make work
properly).
Did anyone check out the default site built from the project.xml?
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
"Howard M. Lewis Ship" <hl...@attbi.com> wrote on 11/03/2003 01:56:49 PM:
> Other stuff is needed to build some of the demos, which make use of JMX
and
> JBoss specific extensions.
>
> Clover shows up to build the code coverage report.
>
> The docbook stuff, yes, for building documentation (using FOP).
>
> jdom is used as part of the unit tests. The code coverage report is
built
> on top of the unit tests.
>
> jfreechart and jcommon for building the Workbench example.
>
> Think you are on the money for the rest.
>
> --
> Howard M. Lewis Ship
> Creator, Tapestry: Java Web Components
> http://jakarta.apache.org/proposals/tapestry
>
>
>
> > -----Original Message-----
> > From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> > Sent: Monday, March 10, 2003 9:52 PM
> > To: Tapestry development
> > Subject: Re: Building Tapestry from CVS
> >
> >
> > "Howard M. Lewis Ship" <hl...@attbi.com> wrote on 11/03/2003
> > 11:51:32 AM:
> >
> > > Much of this detail is in the Contributor's Guide, I'm working to
> > > update
> > it
> > > fully refect the latest stuff.
> > >
> > > You need to build.properties file in the config directory,
> > specifying
> > where
> > > JBoss 3.0.4 (jboss.dir), Jetty 4.x (jetty.dir) and Clover
> > (clover.dir)
> > have
> > > been installed.
> >
> > What does Tapestry need JBoss, Jetty and Clover for?
> >
> > The framework directory builds a jar nicely without them.
> >
> > > You need the following in the Tapestry/ext-dist directory:
> > >
> > > docbkx412.zip
> > > docbook-xsl-1.59.2.zip
> > For building documentation?
> >
> > > jcommon-0.6.5.jar
> > Charts for a demo app?
> >
> > > jdom-b8.jar
> > Not sure.
> >
> > > jfreechart-0.9.2.jar
> > Charts for a demo app?
> >
> > > junit.jar
> > For the unit tests.
> >
> > > The README there defines where to get most of those.
> > But not where they're used.
> >
> > e.g. on a per directory basis:
> > bin - empty
> > config - various set up files for build, demo, runtime?
> > doc - docbook source for documentation
> > eclipse - developer files for developing/debugging tapestry
> > in eclipse examples - example tapestry web apps? ext-dist -
> > directory to hold external jars framework - the java source
> > for the tapestry framework img-src - images in photoshop
> > format junit - unit test source lib - compile and runtime
> > jars being distributed package-lists - for javadoc support -
> > various development scripts web - dunno - looks like static
> > resources for the web site
> >
> > Is this close?
> > --
> > dIon Gillard, Multitask Consulting
> > Blog: http://www.freeroller.net/page/dion/Weblog
> > Work: http://www.multitask.com.au
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
RE: Building Tapestry from CVS
Posted by "Howard M. Lewis Ship" <hl...@attbi.com>.
Other stuff is needed to build some of the demos, which make use of JMX and
JBoss specific extensions.
Clover shows up to build the code coverage report.
The docbook stuff, yes, for building documentation (using FOP).
jdom is used as part of the unit tests. The code coverage report is built
on top of the unit tests.
jfreechart and jcommon for building the Workbench example.
Think you are on the money for the rest.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry
> -----Original Message-----
> From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> Sent: Monday, March 10, 2003 9:52 PM
> To: Tapestry development
> Subject: Re: Building Tapestry from CVS
>
>
> "Howard M. Lewis Ship" <hl...@attbi.com> wrote on 11/03/2003
> 11:51:32 AM:
>
> > Much of this detail is in the Contributor's Guide, I'm working to
> > update
> it
> > fully refect the latest stuff.
> >
> > You need to build.properties file in the config directory,
> specifying
> where
> > JBoss 3.0.4 (jboss.dir), Jetty 4.x (jetty.dir) and Clover
> (clover.dir)
> have
> > been installed.
>
> What does Tapestry need JBoss, Jetty and Clover for?
>
> The framework directory builds a jar nicely without them.
>
> > You need the following in the Tapestry/ext-dist directory:
> >
> > docbkx412.zip
> > docbook-xsl-1.59.2.zip
> For building documentation?
>
> > jcommon-0.6.5.jar
> Charts for a demo app?
>
> > jdom-b8.jar
> Not sure.
>
> > jfreechart-0.9.2.jar
> Charts for a demo app?
>
> > junit.jar
> For the unit tests.
>
> > The README there defines where to get most of those.
> But not where they're used.
>
> e.g. on a per directory basis:
> bin - empty
> config - various set up files for build, demo, runtime?
> doc - docbook source for documentation
> eclipse - developer files for developing/debugging tapestry
> in eclipse examples - example tapestry web apps? ext-dist -
> directory to hold external jars framework - the java source
> for the tapestry framework img-src - images in photoshop
> format junit - unit test source lib - compile and runtime
> jars being distributed package-lists - for javadoc support -
> various development scripts web - dunno - looks like static
> resources for the web site
>
> Is this close?
> --
> dIon Gillard, Multitask Consulting
> Blog: http://www.freeroller.net/page/dion/Weblog
> Work: http://www.multitask.com.au
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
Re: Building Tapestry from CVS
Posted by di...@multitask.com.au.
"Howard M. Lewis Ship" <hl...@attbi.com> wrote on 11/03/2003 11:51:32 AM:
> Much of this detail is in the Contributor's Guide, I'm working to update
it
> fully refect the latest stuff.
>
> You need to build.properties file in the config directory, specifying
where
> JBoss 3.0.4 (jboss.dir), Jetty 4.x (jetty.dir) and Clover (clover.dir)
have
> been installed.
What does Tapestry need JBoss, Jetty and Clover for?
The framework directory builds a jar nicely without them.
> You need the following in the Tapestry/ext-dist directory:
>
> docbkx412.zip
> docbook-xsl-1.59.2.zip
For building documentation?
> jcommon-0.6.5.jar
Charts for a demo app?
> jdom-b8.jar
Not sure.
> jfreechart-0.9.2.jar
Charts for a demo app?
> junit.jar
For the unit tests.
> The README there defines where to get most of those.
But not where they're used.
e.g. on a per directory basis:
bin - empty
config - various set up files for build, demo, runtime?
doc - docbook source for documentation
eclipse - developer files for developing/debugging tapestry in eclipse
examples - example tapestry web apps?
ext-dist - directory to hold external jars
framework - the java source for the tapestry framework
img-src - images in photoshop format
junit - unit test source
lib - compile and runtime jars being distributed
package-lists - for javadoc
support - various development scripts
web - dunno - looks like static resources for the web site
Is this close?
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au