[ https://jira.jboss.org/browse/JBBUILD-664?page=com.atlassian.jira.plugin.... ] Paul Gier updated JBBUILD-664: ------------------------------ Fix Version/s: Repository Support 2010 Component/s: Artifact Repositories -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBBUILD-664?page=com.atlassian.jira.plugin.... ] Sean Flanigan commented on JBBUILD-664: --------------------------------------- Thanks Paul! Could I get you to add the groupIds org.fedorahosted.openprops and org.fedorahosted.tennera to the routing rule, please? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBBUILD-664?page=com.atlassian.jira.plugin.... ] Sean Flanigan reopened JBBUILD-664: ----------------------------------- Paul, thanks for adding the proxies! I'm afraid I still need some help. Not sure if it's routing or something else. I'm finding that flies artifacts, for example: org.fedorahosted.openprops:openprops:0.5 org.fedorahosted.tennera:jgettext:0.6 net.openl10n.flies:flies-maven-plugin:1.1-alpha-1 are available if I go directly to the proxy repository: https://repository.jboss.org/nexus/content/repositories/flies-releases/ but not through the groups: https://repository.jboss.org/nexus/content/groups/developer/ https://repository.jboss.org/nexus/content/groups/public/ https://repository.jboss.org/nexus/content/groups/public-thirdparty-relea... (Also, the org.fedorahosted artifacts don't show up in the index for flies-releases or anywhere else, but the indices are obviously less important than the artifacts. I think snapshots have even more problems, but they're the least of my worries at present!) I've been testing the repo setup with this little script 'm2checkflies': ----------------------------------------------------------------------------------- #!/bin/bash # this repo works: #REPO=https://repository.jboss.org/nexus/content/repositories/flies-releases/ # these repos don't: REPO=https://repository.jboss.org/nexus/content/groups/developer/ #REPO=https://repository.jboss.org/nexus/content/groups/public/ #REPO=https://repository.jboss.org/nexus/content/groups/public-thirdparty-releases/ get=org.apache.maven.plugins:maven-dependency-plugin:2.1:get rm -fr ~/.m2/repository/org/fedorahosted ~/.m2/repository/net/openl10n mvn $get -DrepoUrl=$REPO -Dartifact=org.fedorahosted.openprops:openprops:0.5 mvn $get -DrepoUrl=$REPO -Dartifact=org.fedorahosted.tennera:jgettext:0.6 mvn $get -DrepoUrl=$REPO -Dartifact=net.openl10n.flies:flies-maven-plugin:1.1-alpha-1 ----------------------------------------------------------------------------------- Those artifacts should be available via the above group repositories, right? (And the staging repo too?) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBBUILD-664?page=com.atlassian.jira.plugin.... ] Sean Flanigan closed JBBUILD-664. --------------------------------- Resolution: Done Thank you Paul and Graeme; that's looking great. The groups all work, including Staging, except Public Thirdparty Releases Group. Was that one meant to include Flies? Either way, I don't think it will cause a problem. I see the indexing is a known problem area: https://jira.jboss.org/browse/JBBUILD-663 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBBUILD-664?page=com.atlassian.jira.plugin.... ] Sean Flanigan commented on JBBUILD-664: --------------------------------------- Got it, thanks. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira