Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

maven-lifecycle problem with jira-maven-plugin and eclipse 3.7

Gaby June 12, 2012

Hi,

since we have upgraded eclipse to version 3.7.2 we receive this errors in our jira-plugins (and confluence-plugins):

Multiple annotations found at this line:

  • Plugin execution not covered by lifecycle configuration: com.atlassian.maven.plugins:maven-jira-plugin:
    3.6:copy-bundled-dependencies (execution: default-copy-bundled-dependencies, phase: generate-resources)
  • Plugin execution not covered by lifecycle configuration: com.atlassian.maven.plugins:maven-jira-plugin:
    3.6:compress-resources (execution: default-compress-resources, phase: process-resources)
  • Plugin execution not covered by lifecycle configuration: com.atlassian.maven.plugins:maven-jira-plugin:
    3.6:generate-manifest (execution: default-generate-manifest, phase: process-classes)
  • Plugin execution not covered by lifecycle configuration: com.atlassian.maven.plugins:maven-jira-plugin:
    3.6:filter-plugin-descriptor (execution: default-filter-plugin-descriptor, phase: process-resources)

here the pom.xml:

<?xml version="1.0" encoding="UTF-8"?>

<project xmlns=
<?xml version="1.0" encoding="UTF-8"?>

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">

	<parent>
		<artifactId>sag-common-pom</artifactId>
		<groupId>sag</groupId>
		<version>1.4.2</version>
	</parent>
	<modelVersion>4.0.0</modelVersion>
	<groupId>sag</groupId>
	<artifactId>jira-wiedervorlage</artifactId>
	<version>1.0.2</version>

	<organization>
		<name>Saarstahl AG</name>
		<url>http://www.saarstahl.com/</url>
	</organization>

	<name>jira-wiedervorlage</name>
	<description>Ergänzt Jira um die Wiedervorlage von Vorgängen zu bestimmten Terminen und in bestimmten Intervallen.</description>
	<packaging>atlassian-plugin</packaging>

	<dependencies>
		<dependency>
			<groupId>com.atlassian.jira</groupId>
			<artifactId>jira-api</artifactId>
			<version>${jira.version}</version>
			<scope>provided</scope>
		</dependency>
		<dependency>
			<groupId>junit</groupId>
			<artifactId>junit</artifactId>
			<version>4.8.1</version>
			<scope>test</scope>
		</dependency>
	<dependency>
		<groupId>com.atlassian.jira</groupId>
		<artifactId>jira-core</artifactId>
		<version>${jira.version}</version>
		<type>jar</type>
		<scope>provided</scope>
	</dependency>
		<dependency>
			<groupId>com.atlassian.jira</groupId>
			<artifactId>jira-tests</artifactId>
			<version>${jira.version}</version>
			<scope>provided</scope>
		</dependency>
	</dependencies>

	<build>
		<plugins>			
			<plugin>
				<groupId>com.atlassian.maven.plugins</groupId>
				<artifactId>maven-jira-plugin</artifactId>
				<version>3.6</version>
				<extensions>true</extensions>
				<configuration>
					<productVersion>${jira.version}</productVersion>
					<productDataVersion>${jira.version}</productDataVersion>
					<instructions>
						<!-- OSGi instructions go here -->
						<Embed-Dependency>*;scope=compile|runtime;artifactId=!incubator;classifier=!GWT</Embed-Dependency>
						<Embed-Directory>META-INF/lib</Embed-Directory>
						<Include-Resource>{maven-dependencies},{maven-resources}</Include-Resource>
						<Bundle-ClassPath>.,{maven-dependencies}</Bundle-ClassPath>
						<Spring-Context>*;timeout:=60</Spring-Context>
					</instructions>
				</configuration>
			</plugin>
			<plugin>
				<artifactId>maven-compiler-plugin</artifactId>
				<configuration>
					<source>1.6</source>
					<target>1.6</target>
				</configuration>
			</plugin>
		</plugins>
	</build>

	<properties>
		<jira.version>5.0.1</jira.version>
		<amps.version>3.9</amps.version>
	</properties>

</project>
In eclipse 3.6 it worked fine. What is wrong?

Regards
Gaby

5 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

2 votes
Jaime Rey October 3, 2012

You have to set maven to ignore those errores.

In the pom editor if you click on the errors it shows the option mark as ignore.

For the lifecycles not included in the POM (like compress-resources, filter-plugin-descriptor, etc) you have to open the lifecycle-mapping-metadata.xml file and modify it like this:

<pluginExecutionFilter>
  <groupId>com.atlassian.maven.plugins</groupId>
  <artifactId>maven-jira-plugin</artifactId>
  <versionRange>3.11</versionRange>
  <goals>
    <goal>filter-plugin-descriptor</goal>
    <goal>copy-bundled-dependencies</goal>
    <goal>compress-resources</goal>
  </goals>
</pluginExecutionFilter>

I took it from here: http://wiki.eclipse.org/M2E_plugin_execution_not_covered#ignore_plugin_goal

0 votes
Felipe Reis
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 16, 2012

Same here....

0 votes
Christa Mabee August 3, 2012

Same problem here. Hope to find answer soon.

0 votes
Xingxiao_Lu July 22, 2012

I have same problem too!!

0 votes
JeffW July 4, 2012

I have same problem!

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

TAGS
AUG Leaders

Atlassian Community Events