git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Imran M Yousuf" <imyousuf@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Nigel Magnay" <nigel.magnay@gmail.com>,
	"Robin Rosenberg" <robin.rosenberg.lists@dewire.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [JGIT RFC] Mavenized JGit
Date: Fri, 6 Jun 2008 11:28:59 +0600	[thread overview]
Message-ID: <7bfdc29a0806052228s2fe764d1pe5d2b8e129115c77@mail.gmail.com> (raw)
In-Reply-To: <20080604195934.GU12896@spearce.org>

On Thu, Jun 5, 2008 at 1:59 AM, Shawn O. Pearce <spearce@spearce.org> wrote:
> Imran M Yousuf <imyousuf@gmail.com> wrote:
>> On Wed, Jun 4, 2008 at 12:40 PM, Nigel Magnay <nigel.magnay@gmail.com> wrote:
>> >>
>> >> But this shows one reason why I don't use Maven I think.  The
>> >> fact that we need a "java" directory to hold our java code.
>> >> What if another build system wants a different name?  Grumble.
>> >>
>> >
>> > You don't. Just set the appropriate config item in pom.xml
>> > (sourceDirectory possibly, but my memory isn't good this morning) and
>> > you can use 'src' as it is currently. src/main/java is just the
>> > default.
>>
>> You are absolutely right in fact (your memory did not betray ;)) its
>> <project><build><sourceDirectory>.
>
> If we can avoid doing this rename and instead just configure Maven
> to use the existing directory it would be better.  Then we don't
> have to bother everyone's branches with this rename business.

I have just tested it and it works fine. Now maven is configured to
use the existing locations for source and it builds fine.

Best regards,

Imran

PS: This is the link to the commit
http://repo.or.cz/w/egit/imyousuf.git?a=commit;h=7c69b95cee245edd0701e09d5f0357f7ffbbd9ea
>
> --
> Shawn.
>



-- 
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: imran@smartitengineering.com
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557

  parent reply	other threads:[~2008-06-06  5:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 14:42 [JGIT RFC] Mavenized JGit Imran M Yousuf
2008-06-03 16:56 ` Robin Rosenberg
2008-06-03 22:54   ` Shawn O. Pearce
2008-06-03 23:30     ` Robin Rosenberg
2008-06-04  3:52       ` Imran M Yousuf
2008-06-04  4:27         ` Shawn O. Pearce
2008-06-04  6:40           ` Nigel Magnay
2008-06-04  6:46             ` Imran M Yousuf
2008-06-04 19:59               ` Shawn O. Pearce
2008-06-05  2:31                 ` Imran M Yousuf
2008-06-06  5:28                 ` Imran M Yousuf [this message]
2008-06-06 11:59                   ` Robin Rosenberg
2008-06-06 12:40                     ` Imran M Yousuf
2008-06-04  6:45           ` Imran M Yousuf
2008-06-05  3:23             ` Ittay Dror
2008-06-05  3:33               ` Imran M Yousuf
2008-06-06  5:31               ` Imran M Yousuf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7bfdc29a0806052228s2fe764d1pe5d2b8e129115c77@mail.gmail.com \
    --to=imyousuf@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=nigel.magnay@gmail.com \
    --cc=robin.rosenberg.lists@dewire.com \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).