Skip to content

have older versions in the same p2 repo -> Enide repository #100

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

Closed
paulvi opened this issue Dec 11, 2013 · 3 comments
Closed

have older versions in the same p2 repo -> Enide repository #100

paulvi opened this issue Dec 11, 2013 · 3 comments

Comments

@paulvi
Copy link
Member

paulvi commented Dec 11, 2013

@zamnuts in #81 mention

...In other news, it would be nice to keep the version history intact on the primary update site(s) so you can revert to a previous eclipse configuration (under "Installation History"). When using the current update sites for 0.5 and 0.6, Eclipse says it cannot find the old plugin versions.

I guess, it means "have older versions in the same p2 repo" which is currently impossible as mvn build produce new p2 repo every time and Bintray does not allow to update files.

Go on only if someone with knowledge how-to agrees t help.

@paulvi
Copy link
Member Author

paulvi commented Jan 6, 2014

@paulvi
Copy link
Member Author

paulvi commented Jan 27, 2014

solved with Enide repository

@paulvi paulvi closed this as completed Jan 27, 2014
@paulvi
Copy link
Member Author

paulvi commented Feb 8, 2014

Alternatively see mybatis/mybatipse#2 harawata/mybatipse way

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

No branches or pull requests

1 participant