Yes - character encodings are always a nightmare. I'd say the by far best
solution (if at all possible) is to change your database configuration and
use UTF-8 throughout. Latin-1 is a bad idea, even if you're only planning to
support Norwegian in your application. I've lost count of the number of
h
e it is a necessity for us and I don't at all enjoy the
prospect of going back to the complexity of configuring Cruisecontrol
again.. :(
/ Petter
> -Original Message-
> From: Petter Måhlén [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 15, 2007 3:32 PM
> To: [EMAIL P
Hi,
We have a setup that works well during development but doesn't agree with
Continuum's philosophy of how to handle things - or so it seems to me. I
think there is a point in doing it another way than we are, but I am not
sure how. Hopefully, somebody here can enlighten me. :)
We have three pro
http://svn.apache.org/repos/asf/maven/continuum/trunk/continuu
> m-core/src/main/java/org/apache/maven/continuum/utils/ProjectS
> orter.java
> We don't look for the moment at plugins dependencies.
>
> Emmanuel
>
> Petter Måhlén a écrit :
> > I haven't done it like
erver/pom.xml
> ...common...
>
> client/pom.xml
> ...server, common... or
> ...server... and common will be pulled in
> via transitive dependencies
>
> Is there a reason you can't set things up like this, or why this won't
> work for you?
>
> Wayne
&g
Hi,
I have a question concerning what I can do to force projects to be built in
a specific order. There have been some previous similar queries, but they
don't quite seem to apply to our situation. What we want is this:
1. 'mvn clean install' for project 'common': this leads to a jar file with
co
