[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse.org-architecture-council] [Bug 261766] Push the non-externalized strings flag as an error on RC builds.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=261766  
Product/Component: Community / Cross-Project

Martin Oberhuber <martin.oberhuber@xxxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |martin.oberhuber@xxxxxxxxxxx
                   |                            |om
         AssignedTo|eclipse.org-architecture-   |cross-
                   |council@xxxxxxxxxxx         |project.inbox@xxxxxxxxxxx
          Component|Architecture Council        |Cross-Project




--- Comment #1 from Martin Oberhuber <martin.oberhuber@xxxxxxxxxxxxx>  2009-01-21 03:55:29 -0400 ---
This is a matter of policy between Babel and the projects participating on the
Release Train. We cannot force every user of JDT / PDE to externalize Strings.

Forwarding to cross-project for discussion.

One idea to resolve this would be providing a *.epf file of default Preferences
(including default warning levels) that projects should import and/or apply to
their projects. Another idea is asking all projects to have a common set of
flags / warnings defined on project level.

Technically, bug 194414 or bug 245405 could help here. But I believe that the
policy needs to be sorted out by the participating train projects / projects
participating in Babel / the Planning Council first.


-- 
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.