rmcdouga

1. Add a ByteArrayDataSource
   This seems like an odd ommission, surely an in-memory data source makes sense and is trivial to implement (but no more trivial than FileDataSource). It would save people from having to implement this in many places.

2. Move Implementation tests into API project, convert to JUnit 5
   The jakarta.activation apis are a mix of API and implementation. Is there any reason why the implementation pieces are not tested within the API project? Having the tests closer to the code would ease the maintenance burdon and be more in line with modern practices. This will help new contributors.

3. Add "name" attribute

rmcdouga

<configuration>
	<!-- Turning down the wiremock logging -->
	<!-- based on https://stackoverflow.com/questions/44460834/cant-turn-off-debug-logging-for-wiremock -->
	<logger name="com.github.tomakehurst.wiremock" level="DEBUG" />
	<logger name="wiremock.org" level="DEBUG" />
	<logger name="WireMock" level="DEBUG" />
	<!-- wiremock has per endpoint servlet logging -->
	<logger name="/" level="DEBUG" />
</configuration>

rmcdouga

from: docx
to: markdown-smart-simple_tables-multiline_tables-grid_tables+pipe_tables+yaml_metadata_block-superscript-subscript-bracketed_spans-native_spans-link_attributes-raw_html+rebase_relative_paths+four_space_rule
extract-media: "./"
wrap: preserve
markdown-headings: atx
tab-stop: 2
shift-heading-level-by: 1
standalone: true
template: obsidian.md
filters:

rmcdouga

//DEPS com.thedeanda:lorem:2.2

package com._4point.aem.installer;

import java.io.BufferedReader;
import java.io.InputStreamReader;
import java.util.Arrays;
import java.util.List;

import com.thedeanda.lorem.Lorem;