Hello Russel, Russel Winder-4 wrote: >The core problem in trying to be helpful here is that you give too >little information about what you are trying to do to be concretely >helpful. In this topic it was not my intention to write about a specific problem.
... >If you don't know Maven is all your previous experience with Ant? Yes. >The place to start is at the beginning. What does your project look >like? Is it structure according to the Maven standard structure or >something different? What sort of build product are you trying to >create? I have no problem with my project structure. I could tailor my gradle.build. It was more or less straightforward experience to set up my local repo so hat I can compile the project. >Did you start with a trivial project and then add to it to to make the >project bigger and more like the final project you have, or are you >trying to work directly with the final project? This is a new project and is rather simple at present. >> I got an error which says: cannot find include() method. >Without seeing the file it is impossible to interpret the error you are >seeing. Sorry. OK. I started a topic a bit earlier describing the problem. http://old.nabble.com/Could-not-find-method-include()-td26740547.html I always try to give enough context to the problem, but it may happen that now this was not enough. >> I already know what is sourceSet(s), what is main (I can redefine it for >> my >> purposes). "classes" makes the first headache. My guess that this refers >> to >> the set of classes produced by compile task (available under buildDir >> property as defined by project). "from" means a kind of referencing to >> this >> set and include is the selection/filtering from that set. >Again without the file it is difficult to say anything constructive let >alone useful. I am talking about this in a generic context to illustrate what kind of problems I face when trying to understand things within gradle. I do not want to flood the list with too basic question. I don't mind to work through the hard way. Just wanted to make sign that this feels too hard way compared to what I think it ought to be. ... >> Can you advice me where to start with my basic understanding after of >> what I >> can fully enjoy gradle's wonders? >First play with a trivial standard Maven structured project. >Then play with the structure and make the build work. >Then put it back as standard is good :-) >Then try various experiments leading towards the final project. As said, the first three was not a problem. The last point is what I am following :-) >Hopefully the above helps start the process of helping. Thank you for paying attention to my problem! Zsolt -- View this message in context: http://old.nabble.com/where-to-start-for-a-beginner-tp26741219p26758983.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
