binding ant plugin to specific packaging

Hello, I've been working on what I'd hoped would be a fairly simple plugin in Ant, but I'm coming up against great difficulty trying to get it bound only to those project which I want it to execute for. I've tried every hack I can think of, from trying to override inherited plugin configuratio

multiproject and util:available, strange behavior all of a sudden

is looking for it relative to the sub-project, 'searchengine' directory. This behavior is strange enough, but stranger still is that I can't for the life of me figure out what changed to make this happen. If anyone could provide any insight into either or both of these mysteries,

Re: problem *not* forking unit tests

is "thou shall fork", not forking is a real classpath mess between maven and project classpath (and caused your problem), I don't think not forking is ever a good idea. Julien Micah Craig wrote: Hi, I just upgraded from rc1 to 1.0.1, and suddenly, I can't run JUnit t

problem *not* forking unit tests

Hi, I just upgraded from rc1 to 1.0.1, and suddenly, I can't run JUnit tests un-forked (maven.junit.fork=no). Failure output is below. Could this be some sort of mangled classpath issue left over from the upgrade, or is something more sinister afoot. Thanks, -micah BUILD FAILED File...

problem *not* forking unit tests

Hi, I just upgraded from rc1 to 1.0.1, and suddenly, I can't run JUnit tests un-forked (maven.junit.fork=no). Failure output is below. Could this be some sort of mangled classpath issue left over from the upgrade, or is something more sinister afoot. Thanks, -micah BUILD FAILED File..