That was odd. I deleted all the log4j artifacts in my local repo and now it is fine.
Ralph On Apr 5, 2014, at 2:11 PM, Matt Sicker <[email protected]> wrote: > What errors are you getting anyway? > > > On 5 April 2014 16:10, Matt Sicker <[email protected]> wrote: > Oh, that makes sense. I tried doing that and it worked for me. I'll try > cleaning my log4j maven cache and doing that again. > > > On 5 April 2014 16:05, Ralph Goers <[email protected]> wrote: > First run mvn clean install on log4j-api. Then run mvn clean compile, mvn > clean install, or mvn clean test in log4j-core. I can’t get any of them to > work. I do all my unit testing using mvn test -Dtest=xxxxx > -Dmaven.surefire.debug=“remote debug options” and the compile is failing, so > I can’t debug anything. > > Ralph > > On Apr 5, 2014, at 1:43 PM, Matt Sicker <[email protected]> wrote: > >> Oh wait, using mvn compile. I've never gotten that to work without doing a >> mvn install first. >> >> >> On 5 April 2014 15:42, Matt Sicker <[email protected]> wrote: >> Compiling fine for me. I don't see any changes to any of the pom.xml files >> lately. >> >> >> On 5 April 2014 15:26, Ralph Goers <[email protected]> wrote: >> If I do a mvn clean install on the whole project everything builds fine. >> But if I just try to rebuild log4j-core with mvn clean compile I get a bunch >> of compile errors. Did somebody screw up the pom.xml? >> >> Ralph >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> >> >> -- >> Matt Sicker <[email protected]> >> >> >> >> -- >> Matt Sicker <[email protected]> > > > > > -- > Matt Sicker <[email protected]> > > > > -- > Matt Sicker <[email protected]>
