[
https://jira.codehaus.org/browse/MEAR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286306#comment-286306
]
Dennis Lundberg commented on MEAR-60:
-------------------------------------
Hi Andreas,
I've done some more testing and have come to the following conclusions:
* When you "mvn install" something into the local repo it will always be a
-SNAPSHOT version
* When you "mvn deploy" something it will depend on the settings of the repo
and which version of Maven you use. Maven 3 will always deploy a timestamped
version in the remote repo
* I haven't been able to successfully remove a timestamped version from a WAR
using your custom fileNameMapper. When I run my test project version and
baseVersion are always the same
It seems to me that it is the WAR plugin that is at fault here. It should IMO
not include timestamped versions of JARs inside a WAR.
> Improve support for skinny war files
> ------------------------------------
>
> Key: MEAR-60
> URL: https://jira.codehaus.org/browse/MEAR-60
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3
> Environment: mvn 2.0.5
> Reporter: Marcel Schutte
> Assignee: Dennis Lundberg
> Priority: Critical
> Fix For: 2.7
>
> Attachments: maven-ear-plugin-addon-1.0-SNAPSHOT.jar,
> maven-ear-plugin-addon-1.0-SNAPSHOT-sources.jar,
> maven-ear-plugin-MEAR-60.patch
>
>
> Provide a boolean configuration option for webModules to include the war's
> transitive dependencies.
> As described on
> http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html it
> is very common in a J2EE environment to use so called skinny wars. Here the
> war's WEB-INF/lib will not contain the dependent jars, but instead they are
> packaged inside the EAR. The war references them through its
> META-INF/MANIFEST.MF
> This option could be used to avoid the 'painful part' mentioned in the above
> web page. The war's dependencies wouldn't have to be duplicated alongside the
> ear's.
> I also found an old issue (MEAR-14) which has asked for the current default
> behavior of not including the transitive dependencies. It suggests a property
> to include specific dependencies of the war. As far as I can tell this has
> never been implemented and this is also not what I am asking for. My proposal
> is an all of nothing kind of option for each war module in the ear.
> On a side note, for me this is the part where removal of the old maven 1
> style properties per dependency is missed the most. With them it was possible
> to decide for each single dependency whether to put it in WEB-INF/lib or
> reference it through the manifest classpath. But of course, then we didn't
> have the transitive dependencies
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
