I just added a jtidy-8.0-20060801 into the local repo, which was the latest SNAPSHOT version that was out on the sf.net repo.

-Donald

Jarek Gawor wrote:
Thanks, you beat me to it! I'll also update branches/2.0.

Jarek

On Feb 7, 2008 12:15 PM, Donald Woods <[EMAIL PROTECTED]> wrote:
I just removed the bottom 3 in the 2.1 branch with Rev619508 based on
the changes you made in trunk.  I'll start looking at pulling jtidy into
the local repo next.

-Donald


Jarek Gawor wrote:
I just performed a quick scan for direct snapshot dependencies in
branches/2.1, here's the list (excluding jacc spec and
ejbcontainer-tests):

./buildsupport/testsuite-maven-plugin/pom.xml: jtidy 8.0-SNAPSHOT
./plugins/monitoring/agent-jmx/pom.xml: xbean-naming 3.4-SNAPSHOT
./testsuite/pom.xml: maven-surefire-plugin 2.3-SNAPSHOT
./buildsupport/geronimo-maven-plugin/pom.xml surefire-api 2.1-SNAPSHOT

Jarek

On Feb 6, 2008 2:22 PM, Kevan Miller <[EMAIL PROTECTED]> wrote:
On Feb 6, 2008, at 1:26 PM, Donald Woods wrote:

Should we fix the following SNAPSHOT depends, which break offline
builds in 2.1 or wait for 2.1.1?

I can make the changes this afternoon...
We won't be releasing with direct SNAPSHOT dependencies. These will
all be updated as part of the release process.

It may be that the release plugin could be used to detect improper,
transitive SNAPSHOT dependencies.

If you have specific proposals, would be happy to hear about them.

--kevan


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to