Install local Nexus in you machine and add work Nexus as proxy
repository in it and then only one setting.xml works.
It also gives you freedom to work totally offline.
Cheers,
Markku
On 09/24/2013 03:31 AM, Jamie Archibald wrote:
I typically work behind a Nexus server at work which I use a
That seems like overkill. The whole point to a local maven repository is to
provide caching so you don't have to continually redownload load artifacts.
Also, installing a nexus repo on my machine seems counterproductive from
the maven way which includes portable builds.
Unless I'm completely
I think that he was suggesting that you install it as a proxy so that it
would not contain any actual artifacts.
In the office, it would proxy your real Nexus and when you are off-line
it would act as local repo that would not actually resolve anything but
would keep your settings.xml happy. It
Ah ok makes sense. While this would work, it still doesn't explain why
maven is trying to redownload an artifact that is already in my local repo.
I'm reading the maven definitive guide and it hasnt explained much about
how maven resolves dependencies on the wire. However haven't reached the
Maven keeps track of the source of the artifacts that it downloads.
When you swap out your settings.xml, then the source changes from your
corporate proxy to maven central.
Thus Maven expects that the artifacts in the cache may no longer even exist
or may be different.
Maven therefore tries to
Ok this makes perfect sense now.
Thanks for the help.
Jamie
On Tuesday, September 24, 2013, Stephen Connolly wrote:
Maven keeps track of the source of the artifacts that it downloads.
When you swap out your settings.xml, then the source changes from your
corporate proxy to maven central.
Is it possible with the m-release-p to release a multi module project where
each submodule has a different version?
The releaseVersion property applies to all modules equally. Moreover,
since i have over 300 poms, i can't use the interactive mode that asks for
each module.
I know I can use a
if they have the correct versions
mvn release:prepare release:perform -B
if you want to check what will happen first
mvn release:prepare -B -DdryRun=true
On 24 September 2013 16:17, alejandro.e...@miranda.com wrote:
Is it possible with the m-release-p to release a multi module project
Could someone help me tweak my checkstyle plugin in my pom?
I would like `mvn checkstyle:check` to output the checkstyle results
directly to the console, but setting consoleOutputtrue/consoleOutput
has no effect; it all goes to target/checkstyle-results.xml.
