- changed status to resolved
Publish fugue 3.0 Milestone / Beta release / Track the migration process from 2.4 - 3.0
Issue #31
resolved
That would be greatly appreciated! (as I'm currently migrating some libraries that use fugue to java 8).
Comments (17)
-
-
If you spot any issues (or breaking changes you don't expect outside s/guava/java8) please raise comment on https://bitbucket.org/atlassian/fugue/pull-request/35/remove-guava-add-java-8
-
reporter
- changed status to closed
thanks
-
@jbgi have you been caught out by any changes? I'd like to work on and release another milestone over the weekend. It would be good to hear about pain points.
-
reporter
@amckague most pain points are due to the fact that we rely quite heavily on guava (and its api that take guava functions). by the way, there is something wrong with your release process: there is no pom nor source-jar published along with the m006 jar in https://maven.atlassian.com/content/groups/public/com/atlassian/fugue/fugue/3.0.0-m006/
-
- changed status to open
Keep track of the migration from fugue 2 to 3
-
The artefacts are there they just don't show up in that directory view until they are requested. For example https://maven.atlassian.com/content/groups/public/com/atlassian/fugue/fugue/3.0.0-m006/fugue-3.0.0-m006-sources.jar Can you build the correct url for the pom on your end and access it? I'd like to rule out something silly like requests needing to come from the internal network to force things to resolve.
https://maven.atlassian.com/content/groups/public/com/atlassian/fugue/fugue/3.0.0-m002/fugue-3.0.0-m002.pom (change the 2 to a 6 for example)
-
For those places that fugue has equivalents (functions and iterables) I've tried to add equivalent code to fugue for guava. I'd like, where possible, to be able to just change the imports and recompile to make the migration work. https://bitbucket.org/atlassian/fugue/issues/24/support-more-of-the-functions-from-guava (for example is a maybe todo list)
I definitely do not want to make the https://bitbucket.org/atlassian/fugue/issues/15/usage-of-guava-and-fugue-requires-imports issue worse. I'm aware Maps/lists/collections can be an intersection point for example. If you've written code using them you may have to play around with having both java and guava functions but I'm not sure how bad it can be.
-
- changed title to Publish fugue 3.0 Milestone / Beta release / Track the migration process from 2.0 - 3.0
-
- changed title to Publish fugue 3.0 Milestone / Beta release / Track the migration process from 2.4 - 3.0
-
reporter
-
Good.
Have a read of the most recent changelog: https://bitbucket.org/atlassian/fugue/src/9877c33c483bd4769b6b3dee3e73f9a3cacbf49f/changelog.md?at=v3.0.x If anything jumps out or is missing please comment.
-
-
-
- changed status to resolved
-
reporter
congrats!
-
Thank you.
- Log in to comment
3.0.0-m002 should be accessible now from the Atlassian maven.