[GRADLE-3050] No Scala bytecode produced when building mixed Scala/Java project with clashing filenames Created: 18/Mar/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 2


 Description   

I have a mixed Java/Scala project with the following structure:

___bar

____src
  ____test
    ____scala
      ____a
        ____b
          ____FooTest.scala
___foo
____src
  ____main
    ____java
      ____a
        ____b
          ____Foo.java
    ____scala
      ____a
        ____b
          ____Foo.scala

In Foo.java the Foo interface is defined, while in Foo.scala the FooComponent trait and the FooComponentImpl object are defined.

When assembling the foo.jar no Scala bytecode is produced, thus subproject bar cannot even test compile.

I have created a simple project to reproduce here [1]https://github.com/sirocchj/name-clash

Tested with:

$ gradle --version

------------------------------------------------------------
Gradle 1.10
------------------------------------------------------------

Build time: 2013-12-17 09:28:15 UTC
Build number: none
Revision: 36ced393628875ff15575fa03d16c1349ffe8bb6

Groovy: 1.8.6
Ant: Apache Ant(TM) version 1.9.2 compiled on July 8 2013
Ivy: 2.2.0
JVM: 1.7.0_45 (Oracle Corporation 24.45-b08)
OS: Mac OS X 10.9.2 x86_64

----------------------------------------------------------------------------------------
[1] https://github.com/sirocchj/name-clash

 Comments   
Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:38:32 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.