[kepler-dev] Help with Pop Up Box in Kepler
Derik Barseghian
barseghian at nceas.ucsb.edu
Thu Aug 27 16:47:21 PDT 2009
Hi Subhav and kepler-dev,
I'm trying the procedure (it used to work!) I gave you:
> 1) svn co https://code.kepler-project.org/code/kepler/branches/release-2.0.0-pre-alpha1-branch/modules/build-area
> build-area
> 2) cd build-area
> 3) ant clean-cache
> 4) ant change-to -Dsuite=wrp -Dbranch=https://code.kepler-project.org/code/kepler/branches/release-2.0.0-pre-alpha1-branch
> 5) ant update-ptolemy -Drev=54826
> 6) ant run
Like you, I got an error on step 5:
[update-ptolemy] Error: /home/barseghian/dev3/kepler_branch/ptolemy
does not exist.
I noticed this error during step 4:
[change-to] Downloading ptolemy...
[change-to] Using ptolemy branch: ${ptolemyBranch}
[change-to] svn co ${ptolemyBranch} /home/barseghian/dev3/
kepler_branch/ptolemy
[change-to] svn: '${ptolemyBranch}' does not appear to be a URL
[change-to]
[change-to] WARNING: It appears that the command did not execute
properly and exited with an exit code of: 1
[change-to] ptolemy-lib:
Like I recommended to you, at this point I manually copied my ptolemy
directory from my other kepler checkout (head), and then tried steps 5
and 6 again. This didn't work for you (windows), but it did for me
(linux): Kepler launched fine. I'm not sure why you got the error you
pasted below. Yes, please try ant-clean cache and then ant run again.
Does anyone else have ideas on what's wrong here?
Derik
On Aug 26, 2009, at 8:04 AM, subhav mital wrote:
> Hi Derik,
>
> Thanks for that. I did what we had discussed earlier and executed
> 'ant run'. Following is the error message -- stack trace -- I get:
>
>
> java.lang.Exception: Failed to parse "-kepler"
> at
> ptolemy
> .actor
> .gui
> .ConfigurationApplication
> .throwArgsException(ConfigurationApplication.java:635)
> at
> ptolemy
> .actor
> .gui.ConfigurationApplication.<init>(ConfigurationApplication.java:
> 292)
> at ptolemy.actor.gui.MoMLApplication.<init>(MoMLApplication.java:81)
> at ptolemy.vergil.VergilApplication.<init>(VergilApplication.java:
> 104)
> at ptolemy.vergil.VergilApplication$1.run(VergilApplication.java:194)
> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
> at
> java
> .awt
> .EventDispatchThread
> .pumpOneEventForHierarchy(EventDispatchThread.java:242)
> at
> java
> .awt
> .EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:
> 163)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:
> 157)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:
> 149)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
> Caused by: java.lang.Exception: Failed to read configuration 'file:/
> C:/Users/Subhav/Desktop/KeplerNew/wrp/configs/ptolemy/configs/kepler/
> configuration.xml'
> at
> ptolemy
> .vergil
> .VergilApplication
> ._createDefaultConfiguration(VergilApplication.java:286)
> at
> ptolemy
> .vergil
> .VergilApplication._createEmptyConfiguration(VergilApplication.java:
> 322)
> at
> ptolemy
> .actor
> .gui
> .ConfigurationApplication._parseArgs(ConfigurationApplication.java:
> 1109)
> at
> ptolemy.vergil.VergilApplication._parseArgs(VergilApplication.java:
> 452)
> at
> ptolemy
> .actor
> .gui.ConfigurationApplication.<init>(ConfigurationApplication.java:
> 226)
> ... 10 more
> Caused by: com.microstar.xml.XmlException: XML element "property"
> triggers exception:
> ptolemy.kernel.util.NameDuplicationException: Attempt to insert
> object named "_tableauFactory" into a container that already
> contains an object with that name. in file:/C:/Users/Subhav/Desktop/
> KeplerNew/ptolemy/target/classes/ptolemy/configs/
> fsmEffigyFactories.xml at line 30 and column 76
> Caused by:
> ptolemy.kernel.util.NameDuplicationException: Attempt to insert
> object named "_tableauFactory" into a container that already
> contains an object with that name.
> at ptolemy.moml.MoMLParser.startElement(MoMLParser.java:3385)
> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:921)
> at com.microstar.xml.XmlParser.parseContent(XmlParser.java:1104)
> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:924)
> at com.microstar.xml.XmlParser.parseContent(XmlParser.java:1104)
> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:924)
> at com.microstar.xml.XmlParser.parseContent(XmlParser.java:1104)
> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:924)
> at com.microstar.xml.XmlParser.parseDocument(XmlParser.java:481)
> at com.microstar.xml.XmlParser.doParse(XmlParser.java:159)
> at com.microstar.xml.XmlParser.parse(XmlParser.java:132)
> at ptolemy.moml.MoMLParser.parse(MoMLParser.java:1414)
> at ptolemy.moml.MoMLParser.parse(MoMLParser.java:1370)
> at ptolemy.moml.MoMLParser.parse(MoMLParser.java:1331)
> at ptolemy.moml.MoMLParser._parse(MoMLParser.java:5922)
> at ptolemy.moml.MoMLParser.startElement(MoMLParser.java:2681)
> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:931)
> at com.microstar.xml.XmlParser.parseContent(XmlParser.java:1104)
> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:924)
> at com.microstar.xml.XmlParser.parseContent(XmlParser.java:1104)
> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:924)
> at com.microstar.xml.XmlParser.parseDocument(XmlParser.java:481)
> at com.microstar.xml.XmlParser.doParse(XmlParser.java:159)
> at com.microstar.xml.XmlParser.parse(XmlParser.java:132)
> at ptolemy.moml.MoMLParser.parse(MoMLParser.java:1414)
> at ptolemy.moml.MoMLParser.parse(MoMLParser.java:1350)
> at ptolemy.moml.MoMLParser.parse(MoMLParser.java:1300)
> at
> ptolemy
> .actor
> .gui
> .ConfigurationApplication
> .readConfiguration(ConfigurationApplication.java:408)
> at
> ptolemy
> .vergil
> .VergilApplication
> ._createDefaultConfiguration(VergilApplication.java:284)
> ... 14 more
> Caused by: ptolemy.kernel.util.NameDuplicationException: Attempt to
> insert object named "_tableauFactory" into a container that already
> contains an object with that name.
> at ptolemy.kernel.util.NamedList.append(NamedList.java:133)
> at ptolemy.kernel.util.NamedObj._addAttribute(NamedObj.java:2073)
> at ptolemy.kernel.util.Attribute.setContainer(Attribute.java:398)
> at ptolemy.kernel.util.Attribute.<init>(Attribute.java:109)
> at ptolemy.kernel.util.Attribute.<init>(Attribute.java:86)
> at ptolemy.actor.gui.TableauFactory.<init>(TableauFactory.java:94)
> at
> ptolemy
> .vergil
> .fsm.modal.ModalTableauFactory.<init>(ModalTableauFactory.java:65)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun
> .reflect
> .NativeConstructorAccessorImpl
> .newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun
> .reflect
> .DelegatingConstructorAccessorImpl
> .newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at ptolemy.moml.MoMLParser._createInstance(MoMLParser.java:4180)
> at ptolemy.moml.MoMLParser._handlePropertyElement(MoMLParser.java:
> 5411)
> at ptolemy.moml.MoMLParser.startElement(MoMLParser.java:2894)
> ... 42 more
>
> Maybe I will clean cache and try this again? Do you have any other
> suggestions?
>
> Thanks,
> Subhav
>
>
> On Tue, Aug 25, 2009 at 1:41 PM, Derik Barseghian <barseghian at nceas.ucsb.edu
> > wrote:
> Hi Subhav,
>
> Sorry for the delay. I'm not sure why that happened.
> Yes, copying your existing ptolemy folder, and then executing ant
> update-ptolemy -Drev=54826 to move it back to the version that works
> with the kepler release-2.0.0-pre-alpha1-branch should work.
>
> Derik
>
>
>
> On Aug 22, 2009, at 9:56 PM, subhav mital wrote:
>
> Hi Derik,
>
> This is just what I followed and created a new folder where I
> checked out the new build.
> However, from the attached error.jpg image, it appears that Ptolemy
> modules did not get checked out. (Or was there an error in checking
> out the modules? )
>
> So would copying the ptolemy folder form the prev build to this
> folder and then executing ant update-ptolemy -Drev=54826 work fine?
>
> Thanks,
> Subhav
>
>
> On Thu, Aug 20, 2009 at 7:36 PM, Derik Barseghian <barseghian at nceas.ucsb.edu
> > wrote:
> Hi Subhav,
>
> What I would recommend is keeping them completely separate -- do a
> check-out into a different directory for release-2.0.0-pre-alpha1-
> branch, and then copy the files you created in 1.0 into the
> appropriate location in this checkout. That way if it gives you
> problems, your kepler 1.0 checkout is completely untouched. One
> thing to note is that when you do an ant clean-cache or ant clean-
> all in the build-area of the release-2.0.0-pre-alpha1-branch
> checkout, it will delete ~/.kepler, just like would happen if you
> did an ant clean-cache or ant clean all in the build-area of your
> 1.0 checkout would do. You definitely want to issue an ant clean-
> cache when switching between trying 1.0 and release-2.0.0-pre-alpha1-
> branch, as the contents of .kepler will be incompatible.
>
> Derik
>
>
>
> On Aug 19, 2009, at 5:34 PM, subhav mital wrote:
>
> Thanks for your help.
>
> So as I understand, I can check out the new build, without
> disturbing the old one and switch between builds by using the ant
> change-to command. Would this still be possible after I do ant-clean
> cache as mentioned in the steps specified here:
>
> https://kepler-project.org/developers/teams/build/documentation/build-system-instructions
> #downloading-the-build
>
> Thanks.
>
>
>
>
> On Wed, Aug 12, 2009 at 2:24 PM, Derik Barseghian <barseghian at nceas.ucsb.edu
> > wrote:
> Hi Subhav,
>
> I think that they will probably work, but it's possible that they
> won't. A lot of code has changed and been moved -- my guess is that
> you may just have to fix some of your import statements. If you're
> specifically relying on something we've changed, you may have
> problems. But you'd likely be facing those problems in the future
> anyways after we release 2.0 and if you wanted to upgrade. If
> bandwidth and harddrive space aren't an issue for you, I'd give it a
> try. Just keep the pre-alpha1 build separate from your current build
> in case you run into problems.
>
> Derik
>
>
>
> On Aug 11, 2009, at 11:14 PM, subhav mital wrote:
>
> Hi Derik,
>
> One concern: Will my self-created actors using Kepler-1.0 work in
> this latest build? Or would I have to recreate these actors again
> using the latest build?
>
> Thanks
>
>
> On Wed, Aug 12, 2009 at 1:54 AM, subhav mital
> <mital.subhav at gmail.com> wrote:
> Thanks so much. Will try this.
>
>
> On Tue, Aug 11, 2009 at 6:23 PM, Derik Barseghian <barseghian at nceas.ucsb.edu
> > wrote:
> Hi Subhav,
>
> I just checked and see the two bugs related to our below discussion
> are still open.
> http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3930
> http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3943
>
> Before I look into these to see if the problems still occur, let me
> ask: Is your current desire the same, to create and use two actors
> with Kepler-1.0? Since we have made many bug fixes and improvements
> to the development version of Kepler since we last spoke, if you
> don't need to user kepler-1.0 it might make sense for you to instead
> try working with our pre-alpha1-branch of Kepler. Setting up this
> branch requires the same assumptions be fulfilled as listed on the
> website for building the latest development version (https://kepler-project.org/developers/teams/build/documentation/build-system-instructions
> #assumptions), but to build the branch you instead use these commands:
>
> svn co https://code.kepler-project.org/code/kepler/branches/release-2.0.0-pre-alpha1-branch/modules/build-area
> build-area
> cd build-area
> ant clean-cache
> ant change-to -Dsuite=wrp -Dbranch=https://code.kepler-project.org/code/kepler/branches/release-2.0.0-pre-alpha1-branch
> ant update-ptolemy -Drev=54826
> ant run
>
> Derik
>
>
> <Error.jpg>
>
More information about the Kepler-dev
mailing list