[jira] Updated: (MRM-620) pom.xml that inherit version from parent show up in reports as "has an invalid project model"
[ http://jira.codehaus.org/browse/MRM-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-620: - Fix Version/s: 1.x > pom.xml that inherit version from parent show up in reports as "has an > invalid project model" > - > > Key: MRM-620 > URL: http://jira.codehaus.org/browse/MRM-620 > Project: Archiva > Issue Type: Bug > Components: reporting >Affects Versions: 1.0 >Reporter: James MacDonald >Priority: Minor > Fix For: 1.x > > > Maven2 allows child modules to inherit the tag from a parent. When > Archiva sees an empty or nonexistent version tag in the uploaded pom.xml, it > thinks that the pom.xml version does not match the artifacts filename, which > is true, but is a completely valid scenario. As far as I can tell, there is > no requirement to have a version tag in a child module of a parent. > Perhaps Archiva should be looking inside the artifact itself under > META-INF/pom.properties to verify the artifacts file name against the > version. There is always a version number inside the artifacts > pom.properties, but not always in the pom.xml. Perhaps a combination of the > pom.xml having a parent tag, and no version information tells Archiva to not > consider this an error. > Here is an example of an error generated in reports: > File workflow-core-common-1.0.1-rc1.pom has an invalid project model > [groupId:com.tomax.infrastructure.foo|artifactId:foo-core-common|version:1.0.1-SNAPSHOT|packaging:null]; > The model version [1.0.1-SNAPSHOT] does not match the version portion of the > filename: 1.0.1-rc1 > I looked at the artifact it complained about, and the pom.xml has not version > tag by design as it is inherited. I don't think this should be an error. > Perhaps Archiva should not produce this error if the version tag does not > exist in the pom.xml and there is a parent tag present? As far as I can > tell, not having a version tag is completely valid in maven2 as long as > parent inheritence provides the version. -- 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-640) breadcrumbs need to incude current doc so you can navigate back to home page
[ http://jira.codehaus.org/browse/MRM-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-640: - Fix Version/s: 1.x > breadcrumbs need to incude current doc so you can navigate back to home page > > > Key: MRM-640 > URL: http://jira.codehaus.org/browse/MRM-640 > Project: Archiva > Issue Type: Bug >Reporter: Brett Porter > Fix For: 1.x > > > the "1.0" should go back to /archiva/docs/1.0, and the "Archiva" should go > back to "/archiva" - and be available any time you are not on that index page. > Including the page title as a non clickable breadcrumb is an option, or > always making the last breadcrumb clickable if it is a different page to that > linked. -- 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-648) Add description field to the different types of repositories and proxies
[ http://jira.codehaus.org/browse/MRM-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-648: - Fix Version/s: 1.x > Add description field to the different types of repositories and proxies > > > Key: MRM-648 > URL: http://jira.codehaus.org/browse/MRM-648 > Project: Archiva > Issue Type: New Feature >Affects Versions: 1.0 >Reporter: Trygve Laugstol > Fix For: 1.x > > > When looking over the repositories page it would be useful to have a > description for each of the repositories configured. Personally I need it to > be able to describe the owner of the repository and indended purpose. -- 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-629) NullPointer when setting corporate POM on a fresh archvia install
[
http://jira.codehaus.org/browse/MRM-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Odea Ching updated MRM-629:
-
Fix Version/s: 1.x
> NullPointer when setting corporate POM on a fresh archvia install
> -
>
> Key: MRM-629
> URL: http://jira.codehaus.org/browse/MRM-629
> Project: Archiva
> Issue Type: Bug
> Components: web application
>Affects Versions: 1.0
> Environment: archiva deployed as a war on tomcat 5.5
>Reporter: nicolas de loof
>Priority: Minor
> Fix For: 1.x
>
>
> Tryning to set a corporate POM fails with a NullPointerException
> The maven-shared-application configuration expect a configuration to exist as
> either org.apache.maven.shared.app.user or org.apache.maven.shared.app.base.
> The first one is declared in archvia application.xml as
> "config-forceCreate="true"", so it SHOULD have been created, but is absent
> from my ${user.home}/.m2
> This may be a plexus-registry-provider bug, or a commons-configuration bug.
--
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-637) get -Pci build working for Archiva again and generate appropriate developer reports and checks
[ http://jira.codehaus.org/browse/MRM-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-637: - Fix Version/s: 1.x > get -Pci build working for Archiva again and generate appropriate developer > reports and checks > -- > > Key: MRM-637 > URL: http://jira.codehaus.org/browse/MRM-637 > Project: Archiva > Issue Type: Bug > Components: build >Affects Versions: 1.0 >Reporter: Brett Porter > Fix For: 1.x > > -- 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-642) archiva-common tests rely on relative paths
[ http://jira.codehaus.org/browse/MRM-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-642: - Fix Version/s: 1.x > archiva-common tests rely on relative paths > --- > > Key: MRM-642 > URL: http://jira.codehaus.org/browse/MRM-642 > Project: Archiva > Issue Type: Bug > Components: build >Affects Versions: 1.0 >Reporter: Brett Porter > Fix For: 1.x > > Attachments: MRM-642.patch > > > it would be good to make these path independent by using getResource* or > similar > other modules are possibly affected - haven't checked. -- 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-638) some developer reports are appearing in the archiva-docs module and need to be disabled
[ http://jira.codehaus.org/browse/MRM-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-638: - Fix Version/s: 1.x > some developer reports are appearing in the archiva-docs module and need to > be disabled > --- > > Key: MRM-638 > URL: http://jira.codehaus.org/browse/MRM-638 > Project: Archiva > Issue Type: Bug > Components: build >Affects Versions: 1.0 >Reporter: Brett Porter > Fix For: 1.x > > > PMD, changelog are appearing - but they belong in the developers section. -- 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-639) "1.0" in the breadcrumbs is incorrectly linked to /docs/1.0/docs/1.0 in the docs subsite
[ http://jira.codehaus.org/browse/MRM-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-639: - Fix Version/s: 1.x > "1.0" in the breadcrumbs is incorrectly linked to /docs/1.0/docs/1.0 in the > docs subsite > > > Key: MRM-639 > URL: http://jira.codehaus.org/browse/MRM-639 > Project: Archiva > Issue Type: Bug > Components: documentation >Affects Versions: 1.0 >Reporter: Brett Porter > Fix For: 1.x > > -- 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-650) Deleted metadata files still appear in search results
[ http://jira.codehaus.org/browse/MRM-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-650: - Fix Version/s: 1.x > Deleted metadata files still appear in search results > - > > Key: MRM-650 > URL: http://jira.codehaus.org/browse/MRM-650 > Project: Archiva > Issue Type: Bug > Components: indexing >Affects Versions: 1.0 >Reporter: Wendy Smoak >Priority: Minor > Fix For: 1.x > > > When an entire directory tree of artifacts is removed from the repository > filesystem, the metadata files still show up in search results. > To reproduce, delete any group from the repository, then click both 'Scan > Repository Now' and 'Update Database Now'. > Search for the artifact again, and note that the metadata files still appear > in the results. > For example, after deleting /path/to/repository/releases/commons-lang and > scanning/updating, this is in the search results for commons-lang: > http://example.com/archiva/repository/releases/commons-lang/commons-lang/maven-metadata.xml -- 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-625) LDAP authentication leaks connections
[ http://jira.codehaus.org/browse/MRM-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-625: - Fix Version/s: 1.x > LDAP authentication leaks connections > - > > Key: MRM-625 > URL: http://jira.codehaus.org/browse/MRM-625 > Project: Archiva > Issue Type: Bug > Components: Users/Security >Affects Versions: 1.0-beta-4 > Environment: Archiva 1.0-beta-4, OpenLdap >Reporter: Emilio Jose Mena Cebrian >Priority: Minor > Fix For: 1.x > > > I've configured redback to authenticate from a LDAP with cached used manager > and I've detected it's leaking connections. > Connections from web interface seem to be returned to LdapContext pool , > but connection from repository servlet are leaked. > The LdapCtx Configuration is : > > > org.codehaus.plexus.redback.common.ldap.connection.LdapConnectionFactory > configurable > > org.codehaus.plexus.redback.common.ldap.connection.ConfigurableLdapConnectionFactory > > > localhost > 389 > > com.sun.jndi.ldap.LdapCtxFactory > *** > > > > com.sun.jndi.ldap.connect.pool > true > > > com.sun.jndi.ldap.connect.pool.maxsize > 20 > > > com.sun.jndi.ldap.connect.pool.prefsize > 10 > > > com.sun.jndi.ldap.connect.pool.timeout > 3 > > > > > NOTE: sensible configuration tags are correctly configured, but i'm erased > them (marked with *) -- 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-644) org.jvnet.jaxb2.maven2:maven-jaxb2-plugin is not resolved correctly using Archiva as mirror
[ http://jira.codehaus.org/browse/MRM-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-644: - Fix Version/s: 1.x > org.jvnet.jaxb2.maven2:maven-jaxb2-plugin is not resolved correctly using > Archiva as mirror > --- > > Key: MRM-644 > URL: http://jira.codehaus.org/browse/MRM-644 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0 > Environment: Maven version: 2.0.8 > Java version: 1.6.0_03 > OS name: "linux" version: "2.6.22-14-generic" arch: "i386" Family: "unix" >Reporter: Henrik Schmidt > Fix For: 1.x > > Attachments: myproject.pom.xml, schema.xsd, settings.xml > > > org.jvnet.jaxb2.maven2:maven-jaxb2-plugin is not resolved correctly with > tag omitted in pom.xml. Omitting the tag works if Archiva > is not used (Maven will just get the latest version). > Steps to reproduce: > Archiva application: > Unpack and run archiva > $ tar zxvf apache-archiva-1.0-bin.tar.gz > $ apache-archiva-1.0/bin/linux-x86-32/run.sh start > Navigate to http://localhost:8080/archiva > create Admin user and login > In Repositories (under Administration): > Add remote Maven 1 legacy repository > Identifier: maven-repository.dev.java.net > Name: Java.net Maven 1 Repository (legacy) > URL:http://download.java.net/maven/1 > Type: Maven 1.x Repository > Add remote Maven 2 jfrog-plugins repository > Identifier: jfrog-plugins > Name: jFrog plugins > URL:http://www.jfrog.org/artifactory/plugins-releases > Type: Maven 2.x repository > In Proxy Connectors (under Administration) > Edit maven2-repository.dev.java.net proxy connector > Remove "jaxax/**" whitelist constraint and click Save Proxy Connector > Add Proxy Connectors > Managed Repository: internal > Remote Repository: maven-repository.dev.java.net > cache-failures: yes > releases: once > checksum: fix > snapshots: never > Managed Repository: internal > Remote Repository: jfrog-plugins > cache-failures: yes > releases: once > checksum: fix > snapshots: never > Client side: > Copy settings.xml to ~/.m2 > $ cp settings.xml ~/.m2 > Create sample project > $ mvn archetype:create -DgroupId=some.namespace -DartifactId=myproject > Overwrite pom.xml > $ cp myproject.pom.xml myproject/pom.xml > Add sample XML schema > $ mkdir myproject/src/main/resources > $ cp schema.xsd myproject/src/main/resources/ > Run test > $ cd myproject > $ mvn test > This should fail with BUILD ERROR "The plugin > 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin' does not exist or no valid > version could be found" > Workaround: > uncomment tag in pom.xml and run test again > Now mvn test should succeed. -- 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-616) When running on IBM JDK 1.5: java.security.NoSuchProviderException: no such provider: SUN
[ http://jira.codehaus.org/browse/MRM-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-616: - Fix Version/s: 1.x > When running on IBM JDK 1.5: java.security.NoSuchProviderException: no such > provider: SUN > -- > > Key: MRM-616 > URL: http://jira.codehaus.org/browse/MRM-616 > Project: Archiva > Issue Type: Bug > Components: Users/Security >Affects Versions: 1.0 > Environment: Win32 > IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 > j9vmwi3223-20070426 (JIT enabled) >Reporter: Arne Degenring >Priority: Minor > Fix For: 1.x > > > When running Archiva 1.0 on an IBM JDK, the following exception occurs. > (Notice that IBM JDK must be used for running WebSphere.) > jvm 1| 2007-12-04 11:29:28,478 [SocketListener0-1] WARN > org.codehaus.plexus.redback.keys.KeyManager:jdo - Unable t > o use SecureRandom > jvm 1| java.security.NoSuchProviderException: no such provider: SUN > jvm 1| at > sun.security.jca.GetInstance.getService(GetInstance.java:82) > jvm 1| at > sun.security.jca.GetInstance.getInstance(GetInstance.java:206) > jvm 1| at > java.security.SecureRandom.getInstance(SecureRandom.java:310) > jvm 1| at > org.codehaus.plexus.redback.keys.AbstractKeyManager.generateUUID(AbstractKeyManager.java:67) > jvm 1| at > org.codehaus.plexus.redback.keys.jdo.JdoKeyManager.createKey(JdoKeyManager.java:61) > jvm 1| at > org.codehaus.plexus.redback.keys.cached.CachedKeyManager.createKey(CachedKeyManager.java:64) > jvm 1| at > org.codehaus.plexus.redback.xwork.util.AutoLoginCookies.setSignonCookie(AutoLoginCookies.java:144) > jvm 1| at > org.codehaus.plexus.redback.xwork.action.LoginAction.webLogin(LoginAction.java:350) > jvm 1| at > org.codehaus.plexus.redback.xwork.action.LoginAction.login(LoginAction.java:136) > jvm 1| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > jvm 1| at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) > jvm 1| at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > jvm 1| at java.lang.reflect.Method.invoke(Method.java:615) > jvm 1| at > com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:358) > jvm 1| at > com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218) > jvm 1| at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:192) > jvm 1| at > org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionIntercept > or.java:114) > jvm 1| at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) > jvm 1| at > org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcemen > tInterceptor.java:105) > jvm 1| at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) > jvm 1| at > org.codehaus.plexus.redback.xwork.interceptor.AutoLoginInterceptor.intercept(AutoLoginInterceptor.jav > a:156) > jvm 1| at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) > jvm 1| at > org.codehaus.plexus.redback.xwork.interceptor.ForceAdminUserInterceptor.intercept(ForceAdminUserInter > ceptor.java:76) > jvm 1| at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) > jvm 1| at > org.codehaus.plexus.redback.xwork.interceptor.EnvironmentCheckInterceptor.intercept(EnvironmentCheckI > nterceptor.java:122) > jvm 1| at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) > jvm 1| at > com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor. > java:175) > jvm 1| at > com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) > jvm 1| at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) > jvm 1| at > com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115) > jvm 1| at > com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) > jvm 1| at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) > jvm 1| at > com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) > jvm 1|
[jira] Updated: (MRM-604) Company POM - Allow a different version than 1 to be entered.
[ http://jira.codehaus.org/browse/MRM-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-604: - Fix Version/s: 1.x > Company POM - Allow a different version than 1 to be entered. > - > > Key: MRM-604 > URL: http://jira.codehaus.org/browse/MRM-604 > Project: Archiva > Issue Type: Improvement > Components: web application >Affects Versions: 1.0-alpha-2 > Environment: All. >Reporter: Parag Mehta >Priority: Minor > Fix For: 1.x > > > Company POM always takes version 1, a different version cannot be > used/entered via GUI. Allow version to be specified along with existing > group and artifact ids. Thanks. -- 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-656) Admin guide for installing WAR needs updating
[ http://jira.codehaus.org/browse/MRM-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-656: - Fix Version/s: 1.x > Admin guide for installing WAR needs updating > - > > Key: MRM-656 > URL: http://jira.codehaus.org/browse/MRM-656 > Project: Archiva > Issue Type: Improvement > Components: reporting >Affects Versions: 1.0 > Environment: N/a >Reporter: Koryn Grant > Fix For: 1.x > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > The web page at > "http://maven.apache.org/archiva/docs/1.0/adminguide/webapp.html"; needs > updating: > * The name of the archiva WAR file in the archiva.xml sample should be > "apache-archiva-1.0.war". > * For the note about Tomcat versions: Tomcat 5.5.25 works as expected, > provided mail.jar and activation.jar are added to the common/lib directory. > * For the note about Derby: Derby 10.3.2.1 seems to work fine. -- 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-631) network proxy is always used when defined
[ http://jira.codehaus.org/browse/MRM-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-631: - Fix Version/s: 1.x > network proxy is always used when defined > - > > Key: MRM-631 > URL: http://jira.codehaus.org/browse/MRM-631 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0 > Environment: Linux and Windows with JRE 1.5 >Reporter: Jacques REYNARD > Fix For: 1.x > > Attachments: archiva.xml > > > I've installed Archiva 1.0 as a Maven proxy repository for internet and > corporate repositories. > I've added the remote Internet Repositories, the network proxy and the proxy > connectors. > It works well for the internet repositories but when Archiva tries to connect > to the corporate repository in the same subnetwork, Archiva uses > the network proxy despite the proxy connector is set to Direct Connection. > If no proxy connectors is defined, Archiva didn't try to get data form the > corporate repository. > If no network proxy is defined, Archiva can contact the corporate repository > but not the Internet ones. > I've done a test with network capture (wireshark ex ethereal) to confirm the > network proxy defined is used. And the result confirm my opinion, the proxy > is used. > I attach the archiva.xml configuration file in order to check it. > The corporate repository is localrepo and is available in http form the > archiva server using lynx, wget and telnet. > Thanks for your help -- 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-654) Archetype for generation of Consumer plugins
[ http://jira.codehaus.org/browse/MRM-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-654: - Fix Version/s: 1.1 > Archetype for generation of Consumer plugins > > > Key: MRM-654 > URL: http://jira.codehaus.org/browse/MRM-654 > Project: Archiva > Issue Type: Improvement > Components: repository scanning >Affects Versions: 1.1 >Reporter: Stephen Gargan >Priority: Trivial > Fix For: 1.1 > > Attachments: archiva-consumer-plugin-archetype.patch > > > I've created an archetype for use in creating artifact-consumer-plugin > projects. It currently builds and runs against the head version of archiva. > - Apply the attached patch in the archiva sandbox dir. > - Build and install it > - invoke with the following command line > mvn archetype:create \ > -DarchetypeGroupId=org.apache.maven.archiva\ > -DarchetypeArtifactId=archiva-consumer-plugin-archetype \ > -DarchetypeVersion=1.1-SNAPSHOT \ > -DgroupId=org.example \ > -DartifactId=simple-consumer-plugin > This will create a project 'simple-consumer-plugin' > rgds, > ste -- 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-641) mvn cobertura:cobertura does not work with Archiva repository set as mirror
[ http://jira.codehaus.org/browse/MRM-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-641: - Fix Version/s: 1.x > mvn cobertura:cobertura does not work with Archiva repository set as mirror > --- > > Key: MRM-641 > URL: http://jira.codehaus.org/browse/MRM-641 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0 > Environment: Archiva is running on a Tomcat 6.0.14 with default setup. > I've also tried it on a Tomcat 5.5.25 with the same result. >Reporter: Henrik Schmidt > Fix For: 1.x > > Attachments: output1.log, output2.log, settings.xml > > > mvn cobertura:cobertura does not work with Archiva repository set as mirror. > $ mvn cobertura:cobertura > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'cobertura'. > [INFO] org.apache.maven.plugins: checking for updates from central > [INFO] org.codehaus.mojo: checking for updates from central > [INFO] artifact org.apache.maven.plugins:maven-cobertura-plugin: checking for > updates from central > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-cobertura-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Thu Dec 20 16:19:17 GMT 2007 > [INFO] Final Memory: 1M/4M > [INFO] > -- 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-652) Invalid html links in "webdav" directory browsing
[
http://jira.codehaus.org/browse/MRM-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Odea Ching updated MRM-652:
-
Fix Version/s: 1.x
> Invalid html links in "webdav" directory browsing
> -
>
> Key: MRM-652
> URL: http://jira.codehaus.org/browse/MRM-652
> Project: Archiva
> Issue Type: Bug
> Components: WebDAV interface
>Affects Versions: 1.0
>Reporter: Xavier Hanin
> Fix For: 1.x
>
>
> The html page served by archiva in the "webdav" repository browsing contains
> badly formed a href links. Here is an example of what I get at
> http://localhost:8080/archiva/repository/internal/ant/ant/:
> {code}
>
>
> Collection: /ant/ant/
>
>
> Collection: /ant/ant/
>
> ant/ (Parent)
>
>
> 1.6.2/
> 1.6.5/
> 1.6/
>
>
>
> {code}
> As you can see the a elements referencing the available versions are not
> closed.
--
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-632) Repository Purge Consumer throws Invalid Path to Artifact
[
http://jira.codehaus.org/browse/MRM-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Odea Ching updated MRM-632:
-
Fix Version/s: 1.1
> Repository Purge Consumer throws Invalid Path to Artifact
> -
>
> Key: MRM-632
> URL: http://jira.codehaus.org/browse/MRM-632
> Project: Archiva
> Issue Type: Bug
> Components: repository scanning
>Affects Versions: 1.0
> Environment: Tomcat 6.0.14
> Windows Server 2003
>Reporter: Luke Amdor
> Fix For: 1.1
>
>
> I have the repository purge consumer enabled and configured as {{Repository
> Purge By Days Older Than}} to 0 and {{Repository Purge By Retention Count}}
> set to 3.
> This is with a clean database.
> I have more than 3 versions of org.irene:irene:2.0-SNAPSHOT already uploaded
> into the repository.
> When the repository is scanned:
> {noformat}
> 290870 [pool-2-thread-1] ERROR
> org.apache.maven.archiva.repository.scanner.RepositoryScanner:default -
> Consumer [repository-purge] had an error when processing file
> [D:\archiva-web\data\repositories\snapshots\org\irene\irene\2.0-SNAPSHOT\irene-2.0-20071214.204316-1-test-sources.jar]:
> Invalid path to Artifact: filename format is invalid,expected timestamp
> format in filename.
> org.apache.maven.archiva.consumers.ConsumerException: Invalid path to
> Artifact: filename format is invalid,expected timestamp format in filename.
> at
> org.apache.maven.archiva.consumers.core.repository.RepositoryPurgeConsumer.processFile(RepositoryPurgeConsumer.java:189)
> at
> org.apache.maven.archiva.repository.scanner.functors.ConsumerProcessFileClosure.execute(ConsumerProcessFileClosure.java:57)
> at
> org.apache.commons.collections.functors.IfClosure.execute(IfClosure.java:117)
> at
> org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388)
> at
> org.apache.maven.archiva.repository.scanner.RepositoryScannerInstance.directoryWalkStep(RepositoryScannerInstance.java:138)
> at
> org.codehaus.plexus.util.DirectoryWalker.fireStep(DirectoryWalker.java:173)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:391)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:385)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:385)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:385)
> at
> org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:385)
> at
> org.codehaus.plexus.util.DirectoryWalker.scan(DirectoryWalker.java:344)
> at
> org.apache.maven.archiva.repository.scanner.DefaultRepositoryScanner.scan(DefaultRepositoryScanner.java:120)
> at
> org.apache.maven.archiva.repository.scanner.DefaultRepositoryScanner.scan(DefaultRepositoryScanner.java:64)
> at
> org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor.executeTask(ArchivaRepositoryScanningTaskExecutor.java:106)
> 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.runWorker(ThreadPoolExecutor.java:987)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
> at java.lang.Thread.run(Thread.java:595)
> Caused by:
> org.apache.maven.archiva.consumers.core.repository.RepositoryPurgeException:
> Invalid path to Artifact: filename format is invalid,expected timestamp
> format in filename.
> at
> org.apache.maven.archiva.consumers.core.repository.RetentionCountRepositoryPurge.process(RetentionCountRepositoryPurge.java:102)
> at
> org.apache.maven.archiva.consumers.core.repository.RepositoryPurgeConsumer.processFile(RepositoryPurgeConsumer.java:185)
> ... 20 more
> 290885 [pool-2-thread-1] ERROR
> org.apache.maven.archiva.repository.scanner.RepositoryScanner:default -
> Consumer [metadata-updater] had an error when processing file
> [D:\archiva-web\data\repositories\snapshots\org\irene\irene\2.0-SNAPSHOT\irene-2.0-20071214.204316-1-test-sources.jar]:
> Unable to convert to artifact reference:
> org\irene\irene\2.0-SNAPSHOT\irene-2.0-20071214.204316-1-test-sources.jar
> org.apache.maven.archiva.consumers.ConsumerException: Unable to convert to
> artifact reference:
> org\irene\irene\2.0-SNAPSHOT\irene-2.0-20071214.204316-1-test-sources.jar
> at
> org.apache.maven.archiva.consumers.core.MetadataUpdaterConsumer.
[jira] Updated: (MRM-657) 'ORA-00910: specified length too long for its datatype' Error when clicking on searched artifact.
[ http://jira.codehaus.org/browse/MRM-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-657: - Fix Version/s: 1.1 > 'ORA-00910: specified length too long for its datatype' Error when clicking > on searched artifact. > - > > Key: MRM-657 > URL: http://jira.codehaus.org/browse/MRM-657 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0 > Environment: Oracle 10g 10.2.0.3.0 on Sun Solaris Sparc 64 >Reporter: Mick Knutson > Fix For: 1.1 > > > When I do a search for an artifact, then I get the results, I then get this > error: > javax.jdo.JDODataStoreException: An exception was thrown while > adding/validating class(es) : ORA-00910: specified length too long for its > datatype > java.sql.SQLException: ORA-00910: specified length too long for its datatype > at > oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:158) > at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316) > at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:282) > at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:639) > at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:113) > at > oracle.jdbc.driver.T4CStatement.execute_for_rows(T4CStatement.java:703) > at > oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1196) > at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1804) > at > org.apache.tomcat.dbcp.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264) > at > org.jpox.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:614) > at > org.jpox.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:570) > at > org.jpox.store.rdbms.table.AbstractTable.create(AbstractTable.java:297) > at > org.jpox.store.rdbms.table.AbstractTable.exists(AbstractTable.java:341) > at > org.jpox.store.rdbms.RDBMSManager$ClassAdder.performTablesValidation(RDBMSManager.java:3052) > at > org.jpox.store.rdbms.RDBMSManager$ClassAdder.addClassTablesAndValidate(RDBMSManager.java:3313) > at > org.jpox.store.rdbms.RDBMSManager$ClassAdder.run(RDBMSManager.java:2554) > at > org.jpox.store.rdbms.RDBMSManager$MgmtTransaction.execute(RDBMSManager.java:2406) > at org.jpox.store.rdbms.RDBMSManager.addClasses(RDBMSManager.java:821) > at org.jpox.store.rdbms.RDBMSManager.addClass(RDBMSManager.java:835) > at > org.jpox.AbstractPersistenceManager.newObjectIdInstance(AbstractPersistenceManager.java:2377) > at > org.apache.maven.archiva.database.jdo.JdoAccess.getObjectById(JdoAccess.java:429) > at > org.apache.maven.archiva.database.jdo.JdoProjectModelDAO.getProjectModel(JdoProjectModelDAO.java:74) > at > org.apache.maven.archiva.database.browsing.DefaultRepositoryBrowsing.getProjectModel(DefaultRepositoryBrowsing.java:281) > at > org.apache.maven.archiva.database.browsing.DefaultRepositoryBrowsing.selectVersion(DefaultRepositoryBrowsing.java:127) > at > org.apache.maven.archiva.web.action.ShowArtifactAction.artifact(ShowArtifactAction.java:105) > Now this does not come up like with continuum (at start up): > http://jira.codehaus.org/browse/CONTINUUM-1622 > So Archiva runs, but not when I try to search. -- 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-658) org.apache.maven.archiva.repository.content.FilenameParser is unable to determine unique snapshot versions with specific version names
[ http://jira.codehaus.org/browse/MRM-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-658: - Fix Version/s: 1.1 > org.apache.maven.archiva.repository.content.FilenameParser is unable to > determine unique snapshot versions with specific version names > -- > > Key: MRM-658 > URL: http://jira.codehaus.org/browse/MRM-658 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0 > Environment: windows, maven2 >Reporter: Markus Nolte > Fix For: 1.1 > > Attachments: unit_test.snippet > > > After deploying an artifact with version trunk-SNAPSHOT with unique version > set to true, I am not able to download the artifact anymore. The reason is > the org.apache.maven.archiva.repository.content.DefaultPathParser throwing a > LayoutException "filename format is invalid, expected timestamp format in > filename". > The problem is the determination of an unique snapshot in the given file path > using the FilenameParser.nextVersion method that uses VersionUtil.isVersion > to determine if the parsed section of a given filename is part of a version > or not. > The VersionUtil uses a VersionMegaPattern to identify version parts in a > string, this does not work on any possible version name. > A quick solution for me was to patch the VersionUtil and add 'trunk' to the > VersionMegaPattern, but a more stable solution should use the already > identified baseVersion (trunk-SNAPSHOT in this case) to determine the version > and timestamp parts in a given or to skip path validity checks. > I added an additional unit test snippet for > org.apache.maven.archiva.repository.content.DefaultPathParserTest to > reproduce the problem -- 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-653) WebDAV deploy fails with error
[ http://jira.codehaus.org/browse/MRM-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-653: - Fix Version/s: 1.1 > WebDAV deploy fails with error > -- > > Key: MRM-653 > URL: http://jira.codehaus.org/browse/MRM-653 > Project: Archiva > Issue Type: Bug > Components: WebDAV interface >Affects Versions: 1.0 > Environment: Linux > Sun's jdk1.6.0_03 > Tomcat 6.0.14 >Reporter: Erik R. Jensen > Fix For: 1.1 > > Attachments: output.txt > > > I was having problems deploying artifacts using the wagon-webdav plugin. I > originally thought it was a client problem with the plugin since no errors > were showing up in the Archiva logs until I did a tcpdump and found the > exception sent from the Archiva server. I assumed all errors in Archiva would > output a stack trace in the logs, but apparently this is not always the case. > I've attached the HTTP session information showing the stack trace. -- 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
