Re: [m2e-dev] Extension changing runtime environment

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

Re: [m2e-dev] Extension changing runtime environment

From: Csaba Kozák <kozakcsabi@xxxxxxxxx>
Date: Fri, 16 Jan 2015 16:42:05 +0100
Delivered-to: m2e-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/m2e-dev>
List-help: <mailto:m2e-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/m2e-dev>, <mailto:m2e-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/m2e-dev>, <mailto:m2e-dev-request@eclipse.org?subject=unsubscribe>

Hi Fred!

Thanks for the tip! Actually we already do this manually, by calling the javaProjectConfigurator.configure(), so this may be interesting.

BTW, i solved the original problem by removing the target folder from the resolved classpath.

References:
- [m2e-dev] Extension changing runtime environment
  - From: Martin Frydl
- Re: [m2e-dev] Extension changing runtime environment
  - From: Fred Bricon

Prev by Date: Re: [m2e-dev] Extension changing runtime environment
Next by Date: Re: [m2e-dev] Extension changing runtime environment
Previous by thread: Re: [m2e-dev] Extension changing runtime environment
Next by thread: Re: [m2e-dev] Extension changing runtime environment
Index(es):
- Date
- Thread

Back to the top