Rishi Verma created OODT-507:
--------------------------------
Summary: maven-cas-install-plugin should remove legacy jars from
component's lib directory, if customLibs are specified
Key: OODT-507
URL: https://issues.apache.org/jira/browse/OODT-507
Project: OODT
Issue Type: Improvement
Components: cas-mvn-plugins
Affects Versions: 0.4
Reporter: Rishi Verma
Assignee: Rishi Verma
Priority: Minor
Fix For: 0.5
I think the maven-cas-install-plugin could help solve a deployment related
issue: when upgraded versions of JAR files that are specified within the
'customLibs' parameter within the plugin configuration block of a given pom,
legacy versions of the same JAR files already existing within a deployment
directory (ie. filemgr/lib) can potentially conflict with these upgraded JARs
if they are not first removed. This has, in the past, caused runtime errors
that are difficult to trace.
Although this is really more of a deployment issue that can be remedied if the
individual performing the deployment is cognizant of existing legacy JARs, I
think baking some intelligence into the cas-install plugin could ensure this
problem never arises. To accomplish this, we could implement the following
solution:
* Within CASInstallDistMojo.execute [1], we ensure that the contents of a
deployment component's 'libs' directory is removed prior to
un-tarring/deployment if and only if the 'customLibs' element within the plugin
configuration is specified and contains values. This would follow the model
already implemented within CASInstallDistMojo.execute of removing the default
policy files and configuration if custom versions of these files are specified
in the plugin configuration.
--
[1]
http://svn.apache.org/repos/asf/oodt/tags/0.4/mvn/plugins/cas-install/src/main/java/org/apache/oodt/cas/install/CASInstallDistMojo.java
--
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
