Re: Maven classpath ordering
Re: Maven classpath ordering
- Subject: Re: Maven classpath ordering
- From: T Worman <email@hidden>
- Date: Thu, 07 Apr 2016 10:46:26 -0700
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/webobjects-dev/2015/Oct/msg00049.html
Please excuse the hijacking of a maven topic.
Tim
> On Mar 28, 2016, at 3:44 PM, Lachlan Deck <email@hidden> wrote:
>
> 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 your child poms (same deal if you only have one pom), their dependencies reference what’s in your dependency management section and inherit their ordering, versioning, scopes, etc.
>
> <dependencyManagement>
> <dependencies>
> <dependency>
> <artifactId>foo</artifactId>
> <groupId>bar</groupId>
> <version>1.0</version>
> ...
> </dependency>
> </dependencies>
> </dependencyManagement>
>
> <dependencies>
> <dependency>
> <artifactId>foo</artifactId>
> <groupId>bar</groupId>
> </dependency>
> </dependencies>
>
>> On 25 Mar 2016, at 11:53 AM, Ramsey Gurley <email@hidden> wrote:
>>
>> 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@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden