I've got a pile of test data in a .tar.gz. I don't want to unpack it; my code is perfectly happy to open it as-is and read it.
So, I see that I can list it as a dependency with a silly scope (like the use of 'scope=tomcat' in the tomcat-maven-program) and thus force it to download without ending up in classpath, and then I can construct a pathname starting with the macro for the local repository. Two questions: 1) In maven3, is there an extension mechanism I can use to create a scope to avoid the warnings? If so, I can also apply this to the tomcat plugin. 2) Am I missing some existing feature to neaten this up? If not, I'm prone to make a plugin which is configured with GAVCT spec and which sets a property to the local repo pathname, just to make it look prettier. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
