Nuggets/Slinkees and each exported Object should have more meta-information

[GoogleCodeExporter]

What steps will reproduce the problem?
1. use SAPLink

What is the expected output? What do you see instead?

If you work with different source systems and different development states,
  you easily get confused by different xml-files having the same name but
not the same content (e.g. equally called objects from different systems etc.).

I'd like to have a version structure in the XML of a Nugget and each object
stanza consisting of the following information:
1. date/time of export
2. exporting system name
3. version (this could be an auto-incrementing number per object)

This information should also be displayed by SAPLink when displaying
contents, exporting or importing etc.

What version of SAP are you using?
SAP_ABA Release 640 / Level: 3
SAP_BASIS Release 640 / Level: 3

What version of SAPlink are you using:
0.1.2

Original issue reported on code.google.com by nicola.f...@gmail.com on 27 Dec 2006 at 10:23

[GoogleCodeExporter]

Im not sure i understand what you mean here, "different development states," 
please
clarify.

As for versioning in general this is a topic we will be working on in coming
versions.  We think all obejcts will need to have versiona and nuggets should 
check
them when they come in.  This is a topic we are still discussing so, i will 
refer you
to the group for now.

Original comment by daniel.m...@gmail.com on 28 Dec 2006 at 3:37

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

by "different development state" I mean the state of custom written code, the 
one you
typically want to import/export with SAPLink.

Original comment by nicola.f...@gmail.com on 2 Jan 2007 at 11:05

[GoogleCodeExporter]

Yea we will add versioning at some point in the future. We are also going to 
start
work on a development roadmap so people know what we are working on.  One of the
outcomes of this is that we think all nuggets will carry version dependency and 
the
version of the components.

Original comment by daniel.m...@gmail.com on 3 Jan 2007 at 3:29

• Changed state: Duplicate