Re: [kepler-dev] starting an Actor IO package
Hi Jianwu, make sure you're in the ptII-swt directory. that error occurs when you run maven in a directory that doesn't have a pom.xml the os info should be fine for the original pom. On Tue, Jul 8, 2008 at 5:19 PM, Jianwu Wang [EMAIL PROTECTED] wrote: Hi Tristan, Thanks for your great work. I tried to follow your steps, but get the following error. I changed the pom.xml according to the mvn --version info (deleting other profile and add os name). But still failed. Any comments? D:\Kepler\repository\hydrantmvn --version Maven version: 2.0.8 Java version: 1.5.0_15 OS name: windows xp version: 5.1 arch: x86 Family: windows D:\Kepler\repository\hydrantmvn compile exec:exec -e + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'exec'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [compile, exec:exec] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot execute mojo: resources. It requires a project with an existing po m.xml, but the build is not using one. [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot execute mojo: res ources. It requires a project with an existing pom.xml, but the build is not usi ng one. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one. at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:373) Best wishes Sincerely yours Jianwu [EMAIL PROTECTED] Post-Doctor Scientific Workflow Automation Technologies (SWAT) Laboratory San Diego Supercomputer Center University of California, San Diego San Diego, U.S.A. Tristan King wrote: Hi All, I've modified how my prototype works and built an example extension that demos how easy it is to build new a new view for actor outputs. I now use one generic IOFactory which uses spring to load the output devices. the spring config to use is passed in as a system property so it can be easily changed. I have built console output in as the default for which i've built a text output device and a graph output device, and modified the Display, XYPlotter and TimedPlotter actors to take advantage of these (note that this required breaking a lot of other code that depends on the XYPlotter and TimedPlotter actors). Today I built a text output device which opens up a SWT window to display text in. It is in it's own maven project and doesn't require that you have the ptII source on your system as the ptII jar (my actorio version) and all it's dependencies are stored in a maven repository. This small package works on linux and windows, but i'm having trouble with the macosx swt libraries. It's not bug free, but i think it's a good proof-of-concept. to play with this: * install maven http://maven.apache.org/download.html * install git (http://code.google.com/p/msysgit/ works great on windows) * clone ptII-swt (git clone
Re: [kepler-dev] starting an Actor IO package
Hi, Tristan, Thanks for your help. Now I can compile and run it correctly. Best wishes Sincerely yours Jianwu Wang [EMAIL PROTECTED] Post-Doctor Scientific Workflow Automation Technologies (SWAT) Laboratory San Diego Supercomputer Center University of California, San Diego San Diego, U.S.A. Tristan King wrote: Hi Jianwu, make sure you're in the ptII-swt directory. that error occurs when you run maven in a directory that doesn't have a pom.xml the os info should be fine for the original pom. On Tue, Jul 8, 2008 at 5:19 PM, Jianwu Wang [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Tristan, Thanks for your great work. I tried to follow your steps, but get the following error. I changed the pom.xml according to the mvn --version info (deleting other profile and add os name). But still failed. Any comments? D:\Kepler\repository\hydrantmvn --version Maven version: 2.0.8 Java version: 1.5.0_15 OS name: windows xp version: 5.1 arch: x86 Family: windows D:\Kepler\repository\hydrantmvn compile exec:exec -e + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'exec'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [compile, exec:exec] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot execute mojo: resources. It requires a project with an existing po m.xml, but the build is not using one. [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot execute mojo: res ources. It requires a project with an existing pom.xml, but the build is not usi ng one. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one. at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:373) Best wishes Sincerely yours Jianwu Wang [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Post-Doctor Scientific Workflow Automation Technologies (SWAT) Laboratory San Diego Supercomputer Center University of California, San Diego San Diego, U.S.A. Tristan King wrote: Hi All, I've modified how my prototype works and built an example extension that demos how easy it is to build new a new view for actor outputs. I now use one generic IOFactory which uses spring to load the output devices. the spring config to use is passed in as a system property so it can be easily changed. I have built console output in as the default for which i've built a text output device and a graph output device, and modified the Display, XYPlotter and TimedPlotter actors to take advantage of these (note that this required breaking a lot of other
