@atlassian/wrm-troubleshooting/dist/steps/verifyPomConfigIsValid.js

A tool that can help you with troubleshooting the configuration of webpack and Atlassian P2 project.

"use strict";
var __importDefault = (this && this.__importDefault) || function (mod) {
    return (mod && mod.__esModule) ? mod : { "default": mod };
};
Object.defineProperty(exports, "__esModule", { value: true });
exports.verifyPomConfigIsValid = void 0;
const chalk_1 = __importDefault(require("chalk"));
const paths_1 = require("../paths");
const pom_1 = require("../pom");
const types_1 = require("./types");
const verifyPomConfigIsValid = async (options, payload) => {
    const { pomFile, pomXml } = payload;
    const scanFolders = (0, pom_1.getScanFoldersConfig)(pomXml);
    if (!scanFolders) {
        const error = new Error(`The ${chalk_1.default.green((0, paths_1.getRelativePath)(pomFile))} file is missing the "${chalk_1.default.bold(pom_1.SCAN_FOLDERS_KEY)}" configuration.
📖 Check the guide on how to configure it:\nhttps://www.npmjs.com/package/atlassian-webresource-webpack-plugin#consuming-the-output-in-your-p2-plugin`);
        return (0, types_1.getFailedResult)(error);
    }
    return (0, types_1.getPassedResult)();
};
exports.verifyPomConfigIsValid = verifyPomConfigIsValid;
//# sourceMappingURL=verifyPomConfigIsValid.js.map