Shash:
This is great stuff, thanks!
I've also got the "moves" done (locally) to break the various APIs out
of keel-core (e.g. svc-model-api, svc-persist-api, et al). Maybe we
should get these into this set of releases as well, so we only need to
touch every module once before new releases?
It's mostly "cosmetic" in the sense that it's really just stuff moved
around, not much in the way of actual code changes.
Mike
On Sun, 2005-09-04 at 09:51, Shash Chatterjee wrote:
> All,
>
> I have checked in a large (massive?) update to CVS. There are two
> primary changes, but every module in CVS was updated as a result. The
> primary changes are:
>
> - Updated to latest released Avalon/Excalibur JARs (Framework-4.3,
> Logkit-2.1, Fortress-1.2, Components-2.1).
> - Updated the build system (starting with Keel Maven Plugin 1.3 along
> with keel-container 4.2) to not build a uber JAR for the direct-webapp
> case. Uber JAR is still built as before for all other deployments.
> But, for the huge majority of builds, this makes the assemble process
> much faster. A Maven property that you can put in build.properties,
> "keel.maven.keep.targetdirs=true" (default=false), will not delete
> target/* and allow Maven's dependency checking to speed builds even
> more. But use this with a grain of salt, if you delete classes/config
> files, instead of adding/modifying, you'll want to do a manual "maven
> clean".
>
> A few important notes:
>
> - The old plugin will not work with the new keel-container, and old
> Keel container will not work with new plugin. Must use plugin 1.3 and
> keel-container 4.2.
> - This is only available from CVS, we can release to the repo after we
> have a chance to make sure all of this is stable (maybe a week). If
> using from CVS, make sure to update/get *all* modules from CVS,
> without exception.
> - Make sure you do "maven jar:install" in keel-build first, tool-maven
> second. Then, do "maven plugin:install" in tool-maven-plugin
> - delete the "cache" directory from your local Maven repo.
> - cd to $KEEL_HOME, delete */target (in Unix/Cygwin: find . -name
> target -exec rm -rf {} \;)
> - do "maven multiproject:install"
> - Get fresh "project.xml" from keel-build/example-projects/default or
> hoj as necessary, copy to your project directory (save your old one
> first), and do a "maven clean keel:maven", followed by "maven war".
>
> Hope it works! As usual, let me know if something is broken (big
> chance it might be).
>
> Shash
>
http://keelframework.org/documentation.shtml
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
