I am inclined to agree, having wrestled with this all day.
On Tue, Jul 5, 2011 at 9:10 PM, Brett Porter wrote:
>
> On 06/07/2011, at 4:25 AM, Benson Margulies wrote:
>
>> I'm posting this thread, even though I can pretty much guarantee that
>> I'm not going to be able to muster the effort to act
OK, how about this: If I don't see any objection by mid-tomorrow EDT,
I'll set the 'next version' in the branch to 1.0, and start a release?
On Tue, Jul 5, 2011 at 9:17 PM, Brett Porter wrote:
> I'd probably suggest releasing the 1.x line as 1.0 pretty much as is (there
> wasn't much to finish o
I'd probably suggest releasing the 1.x line as 1.0 pretty much as is (there
wasn't much to finish other than the HTTP ping pong that Mark has taken over to
2.x). That gives a stable place for any minor releases to go from and all the
dev can focus on the trunk.
- Brett
On 06/07/2011, at 5:33 A
On 06/07/2011, at 4:25 AM, Benson Margulies wrote:
> I'm posting this thread, even though I can pretty much guarantee that
> I'm not going to be able to muster the effort to act on it.
>
> Sitting over at mojo is a wagon-maven-plugin. It wants to enumerate
> all the artifacts in a repo. It tries
On 06/07/2011, at 3:13 AM, Benson Margulies wrote:
> Mark,
>
> The unit tests fail with the current version of neko. I have them
> passing with jsoup. So it's less work to use jsoup than the latest
> neko, not even counting the effort of getting to publish.
>
> I want to go ahead ...
IMO, go f
Thanks ! :-)
2011/7/6 Hervé BOUTEMY :
> I worked on IRC with Olivier to understand more precisely what is available.
> Then added documentation to maven-reporting-exec and maven-site-plugin.
>
> I won't repeat what is in the doc: please ping if it is not clear
>
> Regards,
>
> Hervé
>
> Le mardi 5
I worked on IRC with Olivier to understand more precisely what is available.
Then added documentation to maven-reporting-exec and maven-site-plugin.
I won't repeat what is in the doc: please ping if it is not clear
Regards,
Hervé
Le mardi 5 juillet 2011, Dennis Lundberg a écrit :
> On 2011-07-0
They do. See https://issues.apache.org/jira/browse/SOLR-2634 for the
whole discussion of *what* they do.
On Tue, Jul 5, 2011 at 5:18 PM, Olivier Lamy wrote:
> They cannot use maven ant tasks ? (http://maven.apache.org/ant-tasks/ )
>
> 2011/7/5 Benson Margulies :
>> Thanks. These people have an an
Meh! there's a lot of maven haters out there... I'm just surprised I was
able to get as far as I have got with Cassandra!
On 5 July 2011 22:18, Olivier Lamy wrote:
> They cannot use maven ant tasks ? (http://maven.apache.org/ant-tasks/ )
>
> 2011/7/5 Benson Margulies :
> > Thanks. These people h
They cannot use maven ant tasks ? (http://maven.apache.org/ant-tasks/ )
2011/7/5 Benson Margulies :
> Thanks. These people have an ant build, and have concocted what you
> saw out of chewing gum more or less. I'm trying to help therm just
> deploy snaps to repository.apache.org.
>
> On Tue, Jul 5,
Thanks. These people have an ant build, and have concocted what you
saw out of chewing gum more or less. I'm trying to help therm just
deploy snaps to repository.apache.org.
On Tue, Jul 5, 2011 at 3:43 PM, Olivier Lamy wrote:
> Maybe Out of Maven Topic : This place in Jenkins is not designed to
>
On 2011-07-05 22:00, Olivier Lamy wrote:
> 2011/7/5 Dennis Lundberg :
>> On 2011-07-04 20:11, Dennis Lundberg wrote:
>>> On 2011-07-03 00:14, Hervé BOUTEMY wrote:
AFAIK, code is ok: I'm closing MSITE-560
>>>
>>> Great, thanks!
>>>
the only thing to confirm is the documentation: there is a
2011/7/5 Dennis Lundberg :
> On 2011-07-04 20:11, Dennis Lundberg wrote:
>> On 2011-07-03 00:14, Hervé BOUTEMY wrote:
>>> AFAIK, code is ok: I'm closing MSITE-560
>>
>> Great, thanks!
>>
>>> the only thing to confirm is the documentation: there is a TODO in
>>> maven-3.apt.vm that we should check c
Maybe Out of Maven Topic : This place in Jenkins is not designed to
serve as Maven repository.
Have a look at this plugin :
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Maven+Repository+Server
--
Olivier Lamy
http://twitter.com/olamy | http://www.linkedin.com/in/olamy
2011/7/5 Benson Marg
why not:
1. release
2. make mvn trunk use it
3. run whatever we have for integration tests
4. 2.0.1 if anything serious turns up
On Jul 5, 2011, at 3:31 PM, Mark Struberg wrote:
> wagon-2 contains almost 50% _more_ tests :)
>
> basically the following things have been done:
>
> * upgrade to jav
wagon-2 contains almost 50% _more_ tests :)
basically the following things have been done:
* upgrade to java5 libs - that was not much, but we were able to upgrade to
newer dependencies which don't support java1.4 anymore.
* upgrade to junit-4.8.x
* upgrade to httpclient-4. This mostly concerns
I don't have enough information to judge. What's the effort level
needed to finish 2?
On Tue, Jul 5, 2011 at 2:48 PM, Mark Struberg wrote:
> question for me is if we like to push hard on wagon-2.0 (which got love
> lately) or just like to release a minor-bugfixed 1.0 first?
>
> LieGrue,
> strub
question for me is if we like to push hard on wagon-2.0 (which got love lately)
or just like to release a minor-bugfixed 1.0 first?
LieGrue,
strub
--- On Tue, 7/5/11, Kristian Rosenvold wrote:
> From: Kristian Rosenvold
> Subject: Re: Next wagon question, beta?
> To: "Maven Developers List"
On 2011-07-04 20:11, Dennis Lundberg wrote:
> On 2011-07-03 00:14, Hervé BOUTEMY wrote:
>> AFAIK, code is ok: I'm closing MSITE-560
>
> Great, thanks!
>
>> the only thing to confirm is the documentation: there is a TODO in
>> maven-3.apt.vm that we should check carefully: I'm personnally lost on
I'm posting this thread, even though I can pretty much guarantee that
I'm not going to be able to muster the effort to act on it.
Sitting over at mojo is a wagon-maven-plugin. It wants to enumerate
all the artifacts in a repo. It tries to do this by walking the repo
as a directory tree.
Sadly for
+1 for 1.0. Version numbers are free, beta on 5th year is ridiculous.
Den 5. juli 2011 kl. 20:28 skrev Benson Margulies :
> Why is wagon still all 'beta'. Could we possibly make the next release
> just '1.0'? It seems embarassing to me to keep calling this production
> code beta.
>
>
Mark or anyone else:
Please point your browser to :
https://builds.apache.org/job/Lucene-Solr-Maven-trunk/lastSuccessfulBuild/artifact/maven_artifacts/.
As of my repairs, the HtmlFileListParser no longer explodes on this
soi-disant repository. But when it analyzes this page, it comes up
with a li
Why is wagon still all 'beta'. Could we possibly make the next release
just '1.0'? It seems embarassing to me to keep calling this production
code beta.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional com
sure, go on!
LieGrue,
strub
--- On Tue, 7/5/11, Benson Margulies wrote:
> From: Benson Margulies
> Subject: Re: How are wagon-providers released?
> To: "Maven Developers List"
> Date: Tuesday, July 5, 2011, 5:13 PM
> Mark,
>
> The unit tests fail with the current version of neko. I
> have th
And BTW, plexus-io 2.0 supports java 1.7 file attributes on posix
compliant systems. No more ugly forks.
Kristian
Den 5. juli 2011 kl. 18:18 skrev Stephen Connolly
:
> Hmmm but that requires plexus-utils 3.0 which blows up all the tests...
>
> On 5 July 2011 15:40, Olivier Lamy wrote:
>
>> Rece
nah, all fine with jsoup :)
I just left a comment in WAGON-338 - almost as fast as you responding the email
:D
LieGrue,
strub
--- On Tue, 7/5/11, Benson Margulies wrote:
> From: Benson Margulies
> Subject: Re: How are wagon-providers released?
> To: "Maven Developers List"
> Date: Tuesday,
Mark,
The unit tests fail with the current version of neko. I have them
passing with jsoup. So it's less work to use jsoup than the latest
neko, not even counting the effort of getting to publish.
I want to go ahead ...
--benson
On Tue, Jul 5, 2011 at 1:00 PM, Mark Struberg wrote:
> Hi Benson
Mark,
It's nothing to do with 2.0 except that the use of neko happens in there.
I have a lot of very unhappy experience with neko, over several years.
I remove it wherever I go. If you look at WAGON-338, you will see what
I ran into.
I'm coding faster than you are emailing! So I've already commi
Hi Benson!
A general note on wagon-2.0:
Are you sure that this is related with wagaon-http-shared4?
I fairly recently upgraded wagon from commons-httpclient-3 to
httpcomponents-httpclient-4 (thus the name 4). But this is not released yet!
Please note that wagon-2.0 is a pretty huge rework, whi
OK, I'll plan on backporting, unless someone is really disturbed by
switching to jsoup.
On Tue, Jul 5, 2011 at 12:31 PM, Dennis Lundberg wrote:
> On 2011-07-05 17:49, Benson Margulies wrote:
>> I just ran smack into a bug in wagon-maven-plugin which is really a
>> bug in wagon-http-lightweight wh
On 2011-07-05 17:49, Benson Margulies wrote:
> I just ran smack into a bug in wagon-maven-plugin which is really a
> bug in wagon-http-lightweight which is really a bug in
> wagon-http-shared4 which is really a bug in cyberneko.
>
> I can fix this by upgrading the later to use jsoup instead of cyb
Could that be related to the java 1.5 requirement of p-u 3.0 ? p-io
2.0 and p-archiver 2.0 are also 1.5.
Kristian
Den 5. juli 2011 kl. 18:18 skrev Stephen Connolly
:
> Hmmm but that requires plexus-utils 3.0 which blows up all the tests...
>
> On 5 July 2011 15:40, Olivier Lamy wrote:
>
>> Rece
I just ran smack into a bug in wagon-maven-plugin which is really a
bug in wagon-http-lightweight which is really a bug in
wagon-http-shared4 which is really a bug in cyberneko.
I can fix this by upgrading the later to use jsoup instead of cyberneko.
Then what? It looks like all of the providers
Got it. Thanks.
On Tue, Jul 5, 2011 at 11:24 AM, Stephen Connolly
wrote:
> or dependencies in the specific plugin looking for the wagon
>
> On 5 July 2011 16:20, Benson Margulies wrote:
>
>> What controls the version of wagon-http-lightweight in use? extensions?
>>
>> ---
or dependencies in the specific plugin looking for the wagon
On 5 July 2011 16:20, Benson Margulies wrote:
> What controls the version of wagon-http-lightweight in use? extensions?
>
> -
> To unsubscribe, e-mail: dev-unsubscr...
What controls the version of wagon-http-lightweight in use? extensions?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hmmm but that requires plexus-utils 3.0 which blows up all the tests...
On 5 July 2011 15:40, Olivier Lamy wrote:
> Recently Kristian released 2.0.
>
> 2011/7/5 Stephen Connolly :
> > Hmmm I wasn't subscribed to dev@p.c.o, resending...
> >
> > On 5 July 2011 15:24, Stephen Connolly
> > wrote:
On Tue, Jul 5, 2011 at 2:50 AM, Kasun Gajasinghe wrote:
>> On Jul 4, 2011, at 11:48 AM, Robert Burrell Donkin wrote:
>> > After many problems, I've now opted to uninstall the official Maven
>> > and Ant packages (and Eclipse...), and use instead a set of scripts
>> > which accurately and fle
On 07/02/2011 08:04 PM, Benson Margulies wrote:
In maven-shade-plugin, I modified my local copy to point to
maven-plugins version 20 as parent. This in turn points to maven
parent 20. Which configures the compiler plugin for source level 1.5.
Perhaps you mean you pointed to maven-plugins-21.pom
Recently Kristian released 2.0.
2011/7/5 Stephen Connolly :
> Hmmm I wasn't subscribed to dev@p.c.o, resending...
>
> On 5 July 2011 15:24, Stephen Connolly
> wrote:
>>
>> Or push it now if you can?
>> I'd like to get m-dependency-p out and this is blocking
>
--
Olivier Lamy
http://twitter.c
Hmmm I wasn't subscribed to dev@p.c.o, resending...
On 5 July 2011 15:24, Stephen Connolly wrote:
> Or push it now if you can?
>
> I'd like to get m-dependency-p out and this is blocking
>
Or push it now if you can?
I'd like to get m-dependency-p out and this is blocking
Hi,
Here a vote to release the first version of maven-reporting-exec component
This component contains necessary code to run site plugin with maven 3.
So currently no jira issues as it's a simply an extraction of code
from maven site plugin for maven 3 branch [1]
Staging repo : https://repository
Hello,
You can have a look at the "simple" embedder, I have done for jenkins [1].
Didn't have time yet to add this here (as it need some cleanup before).
Or the recent stuff from John here [2]
--
Olivier Lamy
http://twitter.com/olamy | http://www.linkedin.com/in/olamy
[1] https://github.com/jenk
You have correctly diagnosed my incorrect diagnosis.
On Tue, Jul 5, 2011 at 4:14 AM, Dennis Lundberg wrote:
> On 2011-07-05 01:51, Benson Margulies wrote:
>> On Mon, Jul 4, 2011 at 6:11 PM, Dennis Lundberg wrote:
>>> Hi
>>>
>>> I'm trying to replace an old version 2.0 MavenEmbedder in the
>>> as
Have a look at #getLocalRepository() method around line 352 in [1].
[1]
http://git.eclipse.org/c/m2e/m2e-core.git/tree/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/embedder/MavenImpl.java?id=releases/1.0/1.0.0.20110607-2117
--
Regards,
Igor
On 11-07-05 12:14 PM, Dennis Lundberg wrot
On 2011-07-05 01:51, Benson Margulies wrote:
> On Mon, Jul 4, 2011 at 6:11 PM, Dennis Lundberg wrote:
>> Hi
>>
>> I'm trying to replace an old version 2.0 MavenEmbedder in the
>> aspectj-maven-plugin, over at mojo@codehaus. That's because we can't
>> upgrade other Maven core dependencies while the
47 matches
Mail list logo
