I updated from using a black list in all proxies to white listing just the repo-specific artifacts, but I still need to fix the issue with the "On Remote Error" settings not persisting.
Does the <propagate-errors/> setting in the archiva.xml correlate directly with "On Remote Error"? Has anyone else seen this? On Tue, Aug 7, 2012 at 5:25 PM, Jeff <[email protected]> wrote: > I don't know if this is a side effect of including a "Black list" pattern > in all of my proxy connectors to filter out my internal company artifacts, > but now when I set "On Remote Error" to "queue error" in my proxy > connectors then restart tomcat or Archiva, the setting reverts back to > "stop". > > In the archiva.xml I thought this setting was associated > with <propagate-errors>queue error</propagate-errors>, but on startup in > archiva.log, I see this: > > 2012-08-07 15:44:47,608 [main] WARN > org.apache.archiva.configuration.DefaultArchivaConfiguration - Policy > [propagate-errors-on-update] does not exist. > 2012-08-07 15:44:47,608 [main] WARN > org.apache.archiva.configuration.DefaultArchivaConfiguration - Policy > [propagate-errors] does not exist. > > If I change the proxy connector "On Remote Error" setting, it seems to > keep it in memory, but I'm not seeing any updates written to the > archiva.xml file. > > Any hints? > > -- > Jeff Vincent > [email protected] > See my LinkedIn profile at: > http://www.linkedin.com/in/rjeffreyvincent > I ♥ DropBox <http://db.tt/9O6LfBX> !! > > -- Jeff Vincent [email protected] See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox <http://db.tt/9O6LfBX> !!
