Ah... they are not deployed, but downloaded from the official repo's when a downstream package needs those deps, such as dojo.
Can somesome make the deployment repository different from the local repo? This will seriously hinder our oversight given the confusion that already exists (and I don't want to have to answer this 'we don't deploy sources' question with every release). Martijn On 9/3/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > Can someone remove those *non-release* jars from the wicketstuff repo? > They are not signed, md5'd, etc. And please remove any automated build > that deploys them on that server. > > Martijn > > On 9/3/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > On 9/3/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > I did: > > > http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3.0-beta3/ > > > > That is not an official maven repo, it is a snapshot repository > > containing only...... snapshots. As such it is not sync'd with any > > other repo. > > > > And as an Apache project, you can not deploy official releases on > > non-Apache hardware. It has to come from Apache. wicketstuff.org is > > not apache. > > > > Martijn > > > > -- > > Buy Wicket in Action: http://manning.com/dashorst > > Apache Wicket 1.3.0-beta3 is released > > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/ > > > > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.0-beta3 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/ > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-beta3 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
