--- On Thu, 6/16/11, Mike Mills <[email protected]> wrote: I am happy to not use the SNAPSHOT nomenclature and I can confirm that you still get the latest jar from project 1 imported into project 2 when you just use version number (eg 1.0.0). This is exactly how we use it for some old legacy component dependencies where there is little/no control over how they get built and how their artifacts get named and where they get placed. I only included the timestamp and SNAPSHOT pieces, to show that they would work as well, since your earlier messages implied that a timestamp at least was likely to be part of the naming convention. I would suggest the following change for the above: def patterns = [repoPath + '[organisation]-[module](-[revision])(-[classifier]).[ext]']
By adding in the organistation, when you have two multi module project builds both with modules called "core" or "common" then you will still be able to use the localRepo without conflicts in the flat dir ie: project1-core.1.0.jar and project2-core.1.0.jarWe actually have to assign several patterns based upon convention to "catch" all the locations of potential artifact files, many of which do not follow anything close to a maven-style layout convention. So, what I provided was the smallest representative example that hopefully would convey the concept. All of the real patterns that we utilize have at least an optional organization, and since you can define what the convention is for the artifact creation, I agree that including organization/organisation is a generally better solution. Glad you were able to work out a simple solution that meets your needs. -Spencer
