Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish the plugin on Eclipse Marketplace #30

Open
nagromc opened this issue Nov 15, 2017 · 2 comments
Open

Publish the plugin on Eclipse Marketplace #30

nagromc opened this issue Nov 15, 2017 · 2 comments

Comments

@nagromc
Copy link

nagromc commented Nov 15, 2017

To make it easier to find for most users, maybe you should publish the plugin on the Eclipse Marketplace.

Maybe you should contact as well the EditorConfig mailing list to let them know your new plugin exists.

Thanks for your work 馃憤

@angelozerr
Copy link
Owner

To make it easier to find for most users, maybe you should publish the plugin on the Eclipse Marketplace.

Yes sure it's planed, but with @ppalaga we have created https://github.com/ec4j/ Before creating the update site we should:

  • stabilize ec4j and finish work on "services" part to provide a very clean integration of ec4j inside ec4e.
  • publish ec4j in maven repository
  • create a release of ec4e by @pascalleclercq
  • create an Eclipse MarketPlace

Maybe you should contact as well the EditorConfig mailing list to let them know your new plugin exists.

Yes it's planned too. @ppalaga do you think you could do that for ec4j? After that I will do that for ec4e.

But we need to wait release of ec4j and ec4e for that.

Thanks for your work 馃憤

Glad it please you:) Please create issues if you have some troubles or need to improve some things.

@ppalaga
Copy link
Contributor

ppalaga commented Nov 15, 2017

Maybe you should contact as well the EditorConfig mailing list to let them know your new plugin exists.

Yes it's planned too. @ppalaga do you think you could do that for ec4j? After that I will do that for ec4e.

Yes, I can. In between, some of the EditorConfig folks already know what we do implictly thanks to the bug reports we filed against their test suite :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants