Update to use Maven Annotations - #15
Conversation
Upgrade to using java 5 annotations for maven as it is much cleaner. Update assembly plugin minor cleanup on formatting to be in sync.
maven-plugin-api to 3.2.5 maven-plugin-descriptor to 2.2.1 maven-assembly-plugin to 2.5.3 maven-surefire-plugin to 2.18.1 junit to 4.12
There was a problem hiding this comment.
This isn't needed anymore
There was a problem hiding this comment.
Not real clear here on what isn't necessary now. Method is called throughout code. Do you mean the cast to artifact? I think that is what you mean but not completely sure.
|
Looks good, few minor issues and I'm good :) Nice work! |
Remove unnecessary artifact cast and use spacing similar to area of code for runtimebits.
|
Let's rock! |
Update to use Maven Annotations
|
Because of the |
|
Very strange. I do not believe I have seen that one before as an issue. Have you tried deleting that item from your local .m2/repository and trying again? If that doesn't end up helping that plugin is 100% safe to delete. All it does more or less is remove other warnings about life cycle issues which in turn can be modified to ignore anyways in eclipse. --- Original Message --- From: "Lukasz Lenart" notifications@github.com Because of the Reply to this email directly or view it on GitHub: |
|
try |
|
This can be ignored but if you want to delve farther, I found this http://stackoverflow.com/questions/7905501/get-rid-of-pom-not-found-warning-for-org-eclipse-m2elifecycle-mapping |
|
Thanks! Moved the plugin into a profile |
No description provided.