[GitHub] [maven-artifact-transfer] aajisaka closed pull request #22: [MSHARED-981] Upgrade Maven common artifact filters to 3.2.0

[GitBox]

aajisaka closed pull request #22:
URL: https://github.com/apache/maven-artifact-transfer/pull/22


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-artifact-transfer] aajisaka commented on pull request #22: [MSHARED-981] Upgrade Maven common artifact filters to 3.2.0

[GitBox]

aajisaka commented on pull request #22:
URL: 
https://github.com/apache/maven-artifact-transfer/pull/22#issuecomment-789778922


   > It might sound a good idea to add this information to the repo itself so 
people won't spend their time on a PR that would be closed.
   
   Yes, that's a good idea.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-artifact-transfer] KroArtem commented on pull request #22: [MSHARED-981] Upgrade Maven common artifact filters to 3.2.0

[GitBox]

KroArtem commented on pull request #22:
URL: 
https://github.com/apache/maven-artifact-transfer/pull/22#issuecomment-789706459


   I was just passing near and remember that the plan was not to update maven 
minimum version https://github.com/apache/maven-artifact-transfer/pull/20 
(especially 
https://github.com/apache/maven-artifact-transfer/pull/20#issuecomment-752440522)
   
   It might sound a good idea to add this information to the repo itself so 
people won't spend their time on a PR that would be closed.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-artifact-transfer] aajisaka opened a new pull request #22: [MSHARED-981] Upgrade Maven common artifact filters to 3.2.0

[GitBox]

aajisaka opened a new pull request #22:
URL: https://github.com/apache/maven-artifact-transfer/pull/22


   Drop support for Maven 3.0.x
   
   Maven Common Artifact Filters 3.2.0 only supports Maven 3.1.1+ 
(https://issues.apache.org/jira/browse/MSHARED-974), and after the dependency 
upgrade, the source code for Maven 3.0.x cannot be compiled. Therefore I 
dropped the source code for Maven 3.0.x.
   
   Manually tested with `mvn -Prun-its verify` command.
   
   JIRA: https://issues.apache.org/jira/browse/MSHARED-981



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-site-plugin] elharo merged pull request #39: [MSITE-871] Upgrade Maven Javadoc Plugin in integration tests

[GitBox]

elharo merged pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-site-plugin] bertysentry commented on pull request #39: [MSITE-871] Upgrade Maven Javadoc Plugin in integration tests

[GitBox]

bertysentry commented on pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39#issuecomment-788041050


   Awesome news! :-)



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-site-plugin] elharo commented on pull request #39: [MSITE-871] Upgrade Maven Javadoc Plugin in integration tests

[GitBox]

elharo commented on pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39#issuecomment-788034268


   Looks good. CI is slow today, but I'll merge as soon as they all pass. 
Thanks!



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-site-plugin] mthmulders commented on pull request #39: [MSITE-871] Upgrade Maven Javadoc Plugin in integration tests

[GitBox]

mthmulders commented on pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39#issuecomment-788023747


   The remaining tests are also fixed by upgrading the Maven Javadoc Plugin. 
Just pushed.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-site-plugin] elharo commented on pull request #39: [MSITE-871] Upgrade Maven Javadoc Plugin in integration tests

[GitBox]

elharo commented on pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39#issuecomment-787975296


   Running through Jenkins:
   
   
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/msite-871/
   
   Given that this fixes some tests, and does not break anything new I'm 
comfortable merging it. We can fix the remaining two in the next PR. 
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-site-plugin] bertysentry commented on pull request #39: [MSITE-871] Upgrade Maven Javadoc Plugin in integration tests

[GitBox]

bertysentry commented on pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39#issuecomment-787963914


   This is cool, thank you!
   We're making good progress as only 2 integration tests are now failing:
   ```
   Error:  The following builds failed:
   Error:  *  MSITE-512/pom.xml
   Error:  *  MSITE-484/pom.xml
   ```



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [maven-site-plugin] mthmulders opened a new pull request #39: [MSITE-871] Upgrade Maven Javadoc Plugin in integration tests

[GitBox]

mthmulders opened a new pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39


   These test failed on macOS with Java above 8; now they pass with
   Java 8, 11 and 15 on macOS.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Cristiano]

The short answer: I just love this IDE and everything that is behind it!

I'm using it since I dropped the IBM VisualAge a long long time ago. ;-)

In my daily working needs with Java, OSGi, Vertx and Maven I have no
complains. it just give me what I need. Of course that are a bug here
and there, but nothing that I can't bypass.

And with the help of some plugins as SonarLint, Kaizen OpenApi editor,
m2e, Mylin, DBeaver, Egit and some others it is just perfect for me.


Btw, I just needed to install intelij once in order to integrate with an
android app and I felt very uncomfortable with it. Would not use it if I
have a choice.


best regards,

Cristiano 



On 08/06/2019 05:29, Tibor Digana wrote:
> 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
>>
>>


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

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Cristiano]

Thanks all,

I've confirmed that upgrading this mavenarchiver connector and also m2e
(thanks Mickael) resolved my issue.

best regards,

Cristiano

On 10/06/2019 04:11, Anders Hammar wrote:
> 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
>>

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

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Tibor Digana]

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?

[Stephen Connolly]

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?

[Mickael Istria]

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?

[Stephen Connolly]

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
> > > >
> > > >
> > >
> >
>

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Anders Hammar]

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
>

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Alix Lourme]

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

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Tibor Digana]

 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
>
>

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Christian Stein]

On Sat, Jun 8, 2019 at 6:14 PM Mickael Istria  wrote:

> [...]
> Then seeing such negative comments towards them, which are more about
> opinion than technical facts, seems really not encouraging to contribute
> more to Maven.

[...]

It's the 2nd time in a short time-frame I find your comments discouraging,
> dismotivating and irritating. If I were not.committed in improving Maven
> for some other reasons, that kind of negativity in the community would make
> me give up contributing.


Mickael, please, keep on rocking and contributing. That (felt) negativity is
just due to the written opinion of a single person who sometimes overshoots
the mark to make his position clear. I always hope that some smileys, irony
and other positive emotions are lost due to translation.

Cheers,
Christian

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Mickael Istria]

It's also interesting to see how much m2e cases and community has
contributed to improve Maven compared to other IDEs.
Then seeing such negative comments towards them, which are more about
opinion than technical facts, seems really not encouraging to contribute
more to Maven. Imagine if on the Eclipse lists we were just telling users
who have questuon about Maven that they should use Gradle because Maven
sucks, how much would you enjoy it? How useful would that be?
It's the 2nd time in a short time-frame I find your comments discouraging,
dismotivating and irritating. If I were not.committed in improving Maven
for some other reasons, that kind of negativity in the community would make
me give up contributing. You should probably spend time learning the value
of a community and how to improve it instead of bugging it, that would be
very profitable to Maven project.


-- 
Mickael Istria
Eclipse IDE 
developer, for Red Hat Developers 

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Romain Manni-Bucau]

Not really Tibor I think, for two reasons:

1. If it is true then the end of your sentence is "and dont use maven but
use gradle". Both IDE have pro and cons, depends who and for what,
2. Vscode uses eclipse as backend of a LSP so as a mvn dev you care of
eclipse whatever you think of the UI since it is gaining a lot of the
market usage

Indeed, just my 2cts but being opiniated in its usage is good, but maven is
too widely adopted to drop part of its users, we stay community driven, not
opinion driven ;).

Le sam. 8 juin 2019 à 17:01, Tibor Digana  a écrit :

> 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
> > > >
> > > >
> > >
> >
>

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Tibor Digana]

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
> > >
> > >
> >
>

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Jeff MAURY]

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
> >
> >
>

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Tibor Digana]

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
>
>

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Mickael Istria]

Hi,

This seems like https://bugs.eclipse.org/bugs/show_bug.cgi?id=547340 .
Please try updating to a more recent build of Eclipse m2e (using
https://download.eclipse.org/technology/m2e/snapshots/1.12.0/latest/ p2
repo), and if you see further issues with that version, please reopen the
m2e bug with steps to reproduce.

Cheers

Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

[Cristiano]

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

[GitHub] maven pull request #149: Upgrade maven-checkstyle-plugin to 3.0.0 (Checkstyl...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/maven/pull/149


---

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

[GitHub] maven issue #149: Upgrade maven-checkstyle-plugin to 3.0.0 (Checkstyle 6.18)...

[slachiewicz]

Github user slachiewicz commented on the issue:

https://github.com/apache/maven/pull/149
  
Please verify after planned plugin release


---

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

[GitHub] maven pull request #149: Upgrade maven-checkstyle-plugin to 3.0.0 (Checkstyl...

[slachiewicz]

GitHub user slachiewicz opened a pull request:

https://github.com/apache/maven/pull/149

Upgrade maven-checkstyle-plugin to 3.0.0 (Checkstyle 6.18) and fix errors



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/slachiewicz/maven 
feature/checkstyle-3.18-maven

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven/pull/149.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #149


commit fad10665e35ad33555c700349bc908aef831eb6d
Author: Sylwester Lachiewicz <slachiewicz@...>
Date:   2018-01-06T19:32:20Z

Upgrade maven-checkstyle-plugin to 3.0.0

with fixing errors

commit a3cc6ade355a79a4e7ae68ba14bcc3bf334c3ca3
Author: Sylwester Lachiewicz <slachiewicz@...>
Date:   2018-01-06T23:01:15Z

Fix more checkstyle errors




---

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

Re: [jira] [Created] (MPOM-152) Upgrade maven-checkstyle-plugin to 2.17.

[Guillaume Boué]

There might be a corner-case here. I remember an issue about this 
upgrade, a dependency onmaven-shared-resourcesneeded to be added:


https://issues.apache.org/jira/browse/MCHECKSTYLE-327?focusedCommentId=15383006=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15383006


Le 18/12/2016 à 01:09, Christian Schulte (JIRA) a écrit :

Christian Schulte created MPOM-152:
--

  Summary: Upgrade maven-checkstyle-plugin to 2.17.
  Key: MPOM-152
  URL: https://issues.apache.org/jira/browse/MPOM-152
  Project: Maven POMs
   Issue Type: Task
 Reporter: Christian Schulte
 Assignee: Christian Schulte
 Priority: Trivial






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)




---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
https://www.avast.com/antivirus

RE: upgrade maven plugin to run with asm 6?

[Martin Gainty]

i find throwing everything in the kitchen sink and hoping all the dishes get 
cleaned doesnt workpick one variable such as maven-plugin-plugin and introduce 
each new version by a point release3.0 causes exception3.1 causes 
exception...3.5 works with asm6 and JDK 1.9
eventually you'll determine which version works with your specific environment 
configuration

ToDo: can someone update README for 3.5 that 3.5 works with JDK1.9 and ASM6?
thanks romainMartin
__ 



> From: rmannibu...@gmail.com
> Date: Mon, 10 Oct 2016 21:04:50 +0200
> Subject: RE: upgrade maven plugin to run with asm 6?
> To: dev@maven.apache.org
> 
> Oh tested 3.4 but missed 3.5. 3.5 solved the issue!
> 
> Thanks!
> 
> Le 10 oct. 2016 20:31, "Martin Gainty" <mgai...@hotmail.com> a écrit :
> >
> >
> >
> >
> > > From: rmannibu...@gmail.com
> > > Date: Mon, 10 Oct 2016 17:07:54 +0200
> > > Subject: Re: upgrade maven plugin to run with asm 6?
> > > To: dev@maven.apache.org
> > >
> > > 2016-10-10 16:54 GMT+02:00 Martin Gainty <mgai...@hotmail.com>:
> > >
> > > >
> > > >
> > > >
> > > > > From: rmannibu...@gmail.com
> > > > > Date: Mon, 10 Oct 2016 15:10:33 +0200
> > > > > Subject: upgrade maven plugin to run with asm 6?
> > > > > To: dev@maven.apache.org
> > > > >
> > > > > Hi guys,
> > > > >
> > > > > is there some plans to upgrade maven plugin to asm6 (thinking
> > > > > to maven-plugin-tools-annotations and maven-plugin-plugin and more
> > > > > concretely to DefaultMojoAnnotationsScanner used to generate the
> help
> > > > mojo)?
> > > > >
> > > > > I know there is only the alpha our ATM but I think it would enable
> users
> > > > to
> > > > > start building using asm 6 instead of preventing them to run their
> build
> > > > > and the later upgrade would be smooth.
> > > > MG>craft a q test-harness
> > > > MG>switch JAVA to JDK 1.8
> > > > MG>in test-harness substitute in asm-6 into dependency-management of
> > > > parent pom
> > > > MG>mvn package and observe:
> > > > MG>ANY TEST ERRORS ?
> > > > MG>ANY TEST FAILURES?
> > > > MG>is JDKProxy being implemented to implement Interfaces?
> > > > MG>is asm-6 being called to extend subclasses?
> > > > MG>http://stackoverflow.com/questions/10664182/what-is-
> > > > the-difference-between-jdk-dynamic-proxy-and-cglib
> > > > MG>if all of these scenarios pass I think you will have a *convincing
> > > > case* to upgrade asm to 6 in all plugins
> > > > MG>I have a few spare cycles today so let me know if you need any
> > > > assistance
> > > >
> > > >
> > > so concretely I wanted to upgrade
> > > https://github.com/tomitribe/crest/tree/master/crest-maven-plugin to
> asm6
> > > to support java 9 (not sure why you spoke of java 8, typo?) but the side
> > > effect of upgrading it as a dependency of my project was to break the
> > > maven-plugin-plugin. I'm not sure why isolation was broken but I'm very
> > > concerned cause soon we'll upgrade the whole tomee stack to asm 6
> (xbean,
> > > openjpa, cxf, openwebbeans, batchee, tomee itself and probably a few I
> > > forget) and most of them have maven plugins and would break.
> > >
> > > It fails with a NPE in Type.getProxyClass IIRC so maven annotation
> scanner
> > > doesn't work on java 9.
> > MG>JDK 1.9 annotation processor has been "tweaked"
> > MG>http://openjdk.java.net/jeps/217
> > MG>which is the reason why I suggested using the older annotation scanner
> > MG>do we know if error originates from ASM6 upgrade, maven-plugin or
> JDK1.9 that said can you post a bug in JIRA?
> > MG>https://maven.apache.org/issue-tracking.html
> > >
> > > Will be a bit short to help in the ~2 coming weeks but if nothing moved
> > > next month I'll try to hack something up for sure!
> > >
> > >
> > > >
> > > > >
> > > > > Romain Manni-Bucau
> > > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > > > rmannibucau> |
> > > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > > > <http://www.tomitribe.com> | JavaEE Factory
> > > > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > > >
> >
  

RE: upgrade maven plugin to run with asm 6?

[Romain Manni-Bucau]

Oh tested 3.4 but missed 3.5. 3.5 solved the issue!

Thanks!

Le 10 oct. 2016 20:31, "Martin Gainty" <mgai...@hotmail.com> a écrit :
>
>
>
>
> > From: rmannibu...@gmail.com
> > Date: Mon, 10 Oct 2016 17:07:54 +0200
> > Subject: Re: upgrade maven plugin to run with asm 6?
> > To: dev@maven.apache.org
> >
> > 2016-10-10 16:54 GMT+02:00 Martin Gainty <mgai...@hotmail.com>:
> >
> > >
> > >
> > >
> > > > From: rmannibu...@gmail.com
> > > > Date: Mon, 10 Oct 2016 15:10:33 +0200
> > > > Subject: upgrade maven plugin to run with asm 6?
> > > > To: dev@maven.apache.org
> > > >
> > > > Hi guys,
> > > >
> > > > is there some plans to upgrade maven plugin to asm6 (thinking
> > > > to maven-plugin-tools-annotations and maven-plugin-plugin and more
> > > > concretely to DefaultMojoAnnotationsScanner used to generate the
help
> > > mojo)?
> > > >
> > > > I know there is only the alpha our ATM but I think it would enable
users
> > > to
> > > > start building using asm 6 instead of preventing them to run their
build
> > > > and the later upgrade would be smooth.
> > > MG>craft a q test-harness
> > > MG>switch JAVA to JDK 1.8
> > > MG>in test-harness substitute in asm-6 into dependency-management of
> > > parent pom
> > > MG>mvn package and observe:
> > > MG>ANY TEST ERRORS ?
> > > MG>ANY TEST FAILURES?
> > > MG>is JDKProxy being implemented to implement Interfaces?
> > > MG>is asm-6 being called to extend subclasses?
> > > MG>http://stackoverflow.com/questions/10664182/what-is-
> > > the-difference-between-jdk-dynamic-proxy-and-cglib
> > > MG>if all of these scenarios pass I think you will have a *convincing
> > > case* to upgrade asm to 6 in all plugins
> > > MG>I have a few spare cycles today so let me know if you need any
> > > assistance
> > >
> > >
> > so concretely I wanted to upgrade
> > https://github.com/tomitribe/crest/tree/master/crest-maven-plugin to
asm6
> > to support java 9 (not sure why you spoke of java 8, typo?) but the side
> > effect of upgrading it as a dependency of my project was to break the
> > maven-plugin-plugin. I'm not sure why isolation was broken but I'm very
> > concerned cause soon we'll upgrade the whole tomee stack to asm 6
(xbean,
> > openjpa, cxf, openwebbeans, batchee, tomee itself and probably a few I
> > forget) and most of them have maven plugins and would break.
> >
> > It fails with a NPE in Type.getProxyClass IIRC so maven annotation
scanner
> > doesn't work on java 9.
> MG>JDK 1.9 annotation processor has been "tweaked"
> MG>http://openjdk.java.net/jeps/217
> MG>which is the reason why I suggested using the older annotation scanner
> MG>do we know if error originates from ASM6 upgrade, maven-plugin or
JDK1.9 that said can you post a bug in JIRA?
> MG>https://maven.apache.org/issue-tracking.html
> >
> > Will be a bit short to help in the ~2 coming weeks but if nothing moved
> > next month I'll try to hack something up for sure!
> >
> >
> > >
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > > rmannibucau> |
> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > > <http://www.tomitribe.com> | JavaEE Factory
> > > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > >
>

RE: upgrade maven plugin to run with asm 6?

[Martin Gainty]

> From: rmannibu...@gmail.com
> Date: Mon, 10 Oct 2016 17:07:54 +0200
> Subject: Re: upgrade maven plugin to run with asm 6?
> To: dev@maven.apache.org
> 
> 2016-10-10 16:54 GMT+02:00 Martin Gainty <mgai...@hotmail.com>:
> 
> >
> >
> >
> > > From: rmannibu...@gmail.com
> > > Date: Mon, 10 Oct 2016 15:10:33 +0200
> > > Subject: upgrade maven plugin to run with asm 6?
> > > To: dev@maven.apache.org
> > >
> > > Hi guys,
> > >
> > > is there some plans to upgrade maven plugin to asm6 (thinking
> > > to maven-plugin-tools-annotations and maven-plugin-plugin and more
> > > concretely to DefaultMojoAnnotationsScanner used to generate the help
> > mojo)?
> > >
> > > I know there is only the alpha our ATM but I think it would enable users
> > to
> > > start building using asm 6 instead of preventing them to run their build
> > > and the later upgrade would be smooth.
> > MG>craft a q test-harness
> > MG>switch JAVA to JDK 1.8
> > MG>in test-harness substitute in asm-6 into dependency-management of
> > parent pom
> > MG>mvn package and observe:
> > MG>ANY TEST ERRORS ?
> > MG>ANY TEST FAILURES?
> > MG>is JDKProxy being implemented to implement Interfaces?
> > MG>is asm-6 being called to extend subclasses?
> > MG>http://stackoverflow.com/questions/10664182/what-is-
> > the-difference-between-jdk-dynamic-proxy-and-cglib
> > MG>if all of these scenarios pass I think you will have a *convincing
> > case* to upgrade asm to 6 in all plugins
> > MG>I have a few spare cycles today so let me know if you need any
> > assistance
> >
> >
> so concretely I wanted to upgrade
> https://github.com/tomitribe/crest/tree/master/crest-maven-plugin to asm6
> to support java 9 (not sure why you spoke of java 8, typo?) but the side
> effect of upgrading it as a dependency of my project was to break the
> maven-plugin-plugin. I'm not sure why isolation was broken but I'm very
> concerned cause soon we'll upgrade the whole tomee stack to asm 6 (xbean,
> openjpa, cxf, openwebbeans, batchee, tomee itself and probably a few I
> forget) and most of them have maven plugins and would break.
> 
> It fails with a NPE in Type.getProxyClass IIRC so maven annotation scanner
> doesn't work on java 9.
MG>JDK 1.9 annotation processor has been "tweaked" 
MG>http://openjdk.java.net/jeps/217
MG>which is the reason why I suggested using the older annotation scanner
MG>do we know if error originates from ASM6 upgrade, maven-plugin or JDK1.9 
that said can you post a bug in JIRA?
MG>https://maven.apache.org/issue-tracking.html
> 
> Will be a bit short to help in the ~2 coming weeks but if nothing moved
> next month I'll try to hack something up for sure!
> 
> 
> >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > <http://www.tomitribe.com> | JavaEE Factory
> > > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
  

Re: upgrade maven plugin to run with asm 6?

[Robert Scholte]

hi,

I've already done some improvements on the maven-plugin-plugin 3.5  
(released 2016-08-30) which should work with Java9.

If there's still an issue, let me know.

Robert

On Mon, 10 Oct 2016 17:07:54 +0200, Romain Manni-Bucau  
<rmannibu...@gmail.com> wrote:



2016-10-10 16:54 GMT+02:00 Martin Gainty <mgai...@hotmail.com>:





> From: rmannibu...@gmail.com
> Date: Mon, 10 Oct 2016 15:10:33 +0200
> Subject: upgrade maven plugin to run with asm 6?
> To: dev@maven.apache.org
>
> Hi guys,
>
> is there some plans to upgrade maven plugin to asm6 (thinking
> to maven-plugin-tools-annotations and maven-plugin-plugin and more
> concretely to DefaultMojoAnnotationsScanner used to generate the help
mojo)?
>
> I know there is only the alpha our ATM but I think it would enable  
users

to
> start building using asm 6 instead of preventing them to run their  
build

> and the later upgrade would be smooth.
MG>craft a q test-harness
MG>switch JAVA to JDK 1.8
MG>in test-harness substitute in asm-6 into dependency-management of
parent pom
MG>mvn package and observe:
MG>ANY TEST ERRORS ?
MG>ANY TEST FAILURES?
MG>is JDKProxy being implemented to implement Interfaces?
MG>is asm-6 being called to extend subclasses?
MG>http://stackoverflow.com/questions/10664182/what-is-
the-difference-between-jdk-dynamic-proxy-and-cglib
MG>if all of these scenarios pass I think you will have a *convincing
case* to upgrade asm to 6 in all plugins
MG>I have a few spare cycles today so let me know if you need any
assistance



so concretely I wanted to upgrade
https://github.com/tomitribe/crest/tree/master/crest-maven-plugin to asm6
to support java 9 (not sure why you spoke of java 8, typo?) but the side
effect of upgrading it as a dependency of my project was to break the
maven-plugin-plugin. I'm not sure why isolation was broken but I'm very
concerned cause soon we'll upgrade the whole tomee stack to asm 6 (xbean,
openjpa, cxf, openwebbeans, batchee, tomee itself and probably a few I
forget) and most of them have maven plugins and would break.

It fails with a NPE in Type.getProxyClass IIRC so maven annotation  
scanner

doesn't work on java 9.

Will be a bit short to help in the ~2 coming weeks but if nothing moved
next month I'll try to hack something up for sure!




>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/
rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>


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

Re: upgrade maven plugin to run with asm 6?

[Romain Manni-Bucau]

2016-10-10 16:54 GMT+02:00 Martin Gainty <mgai...@hotmail.com>:

>
>
>
> > From: rmannibu...@gmail.com
> > Date: Mon, 10 Oct 2016 15:10:33 +0200
> > Subject: upgrade maven plugin to run with asm 6?
> > To: dev@maven.apache.org
> >
> > Hi guys,
> >
> > is there some plans to upgrade maven plugin to asm6 (thinking
> > to maven-plugin-tools-annotations and maven-plugin-plugin and more
> > concretely to DefaultMojoAnnotationsScanner used to generate the help
> mojo)?
> >
> > I know there is only the alpha our ATM but I think it would enable users
> to
> > start building using asm 6 instead of preventing them to run their build
> > and the later upgrade would be smooth.
> MG>craft a q test-harness
> MG>switch JAVA to JDK 1.8
> MG>in test-harness substitute in asm-6 into dependency-management of
> parent pom
> MG>mvn package and observe:
> MG>ANY TEST ERRORS ?
> MG>ANY TEST FAILURES?
> MG>is JDKProxy being implemented to implement Interfaces?
> MG>is asm-6 being called to extend subclasses?
> MG>http://stackoverflow.com/questions/10664182/what-is-
> the-difference-between-jdk-dynamic-proxy-and-cglib
> MG>if all of these scenarios pass I think you will have a *convincing
> case* to upgrade asm to 6 in all plugins
> MG>I have a few spare cycles today so let me know if you need any
> assistance
>
>
so concretely I wanted to upgrade
https://github.com/tomitribe/crest/tree/master/crest-maven-plugin to asm6
to support java 9 (not sure why you spoke of java 8, typo?) but the side
effect of upgrading it as a dependency of my project was to break the
maven-plugin-plugin. I'm not sure why isolation was broken but I'm very
concerned cause soon we'll upgrade the whole tomee stack to asm 6 (xbean,
openjpa, cxf, openwebbeans, batchee, tomee itself and probably a few I
forget) and most of them have maven plugins and would break.

It fails with a NPE in Type.getProxyClass IIRC so maven annotation scanner
doesn't work on java 9.

Will be a bit short to help in the ~2 coming weeks but if nothing moved
next month I'll try to hack something up for sure!


>
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
>

RE: upgrade maven plugin to run with asm 6?

[Martin Gainty]

> From: rmannibu...@gmail.com
> Date: Mon, 10 Oct 2016 15:10:33 +0200
> Subject: upgrade maven plugin to run with asm 6?
> To: dev@maven.apache.org
> 
> Hi guys,
> 
> is there some plans to upgrade maven plugin to asm6 (thinking
> to maven-plugin-tools-annotations and maven-plugin-plugin and more
> concretely to DefaultMojoAnnotationsScanner used to generate the help mojo)?
> 
> I know there is only the alpha our ATM but I think it would enable users to
> start building using asm 6 instead of preventing them to run their build
> and the later upgrade would be smooth.
MG>craft a q test-harness
MG>switch JAVA to JDK 1.8
MG>in test-harness substitute in asm-6 into dependency-management of parent pom
MG>mvn package and observe:
MG>ANY TEST ERRORS ?
MG>ANY TEST FAILURES?
MG>is JDKProxy being implemented to implement Interfaces?
MG>is asm-6 being called to extend subclasses?
MG>http://stackoverflow.com/questions/10664182/what-is-the-difference-between-jdk-dynamic-proxy-and-cglib
MG>if all of these scenarios pass I think you will have a *convincing case* to 
upgrade asm to 6 in all plugins
MG>I have a few spare cycles today so let me know if you need any assistance


> 
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
  

upgrade maven plugin to run with asm 6?

[Romain Manni-Bucau]

Hi guys,

is there some plans to upgrade maven plugin to asm6 (thinking
to maven-plugin-tools-annotations and maven-plugin-plugin and more
concretely to DefaultMojoAnnotationsScanner used to generate the help mojo)?

I know there is only the alpha our ATM but I think it would enable users to
start building using asm 6 instead of preventing them to run their build
and the later upgrade would be smooth.

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

[GitHub] maven-plugin-tools pull request: MPLUGIN-295 - upgrade Maven Invok...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/maven-plugin-tools/pull/8


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] maven-plugin-tools pull request: MPLUGIN-295 - upgrade Maven Invok...

[gslowikowski]

GitHub user gslowikowski opened a pull request:

https://github.com/apache/maven-plugin-tools/pull/8

MPLUGIN-295 - upgrade Maven Invoker Plugin version to 1.10



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gslowikowski/maven-plugin-tools 
issue-mplugin-295

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-plugin-tools/pull/8.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #8


commit 91f5d480f124ba185044729058dc5c119a935327
Author: Grzegorz Slowikowski <gslowikow...@gmail.com>
Date:   2015-11-30T13:33:33Z

[MPLUGIN-295] Upgrade Maven Invoker Plugin version to 1.10




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: Upgrade maven-jar-plugin to have minimum maven 2.2.1 runtime?

[Dan Tran]

There is no hurry on this, but it would be good to know the release status
of this plugin.

Big thanks for all the efforts have been made to plugins lately

-D

On Mon, Oct 27, 2014 at 2:15 PM, Karl Heinz Marbaise khmarba...@gmx.de
wrote:

 hi Michael,

 On 10/27/14 9:53 PM, Michael Osipov wrote:

 Am 2014-10-27 um 21:21 schrieb Karl Heinz Marbaise:

 Hi Dan,

 On 10/27/14 9:01 PM, Dan Tran wrote:

 @Karl

 Are you planing to release a new maven-jar-plugin?

 Thanks


 Yeah...working on a missging single issue...apart from the current down
 issue of the nexus ...

 http://jira.codehaus.org/browse/MJAR


 Please wait until I have released Maven Archiver 2.6. I'd like to update
 this dependency.


 Added an appropriate JIRA http://jira.codehaus.org/browse/MJAR-187 as a
 reminder...

 Kind regards
 Karl Heinz Marbaise

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

Upgrade maven-jar-plugin to have minimum maven 2.2.1 runtime?

[Dan Tran]

@Karl

Are you planing to release a new maven-jar-plugin?

Thanks

-D

Re: Upgrade maven-jar-plugin to have minimum maven 2.2.1 runtime?

[Karl Heinz Marbaise]

Hi Dan,

On 10/27/14 9:01 PM, Dan Tran wrote:

@Karl

Are you planing to release a new maven-jar-plugin?

Thanks


Yeah...working on a missging single issue...apart from the current down 
issue of the nexus ...


http://jira.codehaus.org/browse/MJAR

Kind regards
Karl Heinz Marbaise

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

Re: Upgrade maven-jar-plugin to have minimum maven 2.2.1 runtime?

[Michael Osipov]

Am 2014-10-27 um 21:21 schrieb Karl Heinz Marbaise:

Hi Dan,

On 10/27/14 9:01 PM, Dan Tran wrote:

@Karl

Are you planing to release a new maven-jar-plugin?

Thanks


Yeah...working on a missging single issue...apart from the current down
issue of the nexus ...

http://jira.codehaus.org/browse/MJAR


Please wait until I have released Maven Archiver 2.6. I'd like to update 
this dependency.


Michael

PS: Still waiting for RAO...


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

Re: Upgrade maven-jar-plugin to have minimum maven 2.2.1 runtime?

[Karl Heinz Marbaise]

hi Michael,

On 10/27/14 9:53 PM, Michael Osipov wrote:

Am 2014-10-27 um 21:21 schrieb Karl Heinz Marbaise:

Hi Dan,

On 10/27/14 9:01 PM, Dan Tran wrote:

@Karl

Are you planing to release a new maven-jar-plugin?

Thanks


Yeah...working on a missging single issue...apart from the current down
issue of the nexus ...

http://jira.codehaus.org/browse/MJAR


Please wait until I have released Maven Archiver 2.6. I'd like to update
this dependency.


Added an appropriate JIRA http://jira.codehaus.org/browse/MJAR-187 as a 
reminder...


Kind regards
Karl Heinz Marbaise

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

Upgrade Maven

[MIDON ALEXIS]

 
 
Hi,
 
is there any documentation explaining how to upgrade from 1.0beta7 to
release 1.0?
 
 
Alexis