Hi,
The Mojo team is pleased to announce the release of the
flatten-maven-plugin version 1.0.0-beta-2.
Flatten Maven Plugin generates a flattened version of your pom.xml and
makes maven to install
and deploy this one instead of the original pom.xml.
http://mojo.codehaus.org/flatten-maven-pl
It's possible, of course.
The problem is that some dependencies from atlassian-public will have
dependencies in other proxied repositories (not necessarily central). So
you might ending up trying to find the original repositories, and adding
all of them in your settings.xml.
Doable, of course.
Still not exaclty what you asked, but I would avoid using any repository
that proxy maven central.
It's bettter to use directly
https://maven.atlassian.com/content/repositories/atlassian-public/ , and
maybe https://maven.atlassian.com/content/repositories/atlassian-3rdparty/
and https://maven.atla
AFAICT, Central will always be used unless overridden by another repo with
the same ID, or defining a mirror.
Profiles add up to the default configuration, they don't replace.
Le 6 juin 2014 10:13, "Steinar Bang" a écrit :
> If I add the atlassian repos (the SDK local disk repo and the
> https:/
It's not exactly what you asked, but atlassian-public (
https://maven.atlassian.com/content/groups/public/) should already proxy
central (with just a few exceptions if it conflicts with what we are
already hosting).
I just use in the profile:
true
On 6
If I add the atlassian repos (the SDK local disk repo and the
https://maven.atlassian.com/repository/public repo to the settings.xml,
will maven still fetch dependencies from maven central?
I have tried googling for the behaviour here, and I have tried running
mvn help:active-profiles
without be
