On Thu, Aug 11, 2011 at 5:22 AM, Daivish Shah [via Maven] <
ml-node+4687779-706532986-220...@n5.nabble.com> wrote:
> You have to create Profile for that..
>
> If you will put following entry in your settings.xml file it will first
> look
> at the remote repository and then it will look for your lo
Wayne Fay,
The other idea was having Mirror tag point to remote repo. :)
But configuring another repo made the trick.
Thanks for the Help
-Goutham
On Thu, Aug 11, 2011 at 12:41 AM, Wayne Fay [via Maven] <
ml-node+4686902-1392576678-220...@n5.nabble.com> wrote:
> > Can this be the other way ?
>
hey Barrie
I dint read completely the suggested sources. I am in short of time so read
few which help in picking up artifact's from repository.
Yes i agree with your statement of checking remote repo only is bad idea , i
missed the point "Any released artifact NEVER changes" .
Thanks for the hel
You have to create Profile for that..
If you will put following entry in your settings.xml file it will first look
at the remote repository and then it will look for your local repository.
Basically you need to create
Repository Proxy
true
On Thu, Aug 11, 2011 at 12:06 AM, goutham wrote:
> I want it to restrict to the remote repo only. It should not look into local
> repo , at least first it have to look in remote and then go for local
>
> On Wed, Aug 10, 2011 at 6:02 PM, Anders Hammar [via Maven] <
> ml-node+4685646-210393254-220..
> Can this be the other way ?
What is "the other way"?
> central
>
> also trying to download the other dependencies(ex:
> plexus-interactivity-api) form the same repo which dont exist.
Saying a repo is a "mirror of Central" means that all artifacts which
do exist in Central must also exist
Hey
Can this be the other way ?
I used the mirror tags in settings.xml to point to my nexus repository.
my-repo-releases
Releases
http://mavenrepo.releases
central
This thing actually worked in invoking the plugin from remote repo but it is
also trying t
> I want it to restrict to the remote repo only. It should not look into local
> repo , at least first it have to look in remote and then go for local
Maven always tries to use the local repo first when resolving things.
So if you want to use version 1.2.3 of a plugin, and it is available
locally,
I want it to restrict to the remote repo only. It should not look into local
repo , at least first it have to look in remote and then go for local
On Wed, Aug 10, 2011 at 6:02 PM, Anders Hammar [via Maven] <
ml-node+4685646-210393254-220...@n5.nabble.com> wrote:
> Short answer: it's the same comm
Short answer: it's the same command
somewhat longer answer: Maven will first look in your local repo. If not
found there, it will look in the configured remote repos (and download to
your local repo if found).
Maybe reading some of the first chapters in some Maven book will give you a
better idea
10 matches
Mail list logo
