I'm sorry, I feel really stupid here I've done this in a brand new directory
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic/ co -r MAVEN-1_0-BRANCH maven
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic/ co maven-plugins
(1.0 branch doesn't seem to be on maven-plugins )
cd maven rm -rf /usr/local/maven-cvs $HOME/.maven/plugins export MAVEN_HOME=/usr/local/maven-cvs
ant -d -f build-bootstrap.xml | tee ant.log
PS: Thank you guys for being so pacient...
It seems to be building now, I got confused about the branches.
What I was doing was using 1.0 branch for BOTH project (when it actually doesn't exists on plugins)
so there were no plugins to install, stupid me, still, but some info regarding this may be usefull somewhere on the compilation instructions...
I think I'll submit a path for the document
Arnaud Heritier wrote:
Miguel : Did you try to delete your plugins cache directory before the build?
Maury and others : Do not use the HEAD branch. I verified and the last modifications aren't applied to the HEAD branch. Sorry for this. It should be clarified.
#Arnaud.
-----Message d'origine----- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoy� : lundi 3 mai 2004 20:54 � : Maven Users List Objet : Re: Compile from CVS
Hi I'm getting the same problem there, I just run cvs up -r MAVEN-1_0-BRANCH -d -C on maven and maven-plugins checkouts... I's so happy with maven that I want to start building and contributing (if I can) but debugging the bootstrap seems a bit difficult fo rthe first task..
[exec] __ __ [exec] | \/ |__ _Apache__ ___ [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT
[exec] com.werken.werkz.NoSuchGoalException: No goal [clean] [exec] at org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScriptH ousings(GoalToJellyScriptHousingMapper.java:254) [exec] at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java:64 5) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) [exec] at org.apache.maven.cli.App.doMain(App.java:485) [exec] at org.apache.maven.cli.App.main(App.java:1208) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) [exec] at com.werken.forehead.Forehead.main(Forehead.java:581)
Arnaud Heritier wrote:
-----Message d'origine----- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoy� : lundi 3 mai 2004 20:01 � : Maven Users List Objet : Re: Compile from CVS
Hi I checked out the HEAD But I'm used to compile without problems HEADs (from open source projects...) I posted all info at jira here (included the ouput of ant -d )
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253
Shouldn't the head version compile?
Ok Miguel. In theory the Head must compile but in reality I'm not sure that all modifications are done in the two branches. The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as possible. Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH We are sure that this one compile.
I will try to find what the problem is with the HEAD.
#Arnaud.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
