Begin forwarded message:
From: "Jens Riboe" <[EMAIL PROTECTED]> Date: April 12, 2004 2:52:47 PM EDT To: <[EMAIL PROTECTED]> Subject: Embedded Maven or Maven Light??? Reply-To: "Ant Users List" <[EMAIL PROTECTED]>
Hi,
I have started to messing around with maven.
The repository idea is brilliant and the site generation with all these reports
are very healthy for the ego.
However, every time I try something new, I found my self browsing around chasing
some non-existent or partial documentation, wasting hour after hour.
In addition, I don't really buy the 'one artifact per project' idea.
So, I wonder if I'm alone or there are anybody out there fealing the same,
that Ant should be extended with some of the Maven features.
What I really would like to see is a mavenfileset, similar to the example below
<mavenfileset url="${maven.repo}" cachedir="${maven.local}" >
<include groupid="${xyz.groupid}" artifactid="${xyz.id}" version="${xyz.version}"/>
</mavenfileset >
Has anybody already implemented something like this? Comments?
Kind regards, Jens Riboe
Begin forwarded message:
From: "Stirling, Scott" <[EMAIL PROTECTED]> Date: April 12, 2004 3:20:39 PM EDT To: "Ant Users List" <[EMAIL PROTECTED]> Subject: RE: Embedded Maven or Maven Light??? Reply-To: "Ant Users List" <[EMAIL PROTECTED]>
From: Jens Riboe [mailto:[EMAIL PROTECTED][snip]So, I wonder if I'm alone or there are anybody out there fealing the same, that Ant should be extended with some of the Maven features.
Naaaah. I liked Maven too at first, but ran into the same problems you did. The worst was the dependency checking between project components, which didn't work. A lot of Maven stuff only works right if you're faithful and diligent on the maven email list. After a while I decided the whole thing had miles to go before it could be useful on anything other than Jakarta projects (and other one-offs, like sourceforge projects where 1 jar per project is the norm).
What I really would like to see is a mavenfileset, similar to the example below <mavenfileset url="${maven.repo}" cachedir="${maven.local}" > <include groupid="${xyz.groupid}" artifactid="${xyz.id}" version="${xyz.version}"/> </mavenfileset >
The whole repo idea is pretty useless in my environment. We just check the needed jars for a project into the source control structure for the project and update them there as needed. We depend on stability for internal and external libraries, and have no need to be downloading the nightly build of every jakarta commons project (which seems to be the sweet spot of the REPO idea), or forcing upgrades of our own libraries onto other teams. We toyed with the idea of an intranet Maven REPO, but that quickly seemed stupid since once everyone's downloaded the jars in the REPO (which happens the first two hours of use), it won't get used again until you update a jar. And you can just as easily do that with your source control system without Maven.
I think the best idea Maven has going for it is the Project Object Model concept. Last I looked (about a year ago) it needed a lot of work to be robust enough (and extensible) to support professional enterprise projects. IMO, that's what Maven can and should capitalize on and run with. On a related note, I guess that's an area where Ant could incorporate the ideas of Maven by beefing up the build.xml with some more structure, at least as an alternative for those who want it.
YMMV.
Best, Scott Stirling Workscape, Inc. *********************************************************************** This message is intended only for the use of the intended recipient and may contain information that is PRIVILEGED and/or CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any use, dissemination, disclosure or copying of this communication is strictly prohibited. If you have received this communication in error, please destroy all copies of this message and its attachments and notify us immediately. ***********************************************************************
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Begin forwarded message:
From: Stefan Bodewig <[EMAIL PROTECTED]> Date: April 13, 2004 2:48:10 AM EDT To: [EMAIL PROTECTED] Subject: Re: Embedded Maven or Maven Light??? Reply-To: "Ant Users List" <[EMAIL PROTECTED]>
On Mon, 12 Apr 2004, Jens Riboe <[EMAIL PROTECTED]> wrote:
So, I wonder if I'm alone or there are anybody out there fealing the same, that Ant should be extended with some of the Maven features.
Since you are asking for the repository stuff specifically.
There is a project inside the Apache Incubator[1] named Depot[2] that defines a repository specification (which is based on but goes beyond Maven AFAIU) as well as tools that build upon this. Part of the tool-chain is a set of Ant tasks.
I've not followed this effort but you may find it helpful.
Stefan
Footnotes: [1] http://incubator.apache.org/
[2] http://incubator.apache.org/projects/depot.html
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
