The loose app config generated by the 'deploy' goal does not include the "Maven descriptor" (pom.xml/pom.properties) though some LDT/WDT loose deployments do

[scottkurz]

Answering an internal user's question I learned that apparently the older "Liberty Developer Tools" / "WebSphere Developer Tools" Eclipse managed deployment (using WTP) configured entries adding the two archiver files to the app:

• The pom file, located in the archive in META-INF/maven/${groupId}/${artifactId}/pom.xml
• A pom.properties file, located in the archive in META-INF/maven/${groupId}/${artifactId}/pom.properties

In the liberty-maven-plugin-managed deployment through the 'deploy' goal, however, we do NOT add these two files as part of the app deployment. We don't treat them as part of the app.

It's still a bit unclear to me whether/when LDT/WDT deployments used entries like:

<dir sourceOnDisk=".....\target\m2e-wtp\web-resources" targetInArchive="/"/>

vs. when they added specific <file> entries for pom.xml and pom.properties. In playing around quick, I saw evidence of both. Maybe it depends what level of Maven integration gets activated.

I don't have time to dig further now, but this seemed like a useful writeup to add.