Re: [pde-dev] main vs test source causing annoyance

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

Re: [pde-dev] main vs test source causing annoyance

From: Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
Date: Fri, 28 Jan 2022 10:04:31 +0100
Delivered-to: pde-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/pde-dev/>
List-help: <mailto:pde-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/pde-dev>, <mailto:pde-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/pde-dev>, <mailto:pde-dev-request@eclipse.org?subject=unsubscribe>

On Jan 28, 2022, at 09:21, Mickael Istria <mistria@xxxxxxxxxx> wrote:
> I think we should act on fixing those .classpath and emit a rule to not use those "test" metadata on test bundles. Also, we should probably make PDE *not* add those metadata for plugins by default.


I agree. Forcing a new concept (even if its better) onto a legacy (without updating all the legacy) doesn't make it better. Instead it should be honored that OSGi bundles (and plug-ins) don't have a concept of main vs. test classpath. There is just one bundle classpath.

A test classpath (like Maven projects do) should be added as an opt-in so that projects can start adopting it when they are ready.

-Gunnar

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/

References:
- [pde-dev] main vs test source causing annoyance
  - From: Mickael Istria

Prev by Date: Re: [pde-dev] [platform-dev] main vs test source causing annoyance
Next by Date: Re: [pde-dev] [platform-dev] main vs test source causing annoyance
Previous by thread: Re: [pde-dev] [platform-dev] main vs test source causing annoyance
Next by thread: Re: [pde-dev] [platform-dev] main vs test source causing annoyance
Index(es):
- Date
- Thread

Breadcrumbs