What JIRA number was this request Nico? And what happened to it?
Wayne On 12/12/06, nicolas de loof <[EMAIL PROTECTED]> wrote:
I had the same issue, but with another point of view : I expected all artifacts on maven repo to have source jars. I have created a private "sources" repository, and added missing artifacts sources to it. The summer, I have attached my zipped source repository to an upload request to make them available on maven repo. Maintaining such a "source" repository is not a huge work if done by incremental additions. Nico. 2006/12/12, Mark Struberg <[EMAIL PROTECTED]>: > > Hi! > > Our situation: > > We are using maven in our corporate environment, > maintaining our own local artifact and plugin > repository for inhouse stuff. All locally released > artifacts also have attached source artifacts for > debugging purpose in Idea and Eclipse. > > We are using maven-proxy to reduce traffic and load > time for caching a few public repos. > > Now my question: > Since Idea (idea:idea) and Eclipse (eclipse:eclipse, > m2eclipse) always trie to resolve attached source > artifacts, accessing the global repositories (e.g. for > commons-logging) cause many failed downloads. Is there > any way to tell maven-proxy to exclude some files from > a specific repository, or prevent maven from trying to > resolve a specific artifact type from a specific > repos? > > txs in advance, > strub > > > > > > > ___________________________________________________________ > Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: > http://mail.yahoo.de > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]