On Thursday 30 April 2009 Martin Höller wrote: > The question I now have is, why is source:jar mojo executed at all? > According to the lifecycle reference [1] this mojo shouldn't be executed > (for packaging EAR). How can I deactivate this mojo?
The release-profile seems to introduce the m-source-p into my build. Is this a good idea for EAR packaging? EARs usually don't have java files attached. Any thoughts? - martin PS: For the moment I switched back to maven-source-plugin 2.0.4.
signature.asc
Description: This is a digitally signed message part.
