dashorst opened a new pull request, #1707:
URL: https://github.com/apache/wicket/pull/1707

   ## Summary
   
   - Adds a throwaway spike of a builder API for Wicket components under 
`org.apache.wicket.examples.builder.spike`: a `ComponentBuilder` base, scoped 
containers, forms, lists, links, Ajax links, buttons and check boxes in 
`Builders` and `CoreUi`, and an `EditableLabelBuilder` for the 
wicket-extensions in-place editors in `spike/extensions`. The `Ui` interface 
combines the core and extensions vocabularies.
   - Adds four example pages written against the builder: an index, a 
guestbook, a todo list and the editable labels. `BuilderApplication` mounts 
them, and the examples home page gets one link to it.
   - Wires `BuilderApplication` into 
`wicket-examples/src/main/webapp/WEB-INF/web.xml`.
   - Ports `build-versions.py` from Python 2 to Python 3 and replaces its 
hard-coded module list with a walk over the `<modules>` tree of the root 
`pom.xml`. Artifact IDs are now read from each pom instead of derived from 
directory names, so the `testing/` and `archetypes/quickstart` name mappings 
are gone. The hard-coded 
`org.apache.wicket.experimental.wicket8:wicket-experimental` entry is no longer 
emitted unless a reachable module pom declares that artifact.
   - No framework code changes. The classes are marked `SPIKE - throwaway` in 
their Javadoc.
   
   ## Testing
   
   - Not run: `BuilderSpikeTest`, added in this change, has not been run on 
this branch.
   - Not run: the full `mvn clean verify` required by AGENTS.md.
   - Not run: `build-versions.py` against the current tree. Its output has not 
been compared with the output of the Python 2 script on master.
   - Not run: the four example pages in a browser.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to