You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Reto Bachmann-Gmür <re...@apache.org> on 2012/09/07 14:51:53 UTC
compilation failure because of metaxa dependency
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
Re: compilation failure because of metaxa dependency
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi,
AFAIK metaxa is optional anyway. So removing it from the default build
process should not cause any issues.
> Anyway, IRC the tika engine is used by default for the metaxa
> funcationality, right?
yes
best
Rupert
BTW: we should upgrade Tika to 1.2 (http://tika.apache.org/1.2/index.html)
On Fri, Sep 7, 2012 at 3:04 PM, Fabian Christ
<ch...@googlemail.com> wrote:
> 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 <bu...@gmail.com>:
>> +1
>>
>> On 7 September 2012 14:51, Reto Bachmann-Gmür <re...@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
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: compilation failure because of metaxa dependency
Posted by Fabian Christ <ch...@googlemail.com>.
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 <bu...@gmail.com>:
> +1
>
> On 7 September 2012 14:51, Reto Bachmann-Gmür <re...@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
Re: compilation failure because of metaxa dependency
Posted by Dave Butler <bu...@gmail.com>.
+1
On 7 September 2012 14:51, Reto Bachmann-Gmür <re...@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
**********************************************************************