Traditionally people seperate snapshot and public for various reasons: 1) Snapshots want to be kept private (unnecessary, since the webserver can be configured to grant/deny access to certain files to certain users) 2) Repos are managed by a different team (development team versus build management team, this is probably the only decent reason I know of) 3) Snapshot repos can grow fast so sometimes require servers with more diskspace (bad filesystem setup, imo, and shouldn't be a reason) 4) Snapshot repos need managed more - for example, deleting old datestamped snapshots (not a great reason, since a script can do the same job on a joint repo)
I mirror Taylor's sentiments: "I am personally against it unless there is a good reason *for* it". -- Eric Redmond http://blog.propellors.net On 8/29/07, Taylor Gautier <[EMAIL PROTECTED]> wrote: > > I was talking about the tc-maven-plugin. (Sorry, I hijacked the > thread). If it is not published in iBiblio, then people have to fill in the > pluginRepositories section and add Terracotta. If it is published to > iBiblio, then it can be resolved without an extra setting, and the plugin > knows how to do the remaining repo resolution, so it seems this makes poms > easier to write. > > The issue of a snapshot vs. a release repo is a separate issue. I am > personally against it unless there is a good reason *for* it - it just makes > for more configuration that seems unnecessary to me - snapshots already have > unique names at the jar level, so there is no name collision, and thus > basically no difference between having a snapshot repo separate or combined, > except that the latter case requires more configuration (as if there isn't > enough of that already in maven) > > my $0.02 > > Jeff Genender wrote: > > Agreed..why not create a snapshots.terracotta.org? > > Jeff > > Taylor Gautier wrote: > > What's wrong with publishing a snapshot? People know snapshots are in > flux... > > > > > Eugene Kuleshov wrote: > > We definitely should do that once we get to some release state. > > regards, > Eugene > > > Taylor Gautier wrote: > > I think we should consider publishing our plugin to the iBiblio repo > so we don't have to specify the pluginRepositories. Thoughts? > > Eugene Kuleshov wrote: > > To all Maven users: we are rearranging public maven repositories > and moving all snapshots into the new dedicated repository for > snapshots located at http://download.terracotta.org/maven2-snapshots > > Note that you should NOT have trailing slash because of the issues > between Maven and S3. > > I've updated maven plugin to use new repository by default, but you > may need to wait until Jason push new plugin to S3. > > Also note that we haven't completely cleaned up old repository from > snapshot jars due to some issues with S3. So, if you need to use both > http://download.terracotta.org/maven2-snapshots and > http://download.terracotta.org/maven2 repositories, then you should > put the snapshot one up front. For example: > > <pluginRepositories> > <pluginRepository> > <id>terracotta-snapshots</id> > <url>http://download.terracotta.org/maven2-snapshots</url> > <releases> > <enabled>true</enabled> > </releases> > <snapshots> > <enabled>true</enabled> > </snapshots> > </pluginRepository> > > <pluginRepository> > <id>terracotta-repository</id> > <url>http://download.terracotta.org/maven2</url> > <releases> > <enabled>true</enabled> > </releases> > <snapshots> > <enabled>false</enabled> > </snapshots> > </pluginRepository> > ... > > regards, > Eugene > > > _______________________________________________ > tc-dev mailing list > [EMAIL PROTECTED]://lists.terracotta.org/mailman/listinfo/tc-dev > > > _______________________________________________ > tc-dev mailing list > [EMAIL PROTECTED]://lists.terracotta.org/mailman/listinfo/tc-dev > > > ------------------------------------------------------------------------ > > _______________________________________________ > tc-dev mailing list > [EMAIL PROTECTED]://lists.terracotta.org/mailman/listinfo/tc-dev > > _______________________________________________ > tc-dev mailing list > [EMAIL PROTECTED]://lists.terracotta.org/mailman/listinfo/tc-dev > > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev > >
_______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
