Author: hlship
Date: Fri May 5 09:20:31 2006
New Revision: 400100
URL: http://svn.apache.org/viewcvs?rev=400100&view=rev
Log:
More report setup for Tapestry 5
Modified:
tapestry/tapestry5/tapestry-core/trunk/pom.xml
tapestry/tapestry5/tapestry-core/trunk/src/site/apt/index.apt
Modified: tapestry/tapestry5/tapestry-core/trunk/pom.xml
URL:
http://svn.apache.org/viewcvs/tapestry/tapestry5/tapestry-core/trunk/pom.xml?rev=400100&r1=400099&r2=400100&view=diff
==============================================================================
--- tapestry/tapestry5/tapestry-core/trunk/pom.xml (original)
+++ tapestry/tapestry5/tapestry-core/trunk/pom.xml Fri May 5 09:20:31 2006
@@ -68,4 +68,19 @@
</plugin>
</plugins>
</build>
+ <reporting>
+ <plugins>
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>surefire-report-maven-plugin</artifactId>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-javadoc-plugin</artifactId>
+ <configuration>
+ <linksource>true</linksource>
+ </configuration>
+ </plugin>
+ </plugins>
+ </reporting>
</project>
Modified: 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=400100&r1=400099&r2=400100&view=diff
==============================================================================
--- tapestry/tapestry5/tapestry-core/trunk/src/site/apt/index.apt (original)
+++ tapestry/tapestry5/tapestry-core/trunk/src/site/apt/index.apt Fri May 5
09:20:31 2006
@@ -6,38 +6,3 @@
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
