incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Seaborne (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-196) LARQ svn includes Eclipse .settings directories
Date Wed, 18 Jan 2012 09:01:42 GMT


Andy Seaborne commented on JENA-196:

I'm not sure that m2e can control the warnings levels in the same way as the incremental parser/compiler
in the Eclipse Java editor.  We have per-Eclipse-project settings (e.g. compiler = Java6,
warning enabled) not the general Eclipse-wide preferences. I seem to get different warnings
in an m2e-controlled project with more detailed warnings in Eclipse - can I make them the

There is some point checking in code templates though (ASF bolierplate) which is a ui.prefs

CXF uses;


so isn't that compiler specific?

.settings/ is a directory with separate files for different aspects.  We can check in some
files (e.g. compiler settings) and not other (e.g. UI prefs) if someone wants to spend a moment
to work out which is which.

We do need to have someway of communicating the right setup in Eclipse - it helps processing
contributions if people have used the same setup although it does not force them to and we
get contributions with many warnings.  Unused imports being common; while harmless, it obscures
potentially significant warnings.  "no warning" is much easier to work with at scale.

But in LARQ, the only settings are:
.settings/ ==>
total 4
-rw-r--r-- 1 afs afs 333 Oct  7 18:57 org.eclipse.jdt.core.prefs

and that file is:

#Fri Sep 23 14:59:38 BST 2011

Ian - what was clashing? (Other modules are decidedly messier.)
> LARQ svn includes Eclipse .settings directories
> -----------------------------------------------
>                 Key: JENA-196
>                 URL:
>             Project: Jena
>          Issue Type: Bug
>          Components: LARQ
>            Reporter: Ian Dickinson
>            Assignee: Paolo Castagna
>            Priority: Minor
> I don't think that the svn image should include Eclipse .settings directory. Personally,
I'd prefer the svn didn't include .classpath and .project as well, but definitely not settings.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message