Le mar. 11 févr. 2025 à 07:32, Guillaume Nodet <gno...@apache.org> a écrit :
> I think this discussion tends to go away from two important points. > > First, consumer poms NEED to be able to be read by Maven 3. > So you cannot really add any custom namespace, new elements or > anything that would be rejected by Maven 3. You can force the use > of a modelVersion > 4.0.0 in the consumer POM, though, but applying > that to all consumer poms would simply remove the main driver for it. > > The consumer POM is created starting from the EFFECTIVE pom, > which is computed as an object model in memory. We've long lost > the full DOM tree at this point, so we cannot really recreate it when > building the consumer POM. We do try to keep locations when > merging parents and profiles, so that it helps debugging when > printing the effective pom in verbose mode, but this is not sufficient > to write comments back. > We do not but we can, not sure there is much technical blocker to do. Ack it is not a quick win but it is very feasible. > > If people want the original POM with comments,etc..., why not using > the build pom instead ? We do upload it for this very purpose imho. > Cause it is no more maven 3 as you mentionned? > > > Le dim. 9 févr. 2025 à 20:30, Anders Hammar <and...@hammar.net> a écrit : > > > Hi, > > > > I and Robert did a Maven 4 presentation at Jfokus here in Sweden earlier > > this week. One of the main topics was of course build/consumer POM. > > After the talk we were approached by a couple of people from the audience > > who raised concern about comments in the build POM being removed in the > > published consumer POM. They thought that could be problematic for larger > > corporations who want, for example, copyright comments. > > > > Any thoughts on this? > > > > /Anders > > > > > -- > ------------------------ > Guillaume Nodet >
