[jira] (SCM-779) scm:validate needs to use provided credentials

Dan Tran created SCM-779: Summary: scm:validate needs to use provided credentials Key: SCM-779 URL: https://jira.codehaus.org/browse/SCM-779 Project: Maven SCM Issue Type: Improvement

[jira] (SCM-780) Duplicate connection url's properties

Dan Tran created SCM-780: Summary: Duplicate connection url's properties Key: SCM-780 URL: https://jira.codehaus.org/browse/SCM-780 Project: Maven SCM Issue Type: Bug Components:

[jira] (SCM-780) Duplicate connection url's properties

[ https://jira.codehaus.org/browse/SCM-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-780: - Fix Version/s: 1.9.2 Duplicate connection url's properties -

[jira] (SCM-780) Duplicate connection url's properties

[ https://jira.codehaus.org/browse/SCM-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352804#comment-352804 ] Dan Tran commented on SCM-780: -- This is a trivial fix, can I have for to 1.9.2 release? feelfree to move

[jira] (MDEP-456) Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451

[ https://jira.codehaus.org/browse/MDEP-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352349#comment-352349 ] Dan Tran commented on MDEP-456: --- I wonder if this

[jira] (MDEP-456) Make a dependency:copy-proj goal that is equivalent to dependency:copy but that works in multi- module project. Related issue: https://jira.codehaus.org/browse/MDEP-451

[ https://jira.codehaus.org/browse/MDEP-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352367#comment-352367 ] Dan Tran commented on MDEP-456: --- I use it a lots, but never with your use case Make a

[jira] (WAGON-407) wagon-maven-plugin ITs fail with missing class: org.apache.commons.io.IOUtils

[ https://jira.codehaus.org/browse/WAGON-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352325#comment-352325 ] Dan Tran commented on WAGON-407: Oliver, any chance this would get into 2.7 release?

[jira] (MRELEASE-884) SCM null password configured at settings.xml's server becomes '{}'

Dan Tran created MRELEASE-884: - Summary: SCM null password configured at settings.xml's server becomes '{}' Key: MRELEASE-884 URL: https://jira.codehaus.org/browse/MRELEASE-884 Project: Maven Release

[jira] (MNG-5679) Maven should fetch jars using https

[ https://jira.codehaus.org/browse/MNG-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed MNG-5679. - Resolution: Won't Fix please use maven 3.2.3 Maven should fetch jars using https ---

[jira] (MNG-5678) second import within dependencyManagement is not taken from the correct repository

[ https://jira.codehaus.org/browse/MNG-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351455#comment-351455 ] Dan Tran commented on MNG-5678: --- related to https://jira.codehaus.org/browse/MNG-5663 ? second import

[jira] (MNG-5676) mvn -U crashes with IBM JDK

[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351312#comment-351312 ] Dan Tran commented on MNG-5676: --- I am using java version 1.7.0 Java(TM) SE Runtime Environment (build

[jira] (MNG-5676) mvn -U crashes with IBM JDK

Dan Tran created MNG-5676: - Summary: mvn -U crashes with IBM JDK Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.2.2, 3.1.1

[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project

[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350777#comment-350777 ] Dan Tran commented on MDEP-451: --- So this is maven-core's issue. The best way to get this resolve fast

[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project

[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350790#comment-350790 ] Dan Tran commented on MDEP-451: --- your tar has only one module, and it works for me Regression:

[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project

[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350792#comment-350792 ] Dan Tran commented on MDEP-451: --- works for me ( but why are you have same config on both parent and

[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project

[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350794#comment-350794 ] Dan Tran commented on MDEP-451: --- confirm, but this scenario is quite uncommon, could not think of a

[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.2.2 multi-module project

[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated MDEP-451: -- Summary: Regression: mvn dependency:copy doesn't run under maven 3.2.2 multi-module project (was: Regression:

[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated MDEP-451: -- Summary: Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project (was: Regression: mvn

[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project

[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350797#comment-350797 ] Dan Tran commented on MDEP-451: --- I am not sure if this is high priority since it breaks since 3.0.x

[jira] (MDEP-451) Regression: dependency:copy doesn't run under maven 3.2.2 multi-module project

[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350631#comment-350631 ] Dan Tran commented on MDEP-451: --- how about 3.0.5, 3.1.x, and 3.2.1? Regression: dependency:copy

[jira] (SCM-769) Unable to load maven-scm-provider-vss with Eclipse's M2E

Dan Tran created SCM-769: Summary: Unable to load maven-scm-provider-vss with Eclipse's M2E Key: SCM-769 URL: https://jira.codehaus.org/browse/SCM-769 Project: Maven SCM Issue Type: Task

[jira] (SCM-769) Unable to load maven-scm-provider-vss with Eclipse's M2E

[ https://jira.codehaus.org/browse/SCM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-769. Resolution: Fixed Fix Version/s: 1.9.2 Assignee: Dan Tran fixed at

[jira] (SCM-767) mockito should be under test scope, not compile scope for accurev provider

[ https://jira.codehaus.org/browse/SCM-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-767. Resolution: Fixed fixed at

[jira] (SCM-759) cannot create Branch with TFS-provider: TF10125: The path must start with $/

[ https://jira.codehaus.org/browse/SCM-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-759. Resolution: Fixed fixed the test at http://git-wip-us.apache.org/repos/asf/maven-scm/diff/b273f796 cannot create

[jira] (SCM-768) TfsBranchCommandTest is failing

[ https://jira.codehaus.org/browse/SCM-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-768. Resolution: Fixed Fix Version/s: 1.9.2 Assignee: Dan Tran fixed at

[jira] (SCM-767) mockito should be under test scope not compile code for accurev provider

Dan Tran created SCM-767: Summary: mockito should be under test scope not compile code for accurev provider Key: SCM-767 URL: https://jira.codehaus.org/browse/SCM-767 Project: Maven SCM Issue Type:

[jira] (SCM-767) mockito should be under test scope not compile code for accurev provider

[ https://jira.codehaus.org/browse/SCM-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-767: - Fix Version/s: 1.9.2 Assignee: Dan Tran mockito should be under test scope not compile code for accurev

[jira] (SCM-768) TfsBranchCommandTest is failing

Dan Tran created SCM-768: Summary: TfsBranchCommandTest is failing Key: SCM-768 URL: https://jira.codehaus.org/browse/SCM-768 Project: Maven SCM Issue Type: Task Components:

[jira] (SCM-768) TfsBranchCommandTest is failing

[ https://jira.codehaus.org/browse/SCM-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-768: - Description: it is currently failing under 1.9.2-SNAPSHOT. Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time

[jira] (SCM-759) cannot create Branch with TFS-provider: TF10125: The path must start with $/

[ https://jira.codehaus.org/browse/SCM-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran reopened SCM-759: -- cannot create Branch with TFS-provider: TF10125: The path must start with $/

[jira] (SCM-768) TfsBranchCommandTest is failing

[ https://jira.codehaus.org/browse/SCM-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350365#comment-350365 ] Dan Tran commented on SCM-768: -- it only fails when run under the whose suite, pass as standalone test

[jira] (SCM-767) mockito should be under test scope, not compile scope for accurev provider

[ https://jira.codehaus.org/browse/SCM-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-767: - Description: will use this opportunity to promote mockito to dedenencyManagement using version 1.9.5, since there are a

[jira] (MSITE-726) Document who report sets are selected

[ https://jira.codehaus.org/browse/MSITE-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350324#comment-350324 ] Dan Tran commented on MSITE-726: may be a propose patch would help Document who report sets are

[jira] (SCM-747) [PERFORCE] Support SSL

[ https://jira.codehaus.org/browse/SCM-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-747. Resolution: Fixed Fix Version/s: (was: 1.x) 1.10 Assignee: Dan Tran fixed at

[jira] (MNG-5580) mvn 3.x - unable to resolve snapshot artifact via ArtifactResolver using override local repository

[ https://jira.codehaus.org/browse/MNG-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=349276#comment-349276 ] Dan Tran commented on MNG-5580: --- good news, this issue is not seen starting with apache-maven-3.1.0.

[jira] (MDEP-313) Unable to download snapshot artifact with override local repository using maven 3

[ https://jira.codehaus.org/browse/MDEP-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed MDEP-313. - Resolution: Won't Fix Assignee: Dan Tran This issue is fixed at maven-core starting with apache-maven-3.1.0

[jira] (SCM-762) Validate ScmFileSet's external filelist agrument

Dan Tran created SCM-762: Summary: Validate ScmFileSet's external filelist agrument Key: SCM-762 URL: https://jira.codehaus.org/browse/SCM-762 Project: Maven SCM Issue Type: Improvement

[jira] (SCM-762) Validate ScmFileSet's external filelist agrument

[ https://jira.codehaus.org/browse/SCM-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-762: - Fix Version/s: 1.10 Assignee: Dan Tran Validate ScmFileSet's external filelist agrument

[jira] (SCM-762) Validate ScmFileSet's external filelist agrument

[ https://jira.codehaus.org/browse/SCM-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=348975#comment-348975 ] Dan Tran commented on SCM-762: -- In order to do full validation, there is a need to use

[jira] (SCM-483) Update SCM Perforce Provider to use P4Java

[ https://jira.codehaus.org/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=348771#comment-348771 ] Dan Tran edited comment on SCM-483 at 6/26/14 1:54 AM: --- maven scm provider for

[jira] (SCM-757) bootstrap/checkout/export goals now requires -Dproject.basedir=. set at command line

[ https://jira.codehaus.org/browse/SCM-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-757. Resolution: Fixed fixed at https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=commit;h=82b8f4bd

[jira] (SCM-760) remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement

[ https://jira.codehaus.org/browse/SCM-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-760. Resolution: Fixed fixed at http://git-wip-us.apache.org/repos/asf/maven-scm/commit/2b647833 remove maven-scm-plugin's

[jira] (SCM-761) Allow downstream TCK to define its own tag

Dan Tran created SCM-761: Summary: Allow downstream TCK to define its own tag Key: SCM-761 URL: https://jira.codehaus.org/browse/SCM-761 Project: Maven SCM Issue Type: Task Components:

[jira] (SCM-761) Allow downstream TCK to define its own tag

[ https://jira.codehaus.org/browse/SCM-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-761. Resolution: Fixed Fix Version/s: 1.10 Assignee: Dan Tran fixed at

[jira] (SCM-761) Allow downstream TCK to define its own tag

[ https://jira.codehaus.org/browse/SCM-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-761: - fixed at http://git-wip-us.apache.org/repos/asf/maven-scm/commit/692b76a9 Allow downstream TCK to define its own tag

[jira] (SCM-761) Allow downstream TCK to define its own tag

[ https://jira.codehaus.org/browse/SCM-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-761: - Component/s: (was: maven-scm-api) maven-scm-tck Allow downstream TCK to define its own tag

[jira] (SCM-756) TCK should invoke EditCommand for required edit mode provider like Perforce

[ https://jira.codehaus.org/browse/SCM-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-756: - Component/s: (was: maven-scm-api) maven-scm-tck TCK should invoke EditCommand for required edit

[jira] (SCM-755) Inject SecDispatcher into TCK base test case

[ https://jira.codehaus.org/browse/SCM-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-755: - Component/s: (was: maven-scm-api) maven-scm-tck Inject SecDispatcher into TCK base test case

[jira] (SCM-754) Require Tag/Branch Command to return the entire source tree is impractical

[ https://jira.codehaus.org/browse/SCM-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-754: - Component/s: (was: maven-scm-api) maven-scm-tck Require Tag/Branch Command to return the entire

[jira] (SCM-756) TCK should invoke EditCommand for provider like Perforce before any change

[ https://jira.codehaus.org/browse/SCM-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-756: - Summary: TCK should invoke EditCommand for provider like Perforce before any change (was: TCK should invoke EditCommand

[jira] (SCM-483) Update SCM Perforce Provider to use P4Java

[ https://jira.codehaus.org/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-483. Resolution: Won't Fix Assignee: Dan Tran maven scm provider for Perforce using p4java is not at

[jira] (SCM-757) bootstrap/checkout/export goals now requires -Dproject.basedir=. set at command line

[ https://jira.codehaus.org/browse/SCM-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=348609#comment-348609 ] Dan Tran edited comment on SCM-757 at 6/23/14 10:48 AM: here is build output.

[jira] (SCM-757) bootstrap/checkout/export goals now requires -Dproject.basedir=. set at command line

[ https://jira.codehaus.org/browse/SCM-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=348609#comment-348609 ] Dan Tran commented on SCM-757: -- here is build output C:\Users\trand8\tmpmvn scm:checkout

[jira] (SCM-757) bootstrap/checkout/export goals now requires -Dproject.basedir=. set at command line

[ https://jira.codehaus.org/browse/SCM-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=348611#comment-348611 ] Dan Tran commented on SCM-757: -- hack like this works if (

[jira] (SCM-757) bootstrap/checkout/export goals now requires -Dproject.basedir=. set at command line

[ https://jira.codehaus.org/browse/SCM-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=348611#comment-348611 ] Dan Tran edited comment on SCM-757 at 6/23/14 11:19 AM: hack like this works

[jira] (SCM-757) bootstrap/checkout/export goals now requires -Dproject.basedir=. set at command line

[ https://jira.codehaus.org/browse/SCM-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=348611#comment-348611 ] Dan Tran edited comment on SCM-757 at 6/23/14 11:19 AM: hack like this works

[jira] (SCM-760) remove maven-scm-plugin's RemoveMojoTest

Dan Tran created SCM-760: Summary: remove maven-scm-plugin's RemoveMojoTest Key: SCM-760 URL: https://jira.codehaus.org/browse/SCM-760 Project: Maven SCM Issue Type: Task Components:

[jira] (SCM-760) remove maven-scm-plugin's RemoveMojoTest

[ https://jira.codehaus.org/browse/SCM-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-760: - Fix Version/s: 1.10 Assignee: Dan Tran remove maven-scm-plugin's RemoveMojoTest

[jira] (SCM-760) remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement

[ https://jira.codehaus.org/browse/SCM-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-760: - Summary: remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement (was: remove

[jira] (SCM-760) remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement

[ https://jira.codehaus.org/browse/SCM-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-760: - Description: Currently this test uses P4 for its scm repo, and only runs when p4(.exe) detected on its path, however,

[jira] (SCM-760) remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement

[ https://jira.codehaus.org/browse/SCM-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-760: - Description: Currently this test uses P4 for its scm repo, and only runs when p4(.exe) detected on its path, however,

[jira] (SCM-760) remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement

[ https://jira.codehaus.org/browse/SCM-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-760: - Description: Currently this test uses P4 for its scm repo, and only runs when p4(.exe) detected on its path, however,

[jira] (SCM-760) remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement

[ https://jira.codehaus.org/browse/SCM-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-760: - Description: Currently this test uses P4 for its scm repo, and only runs when p4(.exe) detected on its path, however,

[jira] (SCM-760) remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement

[ https://jira.codehaus.org/browse/SCM-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=348615#comment-348615 ] Dan Tran edited comment on SCM-760 at 6/23/14 11:56 AM: Also this should not

[jira] (SCM-760) remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement

[ https://jira.codehaus.org/browse/SCM-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=348615#comment-348615 ] Dan Tran commented on SCM-760: -- Also this should not work since the url {code }

[jira] (SCM-754) Require Tag/Branch Command to return the entire source tree is impractical

[ https://jira.codehaus.org/browse/SCM-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-754: - Description: Currently the tag command when using with ScmFileSet that has no excludes/includes, it returns the entire

[jira] (SCM-755) Inject SecDispatcher into TCK base test case

[ https://jira.codehaus.org/browse/SCM-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-755. Resolution: Fixed Assignee: Dan Tran fixed at

[jira] (SCM-756) TCK should invoke EditCommand for required edit mode provider like Perforce

[ https://jira.codehaus.org/browse/SCM-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-756. Resolution: Fixed Assignee: Dan Tran fixed at

[jira] (SCM-754) Require Tag/Branch Command to return the entire source tree is impractical

[ https://jira.codehaus.org/browse/SCM-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-754. Resolution: Fixed Assignee: Dan Tran fixed at

[jira] (SCM-757) bootstrap/checkout/export goals now requires -Dproject.basedir=. set at command line

Dan Tran created SCM-757: Summary: bootstrap/checkout/export goals now requires -Dproject.basedir=. set at command line Key: SCM-757 URL: https://jira.codehaus.org/browse/SCM-757 Project: Maven SCM

[jira] (SCM-757) bootstrap/checkout/export goals now requires -Dproject.basedir=. set at command line

[ https://jira.codehaus.org/browse/SCM-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-757: - Fix Version/s: 1.10 Assignee: Dan Tran bootstrap/checkout/export goals now requires -Dproject.basedir=. set at

[jira] (MNG-5580) mvn 3.x - unable to resolve snapshot artifact via ArtifactResolver using override local repository

[ https://jira.codehaus.org/browse/MNG-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=348279#comment-348279 ] Dan Tran commented on MNG-5580: --- it is a shame that I dont have a sample for this, will cook one up.

[jira] (SCM-754) Require Tag Command to return the entire source tree is impractical

Dan Tran created SCM-754: Summary: Require Tag Command to return the entire source tree is impractical Key: SCM-754 URL: https://jira.codehaus.org/browse/SCM-754 Project: Maven SCM Issue Type: Task

[jira] (SCM-754) Require Tag Command to return the entire source tree is impractical

[ https://jira.codehaus.org/browse/SCM-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-754: - Fix Version/s: 1.10 Require Tag Command to return the entire source tree is impractical

[jira] (SCM-755) Inject SecDispatcher into TCK base test case

Dan Tran created SCM-755: Summary: Inject SecDispatcher into TCK base test case Key: SCM-755 URL: https://jira.codehaus.org/browse/SCM-755 Project: Maven SCM Issue Type: Task Components:

[jira] (SCM-755) Inject SecDispatcher into TCK base test case

[ https://jira.codehaus.org/browse/SCM-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-755: - Fix Version/s: 1.10 Inject SecDispatcher into TCK base test case

[jira] (SCM-756) TCK should invoke EditCommand for required edit mode provider like Perforce

Dan Tran created SCM-756: Summary: TCK should invoke EditCommand for required edit mode provider like Perforce Key: SCM-756 URL: https://jira.codehaus.org/browse/SCM-756 Project: Maven SCM Issue

[jira] (SCM-756) TCK should invoke EditCommand for required edit mode provider like Perforce

[ https://jira.codehaus.org/browse/SCM-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-756: - Fix Version/s: 1.10 TCK should invoke EditCommand for required edit mode provider like Perforce

[jira] (MDEP-447) Add option to use native tar executable to unpack

[ https://jira.codehaus.org/browse/MDEP-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated MDEP-447: -- Description: This method is faster and reserve softlinks. This is very edge case. Link to discussion at user list

[jira] (MDEP-447) Add option to use native tar executable to unpack

[ https://jira.codehaus.org/browse/MDEP-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran reassigned MDEP-447: - Assignee: Dan Tran Add option to use native tar executable to unpack

[jira] (MDEP-447) Add option to use native tar executable to unpack

[ https://jira.codehaus.org/browse/MDEP-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=347443#comment-347443 ] Dan Tran commented on MDEP-447: --- David, thank you for the feed back. This is a very edge case where I

[jira] (MDEP-447) Add option to native tar to unpack

Dan Tran created MDEP-447: - Summary: Add option to native tar to unpack Key: MDEP-447 URL: https://jira.codehaus.org/browse/MDEP-447 Project: Maven Dependency Plugin Issue Type: Improvement

[jira] (MDEP-447) Add option to use native tar executable to unpack

[ https://jira.codehaus.org/browse/MDEP-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated MDEP-447: -- Summary: Add option to use native tar executable to unpack (was: Add option to native tar to unpack) Add option to

[jira] (SCM-741) scm:validate for svn should offer a way to check the current directory actually matches what's declared in the pom

[ https://jira.codehaus.org/browse/SCM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran reopened SCM-741: -- Need to reopen this issue to track the failing IT introduced by this fix

[jira] (SCM-741) scm:validate for svn should offer a way to check the current directory actually matches what's declared in the pom

[ https://jira.codehaus.org/browse/SCM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=345882#comment-345882 ] Dan Tran commented on SCM-741: -- I would propose we disable this test, and create another Jira so that we

[jira] (SCM-747) Support SSL

Dan Tran created SCM-747: Summary: Support SSL Key: SCM-747 URL: https://jira.codehaus.org/browse/SCM-747 Project: Maven SCM Issue Type: New Feature Components: maven-scm-provider-perforce

[jira] (SCM-747) [PERFORCE] Support SSL

[ https://jira.codehaus.org/browse/SCM-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-747: - Summary: [PERFORCE] Support SSL (was: Support SSL) [PERFORCE] Support SSL --

[jira] (SCM-747) [PERFORCE] Support SSL

[ https://jira.codehaus.org/browse/SCM-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-747: - Fix Version/s: 1.10 [PERFORCE] Support SSL -- Key: SCM-747 URL:

[jira] (WAGON-411) Enhance merge-maven-repos to work with SNAPSHOT builds

[ https://jira.codehaus.org/browse/WAGON-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=341792#comment-341792 ] Dan Tran commented on WAGON-411: this has nothing to do with wagon itself, it should be back and

[jira] (WAGON-411) Enhance merge-maven-repos to work with SNAPSHOT builds

[ https://jira.codehaus.org/browse/WAGON-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=341801#comment-341801 ] Dan Tran commented on WAGON-411: i saw the patch, looks maven 3 metadata api fix the bug, we just

[jira] (WAGON-411) Enhance merge-maven-repos to work with SNAPSHOT builds

[ https://jira.codehaus.org/browse/WAGON-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=341856#comment-341856 ] Dan Tran commented on WAGON-411: Hi Karl, could you move this issue back to MOJO? Thanks Enhance

[jira] (MNG-5580) mvn 3.x - unable to resolve snapshot artifact via ArtifactResolver using override local repository

Dan Tran created MNG-5580: - Summary: mvn 3.x - unable to resolve snapshot artifact via ArtifactResolver using override local repository Key: MNG-5580 URL: https://jira.codehaus.org/browse/MNG-5580 Project:

[jira] (MNG-5580) mvn 3.x - unable to resolve snapshot artifact via ArtifactResolver using override local repository

[ https://jira.codehaus.org/browse/MNG-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated MNG-5580: -- Description: I can use ArtifactResolver to download a given snapshot maven coordinate. This works with private local

[jira] (WAGON-407) wagon-maven-plugin ITs fail with missing class: org.apache.commons.io.IOUtils

[ https://jira.codehaus.org/browse/WAGON-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338157#comment-338157 ] Dan Tran commented on WAGON-407: so the correct solution is to shade commons-io, common-lang, and

[jira] (SCM-732) plugin desn't work with command line client past 2009R2

[ https://jira.codehaus.org/browse/SCM-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=332759#comment-332759 ] Dan Tran commented on SCM-732: -- since the change sound drastic, you may end up to create another provider

[jira] (SUREFIRE-599) Logs console output multiple times (no. of times log output = the no. of test being run) for JUnit/XMLUnit tests

[ https://jira.codehaus.org/browse/SUREFIRE-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=322722#comment-322722 ] Dan Tran commented on SUREFIRE-599: --- My bad!!! Logs console output multiple

[jira] (SUREFIRE-599) Logs console output multiple times (no. of times log output = the no. of test being run) for JUnit/XMLUnit tests

[ https://jira.codehaus.org/browse/SUREFIRE-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=322704#comment-322704 ] Dan Tran commented on SUREFIRE-599: --- strange, I am still seeing leak for my test which uses

[jira] (SUREFIRE-599) Logs console output multiple times (no. of times log output = the no. of test being run) for JUnit/XMLUnit tests

[ https://jira.codehaus.org/browse/SUREFIRE-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=322711#comment-322711 ] Dan Tran commented on SUREFIRE-599: --- here is the test @Test public void testConsoleLeak()

[jira] (MSTAGE-16) Stage plugin doesn't work with maven3

[ https://jira.codehaus.org/browse/MSTAGE-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=309698#comment-309698 ] Dan Tran commented on MSTAGE-16: may want to try wagon-maven-plugin Stage plugin

[jira] (MECLIPSE-731) eclipse:clean not deleting ./settings folder that it creates

[ https://jira.codehaus.org/browse/MECLIPSE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308110#comment-308110 ] Dan Tran commented on MECLIPSE-731: --- now we need a release :-) eclipse:clean

<    1   2   3   4   5   6   7   8   9   >