If this is a permanent problem, I am +1 for removing from the default build.
Make sure that according integration tests and launcher configuration do not reference the metaxa engine. Anyway, IRC the tika engine is used by default for the metaxa funcationality, right? 2012/9/7 Dave Butler <butle...@gmail.com>: > +1 > > On 7 September 2012 14:51, Reto Bachmann-Gmür <r...@apache.org> wrote: > >> Trying a fresh stanbol build it failf with the following error: >> >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-remote-resources-plugin:1.2.1:process >> (default) on project org.apache.stanbol.enhancer.engines.metaxa: Error >> resolving project artifact: Could not transfer artifact >> org.semweb4j:rdf2go.api:pom:4.7.3 from/to aperture-repo ( >> http://aperture.sourceforge.net/maven/): Failed to look for file: >> >> http://aperture.sourceforge.net/maven/org/semweb4j/rdf2go.api/4.7.3/rdf2go.api-4.7.3.pom >> . >> Return code is: 503 for project org.semweb4j:rdf2go.api:jar:4.7.3 -> [Help >> 1] >> >> >> Maybe we should remove metaxa from profiles executed by default as long as >> STANBOL-510 isn't resolved. >> >> WDYT? >> >> Reto >> > > > > -- > Regards > > Dave Butler > butlerdi-at-pharm2phork-dot-org > > Also on Skype as pharm2phork > > Get Skype here http://www.skype.com/download.html > > > ********************************************************************** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > > This footnote also confirms that this email message has been swept by > MIMEsweeper for the presence of computer viruses. > > www.mimesweeper.com > ********************************************************************** -- Fabian http://twitter.com/fctwitt
