Bug 576973 - eclipse maven plugin doesn't recognize the <configuration> element of the cargo-maven3-plugin
Summary: eclipse maven plugin doesn't recognize the <configuration> element of the car...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.21   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-30 12:01 EDT by Ali Tokmen CLA
Modified: 2023-10-21 14:21 EDT (History)
0 users

See Also:

Attachments
Warning displayed by Eclipse IDE (468.08 KB, image/png)
2021-10-30 12:01 EDT, Ali Tokmen CLA 		no flags Details
Eclipse plugin and version details (1.96 KB, text/plain)
2021-10-30 12:02 EDT, Ali Tokmen CLA 		no flags Details
Example to replicate the issue (8.40 KB, application/zip)
2021-10-30 12:02 EDT, Ali Tokmen CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ali Tokmen CLA 2021-10-30 12:01:06 EDT 
Created attachment 287406 [details]
Warning displayed by Eclipse IDE

Dear Eclipse team

The Eclipse maven plugin recognizes all elements of the org.codehaus.cargo:cargo-maven3-plugin EXCEPT for the <configuration> element.

Attached is a pom.xml file, showing the issue.

Could you have a look please? To run the example (just in case you  want to double check that the plugin configuration is correct), simply type: mvn clean package cargo:run

Regards
Comment 1 Ali Tokmen CLA 2021-10-30 12:02:01 EDT 
Created attachment 287407 [details]
Eclipse plugin and version details
Comment 2 Ali Tokmen CLA 2021-10-30 12:02:34 EDT 
Created attachment 287408 [details]
Example to replicate the issue
Comment 3 Eclipse Genie CLA 2023-10-21 14:21:48 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.