On Thu, Feb 5, 2009 at 5:16 PM, Jody Garnett wrote:
> I will wrap up my contribution to this thread with an amusing story ...
> just so you know you are not alone.
>
> When I first started with the GeoTools community they ad 1.5 build
> process; an ant build process which hated me; and a maven 1 b
I will wrap up my contribution to this thread with an amusing story ...
just so you know you are not alone.
When I first started with the GeoTools community they ad 1.5 build
process; an ant build process which hated me; and a maven 1 build which
was supposed to work.
And I was to shy to compl
Sunburned Surveyor a écrit :
> I wonder if Geotools look something like this in the future:
>
> A set of core modules maintained by the community using Maven and other tools.
> A set of modules maintained by individuals or teams that utilize code
> from the core Jars. Each module maintainer would
I'm surprised at all the programmers that hate Maven but see no
alternative. It's sort of like paying $10,000 for one license of
AutoCAD because there is no real alternative. :]
Michael Bedward's post helped me understand some of the issues better.
It sounds like a lot (or at least some) programme
2009/2/5 Martin Desruisseaux wrote:
> Yes, I'm on mac since a few weeks :)
Excellent - welcome to the fold :-)
Michael
--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe
Michael Bedward a écrit :
> 2009/2/5 Martin Desruisseaux wrote:
>> Not only Linux distributions. Maven 2.0.6 is bundled "out of the box" in
>> MacOS 10.5.
>>
>
> Is it ? Are you sure ?
Yes, I'm on mac since a few weeks :) (but still loving Linux and will probably
move between those two worlds)
Andrea Aime a écrit :
> That's just because you're cherry picking the epsg factory you decided
> to use. Really make one big jar with all the epsg factories we have in
> the build and I don't believe it'll be working.
Right... But this is an other thing that I'm fixing.
Martin
-
Jody Garnett a écrit :
> Martin also suggested we could simplify - martin do you have specific
> ideas of complexity that can be stripped out of our maven configuration?
We could try to reduce the amount of profiles as much as we can. For example
the
"ordinary tests" vs "OnlineTest" setting cou
2009/2/5 Martin Desruisseaux wrote:
> Not only Linux distributions. Maven 2.0.6 is bundled "out of the box" in
> MacOS 10.5.
>
Is it ? Are you sure ?
I've got 10.5 but I didn't find maven in /usr/bin or in the Developer
Tools bin dir. Unless I deleted it at some stage and then deleted my
memor
Sunburned Surveyor ha scritto:
> It seems that Maven is tightly integrated into GeoTools. I am
> wondering what benefits this provides to the GeoTools project, and if
> these benefits outweigh the costs.
Just to chime in late and share my opinion, I sincerely love to hate
maven :)
If there was a b
Jody Garnett a écrit :
> To add fuel to a slightly different fire - the maven plugin system is
> magic to the point of being unstable. There is a branch of maven that
> "hard codes" the plugins used so you can get repeatable stable builds
> (justin recommended it).
This is Maven 2.0.9 if I unde
Martin Desruisseaux ha scritto:
> Hello Jody
>
> Jody Garnett a écrit :
>> The reason
>> we cannot have one big jar of geotools (tm) is more to do with the
>> choice of FactorySPI as the plugin system than anything to do with maven.
>
> This is not true. Geotidy build daily one big JAR with eve
A good discussion :).
Landon I hope you haven't been scared off by some of it and I take off
my hat to you for bravely starting such an exciting conversation.
A quick POV from me:
As far as i can tell there are 2 main options out there:
Maven and
Ant + Ivy
Ant is nice in its simplicity and I
Hello Jody
Jody Garnett a écrit :
> The reason
> we cannot have one big jar of geotools (tm) is more to do with the
> choice of FactorySPI as the plugin system than anything to do with maven.
This is not true. Geotidy build daily one big JAR with everything in it since
last summer. With Maven,
2009/2/5 Ben Caradoc-Davies wrote:
>
> Wilde, I think:
> http://www.quotationspage.com/quote/39714.html
>
http://www.youtube.com/watch?v=UxXW6tfl2Y0
Michael
--
Create and Deploy Rich Internet Apps outside the browser wit
Michael Bedward wrote:
> 2009/2/5 Ben Caradoc-Davies wrote:
>> The only thing worse than using Maven is not using Maven.
>
> Was that in homage to Oscar Wilde or Monty Python (or both) ?
Wilde, I think:
http://www.quotationspage.com/quote/39714.html
--
Ben Caradoc-Davies
Software Engineer, CSI
2009/2/5 Sunburned Surveyor wrote:
> I suppose the best solution
> would be for someone like me to become an expert Maven user, so I
> could then be the point person for non-maven contributors to the
> Geotools library. That would solve two (2) problems at once: (1) You
> guys wouldn't have to hear
2009/2/5 Jody Garnett wrote:
> Michael you mentioned a gaps in the docs; can we fill them in?
I meant the maven docs Jody - but I'd be happy to help out with
updating the maven references in the geotools docs
2009/2/5 Ben Caradoc-Davies wrote:
> The only thing worse than using Maven is not using
Sunburned Surveyor wrote:
> It seems that Maven is tightly integrated into GeoTools. I am
> wondering what benefits this provides to the GeoTools project, and if
> these benefits outweigh the costs.
Maven is terrible. It is complex, fragile, and poorly documented.
The only thing worse than using
Yep this is what I like healthy discussion.
Michael you mentioned a gaps in the docs; can we fill them in? I hate
blog-panning for the golden nugget of information.
I would like to strip out the maven 1 references in the developers guide
(as they just add noise by this stage).
Martin also sugge
Hi Landon,
I feel your pain :-)
I confess that I found maven confusing, intimidating and frustrating
when I started using Geotools last year. On top of coming to grips
with Java (new language for me) and Geotools (a mighty wide, deep and
sometimes murky ocean), this maven thing looked like the s
Heh - it is not a battle. As with any open source project is it a
discussion (hopefully in code).
To add fuel to a slightly different fire - the maven plugin system is
magic to the point of being unstable. There is a branch of maven that
"hard codes" the plugins used so you can get repeatable s
My understanding of the value of maven is threefold:
- we have a lot of dependencies and it is a great tool for managing that
(I understand that ant can now use the repository system as well)
- it allows us to isolate the code into little modules; each of which
has a module maintainer (this had v
Adrian,
I was very careful to preface my comments with an acknowledgement that
I wasn't speaking from a position of great expertise or authority. I
think the tone of your response demonstrates a lack of maturity and
professionalism.
Honest and open communication is important in any community. Peo
Hey,
Honestly, you are so far off the mark that it's not worth discussing.
Geotools needs a build tool. You say a Java project doesn't need to have
a build tool and experience says otherwise. Not using a build tool would
be plain idiotic. Any reasonably sized project has a build tool. So look
ar
It looks like I'm loosing this battle. :]
Thank you for giving me the opportunity to present my ideas.
Landon
On Wed, Feb 4, 2009 at 12:56 PM, Martin Desruisseaux
wrote:
> GeoTools 1 was using Ant if my memory serves me right. Ant could has been
> considered an alternative to Maven. But the fac
GeoTools 1 was using Ant if my memory serves me right. Ant could has been
considered an alternative to Maven. But the fact that Maven injects some
standardization (standard directories, standard build phase) was considered a
good point since it brings a bit of uniformity.
But above all, the maj
Adrian wrote: "Maven rocks, it gets the job done, it is vastly easier than any
alternative, and is comparatively a pure joy."
I guess I was looking for something a little more conrete and
specific. "Maven rocks" is an more like a feeling, and I definitely
don't feel that Maven rocks.
Adrian wrote
Hey,
Maven rocks, it gets the job done, it is vastly easier than any
alternative, and is comparatively a pure joy. There is quite simply zero
chance that the use of maven would be changed.
Learning maven is hard because what it is doing is immensely complex not
because maven is hard as far a buil
Hello Landon
Maven is difficult and unfortunatly not bug free. But I'm not aware of much
alternative... The goal was to allow developper to just invoke "mvn install"
from the root and get everything built, including dependencies.
Part of current difficulties is that our Maven configuration got
I'm sure I'm about to throw open the lid to Pandora's Box. Before I
start asking my questions and presenting my ideas let me say that this
message is meant to be helpful and not critical. I proceed with the
realization that I may have no idea what I am talking about. So,
casting the fear of making
31 matches
Mail list logo
