On Sun, 2006-06-04 at 10:35 +1000, Brett Porter wrote:
> Dennis is already a committer over at Jakarta Commons and has been doing
> a good job submitting patches to Maven plugins and documentation, and
> has been hanging around here for the longest time.
>
> I propose we give him commit access t
+1
On 3 Jun 06, at 8:35 PM 3 Jun 06, Brett Porter wrote:
Dennis is already a committer over at Jakarta Commons and has been
doing a good job submitting patches to Maven plugins and
documentation, and has been hanging around here for the longest time.
I propose we give him commit access to
+1
-Lukas
Brett Porter wrote:
Dennis is already a committer over at Jakarta Commons and has been doing
a good job submitting patches to Maven plugins and documentation, and
has been hanging around here for the longest time.
I propose we give him commit access to apply his own patches, and
Dennis is already a committer over at Jakarta Commons and has been doing
a good job submitting patches to Maven plugins and documentation, and
has been hanging around here for the longest time.
I propose we give him commit access to apply his own patches, and
hopefully a few more besides :)
I'd suggest putting it in JIRA. Making that configurable sounds reasonable.
It should actually be something that is configured on the wagon.get()
request, actually, so that Maven could send it for snapshots and
metadata, but not others. But a global setting should be ok too if the
proxy owner
+1
arnaud
On 6/3/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
+1
-Lukas
Brett Porter wrote:
> Hi,
>
> Jesse M (already a plugins committer), has pinged me off list saying he
> has some changes to the repository manager that he'd like to commit.
> Rather than going through patches, I'd like
+1
-Lukas
Brett Porter wrote:
Hi,
Jesse M (already a plugins committer), has pinged me off list saying he
has some changes to the repository manager that he'd like to commit.
Rather than going through patches, I'd like to suggest we increase his
karma. We need more people working on it :)
+1
On 6/2/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Hi,
Jesse M (already a plugins committer), has pinged me off list saying he
has some changes to the repository manager that he'd like to commit.
Rather than going through patches, I'd like to suggest we increase his
karma. We need more peopl
This didn't get any traction on the users' list. Is there any way to
moderate the cache control pragmas on Maven's GET requests?
— G
Begin forwarded message:
From: Gordon Henriksen <[EMAIL PROTECTED]>
Date: June 2, 2006 15:49:46 EDT
To: Maven Users List
Subject: Pragma: no-cache on GET req
With a name like Jesse how can you go wrong? ;)
+1 (non-binding)
On 6/3/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
On Sat, 3 Jun 2006, Brett Porter wrote:
+1
> Hi,
>
> Jesse M (already a plugins committer), has pinged me off list saying he
> has some changes to the repository manager th
On Sat, 3 Jun 2006, Brett Porter wrote:
+1
> Hi,
>
> Jesse M (already a plugins committer), has pinged me off list saying he
> has some changes to the repository manager that he'd like to commit.
> Rather than going through patches, I'd like to suggest we increase his
> karma. We need more people
I must say that I agree with Brett here. My goal has been to post small
specific patches to JIRA, so that they can be easily reviewed. I know,
from own experience, how difficult it can be to review a patch that does
*everything*. It makes it hard to see what is really going on.
However, if Car
Hi,
indeed, there seems to be something wrong at some other place. I'm also looking
a bit at the code, but I still have a question about the purpose of using a
basedir: for plugins which do not operate on an existing maven project (e.g. the
archetype), having such a basedir is fine and intuitive,
13 matches
Mail list logo
