multi-module

问题 We need a base play framework projects which contains other play and scala projects as module. Those inner independent projects can have different javascript frameworks and build system like webpack, gulp, etc. So I tried the PlayRunHook from https://www.playframework.com/documentation/2.4.x/SBTCookbook . Single project hooking working as expected. But, unable to get it right on multi module project. Some code samples... Project Structure base/build.sbt name := """base""" version := "1.0

问题 I'd like to work on two different versions of the same multi-modules maven project under eclipse. Unfortunately, when you import a multi-module maven project under eclipse, you can change the parent module project name yourself, to prevent conflicts, but not the child modules projects names . Child modules are imported as root projects, named after the module name. Apparently there is no way to rename them during import. In an ideal scenario, I'd like to keep the pom as it is . Obviously I'd

问题 I have several projects that all have a similar Maven build. Each of the project POMs extend from a parent POM containing all of the common dependencies, plugins, etc. that are available to each project. I also have a multi-module POM, currently separate from the parent POM. The purpose of this multi-module POM is to have a single place I can run a target on all of the modules with one command. If I try to run a plugin, say JS Duck, off of the multi-module POM, I get the following output

问题 There is a multi-module project. Inside the child I need to do some complicated stuff (integration test with deploying to application server and so on). So there is an integrationtest child, and from this module I need the root of the parent to reach other modules. I do not want to use "..". There is a property in integrationtest POM: <properties> <main.basedir>${project.parent.basedir}</main.basedir> ... </properties> And there is an antrun plugin with the following content: <plugins>

问题 The problem to which I cannot find a nice, scalable solution: I have a project that delivers multiple flavours of the given artifact. This has been set up as a multimodule project, currently with 3 modules: /flavour1_module /flavour2_module /flavour3_module The thing is that I have another 50 projects that need to be setup in the same way, i.e. delivering the 3 flavours. Solutions considered: turning the already created multimodule project into a parent for all other 50 projects Cons: It just

问题 We've got a multi-module project using Eclipse and Maven. The only way I could get it to work in the past was to use a flat layout for the projects, where the parent module was a peer to the other modules. This worked fine with m2eclipse and Subversion. Now we'd like to move to Git and GitHub. I'd like to expose the entire project, along with all the modules, as a single project on GitHub. The problem is that EGit, the Eclipse/Git plugin, wants to manage projects one at a time, not groups of

问题 I have searched for such a question without finding anything, so here I go. I have a multi-module maven project. Multiple modules all inherit the same parent, where common dependencies are defined. Among them, there is one my own modules, a 'common' one, where some common functionality is implemented. My question is: What would be a better practice for common dependencies: Define them all explicitly in the parent, like I currently do? Or define them in a 'common' module, which other modules

问题 Similar question here. I would like to get ONE resulting WAR to be deployed from 3 different maven modules. The war modules are absolutely non-conflicting : First one that has Java classes and some WEB-INF/artifacts Second one are just API - interfaces - that must be either already present in container or part of the resulting war (that's what I want) Third one with Implementation classes, WEB-INF/artifacts ( spring infrastructure, web.xml, etc) First one depends on interfaces and

问题 My question is: How can I generate multiple executable Jar files (incl. dependencies) for a SWT application according to the target os/architecture at once using maven? I have created a SWT application, which have to run on different operating systems and architectures. The project is a Maven multi-module project including a parent POM. project-pom.xml (packaging = pom, specify SWT dependencies) `- application-module (inherit SWT dependencies) `- pom.xml (packaging = jar) `- domain-specific

问题 Is there any way to share resources between modules of a parent project in Maven? For example, I would like to specify one log4j.properties file for all the modules in a multi-module Maven project. Generally, I use Eclipse IDE to create the parent project by choosing a general project and then convert it to a Maven project by specifying a packaging of pom . This creates a "clean" project structure without src and etc. folders. I wonder where such a shared resource should be put in this case.