Hi,

> On 15/03/18 12:51, Thorsten Heit wrote:
> > Hi,
> > 
> >> The Apache Maven team is pleased to announce the release of the
> >> Apache Maven EAR Plugin Version 3.0.0
> > 
> > First of all thanks for releasing a new version of this plugin!
> > 
> > I just gave it a try in an internal multi-module project, but now I 
can't
> > deploy the EAR anymore to Wildfly 11 server from within Eclipse:
> 
> 
> Sorry to say...you have expected that major version change to not change 

> something ? ...Maybe I misunderstand a thing here...

That was absolutely not my intention :-)
I don't mind if there are changes when a major version is released.


> > Result:
> > After the copying process has finished, Wildfly doesn't start the EAR
> > because it cannot find the WAR module that is referenced in the
> > application.xml....
> 
> If I correctly understand that's only happening within Eclipse?

Yes, that's what I'm seeing. Building the EAR from the command line works 
(as expected).


> The 3.0.0 version contains a change to handle all the time by default a 
> full mapping of artifact names which is noticed on the start page:
> 
> http://maven.apache.org/plugins/maven-ear-plugin/
> 
> There is <outputFileNameMapping> which by default contains:
> 
> @{groupId}@-@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@
> 
> So if you like to go back just change this configuration in your build 
> and it should work as before but with the risk of failing in case of 
> same artifactId's..

Ok, thanks, I'll give this a try.
I guess I won't have failing builds because that's what would already have 
happened actually with m-ear-p 2.10.1 ;-)

OTOH, do you know who is responsible for the now invalid output file 
mapping with m-ear-p 3.0.0 when I'm deploying the EAR in Eclipse to a 
Wildfly server instance? It seems to me that at least in this part there's 
a bug (?) because the (change in the) output file name mapping isn't 
respected...


Side note:
I like the idea of having the group Id in the file name for artifacts. Is 
something similar planned for m-war-p?


Regards

Thorsten

Reply via email to