[
https://issues.apache.org/jira/browse/MNG-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary McWilliams updated MNG-6658:
---------------------------------
Description:
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
Just looking advice. I know I should not be trying to build 2 artifacts in one
project, but it's been working until now
was:
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/.../File.java:[36,8] duplicate class:
com....Class}}
where the "duplcate" classname is "the same class", so ClassA complains about
duplicate ClassA
Just looking advice. I know I should not be trying to build 2 artifacts in one
project, but it's been working until now
> 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
> 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)
