NPE with Maven project with Jenkins 1.445

[Larry Shatzer, Jr.]

After I upgraded this morning to 1.445, when a Maven build runs, I get the following NPE:  http://pastebin.com/V3GjJ9Dt I tried it on both a multi-module project and a single module project.

If I downgrade Jenkins back to 1.444 (along with the Maven plugin), it is fixed.

-- Larry

[Christoph Kutzinski]

Thanks for reporting this!
Could you please create a new JIRA issue with the details, too?

thanks
Christoph

[Tim-Ericsson]

Hi There,

I upgrade jenkins to 1.445 yesterday and met the same problem,
according to my colleague feedback, only build maven 3 project deploy
target will met this type of problem.

In addition to this, I found another tricky issue, all of the build
history console output disappear, and the build number was wrong.

Like Larry, If I change to the version 1.436, everything works well.

Brs,
Tim

On 12月28日, 上午7时15分, Christoph Kutzinski <ku...@gmx.de> wrote:
> Thanks for reporting this!
> Could you please create a new JIRA issue with the details, too?
>
> thanks
> Christoph
>
> Am 27.12.2011 21:53, schrieb Larry Shatzer, Jr.:
>
>
>
>
>
>
>
> > After I upgraded this morning to 1.445, when a Maven build runs, I get

> > the following NPE:http://pastebin.com/V3GjJ9DtI tried it on both a

[Christoph Kutzinski]

I just did a short test with deploying to a local file:// repository,
but couldn't reproduce the issue (Maven 3.0.3 with and without -T option).
Do you have any additional info how to reproduce it - ideally a zip with
simple project that has the problem?
Any non-standard options used o.s.l.t.?

cheers
Christoph

Am 28.12.2011 02:43, schrieb Tim-Ericsson:
> Hi There,
>
> I upgrade jenkins to 1.445 yesterday and met the same problem,
> according to my colleague feedback, only build maven 3 project deploy
> target will met this type of problem.
>
> In addition to this, I found another tricky issue, all of the build
> history console output disappear, and the build number was wrong.
>
> Like Larry, If I change to the version 1.436, everything works well.
>
> Brs,
> Tim

[Olivier Lamy]

Hello,
It looks to happen with mojos which fork lifecycle.
If you use sources jar a workaround is to use source:jar-no-fork
rather than source:jar

BTW as some other errors are skip in case of issues recording
ExecutedMojo.digest, IMHO we are safe to ignore this one too :-).
I'm not really sure this field is used.

2011/12/28 Christoph Kutzinski <ku...@gmx.de>:

> I just did a short test with deploying to a local file:// repository,
> but couldn't reproduce the issue (Maven 3.0.3 with and without -T option).
> Do you have any additional info how to reproduce it - ideally a zip with
> simple project that has the problem?
> Any non-standard options used o.s.l.t.?
>
> cheers
> Christoph
>
> Am 28.12.2011 02:43, schrieb Tim-Ericsson:
>> Hi There,
>>
>> I upgrade jenkins to 1.445 yesterday and met the same problem,
>> according to my colleague feedback, only build maven 3 project deploy
>> target will met this type of problem.
>>
>> In addition to this, I found another tricky issue, all of the build
>> history console output disappear, and the build number was wrong.
>>
>> Like Larry, If I change to the version 1.436, everything works well.
>>
>> Brs,
>> Tim

>> On 12月28日, 上午7时15分, Christoph Kutzinski <ku...@gmx.de> wrote:
>>> Thanks for reporting this!
>>> Could you please create a new JIRA issue with the details, too?
>>>
>>> thanks
>>> Christoph
>>>
>>> Am 27.12.2011 21:53, schrieb Larry Shatzer, Jr.:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>> After I upgraded this morning to 1.445, when a Maven build runs, I get
>>>> the following NPE:http://pastebin.com/V3GjJ9DtI tried it on both a
>>>> multi-module project and a single module project.
>>>> If I downgrade Jenkins back to 1.444 (along with the Maven plugin), it
>>>> is fixed.
>>>> -- Larry
>

--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

[Olivier Lamy]

Hello,
I have fixed that in master.
Could it be released quickly as it breaks a lot of builds ?

2011/12/29 Olivier Lamy <olive...@gmail.com>:

[Christoph Kutzinski]

The question I have, is why this started to show up after Kohsuke's changes?
I didn't see any too obvious reason (but haven't look really closely).
Do you know why?

[Christoph Kutzinski]

+1 for releasing

Additionally, I'm wondering why such critical errors are not caught by
the test-harness

[Arnaud Héritier]

+1 for a quick release 1.445 is unusable

What is strange is that it didn't break all my build thus I discovered the issue only after few hours.

+1000 to try to find why we didn't find this issue with the test harness

2011/12/30 Christoph Kutzinski <ku...@gmx.de>

>>>> On 12月28日, 上午7时15分, Christoph Kutzinski<ku...@gmx.de>  wrote:

[Richard Mortimer]

+1 I just tested the fix and my builds are now succeeding.

[Yves Schumann]

Hi

Any news on this? There seems to be no filed Jira issue for this
problem. So when will it be fixed? We still have this problem on 1.446.

+1 to release it

Kind regards,
Yves

[Maven User]

Looks like the fix is coming in 1.447:

https://issues.jenkins-ci.org/browse/JENKINS-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#issue-tabs

(a coworker just pointed this out to me)

[Maven User]

I just apt-get'd upgraded to 1.447 and it's gone!

THANK YOU JENKINS COMMUNITY!

On Jan 9, 4:00 pm, Maven User <maven.2.u...@gmail.com> wrote:
> Looks like the fix is coming in 1.447:
>

> https://issues.jenkins-ci.org/browse/JENKINS-12259?page=com.atlassian...