A good idea, but definitely something we would need the Maven Dev team to make a decision on... Perhaps one of them is even monitoring this (lengthy) discussion at this point, and will start a discussion on Maven Dev ml if necessary?
I'm not personally convinced that simply appending another version number to an existing version is the "best" way to do it, but it is the generally accepted method. Wayne On 9/20/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
Wayne Fay wrote on Wednesday, September 20, 2006 9:05 AM: >> There is no error in the POM, it in the jar's manifest and > the jar is the one published by the FOP team. >> > > In that case (Markus), take my instructions sent 2mins ago, modify > slightly to adjust the manifest file in the JAR as well as the other > instructions, and proceed to update pom to 0.20.5.1, create bundle for > this version, upload to JIRA, etc. Just a question for the general procedure ... is it really a good idea to produce 0.20.5.1 or should "you" (the Maven team) define special version scheme e.g. 0.20.5-mvn.1, indicating that it is a "fixed" Maven artifact only? While it is unlikely that the FOP team release 0.20.5.1 it might happen for other artifacts. The special scheme would also allow the Maven core to identify and respect such versions better in the dependency resolution (in future). - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
