Steven E. Harris wrote:
"Richard S. Hall" <[EMAIL PROTECTED]> writes:
Perhaps I will add a "deprecated" comment in the title of the old
plugin's page and add a reference to the new one.
That would have saved me plenty of effort. I noticed both plugins, but
decided that "maven-osgi-plugin" /sounded/ like a newer name than
"maven-bundle-plugin", and went off and started using the former in
five different POMs.
Well, I didn't try to deprecate the original plugin at first because I
didn't want to presume to make a decision for the entire community since
the two plugins have quite different approaches. However, now that the
community is moving more toward the new plugin, it makes more sense to
somehow indicate this in the documentation. I have just added a note at
the beginning of the old plugin's documentation.
Transitioning back to maven-bundle-plugin didn't take too long, but I
do miss the auto-Activator detection feature, despite its lack of
specificity making me uncomfortable at first.
I like activator detection too and I have asked Peter to include an
instruction for it too. He complains that auto-detection is not perfect,
but in many cases it works well so I think we should include it in the
new plugin too. (Are you listening Peter?)
-> richard
