On another topic, I went with Mustache of StringTemplate specifically because
of the KVC/getter issue. I shoulda probably dug deeper to override its behavior
but I got lazy. :-) I’d love to see what you did there. Anyway, here was my
original thread:
http://prod.lists.apple.com/archives/webobje
You’ll want to use maven’s dependency management section. If you don’t supply
one you’re inheriting it from somewhere. It provides for better control of the
ordering and so forth of the dependencies you want.
The idea is that in your parent pom, you use a dependency management section.
Then in
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
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:
wonder.core
ERExtensions
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,
