You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Cristiano <cv...@gmail.com> on 2019/06/07 13:32:06 UTC
Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to
3.1.2?
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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin
to 3.1.2?
Posted by Mickael Istria <mi...@redhat.com>.
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
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin
to 3.1.2?
Posted by Stephen Connolly <st...@gmail.com>.
On Mon, 10 Jun 2019 at 13:36, Mickael Istria <mi...@redhat.com> wrote:
> Hi,
>
> On Mon, Jun 10, 2019 at 11:37 AM Stephen Connolly <
> stephen.alan.connolly@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?
Posted by Tibor Digana <ti...@apache.org>.
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 <mi...@redhat.com> wrote:
> Hi,
>
> On Mon, Jun 10, 2019 at 11:37 AM Stephen Connolly <
> stephen.alan.connolly@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?
Posted by Mickael Istria <mi...@redhat.com>.
Hi,
On Mon, Jun 10, 2019 at 11:37 AM Stephen Connolly <
stephen.alan.connolly@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?
Posted by Stephen Connolly <st...@gmail.com>.
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 <ti...@apache.org> 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 <je...@gmail.com> wrote:
>
> > <troll>because it's much better and oss</troll>
> >
> > Le sam. 8 juin 2019 à 10:29, Tibor Digana <ti...@apache.org> 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 <cv...@gmail.com> 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-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > >
> > >
> >
>
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin
to 3.1.2?
Posted by Christian Stein <so...@gmail.com>.
On Sat, Jun 8, 2019 at 6:14 PM Mickael Istria <mi...@redhat.com> 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?
Posted by Mickael Istria <mi...@redhat.com>.
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 <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin
to 3.1.2?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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 <ti...@apache.org> 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 <je...@gmail.com> wrote:
>
> > <troll>because it's much better and oss</troll>
> >
> > Le sam. 8 juin 2019 à 10:29, Tibor Digana <ti...@apache.org> 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 <cv...@gmail.com> 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-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > >
> > >
> >
>
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin
to 3.1.2?
Posted by Tibor Digana <ti...@apache.org>.
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 <je...@gmail.com> wrote:
> <troll>because it's much better and oss</troll>
>
> Le sam. 8 juin 2019 à 10:29, Tibor Digana <ti...@apache.org> 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 <cv...@gmail.com> 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-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
>
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin
to 3.1.2?
Posted by Jeff MAURY <je...@gmail.com>.
<troll>because it's much better and oss</troll>
Le sam. 8 juin 2019 à 10:29, Tibor Digana <ti...@apache.org> 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 <cv...@gmail.com> 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-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin
to 3.1.2?
Posted by Cristiano <cv...@gmail.com>.
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 <cv...@gmail.com> 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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin
to 3.1.2?
Posted by Tibor Digana <ti...@apache.org>.
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 <cv...@gmail.com> 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin
to 3.1.2?
Posted by Cristiano <cv...@gmail.com>.
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 <al...@gmail.com> 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 <ti...@apache.org> 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 <cv...@gmail.com> 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-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>
>> --
>> Alix Lourme
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin
to 3.1.2?
Posted by Anders Hammar <an...@hammar.net>.
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 <al...@gmail.com> 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 <ti...@apache.org> 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 <cv...@gmail.com> 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-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
>
>
> --
> Alix Lourme
>
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin
to 3.1.2?
Posted by Alix Lourme <al...@gmail.com>.
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 <ti...@apache.org> 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 <cv...@gmail.com> 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-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
--
Alix Lourme
Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin
to 3.1.2?
Posted by Tibor Digana <ti...@apache.org>.
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 <cv...@gmail.com> 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>