Our paper has been accepted by the CAISE'05 conference.
- create a directory as the columba workspacemkdir %workspace%- Extract columba source codecolumba-win32-1.0_RC3-src.zipinto the following directory%workspace%/columba- run eclipse with the columba workspace:eclipse -data %workspace%- close the welcome screen - creat a columba project - in the ``package navigator", right click, choose "new"/"project"/"java project from existing ant buildfile" - enter "%workspace%/columba/build.xml" as the Ant buildfile location - fixing the compilation errors - edit .classpath<?xml version="1.0" encoding="UTF-8"?> <classpath> <!-- source code --> <classpathentry kind="src" path="src/addressbook/api"/> <classpathentry kind="src" path="src/addressbook/core"/> <classpathentry kind="src" path="src/addressbook/test"/> <classpathentry kind="src" path="src/columba/core"/> <classpathentry kind="src" path="src/columba/test"/> <classpathentry kind="src" path="src/mail/api"/> <classpathentry kind="src" path="src/mail/core"/> <classpathentry kind="src" path="src/mail/test"/> <classpathentry kind="src" path="res"/> <!-- junit 3.8.1 --> <classpathentry kind="var" path="ECLIPSE_HOME/plugins/org.junit_3.8.1/junit.jar"/> <!-- jre --> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/> <classpathentry kind="lib" path="lib/forms-1.0.5.jar"/> <classpathentry kind="lib" path="lib/jscf-0.3.jar"/> <classpathentry kind="lib" path="lib/commons-cli-1.0.jar"/> <classpathentry kind="lib" path="lib/jwizz-0.1.3.jar"/> <classpathentry kind="lib" path="lib/jhall.jar"/> <classpathentry kind="lib" path="lib/ristretto-1.0_RC3.jar"/> <classpathentry kind="lib" path="lib/macchiato-1.0pre1.jar"/> <classpathentry kind="lib" path="lib/frapuccino-1.0pre1.jar"/> <classpathentry kind="lib" path="lib/lucene-1.3-final.jar"/> <classpathentry kind="lib" path="lib/looks-1.3.1.jar"/> <classpathentry kind="lib" path="native/win32/lib/jniwrap-2.4.jar"/> <classpathentry kind="lib" path="native/win32/lib/winpack.jar"/> <classpathentry kind="lib" path="lib/jdom.jar"/> <classpathentry kind="lib" path="lib/jpim.jar"/> <classpathentry kind="lib" path="lib/je-1.7.1.jar"/> <classpathentry kind="lib" path="native/win32/lib/jdic.jar"/> <classpathentry kind="output" path="bin"/> </classpath>- remove unnecessary files - remove the directory "classes" - delete the linked directory "api" - delete "build.xml" src/*.build.xml src/*/build.xml - delete "maven.xml" - compile plugins - create a separate eclipse projects for every plugincd %workspace%/columba mv plugins/* ..- create a new Java project for each of these plugins - copy the .classpath from the columba and make similar modifications - set the main class to run - extract columba.jar/META-INFjar xf columba.jar META-INF- removing the helpManager error: org.columba.core.help.HelpManager.java add the following line to methods enableHelpOnButton, enableHelpKeyif (getHelpBroker()==null) return;- the main class is org.columba.core.main.Main - run as Java application
Before Talking AOPHP Says: PHP Cant Talk Right Now After Talking N1: 5 | N2: 10 Aspect2: Before Advice on Add Function Just Called Before Advice on Add Function Just Called Aspect2: After Advice on Add Function Just Called After Advice on Add Function Just Called TOTAL OF N1 & N2: 15Although both aspects have "around" advices, only the first one took effect, because the "say" method already disappeared. The second aspect weaves the "before" advices earlier, but "after" advices also earlier! The reason I guess is that the second aspect still weaves its advice with the original function, rather than on the woven function.
- get junction.exe - create two buttons - junction.exe, parameters: %T%N %P%N - junction.exe, parameters: %P%N /d
September 13, 2006 Problem. In total commander, I often want to open a cygwin shell window to put the selected directory as the current one. However, when a cygwin window is opened, the current directory always stick to the HOME, which is for me, "d:\cygwin\home\Yijun Yu". Then to access a file in the visible directory of Total commander, I have to issue a "chdir" to something like "/cygdrive/c/path/to/commander/directory". How annoying! Then how to work around this problem? Solution. It is a combination of small tricks. 1. Create a shortcut button on the commander toolbar Right click at toolbar, choose "Change..." Append a command, fill in the following information:2. Edit the start script of cygwin, namely D:\cygwin\cygwin.bat: @echo off echo cd "%*" > "D:\cygwin\home\Yijun Yu\.cdpath" D: chdir D:\cygwin\bin bash --login -i 3. Create two scripts in your home directory (e.g. "D:\cygwin\home\Yijun Yu"): .profile: . .bashrc .bashrc: source .cdpath That's it. When you open any directory in total commander, just click the cygwin.ico button, you will launch a cygwin shell in the proper place. Enjoy!
eclipse_product\
features\
plugins\
Not all features and plugins are necessary for every user tasks, for example,
a C/C++ development user may want the CDT product, whereas the Java
developer does not need it. Therefore, we consider to create a script
to automatically install/uninstall any Eclipse product.
When the Eclipse platform starts, it first looks at its configuration directory
to see which features should be enabled, then every plugin needed in the
execution will be *lazily* loaded by the platform. Therefore,
the installation of an Eclipse product requires to copy the product features
and plugins into the Eclipse installation directory. The uninstallation of an
Eclipse product requires to remove the product features and plugins from the
Eclipse installation directory.
c:\> junction foo d:\foowill create a mirror of the d:\foo as c:\foo. Here C: must be in a NTFS file system, whereas D: can be any file system format. Junction point is more powerful than the "subst" utility in the DOS file system which mirrors a disk letter to a remote directory (I have written a chapter on how to use *subst* utility to achieve symbolic link effect some years ago). Here the remote directory is *mounted* to any directory in the NTFS file system. An important difference between a junction point and a symbolic link in Unix, unfortunately, is that the junction point is treated as really the remote directory. In other words, if one deletes the junction point directory, all files under the remote directory will be removed. To remove a junction point directory safely without removing the remote files, the junction point is deleted by detaching it from the remote directory. This can be done by the *junction* command by the "/d" option:
c:\> junction /d foo
1 @echo off 2 set ECLIPSE=c:\eclipse 3 pushd %ECLIPSE%\features 4 for /D %%d in (%1\features\*) do @junction %%~nxd %%~dpnxd 5 cd ..\plugins 6 for /D %%d in (%1\plugins\*) do @junction %%~nxd %%~dpnxd 7 popdFirst, let's assume the script has one argument that can be addressed by %1 in the script. This argument is used as the directory of the Eclipse product to be installed and the product has prepared a *features* and a *plugins* subdirectory to hold the features and plugins respectively.
1 @echo off 2 set ECLIPSE=c:\eclipse 3 pushd %ECLIPSE%\features 4 for /D %%d in (%1\features\*) do @junction /d %%~nxd 5 cd ..\plugins 6 for /D %%d in (%1\plugins\*) do @junction /d %%~nxd 7 popd
1. Install the total commander, of course. 2. Press 1, 2 or 3 to the shareware question of Total commander to be able to use all its functionality.5. Alternatively, if you know which products to be installed before hand, in the eclipse-install directory, prepare a script as follows:The file system is viewed by two parallel panes. The left-hand side shows the Eclipse platform directory. The right-hand side shows the Eclipse product directories, such as CDT (org.eclipse.cdt.sdk-3.0.0-M6-win32), ecletex for latex, ome4eclipse, Lavadora webservice for Eclipse, etc. and also our scripts under the *eclipse-install* directory. (I will write a separate tip on the usage of the latex plugins). 3. Now create a tool bar button by right click at the toolbar, apply *change...", fill in the following parameters:
Here %P%N indicate the Eclipse product directory that you just selected. 4. Place your mouse on one of the product directories, then press the toolbar button. When you open the Eclispe plugin directories, you can see the installed directories: the small shortcut decorator on the directory names are created as junction point directories.
call eclipse-install d:\ome4eclipse call eclipse-install d:\org.eclipse.cdt.sdk-3.0.0-M6-win32 call eclipse-install d:\latex call eclipse-install d:\webserviceThen doubleclick this script will install all products at once.
December 7, 2005
The tutorial still works, but I found two simpler workarounds:
1) create a "links" subdirectory under the %ECLIPSE_HOME% directory.
For each product, create a file links/%product%.link which contains
a single line:
path=%path_to_product%
2) create an empty .eclipseextension file under the %product%/eclipse
directory, then use "Help/Manage configuration" dialog to add
an extension to the %product% directory
To me, the first alternative is better, since you may fully automate
the reconfiguration of Eclipse without using its dialog.
Note that the following technique may still be used to create a symbolic
link to the links directory because it is still under the Eclipse
SDK installation directory and could be removed along with the
Eclipse SDK.
Feb 28, 2005
The OpenOME project uses
this script to select the Eclipse products without physically copying them, on
the basis of the above finding.
August 1, 2006
Eclipse products can now be customized by a
downloading service that bundles them on the demand of a client.
September 15, 2006
One can perform automated update of Eclipse products at command line.
This is slower than the previous solution, but platform independent...
See how we update the OpenOME product and its dependent products
automatically for its users/developers.
Goal.java
package edu.toronto.cs.goalmodel;
import java.util.List;
/** @model */
public interface Goal {
/** @model */
String getName();
/** @model default=0 */
LabelType getLabel();
/** @model */
DecompositionType getType();
/** @model */
Goal getParent();
/** @model type="Goal" containment="true" opposite="parent" */
List getGoal();
/** @model type="Topic" containment="true" */
List getTopics();
/** @model type="Contribution" containment="true" */
List getRule();
/** @model type="Property" containment="true" */
List getProperty();
}
Contribution.java
package edu.toronto.cs.goalmodel;
/** @model */
public interface Contribution {
/** @model type="ContributionType" */
int getType();
/** @model */
Goal getTarget();
}
DecompositionType.java
package edu.toronto.cs.goalmodel;
/** @model */
public final class DecompositionType {
/** @model name="OR" */
public static final int OR = 0;
/** @model name="AND" */
public static final int AND = 1;
/** @model name="LEAF" */
public static final int LEAF = 2;
}
ContributionType.java
package edu.toronto.cs.goalmodel;
/** @model */
public final class ContributionType {
/** @model name="HELP" */
public static final int HELP = 1;
/** @model name="HURT" */
public static final int HURT = -1;
/** @model name="MAKE" */
public static final int MAKE = 2;
/** @model name="BREAK" */
public static final int BREAK = -2;
}
LabelType.java
package edu.toronto.cs.goalmodel;
/** @model */
public final class LabelType {
/** @model name="Satisfied" */
public static final int SATISFIED = 2;
/** @model name="Denied" */
public static final int DENIED = -2;
/** @model name="PartiallySatisfied" */
public static final int PARTIALLY_SATISFIED = 1;
/** @model name="PartiallyDenied" */
public static final int PARTIALLY_DENIED = -1;
/** @model name="Unknown" */
public static final int UNKNOWN = 0;
/** @model name="Conflict" */
public static final int CONFLICT = 4;
}
Topic.java
package edu.toronto.cs.goalmodel;
/** @model */
public interface Topic {
/** @model */
String getTopic();
}
Property.java
package edu.toronto.cs.goalmodel;
/** @model */
public interface Property {
/** @model */
String getName();
/** @model */
String getValue();
}
|
|
 ICSE12: How to protect your changes in generated code? Maintaining invariant traceability through bi-directional transformations. |
|
My expertise is in developing Automated Software Engineering methods (e.g., normalising, reasoning, aspect-orientation, visualization, and restructuring), aiming at solving problems in research areas such as Requirements Engineering , Software Maintenance and Evolution , Security and Privacy, and the Empirical Studies on Software Development. Currently I am interested in making evolving systems adapt to contextual changes that are deemed meaningful to the stakeholders (therefore requirements-driven). Research Prototypes |
View by:
