Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] org.eclipse.jdt.core.prefs 1.5, 1.7 ? management by maven
Hi,

There is something like this.  Oomph provides a project preferences management tool that maintains consistency of all our projects' settings.  The JDK level is determined by each plug-in's BREE and everything else is kept in sync with the settings in the org.eclipse.papyrus.infra.core plug-in, which serves as the master or template for our common project preferences.

You will notice how every time new plug-ins are added they are followed shortly after by a commit that brings their preferences up to standard.

The .prefs files for preferences don't support arbitrary variable substitution and never have. They predate any sort of integration of maven into Eclipse.  Using maven to substitute variables in these files would require an external maven execution to populate them before first use of a new workspace. Let's not do that.

Cheers,

Christian




On Wed, Mar 11, 2015 at 3:29 AM, Ed Willink <ed@xxxxxxxxxxxxx> wrote:

Hi

I recall raising a Bugzilla a long time ago about a missing level of Eclipse project hierarchy between project (CM controlled) and workspace (personal and anarchic). There should be super-projects (CM controlled) so that e.g. all Papyrus projects inherit their CM controlled settings from a single super-project. JDT preferences are just one example of this. Without this, everything else seems like a fudge.

Perhaps Papyrus could motivate fixing this longstanding deficiency.

    Regards

        Ed Willink

On 11/03/2015 07:16, LE FEVRE FRANCOIS wrote:

Dear all,

I have some difficulties to understand how is managed the jre version between eclipse, tycho and maven.

I have found that projects/plugins hold a org.eclipse.jdt.core.prefs files with

 

org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.7/1.5

org.eclipse.jdt.core.compiler.compliance=1.7/1.5

org.eclipse.jdt.core.compiler.source=1.7/1.5

 

my question is:

why these file do not have a project properties such as ${jre.compiler.target.version}, ${jre.compiler.compliance.version}, ${jre.compiler.source.version} defined somewhere else?

Or

Why we do not have a uniq org.eclipse.jdt.core.prefs that is hold by a configuration project and when maven/tycho is called the first build phase will consist to copy and filter this file?

 

Thanks for your comments.

 

Francois

 

 

 

 

François Le Fèvre

Institut CARNOT CEA LIST – Nano INNOV

CEA Tech/DILS/Laboratoire d’Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE),

Point Courrier n°174

91191 Gif sur Yvette CEDEX

T :0169084986

@ :francois.le-fevre@xxxxxx

 

-

LISE: http://www-list.cea.fr/fr/ingenierie-logiciel-et-systeme

Papyrus: https://www.eclipse.org/papyrus/

Blog: http://biocamp.blogspot.fr/

 



_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5751 / Virus Database: 4299/9270 - Release Date: 03/10/15


Back to the top