Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Maven version issue
  • From: Ming Cheng <chengm349@xxxxxxxxxxx>
  • Date: Thu, 23 Jan 2020 07:20:45 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; 1; spf=none; dmarc=none; dkim=none; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=x0dC3oqyqFFhYKtif+XjPEQi0I5GTGP5w1LBOYR8ISs=; b=cLCKngZlme1FqPAtTgzRmIPTSGtVKKAlrnYo4SDSRmnYmqNfREsetjY4HVgbkqJLuv/OtST1d9sMyYOegSSVTfZw4JszKJYSiExod/WvYvZ+etA4dFkMpV5KrPLFBS6aH96kuUoos1/qP1wERXmh0D8yuFpVdK6ybys80vo/Ftj2o2nohxKaModO5W0iWvUUKpLA3bqtcvth0on7z9PydalI6mP182b0Z6CdQBus4b+fGJ0Tkj2tMPVUWVxJrxDzPrD/ApYHiDpqxRXDy1IP/zdgex5X80xuxV0/v4m/IHr95S2NQ6l1kyRpZiXEf2Ik9T1xKbPgXGybha9Roqc9dQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=WT/y3o91us7DKf/2uEtpv+0m2nIoZsDjd8tFASa+3aeZef92nNxw/qPJXkNVK4veWRFjmJ2cGFowtgekO8zXQQEb8cPYCEwliJ1BMWr9ZgbC0305fcGjbYblopjSjybAyfJJpLrqjRpUdynBneJtRRVfZEpf5nBt7l8fyqO1X80QQMJtUWyvIN2i3Fms0AC1PP3YeOefvjwlLhGvo+Vr2BKA/whazZ6XcEwyLAfLaP45TtxKVmlIgwtG7WM47aLPSRN7epGnkDOYrEIFCe40SmumGiPFDK6cV3OP8EWnp9x/8nRbWVts6u/vFVO8+8BBfNuXgeLYopowNbkxsahKNg==
  • Delivered-to: cdt-dev@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Thread-index: AQHVzCZzONtTXPMCRki9tc5IVMfayqftNo0AgAWx52iAAvlvBIAABt4AgAHqEA0=
  • Thread-topic: [cdt-dev] Maven version issue

Hi Graham,


I’ll spend time to study

Please see my comments inline below and hope you and other Eclipse/CDT experts can have better pic of my purpose.


Warm Regards.


Sent from Mail for Windows 10


From: Jonah Graham
Sent: Wednesday, January 22, 2020 9:09 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] Maven version issue




I recently responded to a similar question, please see


However, this mailing list is really for development of CDT and most of your questions are basic Java and Eclipse development questions.

[MC]  Yes my purpose is indeed very basic. So my questions are also very basic.  So far I don’t have skill/knowledge to contribute to Eclipse/CDT development. I just want to make use of CDT C++ coding capability. UMLet gives me UML modeling feature and if I can modify it with come CDT function calls to generate C++ code, then it achieves my purpose.

For example, you persist it trying to mixing AWT/Swing code with SWT.

[MC]  I don’t know AWT/Swing/SWT in detail. I heard of them. I am a C++ developer and based on my C++ experience to try to change UMLet java code. UMLet Eclipse plugin seems supporting Eclipse quite well. Now there are 2 possibilities that UMLet plugin code may have AWT, or may no. If there is AWT, then if I just add some CDT function calls without introducing more AWT code, hope the changed plugin should be ok (?) bcos I believe CDT does not have AWT code. If UMLet plugin does NOT have any AWT, then everyone is happy. So I don’t persist to mixing AWT code with SWT.  Swing code yes bcos I guess UMLet uses Swing. Would it be an issue?


You haven't shown what you have done to try and resolve your problems, nor provided stack traces or even transcribed many of the error messages encountered. 

[MC]  This is really the core issue I am facing so far. I tried to add some CDT calls into UMLet Eclipse plugin code but either no effect or hang there. I don’t know how to trace UMLet Eclipse plugin within Eclipse CDT version. What I can think of is to add some printing stmt directly within CDT functions I will use in order to share with your CDT experts. Now I can compile CDT jars but encountered some issue lists in the thread which you can find further below. I’d like to follow any better steps in detail if I don’t need to change CDT but can still trace UMLet Eclipse plugin call stacks. In short changing CDT code is not my purpose.


I really want to support your endeavours, and I have signposted you to solutions and options in private emails that I have had no response to. 

[MC]   thanks again and this is why I can continue to try. Otherwise I could have stopped much earlier.

Please continue to submit CDT specific queries, with relevant stack traces, reproducible code and/or what steps you have taken to resolve the problem.


Thank you, 



On Tue., Jan. 21, 2020, 19:45 Ming Cheng, <chengm349@xxxxxxxxxxx> wrote:

Keen to have your guide to move. Thanks.


Sent from Mail for Windows 10


From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Ming Cheng <chengm349@xxxxxxxxxxx>
Sent: Monday, January 20, 2020 12:12:13 PM
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Maven version issue


Hi Jonah and All,


Thanks for the advice that I can now build ALL CDT jars after a couple of months!


Now I tried to add a couple of JOptionPane.showMessageDialog stmt in file and I could compile successfully also.


I want my Eclipse to use this new org.eclipse.cdt.ui-6.6.100-SNAPSHOT.jar in my Eclipse CDT version:


Eclipse IDE for C/C++ Developers


Version: 2018-09 (4.9.0)

Build id: 20180917-1800


How to do it?


If I simply replace org.eclipse.cdt.ui_6.3.1.201809121146.jar with org.eclipse.cdt.ui-6.6.100-SNAPSHOT.jar, Eclipse will give me an error:




In my com.umlet.plugin code, I called NewClassCodeGenerator.




Sent from Mail for Windows 10


From: Jonah Graham
Sent: Thursday, January 16, 2020 8:21 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Maven version issue


On Linux try in a terminal:


cd path-to-cdt

mvn package 




On Wed., Jan. 15, 2020, 23:52 Ming Cheng, <chengm349@xxxxxxxxxxx> wrote:



Now I run Eclipse committers on Linux trying to avoid any possible windows env bug since I don’t know how to install dockers and jenkinfilers. Still my humble objective is to build CDT jars. I imported CDT source code 9.10.0 and right-click Maven build




[INFO] ------------------------------------------------------------------------

[INFO] Total time:  02:46 min

[INFO] Finished at: 2020-01-16T12:45:26+08:00

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven-version) on project org.eclipse.cdt.core.native: org.apache.maven.plugins.enforcer.RequireMavenVersion failed with message:

[ERROR] Detected Maven Version: 3.6.1 is not in the allowed range [3.6.0,3.6.0].

[ERROR] -> [Help 1]


[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.


[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1]


My current Eclipse version is:

Eclipse IDE for Eclipse Committers


Version: 2019-06 (4.12.0)

Build id: 20190614-1200



I also downloaded older build like 2019-03/2018-12 etc. But the bundled maven version are 3.5.3. (So which Eclipse uses 3.6.0 maven?)


It seems impossible to change Maven usage setting within Eclipse:



I tried and couldn’t save.




Sent from Mail for Windows 10


cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


Back to the top