<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">No, it’s still not the recommend approach for real projects.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 31 Oct 2014, at 16:49, Sande Gilda <<a href="mailto:sgilda@redhat.com" class="">sgilda@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
Which reminds me. Should I remove the 3rd paragraph (see below) from
this topic [1] in the JBoss EAP 6.4 Development Guide?<br class="">
<blockquote class="">This method of configuration is generally not
recommended. If <span style="text-decoration: none;
border-bottom: 1px dashed; border-color: green" onclick="javascript:displayDictionaryTopic(25520)" class="">you</span>
decide to configure repositories in your project POM file, plan
carefully and be aware that it <span style="text-decoration:
none; border-bottom: 1px dashed; border-color: green" onclick="javascript:displayDictionaryTopic(25610)" class="">can</span>
slow down your build and <span style="text-decoration: none;
border-bottom: 1px dashed; border-color: red" onclick="javascript:displayDictionaryTopic(30272)" class="">you may</span>
even end up with artifacts that are not from the expected
repository. <br class="">
</blockquote>
[1]
<a class="moz-txt-link-freetext" href="https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#Configure_the_JBoss_Enterprise_Application_Platform_Maven_Repository_Using_the_Project_POM">https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#Configure_the_JBoss_Enterprise_Application_Platform_Maven_Repository_Using_the_Project_POM</a><br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">On 10/31/2014 12:39 PM, Pete Muir
wrote:<br class="">
</div>
<blockquote cite="mid:68C1469A-3046-4637-8F1E-2CBAC3610044@redhat.com" type="cite" class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
We’re switching back :-/<br class="">
<div class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On 31 Oct 2014, at 15:48, Keith Babo <<a moz-do-not-send="true" href="mailto:kbabo@redhat.com" class="">kbabo@redhat.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
<div class="">Hey - this caught me a bit by surprise. I
thought that the JDF approach was to externalize
repository definitions from the pom.xml and reference
them via an external settings.xml. I ask because we
have traditionally included repo definitions in SY
quickstarts.</div>
<div class=""><br class="">
</div>
<div class="">thanks,</div>
<div class="">keith</div>
<br class="">
<div class="">
<div class="">On Oct 31, 2014, at 9:56 AM, Rafael
Benevides <<a moz-do-not-send="true" href="mailto:benevides@redhat.com" class="">benevides@redhat.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite" class="">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""> Hi
all,<br class="">
<br class="">
I was thinking about the implementation of the
repository definition in pom.xml and I want to
share my thoughts:<br class="">
<br class="">
- Create a QSTools CHECKER to mark the lack of
<repository /> as a guideline violation if
MavenCentralChecker is disabled.<br class="">
- The violation message will instruct to use
the new QSTools GOAL that will be created<br class="">
<br class="">
- Create another QSTools GOAL to setup the
repositories.<br class="">
- There will be a list of approved repositories
and its IDs (redhat techpreview, earlyacess, jboss
developer temporary, etc)<br class="">
- QSTools will remove all previous repositories
from pom.xml and prompt which repositories should
be added.<br class="">
- 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 class="">
<br class="">
Please,<br class="">
<br class="">
If you have any feedback on this, feel free to
reply.<br class="">
<br class="">
<div class="moz-signature">-- <br class="">
<meta http-equiv="content-type" content="text/html; charset=windows-1252" class="">
<div style="font-family: Arial; font-size:
10pt;" class=""><br class="">
<b class="">Rafael Benevides | Senior Software
Engineer</b><br class="">
JBoss Developer<br class="">
M: +55-61-9269-6576<br class="">
<br class="">
<span class=""><{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg></span><br class="">
<br class="">
Better technology. Faster innovation. Powered
by community collaboration. <br class="">
See how it works at <a moz-do-not-send="true" href="http://www.redhat.com/" class="">www.redhat.com</a>
<br class="">
<br class="">
<a moz-do-not-send="true" href="http://www.linkedin.com/company/3258288" class=""><span class=""><linkedin.png></span></a>
<a moz-do-not-send="true" href="https://www.youtube.com/redhatlatam" class=""><span class=""><youtube.png></span></a>
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</blockquote>
<br class="">
</div>
</div></blockquote></div><br class=""></div></body></html>