[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] TCK download directory conventions
|
Right, a link to Jenkins isn't good enough.
I don't think this belongs in Maven. There's plenty of repositories or
web sites associated with a project, I'm just not sure which is best.
Maybe we lay out some options and leave it to the project to decide?
Ed Bratt wrote on 7/16/19 5:24 PM:
> 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.
