[Axis2] maven eclipse

[Dennis Sosnoski <dm...@sosnoski.com>]

The maven eclipse target for Axis2 creates basic .project and .classpath 
files, but (at least for me) these don't really do anything useful - 
Eclipse doesn't recognize the source files as things to include in the 
build, and none of the required libraries are included in the generated 
classpath anyway. Is this how it's supposed to work, or is something broken?

The eclipse target for AXIOM appears to work okay, setting up a project 
that finds all the appropriate source files and has the necessary jars 
in the classpath.

  - Dennis

Re: [Axis2] maven eclipse

[Ruchith Fernando <ru...@gmail.com>]

Hi Dennis,

Following steps are from my experience in setting up axis2 with eclipse.

- Get a checkout of Axis2
(https://svn.apache.org/repos/asf/webservices/axis2/trunk/java) into
'axis2' directory in your eclipse workspace. Run the maven build on
this source.

- Start a new Java project in Eclipse and set the project name as
'axis2' and now with the default settings in eclipse it will
automatically pick up the existing project contents (dirs etc).

- Now in the next step (of the new java project wizard) you can select
the source directories that you want to mount. You can browse the
directories and select all 'src' and 'test' directories in each maven
module (axis2/java/modules/*). In the case of teh security module
there's an additional source directory 'interop'

- At the same step you can use the "Libraries" tab to add the jars
that all modules depends on. Note that you will have to add all
dependant jars required by the modules that you added as source.

- There are two places in axis2 where there's code that doesn't
compile. The missing classes are codegen'ed during the maven build.
	- security module - 'interop' source dir - You can collect the
codegen'ed source from
/axis2/java/modules/security/target/interop/work/src or you can
codegen (XmlBeans) them with the ping.wsdl in the
'axis2/java/modules/security/interop' dir and add them to your source
in 'axis2/java/modules/security/interop' (Make sure you don't check in
these classes when committing)
	- integration module - 'test' source dir - You can exclude the
'samples' package from the source path.
	
- That's it!!! now you have successfully set up axis2 in eclipse :-)

If you still get compilation failures:
- Please check whether you have imported all dependant
- Please check whether you have set up the codegen'ed stuff properly.

HTH

Thanks,
Ruchith

On 2/6/06, Ajith Ranabahu <aj...@gmail.com> wrote:
> Hi Dennis,
>  I suppose this is due to the multiproject nature of the axis2 codebase.
> Eclipse has no notion of multiproject (modules) and perhaps the project
> generator gets confused in the presence of multiple modules ?
>  I guess day to day  Eclipse user (like Ruchith ;-)) would be able to give a
> more practical solution
>
>
> On 2/6/06, Dennis Sosnoski < dms@sosnoski.com> wrote:
> > The maven eclipse target for Axis2 creates basic .project and .classpath
> > files, but (at least for me) these don't really do anything useful -
> > Eclipse doesn't recognize the source files as things to include in the
> > build, and none of the required libraries are included in the generated
> > classpath anyway. Is this how it's supposed to work, or is something
> broken?
> >
> > The eclipse target for AXIOM appears to work okay, setting up a project
> > that finds all the appropriate source files and has the necessary jars
> > in the classpath.
> >
> >   - Dennis
> >
>
>
>
> --
> Ajith Ranabahu

Re: [Axis2] maven eclipse

[Ajith Ranabahu <aj...@gmail.com>]

Hi Dennis,
I suppose this is due to the multiproject nature of the axis2 codebase.
Eclipse has no notion of multiproject (modules) and perhaps the project
generator gets confused in the presence of multiple modules ?
I guess day to day  Eclipse user (like Ruchith ;-)) would be able to give a
more practical solution

On 2/6/06, Dennis Sosnoski <dm...@sosnoski.com> wrote:
>
> The maven eclipse target for Axis2 creates basic .project and .classpath
> files, but (at least for me) these don't really do anything useful -
> Eclipse doesn't recognize the source files as things to include in the
> build, and none of the required libraries are included in the generated
> classpath anyway. Is this how it's supposed to work, or is something
> broken?
>
> The eclipse target for AXIOM appears to work okay, setting up a project
> that finds all the appropriate source files and has the necessary jars
> in the classpath.
>
>   - Dennis
>



--
Ajith Ranabahu