I went back to using the ‘mystery’ jar we had which added the KVC support compiled in. I won’t get the maven-y benefits like downloading sources/javadocs on that one, but that will just encourage me to find a better replacement :D This is still useful as I’m testing deployment on my maven builds. Now that you mention it, I'll need to check that the Joda stuff is working properly. Thanks for the tip Fabian.
On Mar 24, 2016, at 11:56 PM, Fabian Peters <[email protected]> wrote: > Hi Ramsey, > > I don't know about excluding a single class from a jar, but I've had problems > with JavaEOAccess getting on the classpath before ERAttributeExtensions. To > avoid that I've used the following: > > <dependency> > <groupId>wonder.core</groupId> > <artifactId>ERExtensions</artifactId> > <exclusions> > <exclusion> > <!-- make sure JavaEOAccess loads after > ERAttributeExtensions --> > <groupId>com.webobjects</groupId> > <artifactId>JavaEOAccess</artifactId> > </exclusion> > </exclusions> > </dependency> > <dependency> > <groupId>wonder.eof</groupId> > <artifactId>ERAttributeExtension</artifactId> > </dependency> > > Maybe that can help? > > Fabian > >> Am 25.03.2016 um 01:53 schrieb Ramsey Gurley <[email protected]>: >> >> Hi all, >> >> I have a small problem with classpath ordering in Maven and I’m hoping >> someone can explain how it works. >> >> In the log of my app, I see the java.class.path. It starts with lots of >> dependent jars and mostly ends with In house frameworks, Wonder then >> WebObjects frameworks. Unfortunately, one of the jars (StringTemplate) >> contains a class (ASTExpr) I need to override in order to make it happy with >> KeyValueCoding style getter naming. It’s a simple fix, and everything works >> properly in Eclipse as well as with our old Ant builds. But if I include >> this ASTExpr in my framework, the original shows up first in the classpath >> for the maven build, and thus, the class I intended to use as an override is >> overridden. >> >> I relocated my StringTemplate dependency to the bottom of my pom file, but >> that made no difference in classpath ordering. Is there any secret way to >> force that jar down the list, or perhaps remove the original ASTExpr class >> from it? >> >> Thanks, >> >> Ramsey >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com >> >> This email sent to [email protected] > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
