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

python script #1

Open
sebschlicht opened this issue Apr 11, 2014 · 5 comments
Open

python script #1

sebschlicht opened this issue Apr 11, 2014 · 5 comments
Assignees

Comments

@sebschlicht
Copy link
Member

A python script is missing to generate the table displayed in the readme file.
We would end up updating versions manually otherwise.

@renepickhardt
Copy link
Member

should the python script also generate a new version of the parental pom? this would be more work

@sebschlicht
Copy link
Member Author

No, the Version should be edited in the pom manually once and then the script would Export them to be displayed at github

On 12. April 2014 11:00:28 MESZ, renepickhardt notifications@github.com wrote:

should the python script also generate a new version of the parental
pom? this would be more work


Reply to this email directly or view it on GitHub:
#1 (comment)

Mobil gesendet

@lschmelzeisen
Copy link
Member

Wouldn't it make sense to just take all the artifact versions from http://develop.metalcon.de:8080/mvn/ (Rene has wrote a parser for this anyway). And just generate a parental pom and readme table of that?

@sebschlicht
Copy link
Member Author

No. Maybe you Tarent aware of a new Version that has been deployed between your code update and the pom update. I think its Bettler Tod define the combination oft versions that are Wirkung for your Software, at least, yourself.

On 12. April 2014 13:10:41 MESZ, Lukas Schmelzeisen notifications@github.com wrote:

Wouldn't it make sense to just take all the artifact versions from
http://develop.metalcon.de:8080/mvn/ (Rene has wrote a parser for this
anyway). And just generate a parental pom and readme table of that?


Reply to this email directly or view it on GitHub:
#1 (comment)

Mobil gesendet

@sebschlicht
Copy link
Member Author

No. Maybe you Tarent aware of a new Version that has been deployed between your code update and the pom update. I think its Bettler Tod define the combination oft versions that are Wirkung for your Software, at least, yourself.

On 12. April 2014 13:10:41 MESZ, Lukas Schmelzeisen notifications@github.com wrote:

Wouldn't it make sense to just take all the artifact versions from
http://develop.metalcon.de:8080/mvn/ (Rene has wrote a parser for this
anyway). And just generate a parental pom and readme table of that?


Reply to this email directly or view it on GitHub:
#1 (comment)

Mobil gesendet

Mobil gesendet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants