Hi!
I just figured that we still pretty often use the java.net maven repositories.
They are not well maintained and often lead to weird problems. Today I tried to
compile tomahawk and got a weird exception that shale-master-1.pom is broken.
Also, if we use Java JSR spec APIs we should always
Am 19.08.2010 16:58, schrieb Mark Struberg:
I just figured that we still pretty often use the java.net maven repositories.
They are not well maintained and often lead to weird problems. Today I tried to
compile tomahawk and got a weird exception that shale-master-1.pom is broken.
Had the same
On Thu, Aug 19, 2010 at 6:00 PM, Michael Kurz michi.k...@gmx.at wrote:
Am 19.08.2010 16:58, schrieb Mark Struberg:
I just figured that we still pretty often use the java.net maven
repositories.
They are not well maintained and often lead to weird problems. Today I
tried to
compile tomahawk
...@gmx.at
To: dev@myfaces.apache.org
Sent: Thu, August 19, 2010 6:00:00 PM
Subject: Re: [DISCUSS] getting rid of all java.net maven repositories
Am 19.08.2010 16:58, schrieb Mark Struberg:
I just figured that we still pretty often use the java.net maven
repositories.
They are not well
s/tomcat/tomahawk/ ;)
- Original Message
From: Mark Struberg strub...@yahoo.de
To: MyFaces Development dev@myfaces.apache.org
Sent: Thu, August 19, 2010 7:15:44 PM
Subject: Re: [DISCUSS] getting rid of all java.net maven repositories
I also found out that we use 4 different
strub...@yahoo.de
To: MyFaces Development dev@myfaces.apache.org
Sent: Thu, August 19, 2010 7:15:44 PM
Subject: Re: [DISCUSS] getting rid of all java.net maven repositories
I also found out that we use 4 different versions of shale-test in
tomahawk.
And shale-test-1.0.3 is pulling
