Dennis Lundberg wrote:
Hi
I've gone through JIRA tonight and have made sure that fixed issues have
the correct fix version(s), as many issues have been fixed for both 2.3
and 3.0-beta-4.
Looking at the road map [1] there are 24 of 25 issues fixed for 2.3 and
29 of 30 issues fixed for 3.0-beta
I didn't write the page.
2011/3/16 Arnaud Héritier :
> Brian,
>
> No link or reference to Apache ? :(
>
> Arnaud
>
> On Tue, Mar 15, 2011 at 3:43 PM, Brian Fox wrote:
>> Page is updated.
>>
>> On Tue, Mar 15, 2011 at 10:18 AM, Brian Fox wrote:
>>> It should read something like either :
>>>
>>>
Brian,
No link or reference to Apache ? :(
Arnaud
On Tue, Mar 15, 2011 at 3:43 PM, Brian Fox wrote:
> Page is updated.
>
> On Tue, Mar 15, 2011 at 10:18 AM, Brian Fox wrote:
>> It should read something like either :
>>
>> bringing M2eclipse to eclipse...
>>
>> or
>>
>> bringing Maven support
Hi
I've gone through JIRA tonight and have made sure that fixed issues have
the correct fix version(s), as many issues have been fixed for both 2.3
and 3.0-beta-4.
Looking at the road map [1] there are 24 of 25 issues fixed for 2.3 and
29 of 30 issues fixed for 3.0-beta-4. Given the amount of fix
On 2011-03-16 21:01, Lukas Theussl wrote:
>
> is there a special reason for this? I didn't notice any interference
> effects and the deploy locations were chosen such that they correspond
> to common default values (eg stage-deploy = deploy + "staging"), so if
> there is a problem, maybe this need
is there a special reason for this? I didn't notice any interference
effects and the deploy locations were chosen such that they correspond
to common default values (eg stage-deploy = deploy + "staging"), so if
there is a problem, maybe this needs to be fixed separately?
-Lukas
denn...@apa
Thanks Lukas!
Things are looking good so far.
I'll run some more tests and report back.
On 2011-03-16 14:51, Lukas Theussl wrote:
>
> I think I fixed all the issues I introduced regarding test failures on
> windows, at least jenkins is happy again with trunk, but the 3.x branch
> fails at an un-
Ah, that was easy! :) Thanks!
-Lukas
Olivier Lamy wrote:
Sure see [1].
It's an issue with mvn 3.0.2 [2] and fixed in 3.0.3.
I have created a jira entry [3] for jenkins admin @asf
[1]
https://builds.apache.org/hudson/view/M-R/view/Maven/job/maven-site-plugin-3.x/jdk=JDK%201.5%20(latest),lab
Sure see [1].
It's an issue with mvn 3.0.2 [2] and fixed in 3.0.3.
I have created a jira entry [3] for jenkins admin @asf
[1]
https://builds.apache.org/hudson/view/M-R/view/Maven/job/maven-site-plugin-3.x/jdk=JDK%201.5%20(latest),label=Ubuntu/ws/target/it/MSITE-506/build.log
[2] http://jira.code
I think I fixed all the issues I introduced regarding test failures on
windows, at least jenkins is happy again with trunk, but the 3.x branch
fails at an un-related IT (MSITE-506):
https://builds.apache.org/hudson/view/M-R/view/Maven/job/maven-site-plugin-3.x/
However, it works for me local
10 matches
Mail list logo