Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 370310 - Files should be only be able to be opened as read/only for non-SNAPSHOT projects
Summary: Files should be only be able to be opened as read/only for non-SNAPSHOT projects
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-01 04:48 EST by Thorbjørn Ravn Andersen CLA
Modified: 2021-04-19 13:25 EDT (History)
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 Thorbjørn Ravn Andersen CLA 2012-02-01 04:48:47 EST 
We use a lot of helper projects which have different development cycles than the main projects, so they should stay in a released state most of the time, i.e. not have a -SNAPSHOT version.

Released projects should not be modifiable.  Hence it would be good to have m2e enforce that non-SNAPSHOT projects cannot be modified, e.g. by telling Eclipse that all files in that project are read/only.  

Changing the version (and rereading the configuration from pom.xml) should reset this flag.
Comment 1 Igor Fedorenko CLA 2013-09-29 10:03:43 EDT 
m2e dynamic sourcelookup extension https://github.com/ifedorenko/com.ifedorenko.m2e.sourcelookup (also available from eclipse marketplace) supports notion of 'maven binary projects', which I believe is what you want. There are no immediate plans to bring this functionality to m2e core however.
Comment 2 Denis Roy CLA 2021-04-19 13:25:23 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/