Ok, I update our homepage
Arnaud
On 12/9/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 9 Dec 06, at 9:34 AM 9 Dec 06, Arnaud HERITIER wrote:
> http://repo1.maven.org/maven
> or
> http://mirrors.ibiblio.org/pub/mirrors/maven
>
> Lukas and Carlos mentioned the 2nd one.
>
Go with the repo1.m
On 9 Dec 06, at 9:34 AM 9 Dec 06, Arnaud HERITIER wrote:
http://repo1.maven.org/maven
or
http://mirrors.ibiblio.org/pub/mirrors/maven
Lukas and Carlos mentioned the 2nd one.
Go with the repo1.maven.org/maven one as we have full control over
that and can react immediately if there are prob
http://repo1.maven.org/maven
or
http://mirrors.ibiblio.org/pub/mirrors/maven
Lukas and Carlos mentioned the 2nd one.
Arnaud
On 12/9/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 9 Dec 06, at 8:38 AM 9 Dec 06, Arnaud HERITIER wrote:
> Do you want that we add a news on the m1 homepage abou
On 9 Dec 06, at 8:38 AM 9 Dec 06, Arnaud HERITIER wrote:
Do you want that we add a news on the m1 homepage about the current
problem
with the central repository.
To which central repository must invite our users to set the
maven.repo.remote property ? http://repo1.maven.org/maven ?
That wo
Do you want that we add a news on the m1 homepage about the current problem
with the central repository.
To which central repository must invite our users to set the
maven.repo.remote property ? http://repo1.maven.org/maven ?
Arnaud
On 12/8/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 8 Dec
On 8 Dec 06, at 9:16 AM 8 Dec 06, Martin van den Bemt wrote:
Is an hotfix not the easiest way to get this solved ?
Not really. In order for things to work m1 users just need to change
a configuration. Easier then upgrading a JAR. But for a real fix we
need to get m1 users over to the m2 i
Is an hotfix not the easiest way to get this solved ?
Mvgr,
Martin
Jason van Zyl wrote:
>
> On 8 Dec 06, at 8:38 AM 8 Dec 06, Martin van den Bemt wrote:
>
>> (don't use maven 1 anymore)
>> Do you mean the problem that httpclient by default doesn't follow
>> redirects ?
>
> Right.
>
>> If it i
On 8 Dec 06, at 9:06 AM 8 Dec 06, Lukas Theussl wrote:
AFAICT neither maven-core nor the artifact plugin are actually
using httpclient anymore, only the jira and linkcheck plugins still
use it.
For compat, the blocker is MAVEN-1755, that's the only issue IMO
that needs to be resolved for
On 8 Dec 06, at 8:38 AM 8 Dec 06, Martin van den Bemt wrote:
(don't use maven 1 anymore)
Do you mean the problem that httpclient by default doesn't follow
redirects ?
Right.
If it is an option to have a quicker release by just fixing the
httpclient wagon provider, I can
have a go at fixi
AFAICT neither maven-core nor the artifact plugin are actually using
httpclient anymore, only the jira and linkcheck plugins still use it.
For compat, the blocker is MAVEN-1755, that's the only issue IMO that
needs to be resolved for 1.1. Arnaud was working on it, I let him sum up
the status.
(don't use maven 1 anymore)
Do you mean the problem that httpclient by default doesn't follow redirects ?
If it is an option to have a quicker release by just fixing the httpclient
wagon provider, I can
have a go at fixing that (I prefer httpclient over the lightweight one, since
that one interfe
Hi,
Some please get the Maven 1.x that they know of up so we can try to
work together to get the release out. The only things I see are:
- compatibility
- that wagon is used for transport as we have to get rid of commons-
httpclient, or at least the version that is currently killing us
I w
On 4 Dec 06, at 10:06 PM 4 Dec 06, Brett Porter wrote:
The only real condition for Maven 1.1 is making sure backwards
compat is intact, or at least documented where broken intentionally.
+1
Change the default central repo and throw the baby out the window.
Someone will catch it.
Jason.
The only real condition for Maven 1.1 is making sure backwards compat
is intact, or at least documented where broken intentionally.
- Brett
On 05/12/2006, at 1:47 PM, Jesse Kuhnert wrote:
Exactly... Trying to quantify the stability of a release before it
goes out the door is just impossible/
Exactly... Trying to quantify the stability of a release before it
goes out the door is just impossible/not practical for os.
Release early & often. ;)
On 12/4/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
what I see is that there's always issues that anyone wants to get
fixed and that makes th
On 12/5/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
what I see is that there's always issues that anyone wants to get
fixed and that makes the releases take forever. If things are not
critical imho is more important to release often and move issues to
1.1.1
Then we should at least fix 1755 an
what I see is that there's always issues that anyone wants to get
fixed and that makes the releases take forever. If things are not
critical imho is more important to release often and move issues to
1.1.1
On 12/4/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
Hi,
According to the roadmap [1],
Hi,
According to the roadmap [1], there's 25 issues left. Mostly plugin upgrades
which could come quite quickly and at least 1755 and 1789. The problem is
that we're trying to release RC1 and it makes not much sense if we have
still open issues scheduled for 1.1
Cheers,
Stéphane
[1]
http://ji
Hi Guys,
What's left to do before the M1 release can go out? We need to get
the Maven 1.x repository usage off Ibiblio.
Jason.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
19 matches
Mail list logo
