You are viewing a plain text version of this content. The canonical link for it is here.

Posted to scm-dev@maven.apache.org by Wim Deblauwe <wi...@gmail.com> on 2005/11/30 10:09:37 UTC

PrepareReleaseMojo

Hi,

I noticed that to solve the nullpointer that happens in PrepareReleaseMojo,
there are currently 2 solutions:

- mine: initialize pomFiles directely
- other: check if pomFiles is null and then assign new ArrayList() to it.

we should only keep one of these solutions.

regards,

Wim

Re: PrepareReleaseMojo

Posted by Wim Deblauwe <wi...@gmail.com>.

ah, ok, thanks!

2005/11/30, Emmanuel Venisse <em...@venisse.net>:
>
> we have only one solution in code, the second.
>
> If you have those 2 solutions in your file, it's because you modify it
> befire you done an update of
> file and svn merge server content with your modifications.
>
> Run a "svn revert" to cancel your local modifications.
>
> Emmanuel
>
> Wim Deblauwe a écrit :
> > Hi,
> >
> > I noticed that to solve the nullpointer that happens in
> > PrepareReleaseMojo, there are currently 2 solutions:
> >
> > - mine: initialize pomFiles directely
> > - other: check if pomFiles is null and then assign new ArrayList() to
> it.
> >
> > we should only keep one of these solutions.
> >
> > regards,
> >
> > Wim
>
>

Re: PrepareReleaseMojo

Posted by Emmanuel Venisse <em...@venisse.net>.

we have only one solution in code, the second.

If you have those 2 solutions in your file, it's because you modify it befire you done an update of 
file and svn merge server content with your modifications.

Run a "svn revert" to cancel your local modifications.

Emmanuel

Wim Deblauwe a écrit :
> Hi,
> 
> I noticed that to solve the nullpointer that happens in 
> PrepareReleaseMojo, there are currently 2 solutions:
> 
> - mine: initialize pomFiles directely
> - other: check if pomFiles is null and then assign new ArrayList() to it.
> 
> we should only keep one of these solutions.
> 
> regards,
> 
> Wim