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

Watch mode improvements #318

Closed
cescoffier opened this Issue Aug 28, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@cescoffier
Member

cescoffier commented Aug 28, 2014

Right now the watch mode requires 3 processes:

  1. The Maven process launched by the user
  2. A second Maven process monitored and relaunched when the pom file is modified
  3. The Wisdom server.

The second instance is pretty heavy. In addition, it executes the build twice, which can be very slow. In addition, if the pom file contains issue, the watch mode is interrupted abruptly.

Another way to handle the pom file modification need to be implemented. It should:

  1. reduce the number of process requires
  2. support pom file problems

@cescoffier cescoffier added this to the 0.7 milestone Aug 28, 2014

@cescoffier cescoffier self-assigned this Aug 28, 2014

@cescoffier

This comment has been minimized.

Show comment
Hide comment
@cescoffier

cescoffier Aug 28, 2014

Member

Obviously this new version should be able to reload the Maven model on the fly at runtime.

Member

cescoffier commented Aug 28, 2014

Obviously this new version should be able to reload the Maven model on the fly at runtime.

@cescoffier cescoffier modified the milestones: 0.7, 0.6.3 Sep 1, 2014

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