Re: REVERTED MAVEN THIRDPARTY BUILD Re: [jboss-dev] differences between pom.xml / build-thirdparty.xml
As long as you have the right directory structure, you don't have to check out
the whole thing. So if you want to deploy to org/jboss/microcontainer, just
create something like
maven2/org/jboss
Then check out the microcontainer dir to
maven2/org/jboss/microcontainer
Then deploy to
maven2/
I'm certainly open to suggestions for improvement. The central maven repository
(repo1.maven.org) is not backed by svn, so deploying a release is just a matter
of using "mvn deploy". The way the maven repo is now, is just based on the old
repository.
Maybe we should hire an intern to upload all the releases :)
Rémy Maucherat wrote:
On Fri, Mar 14, 2008 at 3:06 PM, Paul Gier <pgier(a)redhat.com>
wrote:
> See inline answers.
>
>
> Thomas Diesler wrote:
> > Hi Paul,
> >
> > do you have documentation on how to publish stuff to the maven
> > repository? The jbossws artifacts need be published properly as well.
> >
>
> There is some information on the wiki here:
> http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenReleaseRepository
> http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenSnapshotRepository
The main problems as far as I am concerned is the need to upload JARs
all over the place, and I certainly don't want to checkout the whole
repository. To me, the previous repository was a lot more manageable.
Could this be improved ? [we could have someone responsible for
signing and uploading stuff, for example]
Rémy
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development