Sorry for the later response, currently, I think the major issues are in
managing the content of java-repository in responsible manner.
Key issues I can see needing to be addressed are the following.
1.) Get projects to be as "responsible" for their content in
java-repository as they are for the
How would this work?
- The projects publish their artifacts to dist/ as they have
without the repository. This includes jar, md5 and sig as
desired/necessary.
- a periodic cron job creates symlinks under java-repository/.
Mark?
--- Noel
Shurly think so! How can we help here?
R,
Markus
>
> Mark R. Diggory wrote:
>
> > Sander Striker wrote:
> >
> >> I understand. But it has to be fairly mature before one can
> >> deploy and recommend using it to the PMCs. Also, you can't
> >> force all the projects to use it. For this you n
On Wed, 2004-02-25 at 03:38, Mark R. Diggory wrote:
> >>3.) For Infrastructure, all this needs to be properly secured and
> >>maintained according to Apache standards.
> >
> > Yes.
> I need allot of help here, if I'm not doing something up to par, I need
> to hear about it. The help you've prov
Markus M. May wrote:
>
> Nicola Ken Barozzi wrote:
>>
Mark R. Diggory wrote:
...
it more configurable, currently all md5 checksums generated using Maven
are broken because of this, I think others have recognized this and
generate them by hand on their own.
In Ruper we have an md5sum implementatio
Mark R. Diggory wrote:
Sander Striker wrote:
I understand. But it has to be fairly mature before one can
deploy and recommend using it to the PMCs. Also, you can't
force all the projects to use it. For this you need some way
of handmaintaining 'shadow' packages in java-repository,
correct?
[..
Wow, I'll try to be concise!
Sander Striker wrote:
I understand. But it has to be fairly mature before one can
deploy and recommend using it to the PMCs. Also, you can't
force all the projects to use it. For this you need some way
of handmaintaining 'shadow' packages in java-repository,
correct?
Note that was not subscribed, so I am breaking the thread with my post.
> From: "Mark R. Diggory" <[EMAIL PROTECTED]>
> Date: Sun, 22 Feb 2004 00:59:58 -0500
> I'll try to expand on the functionalities of Maven below.
>
> Sander Striker wrote:
>
> > On Sat, 2004-02-21 at 01:01, Mark R. Diggory
I'll try to expand on the functionalities of Maven below.
Sander Striker wrote:
On Sat, 2004-02-21 at 01:01, Mark R. Diggory wrote:
Noel J. Bergman wrote:
The issue is... the jars/distributables are placed into the
java-repository using maven.
Can you explain this a bit? I thought Maven was used
On Sat, 2004-02-21 at 01:01, Mark R. Diggory wrote:
> Noel J. Bergman wrote:
> >>The issue is... the jars/distributables are placed into the
> >>java-repository using maven.
Can you explain this a bit? I thought Maven was used to fetch
projects and dependencies. Ofcourse I can read up on Maven,
Noel J. Bergman wrote:
The issue is... the jars/distributables are placed into the
java-repository using maven. so, currently, if you look in
something like the commons project.properties you'll see that
they are pointing to the central repository for the location
of where to "publish" files.
The
> The issue is... the jars/distributables are placed into the
> java-repository using maven. so, currently, if you look in
> something like the commons project.properties you'll see that
> they are pointing to the central repository for the location
> of where to "publish" files.
> The "convergenc
Th issue is... the jars/distributables are placed into the
java-repository using maven. so, currently, if you look in something
like the commons project.properties you'll see that they are pointing to
the central repository for the location of where to "publish" files.
#
Mark,
An issue was raised earlier today that should be addressed. The impression
is that java-repository is publishing copies of jars that are also under
dist/TLP/..., which puts more of a load on the mirrors. It might be best if
the jars/ directories contained symlinks and not copies of artifac
14 matches
Mail list logo
