On Fri, Apr 26, 2013 at 08:58:51AM +0100, Pete Muir wrote:
> Note - I assume we'll
> Still introduce wildfly 8 etc into stacks.yml to get feedback/testing done early
here, correct or?
Yes. I think we can still add upstream stuff to stacks. We may need a way to indicate this
in the format as well.
My main concern is that current logic for our wizards in JBT Central is to lookup a
specific archetype GAV and then
find out which runtimes supports that.
With the new layout there is no such mapping...i.e. how do we know to find the right
archetype for the JavaEE 6 Wizard..there
is no longer a single answer in this case afaics.
>>> Will -qs-1 be adjusted to -qs-1-redhat-NN pattern when
put into products or does that go away for these cases?
>>
>> No, these are the product BOMs.
>
> Ok. Any reason to not use -redhat then ?
> Is that because they will now be considered a separate deliverable ?
We didn't want to overload the meaning of -redhat-X, but we could do so if you guys
think it is best.
if they are products bom's -redhat seems more consistent if I grok it right.
>> We would no longer bundle them in the product zip repos,
instead just deliver them online via
maven.repository.redhat.com
>
> Okey so we can't count on them when users have just the zips for the offline
mode. Just something to remember to copy when we go offline.
Yes. These are now an overlay so don't belong to a particular project. I guess we
could do a zip of the overlay if it's really needed.
not really important for us - what we would need is to run a script to provide an
"offline version" with enough of the artifacts
for the examples to run (independent of runtime versions) in a training room situation.
...depending on how much data/time that takes
it might be creating a full zip of the overlay will be simpler :)
/max