<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
/s/tech/teach<br>
<br>
<div class="moz-cite-prefix">Em 9/5/14, 9:59, Rafael Benevides
escreveu:<br>
</div>
<blockquote cite="mid:5409B3CD.1020505@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">Em 9/5/14, 9:52, Sande Gilda
escreveu:<br>
</div>
<blockquote cite="mid:5409B1FF.6090707@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Hi Rafael and everyone,<br>
<br>
Do I need to change the 6.4.x-develop branch of the quickstarts
at this point? And if so, what do I need to do?<br>
</blockquote>
Idk<br>
<blockquote cite="mid:5409B1FF.6090707@redhat.com" type="cite">
<ul>
<li>Do I need to add the repository to all the POM files? </li>
</ul>
</blockquote>
I'm improving QSTools to do that for us: <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://issues.jboss.org/browse/JDF-762">https://issues.jboss.org/browse/JDF-762</a><br>
<blockquote cite="mid:5409B1FF.6090707@redhat.com" type="cite">
<ul>
<li>Should I update all the README files to mention that it is
not a good practice to add the repository to the POM files?</li>
</ul>
</blockquote>
I think so as one of the goals of the Quickstarts is to "tech"
users about the best practices. But we should make it clear why
we took this decision so it won't be something like : "Do what We
say, not what We do".<br>
<blockquote cite="mid:5409B1FF.6090707@redhat.com" type="cite">
<ul>
<li>Should I remove the settings.xml file?</li>
</ul>
</blockquote>
Maybe after we run QSTools to "inject" the repository into the
Quickstarts.<br>
<blockquote cite="mid:5409B1FF.6090707@redhat.com" type="cite">
<ul>
</ul>
Thanks,<br>
Sande<br>
<br>
<div class="moz-cite-prefix">On 09/05/2014 07:58 AM, Rafael
Benevides wrote:<br>
</div>
<blockquote cite="mid:5409A564.9020504@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">Em 9/5/14, 8:47, Max Rydahl
Andersen escreveu:<br>
</div>
<blockquote
cite="mid:D2D53978-355C-4F16-B73A-87FF211028E9@redhat.com"
type="cite">so a few things: <br>
<br>
in stacks.yml the id is 'redhat-techpreview-all-repository'
and in this patch it is 'jboss-products-ga-repo' but it is
still using the techpreview url (/techpreview/all). <br>
<br>
</blockquote>
Since the Archtypes were released, should I update the Stacks
to `
<meta charset="utf-8">
<meta charset="utf-8">
jboss-product-repository` for those archtypes only ? Then I
update the patch for 'redhat-techpreview-all-repository' for
the next EAP 6.4 release ?<br>
<blockquote
cite="mid:D2D53978-355C-4F16-B73A-87FF211028E9@redhat.com"
type="cite">I can also see that earlyaccess is now enabled
by default on <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://github.com/jboss-developer/jboss-eap-quickstarts/commit/35847933994901f2ff29e0de20de1845f7972708">https://github.com/jboss-developer/jboss-eap-quickstarts/commit/35847933994901f2ff29e0de20de1845f7972708</a>
is that expected ? <br>
</blockquote>
I don't know.<br>
<blockquote
cite="mid:D2D53978-355C-4F16-B73A-87FF211028E9@redhat.com"
type="cite"> <br>
Anyways: <br>
<br>
1) can we agree on aligning the id's ? (just so we are in
sync) <br>
</blockquote>
Yeap. For sure! I'll update the patch file now for
<meta charset="utf-8">
to 'redhat-techpreview-all-repository' as I just said..<br>
<blockquote
cite="mid:D2D53978-355C-4F16-B73A-87FF211028E9@redhat.com"
type="cite"> <br>
2) is it expected the id says 'ga' but the url is not that ?
<br>
</blockquote>
<br>
Once that we change to '
<meta charset="utf-8">
redhat-techpreview-all-repository' it won't matter anymore.<br>
<blockquote
cite="mid:D2D53978-355C-4F16-B73A-87FF211028E9@redhat.com"
type="cite"> <br>
For #1 we should look at updating that in stacks.yml so we
add it with the same id. <br>
<br>
Before changing stacks.yml I want to be sure #2 was
consistent choice we wanted to make for that? <br>
<br>
ps. we actually also add this repo as a plugin repository -
not sure if that matters for you? <br>
</blockquote>
I don't think it matters since the tests worked fine.<br>
<br>
So that's my plan:<br>
<br>
1 - Update the patch file to use
'redhat-techpreview-all-repository' as repo id instead of
'jboss-products-ga-repo'. It will be available for next EAP
6.4 Archtype release.<br>
<br>
2 - Wait for your answer if we should update stacks.yaml repo
to '
<meta charset="utf-8">
jboss-products-ga-repo' for EAP 6.3 Archetypes only <br>
<br>
Is that right ?<br>
<blockquote
cite="mid:D2D53978-355C-4F16-B73A-87FF211028E9@redhat.com"
type="cite"> <br>
/max </blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jbossdeveloper mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:jbossdeveloper@lists.jboss.org">jbossdeveloper@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbossdeveloper">https://lists.jboss.org/mailman/listinfo/jbossdeveloper</a></pre>
</blockquote>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jbossdeveloper mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbossdeveloper@lists.jboss.org">jbossdeveloper@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbossdeveloper">https://lists.jboss.org/mailman/listinfo/jbossdeveloper</a></pre>
</blockquote>
<br>
</body>
</html>