maven: after a successful build, doing a mvn install fails with "The type package-info is already defined"

Presumably, you have a package-info.java file in the same package in both your src/main/java and src/main/groovy source folders. I tried this on a groovy project and I do see the same error on the command line. It is not there when I stop using the groovy-eclipse-compiler.

However, importing this project into Eclipse, I get "The type package-info is already defined" for all these instances, even when on the command line, this error is not shown.

I'll explore a bit more...

Thanks, Andrew

You can see this error by checking out:

https://test.kuali.org/svn/rice/sandbox/KULRICE-5640

Also, we only have one package-info.java file in our java source tree.

I also ran into this bug in our CI environment

https://bugs.eclipse.org/bugs/show_bug.cgi?id=214948

no clue why it didn't show up locally. Maybe related?

What??? I must be smoking something. Now, I can't even get a vanilla project with multiple (non-test) source folders to compile if package-infos overlap. I don't know why this was working for me before.

But, it does make some sense. In this situation, which package-info.java file should make it into the output folder? There is fundamentally a conflict here. The package-info from one source folder should apply to the other source folder.

I think that you get away with this for gmaven since the gmaven compiler compiles groovy source separately from java source. But, that begs the question, which package-info.java would you expect to see in the output folder?

I am going to try some more to see if I can get this working again for a vanilla multi-source folder project. And if not, I am starting to think that this "feature" of gmaven is not really a feature...

Well, let me try your project. I've been hacking away at this without looking for your comments between mine.

hmmm...with your project. I did:

1. mvn clean compile
2. mvn install
3. mvn install

All commands were successful. What version of maven are you using? I am on 3.0.3.

odd. I'm on Windows 7 running maven 3.0.3.

If you recall we tested out this compiler on the rice project a few months back. Then on was on Windows xp. I don't suppose that makes a difference....

And I guess you wouldn't see this on the build server since you would never run mvn install twice.

So, when on Windows xp, you had generally the same setup for package-info.java files? There was a change that we recently made so that annotation statements on package declarations are read and stored by the compiler. This was a change to get a piece of gpp working. I wonder if this could be a cause.

What version of g-e-c are you using?

Oh that could be it! Last I tried this I was probably on an older version of g-e-c. I'll try a different version and let you know what I find.

That did it! g-e-c 2.5.1 is broken for me. g-e-c 2.5.1-1 works just fine. So something between those versions is causing the problem.

Thanks for following up. I am resolving this as fixed, but please re-open if this happens again.

So does that mean it is fixed in trunk? I thought 2.5.1-1 was an older version that 2.5.1....

No, 2.5.1-1 is the next release after 2.5.1. Is that not considered a greater version in the maven world? I had assumed that the same rules would apply from the OSGi world, where 2.5.1 is less than 2.5.1.1.

I am trying to find the maven documentation for version comparisons, but there is nothing that clearly states the rules. The closest I found is this, but even that is unclear about comparing these kinds of versions.
http://mojo.codehaus.org/versions-maven-plugin/version-rules.html

Well regardless when 2.5.2 comes out I will mark it as 2.5.2-01 just in case I need to put out other releases of the maven support between micro releases of Groovy-Eclipse.

Yup you are right. See here for details: http://docs.codehaus.org/display/MAVEN/Versioning

Still, I think it is better to be more explicit with version names and the next release will be 2.5.2-01.