Skip to content

fix #96 gradle build #98

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

Merged
merged 1 commit into from
Nov 22, 2014
Merged

Conversation

ouertani
Copy link
Contributor

No description provided.


subprojects {
apply plugin: 'java'
sourceCompatibility = 1.7
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this true?

Copy link
Contributor

Choose a reason for hiding this comment

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

Hint:
"javacOptions in compile ++= Seq("-encoding", "UTF-8", "-source", "1.6", "-target", "1.6", "-Xlint:unchecked", "-Xlint:deprecation")"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@viktorklang : Should we support java 6 ?

@viktorklang
Copy link
Contributor

Regarding Java6 support, that's what we currently support and changing that would be a completely different PR IMO.


gradle.projectsEvaluated {
tasks.withType(JavaCompile) {
options.compilerArgs << "-Xlint:unchecked" << "-Xlint:deprecation"
Copy link
Contributor

Choose a reason for hiding this comment

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

we need encoding UTF-8 here too, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes indeed, updated on lines below.

@ouertani ouertani force-pushed the gradle_build branch 2 times, most recently from 3e2ca6b to 1e4ff2b Compare August 20, 2014 06:13
@ouertani
Copy link
Contributor Author

@reactive-streams/contributors any update ?

apply plugin: 'idea'

group = 'org.reactivestreams'
version = '0.4.0'
Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated to 0.4.0

@viktorklang
Copy link
Contributor

@reactive-streams/contributors Can the contributors try this PR and verify that it works for the intents and purposes of build and publish?

@ktoso
Copy link
Contributor

ktoso commented Oct 27, 2014

Is it possible to publish locally (ivy-style) with this build or would it need some more plugins?

// that's my use case when working on the tck and validating with akka-streams

@benjchristensen
Copy link
Contributor

The build fails for me.

100 errors
1 warning
:reactive-streams-tck:compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':reactive-streams-tck:compileJava'.
> Compilation failed; see the compiler error output for details.

I also recommend you chmod +x gradlew and commit it in an executable state so on checkout a user can just invoke ./gradlew build without making it executable every time.

The branch and status for me doing the test above is:

$ git remote -v
origin  https://github.com/ouertani/reactive-streams.git (fetch)
origin  https://github.com/ouertani/reactive-streams.git (push)

$ git status
On branch gradle_build
Your branch is up-to-date with 'origin/gradle_build'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

    modified:   gradlew

no changes added to commit (use "git add" and/or "git commit -a")

@ouertani
Copy link
Contributor Author

@benjchristensen build is working ouertani@f8797b8

@ouertani
Copy link
Contributor Author

@ktoso

   ./gradlew install 

Installs the 'archives' artifacts into the local Maven repository.

@ktoso
Copy link
Contributor

ktoso commented Oct 28, 2014

@ouertani that's why I'm asking about local ivy2 repos. Makes things a bit easier on my side if it's possible out-of-the-box.

@ouertani
Copy link
Contributor Author

@ktoso, I think the build definition should be updated as follows but IMHO don't recommend to use urls

    repositories {  
        mavenLocal()
        mavenCentral()   
        ivy { 
            artifactPattern "/opt/ivycache/local2/[organisation]/[module]/[revision]/[artifact](-[classifier])-[revision](.[ext])" 
            url '/opt/ivycache/local' 
        } 
    }
    uploadArchives {
        repositories {
            add(new org.apache.ivy.plugins.resolver.FileSystemResolver()) {
                addIvyPattern "/opt/ivycache/local2/[organisation]/[module]/[revision]/[artifact](-[classifier])-[revision](.[ext])"
                addArtifactPattern "/opt/ivycache/local/[organisation]/[module]/[revision]/[artifact](-[classifier])-[revision](.[ext])"
            }
        }

@viktorklang
Copy link
Contributor

Can more @reactive-streams/contributors verify that this is a solid replacement for the current build so we can either yay or nay it? Thank you

@ktoso
Copy link
Contributor

ktoso commented Nov 6, 2014

Thanks for the links @viktorklang – that works for me then, I'm fine with whatever @reactive-streams/contributors quorum decides on this then 😉

@smaldini
Copy link
Contributor

smaldini commented Nov 6, 2014

Need to take a moment to evaluate it, will do after some work for a customer;

@viktorklang
Copy link
Contributor

Thanks @smaldini

@viktorklang
Copy link
Contributor

@ouertani I think the following PR will be of importance for this PR: #136

Update: fixed PR number

@ouertani
Copy link
Contributor Author

ouertani commented Nov 9, 2014

@viktorklang @ktoso I add ivy support ouertani@8a2e7f0 but noted ;

ivy {
                // change to point to your repo, e.g. http://my.org/repo
                url "${rootProject.buildDir}/repo"
}

@ouertani
Copy link
Contributor Author

ouertani commented Nov 9, 2014

@viktorklang, yes example subproject should also be included. But this should be after or before merging this PR ?

@viktorklang
Copy link
Contributor

@ouertani Absolutely, I just wanted to give you a heads up :)

version = '0.4.0'


gradle.projectsEvaluated {
Copy link
Contributor

Choose a reason for hiding this comment

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

This projectsEvaluated wrapper should go. It's not needed.

@ldaley
Copy link
Contributor

ldaley commented Nov 10, 2014

Looks ok to me. There are probably some cosmetic improvements that can be made though.

@viktorklang
Copy link
Contributor

@reactive-streams/contributors My thinking is to merge this after we ship 1.0-M1 so we can try this out for publishing 1.0-RC1. Sound good? Vote?

@ouertani
Copy link
Contributor Author

@viktorklang @alkemist example project has been add

@viktorklang
Copy link
Contributor

@ouertani Excellent! Would you mind squashing the commits please?

@ouertani ouertani force-pushed the gradle_build branch 2 times, most recently from b9756df to c455d91 Compare November 20, 2014 13:40
@ouertani
Copy link
Contributor Author

@viktorklang done c455d91 👍



group = 'org.reactivestreams'
version = '0.4.0'
Copy link
Contributor

Choose a reason for hiding this comment

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

Bump version to 1.0.0.M1

@viktorklang
Copy link
Contributor

I'm ready to merge this after version bump of RS to 1.0.0.M1 and Gradle 2.1!

Updates CONTRIBUTING.md with Gatekeeper SLAs

=tck method names and fine-details in some specs improved

=tck reactive-streams#128 TCK updated to reflect merged rules 2.13 and 2.14

Moves the examples out to its own sub-project and makes sure that they are compiled but not published.

=tck reactive-streams#138 clarify docs on registerOnSubscribe

Aims to clarify confusion about this method, as seen in reactive-streams#138

fix reactive-streams#96

fix reactive-streams#95 gradle build tool

makes gradlew executable

 add inter dependency

add ivy publish incubator plugin  but using this url "${rootProject.buildDir}/repo"

 merge

add example project

add example project
@ouertani
Copy link
Contributor Author

@viktorklang updated to 2.1 and 1.0.0.M1.

@viktorklang
Copy link
Contributor

@reactive-streams/contributors I think everyone has had ample time to vote against this one (since august 19th to be specific). Merging, and now we are on gradle iso sbt!

viktorklang added a commit that referenced this pull request Nov 22, 2014
@viktorklang viktorklang merged commit 91120b8 into reactive-streams:master Nov 22, 2014
@viktorklang
Copy link
Contributor

Thanks so much for your contribution @ouertani!

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.

6 participants