> Depenedencies have a "type" attribute in the POM, but I don't think that > it is used at the moment... ideally plugins could set up a separate > classpath when, for example, type == 'test' || type == null. Builds > could use type == 'compile' || type == null. > > I'm not sure - what else is type used for at the moment? I noticed it > renaming JARs sometimes, so I took it out...
AFAIK, the type attribute determines the name of the subdirectory in the remote repo (with an 's' appended) where the artifact is stored. So a jar dependency, the default type, is obtained from the jars subdir. A pom dependency is obtained from the poms subdir, etc. Also, the type is used as the default extension of the artifact. Maven verifies and downloads all dependency types, but jars are treated special because they are added to the maven.dependency.classpath. Conversely, you pass the type attribute, with the 's' appended, to the deploy:artifact tag to specify the subdir on the central repo to deploy to. -------------------------------------- David Zeleznik ILOG - Changing the rules of business mailto:[EMAIL PROTECTED] http://www.ilog.com -------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
