+1 but again, I'd like to wait until after the interop event next week. I really don't want to mess with any part of our infrastructure in a way that may cause problems to those that will need to work on Woden while at this event. How about we target next weekend (July 8-9) to make this change?

BTW, our intention in creating /java was that someone may want to contribute a /c. (That's a C/C++ version of Woden not air conditioning - a/c - for the project. :) ) Moving to /trunk/java seems like the correct action for consistency with the way in which SVN is used.

Lawrence




"Jeremy Hughes" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]

06/29/2006 02:56 PM

Please respond to
[email protected]

To
[email protected]
cc
Subject
Re: Woden Build System





I think we should move /java to /trunk/java - axis2/c has a woden/c
module and perhaps they might like to move that to woden one day.

There's a 'but' when we move, all working copies will become invalid.
It's simple to fix - do an svn switch.

I'm +1 to do this sooner rather later.

Cheers,
Jeremy

On 6/25/06, John Kaputin <[EMAIL PROTECTED]> wrote:
> Eran,
>
> I'm +1 to Lawrence's comments and suggestions.
>
> I'm fine about changing source from /java folder to /trunk and moving test
> files to a /test-resources folder and being able to use Maven or Ant to
> build the project. My current focus is some fixes and function for the
> Interop event, but I'm happy for you to contribute a Maven build process
> that doesn't affect the Ant build.  I have not yet tried Maven but would
> like to, so this could be a useful learning opportunity for me.
>
> thanks,
> John Kaputin

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


Reply via email to