You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Srinath Perera (JIRA)" <de...@geronimo.apache.org> on 2004/12/15 05:13:04 UTC
[jira] Resolved: (GERONIMO-490) Axis creates config store in trunk root
[ http://nagoya.apache.org/jira/browse/GERONIMO-490?page=history ]
Srinath Perera resolved GERONIMO-490:
-------------------------------------
Resolution: Fixed
EWS and the axis-geronimo module is updated to not creating anyhting in the target directory. Please cross check
> Axis creates config store in trunk root
> ---------------------------------------
>
> Key: GERONIMO-490
> URL: http://nagoya.apache.org/jira/browse/GERONIMO-490
> Project: Apache Geronimo
> Type: Bug
> Components: webservices
> Reporter: Alan Cabrera
> Assignee: Srianth Perera
>
> Axis creates config store in trunk root, i.e. trunk/target.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
Re: Axis build question
Posted by Srinath Perera <he...@gmail.com>.
Hi Hari;
EWS build.xml generation is first writen without the knowladge about
geronimo axis module and when it try to acomadate later and get the
build working things get messy (there is a problem of finding the
maven repository in all the machines)
I will have a look at the both build to improve the things and get
back .. there must be a way to make the things more simple!
Thanks
Srinath
On Tue, 14 Dec 2004 22:20:45 -0800, Hari Kodungallur
<hk...@spikesource.com> wrote:
> I have a build related question (in axis module) that could be related
> to this JIRA entry.
>
> The EWS code generation currently assumes that the directory structure
> for axis looks like geronimo/modules/axis. Geronimo build runs into
> problems if I either rename geronimo to, say, trunk (i.e.,
> trunk/modules/axis), or if I do not start the build at the geronimo
> level (say I have mywork/geronimo/... and I have another build file at
> mywork level and I call geronimo build from mywork).
> Actually the code generation is okay, but the test:test of axis fails
> when it tries to build the generated files. (Because the generated
> build.xml file does not have the correct class path to the geronimo-axis
> classes)
>
> The classpath for the generated build.xml in this case looks like
>
> <path id="classpath" >
> <pathelement location="{basedir}/target/classes"/>
> <pathelement location="{basedir}/target/test-classes"/>
> <pathelement
> location="{basedir}/modules/axis/target/samples/echo.jar"/>
> <fileset dir="${maven.repo.local}">
> .... (snip)
> </fileset>
> </path>
>
> whereas the geronimo-axis classes are in
> {basedir}/modules/axis/target/classes.
>
> I am curious whether there is there any reason why the first pathelement
> is dependent on the location of ws4j2ee.properties file? Can the Build
> File Generation file just put the {basedir}/modules/axis/target/classes
> irrespective of where the config file is found?
>
> Thanks much!
> -Hari
>
> On Tue, 2004-12-14 at 20:13, Srinath Perera (JIRA) wrote:
> > [ http://nagoya.apache.org/jira/browse/GERONIMO-490?page=history ]
> >
> > Srinath Perera resolved GERONIMO-490:
> > -------------------------------------
> >
> > Resolution: Fixed
> >
> > EWS and the axis-geronimo module is updated to not creating anyhting in the target directory. Please cross check
> >
> > > Axis creates config store in trunk root
> > > ---------------------------------------
> > >
> > > Key: GERONIMO-490
> > > URL: http://nagoya.apache.org/jira/browse/GERONIMO-490
> > > Project: Apache Geronimo
> > > Type: Bug
> > > Components: webservices
> > > Reporter: Alan Cabrera
> > > Assignee: Srianth Perera
> >
> > >
> > > Axis creates config store in trunk root, i.e. trunk/target.
>
>
Axis build question
Posted by Hari Kodungallur <hk...@spikesource.com>.
I have a build related question (in axis module) that could be related
to this JIRA entry.
The EWS code generation currently assumes that the directory structure
for axis looks like geronimo/modules/axis. Geronimo build runs into
problems if I either rename geronimo to, say, trunk (i.e.,
trunk/modules/axis), or if I do not start the build at the geronimo
level (say I have mywork/geronimo/... and I have another build file at
mywork level and I call geronimo build from mywork).
Actually the code generation is okay, but the test:test of axis fails
when it tries to build the generated files. (Because the generated
build.xml file does not have the correct class path to the geronimo-axis
classes)
The classpath for the generated build.xml in this case looks like
<path id="classpath" >
<pathelement location="{basedir}/target/classes"/>
<pathelement location="{basedir}/target/test-classes"/>
<pathelement
location="{basedir}/modules/axis/target/samples/echo.jar"/>
<fileset dir="${maven.repo.local}">
.... (snip)
</fileset>
</path>
whereas the geronimo-axis classes are in
{basedir}/modules/axis/target/classes.
I am curious whether there is there any reason why the first pathelement
is dependent on the location of ws4j2ee.properties file? Can the Build
File Generation file just put the {basedir}/modules/axis/target/classes
irrespective of where the config file is found?
Thanks much!
-Hari
On Tue, 2004-12-14 at 20:13, Srinath Perera (JIRA) wrote:
> [ http://nagoya.apache.org/jira/browse/GERONIMO-490?page=history ]
>
> Srinath Perera resolved GERONIMO-490:
> -------------------------------------
>
> Resolution: Fixed
>
> EWS and the axis-geronimo module is updated to not creating anyhting in the target directory. Please cross check
>
> > Axis creates config store in trunk root
> > ---------------------------------------
> >
> > Key: GERONIMO-490
> > URL: http://nagoya.apache.org/jira/browse/GERONIMO-490
> > Project: Apache Geronimo
> > Type: Bug
> > Components: webservices
> > Reporter: Alan Cabrera
> > Assignee: Srianth Perera
>
> >
> > Axis creates config store in trunk root, i.e. trunk/target.