[
https://issues.apache.org/jira/browse/MNG-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845783#comment-16845783
]
Gary McWilliams commented on MNG-6658:
--------------------------------------
I am indeed a fool (although it's *no excuse*, the project started out as a
single app, hence src at top level).
As you guys say though I've just missed the "move the code to a module" and
that's looking much better
> Maven 3.6.1 breaks build when using custom source folder
> --------------------------------------------------------
>
> Key: MNG-6658
> URL: https://issues.apache.org/jira/browse/MNG-6658
> Project: Maven
> Issue Type: Bug
> Components: core
> Affects Versions: 3.6.1
> Reporter: Gary McWilliams
> Priority: Major
>
> NOTE: apacher 3.5.x and 3.6.0 don't exhibit this behaviour, only 3.6.1
> For reasons too long (and painful) to discuss, I have a need to build 2 war
> files from one codebase.
> What I have:
> {{parent/}}
> {{ src/com/.../*.java}}
> {{ pom.xml}}
> {{ module1/}}
> {{ pom.xml}}
> {{ module2/}}
> {{ pom.xml}}
>
> The parent folder (pom.xml with packaging 'pom') contains all the source and
> defines the 2 modules.
> The parent pom.xml has:
> {{ <build>}}
> {{ <sourceDirectory>../src/main/java</sourceDirectory>}}
> {{ <testSourceDirectory>../src/test/java</testSourceDirectory>}}
>
> When the 2 modules run, they find the source/test code in the parent folder
> and compile/build out the class/war locally in target folder.
> Until 3.6.1, now I get:
> {{[ERROR] COMPILATION ERROR :}}
> {{[INFO] -------------------------------------------------------------}}
> {{[ERROR] /D:/.../src/main/java/com/.../ClassA.java:[36,8] duplicate class:
> com....ClassA}}
> where the "duplcate" classname is "the same class", so ClassA complains about
> duplicate ClassA
> Using maven 3.5.2, I see:
> {{[INFO] Compiling 11 source files to ...}}
> In maven 3.6.1, I see:
> {{[INFO] Compiling 22 source filesto ...}}
> Just looking advice. I know I should not be trying to build 2 artifacts in
> one project, but it's been working until now
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
