Jeremy,
> > Anyone have a preference as to where to deploy the M1 stuff? I think > > Sebastian had deployed something to his public_html dir. Does it make > > sense to just put the released stuff there as well for now? (until M2) > > people.apache.org has limited resources available and is not a suitable > place for a long-lived distribution. Right, which is why I say make sure it's fixed for milestone 2 and once M2 is out, kill it. Basically, let anyone use it know it's only temporary. > We should really push this into the mirror system. If maven can't handle > this kind of version label then perhaps we should respin the release > with a different version id or perhaps not worry about it. Is it only > "latest" versioning that is problematic? Will the typical "exact" > version matching still work? "Exact" match would still work, but that's NOT the typical case for the plugins. For example, I don't think we define explicit version numbers for ANY of our plugins that we use like surefire, compiler, jar, javadoc, etc.... The big issue this causes if people use the Tuscany code generation plugins. They will ALWAYS from now until forever be forced to use an explicit version number, which isn't normal, and pretty much just sucks. In any case, if we HAVE to push it to ibiblio, I would suggest re-building it with a real version number. It will cause a lot less headaches later. However, if we can wait till M2, that might be easier. (since changing the version number is a pretty big thing. It's burned into a bunch of places like html files and such.) -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 F:781-902-8001 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
