3 requests around plugin development


1/ create a plugin-dev forum.
-



It would naturally host technical, as well as "how do I write a plugin"
questions, that currently "pollute" the
- openapi
- plugin
but also the
- eap
- community
forums.




2/ open the tracker to plugins
-


1 plugin -> 1 tracker area.


If you require developers to register a unique root path
ex:
org.plugins.mylittleplugin.*

, then you could also enable the next request :


3/ cool handling of plugin caused stacktraces
-



By examining the stack trace, IDEA could find out it was caused by a plugin.
Using the list of registered plugin root paths, it could be redirected
to the proper tracker,
after telling the user it was caused by a plugin.

3 comments
Comment actions Permalink

>

1/ create a plugin-dev forum.
----------------------------


+1

>

2/ open the tracker to plugins
------------------------------
1 plugin -> 1 tracker area.

>

+1000

>

3/ cool handling of plugin caused stacktraces
---------------------------------------------

>

+100000000000000000000


0
Comment actions Permalink

1. the plugin-dev forum is only OpenAPI. Then "plugin" forum is plugin
request/support forum, i guess.
2. Yes, it will be very nice. I already say about it and ask for not profit
JIRA.
3. +1, but it not realy need.

Thanks!

--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Alain Ravet" <alain.ravet.list@wanadoo.be> wrote in message
news:bl8nch$27p$1@is.intellij.net...
>
>

1/ create a plugin-dev forum.
----------------------------

>

It would naturally host technical, as well as "how do I write a plugin"
questions, that currently "pollute" the
- openapi
- plugin
but also the
- eap
- community
forums.

>
>
>
>

2/ open the tracker to plugins
------------------------------
1 plugin -> 1 tracker area.

>
>

If you require developers to register a unique root path
ex:
org.plugins.mylittleplugin.*

>

, then you could also enable the next request :

>
>

3/ cool handling of plugin caused stacktraces
---------------------------------------------

>

By examining the stack trace, IDEA could find out it was caused by a

plugin.

Using the list of registered plugin root paths, it could be redirected
to the proper tracker,
after telling the user it was caused by a plugin.

>


0
Comment actions Permalink

On Mon, 29 Sep 2003 12:45:13 +0400, Alexey Efimov wrote:

2. Yes, it will be very nice. I already say about it and ask for not
profit JIRA.
3. +1, but it not realy need.


+1 for #3, it would be nice to keep all plugins under a common namespace.
But as you say, its not really needed. However, if plugins could register
some form of "ErrorHandlerInfo" interface which provides the Stack Trace
Handler info like:

- Name of plugin
- Base package for plugin ( any exception thrown starting with this
package would use the other information for bug submission.
- Contact email for plugin maintainer
- Bug Submission email address ( for receiving the stack trace )
- URL of Plugin Home page

--
"It's all in the heat of the moment, it's all in the pain..." Devy.
Mark Derricutt @ mark@talios.com @ talios.blog-city.com

0

Please sign in to leave a comment.