I just tried to build the xo component and it failed. So even the components with an existing maven.xml will need to be updated.
PS: my point with xmlunit was about the naming conflict
-- Dirk
Inger, Matthew wrote:
I know the sourceforge project is active. I'm willing to help out with whatever i can, though I'm new to the commons project, i have submitted stuff for ANT, and i own the ANT-CONTRIB project on sourceforge.
-----Original Message----- From: Dirk Verbeeck [mailto:[EMAIL PROTECTED] Sent: Thursday, November 13, 2003 5:28 PM To: Jakarta Commons Developers List Subject: Re: Web Presence for ALL Jakarta Commons components
I'm also willing to help a hand mavenizing the commons (sandbox) components.
What do you guys think about the maven setup of DBCP as example (menu layout/content)?
Shouldn't we cleanup the sandbox a bit first? (tar & rm) The following components are graduated out the sandbox: betwixt cli codec daemon dbutils digester discovery el fileupload jelly jexl lang latka launcher logging math modeler primitives
These components/directories can also be removed IMHO: amend empty cjan empty graph empty latka-webapp empty morphos empty pattern empty cadastre empty old avalon comp cvs empty dir periodicity_1 empty dir jdbc2pool moved into dbcp util move into lang & collections bzip2 moved into IO altrmi moved to incubator jux no real code armi old altrmi project http old httpclient jpath old jxpath joran only proposal 13 months old
The component template in the "proposal" directory should also be updated.
One last remark, there is a xmlunit component and there is also a
sourceforge project with the same name:
http://sourceforge.net/projects/xmlunit/
-- Dirk
--------------------------------------------------------------------- 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]
