Here is maven-gpg-plugin version 3.0.0 official page: http://maven.apache.org/components/plugins-archives/maven-gpg-plugin-LATEST/download.cgi
However:
the download links not working
Maven central shows that the latest version of plugin is 1.6
Is it some fake page or what am I missing?
This was stage release, which doesn't passed testing and voting on Maven Developers List, so was canceled.
https://lists.apache.org/thread.html/r0286ef73b56cb484952489e6b5757e3b17023e73f8fa0dde7aa80bc4%40%3Cdev.maven.apache.org%3E
After testing two new issues was found:
https://issues.apache.org/jira/browse/MGPG-78
https://issues.apache.org/jira/browse/MGPG-79
There is new plugin https://www.simplify4u.org/sign-maven-plugin/ probably it will be successor of maven-gpg-plugin
Related
I've published a package to qooxdoo, but found that I want remove this.
What is the command to remove a package from the qooxdoo repository?
I was advised by the core team to add "(deprecated)" to the About section of the Github project that i wanted removed from the package system. See here for an example: https://github.com/sqville/sqv-qxthemes
Adding this successfully removed this project from qooxdoo.org's package browser site
As I'm sure many are aware, admob needed an update to use a newer SDK (7.64+) and this message appears on your admob account if you have apps using an SDK below that version:
Some of your iOS apps require a GMA SDK update To keep ads serving normally and minimize a loss in ad revenue, implement the GMA SDK 7.64.0 (or later) for your iOS apps. And configure the SKAdNetwork in your apps with Google's network ID.
Expo had a PR here that was merged 6 days ago. This should have updated the GMA SDK to 7.69.0. However, when I ran expo upgrade it states that it updated expo-ads-admob,
✅ The following packages were updated:
expo-ads-admob, expo-av, expo-keep-awake, expo-updates, react-native, react, react-dom, #babel/core, react-native-web, babel-preset-expo, expo
but no changes actually take effect. And if I have the newer version (10.0.0) that I manually installed as stated below, it downgrades it to 8.4.0.
When that wasn't working, I then went and manually updated expo-ads-admob to 10.0.0 via npm (also tried yarn) and it looked like the node package was actually updated (checking the CHANGELOG and it has info about 10.0.0).
Still when I build my app with expo build:ios, run the new app, and check my GMA SDK version on admob it is still using 7.55.1.
I have also tried completely removing expo-ads-admob and reinstalling, but the same issue occurs.
Any ideas as to why this is occurring? Is there some other method I should be using to upgrade to the latest commit on expo's master branch?
Appreciate all the assistance in advance and let me know if there is any additional info I can provide.
Additional Info:
SDK Version: 40.0.0
Platform: iOS
Workflow: Managed
EDIT: Received answer from Expo member, see answer below.
You cannot use updated packages if using the managed workflow, it must be bare workflow in order to update module versions manually. Therefore, this admob update won't take place for managed workflows until expo SDK 41 is released.
See expo forum here for more.
I have just upgraded a website from DNN version 6.1.3 to 8.0.0.
Post upgrade I found that the FAQ module had updates available as shown in this screen
I downloaded the latest available FAQ module(5.1.1) and installed on my website.
It seemed that the updates are installed successfully but FAQ module stopped rendering.
In the edit mode it displays following error message
DotNetNuke.UI.Modules.ModuleHost - System.Web.HttpParseException (0x80004005): Unknown server tag 'dnn:DnnListBox'
I tried troubleshooting many ways but no luck.
Really appreciate if someone can help in this.
This is related to some of the Controls being moved to the DotNetNuke.Web.Deprecated DLL.
Here's a commit in the FAQ project which looks to correct this issue
https://github.com/DNNCommunity/DNN.Faq/commit/0718e084be5c0dbdf1c085aa804a44cde8ab3037
Your best bet is to fork that project and compile it yourself to build a new ZIP version to use, or to wait for the project to complete a new release with the fixes.
Try installing the latest version (5.3.0). I had to contact support, but they sent me a copy of that version of the FAQ module today and it seems to work in DNN 8.3.0.
My company (Java + AngularJS shop) is evaluating both IDEA and WebStorm. Based on some Googling, it looks like IntelliJ IDEA is a superset of the *Storm editors, assuming you install the proper plugins (source1, source2):
Practically, if we purchased IntelliJ IDEA 13.1 Ultimate, what plugins would we need to get these WebStorm features?
Grunt integration
AngularJS integration
Bower integration
Karma integration
JavaScript auto-complete/navigation
Grunt and Bower support, as well as javaScript completion, etc. are available out of the box. AngularJS, Node.js and Karma plugins have to be installed from the repository (Settings/Plugins, Browse Repositories..., type plugin name in the search box to quickly locate it).
Just search the repo, you can do this from within intellij with a nice gui aswell.
javascript code complete is in vanilla (not an external plugin) version btw, as I would imagine most of the others are. Just try the trial version.
I'm trying to use Google Cloud Endpoints with Android client, built by Maven.
The problem is that appengine-maven-plugin v1.8.3+ require Maven v3.1.0+
[ERROR] Failed to execute goal com.google.appengine:appengine-maven- plugin:1.8.4:endpoints_get_discovery_doc (default) on project pro-gae: The plugin com.google.appengine:appengine-maven-plugin:1.8.4 requires Maven version 3.1.0 -> [Help 1]
while android-maven-plugin v3.6.1 doesn't (and will not) work with Maven v3.1.0 (see devs discussion at https://code.google.com/p/maven-android-plugin/issues/detail?id=395). The error
A required class was missing while executing com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.6.1:generate-sources: Lorg/sonatype/aether/RepositorySystem;
So I'm kinda locked out. One plugin asks for v3.1.0+, while the other one claims Maven 3.1.0 to be fatally buggy. So I left out to generate Endpoints client sources manually.
Any other ideas, besides waiting for fixed Maven 3.1.1? It doesn't seem to happen soon, because Maven 3.1.0 was released more than two months ago.
The latest version of the Android Maven Plugin is 3.8.0 and it now requires Maven 3.1.1+. This should allow you to use the latest appengine plugin as well. And Maven 3.1.1 has been released in the meantime as well.
Update Sept 2015: Latest version of the plugin is 4.3.0 with 4.3.1 around the corner. The 4x branch works with Maven 3.0.5+ but we strongly encourage users to use the latest Maven release.
Hmm, looks resolved by just using older version (1.8.2) of appengine-maven-plugin.
One other way of building is to configure the Run Configuration to use an external Maven Runtime.
To do this in Eclipse for Windows :
Right Click Project -> Run Configuration -> Create a new configuration -> In Main tab configure Maven Runtime.
I hope this helps.