Could you also have a look at ./client/tomcatconf/log4j-cloud.xml.in?
It looks like it was updated in the refactor.
AFAIK, in '<param name="ConversionPattern" value="%-5p [%c{1.}] (%t:%x)
%m%n"/>', {1.} should be {1}.
See "Conversion Character" chart under
http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html
There's a lot of paper work for me to make the update :(
DL
> -----Original Message-----
> From: Alex Huang [mailto:[email protected]]
> Sent: 29 July 2013 6:56 PM
> To: [email protected]
> Subject: RE: [DISCUSS] maven dependencies...
>
> Thanks for pointing that out. I think the latest fixed this.
>
> --Alex
>
> > -----Original Message-----
> > From: Donal Lafferty [mailto:[email protected]]
> > Sent: Monday, July 29, 2013 10:45 AM
> > To: [email protected]
> > Subject: RE: [DISCUSS] maven dependencies...
> >
> > Is it correct for dependencies to appear twice in the base pom.xml?
> >
> > E.g. mysql-connector-java
> >
> > > -----Original Message-----
> > > From: Alex Huang [mailto:[email protected]]
> > > Sent: 26 July 2013 11:10 PM
> > > To: [email protected]
> > > Subject: [DISCUSS] maven dependencies...
> > >
> > > Everyone,
> > >
> > > After looking around in the maven documentation, I realized the way
> > > we are specifying dependencies is not quite right for a large
> > > project such as
> > ours.
> > >
> > > Currently, almost every project declare their own dependencies and
> > > version number of the dependent jar. For those of us who are
> > > conscious of the version number properties declared in the
> > > cloudstack pom file, we follow that example but in many places, the
> > > version numbers are actually hard coded, probably because the writer
> > > is not aware
> > of this.
> > >
> > > Maven actually has a way to do this. In the master pom file, we can
> > > declare in the <dependencyManagment> tags all of the third party
> > > dependencies we need and their version numbers. And then each
> > > individual module can declare their dependency without version
> > > number, which defaults to the version declared by CloudStack's
> > > master pom. If a version number is declared in the module's pom, it
> > > overrides the master's version number but there's a warning about this
> override.
> > >
> > > Sounds good? If so I'll do a quick change to move it over.
> > >
> > > --Alex
