Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(maven-module) : Separate Java/Groovy sources to different modules #12

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

KilianStein
Copy link

Hi Pierre-yves

Here my proposition to separate one java core to Groovy's script.

ContextAccess-core : contains java class
ContextAccess-modules : contains groovy class
ContextAccess-parent : contains all version and configuration (usefull when you need to update versions)
ContextAccess : main pom.xml -> target will contain all data for a release

What do you think of it?

@pierre-yves-monnet
Copy link
Contributor

hello,
The conflicts are too much important to be resolved by the tool.
I thinks the decomposition by src/main/groovy and src/main/java is more easy to handle then "core" and "modules" (note that the groovy is the core).

Is that possible to keep this construction ?
Thanks

@KilianStein
Copy link
Author

here the merge :) !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants