Bug 1255375 - jide-oss 3.6.10 is available
jide-oss 3.6.10 is available
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: jide-oss (Show other bugs)
22
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Hicham HAOUARI
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-20 08:08 EDT by Neal Gompa
Modified: 2016-07-19 13:35 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-19 13:35:46 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Neal Gompa 2015-08-20 08:08:10 EDT
Latest upstream release: 3.6.10

Current version/release in Fedora 23 branch/rawhide: jide-oss-2.7.6-12.1340svn.fc23

New home: https://github.com/jidesoft/jide-oss

Release URL: https://github.com/jidesoft/jide-oss/releases/tag/3.6.10

jide-oss 3.6.10 is a massive upgrade from the one in 2009 that we currently have. There's a ton of improvements over the one we have now. Most importantly, it switched from Ant to Maven and provides pom.xml data that allows programs using XMvn to be able to pull it in properly.

Please upgrade jide-oss.
Comment 1 Fedora End Of Life 2016-07-19 13:35:46 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.