You are viewing a plain text version of this content. The canonical link for it is here.
Posted to savan-dev@ws.apache.org by "Leon S. Searl (JIRA)" <ji...@apache.org> on 2008/02/20 18:13:43 UTC
[jira] Updated: (SAVAN-4) savan-XXXX.mar unable to find
savan-config.xml resource
[ https://issues.apache.org/jira/browse/SAVAN-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leon S. Searl updated SAVAN-4:
------------------------------
Attachment: savan-SVN-20080104_mod.patch
This patch moves the SavanModule.java from the core
over to the mar module since it is not needed
in the core. The patch also moves the savan-config.xml
over to the mar module.
This is how I fixed the problem of the savan-config.xml
from showing up in the savan-XXX.jar file when
two builds in a row without a clean in between them.
This means that if
there is ever a unit test added to test reading in the
savan-config.xml that it may have to be in the mar
instead of where the code is in the core unless the
class is separated into a one that reads the config
(in the mar) and one that holds the config (in the core).
> savan-XXXX.mar unable to find savan-config.xml resource
> -------------------------------------------------------
>
> Key: SAVAN-4
> URL: https://issues.apache.org/jira/browse/SAVAN-4
> Project: Savan
> Issue Type: Bug
> Environment: axis2 v1.3
> SVN snapshot of 20080104
> Reporter: Leon S. Searl
> Attachments: savan-SVN-20080104_mod.patch
>
>
> With a clean build
> > mvn clean install
> The savan module, when invoking the module 'init', was not finding
> the savan-config.xml in the mar resource since it is not
> using the module class loader.
> If two builds were done in a row:
> > mvn clean install; mvn install
> because of a bug in the mavan pom file, the
> savan-config.xml would be put into the
> savan.jar file also. In this case the module 'init' would
> find the savan-config.xml file.
> I'll try to attach two patch files that will fix this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.