Yeah, can't split up the code; 1. A lot of the code in the two artifacts is the same and, 2. This code is an existing project consisting of a enormous ball of mud, and the client will not pay for refactoring. The circular dependencies alone would make any decent programmer run screaming.
I guess it's alright if we have both jars in the war subfolder; we will never reference the main artifact, and it makes the deployment ear bigger for no reason other than maven's idiosyncrasies. Eh. Yeah, sounds like a JIRA ticket is in order. By the time it's addressed, though, I will probably be long done with the project, and no one will ever revisit. :) Thanks for all your help, Wayne. Karma! Tom -----Original Message----- From: Wayne Fay [mailto:[email protected]] Sent: Friday, March 05, 2010 4:13 PM To: Maven Users List Subject: Re: Including sibling module attachment inside another module artifact > It now takes both the main artifact AND the classified attachment. Closer, > but still wrong. So odd. Except in very specific circumstances, I am not a fan of artifacts with classifiers. Reconfigure your project so that you have 2 separate modules and don't use classifier, and I'd assume it will work. But that does seem odd/wrong, so file a JIRA as well. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
