You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Alexander Bender (JIRA)" <ji...@apache.org> on 2016/07/27 06:41:20 UTC

[jira] [Created] (MNG-6071) GetResource ('/) returns 'null' if build is started with -f

Alexander Bender created MNG-6071:
-------------------------------------

             Summary: GetResource ('/) returns 'null' if build is started with -f
                 Key: MNG-6071
                 URL: https://issues.apache.org/jira/browse/MNG-6071
             Project: Maven
          Issue Type: Bug
    Affects Versions: 3.3.9, 3.3.1, 3.2.1
         Environment: Windows 10 x64
Tested in cmd.exe, git bash.
            Reporter: Alexander Bender
            Priority: Minor


I set up a very simple test maven project with only a dependency to testNG.

{code}
    public class TestTest {
    @Test
    public void test() {
        System.out.println(getClass().getResource("/"));
{code}

Depending on how I build this, the call either returns null or the expected directory. How is that?

{code}
    // Prints: file:/C:/workspace/test/testproject/target/test-classes/
    mvn clean test -Dtest=TestTest -f testproject/pom.xml
    // Prints: null
    mvn clean test -Dtest=TestTest -f ./testproject/pom.xml
{code}

Note that the second call includes "./" after -f.

I actually want to find out the /target folder regardless of scenario (testNG in IntelliJ, Maven, Jenkins Buid, ...). So far, this way has proven the most reliable.

{code}
        System.out.println(getClass().getResource("./"));
{code}

This seems to reliably point to file:/C:/workspace/test/testproject/target/test-classes/com/testproject/test. Would this be safer to use?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)