The first error is self explanatory. I've always planned on adding
inter-module dependencies with version compatibility checking. Having
consistent version numbers is important.  Perhaps we need a better
discussion on what a versoin number should look like and how they can
be compared.

Second is probably because your didn't quote your version number properly?


----- Original Message -----
From: Pablo Lalloni <[EMAIL PROTECTED]>
Date: Fri, 02 Jul 2004 18:18:40 -0300
Subject: Errors in module version validation
To: hivemind-dev <[email protected]>

I'm seeing a lot of these after updating to the last 1.0-beta-1-snapshot:


18:00:26,419 ERROR [DescriptorParser] Error at
jar:file:/tmp/pampa-administrador-web/tmp/deploy/tmp3577logging-1.0.jar!/META-INF/hivemodule.sdl,
line 1, column 1: Attribute version (1.0) of element module is
improperly formatted. Version numbers should be a sequence of three
numbers seperated by periods.
HiveMind informs of this in the log but it does not fail and it works
ok (although it's logged on ERROR level, it should be in WARN if it's
gonna keep working anyway).

Now if I change the version attribute to something like "1.0.0"
registry construction FAILS saying:


18:10:11,571 ERROR [RegistryBuilder] Error: Unable to read descriptor
jar:file:/tmp/pampa-administrador-web/tmp/deploy/tmp3595pampa-transaction-1.0-SNAPSHOT.jar!/META-INF/hivemodule.sdl:
Error parsing 
jar:file:/tmp/pampa-administrador-web/tmp/deploy/tmp3595pampa-transaction-1.0-SNAPSHOT.jar!/META-INF/hivemodule.sdl:
Encountered ".0" at line 4, column 61.
Was expecting one of:
    <SIMPLE_ID> ...
    ")" ... 
Besides the bug, is there a reason to validate the format of the
module's version attribute? Isn't this supposed to be dependant on
project's specific versioning schema?

Cheers!
PiL 



-- 
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to