You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2019/07/06 16:40:00 UTC
[jira] [Commented] (MNG-6660) duplicate classes error with source
in the root directory
[ https://issues.apache.org/jira/browse/MNG-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16879722#comment-16879722 ]
Michael Osipov commented on MNG-6660:
-------------------------------------
This is likely a dup of MNG-6700 which has a valid PR.
> duplicate classes error with source in the root directory
> ---------------------------------------------------------
>
> Key: MNG-6660
> URL: https://issues.apache.org/jira/browse/MNG-6660
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.6.1
> Reporter: Luke Usherwood
> Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: debug.log
>
>
> Trying to follow the instructions from [here|[https://github.com/bytedeco/javacpp-presets/tree/master/hdf5#sample-usage]] which entails adding this little pom:
> {{<project>
> <modelVersion>4.0.0</modelVersion>
> <groupId>org.bytedeco.hdf5</groupId>
> <artifactId>H5tutrCmprss</artifactId>
> <version>1.5</version>
> <properties>
> <exec.mainClass>H5tutrCmprss</exec.mainClass>
> </properties>
> <dependencies>
> <dependency>
> <groupId>org.bytedeco</groupId>
> <artifactId>hdf5-platform</artifactId>
> <version>1.10.5-1.5</version>
> </dependency>
> </dependencies>
> <build>
> <sourceDirectory>.</sourceDirectory>
> </build>
> </project>}}
> and a Java source file to the root directory. (There's code in the same link, but actually anything I think anything with a `main` function will do.)
> It does not seem to work with:
> {{<sourceDirectory>.</sourceDirectory>}}
> Yielding the strange error
> Compilation failure
> [ERROR] /D:/work/workspace/hdf5/H5tutrCmprss.java:[7,8] duplicate class: H5tutrCmprss
> (Seen also in: MCOMPILER-235)
> However if I move the source under a sub-directory `src` and update the pom accordingly, it works fine. I assume that this pom worked "out of the box" once, so I wonder if this is a regression?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)