Confirmed, thank you for the fix! Eagerly awaiting the release.
On Mar 27, 2014, at 1:16 PM, Mirko Friedenhagen wrote:
> Steven,
>
> thanks, I now could reproduce this. Installing a local SNAPSHOT of the
> shared library and plugin did resolve this.
> So I guess we have to release both pretty
Basically, with a literate job type (when I get this implemented) you will
be able to define upstream jobs and branch matching rules. The products of
the upstream job will be available as an effective repo injected into the
settings used by the downstream, so when you cut a release the downstream
j
I don't have the time to explain how I want to add maven support to the
literate job type
On Saturday, 29 March 2014, Hervé BOUTEMY wrote:
> I don't understand how pipelines will change anything to the staging issue
>
> Regards,
>
> Hervé
>
> Le vendredi 28 mars 2014 14:53:56 Mirko Friedenhagen
I don't understand how pipelines will change anything to the staging issue
Regards,
Hervé
Le vendredi 28 mars 2014 14:53:56 Mirko Friedenhagen a écrit :
> Hello Stephen,
>
> I am a big fan of pipelines here:
>
> 1. clean test-compile
> 2. clean verify of modules with changes or excluding fails
Hello Stephen,
I am a big fan of pipelines here:
1. clean test-compile
2. clean verify of modules with changes or excluding failsafe/invoker
3. clean verify of all modules with inclusion of invoker tests.
Regards
Mirko
--
Sent from my mobile
On Mar 28, 2014 1:02 PM, "Stephen Connolly"
wrote:
I would rather get some good pipelining going so that we have a better
quality of jobs in the first place, e.g. see the job pipeline I have set up
https://builds.apache.org/job/maven-3.2-release-status/
I want to add other tests into this pipeline and once we have a strong
template for a good pipe
Well, the Windows IT build [1] has failed constantly for over a month. :-(
/Anders
[1] https://builds.apache.org/view/M-R/view/Maven/job/core-it-maven-3-win/
On Fri, Mar 28, 2014 at 12:32 PM, Mirko Friedenhagen <
mfriedenha...@gmail.com> wrote:
> Hello,
>
> as a fresh subscriber to notificatio
Hello,
as a fresh subscriber to notifications I really wonder how often the jobs
have failed in the last two weeks.
- One reason seems to be, that during staging of plugins and especially
shared components the jobs are failing because of staged dependencies are
not available in central. I propose
I have updated quite a few places to asm 4.x compliance (and hence 5.x). Do
let me know if I missed something, I can do the rest.
(The api changes are fairly significant so I'm assuming I can do further
upgrades about twice as fast as someone who hasn't done it...)
K
2014-03-28 8:11 GMT+01:00
why didn't we detect the failure when building the plugin and running ITs with
JDK 8 = somthing we did a long time ago and that I was conviced would give us
more accurate results than what we finally have?
I had a quick look at ITs, and it seems that the compiler plugin is configured
to generat
I have updated dependency (maven shade) to use asm 5.0.1, and I hope to get
version 0.8 of dependency released RealSoon (tm).
Kristian
2014-03-27 21:16 GMT+01:00 Mirko Friedenhagen :
> Steven,
>
> thanks, I now could reproduce this. Installing a local SNAPSHOT of the
> shared library and plugin
Steven,
thanks, I now could reproduce this. Installing a local SNAPSHOT of the
shared library and plugin did resolve this.
So I guess we have to release both pretty soon :-).
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenh
12 matches
Mail list logo
