We have a custom stack image, which we don't build in this repo, but assume it's built elsewhere
We have a custom Dockerfile mod'd to add the 'asset's dir
Let's try to capture a "binary" project but maybe using a different approach in Maven.
What if we were to define a POM packaging type project, with Liberty config in src/main/liberty/config/server.xml. Could we use say the assembly plugin to take a dependency WAR and copy it into target then find a devfile command to do inner loop dev?
Or, perhaps we should use the liberty-assembly packaging type, which I think was made for this purpose.
Since I don't know too many WARs already in Maven Central and don't want to have to employ the "Maven repo embedded in the Git repo trick/hack", maybe this would be a good starting point:
net.wasdev.wlp.sampleferret1.2war
One of the goals would be to use the stack's outer loop Dockerfile unchanged.
In https://github.com/mezarin/application-stack-ta-test we show one approach for providing a sample reflecting the output of a tool like Transformation Advisor.
We have a custom Dockerfile mod'd to add the 'asset's dir
Let's try to capture a "binary" project but maybe using a different approach in Maven.
What if we were to define a POM packaging type project, with Liberty config in src/main/liberty/config/server.xml. Could we use say the assembly plugin to take a dependency WAR and copy it into target then find a devfile command to do inner loop dev?
Or, perhaps we should use the liberty-assembly packaging type, which I think was made for this purpose.
Since I don't know too many WARs already in Maven Central and don't want to have to employ the "Maven repo embedded in the Git repo trick/hack", maybe this would be a good starting point:
One of the goals would be to use the stack's outer loop Dockerfile unchanged.