On 02/06/2013 01:39 PM, Jesse Glick wrote:
I could file a JIRA ticket for it
https://jira.codehaus.org/browse/MNG-5437
Hello Jesse
Le 20/02/13 16:20, Jesse Glick a écrit :
On 02/06/2013 01:39 PM, Jesse Glick wrote:
I could file a JIRA ticket for it
https://jira.codehaus.org/browse/MNG-5437
Thanks a lot for writing this JIRA task. However it may be worth to
emphases that clobbering an open JAR file is an hyp
On 02/20/2013 11:46 AM, Martin Desruisseaux wrote:
clobbering an open JAR file is an hypothesis that may explain the JVM crash,
but this is unverified.
Indeed it is only a hypothesis, though one based on repeated encounters with similar crashes over the course of years of development that were
Le 20/02/13 18:12, Jesse Glick a écrit :
I would merely claim that loading classes from a snapshot JAR is
_prone_ to triggering crashes when other factors come into play which
might be difficult to predict.
I agree. We will move to a non-snapshot version when we can. The only
issue is that we n
Hi there,
Is it possible to have build failure (and back to normal) emails from
builds.a.o go to a different list from build success emails?
The CloudStack project's build send all emails to
cloudstack-commits@i.a.o, but we'd like to have failures and back to
normal emails sent to cloudstack-dev@
In Post build actions, you can add "Editable Email Notification".
Then advanced option. Then "add a trigger". For each trigger you can
configure recipient list.
See https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin .
2013/2/20 Chip Childers :
> Hi there,
>
> Is it possible to have build
