121261 – Need an Export for Compiler Errors/Warnings

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 121261 - Need an Export for Compiler Errors/Warnings

Summary: Need an Export for Compiler Errors/Warnings

Status:	CLOSED DUPLICATE of bug 163543

Alias:	None

Product:	JDT
Classification:	Eclipse Project
Component:	UI (show other bugs)
Version:	3.1.1
Hardware:	PC Windows XP

Importance:	P3 enhancement (vote)
Target Milestone:	---
Assignee:	JDT-UI-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-12-16 14:01 EST by Mark Levison
Modified:	2010-04-15 04:19 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Mark Levison

2005-12-16 14:01:31 EST

I'm attempting to setup project wide standards for coding style warnings (Window -> Preferences -> Java -> Compiler -> Errors/Warnings) and there isn't an export mechanism. So I'm reduced to taking screen shots of my settings and asking developers to use them. As you can imagine this is prone to error.

A solution: Like Code Style -> Formatting; there should be an import/export so I could export my settings and share with my team.

Comment 1 Tobias Widmer

2005-12-22 05:08:49 EST

There is a mechanism called project specific settings, which is available from the project property page. These settings are stored in a subfolder .settings of the project and are therefore shared with the team and can be manually processed.

What you are looking for is probably rather a preference category which can be imported/exported using the export preferences wizard.

Martin, any comments?

Comment 2 Martin Aeschlimann

2006-01-09 06:51:23 EST

No plans yet for more export cateories.

Comment 3 Denis Roy

2009-08-30 02:16:01 EDT

As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.

Comment 4 Dani Megert

2010-04-15 04:19:25 EDT

Fixed in 3.6.

*** This bug has been marked as a duplicate of bug 163543 ***