To reply further, got access to see what the pom.xml was for the plasticscm
plugin. Does look like its the old parent version that will be stopping
Java 7 compatibility. I'm not a Maven whizz but here's what I recently
changed the Gradle plugin's parent in the pom to which works nicely:
<parent>
<groupId>org.jenkins-ci.plugins</groupId>
<artifactId>plugin</artifactId>
<version>1.427</version>
</parent>
Richard.
On Thu, Aug 22, 2013 at 7:07 AM, Richard Bywater <[email protected]> wrote:
> I think you'd be best making the plugin Java 7 compatible especially as
> Java 6 is now EOL.
>
> I don't have access to the code right now but I could be a simple matter
> of the parent Pom version being too low as some older Poms did rely on
> com.sun classes that aren't in Openjdk/Java 7.
>
> Richard.
>
>
> On Thursday, August 22, 2013, Carlos Alba wrote:
>
>> Hi,
>>
>> I´ve performed a few changes in a Jenkins plugin (
>> https://github.com/jenkinsci/plasticscm-plugin), but when I perform a
>> pull request to the repo, a build is automatically done by BuildHive
>> system. It fails because BuildHive systems uses Java 7 by default and the
>> plugin needs Java 6 to be built.
>>
>> How can I configure BuildHive to use Java 6? ****
>>
>> In case it´s not possible, How can I disable automatic BuildHive system?
>> I can build locally the plugin and then upload it to Jenkins web page.
>>
>> Regards,****
>>
>> Carlos****
>>
>> ** **
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
