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

Schemas from src/resources/org/jpeek/xsd must be referenced in generated XMLs #135

Closed
skapral opened this issue Jan 31, 2018 · 23 comments
Closed
Labels

Comments

@skapral
Copy link
Contributor

skapral commented Jan 31, 2018

Subj. First discussed in #133.

We need to make references to the schemas explicit in generated XML documents. This will bring transparency in semantics of the generated XML files and will make their support easier.

@0crat
Copy link
Collaborator

0crat commented Jan 31, 2018

@yegor256/z please, pay attention to this issue

@yegor256 yegor256 added the bug label Jan 31, 2018
@0crat 0crat added the scope label Jan 31, 2018
@0crat
Copy link
Collaborator

0crat commented Jan 31, 2018

Job #135 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Jan 31, 2018

Bug was reported, see §29: +15 points just awarded to @skapral/z, total is +105

@0crat
Copy link
Collaborator

0crat commented Feb 15, 2018

The job #135 assigned to @llorllale/z, here is why. The budget is 30 minutes, see §4. Please, read §8 and §9. If the task is not clear, read this and this.

@llorllale
Copy link
Contributor

@yegor256 can I take the liberty to define namespaces for these schemas? I was thinking of using this for metric.xsd: http://www.jpeek.org/2018/schema/metric

@llorllale
Copy link
Contributor

llorllale commented Feb 15, 2018

@yegor256
Copy link
Member

yegor256 commented Feb 15, 2018

@llorllale let's use the schema without a namespace, it will be easier for everything. This is what we have now. No need to add any namespaces.

@llorllale
Copy link
Contributor

@0crat status

@0crat
Copy link
Collaborator

0crat commented Feb 19, 2018

@0crat status (here)

@llorllale This is what I know about this job, as in §32:

llorllale added a commit to llorllale/jpeek that referenced this issue Feb 20, 2018
As per PR review:
* fixed indentation in Report.java
@0crat
Copy link
Collaborator

0crat commented Feb 20, 2018

@llorllale/z this job was assigned to you 5 days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

llorllale added a commit to llorllale/jpeek that referenced this issue Feb 21, 2018
@llorllale
Copy link
Contributor

@0crat waiting

@0crat
Copy link
Collaborator

0crat commented Feb 23, 2018

@0crat waiting (here)

@llorllale The impediment for #135 was registered successfully by @llorllale/z

@llorllale
Copy link
Contributor

@yegor256 can we close this?

@yegor256
Copy link
Member

yegor256 commented Mar 1, 2018

@llorllale thanks

@yegor256 yegor256 closed this as completed Mar 1, 2018
@0crat
Copy link
Collaborator

0crat commented Mar 1, 2018

@ypshenychka/z please review this job, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

@ypshenychka
Copy link

@0crat quality good

@0crat
Copy link
Collaborator

0crat commented Mar 1, 2018

QA review completed: +8 points just awarded to @ypshenychka/z

@0crat 0crat removed the scope label Mar 1, 2018
@0crat
Copy link
Collaborator

0crat commented Mar 1, 2018

Order was finished, quality was "good": +35 points just awarded to @llorllale/z

@0crat
Copy link
Collaborator

0crat commented Mar 1, 2018

@0crat quality good (here)

@ypshenychka The job #135 is now out of scope

@0pdd
Copy link
Collaborator

0pdd commented Jan 4, 2019

@skapral 3 puzzles #224, #226, #227 are still not solved; solved: #225.

@0pdd
Copy link
Collaborator

0pdd commented Apr 11, 2019

@skapral 2 puzzles #224, #227 are still not solved; solved: #225, #226.

@0pdd
Copy link
Collaborator

0pdd commented May 1, 2019

@skapral 2 puzzles #224, #327 are still not solved; solved: #225, #226, #227.

@0pdd
Copy link
Collaborator

0pdd commented Nov 12, 2019

@skapral the puzzle #327 is still not solved; solved: #224, #225, #226, #227.

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

6 participants