Unable to proxy https://maven.atlassian.com/repository/public

View: New views
5 Messages — Rating Filter:   Alert me  

Unable to proxy https://maven.atlassian.com/repository/public

by Allan Ditzel :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi all,

We are unable to proxy the public repository that Atlassian has set up. The repository configuration is as followsÑ

Repository type: proxy
Provider: Maven 2
Format: Maven 2
Repository Policy: Releases (although the underlying repo supports both releases and snapshots)
Download Remote Indexes: False (Although have tried true to no effect)
Everything else is defaulted.

This repository has been added to our public group, however we cannot download any resources that are visible by directly going to the atlassian repo via the browser. Does anyone have any ideas of what might be going on here?

Thank you,

Allan

Re: Unable to proxy https://maven.atlassian.com/repository/public

by Brian Fox :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Nexus doesn't currently support consuming the index.html to make a browsable tree of the remote repository. This is something we may add soon. Once you start using artifacts they will be browseable. If the remote repository publishes an index, then you could enable the remote index download and you could browse the index. We don't crawl the remote repositories, hence the index. If we do create the index.html parsing, it would be on demand as you click through the tree just like the browser does, not a full crawl.

2009/6/5 Allan Ditzel <allan.ditzel@...>
Hi all,

We are unable to proxy the public repository that Atlassian has set up. The repository configuration is as followsÑ

Repository type: proxy
Provider: Maven 2
Format: Maven 2
Repository Policy: Releases (although the underlying repo supports both releases and snapshots)
Download Remote Indexes: False (Although have tried true to no effect)
Everything else is defaulted.

This repository has been added to our public group, however we cannot download any resources that are visible by directly going to the atlassian repo via the browser. Does anyone have any ideas of what might be going on here?

Thank you,

Allan


Re: Unable to proxy https://maven.atlassian.com/repository/public

by Allan Ditzel :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

When you say use, do you mean access them in a pom file, or would referencing them from the command line also work? For example, I am trying to execute the following command:
 
 
I receive an error telling me that no catalog was found.
 
Or if I run the following:
 
mvn archetype:create ^
    -DarchetypeGroupId=com.atlassian.maven.archetypes ^
    -DarchetypeArtifactId=jira-plugin-archetype ^
    -DarchetypeVersion=15 ^
    -DremoteRepositories=https://maven.atlassian.com/repository/public/ ^
    -DgroupId=%MY_PACKAGE% -DartifactId=%MY_PLUGIN%

(obviously replacing the %vars% with appropriate values)
 
It tells me that it can't find that archetype. I have the repository configured in nexus and added to the group, but as far as maven seems to be concerned, it can't find what it needs to.
 
Thanks,
 
Allan
On Fri, Jun 5, 2009 at 8:23 PM, Brian Fox <brianf@...> wrote:
Nexus doesn't currently support consuming the index.html to make a browsable tree of the remote repository. This is something we may add soon. Once you start using artifacts they will be browseable. If the remote repository publishes an index, then you could enable the remote index download and you could browse the index. We don't crawl the remote repositories, hence the index. If we do create the index.html parsing, it would be on demand as you click through the tree just like the browser does, not a full crawl.

2009/6/5 Allan Ditzel <allan.ditzel@...>

Hi all,

We are unable to proxy the public repository that Atlassian has set up. The repository configuration is as followsÑ

Repository type: proxy
Provider: Maven 2
Format: Maven 2
Repository Policy: Releases (although the underlying repo supports both releases and snapshots)
Download Remote Indexes: False (Although have tried true to no effect)
Everything else is defaulted.

This repository has been added to our public group, however we cannot download any resources that are visible by directly going to the atlassian repo via the browser. Does anyone have any ideas of what might be going on here?

Thank you,

Allan



Re: Unable to proxy https://maven.atlassian.com/repository/public

by Allan Ditzel :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Also, as an FYI, the Atlassian repo has the following at its root:

https://maven.atlassian.com/repository/public/.index/

This looks to me like a browsable index, but the nexus logs show the following:

2009-06-08 11:23:47 INFO  [ool-1-thread-12] - o.s.n.f.FeedRecorder:default  - Reindexing repository Atlassian Public from path / and below. : Process started on Mon Jun 08 11:23:46 EDT 2009, not yet finished.
2009-06-08 11:23:47 INFO  [ool-1-thread-12] - o.s.n.i.IndexerMana~:default  - Trying to get remote index for repository atlassian-public
2009-06-08 11:23:47 INFO  [ool-1-thread-12] - o.s.n.p.r.Repository:maven2   - Expiring local cache in repository ID='atlassian-public' from path='/.index'
2009-06-08 11:23:47 INFO  [ool-1-thread-12] - o.s.n.p.r.Repository:maven2   - Clearing NFC cache in repository ID='atlassian-public' from path='/.index'
2009-06-08 11:23:47 INFO  [ool-1-thread-12] - o.a.c.h.HttpMethodB~          - Response content length is not known
2009-06-08 11:23:47 WARN  [ool-1-thread-12] - o.s.n.i.IndexerMana~:default  - Cannot fetch remote index:
java.io.FileNotFoundException: nexus-maven-repository-index.properties (item not found)
        at org.sonatype.nexus.index.DefaultIndexerManager$1.retrieve(DefaultIndexerManager.java:714)
        at org.sonatype.nexus.index.updater.DefaultIndexUpdater.downloadIndexProperties(DefaultIndexUpdater.java:402)
        at org.sonatype.nexus.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:82)
        at org.sonatype.nexus.index.DefaultIndexerManager.updateRemoteIndex(DefaultIndexerManager.java:724)
        at org.sonatype.nexus.index.DefaultIndexerManager.updateIndexForRemoteRepository(DefaultIndexerManager.java:596)
        at org.sonatype.nexus.index.DefaultIndexerManager.downloadRepositoryIndex(DefaultIndexerManager.java:563)
        at org.sonatype.nexus.index.DefaultIndexerManager.reindexRepository(DefaultIndexerManager.java:477)
        at org.sonatype.nexus.index.DefaultIndexerManager.reindexRepository(DefaultIndexerManager.java:433)
        at org.sonatype.nexus.DefaultNexus.reindexRepository(DefaultNexus.java:1324)
        at org.sonatype.nexus.tasks.ReindexTask.doRun(ReindexTask.java:40)
        at org.sonatype.nexus.scheduling.AbstractNexusTask.call(AbstractNexusTask.java:139)
        at org.sonatype.scheduling.DefaultScheduledTask.call(DefaultScheduledTask.java:342)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
2009-06-08 11:23:47 INFO  [ool-1-thread-12] - o.s.n.i.IndexerMana~:default  - Cascading merge of group indexes for group 'public', where repository 'atlassian-public' is member.
2009-06-08 11:23:51 INFO  [ool-1-thread-12] - o.s.n.i.IndexerMana~:default  - Publishing best index for repository atlassian-public




On Fri, Jun 5, 2009 at 8:23 PM, Brian Fox <brianf@...> wrote:
Nexus doesn't currently support consuming the index.html to make a browsable tree of the remote repository. This is something we may add soon. Once you start using artifacts they will be browseable. If the remote repository publishes an index, then you could enable the remote index download and you could browse the index. We don't crawl the remote repositories, hence the index. If we do create the index.html parsing, it would be on demand as you click through the tree just like the browser does, not a full crawl.

2009/6/5 Allan Ditzel <allan.ditzel@...>

Hi all,

We are unable to proxy the public repository that Atlassian has set up. The repository configuration is as followsÑ

Repository type: proxy
Provider: Maven 2
Format: Maven 2
Repository Policy: Releases (although the underlying repo supports both releases and snapshots)
Download Remote Indexes: False (Although have tried true to no effect)
Everything else is defaulted.

This repository has been added to our public group, however we cannot download any resources that are visible by directly going to the atlassian repo via the browser. Does anyone have any ideas of what might be going on here?

Thank you,

Allan



Re: Unable to proxy https://maven.atlassian.com/repository/public

by Brian Fox :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Allan,
The Atlassian repo currently runs Archiva, and last I knew, Archiva wasn't producing the indexes in the correct format. They use a newer version of Lucene and an older version of the Indexer which produces indexes that can't be consumed by M2e or Nexus. I suspect that's why the index isn't working correctly.

On Mon, Jun 8, 2009 at 11:25 AM, Allan Ditzel <allan.ditzel@...> wrote:
Also, as an FYI, the Atlassian repo has the following at its root:

https://maven.atlassian.com/repository/public/.index/

This looks to me like a browsable index, but the nexus logs show the following:

2009-06-08 11:23:47 INFO  [ool-1-thread-12] - o.s.n.f.FeedRecorder:default  - Reindexing repository Atlassian Public from path / and below. : Process started on Mon Jun 08 11:23:46 EDT 2009, not yet finished.
2009-06-08 11:23:47 INFO  [ool-1-thread-12] - o.s.n.i.IndexerMana~:default  - Trying to get remote index for repository atlassian-public
2009-06-08 11:23:47 INFO  [ool-1-thread-12] - o.s.n.p.r.Repository:maven2   - Expiring local cache in repository ID='atlassian-public' from path='/.index'
2009-06-08 11:23:47 INFO  [ool-1-thread-12] - o.s.n.p.r.Repository:maven2   - Clearing NFC cache in repository ID='atlassian-public' from path='/.index'
2009-06-08 11:23:47 INFO  [ool-1-thread-12] - o.a.c.h.HttpMethodB~          - Response content length is not known
2009-06-08 11:23:47 WARN  [ool-1-thread-12] - o.s.n.i.IndexerMana~:default  - Cannot fetch remote index:
java.io.FileNotFoundException: nexus-maven-repository-index.properties (item not found)
        at org.sonatype.nexus.index.DefaultIndexerManager$1.retrieve(DefaultIndexerManager.java:714)
        at org.sonatype.nexus.index.updater.DefaultIndexUpdater.downloadIndexProperties(DefaultIndexUpdater.java:402)
        at org.sonatype.nexus.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:82)
        at org.sonatype.nexus.index.DefaultIndexerManager.updateRemoteIndex(DefaultIndexerManager.java:724)
        at org.sonatype.nexus.index.DefaultIndexerManager.updateIndexForRemoteRepository(DefaultIndexerManager.java:596)
        at org.sonatype.nexus.index.DefaultIndexerManager.downloadRepositoryIndex(DefaultIndexerManager.java:563)
        at org.sonatype.nexus.index.DefaultIndexerManager.reindexRepository(DefaultIndexerManager.java:477)
        at org.sonatype.nexus.index.DefaultIndexerManager.reindexRepository(DefaultIndexerManager.java:433)
        at org.sonatype.nexus.DefaultNexus.reindexRepository(DefaultNexus.java:1324)
        at org.sonatype.nexus.tasks.ReindexTask.doRun(ReindexTask.java:40)
        at org.sonatype.nexus.scheduling.AbstractNexusTask.call(AbstractNexusTask.java:139)
        at org.sonatype.scheduling.DefaultScheduledTask.call(DefaultScheduledTask.java:342)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
2009-06-08 11:23:47 INFO  [ool-1-thread-12] - o.s.n.i.IndexerMana~:default  - Cascading merge of group indexes for group 'public', where repository 'atlassian-public' is member.
2009-06-08 11:23:51 INFO  [ool-1-thread-12] - o.s.n.i.IndexerMana~:default  - Publishing best index for repository atlassian-public




On Fri, Jun 5, 2009 at 8:23 PM, Brian Fox <brianf@...> wrote:
Nexus doesn't currently support consuming the index.html to make a browsable tree of the remote repository. This is something we may add soon. Once you start using artifacts they will be browseable. If the remote repository publishes an index, then you could enable the remote index download and you could browse the index. We don't crawl the remote repositories, hence the index. If we do create the index.html parsing, it would be on demand as you click through the tree just like the browser does, not a full crawl.

2009/6/5 Allan Ditzel <allan.ditzel@...>

Hi all,

We are unable to proxy the public repository that Atlassian has set up. The repository configuration is as followsÑ

Repository type: proxy
Provider: Maven 2
Format: Maven 2
Repository Policy: Releases (although the underlying repo supports both releases and snapshots)
Download Remote Indexes: False (Although have tried true to no effect)
Everything else is defaulted.

This repository has been added to our public group, however we cannot download any resources that are visible by directly going to the atlassian repo via the browser. Does anyone have any ideas of what might be going on here?

Thank you,

Allan