Re: mvn as used in Eclipse m2e gets parse error because of mistake in Maven 4.0.0 schema

2023-10-17 Thread Stanimir Stamenkov 

Tue, 17 Oct 2023 22:11:29 +0300, /Stanimir Stamenkov/:

I'm not familiar with this attribute but looking at 
:


You can control how child POMs inherit configuration from parent POMs 
by adding combine.children or combine.self 
attributes to the children of the configuration element...


If I'm reading this correctly, it says the attribute could/should be 
added to the children of the  element, and not on that 
element itself.  Then I don't know why it works in the command-line run.  
I guess others would provide more detail.


This also appears suggested by the documentation referenced in the same 
 element description:


https://maven.apache.org/pom.html#advanced_configuration_inheritance

--
Stanimir

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: mvn as used in Eclipse m2e gets parse error because of mistake in Maven 4.0.0 schema

2023-10-17 Thread Stanimir Stamenkov 

Tue, 17 Oct 2023 11:56:12 -0700, /David Karr/:


[...]
 cvc-complex-type.3.2.2: Attribute 'combine.self' is not allowed to
appear in element 'configuration'.

I, along with multiple other people, assumed that this indicates a bug in 
m2e, because it clearly works in the command-line build.  However, it was 
pointed out that m2e is actually USING the defined schema defined in the 
boilerplate of a pom.xml, instead of ignoring it, and if you open up that 
schema, it clearly shows the lack of an "attribute" element in the 
"configuration" complex-type.


So, clearly mvn is using that attribute, but I'm guessing it's not doing 
any schema validation, or builds using that attribute would fail.


I'm not familiar with this attribute but looking at 
:


You can control how child POMs inherit configuration from parent POMs by 
adding combine.children or combine.self 
attributes to the children of the configuration element...


If I'm reading this correctly, it says the attribute could/should be 
added to the children of the  element, and not on that 
element itself.  Then I don't know why it works in the command-line run. 
 I guess others would provide more detail.


--
Stanimir

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: mvn as used in Eclipse m2e gets parse error because of mistake in Maven 4.0.0 schema

2023-10-17 Thread Gary Gregory 
I've seen that in Eclipse for a long time.

Gary

On Tue, Oct 17, 2023, 2:57 PM David Karr  wrote:

> I have a feeling this has been covered before, but I'll ask just in case.
>
> I have a pom.xml that inherits from a parent pom, and the child pom has the
> following plugin definition:
> --
> 
>   maven-compiler-plugin
>   3.8.0
>   
> 11
> 
>   
> org.projectlombok
> lombok
> 1.18.30
>   
> 
>   
> 
> --
>
> Notice the "combine.self" attribute. In a command line mvn build, this does
> exactly what it needs to, completely overriding the plugin configuration
> inherited from the parent pom.  If I don't have that, it results in errors
> because it "merges" the plugin configs by default.
>
> What's annoying is that if I open this pom.xml in Eclipse, with the m2e
> plugin, I get the following error on that line:
>
> cvc-complex-type.3.2.2: Attribute 'combine.self' is not allowed to
> appear in element 'configuration'.
>
> I, along with multiple other people, assumed that this indicates a bug in
> m2e, because it clearly works in the command-line build.  However, it was
> pointed out that m2e is actually USING the defined schema defined in the
> boilerplate of a pom.xml, instead of ignoring it, and if you open up that
> schema, it clearly shows the lack of an "attribute" element in the
> "configuration" complex-type.
>
> So, clearly mvn is using that attribute, but I'm guessing it's not doing
> any schema validation, or builds using that attribute would fail.
>
> I have a feeling this situation has been in place for a long time.
>

mvn as used in Eclipse m2e gets parse error because of mistake in Maven 4.0.0 schema

2023-10-17 Thread David Karr 
I have a feeling this has been covered before, but I'll ask just in case.

I have a pom.xml that inherits from a parent pom, and the child pom has the
following plugin definition:
--

  maven-compiler-plugin
  3.8.0
  
11

  
org.projectlombok
lombok
1.18.30
  

  

--

Notice the "combine.self" attribute. In a command line mvn build, this does
exactly what it needs to, completely overriding the plugin configuration
inherited from the parent pom.  If I don't have that, it results in errors
because it "merges" the plugin configs by default.

What's annoying is that if I open this pom.xml in Eclipse, with the m2e
plugin, I get the following error on that line:

cvc-complex-type.3.2.2: Attribute 'combine.self' is not allowed to
appear in element 'configuration'.

I, along with multiple other people, assumed that this indicates a bug in
m2e, because it clearly works in the command-line build.  However, it was
pointed out that m2e is actually USING the defined schema defined in the
boilerplate of a pom.xml, instead of ignoring it, and if you open up that
schema, it clearly shows the lack of an "attribute" element in the
"configuration" complex-type.

So, clearly mvn is using that attribute, but I'm guessing it's not doing
any schema validation, or builds using that attribute would fail.

I have a feeling this situation has been in place for a long time.

Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14

2023-10-17 Thread Tamás Cservenák 
Yes, I agree.

Created https://issues.apache.org/jira/browse/MNG-7913

On Tue, Oct 17, 2023 at 4:31 PM Konrad Windszus  wrote:

> I think we should revise the decision to not backport
> https://issues.apache.org/jira/projects/MNG/issues/MNG-7587 <
> https://issues.apache.org/jira/projects/MNG/issues/MNG-7587?filter=reportedbyme>
> to Maven 3.9.x…
>
> > On 16. Oct 2023, at 22:08, Garret Wilson 
> wrote:
> >
> > On 10/16/2023 4:59 PM, Tamás Cservenák wrote:
> >> You'd use Plexus?  In 2023?
> >
> > I don't know what I'd use. I'm asking. I haven't written a Maven plugin
> yet. I'm just reading the latest documentation, and the [Plugin Developers
> Centre](https://maven.apache.org/plugin-developers/) seems to say at
> https://maven.apache.org/maven-jsr330.html that I either have to use
> Plexus or JSR-330, and you just told me I can't use JSR-330, so that leaves
> Plexus.
> >
> > If I'm not understanding the documentation correctly, please point out
> what I'm missing.
> >
> >> …
> >> In other words: whatever is "managed by sisu, should be max Java 14"
> >> bytecode in current release Maven versions. Naturally, this does NOT
> apply
> >> to ANY code, just those being JSR330 (and Mojo) annotated.
> >
> > Maybe you are saying I can write a Maven plugin without using Plexus or
> JSR-330? So dependency injection in Maven Plugins is optional? The page at
> https://maven.apache.org/maven-jsr330.html makes it seem like dependency
> injection in a Maven Plugin is a common thing.
> >
> > (Maybe your announcement makes perfect sense to those who have written
> Maven plugins before. In the meantime I'm reading the online documentation
> and trying to understand how this will affect me once I write a plugin.)
> >
> > Garret
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
>
>

Re: Authoring Maven Mojos for Maven 3.9.x - Maximum bytecode version=Java14

2023-10-17 Thread Konrad Windszus 
I think we should revise the decision to not backport 
https://issues.apache.org/jira/projects/MNG/issues/MNG-7587 

 to Maven 3.9.x…

> On 16. Oct 2023, at 22:08, Garret Wilson  wrote:
> 
> On 10/16/2023 4:59 PM, Tamás Cservenák wrote:
>> You'd use Plexus?  In 2023?
> 
> I don't know what I'd use. I'm asking. I haven't written a Maven plugin yet. 
> I'm just reading the latest documentation, and the [Plugin Developers 
> Centre](https://maven.apache.org/plugin-developers/) seems to say at 
> https://maven.apache.org/maven-jsr330.html that I either have to use Plexus 
> or JSR-330, and you just told me I can't use JSR-330, so that leaves Plexus.
> 
> If I'm not understanding the documentation correctly, please point out what 
> I'm missing.
> 
>> …
>> In other words: whatever is "managed by sisu, should be max Java 14"
>> bytecode in current release Maven versions. Naturally, this does NOT apply
>> to ANY code, just those being JSR330 (and Mojo) annotated.
> 
> Maybe you are saying I can write a Maven plugin without using Plexus or 
> JSR-330? So dependency injection in Maven Plugins is optional? The page at 
> https://maven.apache.org/maven-jsr330.html makes it seem like dependency 
> injection in a Maven Plugin is a common thing.
> 
> (Maybe your announcement makes perfect sense to those who have written Maven 
> plugins before. In the meantime I'm reading the online documentation and 
> trying to understand how this will affect me once I write a plugin.)
> 
> Garret
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>

[ANN] Apache Maven Reporting Exec 2.0.0-M11 released

2023-10-17 Thread Michael Osipov 
The Apache Maven team is pleased to announce the release of the Maven 
Reporting Exec version 2.0.0-M11.


https://maven.apache.org/shared/maven-reporting-exec/


Release Notes - Maven Shared Components - Version 
maven-reporting-exec-2.0.0-M11


** Dependency upgrade
* [MSHARED-1322] - Upgrade to Doxia 2.0.0-M8
* [MSHARED-1323] - Upgrade to Maven Reporting API 4.0.0-M8
* [MSHARED-1324] - Upgrade plugins and components (in ITs)


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Doxia Sitetools 2.0.0-M13 released

2023-10-17 Thread Michael Osipov 
The Apache Maven team is pleased to announce the release of the Apache 
Maven Doxia Sitetools, version 2.0.0-M13


https://maven.apache.org/doxia/doxia-sitetools/


Release Notes - Maven Doxia Sitetools - Version 2.0.0-M13

** Dependency upgrade
* [DOXIASITETOOLS-314] - Upgrade to Doxia 2.0.0-M8
* [DOXIASITETOOLS-315] - Upgrade to Maven Fluido Skin 2.0.0-M8 in 
default site descriptor

* [DOXIASITETOOLS-316] - Upgrade to Maven Reporting API 4.0.0-M8


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Reporting API 4.0.0-M8 released

2023-10-17 Thread Michael Osipov 
The Apache Maven team is pleased to announce the release of the Maven 
Reporting API version 4.0.0-M8.


https://maven.apache.org/shared/maven-reporting-api/


Release Notes - Maven Shared Components - Version 
maven-reporting-api-4.0.0-M8


** Dependency upgrade
* [MSHARED-1316] - Upgrade to Parent 40
* [MSHARED-1317] - Upgrade to Doxia 2.0.0-M8


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Site Plugin 4.0.0-M11 released

2023-10-17 Thread Michael Osipov 
The Apache Maven team is pleased to announce the release of the Maven 
Site Plugin, version 4.0.0-M11.


https://maven.apache.org/plugins/maven-site-plugin/


Release Notes - Maven Site Plugin - Version 4.0.0-M11

** Dependency upgrade
* [MSITE-981] - Upgrade to Doxia 2.0.0-M8
* [MSITE-982] - Upgrade to Doxia Sitetools 2.0.0-M13
* [MSITE-983] - Upgrade to Maven Reporting API 4.0.0-M8
* [MSITE-984] - Upgrade to Maven Reporting Impl/Exec 4.0.0-M11
* [MSITE-985] - Upgrade plugins and components (in ITs)


Please also note for this new major version: 
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Reporting Impl 4.0.0-M11 released

2023-10-17 Thread Michael Osipov 
The Apache Maven team is pleased to announce the release of the Maven 
Reporting Impl version 4.0.0-M11.


https://maven.apache.org/shared/maven-reporting-impl/


Release Notes - Maven Shared Components - Version 
maven-reporting-impl-4.0.0-M11


** Improvement
* [MSHARED-1314] - mark execute() final to avoid users extending 
reporting-impl implementation


** Dependency upgrade
* [MSHARED-1318] - Upgrade to Doxia 2.0.0-M8
* [MSHARED-1319] - Upgrade to Doxia Sitetools 2.0.0-M13
* [MSHARED-1320] - Upgrade to Maven Reporting API 4.0.0-M8
* [MSHARED-1321] - Upgrade plugins and components (in ITs)


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Doxia version 2.0.0-M8 released

2023-10-17 Thread Michael Osipov 
The Apache Maven team is pleased to announce the release of the Apache 
Maven Doxia, version 2.0.0-M8


https://maven.apache.org/doxia/


Release Notes - Maven Doxia - Version 2.0.0-M8

* Bug
* [DOXIA-706] - Sink.text(String, SinkEventAttributes) not properly 
supported by Xhtml5BaseSink


** Dependency upgrade
* [DOXIA-708] - Upgrade to Parent 40


Enjoy,

-The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [VOTE] Retire Maven Docck Plugin

2023-10-17 Thread Tamás Cservenák 
+1

On Tue, Oct 17, 2023, 00:50 Slawomir Jaranowski 
wrote:

> Hi,
>
> - Last release was in 2015
> - use Maven 2.2.1
> - we have a Maven Plugin Tools - which should be one project for build and
> check Maven plugins
> - no active development ...
>
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MDOCCK%20AND%20(%20resolution%20%3D%20Unresolved%20OR%20fixVersion%20%3D%203.0.0)
> - no working with current plugins
>
> I therefore propose that we retire maven-docck-plugin -
> https://maven.apache.org/plugins/maven-docck-plugin/
>
> If this vote is successful I will make one final release of the plugin,
> making it clear on the plugin site that it has been retired.
> After that the source code will be moved into read-only mode.
>
> The process for retiring a plugin is described here:
> https://maven.apache.org/developers/retirement-plan-plugins.html
>
> The vote is open for 72 hours.
>
> [ ] +1 Yes, it's about time
> [ ] -1 No, because...
>
> [1]
>
> --
> Sławomir Jaranowski
>