search

pashapm / cofoja

Automatically exported from code.google.com/p/cofoja
GNU Lesser General Public License v3.0
0 stars 0 forks source link

Builds rely on ${java.class.path} #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Compilation on Ubuntu 10.10 with all libasm libraries and sun java

What is the expected output? What do you see instead?
Package does not exists compilation error

What version of the product are you using? On what operating system?
Ubuntu 10.10 with all libasm  (1,2,3) libraries and sun java

Please provide any additional information below.
Manually adding lib to classpath in build helps but this not universal solution.

Original issue reported on code.google.com by teodoz...@gmail.com on 9 Feb 2011 at 9:48

Attachments:

GoogleCodeExporter commented 9 years ago 
The current build file assumes that you have the proper libraries in the class 
path when you try to compile. We could also provide variables to bind to proper 
paths, which may be a bit cleaner. Ant is not an auto-configuration tool 
anyway. At the moment, you should just compile witht he proper environment 
variable set:

CLASSPATH=/usr/share/... ant

In no case should we hard-code these values in the build file, though. The next 
version of the build script, which I'm working on along with Maven support, 
comes with variables, so you can just type instead, if you wish:

ant -Dasmjar=/usr/share/...

Though I'm not convinced that is much of an improvement...

Original comment by nhat.min...@gmail.com on 9 Feb 2011 at 11:33

GoogleCodeExporter commented 9 years ago 
The following patch restructures the build.xml script and allows you to 
override the path to the dependencies in a property file called 
'local.properties' at the root of the project. It also comes with a 
'default.properties' file which contains all the user-settable properties with 
their descriptions. The patch is awaiting review, but feel free to try it out 
and make suggestions.

Original comment by nhat.min...@gmail.com on 11 Feb 2011 at 3:28

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Now user knows that needs to make path and I think this is right way for ant. 
Thanks.

I attach maven template that makes jar only (run with mvn install) maybe will 
help.

I didn't have time to test cofoja itself but weekend is coming.

Original comment by teodoz...@gmail.com on 11 Feb 2011 at 5:09

Attachments:

GoogleCodeExporter commented 9 years ago 
We already have a POM file discussion going on in issue 11, and I've provided 
another uncommitted patch in that thread, which is a bit more complete, but 
thanks anyway. :)

I know there are a few patches floating around (at least three on this bug 
tracker alone) and it's a bit difficult for outsiders to keep track; you may 
wonder why they're not committed yet; here's why: the official policy of the 
project, which we have inherited from Google, is systematic review. And since 
we're a bit shorthanded at the moment with David AFK, it takes time for changes 
to make it into the repo.

Original comment by nhat.min...@gmail.com on 11 Feb 2011 at 6:58

GoogleCodeExporter commented 9 years ago 
Committed the new build system as r78. Paths to JAR files now have to be set 
explicitly and default to lib/<lib>.jar, as per Ant guidelines.

Original comment by nhat.min...@gmail.com on 23 Feb 2011 at 10:39