d여기에서 Error “package android.support.v7.app does not exist” – package com sun image codec jpeg does not exist 주제에 대한 세부정보를 참조하세요
Error “package android.support.v7.app does not exist” ———————————————————————- First of all check if your project is using androidx or android support library. Check gradle.properties file: android.useAndroidX=true android.enableJetifier=true If it contains the above lines, it is using androidx with an old code from some old tutorial. In build.gradle (module:app) Use implementation ‘androidx.appcompat:appcompat:1.0.0’ Instead of compile ‘com.android.support:appcompat-v7:28.0.0’ Also in MainActivity.java : Use import androidx.appcompat.app.AppCompatActivity; instead of : import android.support.v7.app.AppCompatActivity;
package com sun image codec jpeg does not exist 주제에 대한 자세한 내용은 여기를 참조하세요.
I had this problem when compiling with JDK 7. Strange enough Eclipse d not show this error, only javac d. The answer can be found in this Stackoverflow …
Package com.sun.image.codec.jpeg does not exist – Katastros
Reason: Image processing JPEGCodec has been removed from Jdk1.7. Solution 1: This problem can be solved by configuring the maven-compiler-plugin plug-in.
static void saveImage(BufferedImage dstImage, String dstName) throws IOException { String formatName = dstName.substring(dstName.lastIndexOf(“.”) + 1); //FileOutputStream out = new FileOutputStream(dstName); //JPEGImageEncoder encoder = JPEGCodec. createJPEGEncoder(out); //encoder.encode(dstImage); ImageIO.write(dstImage,/*”GIF”*/formatName/* format desired */, new File(dstName)/* target */); }
Retrieved from[url]http://www.vktone.com/articles/com-sun-image-codec-jpeg-not-found.html[/url]Some old Java code compiled under JDK1.7 will report errors, such as This: The package com.sun.image.codec.jpeg does not exist.[javac] D:\work\mpa\hyjc2\src\hyjc\image\ImageUtil.java:87: Error: Cannot find symbol[javac] JPEGImageEncoder encoder = JPEGCodec.createJPEGEncoder(out);[javac] ^[javac] Symbol: Class JPEGImageEncoderbecause this JPEGImageEncoder is a private implementation of sun company.Generally appear in such a Java code segment:Should be changed to this Java code:This is no problem, because the unified ImageIO is used to read and write image format files, and there is no need to use the outdated implementation class JPEGImageEncoder class.Because many articles on the Internet talk about this issue [the package com.sun.image.codec.jpeg does not exist], they all talk about the issue of rt.jar, and they didn’t mention the idea, so I published it specifically, hope that Everyone is helpful.Note that the following classes are used when processing image formats in general.Written as a method://2013.05.04
206774 – [JDK 7] package com.sun.image.codec.jpeg does not exist
This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project’s instructions for reporting issues.
package com.sun.image.codec.jpeg does not exist · Issue #12 · aiinspur/blog
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Pick a username Email Address Password Sign up for GitHub
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gradle build package com sun. image. codec. JPEG does not exist, solution
This is because classpath Contains no sun Some of the company’s packages lead to .
jdk1.7 Start jdk Sold to oracle,sun Some of the company’s packages are not included in jdk in , Become private , The default is not to use , So the compilation failed .
What is it for? ,eclipse、IDEA Be able to compile through , And use it alone gradle perhaps maven no way ？
eclipse and IDEA stay run When , Default classpath Add a lot of jar package . for example IDEA Run a main Method , Combined with the -classpath Parameters ：
1、 Will report an error sun Package code removal , Use other api Instead of .（ recommend *****）
2、 take jre/lib/rt.jar Join in classpath in （ recommend ***）
3、 take jre/lib/rt.jar Join the rely on （ recommend **）
Join in classpath It’s a solution , But there is no guarantee that different environments can be implemented steadily , For example, special new jdk Or some custom jdk. Add dependency Library , For example, the of the project libs Directory , Also do not recommend , Packing will increase the volume .
Recommended replacement , Maintain program compatibility 、 reliability .
PS:
1、sun There are many different types of bags , It needs to be replaced in different ways , No discussion .
2、 The following build scripts are kotlin Script , namely build.gradle.kts ,xxx.gradle Basically applicable , But it needs a little modification .
3、 The following code does not add classpath But join bootstrapClasspath , This is because classpath It’s actually read-only ,
4、 The old version gradle May need to use classbootpath, The new version uses bootstrapClasspath
This article currently uses gradle by 6.1 edition . The latest official version .
[ERROR] COMPILATION ERROR :
[INFO] ————————————————————-
[ERROR] /home/ztzx/ztzx.service/src/main/java/com/telchina/ztzx/common/controller/UploadController2.java:[24,40] package com.sun.image.codec.jpeg does not exist
[ERROR] /home/ztzx/ztzx.service/src/main/java/com/telchina/ztzx/common/controller/UploadController2.java:[25,40] package com.sun.image.codec.jpeg does not exist
[ERROR] /home/ztzx/ztzx.service/src/main/java/com/telchina/ztzx/common/controller/UploadController.java:[25,32] package com.sun.image.codec.jpeg does not exist
[ERROR] /home/ztzx/ztzx.service/src/main/java/com/telchina/ztzx/common/controller/UploadController.java:[26,32] package com.sun.image.codec.jpeg does not exist
[INFO] 4 errors
[INFO] ————————————————————-
[INFO] ————————————————————————
[INFO] Reactor Summary:
[INFO]
[INFO] ztzx 1.0.0 ………………………………….. SUCCESS [ 0.007 s]
[INFO] ztzx.service ………………………………… FAILURE [02:11 min]
[INFO] ztzx.web 1.0.0 ………………………………. SKIPPED
[INFO] ————————————————————————
[INFO] BUILD FAILURE
[INFO] ————————————————————————
[INFO] Total time: 02:11 min
[INFO] Finished at: 2018-08-06T01:51:45Z
[INFO] ————————————————————————
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project ztzx.service: Compilation failure: Compilation failure:
[ERROR] /home/ztzx/ztzx.service/src/main/java/com/telchina/ztzx/common/controller/UploadController2.java:[24,40] package com.sun.image.codec.jpeg does not exist
[ERROR] /home/ztzx/ztzx.service/src/main/java/com/telchina/ztzx/common/controller/UploadController2.java:[25,40] package com.sun.image.codec.jpeg does not exist
[ERROR] /home/ztzx/ztzx.service/src/main/java/com/telchina/ztzx/common/controller/UploadController.java:[25,32] package com.sun.image.codec.jpeg does not exist
[ERROR] /home/ztzx/ztzx.service/src/main/java/com/telchina/ztzx/common/controller/UploadController.java:[26,32] package com.sun.image.codec.jpeg does not exist
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :ztzx.service
分析一
按照Java官方的解释,sun.image.codec这个package已经被deprecated，建议不要使用，看官方的解释： Why Developers Should Not Write Programs That Call ‘sun’ Packages The java.*, javax.* and org.* packages documented in the Java Platform Standard Edition API Specification make up the official, supported, public interface. If a Java program directly calls only API in these packages, it will operate on all Java-compatible platforms, regardless of the underlying OS platform. The sun.* packages are not part of the supported, public interface. A Java program that directly calls into sun.* packages is not guaranteed to work on all Java-compatible platforms. In fact, such a program is not guaranteed to work even in future versions on the same platform. Each company that implements the Java platform will do so in their own private way. The classes in sun.* are present in the JDK to support Oracle’s implementation of the Java platform: the sun.* classes are what make the Java platform classes work “under the covers” for Oracle’s JDK. These classes will not in general be present on another vendor’s Java platform. If your Java program asks for a class “sun.package.Foo” by name, it may fail with ClassNotFoundError, and you will have lost a major advantage of developing in Java. Technically, nothing prevents your program from calling into sun.* by name. From one release to another, these classes may be removed, or they may be moved from one package to another, and it’s fairly likely that their interface (method names and signatures) will change. (From Oracle’s point of view, since we are committed to maintaining the Java platform, we need to be able to change sun.* to refine and enhance the platform.) In this case, even if you are willing to run only on Oracle’s implementation, you run the risk of a new version of the implementation breaking your program. In general, writing java programs that rely on sun.* is risky: those classes are not portable, and are not supported
I have a Java program when I compile it I get the following error [javac] …\MyClass.java:33: package com.sun.image.codec.jpeg does not exist [javac] import com.sun.image.codec.jpeg.*; [javac] ^ what can I do ? What is the correct way of writing an image file now that the com.sun package is deprecated.
Why are you using classes in the package com.sun.image.codec.jpeg ? You are not supposed to use those classes directly: Why Developers Should Not Write Programs That Call ‘sun’ Packages. What does your program do? Does it just try to read or write a JPG image? That’s very easy with the ImageIO API. See this tutorial: Writing/Saving an Image. Addition – The package com.sun.image.codec.jpeg has been removed in Java 7 as mentioned in the Java SE 7 and JDK 7 Compatibility Guide. Synopsis: The Non-standard com.sun.image.codec.jpeg Package is Retired Description: The com.sun.image.codec.jpeg package was added in JDK 1.2 (Dec 1998) as a non-standard way of controlling the loading and saving of JPEG format image files. This package was never part of the platform specification and it has been removed from the Java SE 7 release. The Java Image I/O API was added to the JDK 1.4 release as a standard API and eliminated the need for the com.sun.image.codec.jpeg package.
I had this problem when compiling with JDK 7. Strange enough Eclipse did not show this error, only javac did. The answer can be found in this Stackoverflow answer: javac uses a special symbol table that does not include all Sun-proprietary classes, and suppliying -XDignore.symbol.file makes the problem go away. Of course, a much better solution is to rewrite the code without using the proprietary classes, but to support JDK 7 quickly, this option works.
采集自互联网，如有侵权请联系本人
[JDK-6527962] Retire the non-standard package com.sun.image.codec.jpeg
The package com.sun.image.codec.jpeg was added in JDK 1.2 (Dec 1998)as a non-standard way of controlling the loading and saving of JPEGformat image files.It has never been part of the platform specification and is not partof any compatibility test suite and so compatible Java implementationsare not required to include it.The documentation for it has always been buried under a separate’other API’ heading, clearly distinct from the Java platform APIspecification. The intention was to replace it with a standard API.In JDK 1.4 (FCS/GA 2001) the Java Image I/O API was added(see JSR-15 at http://jcp.org/en/jsr/detail?id=15) as a standard API.This resides in the package javax.imageio.It provides a standard mechanism for controlling the loading andsaving of sampled image formats and requires all compliant Java SEimplementations to support JPEG as per the Image I/O specification.In JDK 6 to encourage migration to Image I/O several things happened.1. All documentation of com.sun.image.codec.jpeg was removedalthough the classes are still present in *Sun* implementations- I can’t speak for others – and probably only direct Sun licenseesare likely to ship the API assuming they bother to do so.2. When compiling code using these classes using JDK 6 a warningis emitted :warning: com.sun.image.codec.jpeg.JPEGCodec is Sun proprietary API andmay be removed in a future releaseJPEGCodec.createJPEGDecoder(…);3. There were substantial performance improvements to Image I/Oincluding JPEG, and overall the performance is now very similarbetween the two APIs.So we think its time to retire com.sun.image.codec.jpeg so wecan focus on the single preferred standard API.However we are aware that applications do still use it, typicallybecause they were written to run on JDK versions prior to 1.4,There are several options, not all exclusive :1. Remove completely in JDK 7 – the most aggressive option.2. Warn in JDK 7 release notes that it will be removed completely inJDK8 – this is really just incremental to the existing compilationwarning3. Make further javac changes in JDK 7 so that the classes are notlocated when compiling. ie the compilation warning turns into an error.Again, with this option the classes *are* still available at runtime sothat code compiled with 1.6 or earlier will still find these classesand run on JDK 7 This preserves binary compatibility.4. Remove the classes completely in a release after JDK 7after a combination of notifications via release notesand compiler warnings/errors. Ideally this would thenhappen in JDK8Implementing 2+3+4 comes down to using JDK 7 to providea further period of grace to migrate and probably providesthe right balance between notice and compatibility (to thesenon-standard, unsupported APIs). Particularly since JDK 6already began this process.How long does this give people to migrate?Our historical run rate of releases is one every two years.JDK 1.2 – Dec 1998…JDK 6 Nov 2006Management may try different models and so forth but I thinkthat’s a good enough estimate which predictsJDK7 – late 2008JDK8 – late 2010
[Maven]package com.sun.image.codec.jpeg does not exist
sym 接下來 workspace lock nis program uic edit 問題
—————————————————————–
原創博文，如需轉載請註明出處！
博主：疲憊的豆豆
鏈接：http://www.cnblogs.com/dzblog/p/6971245.html
—————————————————————-
環境
Maven:3.0.5
Java:1.8.0_45
OS:Linux
問題
拿到一個java項目，想編譯一下，報了如下錯誤：
[INFO] ————————————————————- [ERROR] COMPILATION ERROR : [INFO] ————————————————————- [ERROR] /var/lib/jenkins/jobs/sample_xxx_pipeline/workspace/src/test/java/com/xxx/sxxxx/ib/pdf/PdfServiceTest.java:[ 6 , 31 ] error: package com.sun.image.codec.jpeg does not exist [ERROR] /var/lib/jenkins/jobs/sample_xxx_pipeline/workspace/src/test/java/com/xxx/sxxxx/ib/pdf/PdfServiceTest.java:[ 7 , 31 ] error: package com.sun.image.codec.jpeg does not exist [INFO] 2 errors [INFO] ————————————————————- [INFO] ———————————————————————— [INFO] BUILD FAILURE [INFO] ———————————————————————— [INFO] Total time : 12 .361s [INFO] Finished at: Thu Jun 08 19 : 16 : 04 CST 2017 [INFO] Final Memory: 75M / 1614M [INFO] ————————————————————————
出錯原因（來自stack overflow）：
Why are you using classes in the package com.sun.image.codec.jpeg? You are not supposed to use those classes directly: Why Developers Should Not Write Programs That Call ‘sun‘ Packages.
What does your program do? Does it just try to read or write a JPG image? That‘s very easy with the ImageIO API. See this tutorial: Writing/Saving an Image.
Addition – The package com.sun.image.codec.jpeg has been removed in Java 7 as mentioned in the Java SE 7 and JDK 7 Compatibility Guide.
Synopsis: The Non-standard com.sun.image.codec.jpeg Package is Retired
Description: The com.sun.image.codec.jpeg package was added in JDK 1.2 (Dec 1998) as a non-standard way of controlling the loading and saving of JPEG format image files. This package was never part of the platform specification and it has been removed from the Java SE 7 release. The Java Image I/O API was added to the JDK 1.4 release as a standard API and eliminated the need for the com.sun.image.codec.jpeg package.
The java.*, javax.* and org.* packages documented in the Java Platform Standard Edition API Specification make up the official, supported, public interface.
If a Java program directly calls only API in these packages, it will operate on all Java-compatible platforms, regardless of the underlying OS platform.
The sun.* packages are not part of the supported, public interface.
A Java program that directly calls into sun.* packages is not guaranteed to work on all Java-compatible platforms. In fact, such a program is not guaranteed to work even in future versions on the same platform.
Each company that implements the Java platform will do so in their own private way. The classes in sun.* are present in the JDK to support Oracle‘s implementation of the Java platform: the sun.* classes are what make the Java platform classes work “under the covers” for Oracle‘s JDK. These classes will not in general be present on another vendor‘s Java platform. If your Java program asks for a class “sun.package.Foo” by name, it may fail with ClassNotFoundError, and you will have lost a major advantage of developing in Java.
Technically, nothing prevents your program from calling into sun.* by name. From one release to another, these classes may be removed, or they may be moved from one package to another, and it‘s fairly likely that their interface (method names and signatures) will change. (From Oracle‘s point of view, since we are committed to maintaining the Java platform, we need to be able to change sun.* to refine and enhance the platform.) In this case, even if you are willing to run only on Oracle‘s implementation, you run the risk of a new version of the implementation breaking your program.
In general, writing java programs that rely on sun.* is risky: those classes are not portable, and are not supported.
I had this problem when compiling with JDK 7. Strange enough Eclipse did not show this error, only javac did. The answer can be found in this Stackoverflow answer: javac uses a special symbol table that does not include all Sun-proprietary classes, and suppliying -XDignore.symbol.file makes the problem go away.
Of course, a much better solution is to rewrite the code without using the proprietary classes, but to support JDK 7 quickly, this option works.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.
