java - Maven / eclipse project structure -
i still new maven, have how want need break on again.
here scenario:
i need write 2 different server applications, utilize identical core functionality; just, done framework different. 1 server application easy/simple - it's done - whereas other lot more complicated.
the code written in dependency injection style (using guice, if matters), should extremely easy break apart.
my question this: how construction projects in eclipse, using maven? set 3 different projects, like:
server-core server-appeasy server-appcomplicated
where each server have it's own pom. or, maintain in 1 project? need able recompile appeasy
in, say, month now, while work on appcomplicated
. classes appeasy
in subpackage. note: core
not work without @ to the lowest degree mock dependency injection. doesn't have main
class.
all thoughts appreciated, on things haven't thought of.
i have construction this:
/server /server-core pom.xml /server-appeasy pom.xml /server-appcomplicated pom.xml pom.xml
so each project has own pom.xml allows build project in isolation.
however parent folder has pom.xml, build projects if run. can including projects modules in parent pom.
e.g. in parent pom.xml
<modules> <module>server-core</module> <module>server-appeasy</module> <module>server-appcomplicated</module> </modules>
you can utilize managed dependencies in parent pom tio allow centralise external dependency , plugin version numbers.
java eclipse maven project-management
No comments:
Post a Comment