On Mon, 2005-04-25 at 23:59 +0200, Vincent Massol wrote: > 1/ Why do we need to use the ear.bundle.dir/ear.bundle.name properties in > our plugin tests? It seems these are the properties causing the problem and
The problem is not on the tests, but in the plugin itself. > I don't see why they are required for testing our cactifyear goal. Is it > possible to change the test to remove the issue altogether? We would need to remove the feature to remove the test. > 2/ If it's not possible (but I would really like to be sure it's not) then > we need to add a check in plugin.jelly to verify that the version of the ear > plugin used is greater or equal to 1.6.1. I was going to commit that change :-) > I'd rather we remove complexity instead of adding it as much as possible > though... It's not really complex, as a tag does the job. > Can we do 1/? I still prefer 2/, as we should be "compatible" with the ear plugin (in fact, I added this change after I project failed because it was lacking such feature). -- Felipe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
