10:29 p.m.
Hi Everyone,
This is a reminder that the new Maven repository will be available April 12. We
will be disabling write access to the svn repository 20 UTC April 9. This means
that you will not be able to do any releases to the repository the weekend of
April 9.
I put together a small FAQ [1] with information about the new repository.
Please take a look if you have questions.
Also, if your project uses a groupId other than org.jboss, please take a look at
the JBoss groupId page [2] and make sure yours is included. Otherwise you will
not be able to deploy to the new repository.
[1]http://community.jboss.org/wiki/MavenRepository-FAQ
[2]http://community.jboss.org/wiki/MavenJBossGroupIds
10:24 a.m.
On 2 avr. 2010, at 22:29, Paul Gier wrote:
Do artifacts from the central Maven repository or other thirdparty repositories still need
to be added manually to the repository?
No, artifacts from the central Maven repository and other thirdparty repositories will be
automatically saved by Nexus as long as they are retrieved through the URL of the
repository group.
Does that mean that any random repository (such as svn hosted ones per projects like many
google-code hosted projects do) will be magically picked up? How does that work?
10:14 p.m.
Emmanuel Bernard wrote:
On 2 avr. 2010, at 22:29, Paul Gier wrote:
> http://community.jboss.org/wiki/MavenRepository-FAQ
Do artifacts from the central Maven repository or other thirdparty repositories still
need to be added manually to the repository?
No, artifacts from the central Maven repository and other thirdparty repositories will be
automatically saved by Nexus as long as they are retrieved through the URL of the
repository group.
Does that mean that any random repository (such as svn hosted ones per projects like
many google-code hosted projects do) will be magically picked up? How does that work?
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
We will have a repository group in Nexus that will proxy from a pre-defined set
of repositories [1]. So it won't be able to pull in from unknown repos. If you
want to automatically proxy from a repository that is not currently in the list,
just create a jira issue in JBBUILD, and we can discuss whether to add it as
another proxied repo, or manually uploaded the artifacts that are needed.
[1]http://community.jboss.org/wiki/MavenRepositoryNexusConfiguration
1:36 a.m.
Unfortunately, due to some problems found during our final testing we have to
push back the release of the new repository by 1 week. So the new release date
will be Monday April 19.
Paul Gier wrote:
Hi Everyone,
This is a reminder that the new Maven repository will be available April 12. We
will be disabling write access to the svn repository 20 UTC April 9. This means
that you will not be able to do any releases to the repository the weekend of
April 9.
I put together a small FAQ [1] with information about the new repository.
Please take a look if you have questions.
Also, if your project uses a groupId other than org.jboss, please take a look at
the JBoss groupId page [2] and make sure yours is included. Otherwise you will
not be able to deploy to the new repository.
[1]http://community.jboss.org/wiki/MavenRepository-FAQ
[2]http://community.jboss.org/wiki/MavenJBossGroupIds
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
5140
days inactive
5145
days old
jboss-development@lists.jboss.org
3 comments
2 participants
participants (2)
-
Emmanuel Bernard -
Paul Gier