[jira] Work stopped: (MRM-727) Archiva does not download plugin artifacts
[ 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-730) Index/Search by class, method or package name
[ http://jira.codehaus.org/browse/MRM-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126781 ] Wendy Smoak commented on MRM-730: - This would be a good thing to add, it comes up on [EMAIL PROTECTED] occasionally. > Index/Search by class, method or package name > - > > Key: MRM-730 > URL: http://jira.codehaus.org/browse/MRM-730 > Project: Archiva > Issue Type: New Feature > Components: indexing >Reporter: Maria Odea Ching > -- 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] Created: (MRM-736) User Rights on Webdav : filePermissions are ignored
User Rights on Webdav : filePermissions are ignored --- Key: MRM-736 URL: http://jira.codehaus.org/browse/MRM-736 Project: Archiva Issue Type: Bug Components: WebDAV interface Affects Versions: 1.0.1 Environment: Linux Reporter: Alexandre Navarro I configure my webdav in my settings.xmll like that snapshots repodeployer repodeployer 444 I can deploy but the user right are ignored. It is problematic for non-snapshot because you can redeploy a released jar. -- 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] Created: (MRM-735) Database on MS SQL 2000/2005 fail to be created due to too column length
Database on MS SQL 2000/2005 fail to be created due to too column length Key: MRM-735 URL: http://jira.codehaus.org/browse/MRM-735 Project: Archiva Issue Type: Bug Components: system Affects Versions: 1.0.1, 1.0 Environment: Win XP Tomcat 5.5 MS SQL 2000 / 2005 MS SQL 2005 JDBC Driver, v1.2 Reporter: Thomas Winkler Some column lengths in the datamodel exceed the restrictions of MS SQL Server using the default String jdbc-mapping of jpox (varchar) These are according to package.jdo: - Table: ARCHIVA_PROJECT -> Columns: description - Table: ARCHIVA_LICENSES -> Columns: comments - Table: ARCHIVA_REPOSITORY_PROBLEMS -> Columns: message The 2005 Jdbc driver uses the nvarchar datatype in case of varchar jdbc types. The maximum length here would be 4000 bytes. Some other db systems should have the same problem, as I could see from their specs, but I'm not an expert (Oracle: 4000 bytes, DB2: 4-32k depending on page size). A possible fix for MS SQL is, not to provide any length. Instead we could use the jdo jdbc-type. I tested it with using the jdbc-type="LONGVARCHAR". Then jpox uses ntext column types for those fields. Unfortunatly, there is no way to define this parameter within modello. -- 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-728) After successful admin login archiva reacts as if user is guest
[ http://jira.codehaus.org/browse/MRM-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126703 ] Robin Roos commented on MRM-728: For reference, I am using Archiva stand-alone (Jetty-based). Arun notes above that he has seen this problem with Tomcat. So it would seem not to be appserver-dependent. I have shown it is not browser-dependent. Could it be OS/JDK-specific? I'm on a 64-bit Linux version using /jdk1.5.0_15. > After successful admin login archiva reacts as if user is guest > --- > > Key: MRM-728 > URL: http://jira.codehaus.org/browse/MRM-728 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0.1 > Environment: linux >Reporter: Robin Roos > Fix For: 1.0.x > > Attachments: archiva.log > > > I ran Archiva on my windows box and, after configuring the admin user, I was > able to login. The header of the web page identified me as Administrator > (admin) and I could see all the expected functions on the left hand frame. > So far so good. > I had Archiva installed on a linux box and started. I surfed to the box from > Windows and configured the admin user. But when I logged in as admin I got a > page with only Search/FindArtifact/Browse functions. The header page reads > "Login - Register". It is as if I am not logged in and am seeing the guest > functions. Note that if I log in with a deliberately incorrect password then > I get an error message as expected. But logging in with the right > credentials appears to fail silently. > As a result I cannot deploy any artifacts into Archiva, I cannot roll out the > maven/subversion/archiva based edition of our in-house project, and I fear my > time is limited! -- 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
[ 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
[ 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
