Blocked by a simple ClassNotFoundException ;-)

[Vincent Thoulé]

Hi All,

I have developed a MailHandler, very similar to CreateOrCommentHandler. Since it is very similar, I have reused most of component provided by jira-mail-plugin (HandlerDetailsValidator, HandlerDetailsModel).

My development was completed under JIRA 5.1.8 and it works like a charm.

Now, it is requested by my customer to move to JIRA 5.2.2 ... I have changed my dependency in pom.xml and go for new compilation ... No compilation issue, lets go for the 1st test.

I am experiencing a ClassNotFoundException: com.atlassian.jira.plugins.mail.webwork.AbstractEditHandlerDetailsWebAction.

The only thing I found is that in JIRA 5.1.8, the jira-mail--plugin was a part of jira-components with the same version as JIRA, and now, in JIRA 5.2.2, jira-mail--plugin has been moved to the root of the distribution with a separate version 5.2.16.

I did not find why it could cause an issue.

Any idea on can be the roor cause ?

Thanks by advance.

Vincent

[Vincent Thoulé]

Now, with 6.2.2, I am blocked by another package visisbility (Details uin JRA-37984).

Did somebody find a resolution ?

[GuillermoP]

Hello,

I ve got this configuration in my Pom plugin project when I execute atlas-run --version 5.2.11 --product jira and i try configure the example Mail Handler Demo in the input mail handler the system throws a ClassNotFoundException: com.atlassian.jira.plugins.mail.webwork.AbstractEditHandlerDetailsWebAction.

What can i do by solve this issue?.

I attached my pom configuration.

<properties>
		<jira.version>5.2.11</jira.version>
		<amps.version>4.1.7</amps.version>
		<plugin.testrunner.version>1.1.2</plugin.testrunner.version>
		<!-- TestKit version 5.x for JIRA 5.x, 6.x for JIRA 6.x -->
		<testkit.version>5.2.26</testkit.version>
	</properties>

<dependency>
         <groupId>com.atlassian.jira</groupId>
         <artifactId>jira-mail-plugin</artifactId>
         <version>${jira.version}</version>
         <scope>provided</scope>
     </dependency>
     <dependency>
         <groupId>com.atlassian.mail</groupId>
         <artifactId>atlassian-mail</artifactId>
         <version>2.1</version>
         <scope>provided</scope>
     </dependency>
     <dependency>
         <groupId>javax.mail</groupId>
         <artifactId>mail</artifactId>
         <version>1.4.4</version>
         <scope>provided</scope>
     </dependency>

Turorial Mail Handler

thanks.

[Andy Brook [Plugin People]]

see issue above, is a bug, fixed in 6.0.4+

[Kenny Ayers]

Is this the same problem as here?

https://answers.atlassian.com/questions/265936/plugin-porting-issue-noclassdeffounderror-com-atlassian-jira-plugins-mail-model-handlerdetailsmodel

If so, the issue is present in 6.1.7.

[Andy Brook [Plugin People]]

Regarding the export, you may well be right, I was in 5.1.x able to access specific classes for popup configuration, that broke in 5.2, probably due to that Export restriction. It has yet to be fixed :(

[Andy Brook [Plugin People]]

I'll answer this and say it wont work because of https://jira.atlassian.com/browse/JRA-30451

[Vincent Thoulé]

Thanks for confirmation ... the back to 5.1.8 until it is fixed.

[Vincent Thoulé]

Hi Andy,

Yes I have dependency defined as follow :

<dependency>
			<groupId>com.atlassian.jira</groupId>
			<artifactId>jira-mail-plugin</artifactId>
			<version>${jira.mail.version}</version>
			<scope>provided</scope>
		</dependency>

<properties>
		<jira.version>5.2.2</jira.version>
		<jira.data.version>5.2.2</jira.data.version>
		<jira.test.version>5.2</jira.test.version>
		<jira.mail.version>5.2.16</jira.mail.version>
		<ao.version>0.19.9</ao.version>
	</properties>

and not Core, but

<dependency>
			<groupId>com.atlassian.jira</groupId>
			<artifactId>atlassian-jira</artifactId>
			<version>${jira.version}</version>
			<scope>provided</scope>
		</dependency>

I will make a test with jira-api ... and also jira-core.

V.

[Vincent Thoulé]

<artifactId>atlassian-jira</artifactId> is required.

<artifactId>jira-core</artifactId> or <artifactId>jira-api</artifactId> are not enough.

... 2:25 am ... It is time to stop!

[Vincent Thoulé]

I may have found something ...

IN JIRA 5.1.8, there was no Export-Package instructions, but in JIRA 5.2.2/jira-mail-plugin-5.2.16, there is an Export-Package instruction for com.atlassian.jira.plugins.mail.handlers*.

Does it means that all packages were exported by default in 5.1.8; and now, only com.atlassian.jira.plugins.mail.handlers* are exported.

The Mail Handler tutorial explain that we can extends com.atlassian.jira.plugins.mail.webwork.AbstractEditHandlerDetailsWebAction !!!

Do I miss someting else !

V.

[Andy Brook [Plugin People]]

Hey Vincent, long time!

did you add the jira-mail-plugin as a provided dependency, do you have jira-core imported also?