and now it works fine. I think it is the network between that server and wicketstuff somehow.
Because it is really not reachable when making a socket connection i will try to monitor it On Thu, Feb 19, 2009 at 09:34, nino martinez wael < nino.martinez.w...@gmail.com> wrote: > Yeah I know.. I reported that to sourceforge months ago... :/ And it seems > to be very unpredictable.. > > However Jeremy's server seems to have no problems.. > > 2009/2/19 Johan Compagner <jcompag...@gmail.com> > > > First i also have to checkout why this happens and why it happens only to > > sourceforge wicketstuff > > only from that server > > > > Caused by: java.net.ConnectException: Network is unreachable > > at java.net.PlainSocketImpl.socketConnect(Native Method) > > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) > > at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) > > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) > > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) > > at java.net.Socket.connect(Socket.java:519) > > at > > > > > org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createPlainSocket(SVNSocketFactory.java:53) > > > > Yesterday everything worked fine. Today i get those errors again > > > > johan > > > > > > On Wed, Feb 18, 2009 at 22:07, Jeremy Thomerson > > <jer...@wickettraining.com>wrote: > > > > > Yes - all wicketstuff-core projects appear to be generating timestamped > > > snapshots, which they shouldn't be. The wicketstuff-core parent pom > [1] > > > has > > > the proper line in it (I think) to exclude this from happening: > > > > > > <uniqueVersion>false</uniqueVersion> > > > > > > Continuum is still running on my server [2], building the > > wicketstuff-core > > > projects and deploying to an alternate repo [3] (including javadoc > > > snapshots). Everything there seems to be running fine, and it's not > > > generating timestamped snapshots. Perhaps this is a problem with > > TeamCity? > > > Maybe a Maven / TeamCity guru can help more, but I tried to make sure > > that > > > it wouldn't do this. I never have liked TeamCity too much. > > > > > > Let me know how I can be of assistance. I don't mind hosting these > repos > > > on > > > my servers. And I don't mind keeping Continuum running - it has been > > very > > > easy. > > > > > > PS - Continuum is also building the site:deploy goal on my server, and > > > deploying the sites publicly [4], including nice html views of the > source > > > in > > > the reports section for each project. > > > > > > [1] - > > > > > > > > > https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-core/pom.xml > > > [2] - http://www.wickettraining.com/continuum/ > > > [3] - http://www.wickettraining.com/ws-snaps/ > > > [4] - http://www.wickettraining.com/ws-sites/ > > > > > > > > > -- > > > Jeremy Thomerson > > > http://www.wickettraining.com > > > > > > > > > On Wed, Feb 18, 2009 at 8:41 AM, nino martinez wael < > > > nino.martinez.w...@gmail.com> wrote: > > > > > > > I see this is a issue for wicketstuff core aswell > > > > > > > > 2009/2/18 Johan Compagner <jcompag...@gmail.com> > > > > > > > > > Hi, > > > > > > > > > > if i look into this dir: > > > > > > > > > > > > > > > > > > > > > > > > > http://www.wicketstuff.org/maven/repository/org/wicketstuff/scriptaculous/1.4-SNAPSHOT/ > > > > > > > > > > i am getting really really sad :( > > > > > > > > > > I want to get rid of all those horrible timestamps snapshots > > > > > these should be removed for everything, this will run out of disk > > space > > > > > soon > > > > > like that > > > > > > > > > > i think it has to do something in the profiles and then > > > > > distributionManagement ?? > > > > > > > > > > <distributionManagement> > > > > > <snapshotRepository> > > > > > <id>repo</id> > > > > > <name>Local Bamboo/Tomcat repository</name> > > > > > > > > > > <url>file:/home/wicket/tomcat/webapps/maven/repository/</url> > > > > > <uniqueVersion>false</uniqueVersion> > > > > > </snapshotRepository> > > > > > </distributionManagement> > > > > > > > > > > also wicket 1.3 has the same problem. i guess because the jdk1.4 > and > > > > jdk1.5 > > > > > dirs dont have the right stuff? > > > > > Or is the wrong profiler being done? Where can this be changed? > > > > > > > > > > johan > > > > > > > > > > > > > > >
