|Re: How to display command line of an application that does not start? [message #987075 is a reply to message #986991]
||Fri, 23 November 2012 05:13
| Holger Brands
Registered: September 2012
Hm, I'm puzzled.|
After playing with excluding and including Maven dependencies,
it started working again. I can't say exactly what has changed, to make it work again.
Anyway, I now had a look at the command line of the AspectJ load-time Weaving App and it's currently 31820 characters long, so it's huge.
I noticed that there are many, many JAR dependencies in the aj classpath (-Daj.class.path), a lot of them not in the current Maven classpath container.
I wonder, how the aj.class.path is constructed?
Another observation is, that the source tab in the launch configuration of the AspectJ load-time Weaving App also shows a lot more dependencies than the regular Maven classpath container.
How are the entries in the source lookup path constructed?
I have the feeling, that both the aj classpath and the source lookup path contain Maven dependencies that are located in a Maven profile, that is not active, e.g. those dependencies should not be included in my opinion.
We activate/deactive this profile via the Eclipse Maven project properties "Maven|Active Maven Profiles". After changing the profiles this way, we do an update project configuration.
Perhaps there is a problem dealing with Maven profiles?
Powered by FUDForum
. Page generated in 0.08746 seconds