t, depending on
> how the dependency on Spring Boot artifact is declared and which Spring
> Boot artifact it is.
>
> --
> Dennis Lundberg
>
>
> Den lör 11 juli 2020 kl 08:39 skrev Lukáš Satin :
>
> > Hi,
> >
> > Maven Versions Plugin scans whole Maven r
of
them, because they are transitive dependencies of Spring Boot, depending on
how the dependency on Spring Boot artifact is declared and which Spring
Boot artifact it is.
--
Dennis Lundberg
Den lör 11 juli 2020 kl 08:39 skrev Lukáš Satin :
> Hi,
>
> Maven Versions Plugin scans wh
x27;re using it is a little
hard to help more. Also without seeing your pom or settings.xml as
your output shows central and something called snapshots being polled.
John
On Sat, 11 Jul 2020 at 07:39, Lukáš Satin wrote:
>
> Hi,
>
> Maven Versions Plugin scans whole Maven repository.
Hi,
Maven Versions Plugin scans whole Maven repository.
It takes about 1 hour and scans everything from com.google.* and
org.springframework.* plus other packages while they are nowhere in the
pom.xml! There is only org.springbootframework.boot, org.apache.commons,
com.oracle!
I read all
t;
> On Thu 7 Nov 2019 at 23:22, Sean Horan wrote:
>
>> Hi all,
>>
>> I am tasked with ensuring that the Maven build process of a large
>> government/enterprise-class system does not reach out to the Internet. Our
>> Jenkins server's local maven repository
with ensuring that the Maven build process of a large
> > government/enterprise-class system does not reach out to the Internet.
> Our
> > Jenkins server's local maven repository has 10,000 POMs. There are many
> > individual builds that are specific to our product and what we
enkins server's local maven repository has 10,000 POMs. There are many
> individual builds that are specific to our product and what we customize
> for government clients.
>
> I have a lot of devops experience but practically no experience with Maven
> and Java beyond struggli
s the single
> > point of trust. Only this way you can control all incoming (and
> optionally
> > outgoing) traffic.
> >
> > Robert
> > On 8-11-2019 00:22:28, Sean Horan wrote:
> > Hi all,
> >
> > I am tasked with ensuring that the Maven build process o
am tasked with ensuring that the Maven build process of a large
> government/enterprise-class system does not reach out to the Internet. Our
> Jenkins server's local maven repository has 10,000 POMs. There are many
> individual builds that are specific to our product and what we customize
>
enterprise-class system does not reach out to the Internet. Our
Jenkins server's local maven repository has 10,000 POMs. There are many
individual builds that are specific to our product and what we customize
for government clients.
I have a lot of devops experience but practically no experi
l,
>
> I am tasked with ensuring that the Maven build process of a large
> government/enterprise-class system does not reach out to the Internet. Our
> Jenkins server's local maven repository has 10,000 POMs. There are many
> individual builds that are specific to our product and
Hi all,
I am tasked with ensuring that the Maven build process of a large
government/enterprise-class system does not reach out to the Internet. Our
Jenkins server's local maven repository has 10,000 POMs. There are many
individual builds that are specific to our product and what we cust
ideas for the next major version(s) of Maven
itself.
To be able to gain more focus we need to criticize the current
subprojects and decide if it is worth maintaining.
https://maven.apache.org/shared/maven-repository-builder/ describes the
main purpose in one line: Maven shared components.
cts,
> including our ambitious ideas for the next major version(s) of Maven
> itself.
> To be able to gain more focus we need to criticize the current
> subprojects
> and decide if it is worth maintaining.
>
> https://maven.apache.org/shared/maven-repository-builder/ descri
jects,
including our ambitious ideas for the next major version(s) of Maven
itself.
To be able to gain more focus we need to criticize the current
subprojects and decide if it is worth maintaining.
https://maven.apache.org/shared/maven-repository-builder/ describes the
main purpose in one line:
these projects,
including our ambitious ideas for the next major version(s) of Maven
itself.
To be able to gain more focus we need to criticize the current
subprojects and decide if it is worth maintaining.
https://maven.apache.org/shared/maven-repository-builder/ describes the
main purpose in one
cts,
> including our ambitious ideas for the next major version(s) of Maven
> itself.
> To be able to gain more focus we need to criticize the current
> subprojects
> and decide if it is worth maintaining.
>
> https://maven.apache.org/shared/maven-repository-builder/ describes the
n all these projects,
> including our ambitious ideas for the next major version(s) of Maven
> itself.
> To be able to gain more focus we need to criticize the current
> subprojects
> and decide if it is worth maintaining.
>
> https://maven.apache.org/shared/maven-repository-builder/
Maven
itself.
To be able to gain more focus we need to criticize the current subprojects
and decide if it is worth maintaining.
https://maven.apache.org/shared/maven-repository-builder/ describes the
main purpose in one line: Maven shared components. Okay, that's actually
quite bad.
Based
Maven itself.
To be able to gain more focus we need to criticize the current subprojects and
decide if it is worth maintaining.
One of those subprojects is the maven-repository-plugin, last released on
February 22, 2015. It's main purpose: a plugin that can be used to create
bundles of arti
decide if it is worth maintaining.
> >
> > One of those subprojects is the maven-repository-plugin, last released on
> > February 22, 2015. It's main purpose: a plugin that can be used to create
> > bundles of artifacts that can be uploaded to the central repository.
&g
+1
-Original Message-
From: Robert Scholte
Sent: 23 April 2019 20:43
To: d...@maven.apache.org
Cc: users@maven.apache.org
Subject: EXTERNAL: [VOTE] Retire Maven Repository Plugin
Hi,
The Apache Maven project consist of about 100 (sub)projects. Due to the small
number of volunteers and
ding
> our ambitious ideas for the next major version(s) of Maven itself.
> To be able to gain more focus we need to criticize the current subprojects and
> decide if it is worth maintaining.
>
> One of those subprojects is the maven-repository-plugin, last released on
> February
n all these projects, including our
ambitious ideas for the next major version(s) of Maven itself.
To be able to gain more focus we need to criticize the current subprojects and
decide if it is worth maintaining.
One of those subprojects is the maven-repository-plugin, last released on
February 22,
n all these projects, including
> our ambitious ideas for the next major version(s) of Maven itself.
> To be able to gain more focus we need to criticize the current subprojects
> and decide if it is worth maintaining.
>
> One of those subprojects is the maven-repository-plugin, last re
f.
To be able to gain more focus we need to criticize the current subprojects and
decide if it is worth maintaining.
One of those subprojects is the maven-repository-plugin, last released on
February 22, 2015. It's main purpose: a plugin that can be used to create
bundles of artifacts t
Just a quick heads up for those of you interested in targeted artifact and
dependency migration between repositories and repository managers.
I cut a new release for the Maven Repository Provisioner with some new features
and dependency updates and blogged about it on my site..
https
That error message does not look like a Maven error message. Try running your
build with -X and look at the output of the maven-compiler-plugin. If the
class was not found during compilation, I would expect a different error
message from the Java compiler...
> On Oct 5, 2017, at 4:25 AM, Jul
I need to do edit some code in a maven project. Therefore, I need to include
a jar I made. I am not really experienced in using maven, however I tried an
approach I found on StackoverFlow and the web.
First I added the jar to my m2 repository (just selected some terms for the
IDs):
mvn install:in
lementation. So I've
been looking for the technical specification of the Maven Repository
Protocol, but I can't find it anywhere. Is there such document somewhere
out the code?
Thanks in advance.
Cheers,
Hi Bernd ,
Issue was resolved .. its my bad i didnt check that configuration page.
Thanks a lot for your help.
Regards,
Pradeep
--
View this message in context:
http://maven.40175.n5.nabble.com/local-Maven-Repository-jars-are-pointing-as-0-and-1-tp5880704p5881021.html
Sent from the
Hello,
This sounds like you have enabled seperate local repositories per executor in
the Jenkins settings. This is actually a good thing for parallel builds but it
does of course require more storage space.
Look for Repository „Local to Executor“ setting in Jenkins configure. Here is a
screens
Hi All,
I am trying to build a maven project from jenkins server.I am facing an
issue while creating jar in local maven repository .Even i set the path of
Maven repo locaiton in setting.xml as shown in below.
/var/lib/jenkins/maven-repositories
All the maven jars are creating under 0 and 1
Hi All,
I am trying to build a maven project from jenkins server.I am facing an
issue while creating jar in local maven repository .Even i set the path of
Maven repo locaiton in setting.xml as shown in below.
/var/lib/jenkins/maven-repositories
All the maven jars are creating under 0 and 1
://www.sonatype.org/nexus/2016/05/24/sonatype-automated-deployments-with-atlassian-bitbucket-pipelines/
Manfred
Jeff Jensen wrote on 2016-05-13 05:13:
>>
>> I want to offer my library also via a Maven repository - snapshots as well
>> as releases.
>
>
> Use Sonatype's fre
On 13 May 2016 at 22:33, Ron Wheeler wrote:
> Small technical correction on military notation.
>
> Are you sure that you did not mean FUBARed rather than SNAFU?\
This is Maven we are talking about, its definitely SNAFU.
On 13 May 2016 at 22:33, Ron Wheeler wrote:
> Small technical correction on military notation.
>
> Are you sure that you did not mean FUBARed rather than SNAFU?
Small technical correction on military notation.
Are you sure that you did not mean FUBARed rather than SNAFU?
Ron
On 13/05/2016 3:16 AM, Barrie Treloar wrote:
A snapshot repository won't behave how you think it will behave.
I recommend not providing one.
As a developer you want your code bas
>
> I want to offer my library also via a Maven repository - snapshots as well
> as releases.
Use Sonatype's free OSS repo hosting [0]. It also provides the easiest and
fastest path for deploying artifacts into Central.
Essentially:
1. Deploy snapshots and releases to it.
2. Prom
A snapshot repository won't behave how you think it will behave.
I recommend not providing one.
As a developer you want your code base to be in a known configured state.
Having a snapshot repository will mean that Maven will pull in a new
snapshot occasionally (you have some control over when they
Hallo everyone,
today it's about creating your own Maven repository as plain file
structure on a webserver.
My problem: I have a project and Sourceforge (Please no pro and con sf
discussion :P ).
I want to offer my library also via a Maven repository - snapshots as
well as rel
Hi all,
I just thought I let you know that my Maven Repository Provisioner tool
recently got a few updates and is not at version 1.1.1.
It allows you to provision a Maven repository from the filesystem into a repo
manager or one or number of artifacts (specified by GAV coordinates) including
The Apache Maven team is pleased to announce the release of the
Apache Maven Repository Plugin, version 2.4
This plugin is used to create bundles of artifacts that can be uploaded to the
central repository.
http://maven.apache.org/plugins/maven-repository-plugin/
org.apache.maven.plugins
The Maven team is pleased to announce the release of the Maven
Repository Builder shared library, version 1.0
This library is used primarily to assemble Maven repository directory
structures based on the dependencies of a project or set of projects,
and provides the implementation for the
There is no bug here. I was mistaken. I inadvertently neglected to
convert one of the MQ jars to system scope and so it still appeared in
the manifest. System scope jars are NOT included in the manifest which
is the correct behavior.
Sorry for the confusion.
On 07/28/2014 09:43 AM, Steve C
I don't think so. The path that must be provided with system scope is a
feature I very much want. I chose system over provided for this reason.
On 07/28/2014 12:14 PM, Ron Wheeler wrote:
Scope - "provided" might do the job.
On 28/07/2014 12:52 PM, Steve Cohen wrote:
Actually, given my requ
I'm now being told by IBM that they provide OSGI-compliant jars which
may make all this moot.
On 07/28/2014 12:14 PM, Ron Wheeler wrote:
Scope - "provided" might do the job.
On 28/07/2014 12:52 PM, Steve Cohen wrote:
Actually, given my requirements, I think scope system is exactly what
I nee
Scope - "provided" might do the job.
On 28/07/2014 12:52 PM, Steve Cohen wrote:
Actually, given my requirements, I think scope system is exactly what
I need and your blanket statement that I shouldn't use this seems too
rigid.
To review, these are my requirements.
1) Project already built w
Actually, given my requirements, I think scope system is exactly what I
need and your blanket statement that I shouldn't use this seems too rigid.
To review, these are my requirements.
1) Project already built with Maven and don't want to change that. We
want to continue using Maven both with
They won't even talk to me in spite of
>>>> having a support contract if we repackage the jars.
>>>>
>>>>
>>>> On 07/25/2014 12:22 PM, Curtis Rueden wrote:
>>>>
>>>>> Hi Steve,
>>>>>
>>>>>
e jars.
>>>>
>>>>
>>>> On 07/25/2014 12:22 PM, Curtis Rueden wrote:
>>>>
>>>>> Hi Steve,
>>>>>
>>>>> The easiest way to accomplish this would be if k could get these jars
>>>>>> into the nexus
the nexus repository named as IBM named them.
Overriding the default naming scheme of JARs in a Maven repository has
been
requested on this list many times, and the answer is always that the
naming
scheme cannot be overridden. It is a requirement of the Maven
repository
that the name be "artifact
mplish this would be if k could get these jars
into the nexus repository named as IBM named them.
Overriding the default naming scheme of JARs in a Maven repository has
been
requested on this list many times, and the answer is always that the
naming
scheme cannot be overridden. It is a requ
t;>> led to a clean build and deploy process and everyone was happy.
>>>>
>>>> Now we have need of turning on MQ traces. It turns out that IBM
>>>> offers no
>>>> way of doing this unless the jar files are in a single directory named
>>>&
e repackage the jars.
On 07/25/2014 12:22 PM, Curtis Rueden wrote:
Hi Steve,
The easiest way to accomplish this would be if k could get these jars
into the nexus repository named as IBM named them.
Overriding the default naming scheme of JARs in a Maven repository has
been
requested on this list
repackage the jars.
On 07/25/2014 12:22 PM, Curtis Rueden wrote:
Hi Steve,
The easiest way to accomplish this would be if k could get these jars
into the nexus repository named as IBM named them.
Overriding the default naming scheme of JARs in a Maven repository has been
requested on this
Hi Steve,
> The easiest way to accomplish this would be if I could get these jars
> into the nexus repository named as IBM named them.
Overriding the default naming scheme of JARs in a Maven repository has been
requested on this list many times, and the answer is always that the naming
ess into place, is there a recommended
way of handling this so that the maven repository, maven, and ibm are
all
happy?
Thanks,
Steve Cohen
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional
urns out that IBM offers no
way of doing this unless the jar files are in a single directory named
exactly as IBM named them in their release. So we have to repackage the
application so as to accomplish this.
Before I jump into hacking this mess into place, is there a recommended
way of handling
p into hacking this mess into place, is there a recommended
> way of handling this so that the maven repository, maven, and ibm are all
> happy?
>
> Thanks,
> Steve Cohen
>
> -
> To unsubscribe, e-
f turning on MQ traces. It turns out that IBM offers
>> no way of doing this unless the jar files are in a single directory named
>> exactly as IBM named them in their release. So we have to repackage the
>> application so as to accomplish this.
>>
>> Before I jump int
acking this mess into place, is there a recommended
> way of handling this so that the maven repository, maven, and ibm are all
> happy?
>
> Thanks,
> Steve Cohen
>
> -
> To unsubscribe, e-mail: users-unsubs
IBM named them in their release. So we have to
repackage the application so as to accomplish this.
Before I jump into hacking this mess into place, is there a recommended
way of handling this so that the maven repository, maven, and ibm are
all happy?
Thanks,
Steve Cohen
> There isn't any particular reason for moving off of Nexus.
Then don't.
> I want to do an evaluation before we make the decision to go with one or the
> other
Then evaluate. Currently you are conducting a survey, not an evaluation. ;-)
---
That is certainly something that my bosses will look to.
On Tue, Jun 3, 2014 at 5:37 PM, Dan Tran wrote:
> Perhaps Artifactory is cheaper and support repos like NPM?
>
> 100$ per seat for nexus professional is way expensive? :-)
>
> -D
>
>
> On Tue, Jun 3, 2014 at 1:10 PM, Glenn Brown
> wrote:
There isn't any particular reason for moving off of Nexus. We have Nexus
as its the most common repository manager used. I want to do an evaluation
before we make the decision to go with one or the other and whether to get
the paid version or stick to the free version. Archiva, Artifactory, and
Perhaps Artifactory is cheaper and support repos like NPM?
100$ per seat for nexus professional is way expensive? :-)
-D
On Tue, Jun 3, 2014 at 1:10 PM, Glenn Brown wrote:
> My question was what use case was making you think of no longer using
> nexus?
>
>
> On Tue, Jun 3, 2014 at 3:05 PM, Ma
My question was what use case was making you think of no longer using
nexus?
On Tue, Jun 3, 2014 at 3:05 PM, Manfred Moser wrote:
> The majority of developers seem to be using Nexus according to
>
>
> http://zeroturnaround.com/rebellabs/java-tools-and-technologies-landscape-for-2014/
>
> Slides
The majority of developers seem to be using Nexus according to
http://zeroturnaround.com/rebellabs/java-tools-and-technologies-landscape-for-2014/
Slides 2 and 19
manfred
PS: I am part of the Nexus team.. but was not involved in that survey.
Glenn Brown wrote on 03.06.2014 12:22:
> I would n
I would not recommend Archiva. It's intended to be mainly a reference
implementation of the repository and, personally, i find it's UI to be a
bit clunky. Whats moving you off Nexus?
On Tue, Jun 3, 2014 at 1:40 PM, Mehul Sanghvi
wrote:
> Hit the reply button too quickly on the previous one.
>
>
Hit the reply button too quickly on the previous one.
I did not expect a full review and comparison of the systems plus a
migration guide. I was more looking for gotchas that people may have run
into when doing a migration and/or what they took into account when
choosing a system. I will take Dan
Points well taken. No offence taken. :)
On Tue, Jun 3, 2014 at 1:49 PM, Alexander Kriegisch <
alexan...@kriegisch.name> wrote:
> With all due respect: Can you ask in an even more general way? You do not
> expect someone to write a full review and comparison of those systems plus
> migration gui
There are quite a few discussions of this topic, please search
-D
On Tue, Jun 3, 2014 at 10:49 AM, Alexander Kriegisch <
alexan...@kriegisch.name> wrote:
> With all due respect: Can you ask in an even more general way? You do not
> expect someone to write a full review and comparison of thos
With all due respect: Can you ask in an even more general way? You do not
expect someone to write a full review and comparison of those systems plus
migration guide for you, do you? For such general information there are web
search engines and tutorials.
Constructive hint: Maybe if you explain
Currently we are using Nexus OSS version. I am leaning toward Archiva, but
there is also
Artifactory.
What is involved if we were to migrate from Nexus to one of the others ?
Do the repository URLs
change ? Or the layout ?
What do people recommend ? Why ?
cheers,
mehul
--
Mehul
Jason, William,
Thanks for the clarifications. The information will certainly help
in setting
up for the next release cycle.
cheers,
mehul
On Tue, Jun 3, 2014 at 12:29 AM, William Ferguson <
william.fergu...@xandar.com.au> wrote:
> Mehul, this is the wrong pattern to use. It g
Mehul, this is the wrong pattern to use. It goes against the entire Maven
dependency mechanism.
Each GAV (aside from snapsghots) should represent a unique build.
You should be creating new RC GAVs for each release candidate. eg
groupX-artifactX-versionZ.rc1
William
On Tue, Jun 3, 2014 at 12:2
We use SNAPSHOT during development, say 1.1.0-SNAPSHOT. At code freeze, we
branch off from main line to a version specific branch and remove SNAPSHOT
from the version string, so it becomes 1.1.0. Between code freeze and
release we have RC builds. Its at that point that when a newer build of
the
Are you deploying different artifacts with the same version? Release versions
are expected to be immutable and Maven will not try to download a released
artifact again because it's not expected to change. If you are deploying
different artifacts using the same version you are using Maven incorre
We have a Nexus server to which various projects upload artifacts.
The artifacts are uploaded to a release repository, not a snapshot repository.
One project is just a consumer of the artifacts. It does not upload anything.
Even though we have an updated artifact available, the consuming pro
che. Is this correct?
yes.
>
> thanks again,
> Nathan
>
>
>
>
> From:
> Tamás Cservenák
> To:
> Maven Users List ,
> Date:
> 10/06/2013 11:29
> Subject:
> Re: consuming maven repository indexes
>
>
>
> Take a peek here, this is a stan
:
Tamás Cservenák
To:
Maven Users List ,
Date:
10/06/2013 11:29
Subject:
Re: consuming maven repository indexes
Take a peek here, this is a standalone example doing (I guess) exactly
what
you need:
https://github.com/cstamas/maven-indexer-examples/tree/master/indexer-example-01
Note: on nexus
Take a peek here, this is a standalone example doing (I guess) exactly what
you need:
https://github.com/cstamas/maven-indexer-examples/tree/master/indexer-example-01
Note: on nexus end, you probably want to enable "publish indexes" to make
Nx publish those for downstream consumption.
Thanks,
~t~
Have a look at a sample here
http://svn.apache.org/repos/asf/maven/sandbox/trunk/central-indexer-test/src/test/java/org/apache/maven/indexer/test/SearchFromRemoteIndexDownloadTest.java
This sample download the index from central repository and do some search.
HTH
2013/6/10 Nathan Coast :
> Cla
Classification: Public
Hi,
Internally, we have hundreds of individual repositories and we are
interested in reporting upon the contents of these repositories. We can
see nexus has already created the relevant indexes, we would like to use
this data. I understand maven-indexer is used to crea
es yesterday, when the maven version changed from one build
> to another. This was an unknown error of one change that was made to build
> server (and will never be made again).
> In one build the maven version is 3.0.4 and in the next build the maven
> version 3.0-beta-2 was used. Si
build the maven version is 3.0.4 and in the next build the maven version
3.0-beta-2 was used. Since then our build maven repository seems to be broken,
throwing the exception listed below.
How can we fix this?
We tried clearing the repository by:
1) Re-running the project with maven 3.0.4
2
.40175.n5.nabble.com/Maven-Repository-on-my-home-Tomcat-tp5726788.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail
I've resolved the issue by setting the proxy in settings.xml file.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-Repository-initial-setp-error-tp5714848p5715045.html
Sent from the Maven - Users mailing list archive at Nabbl
nVersionResolver.java:149)
at
org.apache.maven.plugin.version.internal.DefaultPluginVersionResolver
.resolve(DefaultPluginVersionResolver.java:97)
Please help me to resolve the error.
Regards,
NNR.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-Repository-initial-setp-er
.DefaultPluginVersionResolver
.resolve(DefaultPluginVersionResolver.java:97)
Please help me to resolve the error.
Regards,
NNR.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-Repository-initial-setp-error-tp5714848.html
Sent from the Maven - Us
This may be helpful
http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html
-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu]
Sent: Wednesday, June 06, 2012 1:02 PM
To: Maven Users List
Subject: Re: How does one mirror a maven repository?
Nexus Pro
Nexus Pro has functionality that would allow you to do mirroring, we have a
bunch of customers doing exactly what you ask.
On Fri, Jun 1, 2012 at 12:53 PM, Phillip Hellewell wrote:
> Hi,
>
> Our company would like to mirror our Maven repository at a remote
> location. Currentl
On Fri, Jun 1, 2012 at 12:47 PM, Lyons, Roy wrote:
> I think that this is what you might be looking for...
>
> http://mojo.codehaus.org/wagon-maven-plugin/merge-maven-repos-mojo.html
>
Sweet, thanks! I'll give it a try. That looks like just what I was
looking for.
Phillip
oking for...
http://mojo.codehaus.org/wagon-maven-plugin/merge-maven-repos-mojo.html
-Original Message-
From: Phillip Hellewell [mailto:ssh...@gmail.com]
Sent: Friday, June 01, 2012 12:48 PM
To: Maven Users List
Subject: Re: How does one mirror a maven repository?
On a related note, is it
> On a related note, is it safe to use both Nexus set up with a proxy
> repository, and to also have rsync routinely updating it?
...snip...
>> Is there any way to accomplish this with Nexus, or do I just need to set
>> up rsync or something?
Nexus has its own mailing lists. Please use them.
Wayn
a maven repository?
On a related note, is it safe to use both Nexus set up with a proxy repository,
and to also have rsync routinely updating it?
Phillip
On Fri, Jun 1, 2012 at 10:53 AM, Phillip Hellewell wrote:
> Hi,
>
> Our company would like to mirror our Maven repository at
On a related note, is it safe to use both Nexus set up with a proxy
repository, and to also have rsync routinely updating it?
Phillip
On Fri, Jun 1, 2012 at 10:53 AM, Phillip Hellewell wrote:
> Hi,
>
> Our company would like to mirror our Maven repository at a remote
> location
On Thu, Apr 5, 2012 at 10:11 AM, NunoM wrote:
> Hello,
>
> Yes. I already spent some time reading the documentation.
>
> And I thought I had understood it well.
>
> I've already added the server tag and necessary permissions that are located
> in the readme.txt on the website.
>
> Which is: http:
org/apache/shiro/shiro-core/1.2.0-SNAPSHOT/
Also, 1.2.0 is available from the central Maven repository which Maven already
knows about:
http://repo1.maven.org/maven2/org/apache/shiro/shiro-core/1.2.0/
HTH
-Jim
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/200
1 - 100 of 523 matches
Mail list logo