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).
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
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
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
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
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
: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
