Ive done this, not sure if it fixes any thing: Trying to fix <uniqueVersion>false</uniqueVersion> problem added it to non snapshot repos aswell
However it did look ok for snapshot versions, they had unique version set to false.. 2009/12/9 nino martinez wael <[email protected]> > Yup, and theres two places on wicketstuff core it's not set, so it default > to true! Which are the opposite of what we want.. I'll fix it for > wicketstuff.. But what about Wicket itself, I dont have commit rights? > > 2009/12/9 Marat Radchenko <[email protected]> > > That's controlled with <uniqueVersion> >> >> 2009/12/9 nino martinez wael <[email protected]>: >> > Yeah it seems strange, some project seems not to have the issue: >> > >> > >> http://www.wicketstuff.org/maven/repository/org/wicketstuff/iolite/wicketstuff-iolite/0.3-SNAPSHOT/ >> > >> > While a core project does.. >> > >> http://www.wicketstuff.org/maven/repository/org/wicketstuff/openlayers/1.4-SNAPSHOT/ >> > >> > Heres something on the topic.. >> > >> > >> http://jlorenzen.blogspot.com/2007/09/how-to-effectively-use-snapshot.html >> > >> > I might be able to look at it tomorrow.. >> > >> > >> > 2009/12/9 Johan Compagner <[email protected]> >> > >> >> somehow the disks where full again >> >> i deleted as much logging as i can and some old stuff >> >> so we should be able to go on >> >> >> >> Biggest problem is as always but nobody seems to be able to fix that >> shitty >> >> maven: >> >> >> >> >> >> >> http://www.wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.5-SNAPSHOT/ >> >> >> >> It still generates unique snapshots.. Why cant nobody fix that stupid >> maven >> >> build behavior.. >> >> >> >> johan >> >> >> >> >> >> On Wed, Dec 9, 2009 at 10:31, Stefan Blanke <[email protected] >> >> >wrote: >> >> >> >> > Hi, >> >> > >> >> > does somebody know what happened to wicketstuff.org? >> >> > >> >> > >> >> > >> >> > I get the following error message: >> >> > >> >> > >> >> > >> >> > You cannot access Confluence at present. Look at the table below to >> >> > identify >> >> > the reasons >> >> > >> >> > Database is being updated by an instance which is not part of the >> current >> >> > cluster. You should check network connections between cluster nodes, >> >> > especially multicast traffic. >> >> > >> >> > >> >> > >> >> > Best regards, >> >> > >> >> > Stefan >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >
