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

Should biotextmining be a parent pom? #4

Open
pvilaca opened this issue Oct 15, 2019 · 1 comment
Open

Should biotextmining be a parent pom? #4

pvilaca opened this issue Oct 15, 2019 · 1 comment

Comments

@pvilaca
Copy link
Contributor

pvilaca commented Oct 15, 2019

The biotextmining could be a parent pom with the following children poms:

  • core
  • process
  • machinelearning
  • clustering
  • processesgate8
  • semanticanalysis

The Pros for this change are:

  • easier deploy of all the packages
  • organised code into the parent
  • better policy to change versions, when the parent change version all the children also change its version according to parent.

The Cons for this change are:

  • ?

Give me feedback on this..

@Ru13en
Copy link
Contributor

Ru13en commented Oct 15, 2019

That can be a good idea, but I think that cannot be done/or sometimes it doesn't make sense, because packages like machinelearning or sematicanalysis are not always bundled in the same version (only if core package has breaking changes, dependent packages can be upgraded accordingly to the new api).
For instance, for @ note2, we normally make a version upgrade to all are required plugins (except semanticanalysis that i think is not being used on it).
For anotedaemon, you only need the core and process packages, so upgrading versions in other packages without any change doesn't make much sense...

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

No branches or pull requests

2 participants