|null pointer exception when using custom archetype [message #734937]
||Mon, 10 October 2011 09:27
| Madhav Bhargava
Registered: October 2011
We have created a custom maven archetype for creating a custom project structure. We are able to successfully use the archetype from the command line. When we try the same using m2e then it gives a couple of problems:
1. A null pointer exception(NPE) is thrown and we do not get any stack trace.
2. The project gets created in spite of the NPE, however an additional step "Update maven configuration" needs to be done. Is this necessary? Can this be avoided?
3. Since it nature of the project is java eclipse builder is invoked which creates the bin folder which again is not required. When doing from command line this is never created. Is there anyway to avoid this?
We have tried using maven 3.0.3 along with m2e and it still has the same problem. We have also looked at the bug ID 347602 but we have specified the version and the action properly.
Following is our plugin management snippet:
How do we change the log level for this plugin so that we can get a detailed stack trace? Any pointers would be greatly appreciated.
Powered by FUDForum
. Page generated in 0.01786 seconds