Ok. I was thinking that two poms would make sense, since there are
two build artifacts. But they could still live in the same repo if
On Mar 14, 1:24 pm, Arthur Blake <
arthur.bl...@gmail.com> wrote:
> A lot of people have requested Maven support and one guy even
> submitted a Maven patch a long time ago.
>
> I'm not much of a Maven user. Every time I try to use it, it seems
> like I run into little nit-picky issues.
> I'm just an old-timey ant user.
>
> I do want to mavenize the project though so people can easily pull it
> in with just a pom.xml entry, one particular problem is that I have
> two build artifacts and two independent versions of the source tree.
>
> I was thinking about making them separate maven projects.
>
> I will probably be changing the package name (from net.sf.log4jdbc to
> org.log4jdbc) before completing the maven work (because it's no longer
> a sourceforge project) before submitting to all the maven repos.
>
> Also thinking about changing from SVN to git.
>