[kepler-dev] Kepler-dev Digest, Vol 46, Issue 13
David Welker
david.v.welker at gmail.com
Thu Dec 18 19:37:50 PST 2008
Hello Siddeswara,
Can you run "ant clean" and "ant clean-cache" before running "ant run"?
If you get any problems after that, please send me the output and I can
help you further.
David
> Hello Chad,
> I checkout once again and tried to run kepler. But I am getting
> following error. Any help is appreciated.
> Buildfile: build.xml
>
> compile:
> [compile] Compiling common...
> [compile] Compiling directors...
> [compile] Compiling actors...
> [compile] Compiling ptolemy...
> [compile] <<< The module is ptolemy. Setting includes and excludes....
> [compile] Compiling core...
> [compile] Compiling 94 source files
> to /home/gur028/kepler/modules/core/target/classes
>
> [compile] /home/gur028/kepler/modules/core/src/org/ecoinformatics/util/DBConnection.java:67: org.ecoinformatics.util.DBConnection is not abstract and does not override abstract method createSQLXML() in java.sql.Connection
> [compile] public class DBConnection implements Connection {
> [compile] ^
> [compile] Note: Some input files use or override a deprecated API.
> [compile] Note: Recompile with -Xlint:deprecation for details.
> [compile] Note: Some input files use unchecked or unsafe operations.
> [compile] Note: Recompile with -Xlint:unchecked for details.
> [compile] 1 error
>
>
> Regards
> S.M.Guru
>
> On Fri, 2008-12-19 at 10:44 +1100, Chad Berkley wrote:
>
>> Hello,
>>
>> We've now changed the build again. Here are the current instructions:
>>
>> Here is how you would use the build system to build at the trunk
>> (assuming you want to check out the trunk, which will check out all
>> modules except for ptolemy.)
>>
>> svn co https://code.kepler-project.org/code/kepler/trunk kepler
>> cd kepler/modules/build-area
>> ant change-to -Dsuite=vanilla-trunk
>> ant run
>>
>> Here are the same commands, but with some explanation.
>>
>> 1.) svn co https://code.kepler-project.org/code/kepler/trunk kepler
>>
>> This checks out the trunk of kepler including all the modules. Except,
>> this doesn't check out ptolemy. This is a lengthy checkout, so be patient.
>>
>> 2.) cd kepler/modules/build-area
>>
>> You need to change to this directory because this is where the build.xml
>> that runs everything is located.
>>
>> 3.) ant change-to -Dsuite=vanilla-trunk
>>
>> You need to do this to download ptolemy. Note, that temporarily, this
>> will download Ptolemy to the directory ptolemy-trunk. The reason is
>> because there already exists a ptolemy directory that is in use for
>> another purpose.
>>
>> 4.) ant run
>>
>> This will compile the code, build the kar files, and execute Kepler.
>>
>> Hope this helps. As you requested, I am sending this email to kepler-dev
>> as well.
>>
>> Please also note that the checkout is a little larger now than it will
>> be in the future as we make necessary modifications.
>>
>> If you want to build eclipse .project files, use the 'ant eclipse'
>> command. David will have to add more here about how to use this with
>> eclipse, as I am not an eclipse user myself.
>>
>> Let us know if this doesn't work for you.
>>
>> Thanks,
>> chad
>>
>>
>> Siddeswara Guru wrote:
>>
>>> Hello All,
>>> I was trying to build kepler from the trunk But I am getting the
>>> following error. Any help is really appreciated. I am using linux and
>>> eclipse. It is not compiling from both eclipse and command line.
>>> The build was working fine when I followed original Chad's instruction.
>>> I update the SVN but now I cannot run kepler. Following are the errors I
>>> am getting.
>>>
>>> Buildfile: build.xml
>>>
>>> compile:
>>> [compile] Compiling common...
>>> [compile] Compiling directors...
>>> [compile] Compiling actors...
>>> [compile] Compiling ptolemy...
>>> [compile] <<< The module is ptolemy. Setting includes and excludes....
>>> [compile] Compiling core...
>>> [compile] Compiling 98 source files
>>> to /home/gur028/workspace/kepler/modules/core/target/classes
>>>
>>> [compile] /home/gur028/workspace/kepler/modules/core/src/org/kepler/objectmanager/ActorMetadata.java:65: package ptolemy.moml.unit does not exist
>>> [compile] import ptolemy.moml.unit.UnitAttribute;
>>> [compile] ^
>>>
>>> [compile] /home/gur028/workspace/kepler/modules/core/src/org/ecoinformatics/util/DBConnection.java:67: org.ecoinformatics.util.DBConnection is not abstract and does not override abstract method createSQLXML() in java.sql.Connection
>>> [compile] public class DBConnection implements Connection {
>>> [compile] ^
>>>
>>> [compile] /home/gur028/workspace/kepler/modules/core/src/org/kepler/objectmanager/ActorMetadata.java:241: cannot find symbol
>>> [compile] symbol : class UnitAttribute
>>> [compile] location: class org.kepler.objectmanager.ActorMetadata
>>> [compile] else if(a instanceof UnitAttribute)
>>> [compile] ^
>>>
>>> [compile] /home/gur028/workspace/kepler/modules/core/src/org/kepler/objectmanager/ActorMetadata.java:243: cannot find symbol
>>> [compile] symbol : class UnitAttribute
>>> [compile] location: class org.kepler.objectmanager.ActorMetadata
>>> [compile] attValue = ((UnitAttribute)a).getExpression();
>>> [compile] ^
>>>
>>> [compile] /home/gur028/workspace/kepler/modules/core/src/org/kepler/moml/filter/ClassChanges.java:53: cannot find symbol
>>> [compile] symbol : method put(java.lang.String,java.lang.String)
>>> [compile] location: class ptolemy.moml.filter.ClassChanges
>>> [compile]
>>> changes.put("org.kepler.provenance.ProvenanceListener",
>>> [compile] ^
>>>
>>> [compile] /home/gur028/workspace/kepler/modules/core/src/org/kepler/moml/filter/PortNameChanges.java:61: cannot find symbol
>>> [compile] symbol : method
>>> put(java.lang.String,java.util.HashMap<java.lang.String,java.lang.String>)
>>> [compile] location: class ptolemy.moml.filter.PortNameChanges
>>> [compile] changes.put("org.sdm.spa.DatabaseWriter",
>>> [compile] ^
>>>
>>> [compile] /home/gur028/workspace/kepler/modules/core/src/org/kepler/moml/filter/PortNameChanges.java:73: cannot find symbol
>>> [compile] symbol : method
>>> put(java.lang.String,java.util.HashMap<java.lang.String,java.lang.String>)
>>> [compile] location: class ptolemy.moml.filter.PortNameChanges
>>> [compile]
>>> changes.put("org.kepler.dataproxy.datasource.opendap.OpendapDataSource",
>>> [compile] ^
>>>
>>> [compile] /home/gur028/workspace/kepler/modules/core/src/org/kepler/moml/filter/PropertyClassChanges.java:60: cannot find symbol
>>> [compile] symbol : method
>>> put(java.lang.String,java.util.HashMap<java.lang.String,java.lang.String>)
>>> [compile] location: class ptolemy.moml.filter.PropertyClassChanges
>>> [compile] changes.put("org.geon.OpenDBConnection",
>>> openDatabaseClassChanges);
>>> [compile] ^
>>>
>>> [compile] /home/gur028/workspace/kepler/modules/core/src/org/kepler/moml/filter/PropertyClassChanges.java:70: cannot find symbol
>>> [compile] symbol : method
>>> put(java.lang.String,java.util.HashMap<java.lang.String,java.lang.String>)
>>> [compile] location: class ptolemy.moml.filter.PropertyClassChanges
>>> [compile]
>>> changes.put("org.kepler.dataproxy.datasource.opendap.OpendapDataSource",
>>> [compile] ^
>>> [compile] Note: Some input files use or override a deprecated API.
>>> [compile] Note: Recompile with -Xlint:deprecation for details.
>>> [compile] Note: Some input files use unchecked or unsafe operations.
>>> [compile] Note: Recompile with -Xlint:unchecked for details.
>>> [compile] 9 errors
>>>
>>> regards
>>> S.M.Guru
>>>
>>> On Fri, 2008-12-19 at 07:00 +1100, kepler-dev-request at kepler-project.org
>>> wrote:
>>>
>>>> Send Kepler-dev mailing list submissions to
>>>> kepler-dev at kepler-project.org
>>>>
>>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>>> or, via email, send a message with subject or body 'help' to
>>>> kepler-dev-request at kepler-project.org
>>>>
>>>> You can reach the person managing the list at
>>>> kepler-dev-owner at kepler-project.org
>>>>
>>>> When replying, please edit your Subject line so it is more specific
>>>> than "Re: Contents of Kepler-dev digest..."
>>>>
>>>>
>>>> Today's Topics:
>>>>
>>>> 1. Re: New instructions for building the trunk of Kepler...
>>>> (Christopher Brooks)
>>>> 2. Re: New instructions for building the trunk of Kepler...
>>>> (Matt Jones)
>>>> 3. Re: New instructions for building the trunk of Kepler...
>>>> (David Welker)
>>>>
>>>>
>>>> ----------------------------------------------------------------------
>>>>
>>>> Message: 1
>>>> Date: Thu, 18 Dec 2008 08:45:25 -0800
>>>> From: Christopher Brooks <cxh at eecs.berkeley.edu>
>>>> Subject: Re: [kepler-dev] New instructions for building the trunk of
>>>> Kepler...
>>>> To: David Welker <david.v.welker at gmail.com>
>>>> Cc: kepler-dev <kepler-dev at ecoinformatics.org>
>>>> Message-ID: <494A7E25.9090701 at eecs.berkeley.edu>
>>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>>
>>>> Hi David,
>>>> Congrats! The build system looks pretty good. Below are
>>>> some suggestions
>>>>
>>>> 1. kepler/INSTALL.txt needs updating.
>>>> 2. kepler/modules/build-area/README.txt says:
>>>> > The latest version of quick instructions on how to build Kepler using
>>>> > the Extension Build System
>>>> > can be found here:
>>>> >
>>>> >
>>>> https://dev.kepler-project.org/developers/teams/build/systems/build-system/extension-build-system/view
>>>> >
>>>> >A possibly out-of-date version of this document is reproduced below:
>>>> ...
>>>>
>>>> It would be good to commit to updating the README.txt file instead of
>>>> updating the a webpage. The primary reason is that people who
>>>> are building might not have web access.
>>>>
>>>> 3. In kepler/modules/build-area/README.txt, I ran
>>>> ant change-to -Dsuite=vanilla-1.0
>>>> which downloaded a jar file. It would be nice if this download was
>>>> not required, perhaps if the jar file was checked in or built.
>>>> The primary reason is that if I'm on the plane and want to try out
>>>> Kepler from source, I can't.
>>>>
>>>> 4. There should probably be a top-level kepler/build.xml file that
>>>> runs the basic commands to build and run Kepler. The reason is
>>>> that users will expect to be able to run ant in the top-level
>>>> directory and have something happen. The kepler/build.xml
>>>> file need not be too complex, but it should have the basics
>>>> like run, compile and clean
>>>>
>>>> 5. When I'm in kepler/modules/build-area, if I run "ant" with
>>>> no arguments, I should get back a list of the possible targets.
>>>>
>>>> 6. When I'm in kepler/modules/build-area, what are the other
>>>> possibilities for "ant change-to"?
>>>>
>>>> 7. I want to add targets for running findbugs and the Javadoc
>>>> doccheck. Where should these go?
>>>>
>>>> 8. We really need a nightly Kepler build and a continuous build.
>>>>
>>>> Again, these are all just small things and I'm sure that many
>>>> of them are on a todo list somewhere. Again, congrats on getting
>>>> this going.
>>>>
>>>> _Christopher
>>>>
>>>> David Welker wrote:
>>>>
>>>>> Hi Matt and everyone:
>>>>>
>>>>> Here is how you would use the build system to build at the trunk
>>>>> (assuming you want to check out the trunk, which will check out all
>>>>> modules except for ptolemy.)
>>>>>
>>>>> svn co https://code.kepler-project.org/code/kepler/trunk kepler
>>>>> cd kepler/modules/build-area
>>>>> ant change-to -Dsuite=vanilla-trunk
>>>>> ant run
>>>>>
>>>>> Here are the same commands, but with some explanation.
>>>>>
>>>>> 1.) svn co https://code.kepler-project.org/code/kepler/trunk kepler
>>>>>
>>>>> This checks out the trunk of kepler including all the modules. Except,
>>>>> this doesn't check out ptolemy. This is a lengthy checkout, so be patient.
>>>>>
>>>>> 2.) cd kepler/modules/build-area
>>>>>
>>>>> You need to change to this directory because this is where the build.xml
>>>>> that runs everything is located.
>>>>>
>>>>> 3.) ant change-to -Dsuite=vanilla-trunk
>>>>>
>>>>> You need to do this to download ptolemy. Note, that temporarily, this
>>>>> will download Ptolemy to the directory ptolemy-trunk. The reason is
>>>>> because there already exists a ptolemy directory that is in use for
>>>>> another purpose.
>>>>>
>>>>> 4.) ant run
>>>>>
>>>>> This will compile the code, build the kar files, and execute Kepler.
>>>>>
>>>>> Hope this helps. As you requested, I am sending this email to kepler-dev
>>>>> as well.
>>>>>
>>>>> Please also note that the checkout is a little larger now than it will
>>>>> be in the future as we make necessary modifications.
>>>>>
>>>>> _______________________________________________
>>>>> Kepler-dev mailing list
>>>>> Kepler-dev at kepler-project.org
>>>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>>>>
>>>> --
>>>> Christopher Brooks (cxh at eecs berkeley edu) University of California
>>>> CHESS Executive Director US Mail: 337 Cory Hall
>>>> Programmer/Analyst CHESS/Ptolemy/Trust Berkeley, CA 94720-1774
>>>> ph: 510.643.9841 fax:510.642.2718 (Office: 545Q Cory)
>>>> home: (F-Tu) 707.665.0131 (W-F) 510.655.5480
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> Message: 2
>>>> Date: Thu, 18 Dec 2008 09:23:17 -0900
>>>> From: "Matt Jones" <jones at nceas.ucsb.edu>
>>>> Subject: Re: [kepler-dev] New instructions for building the trunk of
>>>> Kepler...
>>>> To: "Christopher Brooks" <cxh at eecs.berkeley.edu>
>>>> Cc: kepler-dev <kepler-dev at ecoinformatics.org>
>>>> Message-ID:
>>>> <fa9a3c5e0812181023j14dcfb16l80c320489ffd7861 at mail.gmail.com>
>>>> Content-Type: text/plain; charset=ISO-8859-1
>>>>
>>>> Hi Christopher,
>>>>
>>>> Some comments to your email below...
>>>>
>>>> On Thu, Dec 18, 2008 at 7:45 AM, Christopher Brooks
>>>> <cxh at eecs.berkeley.edu> wrote:
>>>>
>>>>> Hi David,
>>>>> Congrats! The build system looks pretty good. Below are
>>>>> some suggestions
>>>>>
>>>>> 1. kepler/INSTALL.txt needs updating.
>>>>> 2. kepler/modules/build-area/README.txt says:
>>>>>
>>>>>> The latest version of quick instructions on how to build Kepler using >
>>>>>> the Extension Build System
>>>>>> can be found here:
>>>>>>
>>>>>>
>>>>>> https://dev.kepler-project.org/developers/teams/build/systems/build-system/extension-build-system/view
>>>>>>
>>>>>> A possibly out-of-date version of this document is reproduced below:
>>>>>>
>>>>> ...
>>>>>
>>>>> It would be good to commit to updating the README.txt file instead of
>>>>> updating the a webpage. The primary reason is that people who
>>>>> are building might not have web access.
>>>>>
>>>> I agree -- it would be best to keep the build instructions up to date
>>>> in the SVN checkout.
>>>>
>>>>
>>>>> 3. In kepler/modules/build-area/README.txt, I ran
>>>>> ant change-to -Dsuite=vanilla-1.0
>>>>> which downloaded a jar file. It would be nice if this download was
>>>>> not required, perhaps if the jar file was checked in or built.
>>>>> The primary reason is that if I'm on the plane and want to try out
>>>>> Kepler from source, I can't.
>>>>>
>>>> I also agree with this. We'll need to discuss further how this core
>>>> trunk module build works while we continue to refactor the core into
>>>> more functionally distinct and smaller modules.
>>>>
>>>>
>>>>> 4. There should probably be a top-level kepler/build.xml file that
>>>>> runs the basic commands to build and run Kepler. The reason is
>>>>> that users will expect to be able to run ant in the top-level
>>>>> directory and have something happen. The kepler/build.xml
>>>>> file need not be too complex, but it should have the basics
>>>>> like run, compile and clean
>>>>>
>>>> I also would like this. In every other project the main build file is
>>>> at the root of the development tree and can be run immediately after
>>>> checkout. We should be able to achieve the same while maintaining the
>>>> whole ability to switch modules.
>>>>
>>>>
>>>>> 5. When I'm in kepler/modules/build-area, if I run "ant" with
>>>>> no arguments, I should get back a list of the possible targets.
>>>>>
>>>> An alternative would be to have 'ant' run the default trunk build,
>>>> while the standard 'ant -projecthelp' gives the list of targets. I
>>>> could go either way on this.
>>>>
>>>>
>>>>> 6. When I'm in kepler/modules/build-area, what are the other
>>>>> possibilities for "ant change-to"?
>>>>>
>>>> Any of the other defined suites or modules that are in the modules
>>>> subdirectory. That this is confusing is one of the reasons we need
>>>> the root level trunk build to be more transparent to developers who
>>>> are new to the system.
>>>>
>>>>
>>>>> 7. I want to add targets for running findbugs and the Javadoc
>>>>> doccheck. Where should these go?
>>>>>
>>>> Can't they just be added to the build.xml file, either directly or via
>>>> an import?
>>>>
>>>>
>>>>> 8. We really need a nightly Kepler build and a continuous build.
>>>>>
>>>> We have the nightly build via NMI. Its on Chad and David's todo lists
>>>> to make this work again with the newly rearranged build. Currently it
>>>> is scheduled to run twice a day. We could change this to run
>>>> continuously, immediately starting a new build after the old one
>>>> finishes, and only emailing results if there is an error. Would that
>>>> be helpful?
>>>>
>>>> Matt
>>>>
>>>>
>>>>> Again, these are all just small things and I'm sure that many
>>>>> of them are on a todo list somewhere. Again, congrats on getting
>>>>> this going.
>>>>>
>>>>> _Christopher
>>>>>
>>>>> David Welker wrote:
>>>>>
>>>>>> Hi Matt and everyone:
>>>>>>
>>>>>> Here is how you would use the build system to build at the trunk (assuming
>>>>>> you want to check out the trunk, which will check out all modules except for
>>>>>> ptolemy.)
>>>>>>
>>>>>> svn co https://code.kepler-project.org/code/kepler/trunk kepler
>>>>>> cd kepler/modules/build-area
>>>>>> ant change-to -Dsuite=vanilla-trunk
>>>>>> ant run
>>>>>>
>>>>>> Here are the same commands, but with some explanation.
>>>>>>
>>>>>> 1.) svn co https://code.kepler-project.org/code/kepler/trunk kepler
>>>>>>
>>>>>> This checks out the trunk of kepler including all the modules. Except,
>>>>>> this doesn't check out ptolemy. This is a lengthy checkout, so be patient.
>>>>>>
>>>>>> 2.) cd kepler/modules/build-area
>>>>>>
>>>>>> You need to change to this directory because this is where the build.xml
>>>>>> that runs everything is located.
>>>>>>
>>>>>> 3.) ant change-to -Dsuite=vanilla-trunk
>>>>>>
>>>>>> You need to do this to download ptolemy. Note, that temporarily, this will
>>>>>> download Ptolemy to the directory ptolemy-trunk. The reason is because there
>>>>>> already exists a ptolemy directory that is in use for another purpose.
>>>>>>
>>>>>> 4.) ant run
>>>>>>
>>>>>> This will compile the code, build the kar files, and execute Kepler.
>>>>>>
>>>>>> Hope this helps. As you requested, I am sending this email to kepler-dev
>>>>>> as well.
>>>>>>
>>>>>> Please also note that the checkout is a little larger now than it will be
>>>>>> in the future as we make necessary modifications.
>>>>>>
>>>>>> _______________________________________________
>>>>>> Kepler-dev mailing list
>>>>>> Kepler-dev at kepler-project.org
>>>>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>>>>>
>>>>> --
>>>>> Christopher Brooks (cxh at eecs berkeley edu) University of California
>>>>> CHESS Executive Director US Mail: 337 Cory Hall
>>>>> Programmer/Analyst CHESS/Ptolemy/Trust Berkeley, CA 94720-1774
>>>>> ph: 510.643.9841 fax:510.642.2718 (Office: 545Q Cory)
>>>>> home: (F-Tu) 707.665.0131 (W-F) 510.655.5480
>>>>> _______________________________________________
>>>>> Kepler-dev mailing list
>>>>> Kepler-dev at kepler-project.org
>>>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>>>>
>>>>>
>>>> --
>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>> Matthew B. Jones
>>>> Director of Informatics Research and Development
>>>> National Center for Ecological Analysis and Synthesis (NCEAS)
>>>> UC Santa Barbara
>>>> jones at nceas.ucsb.edu Ph: 1-907-523-1960
>>>> http://www.nceas.ucsb.edu/ecoinfo
>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> Message: 3
>>>> Date: Thu, 18 Dec 2008 10:52:41 -0800
>>>> From: David Welker <david.v.welker at gmail.com>
>>>> Subject: Re: [kepler-dev] New instructions for building the trunk of
>>>> Kepler...
>>>> To: Matt Jones <jones at nceas.ucsb.edu>
>>>> Cc: kepler-dev <kepler-dev at ecoinformatics.org>
>>>> Message-ID: <494A9BF9.8040101 at post.harvard.edu>
>>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>>
>>>> Hi Christopher and Matt,
>>>>
>>>> I thought I would chime in:
>>>>
>>>>> Hi Christopher,
>>>>>
>>>>> Some comments to your email below...
>>>>>
>>>>> On Thu, Dec 18, 2008 at 7:45 AM, Christopher Brooks
>>>>> <cxh at eecs.berkeley.edu> wrote:
>>>>>
>>>>>
>>>>>> Hi David,
>>>>>> Congrats! The build system looks pretty good. Below are
>>>>>> some suggestions
>>>>>>
>>>>>> 1. kepler/INSTALL.txt needs updating.
>>>>>> 2. kepler/modules/build-area/README.txt says:
>>>>>>
>>>>>>
>>>>>>> The latest version of quick instructions on how to build Kepler using >
>>>>>>> the Extension Build System
>>>>>>> can be found here:
>>>>>>>
>>>>>>>
>>>>>>> https://dev.kepler-project.org/developers/teams/build/systems/build-system/extension-build-system/view
>>>>>>>
>>>>>>> A possibly out-of-date version of this document is reproduced below:
>>>>>>>
>>>>>>>
>>>>>> ...
>>>>>>
>>>>>> It would be good to commit to updating the README.txt file instead of
>>>>>> updating the a webpage. The primary reason is that people who
>>>>>> are building might not have web access.
>>>>>>
>>>>>>
>>>>> I agree -- it would be best to keep the build instructions up to date
>>>>> in the SVN checkout.
>>>>>
>>>>>
>>>>>
>>>>>> 3. In kepler/modules/build-area/README.txt, I ran
>>>>>> ant change-to -Dsuite=vanilla-1.0
>>>>>> which downloaded a jar file. It would be nice if this download was
>>>>>> not required, perhaps if the jar file was checked in or built.
>>>>>> The primary reason is that if I'm on the plane and want to try out
>>>>>> Kepler from source, I can't.
>>>>>>
>>>>>>
>>>>> I also agree with this. We'll need to discuss further how this core
>>>>> trunk module build works while we continue to refactor the core into
>>>>> more functionally distinct and smaller modules.
>>>>>
>>>>>
>>>>>
>>>> For Kepler 1.0, we download a jar rather than source because 1.) it is a
>>>> faster download and 2.) compiling is much faster. The jar file that you
>>>> download actually contains the source and already compiled class files
>>>> for both Kepler 1.0 and Ptolemy within their own jars. Any IDE should be
>>>> able to read this source if you are interested.
>>>>
>>>> For Kepler trunk, in contrast, you download the modules that constitute
>>>> the base system (common, core, util, actors, and directors) but probably
>>>> soon some additional modules soon as well as Ptolemy just as they are
>>>> found in the repository. The download takes a little longer as does
>>>> compilation since you need to compile both the base system and ptolemy,
>>>> whereas when working with 1.0 these are precompiled.
>>>>
>>>>>> 4. There should probably be a top-level kepler/build.xml file that
>>>>>> runs the basic commands to build and run Kepler. The reason is
>>>>>> that users will expect to be able to run ant in the top-level
>>>>>> directory and have something happen. The kepler/build.xml
>>>>>> file need not be too complex, but it should have the basics
>>>>>> like run, compile and clean
>>>>>>
>>>>>>
>>>>> I also would like this. In every other project the main build file is
>>>>> at the root of the development tree and can be run immediately after
>>>>> checkout. We should be able to achieve the same while maintaining the
>>>>> whole ability to switch modules.
>>>>>
>>>>>
>>>> We can make a build file that calls that build.xml in the build-area
>>>> subdirectory. The reason this is like this is because Eclipse does not
>>>> allow for nested projects. The modules need to be in their own projects
>>>> because otherwise you have name clashes that confuse Eclipse due to
>>>> overrides. Basically, if you want Eclipse to be able to see the
>>>> build.xml file and associated files, they need to be peers to the
>>>> modules, rather than one level higher.
>>>>
>>>>>> 5. When I'm in kepler/modules/build-area, if I run "ant" with
>>>>>> no arguments, I should get back a list of the possible targets.
>>>>>>
>>>>>>
>>>>> An alternative would be to have 'ant' run the default trunk build,
>>>>> while the standard 'ant -projecthelp' gives the list of targets. I
>>>>> could go either way on this.
>>>>>
>>>>>
>>>>>> 6. When I'm in kepler/modules/build-area, what are the other
>>>>>> possibilities for "ant change-to"?
>>>>>>
>>>>>>
>>>>> Any of the other defined suites or modules that are in the modules
>>>>> subdirectory. That this is confusing is one of the reasons we need
>>>>> the root level trunk build to be more transparent to developers who
>>>>> are new to the system.
>>>>>
>>>>>
>>>> I am going to add a command that will query the repository and tell you
>>>> what the other possibilities are for change-to. But the answer is any
>>>> module that contains a modules.txt in a module-info directory is a
>>>> candidate for the change-to command.
>>>>
>>>>>> 7. I want to add targets for running findbugs and the Javadoc
>>>>>> doccheck. Where should these go?
>>>>>>
>>>>>>
>>>>> Can't they just be added to the build.xml file, either directly or via
>>>>> an import?
>>>>>
>>>>>
>>>> Sure. But you have to keep in mind that you are working with a differing
>>>> set of modules as specified in modules.txt.
>>>>
>>>>
>>>>>> 8. We really need a nightly Kepler build and a continuous build.
>>>>>>
>>>>>>
>>>>> We have the nightly build via NMI. Its on Chad and David's todo lists
>>>>> to make this work again with the newly rearranged build. Currently it
>>>>> is scheduled to run twice a day. We could change this to run
>>>>> continuously, immediately starting a new build after the old one
>>>>> finishes, and only emailing results if there is an error. Would that
>>>>> be helpful?
>>>>>
>>>>> Matt
>>>>>
>>>>>
>>>>>
>>>>>> Again, these are all just small things and I'm sure that many
>>>>>> of them are on a todo list somewhere. Again, congrats on getting
>>>>>> this going.
>>>>>>
>>>>>> _Christopher
>>>>>>
>>>>>> David Welker wrote:
>>>>>>
>>>>>>
>>>>>>> Hi Matt and everyone:
>>>>>>>
>>>>>>> Here is how you would use the build system to build at the trunk (assuming
>>>>>>> you want to check out the trunk, which will check out all modules except for
>>>>>>> ptolemy.)
>>>>>>>
>>>>>>> svn co https://code.kepler-project.org/code/kepler/trunk kepler
>>>>>>> cd kepler/modules/build-area
>>>>>>> ant change-to -Dsuite=vanilla-trunk
>>>>>>> ant run
>>>>>>>
>>>>>>> Here are the same commands, but with some explanation.
>>>>>>>
>>>>>>> 1.) svn co https://code.kepler-project.org/code/kepler/trunk kepler
>>>>>>>
>>>>>>> This checks out the trunk of kepler including all the modules. Except,
>>>>>>> this doesn't check out ptolemy. This is a lengthy checkout, so be patient.
>>>>>>>
>>>>>>> 2.) cd kepler/modules/build-area
>>>>>>>
>>>>>>> You need to change to this directory because this is where the build.xml
>>>>>>> that runs everything is located.
>>>>>>>
>>>>>>> 3.) ant change-to -Dsuite=vanilla-trunk
>>>>>>>
>>>>>>> You need to do this to download ptolemy. Note, that temporarily, this will
>>>>>>> download Ptolemy to the directory ptolemy-trunk. The reason is because there
>>>>>>> already exists a ptolemy directory that is in use for another purpose.
>>>>>>>
>>>>>>> 4.) ant run
>>>>>>>
>>>>>>> This will compile the code, build the kar files, and execute Kepler.
>>>>>>>
>>>>>>> Hope this helps. As you requested, I am sending this email to kepler-dev
>>>>>>> as well.
>>>>>>>
>>>>>>> Please also note that the checkout is a little larger now than it will be
>>>>>>> in the future as we make necessary modifications.
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Kepler-dev mailing list
>>>>>>> Kepler-dev at kepler-project.org
>>>>>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>>>>>>
>>>>>>>
>>>>>> --
>>>>>> Christopher Brooks (cxh at eecs berkeley edu) University of California
>>>>>> CHESS Executive Director US Mail: 337 Cory Hall
>>>>>> Programmer/Analyst CHESS/Ptolemy/Trust Berkeley, CA 94720-1774
>>>>>> ph: 510.643.9841 fax:510.642.2718 (Office: 545Q Cory)
>>>>>> home: (F-Tu) 707.665.0131 (W-F) 510.655.5480
>>>>>> _______________________________________________
>>>>>> Kepler-dev mailing list
>>>>>> Kepler-dev at kepler-project.org
>>>>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>> ------------------------------
>>>>
>>>> _______________________________________________
>>>> Kepler-dev mailing list
>>>> Kepler-dev at kepler-project.org
>>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>>>
>>>>
>>>> End of Kepler-dev Digest, Vol 46, Issue 13
>>>> ******************************************
>>>>
>>> _______________________________________________
>>> Kepler-dev mailing list
>>> Kepler-dev at kepler-project.org
>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>>
More information about the Kepler-dev
mailing list