Wicketstuff core repository deployment
It seems like artifacts for the projects/modules under wicketstuff-core are not deployed to the maven repository anymore. Is this being addressed? I do not see any deployment configuration in the pom.xml for wicketstuff-core, or its modules (I checked a few).
Re: Wicketstuff core repository deployment
Hmm, I though that Jeremy were into this.. Pointbreak wrote: It seems like artifacts for the projects/modules under wicketstuff-core are not deployed to the maven repository anymore. Is this being addressed? I do not see any deployment configuration in the pom.xml for wicketstuff-core, or its modules (I checked a few). -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684
Re: Wicketstuff core repository deployment
Sorry - I've been out of town. I'm working on it this morning It's still just a build problem with the TeamCity server trying to resolve com.sun stuff, which hasn't been manually installed on that server. In the meantime, my Continuum server is building and deploying the artifact snapshots and the sites: http://www.wickettraining.com/ws-snaps/ http://www.wickettraining.com/ws-sites/ You could use that for now, although we still need to get the official repository working. -- Jeremy Thomerson http://www.wickettraining.com On Wed, Dec 10, 2008 at 10:14 AM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: Hmm, I though that Jeremy were into this.. Pointbreak wrote: It seems like artifacts for the projects/modules under wicketstuff-core are not deployed to the maven repository anymore. Is this being addressed? I do not see any deployment configuration in the pom.xml for wicketstuff-core, or its modules (I checked a few). -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684
Re: Wicketstuff core repository deployment
Okay, this is fixed. The problem was that in the pom we had updated the dependency on log4j to 1.2.15, which for some odd reason now includes dependencies on com.sun*. So, I reverted that to 1.2.14 and it's working. I'll look more in depth at all these version things later. -- Jeremy Thomerson http://www.wickettraining.com On Wed, Dec 10, 2008 at 10:24 AM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Sorry - I've been out of town. I'm working on it this morning It's still just a build problem with the TeamCity server trying to resolve com.sun stuff, which hasn't been manually installed on that server. In the meantime, my Continuum server is building and deploying the artifact snapshots and the sites: http://www.wickettraining.com/ws-snaps/ http://www.wickettraining.com/ws-sites/ You could use that for now, although we still need to get the official repository working. -- Jeremy Thomerson http://www.wickettraining.com On Wed, Dec 10, 2008 at 10:14 AM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: Hmm, I though that Jeremy were into this.. Pointbreak wrote: It seems like artifacts for the projects/modules under wicketstuff-core are not deployed to the maven repository anymore. Is this being addressed? I do not see any deployment configuration in the pom.xml for wicketstuff-core, or its modules (I checked a few). -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684
Re: Wicketstuff core repository deployment
Thanks! One remark: do I understand correctly that if the build of one of the wicketstuff-core modules fails, this will prevent other core modules from being built and deployed? On Wed, 10 Dec 2008 10:39:19 -0600, Jeremy Thomerson [EMAIL PROTECTED] wrote: Okay, this is fixed. The problem was that in the pom we had updated the dependency on log4j to 1.2.15, which for some odd reason now includes dependencies on com.sun*. So, I reverted that to 1.2.14 and it's working. I'll look more in depth at all these version things later. -- Jeremy Thomerson http://www.wickettraining.com
RE: Wicketstuff core repository deployment
Only with the way it's set up on TeamCity. Continuum automatically breaks all the modules into individual builds. In my opinion, it is MUCH easier to set up and use. You can see mine at http://www.wickettraining.com/continuum. Anyway, we can set up individual module builds (see inmethod) on TeamCity, I just haven't done it yet. Jeremy Thomerson http://www.wickettraining.com -- sent from a wireless device -Original Message- From: Pointbreak [EMAIL PROTECTED] Sent: Wednesday, December 10, 2008 1:14 PM To: Wicket Dev Mailing List dev@wicket.apache.org Subject: Re: Wicketstuff core repository deployment Thanks! One remark: do I understand correctly that if the build of one of the wicketstuff-core modules fails, this will prevent other core modules from being built and deployed? On Wed, 10 Dec 2008 10:39:19 -0600, Jeremy Thomerson [EMAIL PROTECTED] wrote: Okay, this is fixed. The problem was that in the pom we had updated the dependency on log4j to 1.2.15, which for some odd reason now includes dependencies on com.sun*. So, I reverted that to 1.2.14 and it's working. I'll look more in depth at all these version things later. -- Jeremy Thomerson http://www.wickettraining.com
Re: Wicketstuff core repository deployment
Very nice, I like the fact that it's so structured... Jeremy Thomerson wrote: Only with the way it's set up on TeamCity. Continuum automatically breaks all the modules into individual builds. In my opinion, it is MUCH easier to set up and use. You can see mine at http://www.wickettraining.com/continuum. Anyway, we can set up individual module builds (see inmethod) on TeamCity, I just haven't done it yet. Jeremy Thomerson http://www.wickettraining.com -- sent from a wireless device -Original Message- From: Pointbreak [EMAIL PROTECTED] Sent: Wednesday, December 10, 2008 1:14 PM To: Wicket Dev Mailing List dev@wicket.apache.org Subject: Re: Wicketstuff core repository deployment Thanks! One remark: do I understand correctly that if the build of one of the wicketstuff-core modules fails, this will prevent other core modules from being built and deployed? On Wed, 10 Dec 2008 10:39:19 -0600, Jeremy Thomerson [EMAIL PROTECTED] wrote: Okay, this is fixed. The problem was that in the pom we had updated the dependency on log4j to 1.2.15, which for some odd reason now includes dependencies on com.sun*. So, I reverted that to 1.2.14 and it's working. I'll look more in depth at all these version things later. -- Jeremy Thomerson http://www.wickettraining.com -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684
