Kenney Westerhof wrote: > > > Patrick Schneider wrote: >> For now, I'm a fan of disallowing snapshots when they are not >> explicitly in >> the boundary, as per the patch. >> >> In my mind, the problem with a profile flag is that it's an >> all-or-nothing >> proposition. Any released artifacts with version ranges will also >> start to >> pull in snapshots. There wouldn't be enough control, IMO. >> > > You can always exclude snapshots explicitly: > > [1.0,1.1-SNAPSHOT),(1.1-SNAPSHOT,1.1] > > Snapshots are valid versions in a range [1.0, 1.1], or even [1.0, 1.1). > > Personally I'm +1 for updating the docs, and let the presence of > snapshot repo's > and valid snapshot artifacts there determine wheter snapshots are used > or not.
Not only is the syntax above very cumbersome, but what about the possibility of 1.0.1-SNAPSHOT, etc? Controlling this through snapshot repo presence/absence would be rather suboptimal, because you couldn't pull in a snapshot for one particular artifact without possibly getting unwanted snapshots for other dependency artifacts published in the same repo. Max.
signature.asc
Description: OpenPGP digital signature
