You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Alex Karasulu <ao...@bellsouth.net> on 2004/03/13 18:23:17 UTC
[vote] Nominate Ibiblio Content Manager
Guys,
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.
Alex
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 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
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
cvs.apache.org SNAPSHOT repository (was: Re: [vote] Nominate Ibiblio
Content Manager)
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
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
cvs.apache.org SNAPSHOT repository (was: Re: [vote] Nominate Ibiblio
Content Manager)
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
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: [vote] Nominate Ibiblio Content Manager
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Alex Karasulu wrote:
>>-----Original Message-----
>>From: Mark R. Diggory [mailto:mdiggory@latte.harvard.edu]
>>
>>I just created it a few moments ago. You should have write access there.
>
>
> That's just marvelous!
>
>
>>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/
>
>
> Will do!
>
>
>>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 don't think the lack of mirroring is an issue to anyone of us. Thanks
> much Mark. I guess this problem is laid to rest and I'm a happy camper.
>
> Thanks again for your help,
> Alex
Its actually a big benefit to everyone that this isn't mirrored, Apache
and Mirror folks don't want unsanctioned releases on their mirrors either.
-Mark
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
RE: [vote] Nominate Ibiblio Content Manager
Posted by Alex Karasulu <ao...@bellsouth.net>.
> -----Original Message-----
> From: Mark R. Diggory [mailto:mdiggory@latte.harvard.edu]
>
> I just created it a few moments ago. You should have write access there.
That's just marvelous!
> 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/
Will do!
> 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 don't think the lack of mirroring is an issue to anyone of us. Thanks
much Mark. I guess this problem is laid to rest and I'm a happy camper.
Thanks again for your help,
Alex
Re: [vote] Nominate Ibiblio Content Manager
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
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.
-Mark
Alex Karasulu wrote:
>>Hmm, then I suspect that it would be in the groupId, really, I guess if
>>a project is depending on something in the incubator, then they
>>themselves are probably not at release state too (and probably another
>>incubator project). In which case, its probably quite acceptable that
>>incubator can be in the groupId.
>>
>>In which case incubator dev builds would look like
>>
>>/www/cvs.apache.org/repository/incubator-directory/jars/<artifact>...
>>/www/cvs.apache.org/repository/incubator-depot/jars/<artifactid>...
>>/www/cvs.apache.org/repository/incubator-geronimo/jars/<artifact>...
>>/www/cvs.apache.org/repository/incubator-axion/jars/<artifact>...
>>
>>We just need to make it clear that when a project Graduates, its groupId
>>needs to change appropriately. When it starts doing release builds into
>>/www/www.apache.org/java-repository, it needs to loose the incubator.
>
>
> I like this! So when do you think we can have this area?
>
> Again I would love to stop using ~akarasulu for my own personal maven
> repo that my build.properties in ${user.home} points maven to. Also we
> can add the second repo to the project.properties of each project in
> addition to Ibiblio.
>
> Thanks,
> Alex
>
>
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
RE: [vote] Nominate Ibiblio Content Manager
Posted by Alex Karasulu <ao...@bellsouth.net>.
> Hmm, then I suspect that it would be in the groupId, really, I guess if
> a project is depending on something in the incubator, then they
> themselves are probably not at release state too (and probably another
> incubator project). In which case, its probably quite acceptable that
> incubator can be in the groupId.
>
> In which case incubator dev builds would look like
>
> /www/cvs.apache.org/repository/incubator-directory/jars/<artifact>...
> /www/cvs.apache.org/repository/incubator-depot/jars/<artifactid>...
> /www/cvs.apache.org/repository/incubator-geronimo/jars/<artifact>...
> /www/cvs.apache.org/repository/incubator-axion/jars/<artifact>...
>
> We just need to make it clear that when a project Graduates, its groupId
> needs to change appropriately. When it starts doing release builds into
> /www/www.apache.org/java-repository, it needs to loose the incubator.
I like this! So when do you think we can have this area?
Again I would love to stop using ~akarasulu for my own personal maven
repo that my build.properties in ${user.home} points maven to. Also we
can add the second repo to the project.properties of each project in
addition to Ibiblio.
Thanks,
Alex
Re: [vote] Nominate Ibiblio Content Manager
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Noel J. Bergman wrote:
>>I don't believe I'm on the directory developers list, sorry.
>
>
> Nope. I cc'd you because you are the most knowledgeable person on the
> subject of Maven and our repositories whom I know. :-)
>
Thanks for including me.
> Here is the thread:
> http://nagoya.apache.org/eyebrowse/BrowseList?listName=directory-dev@incubat
> or.apache.org&by=thread&from=672486
>
>
>>if you want to publicize your jars for use by the world
>
>
> That not what an Incubator project should normally be doing.
yes, I get that.
>
>>Since projects don't stay in the incubator forever, I suggest you don't
>>use it in the groupId for a incubator project.
>
>
> Somewhere in the URL we want it clear that the artifact is in the Incubator.
>
Hmm, then I suspect that it would be in the groupId, really, I guess if
a project is depending on something in the incubator, then they
themselves are probably not at release state too (and probably another
incubator project). In which case, its probably quite acceptable that
incubator can be in the groupId.
In which case incubator dev builds would look like
/www/cvs.apache.org/repository/incubator-directory/jars/<artifact>...
/www/cvs.apache.org/repository/incubator-depot/jars/<artifactid>...
/www/cvs.apache.org/repository/incubator-geronimo/jars/<artifact>...
/www/cvs.apache.org/repository/incubator-axion/jars/<artifact>...
We just need to make it clear that when a project Graduates, its groupId
needs to change appropriately. When it starts doing release builds into
/www/www.apache.org/java-repository, it needs to loose the incubator.
/www/www.apache.org/java-repository/jaxme/jars/<artifact>...
-Mark
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
RE: [vote] Nominate Ibiblio Content Manager
Posted by "Noel J. Bergman" <no...@devtech.com>.
> I don't believe I'm on the directory developers list, sorry.
Nope. I cc'd you because you are the most knowledgeable person on the
subject of Maven and our repositories whom I know. :-)
Here is the thread:
http://nagoya.apache.org/eyebrowse/BrowseList?listName=directory-dev@incubat
or.apache.org&by=thread&from=672486
> if you want to publicize your jars for use by the world
That not what an Incubator project should normally be doing.
> > 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.
I'll leave the details of Mavenization to you, Alex, Phil, et al. :-)
> we need a more generic location for all apache projects
> Since projects don't stay in the incubator forever, I suggest you don't
> use it in the groupId for a incubator project.
Somewhere in the URL we want it clear that the artifact is in the Incubator.
--- Noel
Re: [vote] Nominate Ibiblio Content Manager
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
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: [vote] Nominate Ibiblio Content Manager
Posted by Alex Karasulu <ao...@bellsouth.net>.
I think he's subscribed to the list but the ossie is sleeping!
> -----Original Message-----
> From: Noel J. Bergman [mailto:noel@devtech.com]
> Sent: Saturday, March 13, 2004 3:14 PM
> To: Apache Directory Developers List
> Subject: RE: [vote] Nominate Ibiblio Content Manager
>
> > It does not make sense to me that an external repo should be
> > required to push out and pull back jars as part of the build
> > process.
>
> Me neither, but I don't use Maven other than "maven <do-it>".
>
> > Brett can probably help with this.
>
> Feel free to invite him to the party. :-)
>
> http://nagoya.apache.org/eyebrowse/BrowseList?listName=directory-
> dev@incubat
> or.apache.org&by=thread&from=672486
>
> --- Noel
RE: [vote] Nominate Ibiblio Content Manager
Posted by "Noel J. Bergman" <no...@devtech.com>.
> It does not make sense to me that an external repo should be
> required to push out and pull back jars as part of the build
> process.
Me neither, but I don't use Maven other than "maven <do-it>".
> Brett can probably help with this.
Feel free to invite him to the party. :-)
http://nagoya.apache.org/eyebrowse/BrowseList?listName=directory-dev@incubat
or.apache.org&by=thread&from=672486
--- Noel
RE: [vote] Nominate Ibiblio Content Manager
Posted by Alex Karasulu <ao...@bellsouth.net>.
Phil, Noel & Mark,
I'm not talking about pushing out and pulling them back in. Take
for example the ldap project which has a common jar for both clients
and servers. Eve (server) needs that jar. Rather than have the user
have to build the common jar and the Eve jar its better to have common
up on some site we all can access.
Noel's idea is a good one. Since we cannot control the fact that any
project in the incubator can set the version to something other than
SNAPSHOT and upload it we need to enforce the use of a repo that had
incubator in the URL somewhere. It's just an additional repo that
all in the incubator have access to. It's just in one place.
The bottom line is xyz-SNAPSHOT.jar != release but you cannot enforce
this unless you restrict publishing (loosely termed) to a specific
repo. It should be a rule of the incubator actually to keep things here
and only here.
I personally use a repo in my home account
http://www.apache.org/~akarasulu/maven to manage these jars because when I
move to a new machine I don't want everything to have to rebuild over again.
Plus I can manage snapshot's I expose to the other members of the team.
Its for internal use really. BTW I would really love to blow this
http://www.apache.org/~akarasulu/maven directory away.
It would be nice to have an additional incubator based maven repo for
projects under incubation. That way I don't have to replicate jars and
others don't either off their own user accounts or yet another site all
together.
Alex
> -----Original Message-----
> From: Phil Steitz [mailto:phil@steitz.com]
> Sent: Saturday, March 13, 2004 2:41 PM
> To: Apache Directory Developers List
> Subject: Re: [vote] Nominate Ibiblio Content Manager
>
> Alex Karasulu wrote:
> >>I am not a maven expert, but I don't think that anything other than
> >>external jars needs to be externally hosted -- i.e., you can install
> >>internally generated jars to the local maven repo to get multi-project
> >>builds to work. I think you can get maven to do that automatically using
> >>install goals. That's how the directory-naming build works now. See
> >>http://incubator.apache.org/directory/subprojects/naming/building.html.
> >
> >
> > Already have the reactor in use for this but can't do another
> indirection.
> > Plus we have multiple subprojects some of which depend on another.
> >
> > Alex
> >
> >
>
> I don't get this. At the very least, you could generate the jars
> individually and them jar:install them into the local repo or just put
> them in the expected locations in .maven/repsitory. It does not make
> sense to me that an external repo should be required to push out and pull
> back jars as part of the build process.
>
> Brett can probably help with this.
>
> Phil
Re: [vote] Nominate Ibiblio Content Manager
Posted by Phil Steitz <ph...@steitz.com>.
Alex Karasulu wrote:
>>I am not a maven expert, but I don't think that anything other than
>>external jars needs to be externally hosted -- i.e., you can install
>>internally generated jars to the local maven repo to get multi-project
>>builds to work. I think you can get maven to do that automatically using
>>install goals. That's how the directory-naming build works now. See
>>http://incubator.apache.org/directory/subprojects/naming/building.html.
>
>
> Already have the reactor in use for this but can't do another indirection.
> Plus we have multiple subprojects some of which depend on another.
>
> Alex
>
>
I don't get this. At the very least, you could generate the jars
individually and them jar:install them into the local repo or just put
them in the expected locations in .maven/repsitory. It does not make
sense to me that an external repo should be required to push out and pull
back jars as part of the build process.
Brett can probably help with this.
Phil
RE: [vote] Nominate Ibiblio Content Manager
Posted by Alex Karasulu <ao...@bellsouth.net>.
Meaning can extend another POM sorry.
> -----Original Message-----
> From: Alex Karasulu [mailto:aok123@bellsouth.net]
> Sent: Saturday, March 13, 2004 2:03 PM
> To: 'Apache Directory Developers List'
> Subject: RE: [vote] Nominate Ibiblio Content Manager
>
> > I am not a maven expert, but I don't think that anything other than
> > external jars needs to be externally hosted -- i.e., you can install
> > internally generated jars to the local maven repo to get multi-project
> > builds to work. I think you can get maven to do that automatically using
> > install goals. That's how the directory-naming build works now. See
> > http://incubator.apache.org/directory/subprojects/naming/building.html.
>
> Already have the reactor in use for this but can't do another indirection.
> Plus we have multiple subprojects some of which depend on another.
>
> Alex
>
RE: [vote] Nominate Ibiblio Content Manager
Posted by Alex Karasulu <ao...@bellsouth.net>.
> I am not a maven expert, but I don't think that anything other than
> external jars needs to be externally hosted -- i.e., you can install
> internally generated jars to the local maven repo to get multi-project
> builds to work. I think you can get maven to do that automatically using
> install goals. That's how the directory-naming build works now. See
> http://incubator.apache.org/directory/subprojects/naming/building.html.
Already have the reactor in use for this but can't do another indirection.
Plus we have multiple subprojects some of which depend on another.
Alex
Re: [vote] Nominate Ibiblio Content Manager
Posted by Phil Steitz <ph...@steitz.com>.
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? 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. :-)
I am not a maven expert, but I don't think that anything other than
external jars needs to be externally hosted -- i.e., you can install
internally generated jars to the local maven repo to get multi-project
builds to work. I think you can get maven to do that automatically using
install goals. That's how the directory-naming build works now. See
http://incubator.apache.org/directory/subprojects/naming/building.html.
Phil
>
> --- 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
>
>
>
>
RE: [vote] Nominate Ibiblio Content Manager
Posted by "Noel J. Bergman" <no...@devtech.com>.
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? 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. :-)
--- 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
RE: [vote] Nominate Ibiblio Content Manager
Posted by Alex Karasulu <ao...@bellsouth.net>.
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
RE: [vote] Nominate Ibiblio Content Manager
Posted by "Noel J. Bergman" <no...@devtech.com>.
> 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