maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <stephen.alan.conno...@gmail.com>
Subject Re: [jira] Michael Osipov mentioned you (JIRA)
Date Sun, 17 Apr 2016 08:29:54 GMT
On Sunday 17 April 2016, Stephen Connolly <stephen.alan.connolly@gmail.com>
wrote:

> So the following is not of concern to the maven project - as we do not
> ship a JRE - but anyone who does ship a JRE cannot do so and ship the
> annotations *claimed* to be JSR-305


Now it could very easily become our problem,

For example if we were to take the Docker images for maven that Carlos has
been maintaining and bring them in-project so that they are being released
by the maven project...

Those images bundle a JRE, so if the Maven Project were publishing those
images we could not include the jar known as JSR-305 in the docker
image..., I'm not sure if the annotations retained in bytecode counts

And I haven't even started in the poor licensing of some classes in that
jar... At least some have source headers in Cat 2 or Cat X (I'd need to
double check which... I think Cat X but it might not be that bad)


>
> This is because the JRE binary license specifically contains a clause
> mandating that you do not add or redefine classes in the java, javax,
> com.sun or sun package namespaces.
>
> The only way to add such classes - if you are distributing a JRE - is if
> they are *published* by a JSR under the JCP process.
>
> JSR-305 has not published any RI on its official page *and* the only
> published information there references NonNull *not* Nonnull (note the case
> change) which means that on the basis of the JSR-305 *official published
> information* the JAR doing the rounds cannot even be inferred as "official"
>
> In light of this, I think we need to put pressure on the findbugs project
> to EITHER reboot JSR-305 and get the annotations published OR refactor them
> back into the findbugs package namespace and remove the depredations there.
>
> I do not think we should encourage use of JSR-305 until the situation is
> resolved
>
> -Stephen
>
> On Sunday 17 April 2016, Michael Osipov (JIRA) <jira@apache.org
> <javascript:_e(%7B%7D,'cvml','jira@apache.org');>> wrote:
>
>>
>>      [
>> https://issues.apache.org/jira/browse/MPOM-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Michael Osipov mentioned you on MPOM-40
>> -------------------------------
>>
>> [~mavendevlist], unfortunately JSR 305 has virtually been ceased and
>> Google's reference implementation is offline. Do you want to drop any
>> effect on this topic and close this issue?
>>
>> >                 Key: MPOM-40
>>
>> >         View Online: https://issues.apache.org/jira/browse/MPOM-40
>> >         Add Comment:
>> https://issues.apache.org/jira/browse/MPOM-40#add-comment
>>
>> Hint: You can mention someone in an issue description or comment by
>> typing  "@" in front of their username.
>>
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.4#6332)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> --
> Sent from my phone
>


-- 
Sent from my phone

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message