maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cristiano <cvgav...@gmail.com>
Subject Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?
Date Fri, 14 Jun 2019 18:15:49 GMT
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 <alix.lourme@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 <tibordigana@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 <cvgaviao@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


Mime
View raw message