[ https://issues.jboss.org/browse/JBDS-3775?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3775: ------------------------------------------- This issue is tricky. btw. you can fix this by using quick fix on the missing dependency, right ? Force adding our maven repository have so far been considered really intrusive. In eclipse we have a quick fix for it that very clearly shows what we will change. This quick fix must still exist since majority of users bumping into this will *not* use the uber installer (i.e. eclipse marketplace installs) Doing it in the installer I guess is feasible, but we'll need to take care of the following situatoins: A) user has no maven settings file - installer should ask if we should create one for him since it is not sure he will even need/use it. B) user has maven settings file - installer could assume he wants the change, but do have it clear in the UI it is changing and be able to turn it of. C) B but file is not in standard location - this is similar to A, but user has MAVEN_SETTINGS (?) set to point somewhere else. we'll need to be able to handle that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)