Can't use mxunit on projects with java nature

[Coke]

I've got a project that has java nature in addition to cf nature:

<natures>

        <nature>org.cfeclipse.cfml.CFENature</nature>

        <nature>org.eclipse.jdt.core.javanature</nature> 

    </natures>

However, once the java nature is added, I can no longer set the mxunit properties for the project - the configuration option under project's properties context menu vanishes. Same thing happens with a buildSpec setting in the .project file.

So, in order to use mxunit on this project, I have to first edit the .project file to make it look like a simple CF project, edit the mxunit settings so they point to the correct copy of the facade, then revert the changes to the project file - at this point I can run the mxunit tests.

Being able to edit this setting without jumping through these hoops would be nice.

Alternatively, If there was a to save these settings in the project's directory, that would also be nice, because then other developers could take advantage of the fact that I jumped through hoops.

After making this edit, I see that it's in the workspace, in an "properties.index" file, but is not saved in the project's dir.

Any suggestions?

[Marc Esher]

Will,

That's quite strange. I know this isn't what you wanted to hear,
but I've got several CF projects with a javanature and it works fine.
However, I'm running CFB and not CFE, though even when I was working
with CFE I didn't have this problem as you describe.

Do you see any errors in the error log?

Marc

> --
> You received this message because you are subscribed to the Google Groups
> "mxunit" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/mxunit/-/oOMZVtNQzMQJ.
> To post to this group, send email to mxu...@googlegroups.com.
> To unsubscribe from this group, send email to
> mxunit+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/mxunit?hl=en.

[Will Coleda]

I just closed eclipse, reopened it, opened one of the impacted
projects, opened its properties (with no mxunit in the list of
options), and see nothing new in the error log
($WORKSPACE/.metadata/.log) about mxunit - just that eclipse started
and that the workspace had unsaved changes.

I'm using Juno, btw, in case that impacts anything.

--
Will "Coke" Coleda

[Marc Esher]

shot in the dark here, but maybe try starting eclipse with a -clean option?

also, if you have another eclipse install, without CFE, try it in there.

I'm not quite sure how I can help here, except to suggest isolating
whether the problem is related to CFE or Juno (I'm still on 3.7 and
won't be upgrading any time soon)

[Will Coleda]

--clean had no impact.

I'll try it with the various other configurations and get back to you.

[Marc Esher]

Thanks Will.

Curious... are you using the MXUnit that ships with CFEclipse?

I know Denny (CFE lead) keeps up pretty well with the goings on of
Eclipse, and it's possible he'll have some ideas.

Marc

[Will Coleda]

Yes, the bundled version:

MXUnit Test Runner 1.4.4.201201170659 org.mxunit.eclipseplugin.feature.feature.group MXUnit