Getting Flies maven plugin into jboss.org repository

[sflanigan]

G'day,

I want to get the Flies maven plugin into the jboss.org repository so that it can be used by jboss.org projects.  At present the Flies plugin is available through the group repository http://nexus.openl10n.net/content/groups/public/.  It has dependencies from Central, JBoss and a few third-party jars (all available through the group repository, some via proxy repositories).

I've found the pages  http://community.jboss.org/wiki/MavenRepository and http://community.jboss.org/wiki/UploadingaThirdpartyArtifact but I'm still unclear on the best approach.  Should I be asking to have the above group repository (or the individual repositories) added as proxies in JBoss Nexus?  What are the policies for adding a new proxy?

I see there is a proxy for Central, but I see it is excluded from groups/public.  Hypothetically speaking, if the Flies maven plugin were deployed to maven Central, would it be available to JBoss projects? 

Thanks

Sean.

[pgier]

The best approach is probably to get it into central either via oss.sonatype.org (https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide) or some other way.  If it's in central, it is available to jboss projects either directly from central or through the "developer" and "staging" repository groups.  For development builds, it's recommended that central is used directly because of our bandwidth limitations, but for release builds, JBoss community developers are recommended to use the "staging" group which includes the central proxy.

[sflanigan]

Thanks, that's good to know, but I don't think I'll be able to get my plugin into Central unless I replace my JBoss dependencies (specifically RESTEasy) with non-JBoss alternatives.  (That's why it was hypothetical!)

What are the policies for adding a new proxy to JBoss Nexus?  UploadingaThirdpartyArtifact just says to request a proxy if the artifact is available elsewhere, but I assume you don't just approve any and all proxies.

[pmuir]

Paul, what about just adding Sean's repo to the list that we proxy? Flies is the "new" way that JBoss projects can do l10n for docs, so will be used by a lot of JBoss projects. If Sean's repo is pretty clean (just flies + deps) I can't see a problem with that.

[sflanigan]

I reviewed the plugin dependencies today, using Maven's dependency report.  Almost all the dependencies should be available in jboss.org or central, so it would be great if you could proxy the Flies Releases repository:

http://nexus.openl10n.net/content/repositories/releases/

It's pretty clean IMHO.  The Flies plugin has one dependency (Tennera JGettext)  which comes from an old SVN-based repository, a repo which isn't so clean because I uploaded a few random jars which couldn't be found anywhere as Maven artifacts.  But I maintain JGettext too, so I think I'll just move it into the above repository and deprecate the unclean repository.

It wouldn't hurt to proxy the Flies Snapshots too, if that's okay:

http://nexus.openl10n.net/content/repositories/snapshots/

Edit: https://jira.jboss.org/browse/JBBUILD-664

Thanks!

Sean.

PS what is with this editor?  If I paste from another window, the text is only visible in the HTML view.