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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop the sample extension #2300
Comments
@wetneb: Hi, I would like to work on this issue if it's not already taken. Thanks. |
Concerning rearranging the source into new modules and namespaces, I have done that in |
Sounds good to me. It will be easier after the release is published to Maven central. |
@wetneb Are we still waiting for the release to start working on this? |
Unless you have ideas about how to do this without releasing to Maven, I would wait for this, yes. |
@wetneb: I suggest for a nightly release for this to proceed. Otherwise, I can release a snapshot that can be replaced later. |
Sure, go for it then :) |
Changing the title of this issue to reflect the opinion I voiced in #6426 (comment) |
I think it would still be useful to have a basic scaffold that people could use to start their own extensions, so I copied the sample extension to a dedicated repository here: |
We have a
sample
extension which is meant to demonstrate the basic scaffolding to get a minimalistic extension to work.This is not super useful since we already have quite a lot other extensions in the repository, which are actually maintained since they expose functionality that people use. There is a risk is that this extension does not get updated (because breaking it does not actually break anything for users).
Also, as an extension developer, I generally want to develop my extension in its own repository, with its own build system. The Maven set up for extensions included in this repository is not easy to translate to extensions developed outside the repository, since our own set up relies on the main OpenRefine classes being present in the reactor at build time.
Once #2254 is done, it should be easier to propose a clean Maven setup for external extensions. We could move the sample extension to a dedicated repository, which was created a long time ago but remained empty:
https://github.com/OpenRefine/refine-sample-extension
The text was updated successfully, but these errors were encountered: