YES!! That is exactly what I need/want. Sorry if I wasn't clear before, but
I'm definitely not for the embedding of command lines in he pom. Now that I
understand where you're coming from, I can completely agree with you that
embedding this stuff in a pom would definitely lead to cut-n-paste code
which s why I'm actively moving nearly 100 dev's from ant to maven 2
starting with my project.

Wb

On 9/20/05, John Casey <[EMAIL PROTECTED]> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> that sounds perfectly sane, except it sounds like you only need an API
> for calling a java main() method and handling output than an actual
> plugin. Once you have that API, you're set, it sounds like...then your
> plugin can depend on that api, and give it the stream consumers for
> sterr/stout and stream provider for stdin, I guess.
>
> I suppose I misunderstood where you were going with the
> maven-java-plugin. You're after more of a main() support API than an
> actual java-plugin, since you're writing the plugin yourself. Correct?
>
> - -john
>
> Wendell Beckwith wrote:
> | I just re-read you email and I'm confused by your comment, please
> clarify if
> | possible. But isn't what I've been hopefully explaining is the
> creation of a
> | mojo that wraps a command line process. I have written the mojos
> (agitate
> | and dashboard) an users only need to reference the plugin in their build
> | element. If the defaults are right for them, say they have a 80% code
> | coverage target instead of the default of 70% then they can add a
> <coverage>
> | element to the <configuration> element for the plugin. Now the plugin
> takes
> | the prams and puts then in the correct order and that is where I'm
> currently
> | am. I would like to have a maven-java-plugin or something like it that
> my
> | plugin can depend on to actually execute the process and tie its output
> | stdout and stderr back to my process. That's all I need. I'm not
> advocating
> | giving users the ability to execute any java command from their pom.
> |
> | This is my 1st m2 plugin so if I'm now one of those clueless users, then
> | please correct me where I'm wrong.
> |
> | Wb
> | On 9/20/05, John Casey <[EMAIL PROTECTED]> wrote:
> |
> |>-----BEGIN PGP SIGNED MESSAGE-----
> |>Hash: SHA1
> |>
> |>
> |>I guess I don't understand what's wrong with writing mojos to wrap
> |>specific command-line-driven use cases...?
> |>
> |>- -john
> |>
> |
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (GNU/Linux)
>
> iD8DBQFDMFEWK3h2CZwO/4URAveWAKCDHwHQN8WHKYx0V7YtI1mto4x4mgCdG+v9
> pTLGzK9uJsmhto/wMtt1+vo=
> =NYSU
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to