ajwang / groovypptest

Automatically exported from code.google.com/p/groovypptest
0 stars 0 forks source link

Cannot build Groovy++ on Debian Testing With Gradle #375

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.  Clone the Groovy++ repository using Git from GitHub using Git protocol
2.  cd to directory and pull to ensure up-to-datedness
3.  Type "gradle clean"

What is the expected output? What do you see instead?

I expec a clean to happen.  Instead I get:

The sourceSet.classes method is deprecated and will be removed in the next 
version of Gradle. You should use the sourceSet.output method instead.
The sourceSet.classesDir method is deprecated and will be removed in the next 
version of Gradle. You should use the sourceSet.output.classesDir method 
instead.

FAILURE: Build failed with an exception.

* Where:
Build file '/home/Checkouts/Git/Git/GroovyPP/build.gradle' line: 210

* What went wrong:
A problem occurred evaluating root project 'GroovyPP'.
Cause: No such property: ARTIFACTORY_USER for class: 
org.gradle.api.internal.artifacts.publish.maven.deploy.groovy.DefaultGroovyMaven
Deployer

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug 
option to get more log output.

BUILD FAILED

Total time: 3.347 secs

What version of the product are you using? On what operating system?

HEAD on Debian Testing

Please provide any additional information below.

Original issue reported on code.google.com by russel.winder on 12 May 2011 at 2:45

GoogleCodeExporter commented 8 years ago
Properties  ARTIFACTORY_USER and ARTIFACTORY_PASSWORD should be defined in 
~/.gradle/gradle.properties

It can hold any values as long as you don't deploy on repo.

I wish I knew how to fix it with gradle

Original comment by alex.tka...@gmail.com on 12 May 2011 at 3:03

GoogleCodeExporter commented 8 years ago
A new user should not have to define arbitrary constants, especially if there 
are constraints on normal use.  Simple Groovy programming in build.gradle gets 
round this problem.  I'll see if I can do something in terms of a GitHub and 
pull request from a branch.

Original comment by russel.winder on 12 May 2011 at 3:11

GoogleCodeExporter commented 8 years ago
I have forked the repository on GitHub and will hopefully send it a pull 
request fairly quickly.

Original comment by russel.winder on 12 May 2011 at 4:33

GoogleCodeExporter commented 8 years ago
Alex, I submitted a patch for this issue: 
https://github.com/roshandawrani/groovypp/commit/fabec2c41677f489c2641e619865ac7
a273bb175

Also, can you please close my earlier pull request: 
https://github.com/alextkachman/groovypp/pull/4, because otherwise it does not 
let me submit a new pull request. Instead it updated the commit range on the 
same, old pull request, which was for a separate issue (#296).

Original comment by roshanda...@gmail.com on 23 May 2011 at 5:21

GoogleCodeExporter commented 8 years ago

Original comment by alex.tka...@gmail.com on 24 May 2011 at 11:21