How about we put it in the woden-tools jar for now and revisit this issue if it is a problem later? We can also create a custom build step to publish the WSDL viewer as a separate file alongside the jars.
Lawrence From: "John Kaputin (gmail)" <[EMAIL PROTECTED]> To: woden-dev@ws.apache.org Date: 07/07/2008 09:55 AM Subject: Re: Refactoring status Jeff, I'm not sure what to do with the wsdl viewer. It is a stand alone xsl tool, not a resource used by a woden java tool, so perhaps making it a subdirectory of resource within the woden-tool jar is not the right thing. Do any of the other woden devs have any thoughts on where to place wsdl viewer in the new maven source structure and build tree? John. On Fri, Jul 4, 2008 at 12:29 AM, Jeff MAURY <[EMAIL PROTECTED]> wrote: John, Yes, I started the refactoring based on option 3. I'm almost finished, I just need to check the Ant build. Regarding the wsdlprinter, my intent is to put it into woden-tool, but don't know exactly how to do: if I put it as a resource, it will be in the woden-tool JAR, do you think this is ok ? Regards Jeff MAURY On Thu, Jul 3, 2008 at 4:20 PM, John Kaputin (gmail) <[EMAIL PROTECTED]> wrote: Jeff, I think option 3 seems best too, although my knowledge of Maven is still a bit limited. I assume you will also refactor the converter and wsdl printer into woden-tools? thanks, John. On Fri, Jun 27, 2008 at 3:30 AM, Lawrence Mandel <[EMAIL PROTECTED]> wrote: Jeff, I'm in favour of following conventions where possible. I'd also go with option 3. Lawrence "Jeff MAURY" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 06/26/2008 06:13 AM Please respond to woden-dev@ws.apache.org To woden-dev@ws.apache.org cc Subject Refactoring status Hello, just to report what I have done and what is left. I have refactored woden-api, woden-om, woden-dom and created woden-ant and woden-commons. As of yet, I have just refactored the source and not the tests. I have a little problem with the tests and need your opinion. Maven convention about test is to store the test with the Maven project. However, in our case, most of the tests are shared between woden-om and woden-dom. So the solutions presented to use are the following: 1) create a separate test folder under trunk and update woden-om and woden-dom to use this folder (like it is done today). Pros: easy to implement. Cons: does not follow Maven conventions 2) create a separate test Maven project with two profiles (om and dom) to manage the dependency for the execution. Pros: follow Maven conventions. Cons: needs to run Maven twice 3) create a separate test Maven project without profiles that will launch Maven twice (thanks to the maven-invoker-plugin http://maven.apache.org/plugins/maven-invoker-plugin) one for OM and one for DOM. Pros: follow Maven conventions. Cons: needs 3 POMs Please let me know what is your preferred choice, mine is the third. Jeff MAURY -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.lastfm.fr/listen/user/jeffmaury/personal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.lastfm.fr/listen/user/jeffmaury/personal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
