Re: [cross-project-issues-dev] EMF Plug-in Versioning and Reexported Dep

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

Re: [cross-project-issues-dev] EMF Plug-in Versioning and Reexported Dependencies

From: Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>
Date: Mon, 23 Oct 2006 12:55:09 -0700
Delivered-to: cross-project-issues-dev@xxxxxxxxxxx
List-archive: <http://eclipse.org/pipermail/cross-project-issues-dev>
List-help: <mailto:cross-project-issues-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>, <mailto:cross-project-issues-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>, <mailto:cross-project-issues-dev-request@eclipse.org?subject=unsubscribe>
Organization: Eclipse Foundation Inc.
User-agent: Thunderbird 1.5.0.7 (Windows/20060909)

This makes sense to me.

John Arthorne wrote:

I agree with this. If A changes version, but still falls within the range originally exported by B, then there is no need for B to update its own version number. However, if B changes the range that it imports for A, then it must increase its own version number accordingly.

If this makes sense to everyone I'll update the guidelines accordingly.

References:
- Re: [cross-project-issues-dev] EMF Plug-in Versioning and Reexported Dependencies
  - From: John Arthorne

Prev by Date: Re: [cross-project-issues-dev] EMF Plug-in Versioning and Reexported Dependencies
Next by Date: Re: [cross-project-issues-dev] EMF Plug-in Versioning and Reexported Dependencies
Previous by thread: Re: [cross-project-issues-dev] EMF Plug-in Versioning and Reexported Dependencies
Next by thread: Re: [cross-project-issues-dev] EMF Plug-in Versioning and Reexported Dependencies
Index(es):
- Date
- Thread

Breadcrumbs