Maven?

92 views
Skip to first unread message

mmichalek

unread,
Mar 14, 2009, 1:18:06 PM3/14/09
to log4jdbc
Arthur, are you currently working on mavenizing log4jdbc? Are you
aware of any specific challenges with that?

If you haven't gotten to this yet, I might be able to take a swing at
converting this to a maven project.

Thanks again for a great little project.

Arthur Blake

unread,
Mar 14, 2009, 1:24:50 PM3/14/09
to log4...@googlegroups.com
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.

mmichalek

unread,
Mar 15, 2009, 12:24:23 PM3/15/09
to log4jdbc
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
that makes things easier.

Unrelated, but what led you to move away from sourceforge?

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.
>

Arthur Blake

unread,
Mar 15, 2009, 12:49:27 PM3/15/09
to log4...@googlegroups.com
On Sun, Mar 15, 2009 at 12:24 PM, mmichalek <mark.m....@gmail.com> wrote:
> Unrelated, but what led you to move away from sourceforge?

I used google code on another project, and found that the tools are
better laid out and much easier to use, the interface is cleaner and
the site (ironically) doesn't have ads plastered all over it. Some
things are more powerful in sourceforge for sure, but all that just
gets in the way for a small project like this.

Reply all
Reply to author
Forward
0 new messages