Hi Todd.
> Ok. I will refocus here. Let me just say that this discussion is > inevitable. It is important as the value of CD will help determine if Maven > should consider working towards supporting this kind of process. The basic > architecture of Maven today does not lend well to it. So we can table it > for now. You comments I think took what I am trying to get across very much > out of context but *snip* them for now and defer the discussion to a later > date. > My apologies - I realize it's somewhat unfair of me to say I don't want to discuss the value proposition any more and then dissect a bunch of what you said. I guess I have been explaining the value proposition quite a lot recently and would like to get back to some more technical stuff, but that is my problem, not yours. Having said that, I wrote something which you may find interesting here: http://www.informit.com/articles/article.aspx?p=1641923 - it has a bunch of links to other stuff too. > The final artifacts and all the meta do not represent what is considered a > released artifact. The meta data is different and the artifact names are > different. So the release process would have to "massage" the snapshot > artifacts to "look" like releases. This will of course invalidate much of > the testing done by your CI. > So long as I don't change the actual binaries, how does this invalidate the testing? All I'm doing is adding some more metadata (in the form of changing the names, doing tagging, or whatever) > When I say meta data here, I am referring to the meta data maven stores > about the artifact. This information doesn't appear in the pom. > I must admit my ignorance here - I thought Maven stored metadata about the artifact in the form of pom files (e.g. this one: http://repo2.maven.org/maven2/HTTPClient/HTTPClient/0.3-3/HTTPClient-0.3-3.pom ) > Also if you do this you will be breaking the idea of CI. If your > dependencies point to specific time stamp then that build won't be getting > the latest version of those dependencies. You'd need some process to > constantly update the pom to always point to the latest version of all your > dependencies. This I think would be fairly complex as your pom files would > be constantly changing, even if you as a developer didn't need to change it. > > So the idea is that the pom files for the build just point to the upstream snapshot as happens right now. However when the build artifact is created as part of the CI process, the pom that is created with it also includes the information about exactly which versions of these snapshots were used, including the version in version control they were created from. You can then re-use the same binaries you created from CI throughout the rest of your delivery process. -- Jez Humble Co-author, *Continuous Delivery <http://continuousdelivery.com/>* http://continuousdelivery.com/ http://jezhumble.net/ -- View this message in context: http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-tp3245370p3255684.html Sent from the Maven - Users mailing list archive at Nabble.com.
