[
http://jira.codehaus.org/browse/JIBX-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Corley resolved JIBX-429.
-----------------------------
Resolution: Fixed
Fix Version/s: JiBX 1.2.3
Dave,
I found a nice method that should fix this bug for any platform.
Give it a try and close this bug if this fixes your problem.
The bugfix is in this commit:
git commit: 193ba70710d71133813fe59656e28bc82cd809ae
I have deployed the new code to the sonatype snapshop repository.
If you don't know how to use the snapshot repo, just download the jar file
directly:
https://oss.sonatype.org/content/repositories/snapshots/org/jibx/
The actual file that you need is here:
https://oss.sonatype.org/content/repositories/snapshots/org/jibx/jibx-maven-plugin/1.2.4-SNAPSHOT/jibx-maven-plugin-1.2.4-20110317.142136-1.jar
Just rename this file to jibx-maven-plugin-1.2.3 and replace this file with the
one in your local maven repository... someplace like:
C:\Documents and
Settings\[yourusername]\.m2\repository\org\jibx\jibx-maven-plugin\1.2.3\jibx-maven-plugin-1.2.3
Remember to use the new maven plugin name:
jibx-maven-plugin
not
maven-jibx-plugin
Also, use the new parameter names:
<schemaBindingDirectory>${project.basedir}/src/test/resources/org/jibx/test/jibx</schemaBindingDirectory>
<includeSchemaBindings>
<includeSchemaBinding>binding.xml</includeSchemaBinding>
</includeSchemaBindings>
not
<bindingDirectory>
Thanks,
Don
> Directory issue when configuring the plugin using ${project.basedir}... in a
> windows environment
> ------------------------------------------------------------------------------------------------
>
> Key: JIBX-429
> URL: http://jira.codehaus.org/browse/JIBX-429
> Project: JiBX
> Issue Type: Bug
> Components: maven plugin
> Affects Versions: JiBX 1.2.3
> Environment: Windows 7, Java JDK 1.6.0_24, Maven 3.0.3
> Reporter: David Wolff
> Assignee: Don Corley
> Priority: Minor
> Fix For: JiBX 1.2.3
>
>
> I had a booger of a time getting the plugin to work because I was specifying
> an absolute path (by putting ${project.basedir} on the front of my relative
> path) in the <bindingDirectory/> element. The code in
> AbstractJibxMojo.getFullPath(String dir)... looks to see if the path
> specified is absolute by checking for a file separator at the beginning.
> This works great for linux style file systems but bombs for windows
> <drive>:<path> type entries.
> Example:
> ---------------
> My config was as follows:
> <bindingDirectory>${project.basedir}/src/main/resources/schema</bindingDirectory>
> The directory that the JiBX maven plugin ended up searching for my binding
> files was
> "D:/dev/java/myprojectD:/dev/java/myproject/src/main/resources/schema", which
> is obviously an invalid directory, because the mojo was presuming the path
> was relative and prepended another project base directory to the front. This
> naturally resulted in zero binding files found and no JiBX bytecode
> enhancement.
> ---------------
> The mojo works great when I specify a relative path (e.g.
> <bindingDirectory>src/main/resources/schema</bindingDirectory>) however, I
> think it should work when I have {$project.basedir} on the front as well. I
> wasted a tremendous amount of time trying to determine what the problem was
> when my configuration was more or less correct.
> Many thanks in advance for a fix for this :)
> Dave Wolff
--
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
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
jibx-devs mailing list
jibx-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-devs
