we have a project , the porject contains three features and each feature contains its separate component files. we have also created patches for this install project. but have strange issues.
The three features can be installed individually in several machines, we can say we have A,B.C three features. in machine 1, i have installed feature B only, and applyed patch1, 2 ,3 . but when i uninstall patch3, it will bring other component files in . just like it installed other features. Check the install dir it installed other features. almost every file from other features. How could it happen? do anyone have a fix on this, thanks in advance.
after reanalysis my project, i re-structured the feature and pick the common component into a separate feature, and that resolved the issue.
Related
I have a shopware installation with the dev template. There is no .git folder so I don´t know which Shopware version or commit was/is used. In the composer.json I have something like this: "shopware/platform": "6.4.x#dev" So I know it was 6.4.x But no minor version or which commit.
My plan is to migrate this to the production template but I want to do a diff (with the original version) and migrate some things into plugins (which where changed in the platform).
Is there an other way to determine the shopware version?
You can find the installed version either in the composer.lock by searching e.g. shopware/administration
"name": "shopware/administration",
"version": "6.4.12.0",
or you can login into the admin interface and in the upper left corner you also find the version.
Or if you don't have a composer installation, the only way to find out will be to compare the existing migration files and other recently changing files and folders unfortunatelly.
https://github.com/shopware/platform/tree/trunk/src/Core/Migration
You can pin the Shopware version to a specific release in the composer.json e.g. by setting it to "shopware/platform": "6.4.13.0". You could then run composer install again but there might be differences in the database structure, changed administration builds and so on. So once you pin the version it might be best to run ./psh.phar install which will do all of that (including the composer install step). You can find all available versions over at Packagist.
I am building an app in Flutter. I need to make two versions of it - a pro and lite version. I use Android Studio. What would be the best way to maintain two versions of an app, so I don't have to create two different projects and update the code in both projects ?
You could achieve this using Flavors where you can create 2 binaries from the same code base with different app ids. Anotehr way, although not tried myself you can use the flutter tools to create multiple different builds for each platform.
From there you can have 2 entry main files that will be configured for each flavor, main.dart and main_lite.dart. In there you can specify what features are enabled for each one
I ran into a similar issue with an app for work. The solution I am using is to simply have a singe project for both apps but a special gitHub branch for the 2nd app.
So for instance my main app is on master and the 2nd app is on the second_app branch.
When I make a significant change, I make sure to merge it in master first.
And then I just git merge master into second_app.
So, it's not 100% automatic, but it works fine for most cases. And you have the whole git merge workflow at your disposal so you can easily resolve conflicts when you merge.
I know this has been asked before but I haven't seen a working solution. I have two android studio (V 3.1.3) projects, MyAppBasic and MyAppPro. They each have 3 modules in common and one that is unique. My current implementation is duplicating the 3 common modules in each project. Obviously this is undesirable. What is the recommended way to implement these two apps and avoid code duplication? Thanks.
In case both of your project: MyAppBasic and MyAppPro, have almost a similar code, you can merge them and use build variant to differentiate between basic and pro app.
You also need to installing each module as a local library by using Gradle Android Maven plugin (you can see this answer for details: https://stackoverflow.com/a/33736043/4758255). Then you only need to maintain 3 common modules which is reusable as the libraries for both of your projects.
I'm using NuGet to create a 'web framework' package containing code, master pages, css, javascript, etc.
In an attempt to speed up the build / test process I'm running nuget.exe update packages.config but I've noticed that it behaves differently than the package manager console's Update-Package command.
nuget.exe update seems to leave the previous version of the package still installed, resulting in multiple versions of the package installed. This usually doesn't cause problems but the Package-Manager Get-Package command shows many versions installed and sometimes the project will fail to build.
Update-Package actually uninstalls the package then reinstalls it, this is cleaner but slower
My questions are:
1. Is there documentation about the difference / relationship between these commands
2. Is the nuget.exe update behavior of installing multiple versions a bug?
3. Is there a better method for creating a package in one project and updating it in another project in a fast & automated manner?
Unfortunately, there's not much official guidelines or documentation except from piecing together forum and work item threads.
Current package manager console behavior was first included as a result from discussion in this thread, which later derived in a work item (sorry, apparently not enough rep to post more links).
However, as others already noted, behavior is not consistent with nuget.exe, where there's no such switch.
So, in answer to your questions:
VS Package Manager Console and nuget.exe do have different behaviors and seem to be updated independently (which is very unfortunate).
nuget.exe update behavior of installing multiple versions side-by-side has been a design feature from the start, as you can find from a comment on David Ebbo's blog about NuGet command line (again, I would have given you the link, but SO still doesn't trust me).
Unfortunately I haven't found anything about using package manager console cmdlets during build. What you could try is manually deleting all folders with your packageId on a build event and then packaging and installing using nuget.exe. Essentially replicate what Update-Package does manually, since as David Ebbo says, the way you uninstall a package through the command line interface is by, well, deleting the folder (again, can't post a reference, this is a bit annoying...)
I have CCValidator installed in 3 different locations (servers where CC.NET runs).
The problem that I have is that 2 of them do not recognize CC.NET plugins that I have installed - specifically conditional elements within the .config file. One version of CCValidator works as expected with conditional elements, but the other 2 do not.
The conditional elements are coming into use more and more often. I need to find updates for CCValidator to recognize the plugins I have and use regularly.
I did not install the various instances of CCValidator and can find nothing about downloading the newest version or updates. I have checked several posts that included links that did not lead anywhere that helped.
CruiseControl.net configuration validation tool is provided with ccnet installation. It has the same version as ccnet.
You should not install another version, as it is linked to your ccnet installation. If you have warnings or errors with the validator then :
be sure to use the right CCValidator.exe under the server folder (not inside ccvalidator).
upgrade your ccnet installation. v1.6.xxxx is stable enough and fix many thing from v1.5
For your information, I'm using ccnet v1.5.7385.122 and ccnet v1.6.7991.1 without any plugin error/issue.