+1 on moving the axis stuff into it's own module, and +1 for using maven2 exclusively. We can drop the lib directory, if we do that :) Would Rampart what to adopt the axis code? If not, we can maintain it here.

I'm less inclined to create a separate tests module, as most of the core functionality should be unit-testable in each maven module (src/ main/java/... and src/test/java/...), but let me know if I'm missing something technically about that. For "system" level testing, if there is such a thing in WSS4J, maybe a separate module is called for. But I'm not sure I see a need for that.

Not sure about the need for a modules super-directory, unless we have artifacts like specs and such, which are basically non-source material, but more referency things. Whatever the going conventions are, for this sort of thing at apache, is fine.

I also think we may want a parent module, which just contains a parent POM, which all WSS4J modules can inherit from. Good place to put version dependencies in one place. CXF does this to good effect.

-Fred

On Apr 18, 2008, at 10:50 AM, O hEigeartaigh, Colm wrote:

Hi Nandana,

+1 to this, although definitely after the 1.5.4 release. Should we drop
support for ant altogether? I'd be in favour of this, although others
might object.

In addition, I propose moving the org.apache.ws.axis namespace into a
separate module. In this way, other applications could use the
wss4j-core without having an implicit dependency on Axis. In general,
the core code should have as little dependencies on third party code as
possible, e.g. http://issues.apache.org/jira/browse/WSS-75.

Thanks,

Colm.


-----Original Message-----
From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED]
Sent: 18 April 2008 15:23
To: wss4j-dev
Subject: Converting wss4j into a multi module project

Hi Devs,
       As a first step of moving the build in to maven, I propose to
make WSS4J a multi module maven project.

wss4j/
      modules/
               wss4j-core (wss4j-handlers/wss4j-*)
               wss4j-tests
               distribution
               documentation

we can integrate the tests in to maven build. Looking at the pom.xml ,
we can see some efforts has been  taken do this, so we will be able to
continue from there. But I think we should start this after the 1.5.4
release.

Fred, WDYT ?

thanks,
/nandana

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to