[jira] Updated: (MRM-206) Add xml-rpc search

[ http://jira.codehaus.org/browse/MRM-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Didion updated MRM-206: Attachment: archiva-xmlrpc.zip I basically took the xmlrpc stuff from Continuum and ported it over to Archiva. Ther

[jira] Commented: (MRM-425) Search and Browse do not work for snapshots

[ http://jira.codehaus.org/browse/MRM-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100563 ] John Didion commented on MRM-425: - The repro for search is similar: search for an artifact with snapshot versions, click on one

[jira] Created: (MRM-425) Search and Browse do not work for snapshots

Search and Browse do not work for snapshots --- Key: MRM-425 URL: http://jira.codehaus.org/browse/MRM-425 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.

[jira] Reopened: (MRM-419) WebDAV functionality not working for Internet Explorer / Windows Network Places

[ http://jira.codehaus.org/browse/MRM-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Didion reopened MRM-419: - This bug is only fixed for IE. I am still unable to create a Windows Network Place for the repository. Repro step/err

[jira] Created: (MRM-419) WebDAV functionality not working for Internet Explorer / Windows Network Places

WebDAV functionality not working for Internet Explorer / Windows Network Places --- Key: MRM-419 URL: http://jira.codehaus.org/browse/MRM-419 Project: Archiva Issue

[jira] Commented: (MNG-1994) Execution order of child plugins is arbitrary if inheritance is involved

[ http://jira.codehaus.org/browse/MNG-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87742 ] John Didion commented on MNG-1994: -- Actually, it's pretty easy to unit test this bug. You have a parent POM that defines two o

[jira] Commented: (CONTINUUM-995) MavenTwoBuildExecutor.getDeployableArtifacts does not return attached artifacts

[ http://jira.codehaus.org/browse/CONTINUUM-995?page=comments#action_79870 ] John Didion commented on CONTINUUM-995: --- -dist is a loose standard we decided on internally for installable assemblies (as opposed to -bin, which typically implie

[jira] Updated: (CONTINUUM-798) Modules automatic discovery

[ http://jira.codehaus.org/browse/CONTINUUM-798?page=all ] John Didion updated CONTINUUM-798: -- Attachment: add-modules-from-updated-project.diff The attached patch addresses this issue for Maven 2 projects. Basically, it adds an action call in DefaultB

[jira] Created: (CONTINUUM-995) MavenTwoBuildExecutor.getDeployableArtifacts does not return attached artifacts

MavenTwoBuildExecutor.getDeployableArtifacts does not return attached artifacts --- Key: CONTINUUM-995 URL: http://jira.codehaus.org/browse/CONTINUUM-995 Project: Continuum

[jira] Commented: (CONTINUUM-992) Configure SCM username/password from settings.xml

[ http://jira.codehaus.org/browse/CONTINUUM-992?page=comments#action_79264 ] John Didion commented on CONTINUUM-992: --- This patch was made against the 1.0.3 tag. It's really confusing to know what codebase to be working from...we use Maestr

[jira] Created: (SCM-247) SvnChangeSet.containsFileName has false negatives for Windows file names

SvnChangeSet.containsFileName has false negatives for Windows file names Key: SCM-247 URL: http://jira.codehaus.org/browse/SCM-247 Project: Maven SCM Issue Type: Bug

[jira] Created: (CONTINUUM-992) Configure SCM username/password from settings.xml

Configure SCM username/password from settings.xml - Key: CONTINUUM-992 URL: http://jira.codehaus.org/browse/CONTINUUM-992 Project: Continuum Issue Type: New Feature Reporter: John D

[jira] Commented: (CONTINUUM-418) RSS feed for build status

[ http://jira.codehaus.org/browse/CONTINUUM-418?page=comments#action_79054 ] John Didion commented on CONTINUUM-418: --- I've created a patch against the Maestro source that provides RSS feeds on a per-project and per-group basis. When will t

[jira] Created: (CONTINUUM-991) Add meta refresh header to summary pages

Add meta refresh header to summary pages Key: CONTINUUM-991 URL: http://jira.codehaus.org/browse/CONTINUUM-991 Project: Continuum Issue Type: New Feature Reporter: John Didion

[jira] Commented: (CONTINUUM-605) Add a RecipientSource that derives addresses from the change list

[ http://jira.codehaus.org/browse/CONTINUUM-605?page=comments#action_79052 ] John Didion commented on CONTINUUM-605: --- I've added a new diff against the 1.0.3 tag. It would be idea if RecipientSources could be associated with notifiers (or

[jira] Updated: (CONTINUUM-605) Add a RecipientSource that derives addresses from the change list

[ http://jira.codehaus.org/browse/CONTINUUM-605?page=all ] John Didion updated CONTINUUM-605: -- Attachment: change-list-recipient-source.diff > Add a RecipientSource that derives addresses from the change list > --

[jira] Closed: (CONTINUUM-990) Pass some continuum information to build tools when executing a build

[ http://jira.codehaus.org/browse/CONTINUUM-990?page=all ] John Didion closed CONTINUUM-990. - Resolution: Duplicate Dupliate of CONTINUUM-566 > Pass some continuum information to build tools when executing a build > -

[jira] Reopened: (CONTINUUM-990) Pass some continuum information to build tools when executing a build

[ http://jira.codehaus.org/browse/CONTINUUM-990?page=all ] John Didion reopened CONTINUUM-990: --- Oops...closed the wrong issue > Pass some continuum information to build tools when executing a build > --

[jira] Updated: (CONTINUUM-566) Build numbers are essential

[ http://jira.codehaus.org/browse/CONTINUUM-566?page=all ] John Didion updated CONTINUUM-566: -- Attachment: add-build-number-to-mail-subject.diff > Build numbers are essential > --- > > Key: CONTINUUM-566 >

[jira] Created: (CONTINUUM-990) Pass some continuum information to build tools when executing a build

Pass some continuum information to build tools when executing a build - Key: CONTINUUM-990 URL: http://jira.codehaus.org/browse/CONTINUUM-990 Project: Continuum Issue Type:

[jira] Created: (CONTINUUM-989) There are two component definitions for role org.codehaus.plexus.mailsender.MailSender

There are two component definitions for role org.codehaus.plexus.mailsender.MailSender -- Key: CONTINUUM-989 URL: http://jira.codehaus.org/browse/CONTINUUM-989 Projec

[jira] Commented: (CONTINUUM-605) Add a RecipientSource that derives addresses from the change list

[ http://jira.codehaus.org/browse/CONTINUUM-605?page=comments#action_72964 ] John Didion commented on CONTINUUM-605: --- Basically you just replace ContinuumRecipientSource with ChangeListRecipientSource in application.xml (found in apps/cont

[jira] Commented: (WAGON-47) add zip provider (source attahced)

[ http://jira.codehaus.org/browse/WAGON-47?page=comments#action_72188 ] John Didion commented on WAGON-47: -- Attachment #4 has everything, including tests and docs. For some reason, it didn't obsolete the other diffs with the same name. > add zi

[jira] Updated: (WAGON-47) add zip provider (source attahced)

[ http://jira.codehaus.org/browse/WAGON-47?page=all ] John Didion updated WAGON-47: - Attachment: wagon-provider.zip.diff > add zip provider (source attahced) > -- > > Key: WAGON-47 > URL: http:/

[jira] Commented: (SCM-209) Specifying working directory for Runtime.exec() on linux has no effect

[ http://jira.codehaus.org/browse/SCM-209?page=comments#action_72074 ] John Didion commented on SCM-209: - Sorry...I don' t have the bandwidth for this. We've patched it locally, so I think we'll hang on until you do your refactoring (should be pr

[jira] Created: (SCM-209) Specifying working directory for Runtime.exec() on linux has no effect

Specifying working directory for Runtime.exec() on linux has no effect -- Key: SCM-209 URL: http://jira.codehaus.org/browse/SCM-209 Project: Maven SCM Type: Bug Components: maven-scm-provider-perf

[jira] Commented: (WAGON-47) add zip provider (source attahced)

[ http://jira.codehaus.org/browse/WAGON-47?page=comments#action_65216 ] John Didion commented on WAGON-47: -- Never mind, I found the code style scheme. I've attached a new diff of the zip provider with apache boilerplate and correct code style. > add zip pr

[jira] Commented: (WAGON-47) add zip provider (source attahced)

[ http://jira.codehaus.org/browse/WAGON-47?page=comments#action_65213 ] John Didion commented on WAGON-47: -- Oops...I always forget to change the boilerplate. Hey, is there an apache code style scheme for IntelliJ? > add zip provider (source attahced) > ---

[jira] Updated: (WAGON-47) add zip provider (source attahced)

[ http://jira.codehaus.org/browse/WAGON-47?page=all ] John Didion updated WAGON-47: - Attachment: wagon-provider-zip.diff wagon-provider-api.diff > add zip provider (source attahced) > -- > > Key: WAGON

[jira] Created: (WAGON-47) add zip provider (source attahced)

add zip provider (source attahced) -- Key: WAGON-47 URL: http://jira.codehaus.org/browse/WAGON-47 Project: wagon Type: New Feature Components: wagon-provider-api Reporter: John Didion As part of our build process, we generat

[jira] Commented: (CONTINUUM-309) add junit results report to website, failures to email

[ http://jira.codehaus.org/browse/CONTINUUM-309?page=comments#action_63273 ] John Didion commented on CONTINUUM-309: --- We too are itching for this feature. I want to implement it, but I'm not sure the best way to do it. I'm thinking that I'll add to

[jira] Created: (SCM-184) PerforceScmProvider.createClientspec should use the working dir's canonical path for the clientspec root

PerforceScmProvider.createClientspec should use the working dir's canonical path for the clientspec root Key: SCM-184 URL: http://jira.codehaus.org/browse/SCM-184 Projec

[jira] Reopened: (CONTINUUM-651) DefaultContinuumScm.getScmRepository should not set project scm username/password if they are the empty string

[ http://jira.codehaus.org/browse/CONTINUUM-651?page=all ] John Didion reopened CONTINUUM-651: --- I looked at the trunk version and it's still doing a null check instead of StringUtils.isEmpty. The reason why this is broken is the following: 1. Add a

[jira] Created: (CONTINUUM-651) DefaultContinuumScm.getScmRepository should not set project scm username/password if they are the empty string

DefaultContinuumScm.getScmRepository should not set project scm username/password if they are the empty string -- Key: CONTINUUM-651 URL: http://jira.codehaus.org/browse/C

[jira] Commented: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command

[ http://jira.codehaus.org/browse/SCM-165?page=comments#action_63018 ] John Didion commented on SCM-165: - Oops..replace "change log command" with "checkout command" in steps 4, 6, 7 above. > PerforceChangeLogCommand needs to use the same clientspec as the u

[jira] Reopened: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command

[ http://jira.codehaus.org/browse/SCM-165?page=all ] John Didion reopened SCM-165: - This still breaks in continuum. Here's the problem: continuum may update many different projects within the same VM. If it is always updating the working directory on the