So the plan is that we're going to do a release of spice-inject as fast as we
can and then do the merge. So that will likely happen early next week. Until
then folks can pick things up from Benjamin's branch:
http://github.com/bentmann/maven-3
On Aug 19, 2010, at 4:20 AM, Tamás Cservenák wrote:
Cool!
+1 for merges!
Thanks,
~t~
2010/8/18 Arnaud Héritier
> Hi,
>
> I just rebuilt aether and maven3 and I have now : 14M/125M
> We are really near of 9M/125M we have in beta2
> Perfect !!!
>
> Let's go for a merge in trunk ??
>
> Arnaud
>
>
>>
>> There's been little to no feedback on beta-2 so I honestly don't think it
>> matters.
> feedback from Maven developers was good: since people complain only when it
> does not work, I suppose no feedback = it works as good as for Maven
> developers.
>
I agree, I consider also the no feedback
+1
On 18 August 2010 22:02, Jason van Zyl wrote:
>
> On Aug 18, 2010, at 1:43 PM, Arnaud Héritier wrote:
>
>> Hi,
>>
>> I just rebuilt aether and maven3 and I have now : 14M/125M
>> We are really near of 9M/125M we have in beta2
>> Perfect !!!
>>
>> Let's go for a merge in trunk ??
>>
>
>
Le jeudi 19 août 2010, Jochen Wiedmann a écrit :
> On Wed, Aug 18, 2010 at 11:18 PM, Hervé BOUTEMY
wrote:
> > I have only one concern with current maven-3 code in GitHub: it's not
> > compatible with maven-site-plugin 3.0-beta-1
>
> I think, that's a blocker for a new beta release, but not for a
Le mercredi 18 août 2010, Olivier Lamy a écrit :
> 2010/8/18 Benjamin Bentmann :
> > Olivier Lamy wrote:
> >> So maybe having a compatibility even if we are in a beta release
> >> process (benjamin ?)
> >
> > I don't feel motivated to maintain yet another layer of compat/bridge
> > code for the sa
On Wed, Aug 18, 2010 at 11:18 PM, Hervé BOUTEMY wrote:
> I have only one concern with current maven-3 code in GitHub: it's not
> compatible with maven-site-plugin 3.0-beta-1
I think, that's a blocker for a new beta release, but not for a merge, isn't it?
Jochen
--
I Am What I Am And That's Al
2010/8/18 Benjamin Bentmann :
> Olivier Lamy wrote:
>
>> So maybe having a compatibility even if we are in a beta release
>> process (benjamin ?)
>
> I don't feel motivated to maintain yet another layer of compat/bridge code
> for the sake of single beta plugin.
ok np for me.
>
>
> Benjamin
>
> -
Olivier Lamy wrote:
So maybe having a compatibility even if we are in a beta release
process (benjamin ?)
I don't feel motivated to maintain yet another layer of compat/bridge
code for the sake of single beta plugin.
Benjamin
---
2010/8/18 Hervé BOUTEMY :
> Le mercredi 18 août 2010, Olivier Lamy a écrit :
>> Herve : regarding site plugin there is a patch here (
>> https://issues.sonatype.org/secure/attachment/23615/site-plugin-guice-eathe
>> r.patch ).
> yes, I know the patch (I studied it since our last discussion), but th
Le mercredi 18 août 2010, Olivier Lamy a écrit :
> Herve : regarding site plugin there is a patch here (
> https://issues.sonatype.org/secure/attachment/23615/site-plugin-guice-eathe
> r.patch ).
yes, I know the patch (I studied it since our last discussion), but that
doesn't make the future maven
Well.. can we get that patch applied and a new release of the maven 3 site
plugin as well then.
manfred
PS: beta 2 works on all my projects..
> Hi,
> Let's go for merge ! (with last spice version 1.3.3-SNAPSHOT or
> released version to have a fix for SPICE-34).
>
> Herve : regarding site plugin
Hi,
Let's go for merge ! (with last spice version 1.3.3-SNAPSHOT or
released version to have a fix for SPICE-34).
Herve : regarding site plugin there is a patch here (
https://issues.sonatype.org/secure/attachment/23615/site-plugin-guice-eather.patch
).
2010/8/18 Hervé BOUTEMY :
> Le mercredi 18
Le mercredi 18 août 2010, Jason van Zyl a écrit :
> On Aug 18, 2010, at 1:43 PM, Arnaud Héritier wrote:
> > Hi,
> >
> > I just rebuilt aether and maven3 and I have now : 14M/125M
> > We are really near of 9M/125M we have in beta2
> > Perfect !!!
> >
> > Let's go for a merge in trunk ??
>
>
On Aug 18, 2010, at 1:43 PM, Arnaud Héritier wrote:
> Hi,
>
> I just rebuilt aether and maven3 and I have now : 14M/125M
> We are really near of 9M/125M we have in beta2
> Perfect !!!
>
> Let's go for a merge in trunk ??
>
Yup, let's merge it all in and move forward.
> Arnaud
>
> On Aug
On Aug 18, 2010, at 10:47 PM, Hervé BOUTEMY wrote:
> Le mercredi 18 août 2010, Jason van Zyl a écrit :
>> On Aug 18, 2010, at 12:59 PM, Hervé BOUTEMY wrote:
>>> Le mercredi 18 août 2010, Arnaud Héritier a écrit :
It's always in GitHub or the merge started in trunk ?
>>>
>>> BTW, we have 3.
Le mercredi 18 août 2010, Jason van Zyl a écrit :
> On Aug 18, 2010, at 12:59 PM, Hervé BOUTEMY wrote:
> > Le mercredi 18 août 2010, Arnaud Héritier a écrit :
> >> It's always in GitHub or the merge started in trunk ?
> >
> > BTW, we have 3.0-beta-2 released without Guice nor Aether and GitHub wit
On Wed, Aug 18, 2010 at 10:10 PM, Jason van Zyl wrote:
> There's been little to no feedback on beta-2 so I honestly don't think it
> matters.
That's good news, isn't it? :-)
--
I Am What I Am And That's All What I Yam (Popeye)
---
Hi,
I just rebuilt aether and maven3 and I have now : 14M/125M
We are really near of 9M/125M we have in beta2
Perfect !!!
Let's go for a merge in trunk ??
Arnaud
On Aug 7, 2010, at 2:37 PM, Arnaud Héritier wrote:
> Results I had yesterday were :
>
> 3.0-benjamin (built yesterday) : 14
I'd love to offer more feedback on beta-2, but since it totally breaks our
builds it's a non-starter. Without reworking our entire build setup ( which
we're going to do anyway when we move to git ) M3 is effectively unusable
for my main $work project.
Which is a shame as all the new things look g
On Aug 18, 2010, at 12:59 PM, Hervé BOUTEMY wrote:
> Le mercredi 18 août 2010, Arnaud Héritier a écrit :
>> It's always in GitHub or the merge started in trunk ?
> BTW, we have 3.0-beta-2 released without Guice nor Aether and GitHub with
> both
> Guice and Aether.
> What about merging Guice in s
Le mercredi 18 août 2010, Arnaud Héritier a écrit :
> It's always in GitHub or the merge started in trunk ?
BTW, we have 3.0-beta-2 released without Guice nor Aether and GitHub with both
Guice and Aether.
What about merging Guice in svn trunk, so we can test the 3 major steps: 3.0-
beta-2, +Guice,
Arnaud Héritier wrote:
It's always in GitHub or the merge started in trunk ?
It's still in github.
I'll try to build and test it this evening.
Cool, thanks!
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apach
It's always in GitHub or the merge started in trunk ?
I'll try to build and test it this evening.
Thx
On Aug 18, 2010, at 1:59 PM, Benjamin Bentmann wrote:
> Arnaud Héritier wrote:
>
>> 3.0-benjamin (built yesterday) : 14M/2488M in 5:23.389s (It probably swapped
>> a lot)
>
> Should be fixed
Arnaud Héritier wrote:
3.0-benjamin (built yesterday) : 14M/2488M in 5:23.389s (It probably swapped a
lot)
Should be fixed now, would be cool if you could double-check when time
allows.
Benjamin
-
To unsubscribe, e-mail:
Results I had yesterday were :
3.0-benjamin (built yesterday) : 14M/2488M in 5:23.389s (It probably swapped a
lot)
3.0-beta-2 (downloaded few minutes ago) : 9M/125M built in 23.723s
2.2.1 : 67M/136M built in 30s
I only built one module :
http://svn.exoplatform.org/projects/ecms/trunk/packaging/
On Aug 7, 2010, at 7:26 AM, Brett Porter wrote:
>
> On 07/08/2010, at 12:44 AM, Arnaud Héritier wrote:
>
>> The advantage is to do what I did this morning in few minutes.
>> I found a OOME on Aether/Guice branch (reported to benjamin but not in MNG
>> because it's not yet integrated) and then
On 07/08/2010, at 12:44 AM, Arnaud Héritier wrote:
> The advantage is to do what I did this morning in few minutes.
> I found a OOME on Aether/Guice branch (reported to benjamin but not in MNG
> because it's not yet integrated) and then I validated it wasn't here in
> current trunk.
> The prob
28 matches
Mail list logo
