if the developer just completed the code but the artifact did'nt execute and pass all the test-suites tag as alpha so the user community know thats its dicey at best artifact-version-alpha-1
if the artifact passes muster (no errors and no failures) with all the test suites (surefire) then tag it as beta artifact-version-beta-2 if someone wants a build right now the artifact developer can release immediately as snapshot artifact-version-snapshot if the artifactId is blessed by more than the developer then you can tag as RC e.g. artifact-version-RC1 the idea behind version controlled build environments (such as maven) is the developer can request a specific artifact for example: e.g. user pings author to request artifact-A will incorporate function X developer factors code to implement function X author releases artifact-version-snapshot all the other developers know that referencing an alpha or beta or snapshot is dicey and should not pollute their production builds when the developer finally sees the artifact version has been promoted to RC (release candidate) they can reference the Release Candidate in their production builds this is my understanding of how maven contributes to the SDLC process. Take a look at configuring classifier for use in a qualified artifact for implementation details http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-platform-classifier.html Bedankt Martin ______________________________________________ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Subject: Re: force maven to redownload/refresh "released" dependencies > From: [email protected] > Date: Fri, 6 Aug 2010 18:28:32 -0500 > To: [email protected] > > On Aug 6, 2010, at 6:16 PM, Ron Wheeler wrote: > > > On 06/08/2010 5:56 PM, Haszlakiewicz, Eric wrote: > >>> -----Original Message----- > >>> From: Ron Wheeler [mailto:[email protected]] > >>>> I'm AGREEING with you that the solution is to wipe out the local > >>>> artifact! But you can only do that once you know there is something > >>>> wrong. How do you detect that the artifact has changed? > >>> If you can not deploy the release, that will tell you that you are > >>> trying to rerelease an artifact. > >>>> Maybe you'll get lucky and something is different enough in your > >>>> artifact that the build process fails. > >>> Your attempt to deploy will fail. That will tell you right away that > >> you > >>> are doing the wrong thing. > >> No, the deployment of a project that USES a changed artifact will NOT > >> fail. > > > > Yes. > > That is why releases can not be replaced. > > In your case, you should have deleted the wrong artifacts and loaded them > > with new versions. > > And informed the victims that they needed to update their dependencies. > > > > You were completely in control of the versions and names. > > And, frustrating though it is, that's what I've done when my bad QC has > released bad stuff onto Central. You just put out another version and > apologize on the web page. There's not a lot else to do, and it's not that > bad. > > -K > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
