I did "emerge -e world" last night, and as part of the world update gentoo emerged maven-bin version 2.2. As part of the emerge, my manually changed/ adapted configuration in /usr/share/maven-bin-2.2/conf/settings.xml was overwritten using the default settings.xml from the package. All changes to settings.xml are lost. I would rather expect dispatch-conf to jump in. Reproducible: Always Steps to Reproduce: 1. emerge maven-bin-2.2 2. edit /usr/share/maven-bin-2.2/conf/settings.xml 3. emerge maven-bin-2.2 Actual Results: Any changes /usr/share/maven-bin-2.2/conf/settings.xml Expected Results: Any manual configuration in /usr/share/maven-bin-2.2/conf/settings.xml can be resolved via dispatch-conf The ebuild installs the package using cp -Rp bin boot conf lib "${D}/${MAVEN_SHARE}" || die "failed to copy" which will overwrite conf w/o further notice.
Use /etc/maven2/settings.xml or ~/.m2/settings.xml for custom settings.
(In reply to comment #0) > The ebuild installs the package using > > cp -Rp bin boot conf lib "${D}/${MAVEN_SHARE}" || die "failed to copy" > > which will overwrite conf w/o further notice. That's not the reason, but it can be helped using CONFIG_PROTECT. (In reply to comment #1) > Use /etc/maven2/settings.xml or ~/.m2/settings.xml for custom settings. Since I didn't find maven documentation suggesting /etc/ settings, I rather added the installed one to CONFIG_PROTECT. Should make upgrades via dispatch-conf easier anyway, than keeping your copy in sync manually.
