On 30 Oct 2014, at 22:29, Rafael Benevides wrote:
On 9/22/14 10:54, Max Rydahl Andersen wrote:
On 16 Sep 2014, at 11:56, Pete Muir wrote:
On 16 Sep 2014, at 00:27, Max Rydahl Andersen <max.andersen@redhat.com> wrote:
On 9 Sep 2014, at 16:07, Rafael Benevides wrote:
We also need to check that with JBDS, because it's odd that stacks only
uses "redhat-techpreview-all-repository" as additional repository.
because it was the only thing we needed originally.
Max/Fred,
Is there any issues having
https://maven.repository.redhat.com/earlyaccess/all/ as declared inside
quickstarts pom.xml ?
sorry - but I need to grok when earlyaccess/all is even needed before answering that ? :)
My default position would be that if you need earlyaccess you are expected to be able to understand why you need it.
But i'm not sure if that is true anymore - hence wanting to ask why/when earlyaccess is ever needed ?
is it for running quickstarts targeting a beta version of EAP ? (meaning no snapshots, but actual all releases in it?)
Right, it’s where we put beta and alpha releases.
If yes, why doesn't /all get split up in /supported and /earlyaccess and /all will serve the combined result ?
Propose this on the wolf list?
Added as topic on tomorrows wolf call: http://pad.engineering.redhat.com/wolf
/max
/max
http://about.me/maxandersen
Max,
What was the result of this subject in wolf call ?
For now the split would stay, but we remove the /all grouping that was introduced by error (it was a neither or).
the final grouping says on line 110 on
http://pad.engineering.redhat.com/wolf"Pete and David to follow up offline, fix up mojo doc, and send to list for signoff."
I haven't seen this yet. Maybe I missed something while I was on PTO ?