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

Create an archetype to easily write Watchers #251

Closed
Riduidel opened this Issue Jul 1, 2014 · 0 comments

Comments

Projects
None yet
2 participants
@Riduidel
Contributor

Riduidel commented Jul 1, 2014

This archetype should include all required dependencies, and provide a default class that is vastly documented (typically using the infos available in the doc).

More explanations ?

Adding a watcher is really straightforward. It's indeed linked
automatically to the watcher list. As you say, you can just declare your
watcher as a maven-plugin and 'voila'.

Yeah, after re-reading wisdom doc only once, I understood all that. And
this is cool. By the way, contrary to a full wisdom project, I found out
that wisdom watchers are ideal candidates for maven archetypes :
creation is quite straightforward, it's easy to push a correct pom
(while creating the wrong one is really easier), and it would give
really good starting point, as there is a typical way to call the
"processFile" method from the mojo execute method.

Definitely. Could you open an issue.

@cescoffier cescoffier added feature and removed feature labels Jul 3, 2014

@cescoffier cescoffier added this to the 0.6.1 milestone Jul 3, 2014

cescoffier added a commit that referenced this issue Jul 6, 2014

Refactoring of the Watcher's Mojo handling (internal or external) ass…
…ets.

This commit is a bit related to #251 in the sense it provides an improved API.

Signed-off-by: Clement Escoffier <clement.escoffier@gmail.com>

@cescoffier cescoffier closed this in 22ae663 Jul 7, 2014

cescoffier added a commit that referenced this issue Jul 7, 2014

Add documentation about #251
Signed-off-by: Clement Escoffier <clement.escoffier@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment