Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
SCXML-84 Added a tutorial about using Commons SCXML on Google Android, based on the stopwatch example. Contributed by: Jakob Sachse <jakobsa AT gmail DOT com> Added Jakob to list of contributors. Thanks for the patch!
Turn off site Javadoc reports that do not work and / or do not add significant value.
TLP related blanket changes: s:jakarta.apache.org/commons:commons.apache.org: s/commons-user@jakarta.apache.org/user@commons.apache.org/ s/commons-dev@jakarta.apache.org/dev@commons.apache.org/ s/Jakarta Commons/Apache Commons/ s:svn.apache.org/viewcvs/jakarta/commons:svn.apache.org/viewvc/commons: s:svn.apache.org/viewcvs.cgi/jakarta/commons:svn.apache.org/viewvc/commons: s:svn.apache.org/viewvc/jakarta/commons:svn.apache.org/viewvc/commons: s:svn.apache.org/repos/asf/jakarta/commons:svn.apache.org/repos/asf/commons: I'd appreciate another pair of eyes on this. There are some categories we probably don't want to change ATM (hopefully, none of these snuck in): * Historicals (proposals etc.) * URLs that shouldn't change (DOCTYPE fragments etc.) * Test cases where namespace URLs matter etc. (I'll track any related nightly failures)
Moving to TLP
Moving back :)
Moving to TLP
Setting the maven repo - apologies if this borks anything
Update license headers in source files per: http://www.apache.org/legal/src-headers.html Associated checkstyle and changelog updates as well.
Remove commons-build dependency on site building. Thanks to Stephen.
Update changes report, move issues to JIRA ids.
Move scxml to proper
- Minor site improvements - Stopped using clover a while back - Readability whitespace adjustments for navigation.xml
Modify maven build to add two non-standard attributes to the jar's manifest file to indicate the values of "maven.compile.source" and "maven.compile.target". Also modify the build to include an "Implementation-Vendor-Id" of "org.apache" in the jar's manifest. The two non-standard entires created in the manifest file will look something like the following: X-Compile-Source-JDK: 1.3 X-Compile-Target-JDK: 1.3 This change serves two purposes: 1) To provide comfort to users regarding JVM compatibility. 2) Enable releases to be checked more easily for JVM compatibility. The manifest specification indicates that "unknown" entries in the manifest file are ignored. These entries have been prefixed with "X-" which is a sometimes used "convention" for indicating non-standard entries. See thread: http://tinyurl.com/839zh
Update changes document and add changes issue template.
The second illustrated usecase for Commons SCXML is Shale dialogs. The content in this commit is just a port of: http://people.apache.org/~rahul/scxml-in-shale/ *time sensitive URL* with some changes based on comments from Craig on dev@struts.
Adding a usecases section - the first concrete usecase for Commons SCXML has been rdc:group.
Use a customized set of checkstyle rules. These are the Sun checks with three changes as discussed on the dev list: 1) Use a regexp header check for ASL 2) Disable 'hide a field' check (lot of noise from setters) 3) Disable 'method design for extension' check
1) Corrected year in license for top level artifacts 2) Added source and wiki links to home page
1) Corrected package declarations 2) Removed author tags from Javadoc 3) Added build and site artifacts (ant as well as maven builds) 4) Propedits for scxml/trunk
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
| apache@apache.org | ViewVC Help |
| Powered by ViewVC 1.1.2 |