On 11 Jul 2011, at 16:43, Markus Joschko wrote: > On Mon, Jul 11, 2011 at 5:35 PM, Stuart McCulloch <[email protected]> wrote: >> >> There are options to alter the computed/public URL: >> http://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-2.3.5/doc/site/deploy-mojo.html >> but nothing that would avoid the local repository check, since all the >> use-cases so far have involved installing/deploying artifacts that already >> exist in the local repository. > > I just wonder how they should get there? When the deploy plugin is not > putting it there, then only the install plugin will put a artifact > there. But that does not use the unique version numbers.
yes, that seems to be the difference between Maven 2 and 3 - with Maven 2 it caches the unique version in the local repository, with Maven 3 it doesn't > I can adopt my configuration to whatever is necessary. My use case is > to get the project compiled and deployed to the obr. > >> Without an example project that recreates the issue it's hard to know a) >> exactly which part of the code to fix/improve and b) whether that change >> truly resolves the original issue - especially since I don't know what your >> POM looks like, what plugin executions it defines, and in what order etc. > > Yep I agree. Wasn't too hard so I created the example project that > reproduces the behaviour (at least for me) thanks, I get the same results locally (because of the missing unique artifact version)
