build of this new repository. There were a fer jars that Maven was not able to locate
ibiblio. I think it was for licensing reasons, but I had to go hunting for them myself. I
was able to get things working by placing the correctly named jars into the local maven
repository directories that maven had already created prior to attempting to download
the jars itself.
Setting up a secondary repository would probably be a better option as it would make
it easier to get things working on another machine later...
Now that I have finally gotten maven up and running, I am starting to get used to it.
I don't think that I am aware of the '+'s yet to give it a fair vote.
Maven negatives:
-I have found it to be slower than Ant when I just want to try and compile my jars as
I am doing development.
-The commands to execute maven goals tend to be longer than their ant equivalents.
-The 'maven -g' command is not very useful. It tells you every possible thing that
maven can do. I liked the 'ant -projecthelp' command because it told you what
tasks were useful to the current project. When I don't know how to build a given
project (especially as a new maven user) I could not easily figure out what I was
supposed to have been doing to build the jars. Now I know it is simply
'maven jar:install' or 'maven multiproject:install' to build a series of projects in
subdirectories.
-Maven positives. -There are a lot features built in. (site docs, reports, etc.) -The builds are consistent between projects. -It seems much easier to do to non standard things in Ant (a real plus?) -The project specific build files are much simpler.
Right now, I have both working, so I will go along with the consensus.
Cheers, Leif
Cheers, Leif
Antonio Gallardo wrote:
Peter Donald dijo:
It is easy to maintain your own separate repository if you need this
functionality. ie Several of my own projects have a maven repo kept in
source control to perform this functionality
I know. I was talking about users....
Best Regards,
Antonio Gallardo
Antonio Gallardo wrote:
Hi:
The problem I see with maven is that the repository not always is updated. You need to create a patch is yu want to use a new library. I think overall it makes more complex the jar updates. Recently, I have a similar problem with maven while trying to use util.concurrent.1.3.4 for Apache JCS. Because the library was not there I needed to create a patch for maven repository.
I see that as a dependency. But if this is not important for excalibur, it is OK. I like maven. I don't like to make patch for a new library support.
Best Regards,
Antonio Gallardo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
