You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Johan Compagner <jc...@gmail.com> on 2009/02/18 13:58:17 UTC
maven guru/wickstuff project maintainers..
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
Re: maven guru/wickstuff project maintainers..
Posted by Johan Compagner <jc...@gmail.com>.
As far as i see TeamCity works fine
For example inmethod-grid of matej is doing just fine IF i only checkout
inmethod grid:
+:/trunk/wicketstuff-core/inmethod-grid-parent/inmethod-grid=>.
But if i want to build everything so the parent and the examples and the
grid as once and i checkoout this:
+:/trunk/wicketstuff-core/inmethod-grid-parent=>.
Then it adds that stupid version number. So somehow it is a maven
configuration issue!
I guess the parent of inmethod-grip doesnt have the right deploy stuff? and
the inmethod-grid itself does?
johan
On Thu, Feb 19, 2009 at 09:26, Martijn Dashorst
<ma...@gmail.com>wrote:
> I'm willing to move to hudson (though I don't think hudson's interface
> is inspiring). There has been some discussion moving for Wicket core
> stuff to the Apache based hudson, but I haven't seen that much
> benefits from it. I might follow up on that.
>
> Martijn
>
> On Thu, Feb 19, 2009 at 9:16 AM, Johan Compagner <jc...@gmail.com>
> wrote:
> > 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
> > <je...@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.wael@gmail.com> wrote:
> >>
> >> > I see this is a issue for wicketstuff core aswell
> >> >
> >> > 2009/2/18 Johan Compagner <jc...@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
> >> > >
> >> >
> >>
> >
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.5 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: maven guru/wickstuff project maintainers..
Posted by nino martinez wael <ni...@gmail.com>.
One thing though is that you can get historical metrics(for available
plugins), im not sure if you get that with the other build servers..
2009/2/19 Martijn Dashorst <ma...@gmail.com>
> I'm willing to move to hudson (though I don't think hudson's interface
> is inspiring). There has been some discussion moving for Wicket core
> stuff to the Apache based hudson, but I haven't seen that much
> benefits from it. I might follow up on that.
>
> Martijn
>
> On Thu, Feb 19, 2009 at 9:16 AM, Johan Compagner <jc...@gmail.com>
> wrote:
> > 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
> > <je...@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.wael@gmail.com> wrote:
> >>
> >> > I see this is a issue for wicketstuff core aswell
> >> >
> >> > 2009/2/18 Johan Compagner <jc...@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
> >> > >
> >> >
> >>
> >
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.5 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: maven guru/wickstuff project maintainers..
Posted by Martijn Dashorst <ma...@gmail.com>.
I'm willing to move to hudson (though I don't think hudson's interface
is inspiring). There has been some discussion moving for Wicket core
stuff to the Apache based hudson, but I haven't seen that much
benefits from it. I might follow up on that.
Martijn
On Thu, Feb 19, 2009 at 9:16 AM, Johan Compagner <jc...@gmail.com> wrote:
> 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
> <je...@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.wael@gmail.com> wrote:
>>
>> > I see this is a issue for wicketstuff core aswell
>> >
>> > 2009/2/18 Johan Compagner <jc...@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
>> > >
>> >
>>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: maven guru/wickstuff project maintainers..
Posted by Johan Compagner <jc...@gmail.com>.
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.wael@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 <jc...@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
> > <je...@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.wael@gmail.com> wrote:
> > >
> > > > I see this is a issue for wicketstuff core aswell
> > > >
> > > > 2009/2/18 Johan Compagner <jc...@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
> > > > >
> > > >
> > >
> >
>
Re: maven guru/wickstuff project maintainers..
Posted by nino martinez wael <ni...@gmail.com>.
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 <jc...@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
> <je...@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.wael@gmail.com> wrote:
> >
> > > I see this is a issue for wicketstuff core aswell
> > >
> > > 2009/2/18 Johan Compagner <jc...@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
> > > >
> > >
> >
>
Re: maven guru/wickstuff project maintainers..
Posted by Johan Compagner <jc...@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
<je...@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.wael@gmail.com> wrote:
>
> > I see this is a issue for wicketstuff core aswell
> >
> > 2009/2/18 Johan Compagner <jc...@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
> > >
> >
>
Re: maven guru/wickstuff project maintainers..
Posted by Johan Compagner <jc...@gmail.com>.
i see that wicket1.3 jdk1.4 is using these goals:
-Pbamboo-jdk-1.4 clean deploy
On Thu, Feb 19, 2009 at 08:03, Martin Funk <ma...@googlemail.com>wrote:
> But those are only defined in profiles:
> 'bamboo' and 'wickettraining.com-continuum'
>
> are those profiles pulled for the builds?
>
> mf
>
> Am 18.02.2009 um 22:07 schrieb Jeremy Thomerson:
>
>
> 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.wael@gmail.com> wrote:
>>
>> I see this is a issue for wicketstuff core aswell
>>>
>>> 2009/2/18 Johan Compagner <jc...@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
>>>>
>>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: maven guru/wickstuff project maintainers..
Posted by Martin Funk <ma...@googlemail.com>.
But those are only defined in profiles:
'bamboo' and 'wickettraining.com-continuum'
are those profiles pulled for the builds?
mf
Am 18.02.2009 um 22:07 schrieb Jeremy Thomerson:
> 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.wael@gmail.com> wrote:
>
>> I see this is a issue for wicketstuff core aswell
>>
>> 2009/2/18 Johan Compagner <jc...@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
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: maven guru/wickstuff project maintainers..
Posted by Jeremy Thomerson <je...@wickettraining.com>.
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.wael@gmail.com> wrote:
> I see this is a issue for wicketstuff core aswell
>
> 2009/2/18 Johan Compagner <jc...@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
> >
>
Re: maven guru/wickstuff project maintainers..
Posted by nino martinez wael <ni...@gmail.com>.
I see this is a issue for wicketstuff core aswell
2009/2/18 Johan Compagner <jc...@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
>