Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 35B82DC80 for ; Sun, 2 Sep 2012 18:56:08 +0000 (UTC) Received: (qmail 25010 invoked by uid 500); 2 Sep 2012 18:56:08 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 24645 invoked by uid 500); 2 Sep 2012 18:56:07 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 24634 invoked by uid 99); 2 Sep 2012 18:56:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Sep 2012 18:56:07 +0000 Date: Mon, 3 Sep 2012 05:56:07 +1100 (NCT) From: "Bruno Borges (JIRA)" To: dev@activemq.apache.org Message-ID: <444534889.28904.1346612167781.JavaMail.jiratomcat@arcas> In-Reply-To: <2026218754.27407.1340062362677.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (AMQ-3888) Better Maven dependency for some specs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447001#comment-13447001 ] Bruno Borges commented on AMQ-3888: ----------------------------------- Can't that be another artifact? Something like activemq-jee-specs ? It's better to add one dependency (to run on Tomcat; which would conflict anyway with the jetty dependnecy today) than having to exclude 8 artifacts or define them one by one with 'provided' scope. > Better Maven dependency for some specs > -------------------------------------- > > Key: AMQ-3888 > URL: https://issues.apache.org/jira/browse/AMQ-3888 > Project: ActiveMQ > Issue Type: Improvement > Components: Broker > Affects Versions: 5.6.0 > Reporter: Bruno Borges > > It seems that, to have ActiveMQ component for Camel run fine on a JBoss instance, I had to add all these dependencies as 'provided' to avoid specs artifacts falling on my WEB-INF/lib. > Would be nice to have this fixed on the next release of ActiveMQ > > > org.apache.activemq > activemq-camel > > > org.apache.activemq > activemq-pool > > > > org.apache.geronimo.specs > geronimo-jta_1.0.1B_spec > 1.0.1 > provided > > > org.apache.geronimo.specs > geronimo-jms_1.1_spec > 1.1.1 > provided > > > org.apache.geronimo.specs > geronimo-j2ee-management_1.1_spec > 1.0.1 > provided > > > javax.inject > javax.inject > 1 > provided > > > org.mortbay.jetty > jsp-api-2.1 > 6.1.4 > provided > > > org.mortbay.jetty > jsp-2.1 > 6.1.4 > provided > > > javax.annotation > jsr250-api > 1.0 > provided > > > com.google.code.findbugs > jsr305 > 1.3.9 > provided > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira