Hi,
I've just started using Maven on some project at work (about 1 hour
ago). Just want to say it looks great and the plugin stuff looks very
very promising :-)
Here a few comments I have so far :
1/ I forgot to define lib.repo in my project and when I typed "ant
maven:site", I got an Ant error saying that the taskdef for such task
failed for some reason. Could Maven check for the existence of lib.repo
and report a nice message if it doesn't exist ?
2/ When I run maven:xxx targets, I find that there is a *lot* of garbage
on the screen. For example, just to display some env properties
"maven:env" target, here is what appears on the screen :
----------------------------------
Buildfile: build.xml
maven:env:
env:
update-pom-check:
callUpdateDescriptor:
project-properties:
Creating classpath reference ...
Creating dependency.set ...
Creating source set reference ...
Adding Reference maven.src.set with a value of
E:\Vma\Projets\Encours\ICOM\Icom\development\iceberg\
src\core
Creating aspect source set reference ...
Adding Reference maven.src.aspect.set with a value of
[project-properties] mpsd => null
Adding Reference maven.compile.src.set with a value of
E:\Vma\Projets\Encours\ICOM\Icom\development\
iceberg\src\core
Creating unit test class entries reference ...
Checking for old properties ...
load-default-properties:
prepare.httpget:
verify-project-proxy:
verify-project-noproxy:
verify-project:
init:
local-init:
pre-env-callback-check:
pre-env-callback:
do-env:
[echo]
java.home =
E:\Vma\Projets\Encours\ICOM\Icom\environment\tools\bea\jdk131\jre
user.home = C:\Documents and Settings\Vincent Massol
lib.repo = ../../environment/tools/maven/repository
Classpath:
post-env-callback-check:
post-env-callback:
env:
BUILD SUCCESSFUL
Total time: 3 seconds
----------------------------------
Mostly it is the "project-properties" target that is generating garbage.
If I use Maven, it is because I don't want to know the internal of the
build ... (only in debug mode to see what's happening).
One remark on naming : it would be nice I think if all Maven targets
were consistently named like "maven-xxx"
It would be even better if there were a way of "hiding" the internal
Maven target from being printed on the screen. One solution might
involve a maven specific logger that would not print Maven internal
targets ?
I would really be neat if the output of "ant maven:env" was :
----------------------------------
Buildfile: build.xml
maven:env:
[echo]
java.home =
E:\Vma\Projets\Encours\ICOM\Icom\environment\tools\bea\jdk131\jre
user.home = C:\Documents and Settings\Vincent Massol
lib.repo = ../../environment/tools/maven/repository
Classpath:
BUILD SUCCESSFUL
Total time: 3 seconds
----------------------------------
Don't you think ?
3/ I haven't looked into that one yet but the generated jar file has the
version in its name. We're not using version in names as these files get
used in turn by other projects and only the top level distributable get
a version in their name. Is it possible to customize this behaviour ?
(again I haven't looked at how Maven works yet - I will soon - so please
excuse this question if obvious).
Anyway, Maven looks very nice :-)
Thanks guys,
I might be participating a bit more to Maven development if we get to
use it on our project here ! I'm eager ... :-)
-Vincent
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
