Hi Denis,
This option can be considered also. I have no arguments against this
solution.
In the same time I think Ignite developer will need pre-build distributive
(Jar) of plugin, probably in /idea subfolder.
So standalone ASF repo & [build/link to build] in main repo can be still
considered. This option can save checkout time, and reduce main repo size.
I hope this make sense. I would appreciate Igniter's opinion on this topic.
Sincerely,
Dmitriy Pavlov
ср, 18 июл. 2018 г. в 23:05, Denis Magda <dma...@apache.org>:
> Hi Dmitriy,
>
> Yes, I would have this tool at hands soon as I check out Ignite repo and
> start setting it up. However, instead of a new repo let's place it under
> {ignite}/dev-tools folder. What do you think?
>
> --
> Denis
>
> On Wed, Jul 18, 2018 at 4:37 AM Dmitry Pavlov <dpavlov....@gmail.com>
> wrote:
>
> > Hi Igniters,
> >
> > There is one mode widely used tool in Apache Ignite, abbreviation plugin
> > for Intelli J Idea. This plugin is used by almost all experienced Ignite
> > contributors.
> >
> > I would like to say thanks to all contributors which created this plugin:
> > vkazakov, sevdokimov, daradurvs, agoncharuk. And because this plugin is
> > also a part of our process I also want to place plugin code to ASF
> > repository.
> >
> > What do you think about placing plugin code to supplementary Apache
> > repository? Please share your vision till 24 July.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules#AbbreviationRules-IntelliJIdeaPlugin
> >
> >
> > https://github.com/dspavlov/ignite-abbrev-plugin
> >
>
