Hello Martin,
after a second look onto your mvn.log file... there are three
suspicious lines that I have not in my build log:
> Unable to load a binding file due to the following:
> unknown protocol: c
> The Source Generator will continue with no binding file.
the plugin configuration points to a binding file... seems that the
castor maven plugin has a problem with binding files under windows
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>castor-maven-plugin</artifactId>
<version>2.0-SNAPSHOT</version>
<configuration>
<schema>${basedir}/src/main/resources/org/exolab/castor/mapping/mapping.xsd</schema>
<properties>${basedir}/src/main/resources/org/exolab/castor/mapping/mapping.builder.properties</properties>
<packaging>org.exolab.castor.mapping.xml</packaging>
<bindingfile>${basedir}/src/main/resources/org/exolab/castor/mapping/mapping-binding.xml</bindingfile>
</configuration>
<executions>
<execution>
<goals>
<goal>generate</goal>
</goals>
</execution>
</executions>
<!--
<dependencies>
<dependency>
<groupId>org.codehaus.castor</groupId>
<artifactId>castor-codegen</artifactId>
<version>1.3rc1</version>
</dependency>
</dependencies>
-->
</plugin>
can you please move the project into a 'space free' directory and give
it another try?
Thx
Joachim
2008/11/3 Joachim Grüneis <[EMAIL PROTECTED]>:
> Hello Martin,
>
> I was curious if we really have a building problem when starting with
> the trunk zip...
>
> I took the trunk.zip from the link you write above and Java 6 and
> Maven 2.0.9 - and I even removed the castor stuff from my local Maven
> repository...
>
> but sorry mvn clean install is successful
>
> I also had a look onto the log file you provided -> the code
> generation step in your build has either failed was was not executed
> and this causes the compilation errors
>
> is it possible that you have a modified castor-maven-plugin in your
> Maven repository?
>
> HTH
> Joachim
>
> 2008/11/3 Martin S. Weber <[EMAIL PROTECTED]>:
>> Quoting "Werner Guttmann" <[EMAIL PROTECTED]>:
>>>
>>> (...)
>>> That's odd, as this basically does a SVN checkout behind the scenes,
>>> packages the files obtaind and ships it to you. (...)
>>
>> Well if you want to amuse yourself, have a look at
>> http://ayaken.net/mvn.log
>> (which is result of running mvn -e clean install > ..\mvn.log in trunk dir).
>>
>> java is:
>> ...\Desktop\trunk>java -version
>> java version "1.6.0_10"
>> Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
>> Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)
>>
>> maven is:
>> ...\Desktop\trunk>mvn --version
>> Maven version: 2.0.9
>> Java version: 1.6.0_10
>> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>>
>> Next steps: pack up a unit test case triggering the problem that made me
>> want to build it in the first place and test your suggested solution (using
>> a mapping file although I'm pretty confident that that'll work -- it'll
>> remove the clashes which you produce, so why should it fail?) although I
>> still think the real bug is that you produce clashing symbols in the first
>> place.
>>
>> Regards,
>>
>> -Martin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
