facebook

MyEclipse upgrade

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #625966 Reply

    CS Tan
    Participant

    Hi,

    We would like to ask what version of MyEclipse should we install if we will be using
    – IBM WAS 8.5.5.15 BASE
    – JDK 1.8?

    And we need this version to support CVS and build automation tools as well (eg. Jenkins)
    Please provide us the link to download the installer as well.

    We are currently using:
    – MyEclipse 10
    – IBM WAS 8.0
    – JDK 1.6

    #626072 Reply

    Brian Fernandes
    Moderator

    I would normally recommend MyEclipse 2019.4, but we have some issues that are specific to WAS 8.5, the fixes will be released in the next MyEclipse update. Until then, you can use MyEclipse 2017, you can find the download links on our download page here: https://www.genuitec.com/products/myeclipse/download/

    To be clear on the update process, you should update to a MyEclipse 2019 build when the fix is released, but that will require a separate install of MyEclipse (you will not be able to update the 2017 installs). Once you are on the 2019 build, you will be able to update the Eclipse instance in place going forward (no separate installs required).

    Please let us know if you have any further questions.

    #626187 Reply

    CS Tan
    Participant

    Hi,

    When will be the fixes be available for MyEclipse 2019?
    Can I still use WAS 8.5 using MyEclipse 2017?

    #626316 Reply

    Brian Fernandes
    Moderator

    We are actively working on the next MyEclipse release, and it is targeted to be out within the next 6-8 weeks. As always, we will strive to get it out sooner. Part of this release includes removing the CI variation and having all releases going forward have Stable quality.

    And yes, you can still use WAS 8.5 in MyEclipse 2017.

    #626806 Reply

    CS Tan
    Participant

    Hi –

    I have installed MyEclipse 2017 v2 and checked out our application via CVS. But I am encountering a couple of issues before I can even start our application.

    1.) Upon starting the WAS on eclipse,I am always encountering an error that the port is already in use, even though there’s no IBM services running. As per checking netstat, I found out that the application using the port number(s) required is the myeclipse itself. So, as a work-around, I kill the taskID of myeclipse, then once I re-open myeclipse, I can start the application.

    2.) I cannot see the “OK” button after I update the SHARED_LIB reference on WAS admin console.

    Attachments:
    You must be logged in to view attached files.
    #626836 Reply

    support-swapna
    Moderator

    Hi,

    Thank you for the screenshots.

    Regarding the port in use error, can you please clarify if Websphere server is registered as a service? Those ports are used only for Websphere by MyEclipse.

    Please share with us the workspace error log file which is located at workspace dir/.metadata/.log (rename the extension to .txt and attach it) to help us get full details of the errors logged.

    We do not make any changes to the WAS Admin Console UI. I do not see the OK button either in the Shared library references section for a new project with or without shared libraries added. Looks like a UI issue with WAS 8.5.5.

    –Swapna
    Genuitec Support

    #697268 Reply

    darshan@123
    Participant

    please resolve this error i am getting this error while updating MyEclipse to 2021 version to 2022 version

    please solve this error

    An error occurred while collecting items to be installed
    — error: session context was:(profile=com.genuitec.delivery.package.profile.2915-Enr-0574, phase=com.genuitec.pulse.client.deliverypackage.runtime.p2.DeliveryCollect, operand=, action=).
    — Problems downloading artifact: osgi.bundle,org.springsource.ide.eclipse.commons.frameworks.core,4.18.0.202303131439.
    —- error: Error reading signed content:C:\Users\INGROI~1\AppData\Local\Temp\signatureFile9581928637623344309.jar
    —- java.security.NoSuchAlgorithmException: An error occurred while processing the signatures for the file: C:\Users\INGROI~1\AppData\Local\Temp\signatureFile9581928637623344309.jar
    at org.eclipse.osgi.internal.signedcontent.SignedBundleHook.getSignedContent(SignedBundleHook.java:231)
    at org.eclipse.equinox.internal.p2.artifact.repository.SignatureVerifier.verifyContent(SignatureVerifier.java:84)
    at org.eclipse.equinox.internal.p2.artifact.repository.SignatureVerifier.verify(SignatureVerifier.java:66)
    at org.eclipse.equinox.internal.p2.artifact.repository.SignatureVerifier.close(SignatureVerifier.java:115)
    at org.eclipse.equinox.internal.provisional.p2.artifact.repository.processing.ProcessingStep.close(ProcessingStep.java:92)
    at org.eclipse.equinox.internal.p2.artifact.processors.checksum.MessageDigestProcessingStep.close(MessageDigestProcessingStep.java:58)
    at org.eclipse.equinox.internal.provisional.p2.artifact.repository.processing.ProcessingStep.close(ProcessingStep.java:92)
    at org.eclipse.equinox.internal.p2.artifact.processors.checksum.MessageDigestProcessingStep.close(MessageDigestProcessingStep.java:58)
    at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.reportStatus(SimpleArtifactRepository.java:1253)
    at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:646)
    at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:777)
    at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.getArtifact(MirrorRequest.java:319)
    at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:289)
    at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:225)
    at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:155)
    at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:760)
    at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifacts(SimpleArtifactRepository.java:837)
    at com.genuitec.pulse.client.deliverypackage.runtime.download.DeliveryDownloadManager$DownloadWork.perform(Unknown Source)
    at com.genuitec.pulse.client.deliverypackage.runtime.download.DeliveryDownloadManager$DownloadJob.run(Unknown Source)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
    Caused by: java.security.NoSuchAlgorithmException: No algorithm found for 1.2.840.113549.1.1.12
    at org.eclipse.osgi.internal.signedcontent.PKCS7Processor.findEncryption(PKCS7Processor.java:95)
    at org.eclipse.osgi.internal.signedcontent.PKCS7Processor.processSignerInfos(PKCS7Processor.java:364)
    at org.eclipse.osgi.internal.signedcontent.PKCS7Processor.<init>(PKCS7Processor.java:172)
    at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.processSigner(SignatureBlockProcessor.java:109)
    at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.process(SignatureBlockProcessor.java:76)
    at org.eclipse.osgi.internal.signedcontent.SignedBundleFile.initializeSignedContent(SignedBundleFile.java:56)
    at org.eclipse.osgi.internal.signedcontent.SignedBundleHook.getSignedContent(SignedBundleHook.java:223)
    … 19 more
    — Problems downloading artifact: osgi.bundle,com.genuitec.eclipsecolortheme.api,1.11.0.202307031446.
    —- error: Error reading signed content:C:\Users\INGROI~1\AppData\Local\Temp\signatureFile16104183071632618137.jar
    —- java.security.NoSuchAlgorithmException: An error occurred while processing the signatures for the file: C:\Users\INGROI~1\AppData\Local\Temp\signatureFile16104183071632618137.jar
    at org.eclipse.osgi.internal.signedcontent.SignedBundleHook.getSignedContent(SignedBundleHook.java:231)
    at org.eclipse.equinox.internal.p2.artifact.repository.SignatureVerifier.verifyContent(SignatureVerifier.java:84)
    at org.eclipse.equinox.internal.p2.artifact.repository.SignatureVerifier.verify(SignatureVerifier.java:66)
    at org.eclipse.equinox.internal.p2.artifact.repository.SignatureVerifier.close(SignatureVerifier.java:115)
    at org.eclipse.equinox.internal.provisional.p2.artifact.repository.processing.ProcessingStep.close(ProcessingStep.java:92)
    at org.eclipse.equinox.internal.p2.artifact.processors.checksum.MessageDigestProcessingStep.close(MessageDigestProcessingStep.java:58)
    at org.eclipse.equinox.internal.provisional.p2.artifact.repository.processing.ProcessingStep.close(ProcessingStep.java:92)
    at org.eclipse.equinox.internal.p2.artifact.processors.checksum.MessageDigestProcessingStep.close(MessageDigestProcessingStep.java:58)
    at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.reportStatus(SimpleArtifactRepository.java:1253)
    at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:646)
    at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:777)
    at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.getArtifact(MirrorRequest.java:319)
    at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:289)
    at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:225)
    at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:155)
    at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:760)
    at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifacts(SimpleArtifactRepository.java:837)
    at com.genuitec.pulse.client.deliverypackage.runtime.download.DeliveryDownloadManager$DownloadWork.perform(Unknown Source)
    at com.genuitec.pulse.client.deliverypackage.runtime.download.DeliveryDownloadManager$DownloadJob.run(Unknown Source)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
    Caused by: java.security.NoSuchAlgorithmException: No algorithm found for 1.2.840.113549.1.1.11
    at org.eclipse.osgi.internal.signedcontent.PKCS7Processor.findEncryption(PKCS7Processor.java:95)
    at org.eclipse.osgi.internal.signedcontent.PKCS7Processor.processSignerInfos(PKCS7Processor.java:364)
    at org.eclipse.osgi.internal.signedcontent.PKCS7Processor.<init>(PKCS7Processor.java:172)
    at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.processSigner(SignatureBlockProcessor.java:109)
    at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.process(SignatureBlockProcessor.java:76)
    at org.eclipse.osgi.internal.signedcontent.SignedBundleFile.initializeSignedContent(SignedBundleFile.java:56)
    at org.eclipse.osgi.internal.signedcontent.SignedBundleHook.getSignedContent(SignedBundleHook.java:223)
    … 19 more
    — Problems downloading artifact: osgi.bundle,com.genuitec.eclipse.webicons,1.11.0.202307031446.
    —- error: Error reading signed content:C:\Users\INGROI~1\AppData\Local\Temp\signatureFile5699555905429911655.jar

    • This reply was modified 9 months, 2 weeks ago by darshan@123.
    • This reply was modified 9 months, 2 weeks ago by darshan@123.
    Attachments:
    You must be logged in to view attached files.
    #697281 Reply

    Brian Fernandes
    Moderator

    Darshan,

    I believe you’re looking to update to 2023 and not 2022? Do see this post for details: https://www.genuitec.com/forums/topic/myeclipse-update-to-version-2023-1-1-fails/#post-697208

Viewing 8 posts - 1 through 8 (of 8 total)
Reply To: MyEclipse upgrade

You must be logged in to post in the forum log in