<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Those other repos (jboss-public, fuse-public,
jboss-developer-staging) exists just to make it easy to add them for
development branches. We use jboss-developer-staging a lot for
staged BOMs.<br>
<br>
I also added Fuse repo because 6.1.0 was released using it. Check
it: <a class="moz-txt-link-freetext" href="https://github.com/jboss-fuse/quickstarts/releases">https://github.com/jboss-fuse/quickstarts/releases</a> - Should it
be removed ?<br>
<br>
One of the goals of <b>QSTools:repositories goal</b> (1.5.0.CR3) is
to make it easy to setup repos by making only
redhat-techpreview-all-repository and
redhat-earlyaccess-all-repository
available on stable branches.<br>
<br>
<br>
I'll wait Fred to confirm repo IDs. Thanks<br>
<br>
<br>
<div class="moz-cite-prefix">On 11/13/14 11:21, Max Rydahl Andersen
wrote:<br>
</div>
<blockquote
cite="mid:D443976B-5784-4474-A3E2-2D32BC3989E7@redhat.com"
type="cite">On 31 Oct 2014, at 22:34, Rafael Benevides wrote:
<br>
<br>
<blockquote type="cite">Max/Fred
<br>
<br>
Can you please review <a class="moz-txt-link-freetext" href="https://mojo.redhat.com/docs/DOC-997344">https://mojo.redhat.com/docs/DOC-997344</a>
and confirm if those ids are ok. If not, do you mind to place
the right information at the document?
<br>
</blockquote>
<br>
sorry for late response.
<br>
<br>
Looking at this list the only two repositories I consider valid in
production quickstarts are:
<br>
<br>
redhat-techpreview-all-repository
<br>
<a class="moz-txt-link-freetext" href="http://maven.repository.redhat.com/techpreview/all/">http://maven.repository.redhat.com/techpreview/all/</a>
<br>
<br>
redhat-earlyaccess-all-repository (for things not GA)
<br>
<a class="moz-txt-link-freetext" href="https://maven.repository.redhat.com/earlyaccess/all/">https://maven.repository.redhat.com/earlyaccess/all/</a>
<br>
<br>
<br>
These are I'm surprised we are now letting in:
<br>
<br>
Jboss public repo is not something our productized nor project
quickstarts should depend on is it ? Was there not a requirement
for quickstarts
<br>
to *not* rely on this repo that is a big mashup of dependencies
and instead only rely on central published artifacts ?
<br>
jboss-public-repository
<br>
<a class="moz-txt-link-freetext" href="https://repository.jboss.org/nexus/content/groups/public/">https://repository.jboss.org/nexus/content/groups/public/</a>
<br>
<br>
Fuse reposource repo I thought was only being used for old fuse
releases ? If that is no longer the case then that is not great
since
<br>
it seem to have a lot of redundancy of artifacts.
<br>
fuse-public-repository
<br>
<a class="moz-txt-link-freetext" href="https://repo.fusesource.com/nexus/content/groups/public">https://repo.fusesource.com/nexus/content/groups/public</a>
<br>
<br>
This repo I do not understand what is for and should not be
exposed anywhere IMO. Only relevant to put in testers own
settings.xml is it not ?
<br>
jboss-developer-staging-repository
<br>
<a class="moz-txt-link-freetext" href="http://jboss-developer.github.io/temp-maven-repo/">http://jboss-developer.github.io/temp-maven-repo/</a>
<br>
<br>
About the ID's correctness/alignment with our tools that is
something Fred should be able to verify better than I.
<br>
<br>
/max
<br>
<br>
<blockquote type="cite">Pete/Max,
<br>
<br>
Do you know if Fuse maven repository still valid ?
<br>
<br>
<br>
Thanks
<br>
<br>
On 10/31/14 11:56, Rafael Benevides wrote:
<br>
<blockquote type="cite">Hi all,
<br>
<br>
I was thinking about the implementation of the repository
definition in pom.xml and I want to share my thoughts:
<br>
<br>
- Create a QSTools CHECKER to mark the lack of <repository
/> as a guideline violation if MavenCentralChecker is
disabled.
<br>
- The violation message will instruct to use the new QSTools
GOAL that will be created
<br>
<br>
- Create another QSTools GOAL to setup the repositories.
<br>
- There will be a list of approved repositories and its IDs
(redhat techpreview, earlyacess, jboss developer temporary,
etc)
<br>
- QSTools will remove all previous repositories from pom.xml
and prompt which repositories should be added.
<br>
- This will help Quickstarts and demos to be easily buildable
from development and production branches and will also allow
this list to be bulk updated to remove any previous
development repository definition.
<br>
<br>
Please,
<br>
<br>
If you have any feedback on this, feel free to reply.
<br>
<br>
-- <br>
<br>
*Rafael Benevides | Senior Software Engineer*
<br>
JBoss Developer
<br>
M: +55-61-9269-6576
<br>
<br>
Red Hat
<br>
<br>
Better technology. Faster innovation. Powered by community
collaboration.
<br>
See how it works at <a class="moz-txt-link-abbreviated" href="http://www.redhat.com">www.redhat.com</a>
<a class="moz-txt-link-rfc2396E" href="http://www.redhat.com/"><http://www.redhat.com/></a>
<br>
<br>
LinkedIn <a class="moz-txt-link-rfc2396E" href="http://www.linkedin.com/company/3258288"><http://www.linkedin.com/company/3258288></a>
Youtube <a class="moz-txt-link-rfc2396E" href="https://www.youtube.com/redhatlatam"><https://www.youtube.com/redhatlatam></a>
<br>
<br>
<br>
_______________________________________________
<br>
jbossdeveloper mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:jbossdeveloper@lists.jboss.org">jbossdeveloper@lists.jboss.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbossdeveloper">https://lists.jboss.org/mailman/listinfo/jbossdeveloper</a>
<br>
</blockquote>
<br>
_______________________________________________
<br>
jbossdeveloper mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:jbossdeveloper@lists.jboss.org">jbossdeveloper@lists.jboss.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbossdeveloper">https://lists.jboss.org/mailman/listinfo/jbossdeveloper</a>
<br>
</blockquote>
<br>
<br>
/max
<br>
<a class="moz-txt-link-freetext" href="http://about.me/maxandersen">http://about.me/maxandersen</a>
<br>
</blockquote>
<br>
</body>
</html>