You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Maik Ebert (JIRA)" <ji...@codehaus.org> on 2008/08/27 09:15:26 UTC
[jira] Created: (MRM-925) Access to maven-metadata.xml without
"groupId" fails when accessed via a repository group
Access to maven-metadata.xml without "groupId" fails when accessed via a repository group
-----------------------------------------------------------------------------------------
Key: MRM-925
URL: http://jira.codehaus.org/browse/MRM-925
Project: Archiva
Issue Type: Bug
Components: browser, WebDAV interface
Affects Versions: 1.1.1
Reporter: Maik Ebert
Attachments: stacktrace.txt
One of our repositories contains the following maven-metadata.xml
{code}
<metadata>
<plugins>
<plugin>
<name>Maven CDM Plugin</name>
<prefix>cdm</prefix>
<artifactId>maven-cdm-plugin</artifactId>
</plugin>
<plugin>
<name>Maven CDM Flex Plugin</name>
<prefix>cdm-flex</prefix>
<artifactId>maven-cdm-flex-plugin</artifactId>
</plugin>
</plugins>
</metadata>
{code}
Notice that there is *no* "groupId" element.
This file will be delivered correctly when it is requested via the URL /archiva/repository/continous-integration/com/icw/cdm/plugins/maven-metadata.xml from the containing repository "continous-integration".
Now I tried to use the new feature of repository groups creating a new group named "overall" containing the repository "continous-integration" and others. None of the other repositories contains the above artifacts.
When Maven or a request from a browser is done to the URL /archiva/repository/overall/com/icw/cdm/plugins/maven-metadata.xml the attached stack trace is shown in the browser.
I searched the source code and at the location RepositoryMetadataWriter.java:77 the following code is executed:
{code}
root.addElement( "groupId" ).setText( metadata.getGroupId() );
{code}
This must fail, because the maven-metadata.xml does *not* contain a "groupId".
How can I use the repository group feature with such a maven-metadata.xml file?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-925) Access to maven-metadata.xml without
"groupId" fails when accessed via a repository group
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-925:
---------------------------------
Fix Version/s: 1.2
> Access to maven-metadata.xml without "groupId" fails when accessed via a repository group
> -----------------------------------------------------------------------------------------
>
> Key: MRM-925
> URL: http://jira.codehaus.org/browse/MRM-925
> Project: Archiva
> Issue Type: Bug
> Components: browser, WebDAV interface
> Affects Versions: 1.1.1
> Reporter: Maik Ebert
> Fix For: 1.2
>
> Attachments: stacktrace.txt
>
>
> One of our repositories contains the following maven-metadata.xml
> {code}
> <metadata>
> <plugins>
> <plugin>
> <name>Maven CDM Plugin</name>
> <prefix>cdm</prefix>
> <artifactId>maven-cdm-plugin</artifactId>
> </plugin>
> <plugin>
> <name>Maven CDM Flex Plugin</name>
> <prefix>cdm-flex</prefix>
> <artifactId>maven-cdm-flex-plugin</artifactId>
> </plugin>
> </plugins>
> </metadata>
> {code}
> Notice that there is *no* "groupId" element.
> This file will be delivered correctly when it is requested via the URL /archiva/repository/continous-integration/com/icw/cdm/plugins/maven-metadata.xml from the containing repository "continous-integration".
> Now I tried to use the new feature of repository groups creating a new group named "overall" containing the repository "continous-integration" and others. None of the other repositories contains the above artifacts.
> When Maven or a request from a browser is done to the URL /archiva/repository/overall/com/icw/cdm/plugins/maven-metadata.xml the attached stack trace is shown in the browser.
> I searched the source code and at the location RepositoryMetadataWriter.java:77 the following code is executed:
> {code}
> root.addElement( "groupId" ).setText( metadata.getGroupId() );
> {code}
> This must fail, because the maven-metadata.xml does *not* contain a "groupId".
> How can I use the repository group feature with such a maven-metadata.xml file?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira