On Fri, 2 Sept 2022 at 12:03, Jonathan Bergh wrote:
> 1) Any info on what Release-Profile is - is the a NB provided profile? Its
> not configured in my settings/xml, so I assume its from the Maven conf
> packaged with NB?
AFAIK from Maven itself - eg. see https://issues.apache.org/jira/browse/M
Thanks both for your responses much appreciated - yes Profiles do work for
this, so I have done that.
1) Any info on what Release-Profile is - is the a NB provided profile? Its
not configured in my settings/xml, so I assume its from the Maven conf
packaged with NB?
2) On nbpackge, that looks very
On Fri, 2 Sept 2022 at 11:23, Jonathan Bergh wrote:
> Is there any way to keep an existing execution process configured but still
> be able to run maven projects which are under development?
>
> It would be a bit annoying to have to deconfigure that build step (Inno
> packaging) and run it manua
Hi:
Does NetBeans also breaks if you put your task in a separate Maven profile?
Regards.
On 02/09/2022 12:22, Jonathan Bergh wrote:
hi there,
It's clear that when using NB with Maven, NB uses
the exec-maven-plugin to run the jar, but configuring another process
using that plugin breaks the
hi there,
It's clear that when using NB with Maven, NB uses the exec-maven-plugin to
run the jar, but configuring another process using that plugin breaks the
Run / Run File facility in NB (Inno Setup, for example).
Is there any way to keep an existing execution process configured but still
be ab
