As stated on the link https://github.com/weichsel/ZIPFoundation#in-memory-archives, it should be possible to create in memory archive, still I am unable to find appropriate init method of the Archive class. Am i doing something wrong or this is not yet released?
I have seen the PR but still i cant see why this is in the documentation on the github page.
When will this feature be released?
I got an answer from the author:
weichsel commented on 28 Feb •
Hi,
The GitHub project page shows the state of README.md in the development branch (which is the default branch of the project).
The feature is very new and there is no tagged release yet.
If you want to use/test in-memory archives, please point your package manager to development.
Please also note that this feature is only available if you are targeting Swift 5 or newer. If you are integrating via Carthage, you will have to manually set the SWIFT_VERSION of the ZIPFoundation.xcodeproj to 5 manually. It is currently set to 4 for compatibility reasons. (Carthage does not provide a way to specify the language version).
Related
I’m currently using the library Dynamic Reports that uses Jasper Reports, but it seems the website is out of service now.
Will it be fixed soon ? Is the library still working ?
Thank you for your help.
Don't know what happened to the project but it also disappeared from SourceForge (https://sourceforge.net/p/dynamicreports/).
I guess the project is now on GIT
https://github.com/dynamicreports
Documentation and examples is still missing though
Pursuant to the failure of that website, the project was cloned by some users, from existing files and ported over to github. The documentation is still work in progress, as it seems that it has to be reconstituted from the ground up. The continuing work can be accessed at https://dynamicreports.readthedocs.io/en/latest/.
By the way, the original artifacts can still be downloaded from maven central and the library at least up to version 5.1.0. As for continuing support and maintenance, it's a matter of time, but these contributors contributors intend to see to it that this library flourishes.
I'm developing an Eclipse plugin and i've run into this problem several times already.
I always keep my Target Platform updated for the latest (stable) Eclipse release so that i test my code against all the recent updates, fixes etc.
However, this may (and have) result in accidental breakage of backward compatibility of my plugin, e.g. when i accidentally use new API that did not exist in the Eclipse version i aim to support.
Or, more sneaky example, in 4.6 Eclipse moved to Java 8 and some interface methods got default implementations. Now when i implement these interfaces my IDE doesn't automatically generate empty implementations for those methods and no error is generated. If i install and run this code against a previous Eclipse version these methods will throw AbstractMethodError since no implementation has been provided.
So my question is: is there a tool to further restrict API my Target Platform provides to some earlier Eclipse API version?
Is API Baseline an appropriate tool for this? Because i couldn't get it to work like this. (It allowed even non-baseline method calls not to mention the more complex default-methods example.)
You can use multiple target platforms, switching between them doesn't take long. For testing Stack Overflow questions I have one Eclipse install with 10 target platforms.
So have a target platform for the oldest release you want to support as well as your current release target platform and check the code runs against that.
It is particularly important to test with the actual Target Platform if you want to support Eclipse 3 releases as the were large changes going from Eclipse 3 to 4.
I integrated my first library with cocoapods recently and have a full documentation readme on my github repo.
Unlike other pods, where if you search for them on cocoapods.org there is an expand button to see more information about the pod on the site, mine does not have it.Instead my own has three buttons [ Site, Docs, Spec] to the right of it, which all link to my github page.
What should i do to make the documentation accessible on cocoapods or do I have to wait for cocoapods to gather more information before they do that? Thanks!
The link to my library is https://cocoapods.org/?q=lang%3Aswift%20on%3Aios%20DLLocal. If it helps my library is coded using Swift 3.
I looked at another library and found out that the Documentation parser cocoapods uses could not parse my information because it did not know my swift version.
The error given was:
Error Parsing Pod
Could not find Objective-C Classes.
The solution was to add a file in my github repo named ".swift-version"
With contents:
3.0
Which is the version of swift used in the program.
I have been playing around with the new StateMachine workflow that has been added to Windows Workflow as part of Platform Update 1 (see also). I now want to look at installing what I've created and therefore need to make sure my bootstrapper is up-to-date. In the future, I will be moving to WIX but right now, for the purposes of prototyping, I'm just using a regular Setup and Deployment project and its bootstrap support.
The list of standard pre-requisites does not include the PU1 as an option. Therefore, how can I add support for it?
Update
I found this answer on StackOverflow regarding custom prerequisites, which led me to this article on MSDN, which led me to creating my own pre-requisite. However, I got a new error about mismatched framework requirements. I suspect I need to pick apart the multi-targeting support and the existing .NET framework prerequisite package to see how to make a new prerequisite that will work correctly.
I've had a stab at creating my own bootstrapper packages for this. The results are here to download. Note that these are entirely untested and provided as-is - use at your own risk. However, feedback is welcome. Hopefully Microsoft will provide an official solution.
See How to detect if the .NET Framework Platform Update 1 is installed
is the Microsoft .NET Framework 4 Platform Update 1 - Runtime Update (KB2478063) what you are looking for? See here for the download.
Where can I find information about upgrading Magento Enterprise 1.7. to the latest 1.9. ?
There's no such documentation.
Your general approach:
1. Close production server
2. Backup all DBs and Magento installation
3. Turn off all your custom extensions and themes
4. Delete from HDD: core Magento modules, their layouts, all standard themes and cache.
5. Get 1.9 EE, copy it over your installation
6. Request Magento through http
7. Walk at your site, notice errors and warnings, fix them
8. Check documentation and update for your theme, whether it supports EE 1.9. Turn it on if it supports, otherwise you'll need another theme.
9. Check documentation and updates for all your custom extensions - whether they support 1.9. Turn them on - one by one.
You won't have any problem with upgrading all core DB data - it's made automatically.
You'll have problems with your custom theme, as you'll need new version with support for 1.9. And you'll need to check your custom extensions and upgrade their source and DB data to fit 1.9.
Generally all Magento upgrades work by running the updated code with the old database. The differences will be detected and incorporated automatically on the next page request. Magento keeps track of every module's version number for this reason.
Because there is a chance some modification will break it is best to do this on a new (temporary) site then add the modifications back in gradually. That way the old site is still active and uninterrupted.
I think there is no official documentation. The best way is to figure out what core functionality is used in your customizations and after that look at theirs realization in new version: does it changed or not.
To know what was changed in new version you could check changeslist