It should not be even referencing the SCM to be honest as the perforce plug-in 
is not useable in its present state. 

I am using 2.2.1 myself on Linux and Windows and having no such issue. It must 
be something to do with the Mac or your installation (are you going to the net 
for your repository or using a local cache?), but as my Mac is touring India at 
the moment, I cannot check the Mac version. Perhaps someone else can try this?

Jim

> -----Original Message-----
> From: [email protected] [mailto:antlr-interest-
> [email protected]] On Behalf Of William B. Clodius
> Sent: Tuesday, December 15, 2009 9:23 PM
> To: [email protected]
> Subject: Re: [antlr-interest] Maven problems with ANTLR 3.2
> 
> Jim:
> 
> FWIW
> 
> 1. Commenting out and deleting the scm lines in antler-
> 3.2/runtime/Java/pom.xml yields the same result
> 
> 2. antlr-3.2/BUILD.txt has the lines
> "The main development branch of ANTLR is stored within the Perforce SCM
> at:
> 
>    //depot/code/antlr/main/..."
> could the problem be in the Perforce SCM?
> 
> 3. Those are the only references to an scm I can find in the antlr-3.2
> directory tree
> 
> On Dec 15, 2009, at 2:27 PM, Jim Idle wrote:
> 
> > I am not sure why this would be different on your Mac. It is possible
> though that I did not specify a specific version of the SCM plugin and
> so your build has picked some newly released version which does not
> like the fact that the SCM is seemingly null. However the only place
> where I specified the SCM was in the Java runtime pom, then I abandoned
> the scm idea because the perforce scm plugin is terrible and full of
> bugs. So, you could just remove the scm reference from that pom.xml
> file and see if it makes a difference. However, the scm isn't null in
> that reference so I don't know why you would get this and nobody else
> does.
> >
> > Jim
> >
> >> -----Original Message-----
> >> From: [email protected] [mailto:antlr-interest-
> >> [email protected]] On Behalf Of William B. Clodius
> >> Sent: Monday, December 14, 2009 9:55 PM
> >> To: [email protected]
> >> Subject: [antlr-interest] Maven problems with ANTLR 3.2
> >>
> >> I am trying to build ANTLR 3.2 with maven 2.2.1 on Mac OS X 10.6.2
> and
> >> am having problems with what I believe is a null pointer exception.
> The
> >> test below is the result of trying to rerun maven after my first
> build.
> >> Any suggestions?
> >>
> >> bash-3.2$ mvn -Dmaven.test.skip=true | more
> >> [INFO] Scanning for projects...
> >> [INFO] Reactor build order:
> >> [INFO]   ANTLR Master build control POM
> >> [INFO]   Antlr 3 Runtime
> >> [INFO]   ANTLR Grammar Tool
> >> [INFO]   Maven plugin for ANTLR V3
> >> [INFO]   ANTLR gUnit
> >> [INFO]   Maven plugin for gUnit ANTLR V3
> >> [INFO] -------------------------------------------------------------
> ---
> >> --------
> >> [INFO] Building ANTLR Master build control POM
> >> [INFO]    task-segment: [install]
> >> [INFO] -------------------------------------------------------------
> ---
> >> --------
> >> [INFO] [buildnumber:create {execution: default}]
> >> [INFO] Storing buildNumber: Dec 14, 2009 22:38:09 at timestamp:
> >> 1260855489961
> >> [INFO] -------------------------------------------------------------
> ---
> >> --------
> >> [ERROR] FATAL ERROR
> >> [INFO] -------------------------------------------------------------
> ---
> >> --------
> >> [INFO] The scm url cannot be null.
> >> [INFO] -------------------------------------------------------------
> ---
> >> --------
> >> [INFO] Trace
> >> java.lang.NullPointerException: The scm url cannot be null.
> >>        at
> >>
> org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(Abstr
> >> actScmManager.java:181)
> >>        at
> >>
> org.codehaus.mojo.build.CreateMojo.getScmRepository(CreateMojo.java:722
> >> )
> >>        at
> >> org.codehaus.mojo.build.CreateMojo.getScmBranch(CreateMojo.java:593)
> >>        at
> >> org.codehaus.mojo.build.CreateMojo.execute(CreateMojo.java:452)
> >>        at
> >>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginM
> >> anager.java:490)
> >>        at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defaul
> >> tLifecycleExecutor.java:694)
> >>        at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLife
> >> cycle(DefaultLifecycleExecutor.java:556)
> >>        at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Default
> >> LifecycleExecutor.java:535)
> >>        at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandl
> >> eFailures(DefaultLifecycleExecutor.java:387)
> >>        at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
> >> (DefaultLifecycleExecutor.java:348)
> >>        at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLife
> >> cycleExecutor.java:180)
> >>        at
> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> >>        at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> >>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >>        at
> >>
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> >>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> >>        at
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja
> >> va:39)
> >>        at
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso
> >> rImpl.java:25)
> >>        at java.lang.reflect.Method.invoke(Method.java:597)
> >>        at
> >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >>        at
> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >>        at
> >>
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >>        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >> [INFO] -------------------------------------------------------------
> ---
> >> --------
> >> [INFO] Total time: 2 seconds
> >> [INFO] Finished at: Mon Dec 14 22:38:09 MST 2009
> >> [INFO] Final Memory: 20M/264M
> >> [INFO] -------------------------------------------------------------
> ---
> >> --------
> >>
> >>
> >> List: http://www.antlr.org/mailman/listinfo/antlr-interest
> >> Unsubscribe: http://www.antlr.org/mailman/options/antlr-
> interest/your-
> >> email-address
> >
> >
> >
> >
> > List: http://www.antlr.org/mailman/listinfo/antlr-interest
> > Unsubscribe: http://www.antlr.org/mailman/options/antlr-
> interest/your-email-address
> >
> 
> 
> List: http://www.antlr.org/mailman/listinfo/antlr-interest
> Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-
> email-address




List: http://www.antlr.org/mailman/listinfo/antlr-interest
Unsubscribe: 
http://www.antlr.org/mailman/options/antlr-interest/your-email-address

--

You received this message because you are subscribed to the Google Groups 
"il-antlr-interest" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/il-antlr-interest?hl=en.


Reply via email to