I was thinking of new projects, but the log4j example works.
If you do not rename the packages, Maven might cleverly mix new classes from your log4j in with classes from the original log4j in some hapless artifact that depends on both. This could cause bugs of nightmarish difficulty to track.
Stephen Connolly wrote:
No. e.g. (I own one-dash.com) I might roll a custom version of log4j... I would deploy this as groupId=com.one-dash artifactId=log4j version=1.2.14 Why should I have to change the package names? 2009/3/20 Merv Green <[email protected]>Is it reasonable to insist that a project's Java package name matches ${project.groupId}.${project.artifactId}, with dashes converted to underscores, etc? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
