Hi Martin,
>
some situations I found for doxia (that you pointed out yesterday):
1)Tests wont compile clean e.g. Cast to (LinkItem) was never completed on
return from parent.getBody().getBreadcrumbs().get(0);
parentHref = "scp://parent.com/index.html";
linkItem =(LinkItem)parent.getBody().getBreadcrumbs().get(0);
linkItem.setHref( parentHref );
2)some of the testcases seem to hang?
Running
org.apache.maven.doxia.site.decoration.inheritance.DecorationModelInheritenceAssemblerTest
DecorationModelInheritenceAssemblerTest seems to hang for about an hour?
So why didn't you raise a hand during the release vote of DOXIA ? Or why
didn't you create an issue for that and add log files for further analysis ?
3)doxias <maven-enforcer-plugin> was set to MaxJdkVersion of 5 here are the
rules for maxJdkVersion
<plugin>
<artifactId>maven-enforcer-plugin</artifactId>
<executions>
<execution>
<id>enforce-bytecode-version</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<enforceBytecodeVersion>
<maxJdkVersion>1.5</maxJdkVersion>
I have not used Java5 in about 5 years so Im wondering why is doxia hardgated
to Java 1.5 ?
You answered that question already yourself...in the other thread about
the VOTE for Maven ChangeLog Plugin 2.3 where you wrote (Unfortunately
you didn't answer my questions):
As far as deprecating ..be mindful that Maven is used by over 100,000
shops for production builds
which means simply upgrading an requirement is not that simple...and
currently there is not really a requirement to drop 1.5 support...
Kind regards
Karl-Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
