[
http://jira.codehaus.org/browse/MAXISTOOLS-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156675#action_156675
]
David J. M. Karlsen commented on MAXISTOOLS-36:
-----------------------------------------------
Whats left
The string-typed mojo parameters
- aspectDirectory
- testAspectDirectory
- ajdtBuildDefFile
- outxmlfile
in the various mojos in combination with the construction
basedir.getAbsolutePath() + "/" + aspectDirectory
will fail when users specify the parameter value as
"${basedir}/src/main/aspect". Switching the parameters to java.io.File
should be sufficient to get proper absolute paths.
Users would benefit if the mojo parameter
- encoding
would adopt the proposal for source file encoding [0].
The hard-coded site output directory
return project.getBuild().getDirectory() + "/site/aspectj-report";
makes customization quite challenging and completely prevents localized
sites but AjcReportMojo.getDescription() isn't localized anyway...
[0]
http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding
--------
Thanks Benjamin.
I couldn't get the header/title stuff to work
> Avoid relative path issues
> --------------------------
>
> Key: MAXISTOOLS-36
> URL: http://jira.codehaus.org/browse/MAXISTOOLS-36
> Project: Maven 2.x Axis Tools Plugin
> Issue Type: Improvement
> Affects Versions: 1.1
> Reporter: David J. M. Karlsen
>
> List of paths which should be fixed along with tests:
> http://www.nabble.com/-VOTE--Releaes-maven-aspectj-plugin-1.1-td20805359.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
