a lot of things were done in 0.9.0.M3: will need to review
notice the apidocs is not published yet
http://download.eclipse.org/aether/aether-core/0.9.0.M3/apidocs/
we need it to publish Maven core site
then we probably should create a Jira issue to keep track of this important
change (I have no
I was distracted from Maven yesterday (yes, there is a life...)
Will need to work on it later
Regards,
Hervé
Le dimanche 28 juillet 2013 18:25:58 Hervé BOUTEMY a écrit :
> I'd like to work on http://jira.codehaus.org/browse/MNG-5319 tonight
>
> so if you wait for tomorrow...
>
> notice there
On Jul 28, 2013 9:40 PM, "Baptiste MATHUS" wrote:
> From an external PoV I can only think of it being beneficial to show the
> project is up and running.
>
Hello,
this is a good point as well, one of our architects asked me 6 months ago,
wether Maven was dead, because no new releases were coming
+1
I agree that slight less frequent releases can be easier to users to cope with.
The 6-8 week period is ok with me.
-Chris
Sent from my iPhone
On 29/07/2013, at 2:48 AM, "Robert Scholte" wrote:
> Hi,
>
> Personally I'm not a huge fan of the release-model as done by Jenkins,
> meaning rel
Hi,
I integrated Aether 0.0.9.M3 on a branch for Maven 3.1.x and all the Maven ITs
pass:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=604bf25450be1225c2e856d2045b871d8840376e
Looks good for Maven.
On Jul 28, 2013, at 3:45 PM, Benjamin Bentmann wrote:
> Hi,
>
> I just stage
I staged a release of the remote resources plugin for anyone who wants to try:
https://repository.apache.org/content/repositories/maven-030/
How about we do a simultaneous release vote for the core and the remote
resources plugin?
On Jul 28, 2013, at 3:56 PM, Dennis Lundberg wrote:
> Hi,
>
>
I still don't understand:
- why I can't make it fail on my local machine
- why the fix requires dependencies as runtime
but at leasat, we'll have a fixed Jenkins build: that'll be good to avoid
failure notices
thank you
Hervé
Le dimanche 28 juillet 2013 16:50:58 Jason van Zyl a écrit :
> Fix f
Fix for the ITs pushed, as I noted in the commit this needs to be examined
again to simply the process. It's very annoying.
On Jul 28, 2013, at 12:25 PM, Hervé BOUTEMY wrote:
> I'd like to work on http://jira.codehaus.org/browse/MNG-5319 tonight
>
> so if you wait for tomorrow...
>
> notice t
Yes, it should be released and I think we need to try and stop putting plugin
snapshot dependencies on master as a matter of course so that it's always as
close to releasable. In the case of the sisu dependencies I just kept a branch
here locally and flipped the release version when it worked.
Hi,
There is currently a SNAPSHOT dependency on maven-remote-resources-plugin.
This was done in this commit by Daniel to improve the LICENCE file:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=b4dc8931f2cc7b56302df78c03a7db57211cd3a7
The question is whether we need to push out a
+1. Very good reasoning, Stephen.
Let's just try and accelerate at least just a bit to see how it works. If
it's difficult to handle, then just brake a bit and that's all.
>From an external PoV I can only think of it being beneficial to show the
project is up and running.
Thanks Jason.
2013/7/
On Sunday, 28 July 2013, Robert Scholte wrote:
> Hi,
>
> Personally I'm not a huge fan of the release-model as done by Jenkins,
> meaning releasing once or twice a week with only a few fixes.
I am a really big fan of this model... But it won't work the same for
Maven...
Where the model falls do
On Jul 28, 2013, at 1:16 PM, Hervé BOUTEMY wrote:
> you're getting same failures than ASF's Jenkins
>
That's good. I'll take a look.
I always use this locally:
mvn clean install -Prun-its,embedded -Dmaven.repo.local=`pwd`/repo
> but I can't reproduce here: everything run well (it's still ru
On Jul 28, 2013, at 12:48 PM, "Robert Scholte" wrote:
> Hi,
>
> Personally I'm not a huge fan of the release-model as done by Jenkins,
> meaning releasing once or twice a week with only a few fixes.
> As a user I'm not going to update for every new release, it most have real
> value before I
you're getting same failures than ASF's Jenkins
but I can't reproduce here: everything run well (it's still running at the
moment, but I waited to check these 2 ITs before reporting)
I know there is something I don't understand, but I don't know what
I wrote a little shell script to run the ITs
Le dimanche 28 juillet 2013 18:48:44 Robert Scholte a écrit :
> Hi,
>
> Personally I'm not a huge fan of the release-model as done by Jenkins,
> meaning releasing once or twice a week with only a few fixes.
> As a user I'm not going to update for every new release, it most have real
> value before
Hi,
Personally I'm not a huge fan of the release-model as done by Jenkins,
meaning releasing once or twice a week with only a few fixes.
As a user I'm not going to update for every new release, it most have real
value before I upgrade.
As both developer and user it's much more easier to recog
This is what I get locally:
Results :
Failed tests:
MavenITmng5482AetherNotFoundTest>AbstractMavenIntegrationTestCase.runTest:220->testPluginDependency:49->check:90
ClassNotFoundException message was not found in output.
Tests in error:
MavenITmng3703ExecutionProjectWithRelativePathsTes
ok, I see the reasoning, and since "tomorrow" is another day...
if you can wait for the end of the day to launch the release, it will give me
the few hours to find if I can get it done rapidly
Le dimanche 28 juillet 2013 12:36:32 Jason van Zyl a écrit :
> On Jul 28, 2013, at 12:25 PM, Hervé BOUT
+1 on pushing out regression-free fixes and moving forward.
+1 on frequent and small releases and moving forward.
On Sun, Jul 28, 2013 at 6:36 PM, Jason van Zyl wrote:
> On Jul 28, 2013, at 12:25 PM, Hervé BOUTEMY wrote:
>
> > I'd like to work on cd tonight
> >
> > so if you wait for tomorrow..
On Jul 28, 2013, at 12:25 PM, Hervé BOUTEMY wrote:
> I'd like to work on cd tonight
>
> so if you wait for tomorrow...
>
I don't really want to wait, why can't that just go in next week? You don't
know how long it will take and I think we should just start releasing what we
have.
> notice t
I'd like to work on http://jira.codehaus.org/browse/MNG-5319 tonight
so if you wait for tomorrow...
notice there are 2 ITs failing on ASF's Jenkins because of a failure to find
artifacts that are available AFAIK in the local repo: I suppose I'm missing
something trivial in the configuration
Can
I'd like to release Maven 3.1.1 and try to get the cadence revived for minor
version releases by trying to release minor versions as frequently as there are
fixes to make available.
Just a couple simple fixes:
[MNG-5499] maven-aether-provider leaks Sisu Plexus and ObjectWeb classes onto
the cl
+1
On 27 July 2013 22:25, Dennis Lundberg wrote:
> Hi,
>
> We solved 4 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11241&styleName=Html&version=13719
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=tru
if someone is interested: this build fails when run in parallel mode (-T3) but
builds fine with this -T3 removed
I could reproduce the failure on my local machine.
If someone is interested to discover what goes wrong in parallel...
I won't investigate myself: I just wanted no false positive on A
+1
Regards,
Hervé
Le samedi 27 juillet 2013 23:25:36 Dennis Lundberg a écrit :
> Hi,
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11241&styleName=H
> tml&version=13719
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure
26 matches
Mail list logo
