+1 (non-binding), tested with Java 8 on Windows 10 and Linux, both
personal projects and at work
- Eric L
On 2019-04-04 21:55, Karl Heinz Marbaise wrote:
Hi,
We have solved 42 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12338966
There are issu
Hi,
I think I found a place where you can add the verification of read-only
Mojo parameters, see [1]
For few tests looks it works correctly, we have one ITs failing [2].
Could you help with more testing? The code can be found in MNG-5001 branch
and compiled version - ready for download from our CI
@Parameter( defaultValue = "${mojoExecution}", readonly = true )
private MojoExecution mojo;
private void verifyRemovedParameter( String paramName )
{
Xpp3Dom configDom = mojo.getConfiguration();
if ( configDom != null )
{
if ( configDom.getChil
I want to observe a list of config parameters (names) in MOJO plugin
without injecting @Param for each.
If the customer still uses old parameter, the MOJO wouldn't know it.
Therefore I want to read the list of paramaters. And if he stil uses the
old name, the plugin would fail with a hint saying h
Am 2019-04-05 um 11:39 schrieb Robert Scholte:
Just wondering why this is not 1.1.2, updating versions and a bugfix
don't reflect the 1.2.0 to me.
It contains a huge bump in the Resolver version. I thought this would
justify this bump too.
Michael
On Mon, 01 Apr 2019 22:49:21 +0200, Michael
Just wondering why this is not 1.1.2, updating versions and a bugfix don't
reflect the 1.2.0 to me.
+1
Robert
On Mon, 01 Apr 2019 22:49:21 +0200, Michael Osipov
wrote:
Hi,
We solved 11 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12345231
T
Am 2019-04-01 um 22:49 schrieb Michael Osipov:
Hi,
We solved 11 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12345231
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20res
Thank you very much for confirming Hervé. It would be nice if we had a way
to identify that the value was set and then take an appropriate action in a
custom plugin forthe time being.
Has anybody done that to workaround the issue maybe?
On Fri, Apr 5, 2019 at 8:21 AM Hervé BOUTEMY wrote:
> sadl
+1 (non binding)
built from source with jdk8
used in some big and complex project with JDK-11 + linux
Enrico
Il giorno ven 5 apr 2019 alle ore 07:36 Francois Papon
ha scritto:
>
> +1 (non-binding)
>
> Thanks!
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 04/04/2019 à 23:55, Karl Hei
