Planned maintenance is scheduled for the week of June 15th - the exact date and time will be announced soon.
See More Details
Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: Unable to get default Liferay archetype http://repo1.maven.org/maven2/)
Kapitan Spaulding modifierades för 6 År sedan.
New Member
Inlägg: 8
Anslutningsdatum: 2019-12-03
Senaste inlägg
hello, how to rplace http://repo1.maven.org/maven2/ with https://repo1.maven.org/maven2/ in liferay studio.
Yanan Yuan modifierades för 6 År sedan.
Junior Member
Inlägg: 89
Anslutningsdatum: 2011-10-08
Senaste inlägg
Hello,We've updated it on latest master here:https://github.com/gamerson/liferay-ide/commit/85be5b16d9f7cda74731717cc0c38936a8a7857c
If you still run into this error, could you please provide some detailed steps for us to reproduce? Thanks.
If you still run into this error, could you please provide some detailed steps for us to reproduce? Thanks.
Kapitan Spaulding modifierades för 6 År sedan.
New Member
Inlägg: 8
Anslutningsdatum: 2019-12-03
Senaste inlägg
Thank you for your quick reply.
error stil exist for configuration as bellow
eclipse
Version: 2019-12 (4.14.0)
Build id: 20191212-1212
I add my compilations
liferay-ide-updatesite-3.8.0-ga1-202001191050.zip
new Liferay jsf portlet
log file:
!ENTRY com.liferay.ide.maven.core 4 0 2020-01-19 19:05:26.823
!MESSAGE Unable to get latest Liferay archetype
!STACK 0
org.eclipse.aether.resolution.ArtifactResolutionException: Could not transfer artifact com.liferay.faces.archetype:com.liferay.faces.archetype.primefaces.portlet:jar:5.0.7 from/to central (http://repo1.maven.org/maven2/): Failed to transfer http://repo1.maven.org/maven2/com/liferay/faces/archetype/com.liferay.faces.archetype.primefaces.portlet/5.0.7/com.liferay.faces.archetype.primefaces.portlet-5.0.7.jar. Error code 501, HTTPS Required
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:424)
ect.
error stil exist for configuration as bellow
eclipse
Version: 2019-12 (4.14.0)
Build id: 20191212-1212
I add my compilations
liferay-ide-updatesite-3.8.0-ga1-202001191050.zip
new Liferay jsf portlet
log file:
!ENTRY com.liferay.ide.maven.core 4 0 2020-01-19 19:05:26.823
!MESSAGE Unable to get latest Liferay archetype
!STACK 0
org.eclipse.aether.resolution.ArtifactResolutionException: Could not transfer artifact com.liferay.faces.archetype:com.liferay.faces.archetype.primefaces.portlet:jar:5.0.7 from/to central (http://repo1.maven.org/maven2/): Failed to transfer http://repo1.maven.org/maven2/com/liferay/faces/archetype/com.liferay.faces.archetype.primefaces.portlet/5.0.7/com.liferay.faces.archetype.primefaces.portlet-5.0.7.jar. Error code 501, HTTPS Required
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:424)
ect.
Santiago Pérez de la Cámara modifierades för 6 År sedan.
Junior Member
Inlägg: 53
Anslutningsdatum: 2012-03-23
Senaste inlägg
Hi!Please, could you tell me if you solved this problem?I'm working with the same IDE's version and I can't create a JSF project because the "http" access to the Maven repository.I didn't find any configuration (Window > Preferences > Maven) to change the URL. Neither I have a "settings.xml" in the ".m2" directory.Thanks!
Santiago
Santiago
Yanan Yuan modifierades för 6 År sedan.
Junior Member
Inlägg: 89
Anslutningsdatum: 2011-10-08
Senaste inlägg
Hello,Could you please try this new IDE here: https://liferay.dev/project/-/asset_publisher/TyF2HQPLV1b5/content/ide-installation-instructions, Please let me know if there is anything.
Thanks
Thanks
Santiago Pérez de la Cámara modifierades för 6 År sedan.
Junior Member
Inlägg: 53
Anslutningsdatum: 2012-03-23
Senaste inlägg
Hello!
The problem persists with that version....
This is the maven error:
#NOTE: This is a Maven Resolver internal implementation file, its format can be changed without prior notice.
#Tue Mar 10 18:36:13 CET 2020
maven-metadata-central.xml.error=Could not transfer metadata com.liferay.faces.archetype\:com.liferay.faces.archetype.primefaces.portlet/maven-metadata.xml from/to central (http\://repo1.maven.org/maven2/)\: Failed to transfer http\://repo1.maven.org/maven2/com/liferay/faces/archetype/com.liferay.faces.archetype.primefaces.portlet/maven-metadata.xml. Error code 501, HTTPS Required
maven-metadata-central.xml/@default-central-http\://repo1.maven.org/maven2/.lastUpdated=1583861773203
Thanks!
The problem persists with that version....
This is the maven error:
#NOTE: This is a Maven Resolver internal implementation file, its format can be changed without prior notice.
#Tue Mar 10 18:36:13 CET 2020
maven-metadata-central.xml.error=Could not transfer metadata com.liferay.faces.archetype\:com.liferay.faces.archetype.primefaces.portlet/maven-metadata.xml from/to central (http\://repo1.maven.org/maven2/)\: Failed to transfer http\://repo1.maven.org/maven2/com/liferay/faces/archetype/com.liferay.faces.archetype.primefaces.portlet/maven-metadata.xml. Error code 501, HTTPS Required
maven-metadata-central.xml/@default-central-http\://repo1.maven.org/maven2/.lastUpdated=1583861773203
Thanks!
Yanan Yuan modifierades för 6 År sedan.
Junior Member
Inlägg: 89
Anslutningsdatum: 2011-10-08
Senaste inlägg
Hello,
Could you check your settings in .m2/settings.xml and go to Window > Preferences > Maven to see if you have any settings point to http://repo1.maven.org/maven2?
Could you check your settings in .m2/settings.xml and go to Window > Preferences > Maven to see if you have any settings point to http://repo1.maven.org/maven2?
Gregory Amerson modifierades för 6 År sedan.
Liferay Legend
Inlägg: 1123
Anslutningsdatum: 2010-02-16
Senaste inlägg
So you can configure a newer maven runtime in the Window > Preferences > maven > installations page.

After that, you can try to access the maven archetype catalog. If that doesn't work, you can manually configure a remote maven archetype catalog on "Archetypes" preference page:

After that, you can try to access the maven archetype catalog. If that doesn't work, you can manually configure a remote maven archetype catalog on "Archetypes" preference page:
Community
Company
Feedback