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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ObjectFieldFactory as a separate library #401

Open
vaadin-miki opened this issue Sep 12, 2022 · 1 comment
Open

ObjectFieldFactory as a separate library #401

vaadin-miki opened this issue Sep 12, 2022 · 1 comment
Assignees
Labels
api All things related with adding, removing and modifying public API.
Milestone

Comments

@vaadin-miki
Copy link
Owner

Given the amount of dependencies and features, ObjectFieldFactory should probably be a separate library.

This should be implemented at the same time as #366 and #385.

@vaadin-miki vaadin-miki added the api All things related with adding, removing and modifying public API. label Sep 12, 2022
@vaadin-miki vaadin-miki added this to the Backlog milestone Sep 12, 2022
@vaadin-miki vaadin-miki self-assigned this Sep 12, 2022
@vaadin-miki
Copy link
Owner Author

this requires some reworking of the poms

looks like the parent module will actually become a parent pom as well - there will be three modules (demo, superfields, object-field-utils), two of which will be releasable to maven

also all profiles should be in the parent pom (as they will be reused)

vaadin-miki added a commit that referenced this issue Dec 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api All things related with adding, removing and modifying public API.
Projects
None yet
Development

No branches or pull requests

1 participant