All- I'm working on a simple patch to not add the statically declared DEFAULT_REPOSITORIES (http://osgi.sonatype.org/content/groups/pax-runner) to the list of repositories used by pax-url-maven as long as a user has defined a repository in the external properties file, or specified maven settings.xml. This hopes to solve 2 issues.
Issue 1. Users using software that uses pax-url-maven behind a proxy will experience weird issues. proxySupport is available as a configuration option, but it isn't well documented. Issue 2. Users cannot "lock down" the list of repositories and dependencies that will be pulled in by pax-url-maven, because there is no way to disable the DEFAULT_REPOSITORIES. I created a JIRA: JIRA: http://issues.ops4j.org/browse/PAXURL-92 I'm planning on having this fix tested and updated this week, but it brings up a bigger question about pax-url-maven configuration and behavior as a whole. I'd be interested in hearing feedback from the community, but here is what I am thinking: Proposal 1. Removal of FALLBACK_REPOSITORIES and DEFAULT_REPOSITORIES. This would clean up and simplify the configuration of pax-url-maven and rely on people shipping products that use pax-url-maven and end-users to have one and only one list of repositories. In my opinion, having the statically defined repositories unnecessarily complicates things. Proposal 2. Auto-detection of proxy support if a proxy is configured and active in a Maven settings.xml file. I can't think of a scenario where a user would configure Maven to use a proxy, and pax-url-maven would not use a proxy on the same box. Feedback greatly appreciated. Thanks, Matt Pavlovich _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
