David Jencks wrote:
On Oct 17, 2005, at 10:48 AM, David Sean Taylor wrote:
Does anyone know a way to automate the deleting of the plugin cache
during the build?
I'm wondering why you run into this problem... Do you build a plugin
and try to use it during the same maven multiproject build? What
relationship do the resources have to the plugin? Parameterized sources
for the use of the plugin? Scripts that are used to build the plugin?
Scripts that are run when the plugin is used?
All of these questions, I didn't expect the Maven Inquisition :)
We store resources in the plugin such as SQL scripts, and basically
everything under the src/webapp directory. Its part of our recent "Eat
our own Dogfood Initiative". Quite tasty really, until you choke on a
cached bone.
To complicate matters, I have M3 and M4 projects of Jetspeed on this
machine. So if I need to switch between M3 and M4 or visa versa, I have
scripts to clear the Maven cache and then rebuild and install
(plugin:install) the plugin.
Sometimes the cached files break, and I have zero length cache files.
I'm pretty used to that. Sometimes the Maven Plugin for Eclipse holds on
to resources, thats usually a tough one.
I know how to handle most of these maven cache issues, although
sometimes it can stump me for a bit. Yesterday I had several of my
client/developers all having Maven build/plugin related issues *all at
once*, and I was ready to throw Maven out the door. Hell, we are using a
deadend version (1.x), whereas version 2 doesn't fully support our
current Jelly scripts. Solution from Maven team: rewrite your plugin in
Java. Im sorry, please don't take any offence, but its just not good enough.
--
David Sean Taylor
Bluesunrise Software
[EMAIL PROTECTED]
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
