Hi Guys!
you are right that the package structure is probably not the best possible. At least, it is consistent with the WS-AT parts ;-)

If you don't mind, I'd send you the complete kandula.ba package in one ZIP instead of splitting it. Even though I verified that every splitted part compiles cleanly the packaging into patches seems to be a fragile process :-/

The refactoring of the package structure has influence on the already checked in parts - config and documentation - so if we modify it now, we need to patch also these things.
I think it's the better idea to first commit our patches and afterwards refactor the code, since this is only little work using modern development tools. Moreover I don't even know if it is possible to create a patch-file that moves and changes files at the same time
I guess it would be best to first define what the final package structure should be, and then refactor the classes (AT and BA) to actually go in there. If it shall be

org.apache.kandula.[at,ba,coordination].[coord,part,initiator,schema]

or the other way round is a decision that needs to be discussed and made, but does not impact the source code changes that much.

I'd also propose that we put the autogenerated files in separate packages.
Isn't the proposed schema package (org.apache.kandula.[at,ba,coordination].schema a good place to put the autogenerated files? Or what was the intention of this proposal?
Anyways, if we change the package structure, it should be done at the same time with AT and BA classes. If that is OK with you, we ask you to commit the current package structure and then start refactoring.
I share hannes' opinion on this one. I think it would be better as mentioned before to first finish commiting our patches and then change the package structure in general.
Would the JIRA be a suitable place for patches? As soon as they are committed they become worthless, so personal email is probably also a good solution.
In my opinion personal mail is fairly enough.

regards,
Georg

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

Reply via email to