[
https://issues.apache.org/jira/browse/STANBOL-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204702#comment-14204702
]
Rupert Westenthaler commented on STANBOL-1402:
----------------------------------------------
I can confirm this. The reason is that somehow the most recent release of
"org.apache.felix.http.jetty" (version 2.3.0) got used when building the
launcher. However 0.12.0 is supposed to use version 2.2.1
Explicitly adding this version to the <jarWebSupport> section of the pom fixes
this issue.
Here is the corrected code segment.
{code}
<!-- Standalone jar requires an OSGi http service implementation
-->
<jarWebSupport>
<groupId>org.apache.felix</groupId>
<artifactId>org.apache.felix.http.jetty</artifactId>
<version>2.2.1</version>
<!-- depends on OSGI frameowrk (startLevel=2) and is required
by felix.http.whiteboard (startLevel=4) -->
<startLevel>3</startLevel>
</jarWebSupport>
{code}
I have no idea why this uses the most current version. Especially while 2.2.1
is explicitly specified as version for
org.apache.felix:org.apache.felix.http.jetty in the parent pom [1]
There is not much I can do about this for 0.12.0 as one can not change
releases. However when you build your own custom launcher based on 0.12.0 just
add the explicit {{<version>2.2.1</version>}} and you should be fine.
One thing I will however do (for both 0.12.1-SNAPSHOT and 1.0.0-SNAPSHOT) is to
change all launcher pom.xml files to explicitly specify the version.
[1]
http://search.maven.org/#artifactdetails|org.apache.stanbol|stanbol-parent|4|pom
> stable version 0.12.0 does not compile correctly
> ------------------------------------------------
>
> Key: STANBOL-1402
> URL: https://issues.apache.org/jira/browse/STANBOL-1402
> Project: Stanbol
> Issue Type: Bug
> Components: Build
> Environment: Linux ubuntu 3.2.0
> Java(TM) SE Runtime Environment (build 1.7.0_72-b14)
> Apache Maven 3.0.5
> Reporter: marco salfi
> Labels: bundle, issue
> Attachments: error.log
>
>
> I downloaded the version from the site :
> http://archive.apache.org/dist/stanbol/apache-stanbol-0.12.0-source-release.tar.gz
> mvn clean install compiles correctly.
> I had to skip the geonames test because the geonames server does not allow
> the specified user anymore ! Maybe could be better to add the skiptest by
> default on the pom.
> when I execute the full launcher I've got a lot of BundleException errors,
> and it can't start. In many forum they call STANBOL-1356 issue, but even with
> svn co I can't solve it. I've tried to checkout different revisions after
> 1356 but without any luck.
> Can anyone help me ? I know that it is a pom issue, but can't find the
> correct pom setting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)