Differences between revisions 4 and 6 (spanning 2 versions)
Revision 4 as of 2011-12-05 01:12:06
Size: 1708
Editor: AlexPico
Comment:
Revision 6 as of 2012-03-23 16:15:20
Size: 2979
Editor: 192
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
|| '''Setting up an IDE''' : Command Line|| '''Editor(s)''': PietMolenaar || '''Date''': February 16th 2011 ||'''Status''': Page created, content stubs added || || '''Setting up an IDE''' : Command Line|| '''Editor(s)''': PietMolenaar || '''Date''': March 23, 2012 ||'''Status''': First version ||
Line 7: Line 7:
<<TableOfContents(3)>> <<TableOfContents(2)>>
Line 17: Line 17:
=== UNIX (e.g. Mac OS)/Linux ===

==
== Checkout code from SVN ====
== Checkout code from SVN ==
Line 23: Line 21:
% svn co http://chianti.ucsd.edu/svn/core3/gui-distribution/trunk/ gui-distribution svn co http://chianti.ucsd.edu/svn/core3/gui-distribution/trunk/ gui-distribution
Line 26: Line 24:
==== Compile ==== == Compile ==
Line 28: Line 26:
% cd gui-distribution
% mvn clean install
cd gui-distribution
mvn clean install
Line 32: Line 30:
==== Run Application ==== == Run Application ==

The Cytoscape developer distribution contained in {{{assembly/target/cytoscape}}} is configured to load OSGi bundles from your local Maven repository. If it can't find a bundle there, it will fall back to Cytoscape's repository on {{{code.cytoscape.org}}}. That means you don't have to do a full build of the application to test your changes. All you need to do is {{{mvn install}}} the bundles you change and then run the start up scripts as follows:

=== Mac OS/Linux/UNIX ===
Line 35: Line 37:
% cd distribution/target/cytoscape-${version}-null.dir/cytoscape-${version}
%
cytoscape.sh
cd assembly/target/cytoscape
./cytoscape.sh
Line 39: Line 41:
=== Windows ===
{{{
cd assembly\target\cytoscape
cytoscape.bat
}}}

Cytoscape caches installed bundles so it can start up faster. If you use {{{mvn install}}} to overwrite an existing bundle without changing the OSGi version number, Cytoscape might not load up the new version of the bundle. In this case, you'll need to delete the bundle cache directory before starting Cytoscape:

=== Mac OS/Linux/UNIX ===

{{{
cd assembly/target/cytoscape
rm -rf framework/data
}}}
Line 41: Line 57:
TBD {{{
cd assembly\target\cytoscape
rd /s framework\data
}}}

== Debugging ==

To enable remote debugging, pass the {{{debug}}} argument to the start up script:


=== Mac OS/Linux/UNIX ===
{{{
./cytoscape.sh debug
}}}

=== Windows ===
{{{
cytoscape.bat debug
}}}

At this point, Cytoscape will pause until a debugger is connected to port 12345.
Line 49: Line 85:
 * See also: [[Cytoscape_3/Interactive_Shell|Interactive Shell]]

Setting up an IDE : Command Line

Editor(s): PietMolenaar

Date: March 23, 2012

Status: First version

Introduction

You need the following tools on your machine.

  • JDK 6
  • Apache Maven
  • Subversion client

Checkout code from SVN

First, you need to check out Cytoscape 3 GUI distribution bundle:

svn co http://chianti.ucsd.edu/svn/core3/gui-distribution/trunk/ gui-distribution

Compile

cd gui-distribution
mvn clean install

Run Application

The Cytoscape developer distribution contained in assembly/target/cytoscape is configured to load OSGi bundles from your local Maven repository. If it can't find a bundle there, it will fall back to Cytoscape's repository on code.cytoscape.org. That means you don't have to do a full build of the application to test your changes. All you need to do is mvn install the bundles you change and then run the start up scripts as follows:

Mac OS/Linux/UNIX

cd assembly/target/cytoscape
./cytoscape.sh

Windows

cd assembly\target\cytoscape
cytoscape.bat

Cytoscape caches installed bundles so it can start up faster. If you use mvn install to overwrite an existing bundle without changing the OSGi version number, Cytoscape might not load up the new version of the bundle. In this case, you'll need to delete the bundle cache directory before starting Cytoscape:

Mac OS/Linux/UNIX

cd assembly/target/cytoscape
rm -rf framework/data

Windows

cd assembly\target\cytoscape
rd /s framework\data

Debugging

To enable remote debugging, pass the debug argument to the start up script:

Mac OS/Linux/UNIX

./cytoscape.sh debug

Windows

cytoscape.bat debug

At this point, Cytoscape will pause until a debugger is connected to port 12345.

Issues

List any issues, conflict, or dependencies raised by this proposal

Comments

How to Comment

Edit the page and add your comments under the provided header. By adding your ideas to the Wiki directly, we can more easily organize everyone's ideas, and keep clear records. Be sure to include today's date and your name for each comment. Try to keep your comments as concrete and constructive as possible. For example, if you find a part of the RFC makes no sense, please say so, but don't stop there. Take the extra step and propose alternatives.

Cytoscape_3/AppDeveloper/SettingUpAnIDE/CommandLine (last edited 2013-04-09 21:03:16 by 192)

Funding for Cytoscape is provided by a federal grant from the U.S. National Institute of General Medical Sciences (NIGMS) of the Na tional Institutes of Health (NIH) under award number GM070743-01. Corporate funding is provided through a contract from Unilever PLC.

MoinMoin Appliance - Powered by TurnKey Linux