On Wed, Feb 29, 2012 at 7:12 AM, Wayne Fay <[email protected]> wrote: >> From the looks of the documentation, this was by design. Doesn't mean it >> wasn't a bad design. ;-) > ... >> remote represents the >> http://repo1.maven.org/maven2/archetype-catalog.xml catalog file. > > Well sure, but when you tell Maven that you are offline, it should > respect that and not attempt to resolve any remote catalogs, right?
I had a slightly tangential problem. In the maven-eclipse-plugin code had been contributed to download remote links. But it was just using URL connection, so it didn't use any of the proxy stuff already setup in Maven. >From what I can tell there is no "One Way(tm)" of doing network access, which is why respecting the offline parameter is left up to each plugin. I guess one way to enforce this would be to install a security manager, and only allow the "One Way" access to network resources. But as noted before, no one has really bothered to do that. Mainly because installing a local repository manager is a much cheaper and easier way to work offline. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
