On 12/28/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
Odds and ends: 1) I plan to post the following artifacts up for inspection: (i) Distribution artifacts: Framework (as produced by shale-dist): shale-framework-1.0.4.zip Other assemblies: Extras: mailreader-jpa-1.0.4.zip Apps: shale-blank-1.0.4.zip shale-clay-usecases-1.0.4.zip shale-mailreader-1.0.4.zip shale-mailreader-jpa-1.0.4.zip shale-sql-browser-1.0.4.zip shale-usecases-1.0.4.zip
These are the assembly outputs that include the sources and dependent libraries, right? Separately, I see (and agree with you) that you're proposing to include only zips, not .tar.gzs. If that's the future, we might as well rip creating tar.gz files out of the assemblies and save a few more seconds when we run them. (ii) m2 repo artifacts:
POMs: shale-parent-1.0.4.pom shale-apps-parent-1.0.4.pom
Don't we need the POMs for all of the framework jars below as well? Framework jars:
shale-application-1.0.4.jar shale-clay-1.0.4.jar shale-core-1.0.4.jar shale-dialog-1.0.4.jar shale-dialog-basic-1.0.4.jar shale-dialog-scxml-1.0.4.jar shale-remoting-1.0.4.jar shale-spring-1.0.4.jar shale-test-1.0.4.jar shale-tiger-1.0.4.jar shale-tiles-1.0.4.jar shale-validator-1.0.4.jar shale-view-1.0.4.jar Other jars: mailreader-jpa-1.0.4.jar Anything else? 2) We need to update the release notes. I will take a stab at that.
3) We need to update the API stability guide [A]. Craig, as the
original author of that guide, do you want to do this?
Yes, that's been on my mind (with a bit of reorg as well to make things more clear). I'll open a ticket and work on that today. -Rahul Craig [A] http://shale.apache.org/api-stability.html
