Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XSD schema files and documentation for docu file format #75

Closed
bruderol opened this issue Dec 8, 2013 · 11 comments
Closed

XSD schema files and documentation for docu file format #75

bruderol opened this issue Dec 8, 2013 · 11 comments
Assignees
Labels

Comments

@bruderol
Copy link
Member

bruderol commented Dec 8, 2013

As users of other technologies we want to have access to the XSD files for the documentation file formats to be able to generate documentation files without using the Java scenarioo-api. This will enable other technologies (like Javascript, .NET, etc.) to use Scenarioo.

  • XSD are downloadable in WIKI / Github.
  • file/folder structure is described in WIKI such that anybody could write a documentation without using the Java API.
@forkch
Copy link
Member

forkch commented Dec 18, 2013

are you working on this? otherwise I will implement this since sergio asked again

@forkch
Copy link
Member

forkch commented Dec 18, 2013

gradle task generates schema but need to upload it somewhere

@bruderol
Copy link
Member Author

Sorry erst jetzt gesehen. Nein, bin nicht daran. Nächstes mal besser anrufen.
Ja, das wäre wichtig.

On 18.12.2013, at 10:59, Ben notifications@github.com wrote:

are you working on this? otherwise I will implement this since sergio asked again


Reply to this email directly or view it on GitHub.

@bruderol
Copy link
Member Author

i adjusted the name of the schema and added namespaces.
what is missing: make it somehow available (download link)

@xeronimus
Copy link
Member

it's generated by the build, right?
So you don't have to make it available. I could checkout scenarioo and run the build, in order to generate the schema file(s) for myself?

or you could commit it nevertheless.....

@xeronimus
Copy link
Member

you wrote "i adjusted the name of the schema and added namespaces." can you commit these changes ? I don't see them in the repo

@adiherzog
Copy link
Member

I get this error when calling "gradle clean war":
A problem occurred evaluating project ':scenarioo-api'.

destination directory "/home/ngUSD/Code/scenarioo/scenarioo-api/scenarioo-schema" does not exist or is not a directory

@sergio: Mach Ferie ;-)

@forkch
Copy link
Member

forkch commented Dec 26, 2013

fixed the generation of the scnearioo-schema directory

@forkch forkch closed this as completed Dec 26, 2013
bruderol added a commit that referenced this issue Jan 2, 2014
Changed the directory where the schema is created to src/main/resources/scenarioo-schemas
This ensures that the schema will automatically be included in the packaged and published jar.
I still had problem with generating the schema from eclipse.
Now the directory is taken properly (not just only its name).
@bruderol
Copy link
Member Author

bruderol commented Jan 5, 2014

Just a remark:
the CI build (jenkins) is now configured to archive the XSD from the build directory and therefore to include the
XSD also in the release ZIP.

Therefore it would not be necessary to commit the schema into the source repository anymore but generate it directly into the build directory under resources/main directly.

Anybody who needs the schema could get it from the CI server, instead of from the code repository.

But on the other hand checking it in has the advantage that we will recognize when we do a change that also changes the schema.

@adiherzog
Copy link
Member

I think we should leave it checked in (as it currently is), because it's quite important to recognize changes to the xsd.

@bruderol
Copy link
Member Author

bruderol commented Jan 9, 2014

👍

bruderol added a commit that referenced this issue Jan 12, 2014
Changed the directory where the schema is created to src/main/resources/scenarioo-schemas
This ensures that the schema will automatically be included in the packaged and published jar.
I still had problem with generating the schema from eclipse.
Now the directory is taken properly (not just only its name).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants