Re: [jakarta.ee-spec.committee] Updating APIs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [jakarta.ee-spec.committee] Updating APIs

From: Scott Stark <sstark@xxxxxxxxxx>
Date: Thu, 18 Jul 2019 13:01:12 -0700
Delivered-to: jakarta.ee-spec.committee@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/jakarta.ee-spec.committee>
List-help: <mailto:jakarta.ee-spec.committee-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee>, <mailto:jakarta.ee-spec.committee-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/jakarta.ee-spec.committee>, <mailto:jakarta.ee-spec.committee-request@eclipse.org?subject=unsubscribe>

If @version cannot be generated, can we just recommend dropping it?

On Jul 18, 2019, at 11:18 AM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

You may not remove the Oracle copyright line.

You may add additional copyright lines for additional copyright holders.

Ideally you should be using the GlassFish copyright plugin to verify that the copyright/license headers are correct.

Personally I don't see the value of @version. If it means you have to touch every file for every release, that just seems unnecessary.

There's an ongoing discussion about @since, but what you have below seems fine for now.

Follow-Ups:
- Re: [jakarta.ee-spec.committee] Updating APIs
  - From: Bill Shannon

References:
- [jakarta.ee-spec.committee] Updating APIs
  - From: Richard Monson-Haefel
- Re: [jakarta.ee-spec.committee] Updating APIs
  - From: Bill Shannon

Prev by Date: Re: [jakarta.ee-spec.committee] Updating APIs
Next by Date: Re: [jakarta.ee-spec.committee] Updating APIs
Previous by thread: Re: [jakarta.ee-spec.committee] Updating APIs
Next by thread: Re: [jakarta.ee-spec.committee] Updating APIs
Index(es):
- Date
- Thread

Breadcrumbs