-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
log4j 1.2: Hybrid Maven/Ant build stuff - antrun ant junit tests breaking - MinimumTestCase failed #21
Comments
Here's the underlying unit test failure, I think:
Now, that looks like actual incorrect behavior maybe. (Though why are the X in "output/X" and "witness/X" different?) Gonna have to figure this out before I do a release. Here's the full stacktrace:
|
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The log4j 1.2.x Maven
pom.xml
delegates a bunch of its activity toant
using the Mavenantrun
plugin. I don't know why it does this; maybemvn
wasn't powerful enough back in 2007? Anyway, it's causing me trouble. Like, here's a test failure that's happening not in the Maven surefire plugin, but inside an ant task called from the antrun plugin, inmvn assembly:assembly
:I do not understand why this is happening, how to fix it, or how to get at
ant
's debug output here, without going out and fiddling with ant'sbuild.xml
.The Maven antrun documentation discourages this hybrid approach, basically saying that antrun is for totally delegating the build to
ant
, but providing a Maven wrapper interface for it.(Wait - log4j is an Apache project itself; why is it going against the apparent advice of the antrun plugin?) Or maybe I'm misinterpreting this sentence, and it actually means "hybrid use of Maven and Ant is fine, but don't pull your whole ant
build.xml
into thepom.xml
and its XML document structure; keep them as separate files"?Dunno if it'd be easier to fix this one issue inside
ant
, or try to pull the whole build in to Maven. I wish there were developer documentation in log4j about this design choice.The text was updated successfully, but these errors were encountered: