[virgo-dev] Why keep manifest.mf checked in?

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

[virgo-dev] Why keep manifest.mf checked in?

From: Dmitry Sklyut <dmitry@xxxxxxxxxxx>
Date: Mon, 7 Jun 2010 22:06:38 -0400
Delivered-to: virgo-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/virgo-dev>
List-help: <mailto:virgo-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/virgo-dev>, <mailto:virgo-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/virgo-dev>, <mailto:virgo-dev-request@eclipse.org?subject=unsubscribe>

Hi,

I wonder if it still makes sense keeping all of the MANIFEST.MF files around? Bundlor will regen them anyway.

The only reason is to have immediately importable project for IDE usage. But in that case I would hope to see a really slimmed down version without any OSGi metadata outside of Bundle-SymbolicName, Bundle-Name and Version.

Regards,

Dmitry

Follow-Ups:
- Re: [virgo-dev] Why keep manifest.mf checked in?
  - From: Glyn Normington

Prev by Date: Re: [virgo-dev] Maven build issue with war files
Next by Date: [virgo-dev] Virgo maven build
Previous by thread: [virgo-dev] Critique
Next by thread: Re: [virgo-dev] Why keep manifest.mf checked in?
Index(es):
- Date
- Thread

Breadcrumbs