You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2009/12/03 07:35:46 UTC

release candidate 05 is now posted at the usual place

Find it at
http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC5/

except for the uima-cpp release, which remains under rc1 (it hasn't
changed).

(Release candidate 4 had RAT issues).

The compare of the source export out of svn with our source distribution
should be closer - but some differences remain, including treatment of
empty directories ( present in SVN, but not in the source assembly).

-Marshall

Re: release candidate 05 is now posted at the usual place

Posted by Thilo Goetz <tw...@gmx.de>.
Tommaso Teofili wrote:
> Hi Thilo,
> I tried what you did and got the same problem.
> The <developerConnection> tag inside <scm> is missing, once that is fixed, I
> got everything to work.

Ok, that's great!

> I can commit the patch if you think it's alright.

Yes, please do.  I'm sure Marshall will be happy when he wakes up
and sees this problem has already been fixed :-)

--Thilo

> Cheers.
> Tommaso
> 
> 2009/12/4 Thilo Goetz <tw...@gmx.de>
> 
>> Marshall Schor wrote:
>>> Find it at
>>> http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC5/<http://people.apache.org/%7Eschor/uima-release-candidates/2.3.0-RC5/>
>>>
>>> except for the uima-cpp release, which remains under rc1 (it hasn't
>>> changed).
>>>
>>> (Release candidate 4 had RAT issues).
>>>
>>> The compare of the source export out of svn with our source distribution
>>> should be closer - but some differences remain, including treatment of
>>> empty directories ( present in SVN, but not in the source assembly).
>>>
>>> -Marshall
>> I can't build the release candidate with a clean mvn repo.  Here's
>> what I did.  Downloaded UIMA core sources, unpacked, cd to uimaj.
>> Move local maven repo for really clean build.  I do this with every
>> release candidate, it worked with RC3.  Call mvn install.  I get
>> the usual helpful error message below.  I'm using the latest stable
>> maven release, 2.2.1.
>>
>> Now when I use my previous local maven cache, everything works.  Can
>> anybody reproduce this behavior?
>>
>> --Thilo
>>
>> [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(Abs
>> tractScmManager.java:181)
>>        at
>> org.codehaus.mojo.build.CreateMojo.getScmRepository(CreateMojo.java:7
>> 22)
>>        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(DefaultPlugi
>> nManager.java:490)
>>        at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> ultLifecycleExecutor.java:694)
>>        at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> fecycle(DefaultLifecycleExecutor.java:556)
>>        at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> ltLifecycleExecutor.java:535)
>>        at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> dleFailures(DefaultLifecycleExecutor.java:387)
>>        at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> ts(DefaultLifecycleExecutor.java:348)
>>        at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> fecycleExecutor.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:6
>> 0)
>>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>        at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> java:45)
>>        at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> sorImpl.java:37)
>>        at java.lang.reflect.Method.invoke(Method.java:599)
>>        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: 34 seconds
>> [INFO] Finished at: Fri Dec 04 09:34:49 CET 2009
>> [INFO] Final Memory: 19M/73M
>> [INFO]
>> ------------------------------------------------------------------------
>> D:\installers\uima\2.3-rc5\build\uimaj-2.3.0-incubating\uimaj>
>>
> 


Re: release candidate 05 is now posted at the usual place

Posted by Tommaso Teofili <to...@gmail.com>.
Hi Thilo,
I tried what you did and got the same problem.
The <developerConnection> tag inside <scm> is missing, once that is fixed, I
got everything to work.
I can commit the patch if you think it's alright.
Cheers.
Tommaso

2009/12/4 Thilo Goetz <tw...@gmx.de>

> Marshall Schor wrote:
> > Find it at
> > http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC5/<http://people.apache.org/%7Eschor/uima-release-candidates/2.3.0-RC5/>
> >
> > except for the uima-cpp release, which remains under rc1 (it hasn't
> > changed).
> >
> > (Release candidate 4 had RAT issues).
> >
> > The compare of the source export out of svn with our source distribution
> > should be closer - but some differences remain, including treatment of
> > empty directories ( present in SVN, but not in the source assembly).
> >
> > -Marshall
>
> I can't build the release candidate with a clean mvn repo.  Here's
> what I did.  Downloaded UIMA core sources, unpacked, cd to uimaj.
> Move local maven repo for really clean build.  I do this with every
> release candidate, it worked with RC3.  Call mvn install.  I get
> the usual helpful error message below.  I'm using the latest stable
> maven release, 2.2.1.
>
> Now when I use my previous local maven cache, everything works.  Can
> anybody reproduce this behavior?
>
> --Thilo
>
> [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(Abs
> tractScmManager.java:181)
>        at
> org.codehaus.mojo.build.CreateMojo.getScmRepository(CreateMojo.java:7
> 22)
>        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(DefaultPlugi
> nManager.java:490)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:694)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:556)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:535)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:387)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:348)
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.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:6
> 0)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:45)
>        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:37)
>        at java.lang.reflect.Method.invoke(Method.java:599)
>        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: 34 seconds
> [INFO] Finished at: Fri Dec 04 09:34:49 CET 2009
> [INFO] Final Memory: 19M/73M
> [INFO]
> ------------------------------------------------------------------------
> D:\installers\uima\2.3-rc5\build\uimaj-2.3.0-incubating\uimaj>
>

Re: release candidate 05 is now posted at the usual place

Posted by Thilo Goetz <tw...@gmx.de>.
Marshall Schor wrote:
> Find it at
> http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC5/
> 
> except for the uima-cpp release, which remains under rc1 (it hasn't
> changed).
> 
> (Release candidate 4 had RAT issues).
> 
> The compare of the source export out of svn with our source distribution
> should be closer - but some differences remain, including treatment of
> empty directories ( present in SVN, but not in the source assembly).
> 
> -Marshall

I can't build the release candidate with a clean mvn repo.  Here's
what I did.  Downloaded UIMA core sources, unpacked, cd to uimaj.
Move local maven repo for really clean build.  I do this with every
release candidate, it worked with RC3.  Call mvn install.  I get
the usual helpful error message below.  I'm using the latest stable
maven release, 2.2.1.

Now when I use my previous local maven cache, everything works.  Can
anybody reproduce this behavior?

--Thilo

[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(Abs
tractScmManager.java:181)
        at org.codehaus.mojo.build.CreateMojo.getScmRepository(CreateMojo.java:7
22)
        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(DefaultPlugi
nManager.java:490)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:694)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:556)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:535)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:387)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:348)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.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:6
0)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:45)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:599)
        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: 34 seconds
[INFO] Finished at: Fri Dec 04 09:34:49 CET 2009
[INFO] Final Memory: 19M/73M
[INFO] ------------------------------------------------------------------------
D:\installers\uima\2.3-rc5\build\uimaj-2.3.0-incubating\uimaj>