Em 9/5/14, 9:52, Sande Gilda
escreveu:
Hi Rafael and everyone,
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?
Idk
- Do I need to add the repository to all the POM files?
I'm improving QSTools to do that for us: https://issues.jboss.org/browse/JDF-762
- Should I update all the README files to mention that it is
not a good practice to add the repository to the POM files?
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".
- Should I remove the settings.xml file?
Maybe after we run QSTools to "inject" the repository into the
Quickstarts.
Thanks,
Sande
On 09/05/2014 07:58 AM, Rafael
Benevides wrote:
Em 9/5/14, 8:47, Max Rydahl
Andersen escreveu:
so a few things:
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).
Since the Archtypes were released, should I update the Stacks
to `
jboss-product-repository` for those archtypes only ? Then I
update the patch for 'redhat-techpreview-all-repository' for
the next EAP 6.4 release ?
I can also see that earlyaccess is now enabled
by default on https://github.com/jboss-developer/jboss-eap-quickstarts/commit/35847933994901f2ff29e0de20de1845f7972708
is that expected ?
I don't know.
Anyways:
1) can we agree on aligning the id's ? (just so we are in
sync)
Yeap. For sure! I'll update the patch file now for
to 'redhat-techpreview-all-repository' as I just said..
2) is it expected the id says 'ga' but the url is not that ?
Once that we change to '
redhat-techpreview-all-repository' it won't matter anymore.
For #1 we should look at updating that in stacks.yml so we
add it with the same id.
Before changing stacks.yml I want to be sure #2 was
consistent choice we wanted to make for that?
ps. we actually also add this repo as a plugin repository -
not sure if that matters for you?
I don't think it matters since the tests worked fine.
So that's my plan:
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.
2 - Wait for your answer if we should update stacks.yaml repo
to '
jboss-products-ga-repo' for EAP 6.3 Archetypes only
Is that right ?
/max
_______________________________________________
jbossdeveloper mailing list
jbossdeveloper@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossdeveloper
_______________________________________________
jbossdeveloper mailing list
jbossdeveloper@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossdeveloper