Package Details: oracle-sqldeveloper 23.1.1.345.2114-1

Git Clone URL: https://aur.archlinux.org/oracle-sqldeveloper.git (read-only, click to copy)
Package Base: oracle-sqldeveloper
Description: A graphical tool for database development
Upstream URL: https://www.oracle.com/tools/downloads/sqldev-downloads.html
Licenses: custom:OTN
Submitter: ilikenwf
Maintainer: frealgagu (malek)
Last Packager: malek
Votes: 37
Popularity: 0.000088
First Submitted: 2015-09-22 06:40 (UTC)
Last Updated: 2023-12-16 19:09 (UTC)

Dependencies (5)

Required by (0)

Sources (5)

Pinned Comments

frealgagu commented on 2020-03-11 04:33 (UTC)

To build the package you need to manually download the no-jre archive from Oracle's site[1] and place it in the same directory with the PKGBUILD[2] and then run makepkg.

[1] https://www.oracle.com/tools/downloads/sqldev-downloads.html, you need "Other platforms"

[2] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=oracle-sqldeveloper

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

barkley128 commented on 2017-02-16 15:45 (UTC) (edited on 2017-02-16 15:48 (UTC) by barkley128)

If you're having JDK issues, make sure /usr/lib/jvm/default points to Oracle proprietary JDK installation. (e.g. "yaourt -S jdk") You can see what you have installed with: # archlinux-java status and change the default with: # archlinux-java set <JAVA_ENV_NAME> Also to save this in SQL Developer's config launch it with: cd /opt/oracle-sqldeveloper/ ./sqldeveloper.sh It will ask for the JDK location, /usr/lib/jvm/default should do. I imagine setting the JAVA_HOME does this automatically, I just put the path manually. Probably putting /usr/lib/jvm/java-8-jdk/, without changing the default path works too.

pezzacolori commented on 2017-02-03 15:36 (UTC)

I get an error at startup: Error: SQL Developer can't recognize the JDK version I also set JAVA_HOME to /usr/lib/jvm/default but did not help. My java installations are : $ archlinux-java status Available Java environments: java-7-openjdk java-8-openjdk (default)

ilikenwf commented on 2016-11-22 07:31 (UTC)

I can't replicate your issue: md5sum oracle-sqldeveloper-4.1.5.21.78-1-any.pkg.tar 85dc6a343748a5b819e5240a49963b4f oracle-sqldeveloper-4.1.5.21.78-1-any.pkg.tar

hecsa commented on 2016-11-15 01:49 (UTC)

Even downloading it by hand, the installer cannot know that the package was already downloaded from Oracle: ==> Building and installing package ==> Making package: oracle-sqldeveloper 4.1.5.21.78-1 (lun nov 14 22:47:05 ART 2016) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading sqldeveloper-4.1.5.21.78-no-jre.zip... The source file for this package needs to be downloaded manually, since it requires a login and is not redistributable.;/usr/bin/echo Please visit http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html.; exit 1; manual://sqldeveloper-4.1.5.21.78-no-jre.zip -> Found oracle-sqldeveloper.desktop -> Found oracle-sqldeveloper.sh -> Found LICENSE -> Found java_home.patch ==> Validating source files with md5sums... sqldeveloper-4.1.5.21.78-no-jre.zip ... NOT FOUND oracle-sqldeveloper.desktop ... Passed oracle-sqldeveloper.sh ... Passed LICENSE ... Passed java_home.patch ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build oracle-sqldeveloper. ==> Restart building oracle-sqldeveloper ? [y/N] ==> -------------------------------------------- ==> n [hecsa@sdf1 ~]$ [hecsa@sdf1 ~]$ [hecsa@sdf1 ~]$ ls -las sqldeveloper-4.1.5.21.78-no-jre.zip 341924 -rw-r--r-- 1 hecsa hecsa 349775471 nov 14 22:38 sqldeveloper-4.1.5.21.78-no-jre.zip Any clues? Thanks, and best regards, HeCSa.

ilikenwf commented on 2016-09-28 05:39 (UTC)

Done. Also, I suggest just exporting JAVA_HOME in your zshrc or bashrc for ease with this package.

xduugu commented on 2016-05-18 12:37 (UTC)

The install file can be removed, since we now have a alpm-hook for invoking update-desktop-database.

ilikenwf commented on 2016-01-15 16:13 (UTC)

I'll try to remember to add a message about that at the end of the build next version.

s1ngul4r17y commented on 2016-01-15 11:44 (UTC)

A small detail - first start should be from shell in order to provide path to JDK.

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »