[m2e-users] Eclipse Mars problems with Maven Classpath

I'm running Eclipse Mars on Windows 7 and converting a bunch of old projects over to Maven/m2e. I've run into a problem with one of these projects. I put 14 dependencies in the POM. The POM editor shows these dependencies as resolved. They don't show up in the Maven Dependencies container and I get

Re: [m2e-users] Eclipse Mars problems with Maven Classpath

Sony, I did Maven->Update Project. I did an Eclipse refresh. I tried deleting and then re-importing the project nothing worked. Dagan: I didn't try a command-line execution. I seem to have resolved the problem now by deleting all of the dependencies from the POM and adding them one-by-one. This ti

Re: [m2e-users] Eclipse Mars problems with Maven Classpath

The problem is that it was recognizing some of the dependencies abut not others. There were 14 total dependencies and five of them were ok; the remaining 9 weren't. As noted above, I did try deleting from my workspace and reimporting as a Maven project with no luck.

[m2e-users] M2e not recognizing custom build lifecycle

I have a Maven plugin that provides a custom lifecycle for a custom packaging type. This works fine when run outside of Eclipse, or even using Run As->Maven install. Doing an Eclipse build fails with: Plugin execution not covered by lifecycle configuration: argle:bargle:1.0.0:version-info (executi

Re: [m2e-users] M2e not recognizing custom build lifecycle

Thanks! That worked. On Sun, Jan 24, 2016 at 9:44 AM, Anton Tanasenko wrote: > Hi, > You can make your maven plugin compatible by following this topic: > https://www.eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html > > > 2016-01-24 16:18 GMT+02:00 Art Kaufma

[m2e-users] Problem with m2e and maven-jaxb2-plugin

I have a project that uses the maven-jaxb2-plugin. When the project is built during an Eclipse build, the plugin runs, but it ignores some (but not all) of the configuration parameters. In particular, I have some custom bindings and a binding plugin. I can tell that this is running, but the binding

Re: [m2e-users] EAR Deployment Assembly structure not same as actually deployed to server

In the "Servers" view I remove the application from the server, then Publish (I have things set to manually publish); then add it back and publish again. In fact, I was doing that very thing when I saw your first e-mail. Cheers, Art Art Kaufmann Chief Architect, IRIS (Traceability Se

Re: [m2e-users] EAR Deployment Assembly structure not same as actually deployed to server

I've experienced the same thing publishing from Eclipse Mars with the WAS 8.5 tooling. I, too, suspect the tooling. Some of the time, when I add a Module or Utility JAR to the application, I have to delete and reinstall it. Cheers, Art Art Kaufmann Chief Architect, IRIS (Traceability S

Re: [m2e-users] EAR Deployment Assembly structure not same as actually deployed to server

Roberto, I'm using artifacts on the server (in the workspace won't work for some things, like security) and am having the same sort of issue. Art Kaufmann Chief Architect, IRIS (Traceability Server) "The life so short, the craft so long to learn" "By hammer and hand d

Re: [m2e-users] Error with jaxws-maven-plugin in Mars

r WSDL and make sure that they are consistent with the standards. Art Kaufmann Chief Architect, IRIS (Traceability Server) "The life so short, the craft so long to learn" "By hammer and hand do all things stand" 3960 Fabian Way Palo Alto, CA 94303 art.kaufm...@frequentz.com www.fre

Re: [m2e-users] Error with jaxws-maven-plugin in Mars

uld be the JRE you're using to run Eclipse. Art Kaufmann Chief Architect, IRIS (Traceability Server) "The life so short, the craft so long to learn" "By hammer and hand do all things stand" 3960 Fabian Way Palo Alto, CA 94303 art.kaufm...@frequentz.com www.frequentz.com

Re: [m2e-users] Risks of setting output folders to "target" for maven projects?

We're using "target" as the output both with Eclipse builds and with straight Maven builds and haven't encountered any significant problems with that. If we do the command line build we may have to refresh the projects in Eclipse so that it knows about the files, but that'