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
