[
https://issues.apache.org/jira/browse/STANBOL-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler resolved STANBOL-1402.
------------------------------------------
Resolution: Done
Fix Version/s: 0.12.1
1.0.0
Marking this as "Done" because
* the build of 0.12.0 is now broken (see above comments for details). Nothing
one can do about it
* changed both the 0.12 releasing branch as well as the trunk in a way that
this will not happen to future releases.
Workaround for 0.12.0:
Explicitly adding the {{<version>2.2.1</version>}} to the
{{org.apache.felix:org.apache.felix.http.jetty}} of the {{<jarWebSupport>}}
element of runable jar launchers.
Here is the according code snippet.
{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}
> 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
> Assignee: Rupert Westenthaler
> Labels: bundle, issue
> Fix For: 1.0.0, 0.12.1
>
> 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)
