You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2011/08/01 22:04:28 UTC
Jenkins build failure due to OSGi bundle plugin needing Java 1.6
We currently set our build processes to use Java 5. This insures we don't
accidentally "depend" on a method which is only in Java 6.
The Felix OSGi bundle plugin (version 2.3.5) requires Java 6 - it uses a String
class getBytes(Charset....) method, which was added in Java 6.
We are using version 2.3.5 because it eliminates various spurious warnings, as
compared to earlier levels.
Not sure how to work around this - maybe there's a way to run "forked" in a
different JVM.
-Marshall
Re: Jenkins build failure due to OSGi bundle plugin needing Java
1.6
Posted by Marshall Schor <ms...@schor.com>.
2.3.4 worked.
I changed the build on Jenkins to use 1.6 - that worked too.
I'll commit the change for 2.3.4 version of maven-bundle-plugin, and put Jenkins
back to 1.5.
I noticed that running mvn install on single projects is broken in the addons -
due to the need to release an update to the uima-build-resources project.
I'll post a release for that soon (maybe Wednesday).
-Marshall
On 8/1/2011 4:31 PM, Marshall Schor wrote:
> Got a reply right away on the Felix users list to the q: if Java 6 requirement
> was intentional:
>
> not intentional - https://issues.apache.org/jira/browse/FELIX-3037 - happened when we picked up the new version of bnd
>
> if you don't need any of the changes in 2.3.5 you can lock down the plugin version to 2.3.4, which does work with Java 5
>
>
>
> I'll try 2.3.4
>
> -Marshall
>
> On 8/1/2011 4:04 PM, Marshall Schor wrote:
>> We currently set our build processes to use Java 5. This insures we don't
>> accidentally "depend" on a method which is only in Java 6.
>>
>> The Felix OSGi bundle plugin (version 2.3.5) requires Java 6 - it uses a String
>> class getBytes(Charset....) method, which was added in Java 6.
>>
>> We are using version 2.3.5 because it eliminates various spurious warnings, as
>> compared to earlier levels.
>>
>> Not sure how to work around this - maybe there's a way to run "forked" in a
>> different JVM.
>>
>> -Marshall
>>
Re: Jenkins build failure due to OSGi bundle plugin needing Java
1.6
Posted by Marshall Schor <ms...@schor.com>.
Got a reply right away on the Felix users list to the q: if Java 6 requirement
was intentional:
not intentional - https://issues.apache.org/jira/browse/FELIX-3037 - happened when we picked up the new version of bnd
if you don't need any of the changes in 2.3.5 you can lock down the plugin version to 2.3.4, which does work with Java 5
I'll try 2.3.4
-Marshall
On 8/1/2011 4:04 PM, Marshall Schor wrote:
> We currently set our build processes to use Java 5. This insures we don't
> accidentally "depend" on a method which is only in Java 6.
>
> The Felix OSGi bundle plugin (version 2.3.5) requires Java 6 - it uses a String
> class getBytes(Charset....) method, which was added in Java 6.
>
> We are using version 2.3.5 because it eliminates various spurious warnings, as
> compared to earlier levels.
>
> Not sure how to work around this - maybe there's a way to run "forked" in a
> different JVM.
>
> -Marshall
>