(oracle
> >
> > version) they found jdk 7, jdk 6 is shown as end of life (with security
> > warning everywhere).
> >
> >Side effect is that, you play with the new features. (student later
> >
> > learn backward compatibility)
> >
> >
is that, you play with the new features. (student later
learn backward compatibility)
-Message d'origine-
De : Hervé BOUTEMY [mailto:herve.bout...@free.fr]
Envoyé : jeudi 20 juin 2013 07:19
À : Maven Developers List
Objet : Re: dist tooling
this is not a plugin for end users, only
evelopers List
Objet : Re: dist tooling
this is not a plugin for end users, only for internal Maven team: and once
it is scheduled daily on our Jenkins server, i don't expect us to run it on
our personal machines
so I don't think JDK7 nor Maven version requirements are a problem.
ITs
this is not a plugin for end users, only for internal Maven team: and once it
is scheduled daily on our Jenkins server, i don't expect us to run it on our
personal machines
so I don't think JDK7 nor Maven version requirements are a problem.
ITs would be nice, yes, to be sure things are detected
Hi,
I noticed there are no IT's. It shouldn't be too hard to write that. I can
make a setup for that in order to be able to execute some ITs
Although most of us want to use the latest and greatest, I have my doubts
about using JDK7 and M3.0.4 for compilation. Since our advice is to
compil
I'd like to have a look at it too.
Give me a couple of days.
Robert
Op Wed, 19 Jun 2013 00:11:55 +0200 schreef Hervé BOUTEMY
:
Thanks to Eric, we now have a tool to check dist content
And I just added it to our Jenkins instance, to build once a day: you
can look
at the result [1]
I just
Thanks to Eric, we now have a tool to check dist content
And I just added it to our Jenkins instance, to build once a day: you can look
at the result [1]
I just had to remove the preview of site, since Firefox isn't available on the
CI server (or not able to start in headless mode)
Any feedback
essage d'origine-
> De : Eric Barboni [mailto:eric.barb...@irit.fr]
> Envoyé : mercredi 29 mai 2013 11:35
> À : 'Maven Developers List'
> Objet : RE: CALL TO CONTRIBUTION: dist tooling
>
>
> It finally works(svn client issue reinstalling older tortoiseSVN)
&
d'origine-
De : Eric Barboni [mailto:eric.barb...@irit.fr]
Envoyé : mercredi 29 mai 2013 11:35
À : 'Maven Developers List'
Objet : RE: CALL TO CONTRIBUTION: dist tooling
It finally works(svn client issue reinstalling older tortoiseSVN)
http://svn.apache.org/r1487396
s
s,
>
> Eric
>
> -Message d'origine-
> De : Hervé BOUTEMY [mailto:herve.bout...@free.fr] Envoyé : mardi 28
> mai 2013 22:44 À : Maven Developers List Objet : Re: CALL TO
> CONTRIBUTION: dist tooling
>
> great!
> thanks for your help
>
> yes, a maven p
s,
>
> Eric
>
> -Message d'origine-
> De : Hervé BOUTEMY [mailto:herve.bout...@free.fr] Envoyé : mardi 28
> mai 2013 22:44 À : Maven Developers List Objet : Re: CALL TO
> CONTRIBUTION: dist tooling
>
> great!
> thanks for your help
>
> yes, a maven plugin ca
ic
>
> -Message d'origine-
> De : Hervé BOUTEMY [mailto:herve.bout...@free.fr]
> Envoyé : mardi 28 mai 2013 22:44
> À : Maven Developers List
> Objet : Re: CALL TO CONTRIBUTION: dist tooling
>
> great!
> thanks for your help
>
> yes, a maven plugin can
À : Maven Developers List
Objet : Re: CALL TO CONTRIBUTION: dist tooling
great!
thanks for your help
yes, a maven plugin can be a solution, even if report is overkill IMHO: we
won't publish result
Maven sandbox [1] should be writeable to any Apache committer, IIUC
Regards,
Hervé
[1] https://svn.a
ee (to facilitate patch
> creation) ?
>
> Regards,
>
> Eric
>
> -Message d'origine-
> De : Hervé BOUTEMY [mailto:herve.bout...@free.fr]
> Envoyé : mercredi 24 avril 2013 13:23
> À : Maven Developers List
> Objet : CALL TO CONTRIBUTION: dist tooling
>
&g
27;origine-
De : Hervé BOUTEMY [mailto:herve.bout...@free.fr]
Envoyé : mercredi 24 avril 2013 13:23
À : Maven Developers List
Objet : CALL TO CONTRIBUTION: dist tooling
I just did some checks in our distribution area [1] and found a good number
of missing releases In addition to asking committers t
I just did some checks in our distribution area [1] and found a good number of
missing releases
In addition to asking committers to remember our procedure [2] (and ask for
PMC help if necessary) , I just thought it would be good to have a little tool
to check against latest artifact releases: wi
16 matches
Mail list logo