[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] TCK download directory conventions
|
I’m not keen on putting TCK pass results into maven central. Maven central is for code, not html. I don’t have an issue with EE4J implementations choosing to do that, but I wouldn’t want to.
Alasdair Nottingham
> On Jul 16, 2019, at 8:24 PM, Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:
>
> Then that implies projects may not refer to something volatile -- such as a link to a report on a Jenkins worker node or a "staging" server (unless that report is gong to live "forever"). Should we recommend these results live (or an archive JAR lives) on Maven Central? (I'm not entirely sure if this fits in the T&C of Maven Central, but it would meet the longevity requirement.
>
>> On 7/16/2019 1:36 PM, Bill Shannon wrote:
>> Ed Bratt wrote on 7/16/19 9:44 AM:> How long must these results be made available?
>>
>> I believe as long as the release is available, which for Maven Central
>> means forever.
> _______________________________________________
> jakarta.ee-spec.committee mailing list
> jakarta.ee-spec.committee@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
