[jira] (MRELEASE-775) IllegalStateException while checking for modifications if multiple exclusion patterns match

Arne Degenring created MRELEASE-775: --- Summary: IllegalStateException while checking for modifications if multiple exclusion patterns match Key: MRELEASE-775 URL: https://jira.codehaus.org/browse/MRELEASE-775

[jira] Created: (MRM-617) Reporting does not work due to bug in client-side JavaScript validation

Reporting does not work due to bug in client-side JavaScript validation --- Key: MRM-617 URL: http://jira.codehaus.org/browse/MRM-617 Project: Archiva Issue Type: Bug

[jira] Created: (MRM-616) When running on IBM JDK 1.5: java.security.NoSuchProviderException: no such provider: SUN

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: A

[jira] Created: (MRM-612) Repository scanning does not recognize newly added artifacts if they have an old timestamp

Repository scanning does not recognize newly added artifacts if they have an old timestamp -- Key: MRM-612 URL: http://jira.codehaus.org/browse/MRM-612 Project: A

[jira] Created: (MRM-608) Unable to find project model for [...] if the initial import of the POM failed

Unable to find project model for [...] if the initial import of the POM failed --- Key: MRM-608 URL: http://jira.codehaus.org/browse/MRM-608 Project: Archiva Issue

[jira] Created: (MRM-579) Restricted access to remote repositories

Restricted access to remote repositories Key: MRM-579 URL: http://jira.codehaus.org/browse/MRM-579 Project: Archiva Issue Type: Wish Components: remote proxy, Users/Security Affects Vers

[jira] Commented: (MJAVADOC-116) Impossible to aggregate javadoc if snapshot never built

[ http://jira.codehaus.org/browse/MJAVADOC-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92690 ] Arne Degenring commented on MJAVADOC-116: - I face the same problem. It seems to be a regression, as the problem does

[jira] Created: (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies

go-offline / resolve-plugins does not resolve all plugin dependencies - Key: MDEP-82 URL: http://jira.codehaus.org/browse/MDEP-82 Project: Maven 2.x Dependency Plugin Issue

[jira] Updated: (MDEP-72) "IllegalArgumentException: Cannot accept visitor on URL" when project contains a non-jar (e.g. zip) dependency

[ http://jira.codehaus.org/browse/MDEP-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arne Degenring updated MDEP-72: --- Attachment: pom.xml This does not seem to be fixed completely. When I run dependency:analyze (2.0-alpha-4, Ma

[jira] Commented: (MJAVADOC-98) Add support for Javadoc version different from JAVA_HOME

[ http://jira.codehaus.org/browse/MJAVADOC-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91584 ] Arne Degenring commented on MJAVADOC-98: I have the same usage scenario: JAVA_HOME set to 1.4 JDK, maven-compiler-plu

[jira] Commented: (MJAVADOC-109) Able to point to different JVM, rather then just using what is set in JAVA_HOME

[ http://jira.codehaus.org/browse/MJAVADOC-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91580 ] Arne Degenring commented on MJAVADOC-109: - I would need this feature as well. I found MJAVADOC-98 which describes th

[jira] Created: (SCM-290) Improved documentation for ClearCase SCM provider

Improved documentation for ClearCase SCM provider - Key: SCM-290 URL: http://jira.codehaus.org/browse/SCM-290 Project: Maven SCM Issue Type: Improvement Components: documentation, mav

[jira] Created: (SCM-289) Allow to store clearcase-settings.xml in ${maven.home}/conf instead of ${user.home}/.scm

Allow to store clearcase-settings.xml in ${maven.home}/conf instead of ${user.home}/.scm Key: SCM-289 URL: http://jira.codehaus.org/browse/SCM-289 Project: Maven

[jira] Commented: (SCM-288) Improved support for SCM providers like ClearCase that do NOT check out directly into the check-out-dir but into sub-directories of the check-out-dir

[ http://jira.codehaus.org/browse/SCM-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90708 ] Arne Degenring commented on SCM-288: I filed an issue for Continuum as well: CONTINUUM-1218 > Improved support for SCM provi

[jira] Commented: (CONTINUUM-1218) Automatically determine correct POM file location in Build Definition when checking out from SCMs like ClearCase

[ http://jira.codehaus.org/browse/CONTINUUM-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90706 ] Arne Degenring commented on CONTINUUM-1218: --- I haven't attached a patch to this issue yet, because I do not know

[jira] Created: (CONTINUUM-1218) Automatically determine correct POM file location in Build Definition when checking out from SCMs like ClearCase

Automatically determine correct POM file location in Build Definition when checking out from SCMs like ClearCase Key: CONTINUUM-1218 URL: http://jira.

[jira] Created: (MRELEASE-208) Support for ClearCase, and other SCMs that do checkout projects to subdirectories of the checkout directory

Support for ClearCase, and other SCMs that do checkout projects to subdirectories of the checkout directory --- Key: MRELEASE-208 URL: http://jira.codehaus.org

[jira] Updated: (SCM-288) Improved support for SCM providers like ClearCase that do NOT check out directly into the check-out-dir but into sub-directories of the check-out-dir

[ http://jira.codehaus.org/browse/SCM-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arne Degenring updated SCM-288: --- Attachment: patch-maven-scm-2.txt I have attached an updated patch (patch-maven-scm-2.txt) that contains a new

[jira] Created: (SCM-288) Improved support for SCM providers like ClearCase that do NOT check out directly into the check-out-dir but into sub-directories of the check-out-dir

Improved support for SCM providers like ClearCase that do NOT check out directly into the check-out-dir but into sub-directories of the check-out-dir

[jira] Commented: (CONTINUUM-1120) Default SCM Clearcase

[ http://jira.codehaus.org/browse/CONTINUUM-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90158 ] Arne Degenring commented on CONTINUUM-1120: --- Ausiàs, I think this works as designed. The SCM URL does NOT spec

[jira] Created: (SCM-287) ClearCase / Support for checking out from a tag and auto-creation of config specs

ClearCase / Support for checking out from a tag and auto-creation of config specs - Key: SCM-287 URL: http://jira.codehaus.org/browse/SCM-287 Project: Maven SCM

[jira] Created: (CONTINUUM-937) NPE in DefaultContinuumScm.getValidationMessages, e.g. when maven-scm-local cannot access files

NPE in DefaultContinuumScm.getValidationMessages, e.g. when maven-scm-local cannot access files --- Key: CONTINUUM-937 URL: http://jira.codehaus.org/browse/CONTINUUM-937

[jira] Commented: (CONTINUUM-780) Problem with check out with more than one sheduled projects

[ http://jira.codehaus.org/browse/CONTINUUM-780?page=comments#action_75218 ] Arne Degenring commented on CONTINUUM-780: -- Occasionally some of our builds are failing during scheduled builds. Forced builds are working fine. I see the same

[jira] Created: (SCM-231) Support for incoming deletions through provider-specific metadata file

Support for incoming deletions through provider-specific metadata file -- Key: SCM-231 URL: http://jira.codehaus.org/browse/SCM-231 Project: Maven SCM Issue Type: Improvemen

[jira] Created: (MNG-2528) updatePolicy "always" does not work for repositories with "releases", at least not for transitive dependencies

updatePolicy "always" does not work for repositories with "releases", at least not for transitive dependencies -- Key: MNG-2528 URL: http://jira.codehaus.o