Hi,
The maven-jdeps-plugin uses this class with the integration-tests and to
verify these kind of violations. The plugin has a parameter called
failOnWarning to break the build when using a JDK Internal API.
So it is intended and can be considered as false positive.
Robert
Op Mon, 16 Nov
Sorry for a third email But it totally slipped my mind that Java 8 now
includes a Base64 equivalent:
https://docs.oracle.com/javase/8/docs/api/java/util/Base64.html
Cheers,
Paul
On Mon, Nov 16, 2015 at 11:39 AM, Paul Benedict
wrote:
> Typo. I meant Commons Codec.
>
>
> Cheers,
> Paul
>
> O
Typo. I meant Commons Codec.
Cheers,
Paul
On Mon, Nov 16, 2015 at 11:38 AM, Paul Benedict
wrote:
> But Commons Code has a Base64 equivalent. Why rely on the Sun version when
> you can use Apache's?
>
>
> Cheers,
> Paul
>
> On Mon, Nov 16, 2015 at 11:37 AM, Gary Gregory
> wrote:
>
>> Java 8 ha
But Commons Code has a Base64 equivalent. Why rely on the Sun version when
you can use Apache's?
Cheers,
Paul
On Mon, Nov 16, 2015 at 11:37 AM, Gary Gregory
wrote:
> Java 8 has a java.util.Base64 class so that one is easy.
>
> Gary
>
> On Mon, Nov 16, 2015 at 8:48 AM, Tibor Digana
> wrote:
>
Java 8 has a java.util.Base64 class so that one is easy.
Gary
On Mon, Nov 16, 2015 at 8:48 AM, Tibor Digana
wrote:
> Our plugins are dependent on internal Sun JDK packages.
> This is the list of plugins:Java classes and JDK classes.
> Whatever critical or non-critical, the JDK dependency appear
GitHub user argv-minus-one opened a pull request:
https://github.com/apache/maven-plugin-tools/pull/6
For Groovy/Scala Mojos: Allow Mojo documentation in annotations, too.
Currently, while most information about Mojos can appear in annotations
like `@Mojo` and `@Parameter`, three it
Our plugins are dependent on internal Sun JDK packages.
This is the list of plugins:Java classes and JDK classes.
Whatever critical or non-critical, the JDK dependency appears.
maven-jdeps-plugin:Base64Codec sun.misc.BASE64Decoder
maven-changes-plugin:ProjectJavamailMailSender
in lucene/testframework:renamed CheapBastard codec to Lucene54 to see if the
SPILoader would pick it up ..it didnteven when i replaced CheapBastard entry in
resources/META-INF/services/org.apache.lucene.codecs.Codeca quick refactor
NamedSPILoader.lookup(String name) to read
resources/META-INF/
As part of some side testing of my day job, I have developed a workflow
script to build and test Maven core... once I can get Workflow onto
builds.apache.org we can see to adapt this some more, but if anyone is
interested.
This flow will build on linux with JDK 7 and then run the integration tests
