Tested without running junits (due to my aforementioned junit failure) on
Windows 7 with Java 1.8.0_77-b03. All fine.

+1 from me

On Thu, Sep 22, 2016 at 2:23 AM, Aaron Coburn <acob...@amherst.edu> wrote:

> Hello,
>
> +1 (non-binding)
>
> I was able to successfully build and deploy the war files for Stanbol
> 1.0.0. Some simple testing shows everything working properly. I was also
> able to run the genericrdf indexer over a custom vocabulary (80 million
> triples) with success.
>
> I look forward with working more with this release!
>
> Thanks everyone.
> Aaron Coburn
>
>
> > On Sep 21, 2016, at 3:45 PM, A. Soroka <aj...@virginia.edu> wrote:
> >
> > Thank you for moving the release process forward!
> >
> > https://github.com/apache/stanbol/pull/5
> >
> > ---
> > A. Soroka
> > The University of Virginia Library
> >
> >> On Sep 21, 2016, at 3:27 PM, Rafa Haro <rh...@apache.org> wrote:
> >>
> >> Thanks a lot Soroka!
> >> El El mié, 21 sept 2016 a las 21:00, A. Soroka <aj...@virginia.edu>
> >> escribió:
> >>
> >>> I was able to build the same release code on OS X 10.10.5 using Java
> >>> 1.8.0_40 via mvn clean install. As a simple test, I was able to use the
> >>> EntityHub Generic indexer to index a medium-sized vocabulary of
> interest to
> >>> my site without difficulty. I did notice that the default config for
> the
> >>> Generic indexer uses the namespace prefix bio: for
> >>> http://vocab.org/bio/0.1/, which is apparently no longer an included
> >>> preset. This throws a warning during operation [1}. Also, the usage
> note
> >>> for the Generic indexer refers to
> >>> "org.apache.stanbol.indexing.core-*-jar-with-dependencies.jar" when
> in fact
> >>> the artifact is now called
> >>> "org.apache.stanbol.entityhub.indexing.genericrdf-*.jar". I can send
> a PR
> >>> for these minor annoyances if that would be useful.
> >>>
> >>>
> >>> ---
> >>> A. Soroka
> >>> The University of Virginia Library
> >>>
> >>> [1] E.g.
> >>>
> >>> 14:40:46,767 [main] WARN  mapping.FieldMappingUtils - Unable to parse
> >>> fieldMapping because of unknown namespace prefix
> >>> java.lang.IllegalArgumentException: The prefix 'bio' is unknown (not
> >>> mapped to an namespace) by the Stanbol Namespace Prefix Mapping
> Service.
> >>> Please change the configuration to use the full URI instead of 'bio:*'!
> >>>
> >>>
> >>>
> >>>> On Sep 20, 2016, at 2:07 PM, steve reinders <steve...@gmail.com>
> wrote:
> >>>>
> >>>> All,
> >>>>
> >>>> - I downloaded from
> >>> https://dist.apache.org/repos/dist/dev/stanbol/1.0.0/
> >>>> to OSX 10.11.6 ( 9:00 PM US CST Mon Sep 19 )
> >>>> - using 1.8.0_25 ( oracle )
> >>>> - built w/mvn install
> >>>> - only problem was CELI license
> >>>> - produced org.apache.stanbol.launchers.full-1.0.0.jar
> >>>>
> >>>> TopicClassifier looks to have been built fine.
> >>>>
> >>>> Is this the source's correct source ?
> >>>>
> >>>> BTW is the CMS REST interface in ? Can't tell easily in Jira and I
> knew
> >>> it
> >>>> was pulled in earlier version.
> >>>>
> >>>> danke
> >>>>
> >>>> Steve
> >>>>
> >>>>
> >>>> On Tue, Sep 20, 2016 at 12:00 PM, Rafa Haro <rh...@apache.org> wrote:
> >>>>
> >>>>> Hi Cristian,
> >>>>>
> >>>>> Apparently the Topic Annotation engine is only compiling with OpenJDK
> >>>>> 1.8.x. As far as I know, that code has remained untouched since long
> >>> time
> >>>>> ago, but we should probably remove that dependency (although I don't
> >>> see it
> >>>>> a problem for not going ahead with the release).
> >>>>>
> >>>>> By the way, I have checked the artifacts and signatures, built also
> from
> >>>>> source without problems
> >>>>>
> >>>>> Therefore +1 for me
> >>>>>
> >>>>> Cheers,
> >>>>> Rafa
> >>>>>
> >>>>> On Mon, Sep 19, 2016 at 10:37 PM Rafa Haro <rh...@apache.org> wrote:
> >>>>>
> >>>>>> Hi Cristian,
> >>>>>>
> >>>>>> I build it directly from the SVN tag and didn't have any problem. I
> >>> will
> >>>>>> check tomorrow the source packages
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Rafa
> >>>>>> El El lun, 19 sept 2016 a las 22:21, Cristian Petroaca <
> >>>>>> cristian.petro...@gmail.com> escribió:
> >>>>>>
> >>>>>>> Hi guys,
> >>>>>>>
> >>>>>>> I downloaded the sources from here https://dist.apache.org/repos/
> >>>>>>> dist/dev/stanbol/1.0.0/
> >>>>>>> <https://dist.apache.org/repos/dist/dev/stanbol/1.0.0/> and did a
> >>> "mvn
> >>>>>>> install" but some tests failed with:
> >>>>>>> Tests run: 7, Failures: 0, Errors: 5, Skipped: 0, Time elapsed:
> 4.33
> >>> sec
> >>>>>>> <<< FAILURE! - in org.apache.stanbol.enhancer.
> >>>>> engine.topic.TopicEngineTest
> >>>>>>>
> >>>>>>> testCrossValidation(org.apache.stanbol.enhancer.
> >>>>> engine.topic.TopicEngineTest)
> >>>>>>> Time elapsed: 2.108 sec  <<< ERROR!
> >>>>>>> java.lang.NoClassDefFoundError: Could not initialize class
> >>>>>>> sun.security.provider.SecureRandom$SeederHolder
> >>>>>>>      at
> >>>>>>> sun.security.provider.SecureRandom.engineNextBytes(
> >>>>> SecureRandom.java:221)
> >>>>>>>      at java.security.SecureRandom.nextBytes(SecureRandom.java:
> 468)
> >>>>>>>      at java.util.UUID.randomUUID(UUID.java:145)
> >>>>>>>      at
> >>>>>>>
> >>>>>>> org.apache.stanbol.enhancer.engine.topic.
> TopicClassificationEngine.
> >>>>> addConcept(TopicClassificationEngine.java:790)
> >>>>>>>      at
> >>>>>>>
> >>>>>>> org.apache.stanbol.enhancer.engine.topic.
> TopicClassificationEngine.
> >>>>> addConcept(TopicClassificationEngine.java:825)
> >>>>>>>      at
> >>>>>>>
> >>>>>>> org.apache.stanbol.enhancer.engine.topic.TopicEngineTest.
> >>>>> initArtificialTrainingSet(TopicEngineTest.java:537)
> >>>>>>>      at
> >>>>>>>
> >>>>>>> org.apache.stanbol.enhancer.engine.topic.TopicEngineTest.
> >>>>> testCrossValidation(TopicEngineTest.java:475)
> >>>>>>>
> >>>>>>> Java version:
> >>>>>>> java version "1.8.0_77"
> >>>>>>> Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
> >>>>>>> Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)
> >>>>>>>
> >>>>>>>
> >>>>>>> My java version is the Oracle one, not OpenJDK.
> >>>>>>> I looked that class up, SecureRandom, but I can't find it in
> Oracle's
> >>>>>>> documentation in that package but rather here:
> >>>>>>> https://docs.oracle.com/javase/7/docs/api/java/
> >>>>> security/SecureRandom.html
> >>>>>>>
> >>>>>>> Not sure if this is the problem.
> >>>>>>>
> >>>>>>> Cristian
> >>>>>>>
> >>>>>>> On Sat, Sep 17, 2016 at 1:55 PM, Antonio David Pérez Morales <
> >>>>>>> adperezmora...@gmail.com> wrote:
> >>>>>>>
> >>>>>>>> Tested
> >>>>>>>>
> >>>>>>>> +1 for me
> >>>>>>>>
> >>>>>>>> Regards
> >>>>>>>>
> >>>>>>>> El 16 sept. 2016 6:38 p. m., "Rafa Haro" <rh...@apache.org>
> >>> escribió:
> >>>>>>>>
> >>>>>>>>> Hi devs,
> >>>>>>>>>
> >>>>>>>>> Please vote on wether to release Apache Stanbol 1.0.0 RC0. This
> is
> >>>>> the
> >>>>>>>>> first 1.x.x release and the first release since version 0.12
> (more
> >>>>>>> than 2
> >>>>>>>>> years ago). Therefore, it is not easy to summarize all the
> changes
> >>>>>>> since
> >>>>>>>>> then. Please refer to https://issues.apache.org/
> jira/browse/STANBOL
> >>>>>>> for
> >>>>>>>> an
> >>>>>>>>> exhaustive list of issues fixed in this version.
> >>>>>>>>>
> >>>>>>>>> The release source code can be found at the following tag:
> >>>>>>>>>
> >>>>>>>>> http://svn.apache.org/repos/asf/stanbol/tags/apache-
> stanbol-1.0.0/
> >>>>>>>>>
> >>>>>>>>> The release includes the complete Apache Stanbol stack with all
> >>>>>>>> components.
> >>>>>>>>> The release artifacts are staged at:
> >>>>>>>>>
> >>>>>>>>> https://repository.apache.org/content/repositories/
> >>>>>>>> orgapachestanbol-1009/
> >>>>>>>>>
> >>>>>>>>> and the source packages here:
> >>>>>>>>>
> >>>>>>>>> https://dist.apache.org/repos/dist/dev/stanbol/1.0.0/
> >>>>>>>>>
> >>>>>>>>> You can check the staged Maven artifacts using the script in
> >>>>>>> 'releasing'
> >>>>>>>>> ./check_staged_release.sh 1009 [tmp-directory]
> >>>>>>>>>
> >>>>>>>>> PGP release singing keys are available at:
> >>>>>>>>>
> >>>>>>>>> https://people.apache.org/keys/group/stanbol.asc
> >>>>>>>>>
> >>>>>>>>> The vote will be open for 72 hours
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> >>>
> >
>
>

Reply via email to