Yes, that would definitely be a problem. However, i'm not sure why it happens. The mvn url handler is configured with system as a default repository which should override any other repository, including the default m2 local repository (and obviously any remote repository). I did that a while ago to solve this exact problem.
On Wed, Apr 20, 2011 at 18:50, David Jencks <[email protected]> wrote: > I discovered that features can pull in snapshots from the apache snapshot > repo rather than the ones you carefully installed into system if someone does > a deploy of a snapshot between when you assembled the server and started it. > > I found this behavior very disconcerting and I'm not sure it's what we want. > > One way to change this and also fix the "we're copying all the bundles into > the framework" problem might be to examine each feature bundle and if its in > system use a reference: url instead of the supplied mvn url. > > The situation in more detail: > > build a snapshot bundle X locally with local modifications. > assemble a server X in the system repo and a feature using X in boot features. > > Someone else deploys a different X snapshot to say apache snapshot repo > > Start the server you assembled..... the feature starts and pax-url-aether > fetches the X from apache snapshot repo instead of the one in system. > > thoughts? > > thanks > david jencks -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com Connect at CamelOne May 24-26 The Open Source Integration Conference http://camelone.com/
