[Jamon-hackers] [ jamon-Bugs-3253413 ] jamon-maven-plugin 2.3.3/2.3.4 source scanning not working

[SourceForge.net <no...@so...>]

Bugs item #3253413, was opened at 2011-03-28 11:21
Message generated for change (Comment added) made by iroberts
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=741043&aid=3253413&group_id=138569

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Maven plugins
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Jay Sachs (jaysachs)
Summary: jamon-maven-plugin 2.3.3/2.3.4 source scanning not working 

Initial Comment:
Jamon-maven-plugin fails to find the jamon template files created directly under ${project.basedir}/src/main/jamon directory, while this directory is explicitly set as templateSourceDir in pom.xml.

I think scanning works well only if a directory is created under the src/main/jamon directory. I have attached a proposed patch, which modifies the plugin to really scan the configured source directory without unnecessary (as I believe) path "tricks".

----------------------------------------------------------------------

>Comment By: Ian Robertson (iroberts)
Date: 2011-12-01 12:44

Message:
Fixed in 2.4.0

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=741043&aid=3253413&group_id=138569