+1
Arnaud
On 3/3/07, Vincent Massol <[EMAIL PROTECTED]> wrote:
On Feb 22, 2007, at 8:47 PM, Carlos Sanchez wrote:
> It'd be good to have the tool that checks for API changes between
> versions in the parent pom.
We could try using Clirr for this. The strategy could be something
like http://
On Feb 22, 2007, at 8:47 PM, Carlos Sanchez wrote:
It'd be good to have the tool that checks for API changes between
versions in the parent pom.
We could try using Clirr for this. The strategy could be something
like http://blogs.codehaus.org/people/vmassol/archives/
think_tank.html#001324
On 22 Feb 07, at 5:11 PM 22 Feb 07, Joakim Erdfelt wrote:
Just some thoughts.
I would like to change wagon-webdav's protocol definition.
Currently it is "dav:http://"; and "dav:https://"; both of which are
technically invalid protocols.
It should be "dav://" and "davs://".
As long as you s
Just some thoughts.
I would like to change wagon-webdav's protocol definition.
Currently it is "dav:http://"; and "dav:https://"; both of which are
technically invalid protocols.
It should be "dav://" and "davs://".
I've wanted to make the wagon's register URL handlers for themselves too.
That w
It'd be good to have the tool that checks for API changes between
versions in the parent pom.
I agree with John in pushing towards final releases, I already said
several times that all these alpha/betas are an excuse to make
dramatic changes while we are actually using them as final.
my 0.02 EUR
How do you mean? What else is there to be concerned about WRT backward
compat?
BTW, I don't think dropping the method entirely is a good course of
action...but we do need to adjust the code to accommodate wagon providers
that don't have it.
I think the wagon API is probably stable enough to talk
The Wagon.getProtocol() method could probably be dropped.
But that won't address the bigger concern. Backwards compatibility.
- Joakim
John Casey wrote:
> Also, to be clear, in the past I've broken things massively in Maven and
> other places. Almost without fail, someone has tracked me down, a
Also, to be clear, in the past I've broken things massively in Maven and
other places. Almost without fail, someone has tracked me down, and waited
while I stopped everything I was doing, and fixed the problem...with tests,
if possible.
On 2/22/07, John Casey <[EMAIL PROTECTED]> wrote:
Just to
Just to be clear - did I miss a volley of emails on these topics?
-j
On 2/22/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
The changes to wagon are ... (just to make sure they show in john's
gmail account)
1) Timeouts
2) Streaming Wagon
3) Limited Transactions
- Joakim
John Casey wrote:
> H
The changes to wagon are ... (just to make sure they show in john's
gmail account)
1) Timeouts
2) Streaming Wagon
3) Limited Transactions
- Joakim
John Casey wrote:
> Hi all,
>
> I have something to point out that I think the entire Maven development
> community needs to hear. I've been doing a
Hi all,
I have something to point out that I think the entire Maven development
community needs to hear. I've been doing a lot of work recently with Maven
trunk, so I notice any (perhaps inevitable) instability that comes down the
pike from dependency APIs. Recently, I've been having a LOT of tro
11 matches
Mail list logo
