As far as getting your two jars built, if you think that your opt jars are going to have a ton of odd/different dependencies, then using a single maven project and two subprojects works well. The sub projects share any common project elements from the top project, but function as two existing seperate projects.
Thanks, Eric. That sounds like a good approach. I am still not sure exactly where the boundaries are going to be, but right now it looks like initially we will have the parent core and one or more fully dependent children. Any ideas that you have on the simplest way to set this up (without resorting to piles of jellyscript) would be much appreciated. Thanks in advance.
Phil
-----Original Message----- From: Phil Steitz [mailto:[EMAIL PROTECTED] Sent: Sunday, August 24, 2003 2:03 AM To: Jakarta Commons Developers List Subject: [naming] Getting started...
Anyone have any objections to my adding myself to STATUS and starting on the following:
1. fix a couple of package declarations to make the build work
2. find a way to get both "core" and "opt" jars generated. My current thinking is that core will include everything but the factory implementations. Feedback on this appreciated.
3. get cracking on some unit tests for the core elements
4. encapsulate the tomcat server.xml JDNI resource configuration stuff to add support for xml configuration files
Thoughts?
Phil
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
