Mark, Thank you for the explanation that makes a lot of sense to me. Looks like I know what to do now.
> Mike P.S: Hope your team won! \o/ -----Original Message----- From: Mark Struberg [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2008 7:05 PM To: Maven Users List Subject: RE: Building Maven2 Hi Michael! I did some research and compared the PerforceAddConsumer version you probably use (maven-scm-1.0) with the one from trunk: < private static final String PATTERN = "^([^#]+)#1 - (.*)"; > private static final String PATTERN = "^([^#]+)#(\\d+) - (.*)"; The 2nd line is from trunk (anyone knows the Jira of this change?). So the reg exp which parses the line has changed! Maybe this is the problem you have :( For looking at the RE quickly I would guess the original version only could handle #1 versions, whereas the newer RE also handles your #4. I hope my thoughts are clear enough on the very long cheer- and beerfull soccer-EM evening :) good night, strub PS: the good news: if I'm right, you do not have to change your perforce installation but only use the new perforce provider. the bad news: you have to use the new perforce provider ;) --- Mark Struberg <[EMAIL PROTECTED]> schrieb am Sa, 14.6.2008: > Von: Mark Struberg <[EMAIL PROTECTED]> > Betreff: RE: Building Maven2 > An: "Maven Users List" <users@maven.apache.org> > Datum: Samstag, 14. Juni 2008, 0:32 > Hi Michael! > > You don't need to build the whole maven2 stuff. My goal > was to check if your perforce version generates slightly > different logs than the one the maven-scm-provider-perforce > was programmed with. > > Please see the following debug output files and compare > them with the propriate output from your p4: > http://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-providers/maven-scm-provider-perforce/src/test/resources/perforce/ > > The tests of a SCM provider can be separated into 2 > categories > > 1.) tests which are run against pre generated output files > (like the ones above) > 2.) TCK tests which run real use cases. For this test > cases, the PerforceAddConsumer has to parse the output of > the real p4 command! That's what may fail on your > computer. > > I hope this explains why I asked you to run the tests, and > which part is relevant and which not. > > For not loosing the context, I copy the exception from your > mvn release with your p4 installation from your previous > post (titled "Release plugin questions"): > Caused by: java.lang.IllegalStateException: Unknown input: > //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened > for add > at > org.apache.maven.scm.provider.perforce.command.add.PerforceAddConsumer.consumeLine(PerforceAddConsumer.java:79) > at > org.apache.maven.scm.provider.perforce.command.add.PerforceAddCommand.executeAddCommand(PerforceAddCommand.java:63) > > > At least this would be the first point to look at for > searching the source of the problem. First guess: either p4 > is old, or the scm-provider is old. Which version are you > using? This may also be a line delimiter problem or other > wired stuff ... > > LieGrü, > strub > > > --- Michael Delaney <[EMAIL PROTECTED]> schrieb > am Fr, 13.6.2008: > > > Von: Michael Delaney <[EMAIL PROTECTED]> > > Betreff: RE: Building Maven2 > > An: "Maven Users List" > <users@maven.apache.org> > > Datum: Freitag, 13. Juni 2008, 16:58 > > Wayne, > > > > Well, I am trying to debug a possible issue with the > > Perforce SCM > > provider. I was asked to build & run units tests > > against the Perforce > > SCM provider. Rather then just attempt to build then > post > > errors that > > ended up being an issue with my environment, I decided > it > > would be a > > good idea to build Maven 2 first to validate the > > environment. That way > > if any issue were found with the Perforce SCM > provider, I > > could at least > > say that know my environment is good (or should be). > > > > > > > > > Mike D. > > > > -----Original Message----- > > From: Wayne Fay [mailto:[EMAIL PROTECTED] > > Sent: Friday, June 13, 2008 10:53 AM > > To: Maven Users List > > Subject: Re: Building Maven2 > > > > If you don't mind me asking, why are you trying to > > build Maven? Just > > for fun; because corporate says we have to be able to > build > > everything > > (including our tools) from scratch; some other reason; > etc? > > > > Wayne > > > > On 6/13/08, Michael Delaney > <[EMAIL PROTECTED]> > > wrote: > > > Ram, > > > > > > I was trying to build everything, I went into the > root > > of the Maven 2 > > > source distribution and executed > > "bootstrap.bat". The steps were as > > > follows: > > > cd /d > > C:\tmp\maven-2.0.9-src\maven-2.0.9-src > > > set M2_HOME=c:\apache-maven-2.0.9 > > > set PATH=%M2_HOME%\bin;%PATH% > > > bootstrap.bat > > > > > > The documentation I followed is listed at > > > > > > http://maven.apache.org/guides/development/guide-building-m2.html, > > and > > I > > > was using the section "Building Maven 2.0 > Without > > Maven Installed". > > > > > > Here is a print out of the relevant environment > > variables > > > JAVA_HOME=c:\Program > > Files\Java\jdk1.5.0_13 > > > M2_HOME=c:\tmp\apache-maven-2.0.9 > > > > > > -----Original Message----- > > > From: RAM [mailto:[EMAIL PROTECTED] > > > Sent: Friday, June 13, 2008 4:11 AM > > > To: Maven Users List > > > Subject: Re: Building Maven2 > > > > > > The error message is little bit confusing > :"Null > > Pointer Exception in > > > thread > > > main". What are you trying to build? > > > I did the following setup and its working fine > for me: > > > > > > M2_HOME = D:\apache-maven-2.0.9 > > > JAVA_HOME = {Here the *JDK* Path] Remember Maven > > doesnt work properly > > > with > > > JRE > > > PATH: %M2_HOME%/bin > > > > > > Just run mvn --version and we are good to go. > > > If you are getting the version printed as 2.0.9, > its > > correctly > > > installed. > > > > > > Also, if you can forward the apache link you are > > talking about (where > > > you > > > got the example), I can look into that. > > > > > > __________________________________________________________ > Gesendet von Yahoo! Mail. > Dem pfiffigeren Posteingang. > http://de.overview.mail.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] __________________________________________________________ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com --------------------------------------------------------------------- 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]
