Skip to content

Cherry-pick from 2.8.1-experimental #33

Closed

Description

@tresf

@bmhm I think you're the best candidate for this, but there are some decisions that were made in the 2.8.1-experimental branch that may be useful for this project. Some are duplicates of open bug reports (such as code formatter) but I wanted a proper review of this experimental branch before purging it.

Activity

  1. added
    component:cmakeChanges to the native build process using `cmake`.
    component:mavenChanges to the java build process
    enhancementNew feature or request
    and removed
    component:cmakeChanges to the native build process using `cmake`.
    on Apr 11, 2019
  2. bmarwell commented on Apr 11, 2019

    @bmarwell

    Ok, this is what I picked up from the diff (thanks for directly linking the compare view btw!):

    That about wraps it up. I wish we could have @vogt31337 here to help us implement that maven-osgi part (Apache Felix maven-bundle-plugin).

  3. tresf commented on Apr 11, 2019

    @tresf
    Author

    @bmhm thanks. So what I'd like to do is find a way to purge this experimental branch from our code. Can we open relevant issues, copy code snippet, etc or do you feel it's best to keep it around for a while?

  4. bmarwell commented on Apr 12, 2019

    @bmarwell

    Let's just tick the box for every issue we opened to keep track of them individually.

  5. tresf commented on Apr 12, 2019

    @tresf
    Author

    SerialNativeAccess.java is pretty much what native-lib-loader does. We could pick out parts like this line (v2.8.0...java-native:2.8.1-archivediff-77f0faf141ca0a69b33644e479631d5dR89) to implement armsf or armhf if needed.

    This code already exists in the source tree under a different file (not specific to 2.8.1 branch) https://github.com/java-native/jssc/blob/v2.8.0/src/java/jssc/SerialNativeInterface.java#L118-L135.

    Since we don't have a bug report for it, I'll create one and tick the box.

    File renaming from src/ to src/main/ -- that's what I have proposed, too. But we agreed on waiting for patches to be included before we make that transition.

    Can you check it off then, or is this not yet explained in a bug report?

  6. tresf commented on Apr 14, 2019

    @tresf
    Author

    Copied the unit tests into #37 @bmhm just need checkboxes 1 and 4 ticked, then we can purge off this branch.

  7. tresf commented on Apr 14, 2019

    @tresf
    Author

    All items are checked off. Closing and purging 2.8.1 branch.

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions