>
> MAVEN REPOSITORY AS ONLY SOURCE OF DEPENDENCIES
I don't see the big issue here , as others have pointed out you can solve
this with a system scope.
On the other hand, setting up your own repository is actually very simple
and gives a lot of advantages (like proper version tracking of the
depe
I've been stewing on this for a bit and while I think some of these
things are a "didn't know better/didn't know about that option", there
are some valid complaints in here.
ORDER OF TASKS
There are plenty of plugins - both available via repo1 and internally
developed here that would be much bett
On Nov 19, 2008, at 1:44 PM, Martin von Gagern wrote:
I would much prefer some kind of lib directory, where I
could simply drop the library and start using it, to see if it is fit
for the job I want to use it for in the first place.
You can accomplish that by specifying the dependency with a "
>> Regarding "writing your own build tool" -- I think this is probably a
>> bad idea, but of course, you are welcome to disagree. If you have
>> decided to abandon Maven, perhaps take a look at "buildr" and other
>> tools (you already mentioned ivy) that have taken ideas from Maven and
>> incorpora
Wayne Fay wrote:
> We see "rants" like this every few months from someone. And the fact
> that this is your 4th email to this group suggests that you have
> generally been "going it alone" rather than leaning on this group as
> needed for help. (Note: this is not an open call for n00bs to blast
> t
Michael McCallum wrote:
> You have put a lot of effort into this email and its really important to
> spread the ideas around,
> could you put these issues into jira with suggested solutions? To give more
> visiblity.
I might, for some of them, if I find the time. I guess some of my ideas
concern
You have put a lot of effort into this email and its really important to spread
the ideas around,
could you put these issues into jira with suggested solutions? To give more
visiblity.
cheers
--
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]
Wayne Fay wrote:
Regarding "writing your own build tool" -- I think this is probably a
bad idea, but of course, you are welcome to disagree.
There is a contingent at my office that believes they should write their
own build system. They manage a HUGE project using a directory full of
Ant scr
> I guess many of the issues I don't like about maven could be helped with
> more knowledge about Maven, customized plugins, hackish workarounds, or
> any other kind of additional work. It's the sum of all together and the
> amount of work required which lead me away from Maven. I list these
> issu
Just my pesonnal conviction :
Maven is not the golden bullet tool. It has many issues (some you describe),
and can't cover all requirements.
Many project choosed some complex building (like the sign / assembly process
you describe) that does not match maven conventions.
Maven is a toll for project
Martin von Gagern wrote:
On the whole, I spent way too much time tweaking Maven, time I'd rather
spend working on my project code.
One of the most fundamental things about maven that you need to do to
have a pleasant user experience, is to submit to maven.
In other words, you shouldn't spen
Hi everybody!
I've been using Maven 2 for a few projects now, and found that, although
it provides some nice features, it doesn't seem to be the right tool for
most of my applications. I'll write down some of my experiences here, so
that they might help improving development tools in general.
I'm
12 matches
Mail list logo
