We were discussing how to handle Shale's dependency on Standalone Tiles under this subject line, and I don't think it was ever resolved. Maven's snapshots aren't a good fit for Shale, which needs to depend on a reasonably stable "version" of Standalone Tiles.
In another thread, Craig wrote: > Of course, the other approach to this problem is to do 0.1, 0.2 types of > snapshot releases on the way towards a refactored 1.0. Then, at least, you > can point at a dependency that is likely to be there for a while. What if we... - keep the 'SNAPSHOT' keyword in project.xml/pom.xml and publish Maven snapshots for the general public to use, with no guarantees about older snapshots being kept in the repository. - Occasionally publish a version to the internal repository as as 0.x-dev, which is guaranteed to be kept. This is the one Shale would depend on. To get started, I've published a 0.2-SNAPSHOT (of r371786) to both of the internal Maven repositories. If it works well with Shale, then we could rename it 0.2-dev in the internal m1 repo, and move the build to 0.3-SNAPSHOT. Alternately, we could tag and build it as 0.2, if it seems like a better idea to handle these more like actual releases. That's more work, though. :) Thoughts? -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
