[ 
http://issues.ops4j.org/browse/PAXURL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740#action_13740
 ] 

Matt Pavlovich commented on PAXURL-92:
--------------------------------------

Removed DEFAULT_REPOSITORIES (hard coded, undocumented repo).  The 
PROPERTY_DEFAULT_REPOSITORIES is still in tact.  Unit tests updated, tested 
with ServiceMix 4.3.0-fuse-02-00 without problems.

Git commit
See: 
https://github.com/ops4j/org.ops4j.pax.url/commit/cf43d9aea89ea12f1ea7f7fcfaef172906198fe9

Discussion
See: http://lists.ops4j.org/pipermail/general/2010q4/005001.html

> Do not fallback to static DEFAULT_REPOSITORIES if respositories are configured
> ------------------------------------------------------------------------------
>
>                 Key: PAXURL-92
>                 URL: http://issues.ops4j.org/browse/PAXURL-92
>             Project: Pax URL
>          Issue Type: Improvement
>          Components: mvn
>    Affects Versions: 1.2.1
>         Environment: Windows, Linux
>            Reporter: Matt Pavlovich
>            Assignee: Matt Pavlovich
>             Fix For: 1.2.2
>
>
> The current behavior of pax-url-maven is that the static repository 
> (http://osgi.sonatype.org/content/groups/pax-runner) is appended the list of 
> repositories all the time.  This causes problems when a system using 
> pax-url-maven (such as ServiceMix 4) is running behind a proxy.  Also, the 
> use of this repository is not documented or configurable and it makes it 
> difficult for users to lock down a list of repositories and dependencies used 
> by a program.  
> I'm writing a patch where the DEFAULT_REPOSITORIES constant is not appended 
> to the list if the list of repositories is not empty.  This seems to be the 
> least intrusive way to solve for the above two issues.
> Personally, I think the fallback repositories and default repositories could 
> be removed entirely, since they are masked from the user.  Also, I think the 
> proxy support could be detected automatically if an external maven 
> settings.xml file is specified.  I don't see a use case where a proxy would 
> be used by maven, but not by pax-url-maven when running on the same box.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to