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

New ant target for installing JNA artifacts in local m2-repository #644

Conversation

SevenOf9Sleeper
Copy link
Contributor

I have missed a simple way to activate my recently built jna artifacts so I can use them in other maven projects. So I would appreciate it to add an ant target for doing so after the "dist" build

@@ -1176,6 +1176,24 @@ osname=macosx;processor=x86;processor=x86-64;processor=ppc
</subant>
</target>

<target name="deploy-local" depends="dist" description="deploy snapshot version to local repository">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe change the target name to install-local, and description: install snapshot ..... The maven term for this action is install, so I think this change would be less confusing.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest target name "install" (matches maven goal "install:install", which installs artifacts into the local repository, the installation into a remote repository is "deploy:deploy").

And for the description: "Install jna and jna-platform artifacts into local maven repository". There is nothing preventing the user to run install on a non-snapshot build.

@matthiasblaesing
Copy link
Member

Apart from the nitpick I like this!

@SevenOf9Sleeper
Copy link
Contributor Author

I have changed name and description. You are right: "install" is more suitable.

@bhamail
Copy link
Contributor

bhamail commented Apr 26, 2016

Looks good. Could you also add a short blurb to the CHANGES.md file?

On a separate, but related note, some work has begun to create a "maven" build. See the files in the "parent" folder for details. It's just the "native" bits right now.

@matthiasblaesing matthiasblaesing merged commit 0db246e into java-native-access:master Apr 29, 2016
@matthiasblaesing
Copy link
Member

Build works correctly on linux and windows, with spaces in path and without. Thanks! 👍

mstyura pushed a commit to mstyura/jna that referenced this pull request Sep 9, 2024
…a-native-access#644)

Motivation:

We did fire the SniCompletionEvent only once we were done with the
handshake which is not really the correct time to do this. We should
fire the event as soon as we were able to process the client hello and
selected the hostname.

Modifications:

- Fire the event as soon as we select the hostname

Result:

Fire the event at the correct time
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants