Thanks for loking over my changes.
Mark Phippard wrote:
>That sounds like the right way to accomplish this, if it is a goal. My
>only question would be that this only makes sense to do if we know there
>are some other plugins out there that want to consume this extension
>point. Otherwise, it is a lot of work for something that could just be
>hard-coded. So, do we know that?
We don't know who will use the extesion point (if anyone). The only use
cases i could think of were a bug tracking system (ie a bugzilla or jira
issue number) and perhaps company defined meta data (perhaps for
documents). I am not really sure if we should even consider adding bug
tracking support directly into the core plugins. It would make more
sense to have them as optional components.
The main reason for using an extension point is to allow us to add
properties without requiring code changes (i really hate mixing data and
>PS - Your extension point Schema currently shows an error in the Problems
Could you send me the text of that error please? It doesn't show up for
me. The only thing i noticed is that the plugin.xml had some unicode
characters (i have removed them).
Received on Tue Nov 16 21:04:38 2004