Thanks simon I will take care for the selection of threads in future.Apologies for the same.
On Fri, Feb 15, 2008 at 1:28 PM, Mark Struberg <[EMAIL PROTECTED]> wrote: > The only reason i can think of to have a snapshot repo in a company is to > get rid of very old > snapshots which may bump up your repo size heavily. It is much easier to > drop obsolete snapshots > if they are strictly separated from released modules. > > LieGrü, > strub > > --- "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> schrieb: > > Hi Amit, > > > > Firstly, when you have a question that is not really related to an > > existing thread, then please start a new email thread rather than > > replying to the existing one. By doing that, and choosing a good subject > > line for the email, other people with the same problem can later search > > the email archives and find the necessary answer. > > > > AFAIK, there's no major problem having release and snapshot versions in > > the same repository. > > > > This doesn't happen often with open-source projects because (a) all > > releases get put into the official repositories (ibiblio, > > rep1.maven.org) that are mirrored arround the world, and (b) mirroring > > snapshots is silly. So for apache software for example, there is a > > non-mirrored repo that only holds snapshots, with all actual releases > > going to the mirrored repos. > > > > But for a company that doesn't mirror its releases, I'm not aware of any > > reason why snapshots and releases cannot be on the same repo. > > > > Your problem is probably that you have the <repository> tag that points > > to your repo configured with snapshot-lookup disabled. Try adding this > > to the repository tag: > > <snapshots> > > <enabled>true</enabled> > > </snapshots> > > > > Regards, > > Simon > > > > amit kumar schrieb: > > > SNAPSHOT Vs release version. > > > > > > Hi, > > > In our intranet maven repository we have both release version and > snaphot > > > version under the same groupId (under the same folder on file system). > While > > > amounting to ignorance to SNAPSHOT versions, release version existed > long > > > before SNAPSHOT versions started getting placed in the same folder. > > > Now we realized that when people changed their dependency versions to > > > snapshot, maven is not able to fetch the SNAPSHOT version, and it just > tells > > > not able to find the specified jar. > > > > > > The earlier dependency of y on x > > > > > > <groupId>com.group.x</groupId> > > > <artifactId>x</artifactId> > > > <version>1.0.0</version> > > > > > > has become > > > <groupId>com.group.x</groupId> > > > <artifactId>x</artifactId> > > > <version>1.0.0-SNAPSHOT</version> > > > > > > and x has already been deployed to the repository with > > > 1.0.0-SNAPSHOTversion. Could someone please help me figure out what > > > exactly is happening > > > here? > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > Lesen Sie Ihre E-Mails auf dem Handy. > www.yahoo.de/go > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
