I know that is possible use NuGet with the Nexus pro. I want to know if it is possible to use it with the oss version.
NuGet support is part of the Nexus Professional features. The only way to use it with Nexus Open Source is if you write your own Nexus plugins that implement NuGet support anew. Although that seems like a waste of time and a very expensive exercise compared to getting a Nexus Professional license including support.
Update December 2014: As of September 2014 and the release of Nexus 2.9 the full NuGet support is also part of Nexus OSS. With the following releases of 2.10 and 2.11 we also added support for NPM and RubyGems.
I think now (from version 2.9) you can use NuGet also on oss version.
This comparison says the same.
Related
I'm using a 4.0.2 version of artifactory.
I'd like to know if it's possible a direct migration from 4.0.2 to actual 7 release or some intermediate steps are needed.
Could someone provide documentation about this topic ?
Tks
Tullio
The Quick answer is No.
Upgrading Artifactory from 4.x version to 7.x will require incremental upgrades on the way.
In order to find the best solution, based on your current state of the application, please refer to the guides below:
Upgrading from Artifactory 4.x: https://www.jfrog.com/confluence/display/RTF4X/Upgrading+Artifactory#UpgradingArtifactory-Upgradingfromv3.xorv4.xtotheLatestVersion
Upgrading from Artifactory 5.x: https://www.jfrog.com/confluence/display/RTF5X/Upgrading+Artifactory
Upgrading from Artifactory 6.x & 7.x: https://www.jfrog.com/confluence/display/JFROG/Upgrading+Artifactory#UpgradingArtifactory
is there a way to know when a version of Flyway is going to get deprecated?, actually we were using 6.0.7 the last year and then got deprecated like 6 months ago, now we are using 6.4.1 but I tried to find something on the blog and documentation but there's nothing about some news of when a version is going to be deprecated, only when we run our java spring boot project we know that a version is not usable. And we're aware of this because there's a lot of changes in version 7+ that doesn't work with our project (tested version 7.0.1 and the app crashed) and we need to estimate the cost of the changes.
Any help would be appreciate, thanks.
Flyway releases via Maven OSS. Old versions are kept indefinitely and are outside of Redgate's control. In theory, all older versions which are currently available on Maven will continue to be available for all time.
Newer versions may deprecate features over time, but older versions will always be available.
I can't find this corda-tools-ha-utilities-.jar from internet or enterprise version, could anyone told me that how I could get it , version 4.4 to 4.7 is ok to me . thx.
For corda enterprise users you're gonna need to reach out to support as they have a specific repository for enterprise jars like the ha utilities.
The open source users can get pretty much any of the jars in their usual gradle builds. (repositories can be seen in the cordapp template here: https://github.com/corda/cordapp-template-java)
We are upgrading our nexus artifact repository from 2.x to 3.x version. During this process, after the migration is complete, there is a timestamp missing for the artifacts. Any solution regarding this will be helpful.
This has nothing to do with your upgrade. Tree view (browse) in Nexus Repository Manager 3 does not show last modified for folders. I have never heard this requested but if this is important to you, suggest you file a ticket in issues.sonatype.com in the NEXUS project and it can be evaluated by the team.
We are running an old version of plone (Version 2.0.5). (We will migrate next year to plone 4)
I was trying to install the Plone Hotfix 20121106, but (as mentionened in the installing description), the hotfix will not apply to the version 2.0.5 of plone.
Questions:
Are the security vulnerabilites also relevant for the plone version 2.0.5?
Is there another way to install the hot fix on that old version of plone?
Some of the security vulnerabilities do apply to 2.0.5, yes.
However, there are other unpatched vulnerabilities in 2.0.5 not addressed by this hotfix, and you want to move away from this old a version as soon as possible. The Plone security team does not provide official support for Plone versions this old; currently 3.x and 4.x releases are supported.
You can unzip the hotfix into your Products folder, and it should just work. I believe people have tested it on 2.0.x installations already; the test coverage certainly was run on 2.1. You'll have to run your own tests though to make sure nothing (important) breaks for you when the fix is installed.