Hello
In Apache Jira ?
--
Olivier
Le 17 sept. 2011 00:11, Vincent Siveton vsive...@apache.org a écrit :
Folks,
I need a new jira space for:
http://svn.apache.org/repos/asf/maven/doxia/doxia-ide/trunk/
Someone?
Thanks
Vincent
all Doxia-related Jira projects are on Codehaus: I suppose we won't change
just for this one, it would be hard to follow
regards,
Hervé
Le samedi 17 septembre 2011, Olivier Lamy a écrit :
Hello
In Apache Jira ?
--
Olivier
Le 17 sept. 2011 00:11, Vincent Siveton vsive...@apache.org a
Le vendredi 16 septembre 2011, ol...@apache.org a écrit :
Author: olamy
Date: Fri Sep 16 21:07:28 2011
New Revision: 1171784
URL: http://svn.apache.org/viewvc?rev=1171784view=rev
Log:
[MCHANGELOG-123] Patch with support for SCM provider implementations
(similar to release plugin) add
2011/9/17 Hervé BOUTEMY herve.bout...@free.fr:
Le vendredi 16 septembre 2011, ol...@apache.org a écrit :
Author: olamy
Date: Fri Sep 16 21:07:28 2011
New Revision: 1171784
URL: http://svn.apache.org/viewvc?rev=1171784view=rev
Log:
[MCHANGELOG-123] Patch with support for SCM provider
oups no I have missed something :-)
It's possible with maven2 too with using extensions, I will fix it and doc.
2011/9/17 Olivier Lamy ol...@apache.org:
2011/9/17 Hervé BOUTEMY herve.bout...@free.fr:
Le vendredi 16 septembre 2011, ol...@apache.org a écrit :
Author: olamy
Date: Fri Sep 16
I honestly have no idea what problem you're trying to solve from your comments
in the issues. I'd start with:
- What problem you're trying to solve
- Why you think it's important
- Examples of how it would be used
It's easier if you capture the discussion in the issue.
On Aug 26, 2011, at 6:12
-Original Message-
From: Jason van Zyl
Sent: Saturday, September 17, 2011 10:25
To: Maven Developers List
Subject: Re: Request for review and comment
http://jira.codehaus.org/browse/MNG-5167
I honestly have no idea what problem you're trying to solve
from your comments in the
On Sep 17, 2011, at 11:06 AM, Jason Pyeron wrote:
-Original Message-
From: Jason van Zyl
Sent: Saturday, September 17, 2011 10:25
To: Maven Developers List
Subject: Re: Request for review and comment
http://jira.codehaus.org/browse/MNG-5167
I honestly have no idea what
Hi Jason (and others aether/sisu commiters)
Do you have some news ( am I the only one to cross users waiting for new
releases to show that our project is always alive?)
Is the eclipse infrastructure so slow to create new projects ? I may
understand that these little libraries aren't critical
Hi,
On Sat, Sep 17, 2011 at 5:12 PM, Jason van Zyl ja...@maven.org wrote:
On Sep 17, 2011, at 11:06 AM, Jason Pyeron wrote:
-Original Message-
From: Jason van Zyl
Sent: Saturday, September 17, 2011 10:25
To: Maven Developers List
Subject: Re: Request for review and comment
-Original Message-
From: Jason van Zyl
Sent: Saturday, September 17, 2011 11:13
To: Maven Developers List
Subject: Re: Request for review and comment
http://jira.codehaus.org/browse/MNG-5167
On Sep 17, 2011, at 11:06 AM, Jason Pyeron wrote:
-Original Message-
This is why the project is open source. I don't think this patch is
something I would generally promote if the end result is encouraging people
to put binary dependencies in the source control system. But you are free to
maintain a patched version, that's your right.
I definitely second
On Sat, Sep 17, 2011 at 11:45 AM, Jason Pyeron jpye...@pdinc.us wrote:
-Original Message-
From: Jason van Zyl
Sent: Saturday, September 17, 2011 11:13
To: Maven Developers List
Subject: Re: Request for review and comment
http://jira.codehaus.org/browse/MNG-5167
On Sep 17, 2011, at
-Original Message-
From: Benson Margulies
Sent: Saturday, September 17, 2011 11:43
To: Maven Developers List
Subject: Re: Request for review and comment
http://jira.codehaus.org/browse/MNG-5167
This is why the project is open source. I don't think this
patch is
something I
The latest is always available here:
http://eclipse.org/proposals/technology.aether/
We still have to refactor the package names as well which we are going to do
next week. We've released Aether 1.13 and Sisu 2.3.0 so we can use those as
well if we want. If you want to stick with the proper
-Original Message-
From: Benson Margulies
Sent: Saturday, September 17, 2011 11:44
On Sat, Sep 17, 2011 at 11:45 AM, Jason Pyeron wrote:
-Original Message-
From: Jason van Zyl
Sent: Saturday, September 17, 2011 11:13
On Sep 17, 2011, at 11:06 AM, Jason Pyeron
Ok. Thanks for this update.
We 'll be patient
Arnaud
Le 17 sept. 2011 à 17:53, Jason van Zyl ja...@maven.org a écrit :
The latest is always available here:
http://eclipse.org/proposals/technology.aether/
We still have to refactor the package names as well which we are going to do
I don't have a view on the way things happen nor how much steps are still
pending, but FYI, things are on their way: there is now a project page [1]
(even if empty), and CLAs are on their way: I was asked for it a week ago (i
suppose it's the same for others) and replied a few days ago, I'm now
my comments are in the Jira issue
but the summary is: I don't think this scenario requires a new feature
Regards,
Hervé
Le samedi 17 septembre 2011, Jason Pyeron a écrit :
-Original Message-
From: Jason van Zyl
Sent: Saturday, September 17, 2011 11:13
To: Maven Developers List
-Original Message-
From: Hervé BOUTEMY
Sent: Saturday, September 17, 2011 12:33
To: Maven Developers List
Subject: Re: Request for review and comment
http://jira.codehaus.org/browse/MNG-5167
my comments are in the Jira issue
but the summary is: I don't think this scenario
Hi Folks,
With WAGON-348, the wagon-http based on Apache HttpClient include now
http connection pool mechanism.
This prevent creating http(s) connection for each artifacts requests !
The patch simply remove lightweight and replace it with a shaded jar
of wagon http with classes relocation of
I assume all the ITs pass with this change?
On Sep 17, 2011, at 2:13 PM, Olivier Lamy wrote:
Hi Folks,
With WAGON-348, the wagon-http based on Apache HttpClient include now
http connection pool mechanism.
This prevent creating http(s) connection for each artifacts requests !
The patch
In wagon-2 we approximately doubled the number of tests. I even finally
activated the TCK which John wrote some time ago.
But what we miss imo are tests for the integration of wagon in maven core
itself.
I think it's definitely worth a try, but we should be aware that we might get
some corner
At the very least all the current ITs must pass.
Otherwise I'm not in favour of switching out the default provider. The ITs are
the acid test and the expectation for user-end behaviour.
On Sep 17, 2011, at 3:03 PM, Mark Struberg wrote:
In wagon-2 we approximately doubled the number of tests.
Results :
Failed tests:
testit(org.apache.maven.it.MavenITmng4387QuietLoggingTest):
expected:[] but
was:[#,
JRebel 4.0.3 (201107251640), (c) Copyright ZeroTurnaround OU,
Estonia, Tartu., Over the last 1 days JRebel prevented , at
Hello Barrie,
I am coming back to see if you or anyone else had a chance to look into this
issue and its proposed solutions?
Thanks,
Jean-Noel
2011/9/2 Barrie Treloar baerr...@gmail.com
2011/9/2 Jean-Noël Rouvignac jn.rouvig...@gmail.com:
Hello,
Are there any news about this issue
Would a compromise to something using the baseDir of the project ( or root
project ) and not an arbitrary relative path?
I can see a benefit to this, but I can also see not wanting to allow the user
to reach outside their SCM controlled project.
On 18/09/2011, at 3:42 AM, Benson Margulies
2011/9/18 Jean-Noël Rouvignac jn.rouvig...@gmail.com:
Hello Barrie,
I am coming back to see if you or anyone else had a chance to look into this
issue and its proposed solutions?
Sorry I've been home sick and haven't had a chance.
And since its classpath related I've been trying to find out
-Original Message-
From: Mark Derricutt
Sent: Saturday, September 17, 2011 18:02
To: Maven Developers List
Subject: Re: Request for review and comment
http://jira.codehaus.org/browse/MNG-5167
Would a compromise to something using the baseDir of the
project ( or root project )
I'm waiting for my CEO to sort out the CLA stuff
On 17 September 2011 17:19, Hervé BOUTEMY herve.bout...@free.fr wrote:
I don't have a view on the way things happen nor how much steps are still
pending, but FYI, things are on their way: there is now a project page [1]
(even if empty), and CLAs
On 11-09-17 09:00 AM, Jason Pyeron wrote:
Is the metadata in the revision? Only export the revision. Defense, Healthcare,
life safety, large organizations, all of these type of organizations have rules,
we are trying to make Maven more adaptable so it can be used there on projectes
where the
-Original Message-
From: Manfred Moser
Sent: Saturday, September 17, 2011 23:38
To: dev@maven.apache.org
Subject: Re: Request for review and comment
http://jira.codehaus.org/browse/MNG-5167
On 11-09-17 09:00 AM, Jason Pyeron wrote:
Is the metadata in the revision? Only
On 11-09-17 08:55 PM, Jason Pyeron wrote:
-Original Message-
From: Manfred Moser
Sent: Saturday, September 17, 2011 23:38
To: dev@maven.apache.org
Subject: Re: Request for review and comment
http://jira.codehaus.org/browse/MNG-5167
On 11-09-17 09:00 AM, Jason Pyeron wrote:
Is the
-Original Message-
From: Manfred Moser
Sent: Sunday, September 18, 2011 0:24
To: Maven Developers List
Subject: Re: Request for review and comment
http://jira.codehaus.org/browse/MNG-5167
On 11-09-17 08:55 PM, Jason Pyeron wrote:
-Original Message-
From: Manfred
with ${maven.home}, you can have your use case
for other options:
- POM is a nonsense to me
- WORKINGDIRECTORY too: notice that it can be done with ${user.dir}, if you
really want to
the more I'm thinking at this, the more I'm convinced we should not accept
relative path at all: with java
we have multiple jobs on ASF's Jenkins instance that fail when publishing the
result (after a success in the build)
does anybody know the cause?
Regards,
Hervé
Le dimanche 18 septembre 2011, Apache Jenkins Server a écrit :
See https://builds.apache.org/job/maven-wagon/56/changes
Changes:
36 matches
Mail list logo
