Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of Andreas.Guther@markettools.com
 designates 72.5.112.150 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C89035.071C11E9"
Subject: Snapshot dependency in released ActiveMQ 5.0.0 must be removed
Date: Thu, 27 Mar 2008 11:04:37 -0700
Message-ID: 
 <3FB08D6A21B3EC4D8749EF6D9E62627802ADC6AC@WDCCPMAIL01.markettools.com>
Thread-Topic: Snapshot dependency in released ActiveMQ 5.0.0 must be removed
Thread-Index: AciQNQV001RpOiYXRuW2xfdaiLILtw==
From: "Andreas Guther" <Andreas.Guther@markettools.com>
To: <users@activemq.apache.org>

------_=_NextPart_001_01C89035.071C11E9
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I moved this morning to ActiveMQ 5.0.0 and encountered problems with the
dependency on org.apache.activemq:activeio-core:jar:3.1-SNAPSHOT. This
led me to the following thread:
http://www.mail-archive.com/users@activemq.apache.org/msg04738.html

=20

Using the exclusion fixed my problem.  But I what I found disturbing is
the dependency of a released version on SNAPSHOTS.  This in my eyes not
acceptable and anyone who uses the Maven release process will not be
able to release the application since a build will be refused if any
SNAPSHOT dependency is detected.  This makes totally sense since a
SNAPSHOT is consider as un unstable version and as we can see might
disappear any time.

=20

I think that the dependency needs to be fixed in ActiveMQ 5.0.x as soon
as possible.

=20

Andreas

=20


------_=_NextPart_001_01C89035.071C11E9--