Frederic Simon wrote:
> Let's hope promotion will be used more often by OSS libraries (and 
> Maven plugins). Everyone will benefit and we will start using version 
> ranges without being scare of tomorrow new version of log4j :)
I thought sl4j is the new evil :-)
> The idea is that when you develop something based on log4j, you can 
> use "test" or even "bleeding" level artifacts, and so new open 
> libraries versions have a good level of global worldwide acceptance 
> before being promoted "stable".
>
> BTW: We did the "Full Monty" with Hudson (Promote builds and 
> dependencies as bulks) and we will show it at Devoxx :)
The thing I am imagining is a set of test suites at the top level, doing 
end-to-end testing on things like large web applications or maybe just 
below targeting the appservers, database engines etc. If all projects 
are set up with open dependencies, then a new release of something like 
log4j should trigger a large amount of builds downstream, up to the 
point of the distribution test suites. If all that succeeds, then 
chances are good that the new release is not only reasonably stable but 
also backwards-compatible. Of course no testing is perfect, but with a 
growing test suite confidence could rise.

But I guess I'm preaching to the choir :-)

   Peter



On Tue, Nov 10, 2009 at 1:01 PM, Peter Becker <peter.becker.de 
<http://peter.becker.de>@gmail.com <http://gmail.com>> wrote:
>
>
>     I keep thinking what we need are Maven distributions. Or at least
>     one of
>     them.
>
>     The big feature distributions add to the Linux world is that they
>     do QA
>     and select packages that work together. No one does this in the Maven
>     world -- at least not that I am aware of.
>
>     I don't think it is a technology issue, though. For me it seems more a
>     social issue: we would need some kind of people who are willing to do
>     the work (and work there is) and who would be trusted by others.
>     Ideally
>     there would be external test suites, checking dependencies
>     throughout a
>     whole stack (Hudson can be fun for such things).
>
>     Sometimes I think it would be a good thing for a larger Java shop
>     to do:
>     streamline your in-house Java development with well-tested tools and
>     publish the results as open distribution, which gives you respect and
>     further testing. But it would require at least a full-time position,
>     probably more.
>
>       Peter
>
>
>
>     Frederic Simon wrote:
>     > My first big Maven 2 project was in 2005, and since then nothing
>     > changed: I'm still amazed by the lack of version management and
>     > promotion we used to have with Linux Debian "apt-get" in 1999!!
>     >
>     > The Debian guys understood perfectly what "bleeding", "test",
>     "stage",
>     > and "release" really means. And 10 years after, we still don't have
>     > anything comparable in Maven??
>     >
>     > Anyway, we (at JFrog) worked on trying to solve this issue in
>     > Artifactory
>     >
>     http://blogs.jfrog.org/2009/11/search-based-promotion-staging-and.html
>     > ,
>     >  but the response so far can be qualified of "mild" :)
>     >
>     > I'm thinking: "Am I the only crazy guy out there annoyed by this?"
>     > >
>     >
>
>
>
>
>
>
> -- 
> Co. Founder and Chief Architect
> JFrog Ltd
> 5 Habonim st., P.O.Box 8187
> Netanya, Israel 42504.
> Tel: +972 9 8941444    
> Fax: +972 9 8659977
> http://www.jfrog.org/
> http://twitter.com/freddy33
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "The 
Java Posse" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to