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...@codehaus.org> on 2014/11/25 21:50:18 UTC

[jira] (MCOMPILER-36) class Foo is public, should be declared in a file named Foo.java

     [ https://jira.codehaus.org/browse/MCOMPILER-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MCOMPILER-36.
-----------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> class Foo is public, should be declared in a file named Foo.java
> ----------------------------------------------------------------
>
>                 Key: MCOMPILER-36
>                 URL: https://jira.codehaus.org/browse/MCOMPILER-36
>             Project: Maven Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0.1
>            Reporter: Per Olesen
>            Priority: Minor
>
> When adding a depency to a jar which contains source code like this:
>     <dependency>
>       <groupId>com.nordija</groupId>
>       <artifactId>nordija-midtier</artifactId>
>       <version>snapshot</version>
>       <classifier>sources</classifier>
>       <scope>test</scope>
>     </dependency>
> where I'm using the "classifier", the "compiler:testCompile" goal fails with the error:
> Failure executing javac, but could not parse the error:
> /home/tomcat/.m2/repository/com/nordija/nordija-midtier/snapshot/nordija-midtier-snapshot-sources.jar(com/nordija/midtier/util/NestingException.java):42: class NestingException is public, should be declared in a file named NestingException.java
> (source unavailable)
> 1 error
> Now, my first thought is of course that the jar is corrupt or packaged wrongly or something like that. But it seems to be okay, and my IDEA can browse it and does not show error-marks for the source file in question. And, the same dependency is used in another module in the same build, where it is no problem!!!
> I solved the problem by going back to v2.0 of the compiler plugin, where everything works.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)