We 'll wait with pushing Spring-richclient to Ibiblio till
http://jira.codehaus.org/browse/MREPOSITORY-3
is fixed. (Anyone else is free to push it up there though)
With kind regards,
Geoffrey De Smet
Geoffrey De Smet wrote:
We 'd like to get spring-richclient 0.2.1 (build with m2) on the central
repo.
We have it deployed in our repo:
http://spring-rich-c.sourceforge.net/maven2repository/org/springframework/richclient/
and we have the source here:
https://svn.sourceforge.net/svnroot/spring-rich-c/tags/spring-richclient-0.2.1/
So I followed "Guide to uploading artifacts to Ibiblio" from
http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
but as soon as I did
mvn source:jar javadoc:jar repository:bundle-create
I got this error:
Packaging cannot be POM when creating an upload bundle.
which is probably related to this bug:
http://jira.codehaus.org/browse/MREPOSITORY-3
so what's the easiest way to get spring-richclient on the central repo?
- ask for a sync from our repo? is that possible?
- mess around with manually doing each module (which are a lot...) and
do the parent pom's also manually?
- Just wait till MREPOSITORY-3 is fixed and then do it (even it's just a
snapshot)?
- Will Archiva help in this in any way in the future?
Thanks for any and all help.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
