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.

Sign up for GitHub

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

Jump to bottom

when calculating currentVersion latest matching isn't always correct #88

Open
GoogleCodeExporter opened this issue Mar 24, 2015 · 2 comments
Open

when calculating currentVersion latest matching isn't always correct #88

GoogleCodeExporter opened this issue Mar 24, 2015 · 2 comments
Labels
auto-migrated Milestone-1.0 Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

When you've just created a new development version, with no mcz file 
differences, currentVersion shows up as the development version which can be 
confusing, especially if you've only changed a project reference version....


It might be worth moving a earlier and earlier as long as #allLoadedToSpec or 
#loadedToSpec is true ...

I think

Original issue reported on code.google.com by henrichs...@gmail.com on 9 Jul 2010 at 9:50
@GoogleCodeExporter
Copy link
Author

Original comment by henrichs...@gmail.com on 18 Jan 2012 at 6:52

  • Added labels: Milestone-1.0-beta.32
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

#currentVersion reduces in importance when the project registry is involved

Original comment by henrichs...@gmail.com on 19 May 2012 at 8:00

  • Added labels: Milestone-1.0
  • Removed labels: Milestone-1.0-beta.32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Milestone-1.0 Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter