From: Imran M Yousuf <hidden> Date: 2016-06-15 22:44:40
Hi,
I have successfully Mavenized JGit (at least partially :)) to make it
independent of IDE to develop on. I will also add a code-file format
checker soon. Please have a look at it and let me know what you think
and how it can be improved. If its helpful I will surely send out a
patch in this regard. The one thing that I did not configure is the
external test (exttst), doing that and the code format checker is my
next step.
The 'jgit-mavenize' branch of my fork of egit contains it.
(http://repo.or.cz/w/egit/imyousuf.git?a=shortlog;h=refs/heads/jgit-mavenize).
Best regards,
--
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
From: Robin Rosenberg <hidden> Date: 2016-06-15 22:44:40
tisdagen den 3 juni 2008 16.42.33 skrev Imran M Yousuf:
Hi,
I have successfully Mavenized JGit (at least partially :)) to make it
independent of IDE to develop on. I will also add a code-file format
checker soon. Please have a look at it and let me know what you think
and how it can be improved. If its helpful I will surely send out a
patch in this regard. The one thing that I did not configure is the
external test (exttst), doing that and the code format checker is my
next step.
The 'jgit-mavenize' branch of my fork of egit contains it.
(http://repo.or.cz/w/egit/imyousuf.git?a=shortlog;h=refs/heads/jgit-mavenize).
An abvious problem is that JGit does not handle symbolic links and those do
not work well (if at all) under git on windows either. Cygwin will not do here,
unless you accompany it with a cygwin java build (if such a thing exists). Mingw
also does not support them.
-- robin
From: Shawn O. Pearce <hidden> Date: 2016-06-15 22:44:41
Robin Rosenberg [off-list ref] wrote:
tisdagen den 3 juni 2008 16.42.33 skrev Imran M Yousuf:
quoted
I have successfully Mavenized JGit (at least partially :)) to make it
independent of IDE to develop on. I will also add a code-file format
checker soon. Please have a look at it and let me know what you think
and how it can be improved. If its helpful I will surely send out a
patch in this regard. The one thing that I did not configure is the
external test (exttst), doing that and the code format checker is my
next step.
The 'jgit-mavenize' branch of my fork of egit contains it.
(http://repo.or.cz/w/egit/imyousuf.git?a=shortlog;h=refs/heads/jgit-mavenize).
An abvious problem is that JGit does not handle symbolic links and those do
not work well (if at all) under git on windows either. Cygwin will not do here,
unless you accompany it with a cygwin java build (if such a thing exists). Mingw
also does not support them.
I'm all for a change that widens the group of applications and
users that can use jgit (heck, that's one reason we moved to it to
a BSD license). But we really cannot abandon Windows users in that
process, so yea, anything that tries to use symlinks is bad.
I don't think there is a Cygwin based version of the JVM. That would
be a very interesting beast.
--
Shawn.
From: Imran M Yousuf <hidden> Date: 2016-06-15 22:44:41
The first version I mavenized JGit I moved the source code, but I
thought that would come in for more criticism :), thus I chose the
symlink option. Please let me know if a move based mavenizing would be
welcomed or not.
Best regards,
Imran
On Wed, Jun 4, 2008 at 5:30 AM, Robin Rosenberg
[off-list ref] wrote:
onsdagen den 4 juni 2008 00.54.18 skrev Shawn O. Pearce:
quoted
I don't think there is a Cygwin based version of the JVM. That would
be a very interesting beast.
From: Shawn O. Pearce <hidden> Date: 2016-06-15 22:44:41
Imran M Yousuf [off-list ref] wrote:
The first version I mavenized JGit I moved the source code, but I
thought that would come in for more criticism :), thus I chose the
symlink option. Please let me know if a move based mavenizing would be
welcomed or not.
[please don't top-post on this list]
I'd rather us moving the code into a subdirectory than require
a symlink. For Eclipse this is easy to change the directory that
the code is in, we just have to edit the .classpath to move the
source folder lower in the tree.
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.
For the most part git-merge-recursive can handle a merge through
this sort of rename. But we'd like to do this sort of thing at
some relatively stable point in time to try and minimize the impact
it has.
On Wed, Jun 4, 2008 at 5:30 AM, Robin Rosenberg
[off-list ref] wrote:
quoted
onsdagen den 4 juni 2008 00.54.18 skrev Shawn O. Pearce:
quoted
I don't think there is a Cygwin based version of the JVM. That would
be a very interesting beast.
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.
From: Imran M Yousuf <hidden> Date: 2016-06-15 22:44:41
On Wed, Jun 4, 2008 at 10:27 AM, Shawn O. Pearce [off-list ref] wrote:
Imran M Yousuf [off-list ref] wrote:
quoted
The first version I mavenized JGit I moved the source code, but I
...
welcomed or not.
[please don't top-post on this list]
Sorry, but I thought that I was proposing something new and thus top-posted :)
I'd rather us moving the code into a subdirectory than require
a symlink. For Eclipse this is easy to change the directory that
the code is in, we just have to edit the .classpath to move the
source folder lower in the tree.
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.
I am sorry for my ignorance, I thought that maven was the most widely
accepted java build tool, but what you said is a possibility.
For the most part git-merge-recursive can handle a merge through
this sort of rename. But we'd like to do this sort of thing at
some relatively stable point in time to try and minimize the impact
it has.
When I was working with the moved source code git detected the renames
and propagated the changes, but I had to scrape it because of my
stupidity my mavenized jgit was in jgit folder that clashed with the
jgit shell script :). I would say once the move is done it would be
safe to continue.
--
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
From: Imran M Yousuf <hidden> Date: 2016-06-15 22:44:41
On Wed, Jun 4, 2008 at 12:40 PM, Nigel Magnay [off-list ref] wrote:
quoted
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>.
--
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
From: Shawn O. Pearce <hidden> Date: 2016-06-15 22:44:41
Imran M Yousuf [off-list ref] wrote:
On Wed, Jun 4, 2008 at 12:40 PM, Nigel Magnay [off-list ref] wrote:
quoted
quoted
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.
--
Shawn.
From: Imran M Yousuf <hidden> Date: 2016-06-15 22:44:41
On Thu, Jun 5, 2008 at 1:59 AM, Shawn O. Pearce [off-list ref] wrote:
Imran M Yousuf [off-list ref] wrote:
quoted
On Wed, Jun 4, 2008 at 12:40 PM, Nigel Magnay [off-list ref] wrote:
quoted
quoted
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.
Will give it a try and let all know.
Best regards,
Imran
--
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
I am sorry for my ignorance, I thought that maven was the most widely
accepted java build tool, but what you said is a possibility.
For what it's worth, Ant is the most popular build tool. Ant + Ivy (a
dependency manager) is a great choice. My Next Best Thing (TM) is Gradle
(www.gradle.org). I wouldn't choose Maven because it makes creating
custom logic harder and some functionality (like assembly) is no mature.
I can elaborate on the subject, if people are interested.
Ittay
--
Ittay Dror [off-list ref]
Tikal <http://www.tikalk.com>
Tikal Project <http://tikal.sourceforge.net>
From: Imran M Yousuf <hidden> Date: 2016-06-15 22:44:41
On Thu, Jun 5, 2008 at 9:23 AM, Ittay Dror [off-list ref] wrote:
Imran M Yousuf wrote:
quoted
I am sorry for my ignorance, I thought that maven was the most widely
accepted java build tool, but what you said is a possibility.
For what it's worth, Ant is the most popular build tool. Ant + Ivy (a
dependency manager) is a great choice. My Next Best Thing (TM) is Gradle
(www.gradle.org). I wouldn't choose Maven because it makes creating custom
logic harder and some functionality (like assembly) is no mature. I can
elaborate on the subject, if people are interested.
Ah, thanks for shedding some light on it.
Best regards,
Imran
From: Imran M Yousuf <hidden> Date: 2016-06-15 22:44:41
On Thu, Jun 5, 2008 at 1:59 AM, Shawn O. Pearce [off-list ref] wrote:
Imran M Yousuf [off-list ref] wrote:
quoted
On Wed, Jun 4, 2008 at 12:40 PM, Nigel Magnay [off-list ref] wrote:
quoted
quoted
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.
From: Imran M Yousuf <hidden> Date: 2016-06-15 22:44:41
On Thu, Jun 5, 2008 at 9:23 AM, Ittay Dror [off-list ref] wrote:
For what it's worth, Ant is the most popular build tool. Ant + Ivy (a
dependency manager) is a great choice. My Next Best Thing (TM) is Gradle
(www.gradle.org). I wouldn't choose Maven because it makes creating custom
logic harder and some functionality (like assembly) is no mature. I can
elaborate on the subject, if people are interested.
I have heard of Ant + Ivy but never got the chance to use it. And what
I do for the messy-maven stuffs is I use Ant from maven. But there are
few features of maven (which IMHO is not the discussion topic of this
list) I like. Will checkout Gradle as well.
Thanks for the hints :).
Best regards,
Imran
From: Robin Rosenberg <hidden> Date: 2016-06-15 22:44:42
fredagen den 6 juni 2008 07.28.59 skrev Imran M Yousuf:
I have just tested it and it works fine. Now maven is configured to
use the existing locations for source and it builds fine.
I squashed the two commits involving pom.xml into a new branchy and it works here to.
Still you have a duplicate of the test directory. Can that be fixed too?
-- robin
From: Imran M Yousuf <hidden> Date: 2016-06-15 22:44:42
On Fri, Jun 6, 2008 at 5:59 PM, Robin Rosenberg
[off-list ref] wrote:
Still you have a duplicate of the test directory. Can that be fixed too?
Actually I will give it a try checking what happens if the files are
in maven test resources, will give it a try this weekend and update
you all.
Best regards,
Imran
-- robin
--
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