Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353979 - [mojo] org.codehaus.mojo:jasperreports-maven-plugin support
Summary: [mojo] org.codehaus.mojo:jasperreports-maven-plugin support
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-05 05:13 EDT by fweiler CLA
Modified: 2021-04-19 13:25 EDT (History)
2 users (show)

See Also:

Attachments
sample project (26.84 KB, application/x-zip-compressed)
2011-08-05 07:02 EDT, fweiler 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 fweiler CLA 2011-08-05 05:13:13 EDT 
Build Identifier: 20110615-0604

execution not covered by lifecycle config

Reproducible: Always

Steps to Reproduce:
1. build the project within eclipse
Comment 1 Igor Fedorenko CLA 2011-08-05 06:11:40 EDT 
As explained in [1], please provide standalone example project and detailed description of desired behaviour when the project is imported in Eclipse workspace. 

[1] http://wiki.eclipse.org/M2E_plugin_execution_not_covered#Help_improve_m2e_maven_plugin_coverage
Comment 2 fweiler CLA 2011-08-05 07:02:16 EDT 
Created attachment 200969 [details]
sample project
Comment 3 fweiler CLA 2011-08-05 07:05:06 EDT 
attached a sample project.
The desired behaviour is: 

show not an error in the pom, instead compile jasper report files (jrxml)

The plugin's default binding is at generate-source - step of maven build cycle
Comment 4 Igor Fedorenko CLA 2013-09-28 23:54:18 EDT 
closing old/stale bugreports
Comment 5 Denis Roy CLA 2021-04-19 13:25:55 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/