Maybe in this case it's better to use -DincludeTypes ?

On Sat, May 10, 2014 at 4:38 AM, Lalonde, Michael <Michael_Lalonde@cable.comcast.com> wrote:
Hello Everyone, I have been using db-javap for awhile without issue. Recently I had to takeover a project with nearly 100 (shaking head) pom type maven dependencies.  Maven dependencies with type pom causes semanticdb-javap-classpath-objects to spit out 100’s of classpath not found messages.  This amount of messaging causes the editor to lock for an uncomfortable period of time.

The maven target dependency:build-classpath accepts a flag -DexcludeTypes=… but it has to come after command flags and the target as it is a jvm flag to pass to the maven plugins. The attached patch to maven2.el adds a customization variable for mavens plugins (essentially the arguments after the target) to ignore pom types and all is working well. But I imagine the same could happen with war,ear and the other non jar type projects.

Before i start making a bigger mess out of my maven2.el file, due to my horrible elisp skills, I can't get the customization to take place at runtime if i set the added ede-maven2-plugin-options to anything else. I am looking for advice or suggestions on a better direction to handle customizing mavens plugins.


Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
Cedet-devel mailing list

With best wishes,                    Alex Ott
Twitter: alexott_en (English), alexott (Russian)
Skype: alex.ott