You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Mark R. Diggory" <md...@latte.harvard.edu> on 2004/03/13 21:14:44 UTC

cvs.apache.org SNAPSHOT repository (was: Re: [vote] Nominate Ibiblio Content Manager)

I recommend we use the following location for SNAPSHOT/NIGHTLY/WEEKLY 
builds of jars for Apache Projects.

http://cvs.apache.org/repository/

-Mark



Mark R. Diggory wrote:

> I don't believe I'm on the directory developers list, sorry.
> 
> There is absolutely no such "Requirement", You can configure your client 
> to point at any "repository location" for downloading artifacts (ibiblio 
> or not).
> 
> However, there is no "distributed repository" lookup mechanism in Maven 
> whatsoever, the default configuration points only at ibiblio. So, if you 
> want to publicize your jars for use by the world, then the greatest 
> exposure is via ibiblio at the moment because it is the default.
> 
> Noel J. Bergman wrote:
> 
>> Are you saying that in order for someone to use Maven to build the code,
>> they need access to project artifacts published on ibiblio?  If you are
>> saying that Maven forces Incubator projects to make public publication of
>> code, that raises some concern.
>>
>> Mark, is it not possible for us to host artifacts for maven on
>> cvs.apache.org somewhere so that they are not put out in the public
>> perception as "released" code?  
> 
> 
> Yes, this is something we are in the process of setting up.
> 
>> Can you work with us so that Incubator
>> projects can use Maven without having to push the boundaries?  Does
>> something like "cvs.apache.org/incubator-repository" make sense?  Please
>> advise.  :-)
> 
> 
> 
> Sort of, we need a more generic location for all apache projects
> 
> cvs.apache.org/builds/repository/
> 
> Ideally, in Jakarta-Commons for instance, there are ambitions to see a 
> nightly/weekly automated build process actually generate such content 
> for this repository.
> 
> Since projects don't stay in the incubator forever, I suggest you don't 
> use it in the groupId for a incubator project. This way it can be 
> migrated more easily to www.apache.dist/java-repository without 
> modification of the groupId.
> 
> cvs.apache.org/builds/repository/jaxme/jars/...
> cvs.apache.org/builds/repository/directory/jars/...
> 
> ...
> 
> -Mark
> 
>>
>>     --- Noel
>>
>> -----Original Message-----
>> From: Alex Karasulu [mailto:aok123@bellsouth.net]
>> Sent: Saturday, March 13, 2004 12:55
>> To: 'Apache Directory Developers List'
>> Subject: RE: [vote] Nominate Ibiblio Content Manager
>>
>>
>> This is not for any release but for snapshots to allow the build to 
>> happen.
>>
>>
>>> -----Original Message-----
>>> From: Noel J. Bergman [mailto:noel@devtech.com]
>>> Sent: Saturday, March 13, 2004 12:32 PM
>>> To: Apache Directory Developers List
>>> Subject: RE: [vote] Nominate Ibiblio Content Manager
>>>
>>>
>>>> I'd like to nominate myself as the Ibiblio content manager if
>>>> that's ok with the group.  If stuff like snapshots need to go
>>>> up to Ibiblio I'll push it up on behalf of the team.  If others
>>>> would like the privilege instead let me know.
>>>
>>>
>>> Just remember that we should not be doing any releases while in the
>>> Incubator.  Exceptions can be voted on, with suitable tagging, but as a
>>> normative thing, projects in the incubator don't put out releases.
>>>
>>>     --- Noel
>>
>>
>>
>>
>>
> 

-- 
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu

Re: cvs.apache.org SNAPSHOT repository

Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.

Noel J. Bergman wrote:
> Mark R. Diggory wrote:
>>If your using your own workstation to build using Maven, then you can
>>set your central-repository property to point to
>>  maven.repo.central=minotaur.apache.org
>>  maven.repo.central.directory=/www/cvs.apache.org/repository/
>>Incubator can gladly be the first to start producing builds here. This
>>is not mirrored, there is no concern about making changes if you screw
>>up a deploy here.
> 
> 
> I think that last point is important for infrastructure to know.  And please
> correct me if I am wrong, but my understanding is that the clients (maven in
> this case) will check that location, but only download if they need
> something that hasn't been cached.  Therefore this shouldn't be a big
> bandwidth issue.
> 

Not only that, but it is also the case that only Apache developers 
should really be using this (with some bleed). If you look on 
cvs.apache.org, you'll also notice that other nightly/snapshot builds 
are getting dumped there and are web accessible.

http://cvs.apache.org/dist/
http://cvs.apache.org/builds/
http://cvs.apache.org/snapshots/

So we want to highly disapprove of external projects using this location 
at all for getting hold of jars from apache projects. Someday, maybe 
we'll have smarter repository tools that can make use of http auth 
mechanisms, then this can really be enforced.

-Mark

-- 
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu

Re: cvs.apache.org SNAPSHOT repository

Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.

Noel J. Bergman wrote:
> Mark R. Diggory wrote:
>>If your using your own workstation to build using Maven, then you can
>>set your central-repository property to point to
>>  maven.repo.central=minotaur.apache.org
>>  maven.repo.central.directory=/www/cvs.apache.org/repository/
>>Incubator can gladly be the first to start producing builds here. This
>>is not mirrored, there is no concern about making changes if you screw
>>up a deploy here.
> 
> 
> I think that last point is important for infrastructure to know.  And please
> correct me if I am wrong, but my understanding is that the clients (maven in
> this case) will check that location, but only download if they need
> something that hasn't been cached.  Therefore this shouldn't be a big
> bandwidth issue.
> 

Not only that, but it is also the case that only Apache developers 
should really be using this (with some bleed). If you look on 
cvs.apache.org, you'll also notice that other nightly/snapshot builds 
are getting dumped there and are web accessible.

http://cvs.apache.org/dist/
http://cvs.apache.org/builds/
http://cvs.apache.org/snapshots/

So we want to highly disapprove of external projects using this location 
at all for getting hold of jars from apache projects. Someday, maybe 
we'll have smarter repository tools that can make use of http auth 
mechanisms, then this can really be enforced.

-Mark

-- 
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu

RE: cvs.apache.org SNAPSHOT repository (was: Re: [vote] Nominate Ibiblio Content Manager)

Posted by "Noel J. Bergman" <no...@devtech.com>.
Mark R. Diggory wrote:
> I recommend we use the following location for SNAPSHOT/NIGHTLY/WEEKLY
> builds of jars for Apache Projects.
> http://cvs.apache.org/repository/

Mark R. Diggory later wrote in the original thread:

> I just created it a few moments ago. You should have write access there.

> If your using your own workstation to build using Maven, then you can
> set your central-repository property to point to
>   maven.repo.central=minotaur.apache.org
>   maven.repo.central.directory=/www/cvs.apache.org/repository/
> Incubator can gladly be the first to start producing builds here. This
> is not mirrored, there is no concern about making changes if you screw
> up a deploy here.

I think that last point is important for infrastructure to know.  And please
correct me if I am wrong, but my understanding is that the clients (maven in
this case) will check that location, but only download if they need
something that hasn't been cached.  Therefore this shouldn't be a big
bandwidth issue.

	--- Noel


RE: cvs.apache.org SNAPSHOT repository (was: Re: [vote] Nominate Ibiblio Content Manager)

Posted by "Noel J. Bergman" <no...@devtech.com>.
Mark R. Diggory wrote:
> I recommend we use the following location for SNAPSHOT/NIGHTLY/WEEKLY
> builds of jars for Apache Projects.
> http://cvs.apache.org/repository/

Mark R. Diggory later wrote in the original thread:

> I just created it a few moments ago. You should have write access there.

> If your using your own workstation to build using Maven, then you can
> set your central-repository property to point to
>   maven.repo.central=minotaur.apache.org
>   maven.repo.central.directory=/www/cvs.apache.org/repository/
> Incubator can gladly be the first to start producing builds here. This
> is not mirrored, there is no concern about making changes if you screw
> up a deploy here.

I think that last point is important for infrastructure to know.  And please
correct me if I am wrong, but my understanding is that the clients (maven in
this case) will check that location, but only download if they need
something that hasn't been cached.  Therefore this shouldn't be a big
bandwidth issue.

	--- Noel


RE: cvs.apache.org SNAPSHOT repository (was: Re: [vote] Nominate Ibiblio Content Manager)

Posted by Alex Karasulu <ao...@bellsouth.net>.
> I recommend we use the following location for SNAPSHOT/NIGHTLY/WEEKLY
> builds of jars for Apache Projects.
> 
> http://cvs.apache.org/repository/
> 
> -Mark

Would you include snapshots for incubator projects here?

Alex