nebula-plugins / nebula-plugins/nebula-project-plugin

Facet not being included in Jar

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Groovy
Stars
98
Forks
19
PR merge metrics
No merged PRs in 30d

Description

I create a facet "secondSrc" and everything seems fine. But when i do a gradle build i get a jar file that only has the classes from the main sourceset. And, here's my output

:clean
:compileJava
:compileGroovy UP-TO-DATE
:processResources UP-TO-DATE
:classes
:writeManifestProperties
:jar
:assemble
:compileTestJava UP-TO-DATE
:compileTestGroovy UP-TO-DATE
:processTestResources UP-TO-DATE
:testClasses UP-TO-DATE
:test UP-TO-DATE
:compileFunctionalTestJava UP-TO-DATE
:compileFunctionalTestGroovy UP-TO-DATE
:processFunctionalTestResources UP-TO-DATE
:functionalTestClasses UP-TO-DATE
:functionalTest UP-TO-DATE
:compileIntegTestJava UP-TO-DATE
:compileIntegTestGroovy UP-TO-DATE
:processIntegTestResources UP-TO-DATE
:integTestClasses UP-TO-DATE
:integrationTest UP-TO-DATE
:check UP-TO-DATE
:compileSecondSrcJava
:compileSecondSrcGroovy UP-TO-DATE
:processSecondSrcResources UP-TO-DATE
:secondSrcClasses
:build

BUILD SUCCESSFUL

It appears the facet is being executed after the java stuff is executed. This is on gradle 3.0 and 3.1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported build on Gradle 3.0 or 3.1 using a project with a secondSrc facet, then inspect the build output and resulting JAR. Trace why compileSecondSrcJava and secondSrcClasses run after jar; done means the JAR contains the facet's classes as well as the main source set.

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.