All notable changes to this project will be documented in this file. See standard-version for commit guidelines.
0.1.0 (2024-03-19)
- add update:logs command to package.json (bebe39a)
- automated semantic versioning for pom.xml and package.json (2583086)
- initial auto-generate CHANGELOG.md setup (6653871)
- installed versions-maven-plugin (db31f5a)
- update README.md (f99c2b4)
- add new type to .versionrc (c2fbd80)
- commons-beanutils:commons-beanutils installed.
- PropertiesLoader JavaDoc
- README.md
- pom.xml
- PropertiesLoader Improved
- Configured
maven.yml
to create tag based onpom.xml
version. - Configured
maven.yml
to deploy release to mvn central and GitHub packages.
EnvPathParser
first implementation and JavaDocEnvPathParser
simple unit testsParametersProvider
in test package to facilitate testing with several, different parameters.
- Reworked GitHub
maven.yml
to only test in non-production branches and compile, test, package and deploy on production branches. - README.md Update
- Moved
DocConstants
topt/codeforge/toolertools/xml
to make it effectively Package-Private
- Unit tests in
pt.codeforge.toolertools.xml.XmlHandlerTest
- Tested
#getOptionalDomFromFile
- Tested
- JavaDoc to
pt.codeforge.toolertools.xml.XmlHandler
- Unit tests in
pt.codeforge.toolertools.xml.XmlHandlerTest
- Tested
#getOptionalDomFromFile
- Tested
- JavaDoc to
pt.codeforge.toolertools.xml.XmlHandler
- README.md
- pom.xml for integration with Maven Central
- Unit tests signatures in
XmlHandlerTest
for improved readability. - Separated
#getNodeFromXPath
unit test assertions for better readability.
- Maven Wrapper for smaller binary. Unecessary since "this is wibrary".
- Package name change to reflect new org. From
org.tooler-tools
topt.codeforge
. - Domain
pt.codeforge
now redirects to this repository -https://github.com/rikkarth/tooler-tools
.
- CHANGELOG.md
- Installed: Maven Wrapper
- Installed: JUnit Params
- Ability to retrieve single Node from XPath with XmlHandler.
- XmlHandler now handles XPathExpressions internally, getStringFromXPath and getNodeListFromXPath both now only require the expression to be provided as a String instead of an XPathExpression object.