Large update to CVS
Shash Chatterjee <[email protected]> Sun, 04 Sep 2005 08:51:08 -0500
| Newsgroups | gmane.comp.java.keel.user |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--------------070308060707090601070800
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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
--------------070308060707090601070800
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#6600cc">
All,<br>
<br>
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:<br>
<br>
- Updated to latest released Avalon/Excalibur JARs (Framework-4.3,
Logkit-2.1, Fortress-1.2, Components-2.1).<br>
- 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".<br>
<br>
A few important notes:<br>
<br>
- 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.<br>
- 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.<br>
- Make sure you do "maven jar:install" in keel-build first, tool-maven
second. Then, do "maven plugin:install" in tool-maven-plugin<br>
- delete the "cache" directory from your local Maven repo.<br>
- cd to $KEEL_HOME, delete */target (in Unix/Cygwin: find . -name
target -exec rm -rf {} \;)<br>
- do "maven multiproject:install"<br>
- 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".<br>
<br>
Hope it works! As usual, let me know if something is broken (big
chance it might be).<br>
<br>
Shash<br>
<br>
</body>
</html>
--------------070308060707090601070800--