Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

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

RFP - Oracle SQL Developer #383

Closed
PacMo66 opened this issue Jul 24, 2018 · 16 comments
Closed

RFP - Oracle SQL Developer #383

PacMo66 opened this issue Jul 24, 2018 · 16 comments

Comments

@PacMo66
Copy link

PacMo66 commented Jul 24, 2018

Database Development tool
common in enterprise enviroment
used every day by my team

Oracle SQL Developer is a free and fully supported graphical tool for database development. With SQL Developer, you can browse database objects, run SQL statements and SQL scripts, and edit and debug PL/SQL statements. You can also run any number of provided reports, as well as create and save your own. SQL Developer enhances productivity and simplifies your database development tasks.

latest available via http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html

@Rhonda-Rathburn
Copy link

please do!
:D

@gsmitheidw
Copy link

Tempted to bite but this one will be trick to do because download requires clicking boxes for licence and then logging in. Hosting the package within the nupkg would be possible technically but it's Oracle, so legally that would want to be very clearly defined and agreed in writing.

@AdmiringWorm
Copy link
Member

Well, since the license doesn't explicitly allow distribution of the installer, it certainly can't be embedded without permission from Oracle.

If there is a requirement to click the accept license boxes, this certainly complicates things. But maybe it could be worked around similiar in how it's done with the jre and jdk packages.

Anyhow, I'll also mark this with an Blocked Upstream label, at least until we know for sure.

@wget wget self-assigned this Sep 1, 2018
@karolzlot
Copy link

"requirement to click the accept license boxes"
this is doable or bypassable

But in next step we need some account credentials

Is it okay to put these dummy account credentials into nupkg?

@gsmitheidw
Copy link

gsmitheidw commented Dec 21, 2018

I think Oracle may dislike that, if they start seeing floods of downloads from one account they may block it or even worse, they might call the legal department to send cease and desist letters. They might even put a captcha to weed out scripts.

I think it would be more successful if the nupkg could pass parameters for specific oracle credentials added per user and submit them through the site. It would not be an anonymous download but at least it would be silent.

@ChargingBulle
Copy link

ChargingBulle commented Jan 28, 2019

This StackExchange describes a way to download JDK without sign-up:

curl -L -C - -b "oraclelicense=accept-securebackup-cookie" -O http://download.oracle.com/otn-pub/java/jdk/11.0.1+13/90cf5d8f270a4347a95050320eef3fb7/jdk-11.0.1_linux-x64_bin.tar.gz

maybe it's applicable for this package too?

@pauby
Copy link
Member

pauby commented Feb 19, 2019

Can we progress this package and remove the 'Blocked Upstream' label given the comment by @JonasDralle ?

@AdmiringWorm
Copy link
Member

@pauby yeah, we probably can do that

@wcarson
Copy link

wcarson commented Feb 26, 2019

I'm new to chocolatey but would be interested in taking a shot at this one. I've played around with this a little bit, and it seems doable using a technique similar to what @JonasDralle proposed to get around having to click the license agreement. The issue is that at some point you have to have a (free) Oracle account to download the file. Is it acceptable to prompt for credentials during a chocolatey install (Get-Credential or similar) and/or allow the credentials to be passed in as argument to the install?

@pauby
Copy link
Member

pauby commented Feb 27, 2019

@wcarson the install should be silent. If it is absolutely required you could make sure the details are passed as package parameters.

@AdmiringWorm
Copy link
Member

the install should be silent.

Or at least unattended (silent would mean nothing is shown during install)

@pauby
Copy link
Member

pauby commented Feb 27, 2019

Unattended is a better description :)

@wcarson
Copy link

wcarson commented Feb 28, 2019

Hi. I pushed an initial version for review. To handle the Oracle Account requirement, the package requires that the credentials be specified as package params: "'/Username:{username} /Password:{password}'". The package is attached if anyone is feeling brave. (It's been tested locally on Win10 and on the Chocolatey Testing Environment VM)

[removed attachment - package is now available here: https://chocolatey.org/packages/oracle-sql-developer]

@jpluimers
Copy link

jpluimers commented May 22, 2019

For Oracle SQL Developer 19.1.0, I made a commit in a fresh branch at jpluimers/chocolatey-packages@796b1e4

Detailled change description and process is in the commit.

Two questions:

I am not sure for how long I will be using Oracle SQL Developer, but it is likely not for years, so I might not be able to provide updates for future Oracle SQL Developer versions.

(Edit: I'm really new to chocolatey, but not new to software development; I read through the Chocolatey Testing Environment VM that @wcarson mentioned, but doing a deep dive into vagrant is too much for me right now, this apart from the verifier service link in it not working at all since december 2017 makes me feel a lot of it is outdated with a steep learning curve ahead)

@pauby
Copy link
Member

pauby commented May 23, 2019

What's the easiest way to test if I did not goof up that commit?

Run the package through the Chocolatey Test Environment. However I noted your comments about it - the Vagrant environment is simply a bare, unpatched (for a reason) Windows Server 2012 R2 server. So if you can spin one of those up you can test your package on there. Ordinarily we woudl recommend not testing on your machine as you may not be able to pick up all the dependencies required. However as this is a change to an existing package, as long as you are mindful of it, you should be able to get away with testing it there.

Should I make a pull request to wcarson/chocolatey-packages in order to get it at chocolatey.org/packages/oracle-sql-developer or is there another way?

If you're confident the code / package works then contacting the maintainer and submitting the PR would be a good way to start. This is the reason why we ask maintainers to provide a <packageSourceUrl> in their .nuspec file as it allows this process to happen.

You might want to reach out to Gitter if you need more help.

@ChargingBulle
Copy link

Hidden dependency: Internet Explorer needs to be initialized

The response content cannot be parsed because the Internet Explorer engine is not available, or Internet Explorer's first-launch configuration is not complete. Specify the UseBasicParsing parameter and try again.
log

Can be solved by opening IE and clicking a few boxes.

The far more pressing issue is that the package does not work on 64 Bit machines:

ERROR: This package does not support 64 bit architecture.
log

The log contains credentials which can be used by anyone for testing purposes:
USER [email protected]
PASS FZEOAO8ytZEMsrgDgK4s+4M0xADoy8y

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests