Major
Detail
Bugfix
Major
Detail
#26382
Error messages "Duplicate tag name..." when starting an application in the IDE from a TL-Studio
#26405
TTypeRewriter logs warning "Unable to resolve items by external reference" also unnecessarily
#26431
Changed superclass relationship leads to changed attribute list in the form editor only after a restart
Enhancement
- Log message "Duplicate tag names" when starting the application
- Remove redundant library dependencies from the Eclipse classpath.
- Separate parent modules and GroupIds for tl, project, vw.
- IDE startup from an incomplete workspace (boot directly from the Maven repository).
- Maven build of GWT modules.
- WAR build via Maven.
- Overlay dependent modules.
- Generate metaConf.txt.
- Apply layout overlays.
- Merge theme settings.
- Test execution via Maven.
- Fixing failing tests.
- Remove test errors due to "known bugs".
- Integrate type indexer in Eclipse directly from Maven repository.
- Automatic translations from Java-Doc. Must be triggered manually during development via a launch config.
- Deploy in Nexus from Maven build.
- Consider deploy overlays.
- Remove studio overlays (each build is a studio build).
- Src strip/class postprocess in the build (TL-Studio)
- Maven archetype(s) for TL modules.
- Docker deploy from Maven build results.
- Solution for parallel build (build repository is workspace-local).
- Solution for "system dependencies" for JARs that do not originate from an official Maven repository. An inner install module can install the artifact into the local repository before the main module is built.
- Remove checked-in external libraries.
- Release process
- Update the TopLogic version. mvn versions:set versions:set-property -Dproperty=tl.version -DnewVersion=7.5.0-SNAPSHOT
- ~~ Commit the new version in SVN ~~ Cannot be made to work via the Maven release plugin.
- Setup of an application purely from the TopLogic Maven repository.
Optional
- Remove superfluous Ext modules.
- ~~ Remove resources from the Java source directories. ~~
- ~~ Use web JARs instead of copied libraries. ~~
- Search for an alternative to origin.properties. A file /license/THIRD-PARTY.txt is generated in the deployment, which can be retrieved by the application.
- Replacement for Ant-Tooling for
- Normalization of layout XMLs (currently possible via Lauch-Config for individual files).
- Normalization of resource files (currently possible via Lauch-Config for individual files).
Code migration
- Create pom.xml from the current Eclipse classpath per module.
- Convert own modules to Maven modules(Configure > Convert to Maven project).
- Remove the configuration option test-no-hard-icon-references in test.com.top_logic.util.AbstractTestAll$GlobalConfig from the modules.
- Delete your own version classes (derivatives of AbstractVersion) and version.properties.
- Delete your own ServletContextListener and remove it from the web.xml of the module.
- In launch configurations, reset the class path to the default.
See also
doc:maven
Test
- Refactoring, no additional test.
- Tests now with mvn -DskipTests=false test in tl-parent-all.