My guess is there's a corporate repository set up with snapshots set
to false. So his Maven install did not find the build extension until
it was released. We won't know for sure until he provides more
information.
Wayne
On Mon, Nov 18, 2013 at 1:04 AM, Anders Hammar and...@hammar.net wrote:
That's exactly what it looks like. First extension of maven, and thought
it was behaving differently.
James.
On Nov 18, 2013 9:06 AM, Wayne Fay wayne...@gmail.com wrote:
My guess is there's a corporate repository set up with snapshots set
to false. So his Maven install did not find the build
Hi,
I have a project where I need to temporarily have a maven build extension
(because we're migrating to maven) and did not know if there is any way to
get the maven extension artifact to automatically download. I have seen
that if the artifact is in my local repository that it does not need to
Hi James,
There are some things I don’t understand about your scenario. You say you
“temporarily” have a maven build extension. What does that mean? Are you
currently using ant? And using ant tasks for maven to build the maven portions?
Or now using maven and having it call an old build tool?
Yeah, turns out I just needed to release it. For some reason maven wasn't
downloading the build extension at all when it was a snapshot version.
After making a release maven pulled down the artifact correctly without it
being preloaded in my maven install or local repository.
On Sun, Nov 17,
Strange, you should file a ticket about this. Please provide a simple
project to reproduce the issue.
/Anders (mobile)
Den 18 nov 2013 02:38 skrev James Hutton james.a.hut...@gmail.com:
Yeah, turns out I just needed to release it. For some reason maven wasn't
downloading the build extension
