eclipse make dependencies
Status: Planning
Brought to you by:
laszewsk
Menu
▾
▴
#2 eclipse make dependencies
The current system is dependent on eclipse. The location of lib, etc, should be in cyberaide so that their contents can be shared accoss projects.
This way the jars are not replicated and code developed by different teams can be run within the same JVM.
.casspath needs also to be relocated.
It should be investigated if ant can be used as build system.
We have for years in the Java CoG Kit operated this way. A eevaluation of new Java technologies should be conducted to assess how to do this best with the newest generation of software.
Logged In: NO
Please note that there already exists a bug for b)
https://sourceforge.net/tracker/index.php?func=detail&aid=1915131&group_id=210433&atid=1013714
Will will address it if we have the time.
On Sat, Apr 19, 2008 at 7:38 PM, Gregor von Laszewski <laszewski@gmail.com> wrote:
its a requirement. However, i accept that it takes time.
When we speack of refactoring I also looked into the source code and find the following
a) gridshell_se needs to be refactored to gridshell
b) there are lots of duplicated jar files in the svn which is unnecessary and convolutes the tree.
all jar files should be stored in a lib directory on the top most level. if they are needed in some different fashion you ned to copy them from there.
to be specific: ./cyberaide/src/gridshell_se/GridShell/lib
contains
activation.jar jaxrpc.jar
apache2.0-LICENSE.txt jsr173_1.0_api.jar
axis.jar mail.jar
axis2 nwsXMLType.jar
commons-cli-2.0-SNAPSHOT.jar saaj.jar
commons-discovery-0.2.jar wsdl4j-1.5.1.jar
commons-io-1.4.jar xbean.jar
commons-logging-1.0.4.jar xbean_xpath.jar
edu.ucsb.cs.qbets-LICENSE.txt xmlbeans-qname.jar
edu.ucsb.cs.qbets.jar
all these files need to be in
./cyberaide/lib
this also requires the change and cleaning of what you have in your example directory that should be handled the same way.
In case you use maven for your build process you could simplify this even further and avoid storing the jars entirely in the svn. BUt I do not require that you use maven at this time, I do however require that all libraries are shared among all projects in the top most lib directory.
hope that helps
Gregor
On Apr 19, 2008, at 7:23 PM, Kyle Tirak wrote:
I've already made the commit. The change to a .cyberaide directory will take
some more changes to both the python and java code than just what deployment
touches, Jeff was already storing the gridshell.prop file there.
-Kyle
On Saturday 19 April 2008 07:14:18 pm Gregor von Laszewski wrote:
please hold on for a second as the dir needs to be .cyberaide and
not .gridshell
this way we can put in more than just the gridshell properties, but
also put in configuration files from others.
also remember that the project package names are org.cyberaide. ....
so all is well if we do it this way and we can integrate
On Apr 19, 2008, at 6:51 PM, Kyle Tirak wrote:
Hey everyone,
I'm about to commit necessary changes for deployment of the
GridShell. These
changes will break everyone's development environment due the
removal of
hard-coded paths from our code.
To resolve the breakages, everyone will have to create a file
called 'gridshell.conf' (without quotes) in their $HOME/.gridshell/
directory
with the following contents:
[CONFIGURATION]
install_dir:{The base directory on your system containing our java
project}
jvm_path:{The path to your system's JVM}
Hints:
1. The install_dir should contain the folders 'bin' and 'lib' for
our java
project.
2. The jvm_path on a Mac should
be '/System/Library/Frameworks/JavaVM.framework/JavaVM'
On a linux machine, the file it should point to is named 'libjvm.so'
in the
server directory of your JRE.
3. Neither entry should include quotes around the path.
Note: Our install script auto-configures this file for the end-user.
If you
need help with this, feel free to email me.
I've also attached a new ipythonrc that needs be placed in
$HOME/.ipython/
The file can also be found in svn under the PythonCLI project or the
ClientDeployment project.
That should be all changes necessary, if you still have problems,
try to copy
the GridShell directory in PythonCLI/IPython/ to $HOME/.ipython/
Email me if you have more problems than this.
-Kyle
On Friday 18 April 2008 08:49:29 am Gregor von Laszewski wrote:
Dear All:
Yesterday it was mentioned in the meting that one can not show of
the
shell. However, another undergraduate has developed a test program to
show of the cluster he developed with other students. Interesting is
that the way he invokes the program can be easily done through your
shell. The shell could be used to coordinate all invocations on the
various resources available to the team which could include
* cluster.rit.edu
* lmc.rit.edu
* lilacs (gt4)
* iris01 (ssh)
* daisys (ssh)
and create a cool output. What is needed is actually an ipython
script
doing this.
The result of what comes out is a movie using ray tracing. One could
even argue this is could be a "test" for the functionality of your
shell and exploring its limitations.
I am not saying that you need to do that, but I am saying there are
creative ways on demonstrating that when you show of the shell you
may
need to do this in a context. A context that is obvious from the
users
requirements.
Gregor
<ipythonrc.txt>
Logged In: NO
i suggest to se maven instead of ant. this way many lib files can be kept outside of the source and maven will take care of downloading it.