Martijn,

Please investigate it if you have time.
I was going to remove m2e lifecycle-mappings plugin completely as suggested
by Garret in JIRA. It seems it doesn't actually help and the "Ignore error
type" solutions seems to work better.

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Mon, Sep 22, 2014 at 1:13 AM, Martijn Dashorst <
[email protected]> wrote:

> I got the NPE as well.
>
> Are the repeated lifecycle mappings necessary for each individual
> project? Why not define the plugin in the parent and have it drip down
> to lower modules?
>
> Martijn
>
>
>
> On Sat, Sep 20, 2014 at 7:30 PM, Garret Wilson <[email protected]>
> wrote:
> > I'm exhausted. Try as I might, I can't get Wicket to build on Eclipse
> 4.4.1
> > M20140903-1600.
> >
> > I think I'm past WICKET-5649
> > <https://issues.apache.org/jira/browse/WICKET-5649>, thanks to a tip
> from
> > Andrew Geery.
> >
> > Now I'm running into various NullPointerExceptions. This may be the same
> as
> > reported on StackOverflow <http://stackoverflow.com/q/19522897/421049>,
> but
> > even after deleting all the .settings directories and .project files and
> > importing anew, I still get them.
> >
> > Maybe it's Eclipse Bug 371618
> > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=371618>. I don't know.
> >
> > Is this working for anyone using Eclipse?
> >
> > Garret
> >
> > P.S. I've (gasp) downloaded NetBeans as a last attempt just to debug the
> > character encoding issue I reported on [email protected].
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
>

Reply via email to