[jira] Commented: (MAVEN-1426) CreatingJ2eeApplications : KevinRoss' works

[ji...@codehaus.org]

The following comment has been added to this issue:

     Author: bmak
    Created: Tue, 17 Aug 2004 2:09 AM
       Body:
forgot to mention: RE: command lines:

i dunno, maybe there's some other way, but i found that using -p <fullfilepath>/root/project.xml was the only way that i could get the root to run first. 

and the command line interface is not defined anywhere I've spotted. maven -h is god awful documentation artifact. clearly, it is the last resort, and not the same as a UNIX manpage on maven.

so documenting the fact that the -p option requires the entire path AND the project.xml filename would help a whole lot.

ditto that -p required to get to the ${basename}/root/project.xml

of course, i have no idea what the -d or -f options buy relative to -p or their true option argument syntax.


---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MAVEN-1426?page=comments#action_23169

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MAVEN-1426

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1426
    Summary: CreatingJ2eeApplications :  KevinRoss' works
       Type: Bug

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
   Versions:
             1.0

   Assignee: 
   Reporter: bmak

    Created: Tue, 17 Aug 2004 1:27 AM
    Updated: Tue, 17 Aug 2004 2:09 AM
Environment: maven 1.0 on windows 2k/sp4, running over cygwin, sun 1.4.2 j2se

Description:
maven documentation crippled and braindead as what a newbie needs to see. nine months ago, it took me a couple days to get my first maven to work. and this week, almost as long to get my first multiproject to work. 

there're tons of examples of newbie documentation for other tools in the world, so I just don't get why the most simpliest of concepts are lost such as an examples using the code ...

so my rant includes the observation of "many hours" to first multiproject:install would have been avoided if:

1. the example maven project.* files depicted on the wiki CreatingJ2eeApplications actually worked. they do not!!!!! When I run it, maven does not detect any of the subprojects. It prints a short few comments, basically shugging its shoulders in a big "ah, I dunno. nothing to do. you win!" in short, the maven.xml files screw everything up. nice to know you can drop a maven.xml into an subproject tree, but maybe a simpler example -- or 2 or 3 -- would build some confidence up before trying that maven.xml stuff......

2. Someone actually documented what command lines to run, starting with 'multiproject:install'. Plus, some example goals that you might want OTHER than 'multiproject:install'. Like clean. (I wasn't too crazy that it dumped my jar into my local maven repository, so like describing what will happen when you run these goals would have been nice.)

3. someone update the CreatingJ2eeApplications wiki page to reflect KevinRoss source code (hidden away in the small print). THAT actually works out of the box. 

end rant


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org