Structure of the <metadata> element in the .reahlproject file

[Hendrik du Toit]

My naming convention for my directory structure in my development environment is currently not to keep the code in a directory (root directory) with the same name as the project name i.e. when the "hello" example is extracted, it is extracted in to a "hello" directory which then become the "root directory" for the project.  My naming convention is to rather keep it in a "..\hello\code" directory.  The "reahl build" command then creates a wheel with the name of "Code-0.0-py2.py3-none-any.whl" which is not desirable.  From reading the documentation it seems that it can be changed in the <metadata>  element in the .reahlproject file.
1.  SI this correct?
2.  If it is, what is the structure of the <metadata> element.  I tried to figure it our from the documentation but I failed.

[Craig Sparks]

Hi Hendrik,

You are spot on.

In your .reahlproject you can add the metadata yourself, so that reahl does not use defaults.

For reference, you can look here:

https://www.reahl.org/docs/5.0/devtools/xmlref.d.html?highlight=xml#metadata

You can also have a look at the schema evolution tutorial (tutorial.migrationexamplebootstrap) which has metadata defined in its ".reahlproject". It does not define project_name, which I think you should add for your purpose.

https://www.reahl.org/docs/5.0/tutorial/schemaevolution.d.html

Here is a snippet of a .reahlproject defining all of the metadata:

...

<metadata type="reahlproject">
 <info name="project_name">
  mymigrationexample
 </info>
 <info name="version">
  0.0
 </info>
 <info name="description">
  Migration example
 </info>
 <info name="long_description">
  An example to show how migration works in Reahl
 </info>
 <info name="maintainer_name">
  Reahl (Pty) Ltd
 </info>
 <info name="maintainer_email">
  in...@reahl.org
 </info>
 <info name="url">
  http://www.reahl.org
 </info>
</metadata>
...

This will cause reahl to build a package named "mymigrationexample".

Regards,
Craig. 

On 4/15/21 11:04 PM, Hendrik du Toit wrote:

My naming convention for my directory structure in my development environment is currently not to keep the code in a directory (root directory) with the same name as the project name i.e. when the "hello" example is extracted, it is extracted in to a "hello" directory which then become the "root directory" for the project.  My naming convention is to rather keep it in a "..\hello\code" directory.  The "reahl build" command then creates a wheel with the name of "Code-0.0-py2.py3-none-any.whl" which is not desirable.  From reading the documentation it seems that it can be changed in the <metadata>  element in the .reahlproject file.
1.  SI this correct?

2.  If it is, what is the structure of the <metadata> element.  I tried to figure it our from the documentation but I failed. --
You received this message because you are subscribed to the Google Groups "Reahl discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reahl-discus...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/reahl-discuss/fd7293ec-4cab-41f9-b95d-8d9b0b5977d3n%40googlegroups.com.