I'm having a hard time following this discussion, because I'm not
sure of the scope of this problem. Is this a problem that only
impacts our xml configs, and does it only impact the following:
o parentId attribute
o import short form element
o import long form
If there are more places we need to address this problem, I'd like to
get them on the table now.
-dain
On Jan 24, 2006, at 11:52 AM, Aaron Mulder wrote:
All,
There was some IRC talk but not a lot of list response to the configId
versioning issue. Right now, it's kind of holding up 1.0.1 IMHO
because I can't support releasing 1.0.1 until we resolve the
compatibility issue somehow, and there's going to be a fair bit of
work to get it going one way or another. Anyway, for the 1.0.1
release, please indicate your preference for:
[ ] Change all configIds to 1.0 even though it's the 1.0.1 release
[ ] Change all references to use no version and make that work
[ ] Something else (please explain)
For the second option, that means the configId for module would still
be geronimo/foo/1.0.1/car but any parentId, import, or GBean reference
would look like this:
parentId="geronimo/foo//car"
<import>geronimo/foo//car</import>
<import>
<groupId>geronimo</groupId>
<artifactId>foo</artifactId>
<type>car</type>
</import>
That is, the version would be omitted from the reference, and we'd
somehow interpret that to mean "whatever version is present" or "use
most current version". You still *could* use a specific version, we'd
just emphasize the version-less option for maximum compatibility. I
think this alternative would require more work but might be a better
fit for a long-term strategy.
Thanks,
Aaron
