You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Christian Rigdon (JIRA)" <ji...@codehaus.org> on 2008/08/06 00:39:26 UTC
[jira] Created: (MRM-901) Repository groups does not display groups
that have the same groupId
Repository groups does not display groups that have the same groupId
--------------------------------------------------------------------
Key: MRM-901
URL: http://jira.codehaus.org/browse/MRM-901
Project: Archiva
Issue Type: Bug
Components: WebDAV interface
Environment: Using apache-archiva-1.1.war in tomcat 6.0.16
Reporter: Christian Rigdon
I have 2 repositories (approved and unapproved) combined into a group (dev). Each repository has only 1 artifact. The repositories both had the default setup for a repository in archiva.
The first artifact (in approved) used:
groupId: org.foo.firstTest
artifactId:aTest
version:1.0
package:org.foo.firstTest
The second artifact (in unapproved) used:
groupId: org.foo.secondTest
artifactId: anotherTest
version: 1.0
package:org.foo.secondTest
When I looked at http://localhost:8080/archiva/repository/approved I could see the first artifact. When I looked at http://ocalhost:8080/archiva/repository/unapproved I could see the second artifact. However when I looked at the repository group (http://localhost:8080/archiva/repository/dev) I could only see the first artifact and not the second artifact. If I removed the approved from the group I could then see the second artifact, but obviously not the first artifact. It appears that if there are common groupIds in different repositores that are grouped together, then they aren't displayed in the group.
I have seen this effect on other servers with different named repositories in addition to the sample test.
--
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] Commented: (MRM-901) Repository groups does not display
groups that have the same groupId
Posted by "Gilles Bernaerts (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146969#action_146969 ]
Gilles Bernaerts commented on MRM-901:
--------------------------------------
I have this very same problem. It appears that for each directory the repository group hosts the content of the directory in the first grouped repository in declaration order instead of the union of those directories (with declaration order precedence in case of clashes at artefact level). This means that changing the order of repositories will completely change the hosted files by the group.
> Repository groups does not display groups that have the same groupId
> --------------------------------------------------------------------
>
> Key: MRM-901
> URL: http://jira.codehaus.org/browse/MRM-901
> Project: Archiva
> Issue Type: Bug
> Components: WebDAV interface
> Affects Versions: 1.1
> Environment: Using apache-archiva-1.1.war in tomcat 6.0.16
> Reporter: Christian Rigdon
> Fix For: 1.1.x
>
>
> I have 2 repositories (approved and unapproved) combined into a group (dev). Each repository has only 1 artifact. The repositories both had the default setup for a repository in archiva.
> The first artifact (in approved) used:
> groupId: org.foo.firstTest
> artifactId:aTest
> version:1.0
> package:org.foo.firstTest
> The second artifact (in unapproved) used:
> groupId: org.foo.secondTest
> artifactId: anotherTest
> version: 1.0
> package:org.foo.secondTest
> When I looked at http://localhost:8080/archiva/repository/approved I could see the first artifact. When I looked at http://ocalhost:8080/archiva/repository/unapproved I could see the second artifact. However when I looked at the repository group (http://localhost:8080/archiva/repository/dev) I could only see the first artifact and not the second artifact. If I removed the approved from the group I could then see the second artifact, but obviously not the first artifact. It appears that if there are common groupIds in different repositores that are grouped together, then they aren't displayed in the group.
> I have seen this effect on other servers with different named repositories in addition to the sample test.
--
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-901) Repository groups does not display groups
that have the same groupId
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-901:
---------------------------------
Affects Version/s: 1.1
Fix Version/s: 1.1.x
> Repository groups does not display groups that have the same groupId
> --------------------------------------------------------------------
>
> Key: MRM-901
> URL: http://jira.codehaus.org/browse/MRM-901
> Project: Archiva
> Issue Type: Bug
> Components: WebDAV interface
> Affects Versions: 1.1
> Environment: Using apache-archiva-1.1.war in tomcat 6.0.16
> Reporter: Christian Rigdon
> Fix For: 1.1.x
>
>
> I have 2 repositories (approved and unapproved) combined into a group (dev). Each repository has only 1 artifact. The repositories both had the default setup for a repository in archiva.
> The first artifact (in approved) used:
> groupId: org.foo.firstTest
> artifactId:aTest
> version:1.0
> package:org.foo.firstTest
> The second artifact (in unapproved) used:
> groupId: org.foo.secondTest
> artifactId: anotherTest
> version: 1.0
> package:org.foo.secondTest
> When I looked at http://localhost:8080/archiva/repository/approved I could see the first artifact. When I looked at http://ocalhost:8080/archiva/repository/unapproved I could see the second artifact. However when I looked at the repository group (http://localhost:8080/archiva/repository/dev) I could only see the first artifact and not the second artifact. If I removed the approved from the group I could then see the second artifact, but obviously not the first artifact. It appears that if there are common groupIds in different repositores that are grouped together, then they aren't displayed in the group.
> I have seen this effect on other servers with different named repositories in addition to the sample test.
--
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