Re: Cutting Releases of JDeps and Scripting Plugins
I see no one objects. I will cut a release for jdeps as soon as possible. for the 'scripting' plugin maybe I will need more help than usual as it is the first release of ever. Thanks Enrico Il giorno mar 28 mag 2019 alle ore 14:11 Enrico Olivelli < eolive...@gmail.com> ha scritto: > Hi, > I would like to cut a release of JDeps plugin soon. > I have committed a fix for an annoying problem with MultiRelease Jars (1) > > It is time to cut a first release of Maven Scripting Plugin. > > Thoughts ? > > Enrico > > > [1] https://issues.apache.org/jira/browse/MJDEPS-23 > >
Re: proposal for maven-archetype to switch to dom4j 2.1.1 (and Java 8)
Hi Tony, I answered your question at Jira. The release Vote will start asap. Cheers Tibor On Mon, Jun 10, 2019 at 8:27 PM Homer, Tony wrote: > Tibor completed the work of removing dom4j library and reverted the change > that moves maven-archetype to Java 8 [1]. > This change mitigates the vulnerability to CVE-2018-1000632 while > retaining Java 7 compatibility. > In the JIRA I asked about when this can be released and Tibor suggested > that I ask the ML. > It seemed best to keep the discussion in the original thread for context, > although the subject is no longer accurate! > > Can maven-archetype 3.1.1 be released ASAP so that this fix is made public? > My interest (as described earlier in this thread) is to get the CVE > mitigation into m2e so that I can stop using a fork in my eclipse product, > but it is worthwhile for anyone who has a company policy that is aggressive > about CVEs. > Please let me know if there is anything I can do to help with this. > > [1] https://issues.apache.org/jira/browse/ARCHETYPE-568 > > Thanks! > Tony Homer > > On 6/5/19 , 5:52 AM, "Tibor Digana" wrote: > > I am working on a removal of dom4j library and use of Java XML API. > Sytwester, connect to the Slack pls. > > On Wed, Jun 5, 2019 at 8:28 AM Robert Scholte > wrote: > > > > What stops us developing on Java 8? > > > Maven project stops us. > > > > I think this deserves some clearance, because I have a different > opinion > > on this. > > It is quite natural that plugins start picking up and requiring a > more > > recent version of Java before Maven does. > > If there's a good reason to move forward (in this case to Java 8), I > don't > > mind doing that. > > With our plugin system, if they can't use this because they run > Maven on > > an older version of Java, they can lock the plugin version to the > last > > compatible one. > > Right now most environments are already running on Java 8 and won't > notice > > such upgrade. > > Also keep in mind there's a difference between Java for Maven > runtime and > > JDK for the compiler, these can be separated. > > I would love to hear from somebody that thinks he or she would be > blocked > > by such change, it shouldn't be an issue but maybe I'm missing a > detail. > > > > So if we can stay Java 7 compatible, that's fine but is not a > blocking > > requirement (especially since this plugin is not a lifecycle plugin). > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org >
Re: proposal for maven-archetype to switch to dom4j 2.1.1 (and Java 8)
Tibor completed the work of removing dom4j library and reverted the change that moves maven-archetype to Java 8 [1]. This change mitigates the vulnerability to CVE-2018-1000632 while retaining Java 7 compatibility. In the JIRA I asked about when this can be released and Tibor suggested that I ask the ML. It seemed best to keep the discussion in the original thread for context, although the subject is no longer accurate! Can maven-archetype 3.1.1 be released ASAP so that this fix is made public? My interest (as described earlier in this thread) is to get the CVE mitigation into m2e so that I can stop using a fork in my eclipse product, but it is worthwhile for anyone who has a company policy that is aggressive about CVEs. Please let me know if there is anything I can do to help with this. [1] https://issues.apache.org/jira/browse/ARCHETYPE-568 Thanks! Tony Homer On 6/5/19 , 5:52 AM, "Tibor Digana" wrote: I am working on a removal of dom4j library and use of Java XML API. Sytwester, connect to the Slack pls. On Wed, Jun 5, 2019 at 8:28 AM Robert Scholte wrote: > > What stops us developing on Java 8? > > Maven project stops us. > > I think this deserves some clearance, because I have a different opinion > on this. > It is quite natural that plugins start picking up and requiring a more > recent version of Java before Maven does. > If there's a good reason to move forward (in this case to Java 8), I don't > mind doing that. > With our plugin system, if they can't use this because they run Maven on > an older version of Java, they can lock the plugin version to the last > compatible one. > Right now most environments are already running on Java 8 and won't notice > such upgrade. > Also keep in mind there's a difference between Java for Maven runtime and > JDK for the compiler, these can be separated. > I would love to hear from somebody that thinks he or she would be blocked > by such change, it shouldn't be an issue but maybe I'm missing a detail. > > So if we can stay Java 7 compatible, that's fine but is not a blocking > requirement (especially since this plugin is not a lifecycle plugin). - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: hocon and json formats for the Project Object Model
Trying again in plain text. Sorry for the resends. Its Monday morning and I'm moving a bit slowly today... https://github.com/hunterpayne/maven-unbound Hunter On Monday, June 10, 2019, 4:15:32 AM PDT, Enrico Olivelli wrote: Hi, Hunter, I have received your email a bit corrupted. Did you put some ASCII art ? Did you add attachments ? I find your idea interesting. thank you Enrico Il giorno lun 10 giu 2019 alle ore 11:33 Hunter C Payne ha scritto: > Hello all, I've used Maven for probably 15 years now. I think its great > and want to thank you all for all your hard work. > I've written a quick Scala library that converts pom.xml files to/from > pom.json and pom.conf (Hocon) files. This allows for a much less verbose > way to specify pom files. The code I've written should also be suitable to > integrate into Maven proper (if you so choose) as it can construct the > Maven bean classes that represent a POM in the Maven source base. > > Here is a link to that library which I call Unbound. Hope everyone likes > this little project and thinks it helps promote Maven. Its not quite > complete yet as a bit more testing and debugging is necessary before it can > be used but I still wanted to broadcast the idea to see how everyone felt > about it. > > hunterpayne/maven-unbound > > | > | > | > | | | > > | > > | > | > | | > hunterpayne/maven-unbound > > Hocon and Json to Apache pom.xml. Contribute to hunterpayne/maven-unbound > development by creating an account on ... > | > > | > > | > > > thank you for your time, > Hunter > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: hocon and json formats for the Project Object Model
Weird. The url you want is https://github.com/hunterpayne/maven-unboundSent from my T-Mobile 4G LTE Device Original message From: Enrico Olivelli Date: 6/10/19 4:15 AM (GMT-08:00) To: Maven Developers List Subject: Re: hocon and json formats for the Project Object Model Hi, Hunter,I have received your email a bit corrupted.Did you put some ASCII art ?Did you add attachments ?I find your idea interesting. thank youEnricoIl giorno lun 10 giu 2019 alle ore 11:33 Hunter C Payne ha scritto:> Hello all, I've used Maven for probably 15 years now. I think its great> and want to thank you all for all your hard work.> I've written a quick Scala library that converts pom.xml files to/from> pom.json and pom.conf (Hocon) files. This allows for a much less verbose> way to specify pom files. The code I've written should also be suitable to> integrate into Maven proper (if you so choose) as it can construct the> Maven bean classes that represent a POM in the Maven source base.>> Here is a link to that library which I call Unbound. Hope everyone likes> this little project and thinks it helps promote Maven. Its not quite> complete yet as a bit more testing and debugging is necessary before it can> be used but I still wanted to broadcast the idea to see how everyone felt> about it.>> hunterpayne/maven-unbound>> |> |> |> | | |>> |>> |> |> | |> hunterpayne/maven-unbound>> Hocon and Json to Apache pom.xml. Contribute to hunterpayne/maven-unbound> development by creating an account on ...> |>> |>> |>>> thank you for your time,> Hunter>
Re: hocon and json formats for the Project Object Model
Weird. The url you want is https://github.com/hunterpayne/maven-unboundSent from my T-Mobile 4G LTE Device Original message From: Enrico Olivelli Date: 6/10/19 4:15 AM (GMT-08:00) To: Maven Developers List Subject: Re: hocon and json formats for the Project Object Model Hi, Hunter,I have received your email a bit corrupted.Did you put some ASCII art ?Did you add attachments ?I find your idea interesting. thank youEnricoIl giorno lun 10 giu 2019 alle ore 11:33 Hunter C Payne ha scritto:> Hello all, I've used Maven for probably 15 years now. I think its great> and want to thank you all for all your hard work.> I've written a quick Scala library that converts pom.xml files to/from> pom.json and pom.conf (Hocon) files. This allows for a much less verbose> way to specify pom files. The code I've written should also be suitable to> integrate into Maven proper (if you so choose) as it can construct the> Maven bean classes that represent a POM in the Maven source base.>> Here is a link to that library which I call Unbound. Hope everyone likes> this little project and thinks it helps promote Maven. Its not quite> complete yet as a bit more testing and debugging is necessary before it can> be used but I still wanted to broadcast the idea to see how everyone felt> about it.>> hunterpayne/maven-unbound>> |> |> |> | | |>> |>> |> |> | |> hunterpayne/maven-unbound>> Hocon and Json to Apache pom.xml. Contribute to hunterpayne/maven-unbound> development by creating an account on ...> |>> |>> |>>> thank you for your time,> Hunter>
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?
Hey StephenC, I was looking for Anders' answer in Eclipse issue. Important is that the issue was isolated to https://github.com/tesla/m2eclipse-mavenarchiver and to Maven. Issues are everywhere, in every tool, that's the life. Maybe some did not reach such ratings to fix them nor contributor who could fix them. In 2010 I worked with Eclipse and Idea but I was missing such code inspection in Eclipse that Idea had, but Eclipse has many other plugins for EE and Web, where other tool does not and so therefore there are separately specialized tools for Web (.., ..., ...), UML - EnterpriseArchitect, etc. Drawback of those tools is the cost, advantage of Eclipse is free cost, user conformance is different in each. So I used Idea due to the code inspection analysis which fits to me and my commercial collagues in companies (not talking about oss), but other people may have different feelings. I utilized code inspection as much as possible, but according to my experiences in commercial companies my collagues did not utilize it so much which affected their code quality. So everyone can choose, so I tried 3 tools and chose the one. Maybe everybody has tried all tools and has own preference, that's the life. I am only glad that I can share the reasoning and exps, that's all. Cheers Tibor17 On Mon, Jun 10, 2019 at 2:36 PM Mickael Istria wrote: > Hi, > > On Mon, Jun 10, 2019 at 11:37 AM Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > > however > > because of architectural history, Eclipse (last time I checked... some > > years ago) had issues keeping the main and test classpaths separate > > > This was fixed last year, during development of the "Photon" release: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=526858 > > > > and I hate Eclipse as and IDE > > > If one day you're interested in sharing why, you can send the reasons > behind this hate to whichever Eclipse community channel, or even DM me. > I'll try to (with the help of the community) turn the hate into bug reports > and then bugs into patches. >
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?
On Mon, 10 Jun 2019 at 13:36, Mickael Istria wrote: > Hi, > > On Mon, Jun 10, 2019 at 11:37 AM Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > > however > > because of architectural history, Eclipse (last time I checked... some > > years ago) had issues keeping the main and test classpaths separate > > > This was fixed last year, during development of the "Photon" release: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=526858 Excellent to hear that! > > > > > and I hate Eclipse as and IDE > > > If one day you're interested in sharing why, you can send the reasons > behind this hate to whichever Eclipse community channel, or even DM me. > I'll try to (with the help of the community) turn the hate into bug reports > and then bugs into patches. > It's more a personal preference... and the way the display gets messed up when debugging... and now I'm use to the IntelliJ crazy, so it seems normal to me!
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?
Hi, On Mon, Jun 10, 2019 at 11:37 AM Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > however > because of architectural history, Eclipse (last time I checked... some > years ago) had issues keeping the main and test classpaths separate This was fixed last year, during development of the "Photon" release: https://bugs.eclipse.org/bugs/show_bug.cgi?id=526858 > and I hate Eclipse as and IDE If one day you're interested in sharing why, you can send the reasons behind this hate to whichever Eclipse community channel, or even DM me. I'll try to (with the help of the community) turn the hate into bug reports and then bugs into patches.
Re: hocon and json formats for the Project Object Model
Hi, Hunter, I have received your email a bit corrupted. Did you put some ASCII art ? Did you add attachments ? I find your idea interesting. thank you Enrico Il giorno lun 10 giu 2019 alle ore 11:33 Hunter C Payne ha scritto: > Hello all, I've used Maven for probably 15 years now. I think its great > and want to thank you all for all your hard work. >I've written a quick Scala library that converts pom.xml files to/from > pom.json and pom.conf (Hocon) files. This allows for a much less verbose > way to specify pom files. The code I've written should also be suitable to > integrate into Maven proper (if you so choose) as it can construct the > Maven bean classes that represent a POM in the Maven source base. > > Here is a link to that library which I call Unbound. Hope everyone likes > this little project and thinks it helps promote Maven. Its not quite > complete yet as a bit more testing and debugging is necessary before it can > be used but I still wanted to broadcast the idea to see how everyone felt > about it. > > hunterpayne/maven-unbound > > | > | > | > | | | > > | > > | > | > | | > hunterpayne/maven-unbound > > Hocon and Json to Apache pom.xml. Contribute to hunterpayne/maven-unbound > development by creating an account on ... > | > > | > > | > > > thank you for your time, > Hunter >
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?
Tibor, If one is ranking correctness of integration with Maven of the various IDEs then IntelliJ is not the "gold standard". There are two *major* bugs in how IntelliJ handles Maven projects: 1. It does not allow different Java versions for test versus main trees: https://youtrack.jetbrains.com/issue/IDEA-85478 2. It does not consult ArtifactHandler.isAddedToClasspath() and consequently generates incorrect classpaths: https://youtrack.jetbrains.com/issue/IDEA-175538 Both of these force users to contort their Maven projects in strange ways just to make them work in their IDE. >From my understanding, from the PoV of a Maven integration, the *gold standard* IDE is probably NetBeans, largely because it falls back to Maven to do the lifting. (Granted I do not use NetBeans, so I probably haven't found the bugs in its integration :-P) IIUC Eclipse could not have an issue like https://youtrack.jetbrains.com/issue/IDEA-175538 because m2e doesn't suffer from NIH syndrome when it comes to parsing the pom.xml files... however because of architectural history, Eclipse (last time I checked... some years ago) had issues keeping the main and test classpaths separate, which is worse than https://youtrack.jetbrains.com/issue/IDEA-85478 (And to defend IntelliJ, there may actually be some good reasons for their having NIH syndrome with respect to parsing the pom.xml files... but if you're going to have NIH syndrome you had better put in the work to make sure things actually work... and 2 years is a long time for https://youtrack.jetbrains.com/issue/IDEA-175538 to sit there without even a triage comment) Now I personally don't like NetBeans as an IDE, and I hate Eclipse as and IDE, so I continue to use IntelliJ despite its flaws... but I also recognise that these are personal preferences of mine. IDEs are subjective. Please try to remember what Clint Eastwood's character says about opinions in the film Dirty Harry. On Sat, 8 Jun 2019 at 16:01, Tibor Digana wrote: > No, it is not truth. And the price is nothing one cannot survive. IDEA is > also OSS. > User exp of IDEA is ideally joined together with Maven and working > naturally well. > Try Maven + IDEA and you will see. I used both. > > On Sat, Jun 8, 2019 at 4:51 PM Jeff MAURY wrote: > > > because it's much better and oss > > > > Le sam. 8 juin 2019 à 10:29, Tibor Digana a > > écrit : > > > > > Why you use Eclipse. Use InteliJ IDEA. It is professional tool. Every > > > company has money to buy enterprise IDEA, the company wouln'd say no > > > because it is price you pay once and you can upgrade to major version > > > within whole year. You can use it forever without paying more after the > > > support period of one year you paid before. For instance I had IDEA 14 > > > since 2014 - 2019 without any issue in that tool. > > > > > > On Fri, Jun 7, 2019 at 3:32 PM Cristiano wrote: > > > > > > > Hello, > > > > > > > > Yesterday I did an upgrade on some dependencies and plugins of my > > > > company's master POM. > > > > > > > > I used the versions-plugin and changed many of the suggested ones. > > After > > > > conclude and build on CI without error, I ended up with a strange > error > > > > in Eclipse IDE (ubuntu, 201903, jdk11) on every project that has it > as > > > > its parent POM. > > > > > > > > The error has no description and its title is "Unknown". > > > > > > > > > > > > It took some time to track the culprit down and after I have > downgraded > > > > the maven-jar-plugin to 3.1.1 the error was gone. > > > > > > > > I'm curious about this... > > > > > > > > best regards, > > > > > > > > > > > > Cristiano > > > > > > > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > > > > >
hocon and json formats for the Project Object Model
Hello all, I've used Maven for probably 15 years now. I think its great and want to thank you all for all your hard work. I've written a quick Scala library that converts pom.xml files to/from pom.json and pom.conf (Hocon) files. This allows for a much less verbose way to specify pom files. The code I've written should also be suitable to integrate into Maven proper (if you so choose) as it can construct the Maven bean classes that represent a POM in the Maven source base. Here is a link to that library which I call Unbound. Hope everyone likes this little project and thinks it helps promote Maven. Its not quite complete yet as a bit more testing and debugging is necessary before it can be used but I still wanted to broadcast the idea to see how everyone felt about it. hunterpayne/maven-unbound | | | | | | | | | | | hunterpayne/maven-unbound Hocon and Json to Apache pom.xml. Contribute to hunterpayne/maven-unbound development by creating an account on ... | | | thank you for your time, Hunter
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?
Please read the bug report [1], which was reference in the first reply to this thread. It clearly explains that the problem is in the mavenarchiver m2e connector/plugin. The simplest solution is to just update that plugin. URL to update site is in the bug report. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=547340 /Anders On Mon, Jun 10, 2019 at 12:39 AM Alix Lourme wrote: > Hello Cristiano, > > Original root cause not analysed but: > - Same problem here with Eclipse Oxygen (3a) + m2e - Maven Integration for > Eclipse 1.8.3. > - It works with Eclipse 2019-03 + m2e - Maven Integration for Eclipse > 1.11.0 > => m2e - Maven Integration for Eclipe plugin upgrade could be a solution > > Best regards > > Le dim. 9 juin 2019 à 00:07, Tibor Digana a > écrit : > > > Hi Cristiano, > > > > I guess your architect who designed your company parent POM made everying > > honestly right. > > But we can prove or avoid the error on the tool if we simply add > something, > > then make a comparison test and we exclude added things which could not > > change the outcome. > > > > Open the project in another tool, like Intellij IDEA or NetBeans and do > > whta you expected in Ecplise, e.g. building the project. > > If the project is built correctly, then it means Eclipse is not compliant > > with the project. > > If it would not work with IDEA nor NetBeans then maybe the architect did > > not check the IDE tools even if he used commandline of Maven. > > > > The IntelliJ IDEA is usually very smart and understands configuration > > parameters of Maven plugins, as well as repository settings and other > Maven > > specifics. > > The best is to use default path in Maven local repo with these new tools > > especially if their are new for you. > > > > Here in Maven OSS I also use IDEA and I am able to find issues nobody saw > > before (using the Eclipse). These do not seem to be visible in Eclipse. > You > > know JetBrains improves the code analysis in every next version, so I > > recommend this tool to every company and developer. > > Pls try and exclude it if there is no positive influence. > > > > Cheers > > Tibor17 > > > > > > > > On Fri, Jun 7, 2019 at 3:32 PM Cristiano wrote: > > > > > Hello, > > > > > > Yesterday I did an upgrade on some dependencies and plugins of my > > > company's master POM. > > > > > > I used the versions-plugin and changed many of the suggested ones. > After > > > conclude and build on CI without error, I ended up with a strange error > > > in Eclipse IDE (ubuntu, 201903, jdk11) on every project that has it as > > > its parent POM. > > > > > > The error has no description and its title is "Unknown". > > > > > > > > > It took some time to track the culprit down and after I have downgraded > > > the maven-jar-plugin to 3.1.1 the error was gone. > > > > > > I'm curious about this... > > > > > > best regards, > > > > > > > > > Cristiano > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > > -- > Alix Lourme >
