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 Domsch (JIRA)" <ji...@codehaus.org> on 2008/03/04 04:19:29 UTC

[jira] Created: (MRM-727) Archiva does not download plugin artifacts

Archiva does not download plugin artifacts
------------------------------------------

                 Key: MRM-727
                 URL: http://jira.codehaus.org/browse/MRM-727
             Project: Archiva
          Issue Type: Bug
    Affects Versions: 1.0.1
         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
            Reporter: Christian Domsch
         Attachments: settings-wrong.xml

When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.

When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.

>From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Commented: (MRM-727) Archiva does not download plugin artifacts

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126686 ] 

Maria Odea Ching commented on MRM-727:
--------------------------------------

The workaround specified here https://issues.apache.org/jira/browse/GERONIMO-3894 solves this issue :-) Just need to hide the jaxen jar.

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Commented: (MRM-727) Archiva does not download plugin artifacts

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126680 ] 

Maria Odea Ching commented on MRM-727:
--------------------------------------

I also found this in the geronimo logs.. 

14:32:33,558 ERROR [[RepositoryServlet]] Servlet.service() for servlet RepositoryServlet threw exception
org.dom4j.InvalidXPathException: Invalid XPath expression: '//metadata/groupId'. Caused by: org/dom4j/Element
	at org.dom4j.xpath.DefaultXPath.parse(DefaultXPath.java:362)
	at org.dom4j.xpath.DefaultXPath.<init>(DefaultXPath.java:59)
	at org.dom4j.DocumentFactory.createXPath(DocumentFactory.java:230)
	at org.dom4j.tree.AbstractNode.createXPath(AbstractNode.java:207)
	at org.apache.maven.archiva.xml.XMLReader.createXPath(XMLReader.java:175)
	at org.apache.maven.archiva.xml.XMLReader.getElementText(XMLReader.java:258)
	at org.apache.maven.archiva.repository.metadata.RepositoryMetadataReader.read(RepositoryMetadataReader.java:56)
	at org.apache.maven.archiva.repository.metadata.MetadataTools.readProxyMetadata(MetadataTools.java:360)
	at org.apache.maven.archiva.repository.metadata.MetadataTools.updateMetadata(MetadataTools.java:435)
	at org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:367)
	at org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchMetadataFromProxies(ProxiedDavServer.java:405)
	at org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFromProxies(ProxiedDavServer.java:343)
	at org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:189)
	at org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:119)
	at org.apache.maven.archiva.web.repository.RepositoryServlet.service(RepositoryServlet.java:155)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
	at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
	at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:353)
	at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	at java.lang.Thread.run(Thread.java:595)

Is this the one you've mentioned above Christian?



> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Commented: (MRM-727) Archiva does not download plugin artifacts

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126674 ] 

Maria Odea Ching commented on MRM-727:
--------------------------------------

Christian, I think the dom4j problem is a different one. I got those errors from the geronimo logs as well (see below), but not from proxying but during the repo scanning.. 

...
11:00:07,819 ERROR [DatabaseUnprocessedArtifactConsumer:update-db-project] Unable to process model /home/deng/TestFiles/internal/org/codehaus/plexus/plexus-utils/1.0.4/plexus-utils-1.0.4.pom due to : org.dom4j.InvalidXPathException : Invalid XPath expression: '//project'. Caused by: org/dom4j/Element
org.dom4j.InvalidXPathException: Invalid XPath expression: '//project'. Caused by: org/dom4j/Element
        at org.dom4j.xpath.DefaultXPath.parse(DefaultXPath.java:362)
        at org.dom4j.xpath.DefaultXPath.<init>(DefaultXPath.java:59)
        at org.dom4j.DocumentFactory.createXPath(DocumentFactory.java:230)
        at org.dom4j.tree.AbstractNode.createXPath(AbstractNode.java:207)
        at org.apache.maven.archiva.xml.XMLReader.createXPath(XMLReader.java:175)
        at org.apache.maven.archiva.xml.XMLReader.getElement(XMLReader.java:152)
        at org.apache.maven.archiva.repository.project.readers.ProjectModel400Reader.read(ProjectModel400Reader.java:80)
        at org.apache.maven.archiva.consumers.database.ProjectModelToDatabaseConsumer.processArchivaArtifact(ProjectModelToDatabaseConsumer.java:151)
        at org.apache.maven.archiva.database.updater.ProcessArchivaArtifactClosure.execute(ProcessArchivaArtifactClosure.java:52)
        at org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388)
        at org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateUnprocessed(JdoDatabaseUpdater.java:152)
        at org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateAllUnprocessed(JdoDatabaseUpdater.java:86)
        at org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor.executeTask(ArchivaDatabaseUpdateTaskExecutor.java:68)
        at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
        at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
        at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
        at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
        at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
        at java.lang.Thread.run(Thread.java:595)
...


> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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-727) Archiva does not download plugin artifacts

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-727:
---------------------------------

    Fix Version/s: 1.0.2

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>             Fix For: 1.0.2
>
>         Attachments: settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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-727) Archiva does not download plugin artifacts

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-727:
---------------------------------

    Attachment: MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Commented: (MRM-727) Archiva does not download plugin artifacts

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126687 ] 

Maria Odea Ching commented on MRM-727:
--------------------------------------

Could you try it Christian and see if it works for you? 
Thanks..

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Commented: (MRM-727) Archiva does not download plugin artifacts

Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126412 ] 

James William Dumay commented on MRM-727:
-----------------------------------------

Christian, are you able to reproduce this again and attach your log?

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Assigned: (MRM-727) Archiva does not download plugin artifacts

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching reassigned MRM-727:
------------------------------------

    Assignee: Maria Odea Ching

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Commented: (MRM-727) Archiva does not download plugin artifacts

Posted by "Christian Domsch (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126215 ] 

Christian Domsch commented on MRM-727:
--------------------------------------

As far as I found out, part of the problem seems to be a classloading issue with geronimo. I found out, that when the DefaultRepositoryProxyConnector finished with downloading the maven-metadata-central.xml, it tries to merge it with a possible existing maven-metadata.xml. In this process, the previously downloaded xml is read with a RepositoryMetadataReader, that uses dom4j internally with xpath expressions. This process throws a NoDefClassFoundError while it tries to load org.dom4j.Element. By googling this issue, I found this link:

http://mail-archives.apache.org/mod_mbox/geronimo-user/200705.mbox/%3Ce9f11b850705311735q5e050503s6c29d6c9b968a4e9@mail.gmail.com%3E

I have no clue, what the real problem is in detail, nor how to solve it.

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Commented: (MRM-727) Archiva does not download plugin artifacts

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126673 ] 

Maria Odea Ching commented on MRM-727:
--------------------------------------

Hi James, I was able to reproduce the plugin download problem in Geronimo. The metadata xml files are all incorrect for the plugins. I've attached the logs and the metadata files.

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Work started: (MRM-727) Archiva does not download plugin artifacts

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on MRM-727 started by Maria Odea Ching.

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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-727) Archiva does not download plugin artifacts

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-727:
-----------------------------

    Fix Version/s:     (was: 1.0.2)
                   1.0.x

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.x
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Commented: (MRM-727) Archiva does not download plugin artifacts

Posted by "Christian Domsch (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126015 ] 

Christian Domsch commented on MRM-727:
--------------------------------------

I debugged through archiva and found out, that one reason for this bug, is that in DefaultRepositoryProxyConnectors in line 405 the filename for the local repo file gets renamed from maven-metadata.xml to maven-metadata-central.xml. This causes a problem later on, when this file is accessed because 1. the file never gets found by maven and 2. if you try to access it directly ProxiedDavServer fails to recognize it as a metadata file because the check in line 341 compares it to the string "maven-metadata.xml" and fails.

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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-727) Archiva does not download plugin artifacts

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-727:
---------------------------------

    Attachment: maven-resources-plugin-maven-metadata-central.xml

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Closed: (MRM-727) Archiva does not download plugin artifacts in Geronimo

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching closed MRM-727.
--------------------------------

    Resolution: Fixed

> Archiva does not download plugin artifacts in Geronimo
> ------------------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.x
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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-727) Archiva does not download plugin artifacts

Posted by "Christian Domsch (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Domsch updated MRM-727:
---------------------------------

    Attachment: MRM727.diff

This patches the problem with the metadata naming on the server.

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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-727) Archiva does not download plugin artifacts in Geronimo

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-727:
-----------------------------

    Summary: Archiva does not download plugin artifacts in Geronimo  (was: Archiva does not download plugin artifacts)

> Archiva does not download plugin artifacts in Geronimo
> ------------------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.x
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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-727) Archiva does not download plugin artifacts in Geronimo

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-727:
-----------------------------

    Fix Version/s:     (was: 1.0.x)
                   1.0.2

> Archiva does not download plugin artifacts in Geronimo
> ------------------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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-727) Archiva does not download plugin artifacts

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-727:
---------------------------------

    Attachment: MRM-727-build-stack-trace.txt

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: MRM-727-build-stack-trace.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Commented: (MRM-727) Archiva does not download plugin artifacts

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126106 ] 

Maria Odea Ching commented on MRM-727:
--------------------------------------

I tried to replicate this in the standalone archiva using the attached settings.xml, and I couldn't replicate the issue. This is my environment:
- maven 2.0.7/maven-2.0.8
- ubuntu 7.04
- jdk 1.5.0_11

I will try deploying Archiva to Geronimo..

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Commented: (MRM-727) Archiva does not download plugin artifacts

Posted by "Christian Domsch (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126937 ] 

Christian Domsch commented on MRM-727:
--------------------------------------

Thanxs for all the work so far. As I am pretty busy during this week, I dont know if I find the time to test the workaround. But I will try.

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Work stopped: (MRM-727) Archiva does not download plugin artifacts

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on MRM-727 stopped by Maria Odea Ching.

> Archiva does not download plugin artifacts
> ------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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] Commented: (MRM-727) Archiva does not download plugin artifacts in Geronimo

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128633#action_128633 ] 

Maria Odea Ching commented on MRM-727:
--------------------------------------

I made some comments on the instruction on how to deploy to Geronimo in the wiki:

http://cwiki.apache.org/confluence/display/ARCHIVA/Archiva+on+Geronimo-2.0.2+with+MySQL+backend

> Archiva does not download plugin artifacts in Geronimo
> ------------------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.x
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, MRM-727-build-stack-trace.txt, MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, MRM727.diff, settings-wrong.xml
>
>
> When i have an initially blank local maven repo and for example start maven with "mvn clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a 404.
> When I browse the repository file system on the server where archiva stores its files, i see that a maven-metadata-central.xml was stored. the contents of this file are not correct, though.
> From trial and error I found out, that any request to a plugin related maven-metadata.xml file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one for commons-lang) then archiva downloads the correct 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