Nope; this is about Tapestry 5, not about earlier releases.

I do think that this is a better structure however, especially in
terms of building the appliations using Eclipse.  Next to
tapestry5/tapestry-core and tapestry5/tapestry-project will eventually
be others: tapestry-components, tapestry-portlet, tapestry-hibernate,
etc.

I'd like to see 4.1 organized the same way.

The biggest impediment is the existing documentation. I've been
working on the HiveMind code base, and have an XSLT to convert from
Forrest to XDoc (Maven's format).

On 5/4/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Howard -

  Does this mean I should drop work on integrating the 3 branches + site
into a single maven build [site == 'site' project/component]?

[EMAIL PROTECTED] wrote:
> Author: hlship
> Date: Thu May  4 10:11:38 2006
> New Revision: 399775
>
> URL: http://svn.apache.org/viewcvs?rev=399775&view=rev
> Log:
> Start building documentation.
>
> Added:
>     tapestry/tapestry5/tapestry-core/trunk/src/site/
>     tapestry/tapestry5/tapestry-core/trunk/src/site/apt/
>     tapestry/tapestry5/tapestry-core/trunk/src/site/apt/index.apt
>     tapestry/tapestry5/tapestry-core/trunk/src/site/apt/upgrade.apt
>     tapestry/tapestry5/tapestry-core/trunk/src/site/resources/
>     tapestry/tapestry5/tapestry-core/trunk/src/site/resources/images/
>     
tapestry/tapestry5/tapestry-core/trunk/src/site/resources/images/asf_logo_wide.gif 
  (with props)
>     tapestry/tapestry5/tapestry-core/trunk/src/site/site.xml
> Modified:
>     tapestry/tapestry5/tapestry-core/trunk/pom.xml
>
> Modified: tapestry/tapestry5/tapestry-core/trunk/pom.xml
> URL: 
http://svn.apache.org/viewcvs/tapestry/tapestry5/tapestry-core/trunk/pom.xml?rev=399775&r1=399774&r2=399775&view=diff
> ==============================================================================
> --- tapestry/tapestry5/tapestry-core/trunk/pom.xml (original)
> +++ tapestry/tapestry5/tapestry-core/trunk/pom.xml Thu May  4 10:11:38 2006
> @@ -6,6 +6,7 @@
>      <artifactId>tapestry-core</artifactId>
>      <packaging>jar</packaging>
>      <version>5.0.0</version>
> +    <!-- This should change to tapestry-project -->
>      <parent>
>          <groupId>com.javaforge.tapestry</groupId>
>          <artifactId>common</artifactId>
>
> Added: tapestry/tapestry5/tapestry-core/trunk/src/site/apt/index.apt
> URL: 
http://svn.apache.org/viewcvs/tapestry/tapestry5/tapestry-core/trunk/src/site/apt/index.apt?rev=399775&view=auto
> ==============================================================================
> --- tapestry/tapestry5/tapestry-core/trunk/src/site/apt/index.apt (added)
> +++ tapestry/tapestry5/tapestry-core/trunk/src/site/apt/index.apt Thu May  4 
10:11:38 2006
> @@ -0,0 +1,43 @@
> + ----
> + tapestry-core
> + ----
> +
> +Description
> +
> +  The core module of Tapestry provides the interfaces and annocations that 
form the Tapestry API.
> +  It also includes the core implementations and and internal code.
> +
> +Public vs. Internal
> +
> +  An issue plaguing previous versions of Tapestry was the lack of a clear 
deliniator
> +  between private, internal APIs and public, external APIs.  The fact that 
your code would extend
> +  from base objects but that many of the methods on those base objects were "off 
limits"
> +  further confused the issue. This has been identified as a key factor in the
> +  "steep learning curve of Tapestry" myth.
> +
> +  With the clean slate of Tapestry 5, we are being much more ruthless about 
internal vs. external.
> +
> +  First of all, anything inside the org.apache.tapestry.internal package
> +  is <<internal>>.  It is part of the implementation of Tapestry.  It is the 
man behind the curtain.
> +  You should not ever need to directly use this code.  It is a <<bad idea>> 
to do so, because
> +  internal code may <<change from one release to the next>> without concern 
for backwards
> +  compatibility.
> +
> +Backwards Compatibility
> +
> +  Tapestry has been plagued by backwards compatibility problems with every 
major release. Tapestry 5
> +  does not even attempt to be backards compatible to Tapestry 4. Instead, it 
lays the ground work for
> +  true backwards compatibility going forwards.
> +
> +  Tapestry 5's API is based almost entirely on <annotations>.  You will 
annotate classes to indicate that
> +  they are components, you will annotate fields to allow Tapestry to 
maintain their state or to allow Tapestry
> +  to inject resources, and you will annotate methods to tell Tapestry when 
and if a method should be invoked.
> +
> +  Tapestry will adapt to your classes. It will call your methods, passing in 
values via method parameters.
> +  Instead of the rigidness of a fixed interface to implement, Tapestry will 
simply adapt to your classes, using
> +  the hints provided by the annotations.
> +
> +  Because of this, Tapestry will be able to change internally to a great 
degree without it affecting any
> +  of the application code <you> write. This should finally crack the 
backwards compatibility nut, allowing you to have
> +  great assurance that you can upgrade to future releases of Tapestry 
without breaking your existing applications.
> +
> \ No newline at end of file
>
> Added: tapestry/tapestry5/tapestry-core/trunk/src/site/apt/upgrade.apt
> URL: 
http://svn.apache.org/viewcvs/tapestry/tapestry5/tapestry-core/trunk/src/site/apt/upgrade.apt?rev=399775&view=auto
> ==============================================================================
> --- tapestry/tapestry5/tapestry-core/trunk/src/site/apt/upgrade.apt (added)
> +++ tapestry/tapestry5/tapestry-core/trunk/src/site/apt/upgrade.apt Thu May  
4 10:11:38 2006
> @@ -0,0 +1,16 @@
> +  ----
> +  Upgrading from Tapestry 4 to Tapestry 5
> +  ----
> +
> +Upgrading from Tapestry 4 to Tapestry 5
> +
> + There is no simple, direct upgrade path from Tapestry 4 to Tapestry 5.
> +
> + Tapestry 5 represents a completely new code base. Although it maintains the 
<spirit> of
> + Tapestry 4, it is also a quantum leap ahead of Tapestry 4.
> +
> + A lot of the familiar aspects of Tapestry are completely different between 
the two releases.
> + In other cases, core concepts remain, but the details, names, and 
implementations
> + have changed.
> +
> + More to come ...
> \ No newline at end of file
>
> Added: 
tapestry/tapestry5/tapestry-core/trunk/src/site/resources/images/asf_logo_wide.gif
> URL: 
http://svn.apache.org/viewcvs/tapestry/tapestry5/tapestry-core/trunk/src/site/resources/images/asf_logo_wide.gif?rev=399775&view=auto
> ==============================================================================
> Binary file - no diff available.
>
> Propchange: 
tapestry/tapestry5/tapestry-core/trunk/src/site/resources/images/asf_logo_wide.gif
> ------------------------------------------------------------------------------
>     svn:mime-type = application/octet-stream
>
> Added: tapestry/tapestry5/tapestry-core/trunk/src/site/site.xml
> URL: 
http://svn.apache.org/viewcvs/tapestry/tapestry5/tapestry-core/trunk/src/site/site.xml?rev=399775&view=auto
> ==============================================================================
> --- tapestry/tapestry5/tapestry-core/trunk/src/site/site.xml (added)
> +++ tapestry/tapestry5/tapestry-core/trunk/src/site/site.xml Thu May  4 
10:11:38 2006
> @@ -0,0 +1,20 @@
> +<?xml version="1.0" encoding="ISO-8859-1"?>
> +<project name="Tapestry Core">
> +    <bannerLeft>
> +        <name>Tapestry</name>
> +        <href>http://tapestry.apache.org/</href>
> +    </bannerLeft>
> +    <bannerRight>
> +        <name>Apache</name>
> +        <href>http://www.apache.org</href>
> +        <src>images/asf_logo_wide.gif</src>
> +    </bannerRight>
> +    <body>
> +        <links>
> +            <item name="Apache" href="http://www.apache.org/"/>
> +        </links>
> +        <menu name="Tapestry Core">
> +            <item name="Introduction" href="index.html"/>
> +            <item name="Upgrade from Tapestry 4" href="upgrade.html"/>
> +        </menu> ${reports} </body>
> +</project>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)

iD8DBQFEWkMKaCoPKRow/gARAscRAJwMwvEPA6/O0s0mzH/k1T0hPMeAcACdEo9r
zee25/e9enuTrn+C++HZj+g=
=fVbY
-----END PGP SIGNATURE-----

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




--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Jakarta HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

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

Reply via email to