Open mxread opened 3 years ago
hola soy nuevo con esto y no se a que se refiere cuando dice : la aplicación de un @fix_1 o @fix_2
Hi @mxread,
I am able to verify it. Thanks for raising the bug and submitting the possible fixes. Your contribution is highly appreciated.
@developmentes, if you need assistance in implementing the fixes recommended by the reporter, I'd recommend you to go and seek assistance in the Payara Forum.
Hola @developmentes, La aplicación del @fix1 consiste en actualizar el pom.xml del proyecto (webapp) que deseas desplegar en payara. Para aplicar los fixes @fix2 y @fix3 debes:
Soy bastante nuevo en el tema pero al menos logré resolver esto. Si necesitas ayuda avisa.
hi,where to add this fix1 in pom.xml ?
Hi,
I'm using Payara Tools v1.3.0 (which, I assume is the latest version) and the problem is still there. I get the following when trying to run a project (which I know runs when I do it via Netbeans).
Any update on this ?
Description
I have tried to set up a vscode sample project on a windows 10 machine as described in Add Payara Server 5 to the Visual Studio Code Tutorial.
The server starts and stops fine, but deploying via right click context menu doesn't work. Build does not start and exits with a cryptic:
The problem seems to be a missing plugins section in the build section of the pom.xml generate by the maven javaee8 essentials archetype. If a plugin is declared without a groupId (e.g. as in NetBeans based projects), the same error occurs.
Applying @fix_1 and an ide restart removes this error.
But the build still does not start and exits with another message:
I could track down the second issue to:
Applying @fix_2 and an ide restart removes the second error. Build and deployment finish w/o any issue. Applying @fix_3 will eliminate further problems with missing/incomplete plugins.
Expected Outcome
Current Outcome
Environment
Fixes
@fix_1 Adding following lines to the build sections solves the issue with the first cryptic error message:
(Why is this missing in the maven archetype?)
@fix_2 Replacing the return line of parseBuild(build) removes the second error:
@fix_3 Adding null safety and complete null checks eliminates first error regardless of missing maven plugins.