From issues-return-131856-archive-asf-public=cust-asf.ponee.io@maven.apache.org Tue Apr 24 20:24:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B1F65180671 for ; Tue, 24 Apr 2018 20:24:03 +0200 (CEST) Received: (qmail 25099 invoked by uid 500); 24 Apr 2018 18:24:02 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 25088 invoked by uid 99); 24 Apr 2018 18:24:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Apr 2018 18:24:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 4F104C81A2 for ; Tue, 24 Apr 2018 18:24:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id O9biY5P_Rt-5 for ; Tue, 24 Apr 2018 18:24:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 3FF585F3CE for ; Tue, 24 Apr 2018 18:24:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id AD7E4E0375 for ; Tue, 24 Apr 2018 18:24:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 6587A241C6 for ; Tue, 24 Apr 2018 18:24:00 +0000 (UTC) Date: Tue, 24 Apr 2018 18:24:00 +0000 (UTC) From: "Leonid Rozenblyum (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MEAR-267) assembly.xml contains incorrect references to modules MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MEAR-267?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Rozenblyum updated MEAR-267: ----------------------------------- Description:=20 SCENARIO: Create a=C2=A0EAR project with maven-ear-plugin 3.0.0 execute mvn ear:ear EXPECTED: assembly.xml contains reference to the jar/war equivalent to their physical= names inside the EAR (e.g. if the jar is named=C2=A0tryEar-ejb-1.0-SNAPSHOT.jar then assembly.xm= l reference would be: tryEar-ejb-1.0-SNAPSHOT.jar (this worked in 2.10.1) ACTUALLY: assembly.xml contains reference com.leokom-tryEar-ejb-1.0-SNAPSHOT.jar =C2=A0 Due to this difference - JBoss/WildFly cannot deploy the EAR. (it's easy to reproduce: you may create a ear project from some standard on= es from maven-archetypes and change maven-ear-plugin version to 3.0.0). =C2=A0 UPDATE: Sorry, maybe it's a bug in M2E-WTP plugin of Eclipse. I tried this = scenario in standalone mode without Eclipse - and=C2=A0assembly.xml is cons= istent with the jar files was: SCENARIO: Create a=C2=A0EAR project with maven-ear-plugin 3.0.0 execute mvn ear:ear EXPECTED: assembly.xml contains reference to the jar/war equivalent to their physical= names inside the EAR (e.g. if the jar is named=C2=A0tryEar-ejb-1.0-SNAPSHOT.jar then assembly.xm= l reference would be: tryEar-ejb-1.0-SNAPSHOT.jar (this worked in 2.10.1) ACTUALLY: assembly.xml contains reference com.leokom-tryEar-ejb-1.0-SNAPSHOT.jar =C2=A0 Due to this difference - JBoss/WildFly cannot deploy the EAR. (it's easy to reproduce: you may create a ear project from some standard on= es from maven-archetypes and change maven-ear-plugin version to 3.0.0). =C2=A0 Sorry, maybe it's a bug in M2E-WTP plugin of Eclipse. I tried this scenario= in standalone mode without Eclipse - and=C2=A0assembly.xml is consistent w= ith the jar files > assembly.xml contains incorrect references to modules > ----------------------------------------------------- > > Key: MEAR-267 > URL: https://issues.apache.org/jira/browse/MEAR-267 > Project: Maven Ear Plugin > Issue Type: Bug > Affects Versions: 3.0.0 > Reporter: Leonid Rozenblyum > Priority: Major > > SCENARIO: > Create a=C2=A0EAR project with maven-ear-plugin 3.0.0 > execute mvn ear:ear > EXPECTED: > assembly.xml contains reference to the jar/war equivalent to their physic= al names inside > the EAR > (e.g. if the jar is named=C2=A0tryEar-ejb-1.0-SNAPSHOT.jar then assembly.= xml reference would be: > > tryEar-ejb-1.0-SNAPSHOT.jar > > (this worked in 2.10.1) > ACTUALLY: > assembly.xml contains reference > > com.leokom-tryEar-ejb-1.0-SNAPSHOT.jar > > =C2=A0 > Due to this difference - JBoss/WildFly cannot deploy the EAR. > (it's easy to reproduce: you may create a ear project from some standard = ones from maven-archetypes and change maven-ear-plugin version to 3.0.0). > =C2=A0 > UPDATE: Sorry, maybe it's a bug in M2E-WTP plugin of Eclipse. I tried thi= s scenario in standalone mode without Eclipse - and=C2=A0assembly.xml is co= nsistent with the jar files -- This message was sent by Atlassian JIRA (v7.6.3#76005)