[#IDEABKL-5391] Allow Pluggins to be Project Defined.

IDEA: Backlog

Allow Pluggins to be Project Defined.

Created: 15 Apr 08 16:32 Updated: 13 Aug 08 04:38

Component/s:

Plugin Support. API

Affects Version/s:

None

Fix Version/s:

None

Original Estimate:	Unknown	Remaining Estimate:	Unknown	Time Spent:	Unknown
Environment:	« Hide OS: Windows XP JDK: JDK 1.5.0 IDEA: 7.0 Build: 7757 Show » OS: Windows XP JDK: JDK 1.5.0 IDEA: 7.0 Build: 7757

Build:	7,757
Severity:	Medium

Description

« Hide

It would be NICE if we could have Pluggins Defined Per Project. This would address the following:

1.) This would reduce the "noise" in the IPRs generated from Pluggins.
2.) it would allow Teams to define what is needed.
3.) It could improve performance by allowing a team to determine if a plug is needed or not ( reducing pluggins increases the performance ).

User pluggins could be used, but have the persisted information directed to something other than the IPR like the IML?

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Dmitry Jemerov - 15 Apr 08 16:41

A plugin may have components which are initialized before any project is loaded, and unloading plugins or plugin components is not supported. Thus the current architecture does not allow us to implement per-project plugins.

[ Permlink | « Hide ]

Philip Senger - 17 Apr 08 19:38

Dmitry,

When I wrote this up, I understand this would be a massive architectural change. I respect your hesitation to deal with such a large issue.

However, consider this... the number ONE problem with our team is the conflicts generated from checked in IPRs... which HAVE to be checked in because they have the Module Dependency, Libraries, etc. Jet Brains has to address this problem. I have worked at several clients now, and ALL of them had the same complaint... So, either move the Pluggin persisted state out of the IPR or move the Module Dependency stuff out to something else. SOMETHING has to give here we have had this problem since version 1.0 of IntelliJ.

Best Regards,
Philip A. Senger

[ Permlink | « Hide ]

Dmitry Jemerov - 18 Apr 08 00:07

Sorry, but exaggerations don't help you state your point. Support for third-party plugins first appeared in IntelliJ IDEA 3.0, so you weren't able to have this problem in v1.

Moving third-party plugin settings out of .ipr is relatively easy to do, in fact, but that's a very much different thing from per-project plugins.

[ Permlink | « Hide ]

Philip Senger - 13 Aug 08 04:38

Dmitry, And is there a back log that is assigned to move the third-party plugins out of the ipr? Despite my over reaching exaggeration of the problem, this is still the most talked about annoyance next to performance.