multi-project

Closure defined in root not visible in child

由 半城伤御伤魂 提交于 2019-12-10 22:45:22
问题 I have root project and subproject ( :child ). Root build looks like like this: def foo = { println("foo") } allprojects { task bar << { println(project.name + ":bar") } afterEvaluate { foo() } } Running gradle bar prints: foo foo :bar :child:bar child:bar parent:bar This make sense. However, IRL I need foo to be called by the child's build file (because I want it to be called only by some of the submodules). The documentation seems to be clear enough: In a multi-project build, sub-projects

How to include projects in multiproject build from master directory in Gradle?

由 本小妞迷上赌 提交于 2019-12-10 22:18:09
问题 Lets have this structure I am in subproject1 how to write my settings.gradle file to include subproject1 and subproject2 as subprojects of the root Project. My settings.gradle file is in master directory? I tried: include 'root:subproject1', 'root:subproject2' but nothing happened. From Gradle doc: If you execute Gradle from within a project that has no settings.gradle file, Gradle does the following: It searches for a settings.gradle in a directory called master which has the same nesting

sbt gives “configuration not public” for depending on test in subproject

由 我怕爱的太早我们不能终老 提交于 2019-12-10 20:10:20
问题 I have an sbt multi-project build, which works fine locally. It uses an external ivy settings file, and on my machine I have the sbt inter-project resolver added to my ivy settings file. However, when I build on Jenkins, I'd like to build each subproject separately , so that I can independently release each subproject. So on the Jenkins server, I have not included the inter-project resolver in the ivy settings file. The problem is, I have my main subproject configured in project/Build.scala

Define modules list which shall be build in Maven multiproject build

由 ￡可爱￡侵袭症＋ 提交于 2019-12-07 13:47:58
问题 I would like to use Maven -pl option to define which specific modules shall be included into reactor. The option works if list of module's paths is provided. Unfortunately, providing module's artifactIds is not working at all. Sonatype 'Maven: The Complete Reference' docs are using multiproject example where directories names are matching artifactIds: http://books.sonatype.com/mvnref-book/reference/_using_advanced_reactor_options.html Is it possible to use -pl option with artifactId? 回答1: Yes

Build multiproject Gradle on Jenkins

由 老子叫甜甜 提交于 2019-12-07 06:27:10
问题 I have a Gradle multiproject hosted in Mercurial repo. I would like to setup my Jenkins in such a way, that if I commit changes into only 1 subproject, then only that subproject will be built and published to my Nexus repo. Can somebody give me a hint? Or is it at all possible? 回答1: We sort of have this working. We create a project in Jenkins for each gradle subproject. And in the Jenkins configuration we build only the subproject by doing something like: gradle clean :<subproject>:build We

Webpack - Uncaught ReferenceError: webpackJsonp is not defined

由 ￡可爱￡侵袭症＋ 提交于 2019-12-06 08:09:28
问题 I'm developing a project that has two Angular 4 application and I'm having some problem configuring Webpack (3.5.2). Im getting this error in just one of the applications: Uncaught ReferenceError: webpackJsonp is not defined at styles.bundle.js:1 (anonymous) @ styles.bundle.js:1 vendor.bundle.js:1 Uncaught ReferenceError: webpackJsonp is not defined at vendor.bundle.js:1 (anonymous) @ vendor.bundle.js:1 main.bundle.js:1 Uncaught ReferenceError: webpackJsonp is not defined at main.bundle.js:1

how to tell gradle to build and upload archives of dependent projects to local maven

由 一曲冷凌霜 提交于 2019-12-06 04:07:12
问题 I have a multi-project problem that Gradle's documentation doesn't have any info on (and can't find on stackoverflow also). Any help/guidance will be greatly appreciated. Here are my project layouts: project LeftArm : produces a jar file project RightArm : produces a jar file project AllArms : depends on projects LeftArm and RightArm and produces a war file When I run 'gradle build uploadArchives' in AllArms project, it builds LeftArm and RightArm projects but it doesn't upload the jar files

Define modules list which shall be build in Maven multiproject build

由 我们两清 提交于 2019-12-05 18:28:47
I would like to use Maven -pl option to define which specific modules shall be included into reactor. The option works if list of module's paths is provided. Unfortunately, providing module's artifactIds is not working at all. Sonatype 'Maven: The Complete Reference' docs are using multiproject example where directories names are matching artifactIds: http://books.sonatype.com/mvnref-book/reference/_using_advanced_reactor_options.html Is it possible to use -pl option with artifactId? Yes, it's possible to do this. Take a look at mvn --help : -pl,--projects <arg> Comma-delimited list of

How do you handle multiple (overlapping) projects in trac?

由 匆匆过客 提交于 2019-12-05 15:30:21
问题 We are using trac and are really satisfied with it. However, out of the box, trac is best suited for single-project environments only. I'd be interested to hear about the various approaches people take to make it work with multiple projects nevertheless and their experiences with them. Are there any plugins to recommend? Any patches, tweaks or whatnots? Are you maybe even using an entirely different bug-tracking system that offers all of trac's functionality plus multi-project support? We

Gradle multiproject define dependency on root project

由 喜欢而已 提交于 2019-12-04 18:21:03
问题 I have a multi project gradle build, configured in this way: root | |---- projectA | |---- projectB I want to declare in the root/build.gradle a dependency for all nested projects, this is the file: subprojects { version = '1.0-SNAPSHOT' repositories { mavenLocal() mavenCentral() maven { url 'https://repository.jboss.org/nexus/content/groups/public-jboss/' } } } allprojects { dependencies { compile 'org.projectlombok:lombok:1.12.2' } } But when I execute the build, I have: * What went wrong:
订阅 multi-project