David H Nebinger 8 Years Ago The snapshots in the maven repo for L7 only go up to M2 even though M4 is available. Please sign in to reply. Reply as... Cancel James Falkner David H Nebinger 8 Years Ago So, starting with M3 we decided to stop using snapshots for the milestone releases - it's a little confusing because the milestone releases are like "releases" (from the maven perspective) but we don't want to pollute the main CE repo with "releases" that aren't really releases. So they are now in the liferay-previews repo. e.g. here: https://repository.liferay.com/nexus/content/repositories/liferay-previews/com/liferay/portal/portal-service/ you can see the M3 and M4 artifacts. Please sign in to reply. Reply as... Cancel Marco Re James Falkner 8 Years Ago What about 6.2.3 maven artifact ? I can't found them in release repository Please sign in to reply. Reply as... Cancel James Falkner Marco Re 8 Years Ago Marco - sorry for the delay - they should be available later today! We had an issue with our maven process that we're ironing out today. Please sign in to reply. Reply as... Cancel James Falkner James Falkner 8 Years Ago Maven artifacts now posted to repository.liferay.com - eventually they will find their way to Maven Central! But the time delay is unpredictable. Please sign in to reply. Reply as... Cancel Philippe Rouvray James Falkner 8 Years Ago It is still not quite ok I'm afraid : Failure to find com.liferay.maven.plugins:liferay-maven-plugin:jar:6.2.3 in http://repository.liferay.com/nexus/content/repositories/liferay-releases-ce/ Please sign in to reply. Reply as... Cancel Marco Re Philippe Rouvray 8 Years Ago I was talking about portal-impl, portal-service, etc artifacts and I can confirm that those are available in the repository.I think liferay-maven-plugin has a different release cycle....this is the main reason of having two different properties in the liferay archetype :${liferay.version} and ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel James Falkner Philippe Rouvray 8 Years Ago @Philippe - we'll be releasing the 6.2.3 Maven plugin to keep it in sync and reduce confusion - but there have been no changes in it since 6.2.2 so it should be OK to use the 6.2.2 version for ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel
James Falkner David H Nebinger 8 Years Ago So, starting with M3 we decided to stop using snapshots for the milestone releases - it's a little confusing because the milestone releases are like "releases" (from the maven perspective) but we don't want to pollute the main CE repo with "releases" that aren't really releases. So they are now in the liferay-previews repo. e.g. here: https://repository.liferay.com/nexus/content/repositories/liferay-previews/com/liferay/portal/portal-service/ you can see the M3 and M4 artifacts. Please sign in to reply. Reply as... Cancel Marco Re James Falkner 8 Years Ago What about 6.2.3 maven artifact ? I can't found them in release repository Please sign in to reply. Reply as... Cancel James Falkner Marco Re 8 Years Ago Marco - sorry for the delay - they should be available later today! We had an issue with our maven process that we're ironing out today. Please sign in to reply. Reply as... Cancel James Falkner James Falkner 8 Years Ago Maven artifacts now posted to repository.liferay.com - eventually they will find their way to Maven Central! But the time delay is unpredictable. Please sign in to reply. Reply as... Cancel Philippe Rouvray James Falkner 8 Years Ago It is still not quite ok I'm afraid : Failure to find com.liferay.maven.plugins:liferay-maven-plugin:jar:6.2.3 in http://repository.liferay.com/nexus/content/repositories/liferay-releases-ce/ Please sign in to reply. Reply as... Cancel Marco Re Philippe Rouvray 8 Years Ago I was talking about portal-impl, portal-service, etc artifacts and I can confirm that those are available in the repository.I think liferay-maven-plugin has a different release cycle....this is the main reason of having two different properties in the liferay archetype :${liferay.version} and ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel James Falkner Philippe Rouvray 8 Years Ago @Philippe - we'll be releasing the 6.2.3 Maven plugin to keep it in sync and reduce confusion - but there have been no changes in it since 6.2.2 so it should be OK to use the 6.2.2 version for ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel
Marco Re James Falkner 8 Years Ago What about 6.2.3 maven artifact ? I can't found them in release repository Please sign in to reply. Reply as... Cancel James Falkner Marco Re 8 Years Ago Marco - sorry for the delay - they should be available later today! We had an issue with our maven process that we're ironing out today. Please sign in to reply. Reply as... Cancel James Falkner James Falkner 8 Years Ago Maven artifacts now posted to repository.liferay.com - eventually they will find their way to Maven Central! But the time delay is unpredictable. Please sign in to reply. Reply as... Cancel Philippe Rouvray James Falkner 8 Years Ago It is still not quite ok I'm afraid : Failure to find com.liferay.maven.plugins:liferay-maven-plugin:jar:6.2.3 in http://repository.liferay.com/nexus/content/repositories/liferay-releases-ce/ Please sign in to reply. Reply as... Cancel Marco Re Philippe Rouvray 8 Years Ago I was talking about portal-impl, portal-service, etc artifacts and I can confirm that those are available in the repository.I think liferay-maven-plugin has a different release cycle....this is the main reason of having two different properties in the liferay archetype :${liferay.version} and ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel James Falkner Philippe Rouvray 8 Years Ago @Philippe - we'll be releasing the 6.2.3 Maven plugin to keep it in sync and reduce confusion - but there have been no changes in it since 6.2.2 so it should be OK to use the 6.2.2 version for ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel
James Falkner Marco Re 8 Years Ago Marco - sorry for the delay - they should be available later today! We had an issue with our maven process that we're ironing out today. Please sign in to reply. Reply as... Cancel James Falkner James Falkner 8 Years Ago Maven artifacts now posted to repository.liferay.com - eventually they will find their way to Maven Central! But the time delay is unpredictable. Please sign in to reply. Reply as... Cancel Philippe Rouvray James Falkner 8 Years Ago It is still not quite ok I'm afraid : Failure to find com.liferay.maven.plugins:liferay-maven-plugin:jar:6.2.3 in http://repository.liferay.com/nexus/content/repositories/liferay-releases-ce/ Please sign in to reply. Reply as... Cancel Marco Re Philippe Rouvray 8 Years Ago I was talking about portal-impl, portal-service, etc artifacts and I can confirm that those are available in the repository.I think liferay-maven-plugin has a different release cycle....this is the main reason of having two different properties in the liferay archetype :${liferay.version} and ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel James Falkner Philippe Rouvray 8 Years Ago @Philippe - we'll be releasing the 6.2.3 Maven plugin to keep it in sync and reduce confusion - but there have been no changes in it since 6.2.2 so it should be OK to use the 6.2.2 version for ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel
James Falkner James Falkner 8 Years Ago Maven artifacts now posted to repository.liferay.com - eventually they will find their way to Maven Central! But the time delay is unpredictable. Please sign in to reply. Reply as... Cancel Philippe Rouvray James Falkner 8 Years Ago It is still not quite ok I'm afraid : Failure to find com.liferay.maven.plugins:liferay-maven-plugin:jar:6.2.3 in http://repository.liferay.com/nexus/content/repositories/liferay-releases-ce/ Please sign in to reply. Reply as... Cancel Marco Re Philippe Rouvray 8 Years Ago I was talking about portal-impl, portal-service, etc artifacts and I can confirm that those are available in the repository.I think liferay-maven-plugin has a different release cycle....this is the main reason of having two different properties in the liferay archetype :${liferay.version} and ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel James Falkner Philippe Rouvray 8 Years Ago @Philippe - we'll be releasing the 6.2.3 Maven plugin to keep it in sync and reduce confusion - but there have been no changes in it since 6.2.2 so it should be OK to use the 6.2.2 version for ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel
Philippe Rouvray James Falkner 8 Years Ago It is still not quite ok I'm afraid : Failure to find com.liferay.maven.plugins:liferay-maven-plugin:jar:6.2.3 in http://repository.liferay.com/nexus/content/repositories/liferay-releases-ce/ Please sign in to reply. Reply as... Cancel Marco Re Philippe Rouvray 8 Years Ago I was talking about portal-impl, portal-service, etc artifacts and I can confirm that those are available in the repository.I think liferay-maven-plugin has a different release cycle....this is the main reason of having two different properties in the liferay archetype :${liferay.version} and ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel James Falkner Philippe Rouvray 8 Years Ago @Philippe - we'll be releasing the 6.2.3 Maven plugin to keep it in sync and reduce confusion - but there have been no changes in it since 6.2.2 so it should be OK to use the 6.2.2 version for ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel
Marco Re Philippe Rouvray 8 Years Ago I was talking about portal-impl, portal-service, etc artifacts and I can confirm that those are available in the repository.I think liferay-maven-plugin has a different release cycle....this is the main reason of having two different properties in the liferay archetype :${liferay.version} and ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel
James Falkner Philippe Rouvray 8 Years Ago @Philippe - we'll be releasing the 6.2.3 Maven plugin to keep it in sync and reduce confusion - but there have been no changes in it since 6.2.2 so it should be OK to use the 6.2.2 version for ${liferay.maven.plugin.version} Please sign in to reply. Reply as... Cancel
Pius Onobhayedo 8 Years Ago Tag on github is not available. i.e. https://github.com/liferay/liferay-portal/releases/tag/6.2.3-ga4 is broken. Kindly fix. Please sign in to reply. Reply as... Cancel
Pasi Kössi 8 Years Ago thanks a lot for the good work. However, I have some comments to make. Firstly, the link to the source code bundle is broken, it retrieves the javadoc bundle, not the source code (at least with my version of Chrome). I can find the correct file from Sourceforge, though.The second point is about not tagging the plug-ins in GitHub. There are a number of plugins delivered in the bundles (Calendar Portlet, Knowledge Base etc.). If I need to tweak any of them, how do I know which source code to fetch from GitHub to work on? Someone has to know from which versions of the plugins the bundle has been made of, so why not tag them?Best Regards,Pasi Please sign in to reply. Reply as... Cancel Pasi Kössi Pasi Kössi 8 Years Ago And I meant the source code download link on the actual download page https://www.liferay.com/downloads/liferay-portal/available-releases. The link on this page seems to be OK, though. Sorry for the confusion. Please sign in to reply. Reply as... Cancel James Falkner Pasi Kössi 8 Years Ago Hey Pasi - the source download link on the downloads page has been fixed - thanks!As for tagging the liferay-plugins repo - unfortunately github tags apply to the entire repo, but not all plugins in that repo are tested or delivered with each CE release. So while we could tag it on the day of release, it wouldn't correspond to the binary you see on the Marketplace.Each plugin has a liferay-releng.changelog file associated with it. If you look in that file you can see the github commits which produced the binary you see on Marketplace. So if you want to tweak, say, the youtube portlet - check out its changelog on Marketplace - https://www.liferay.com/marketplace/-/mp/application/15194204?_7_WAR_osbportlet_backURL=&_7_WAR_osbportlet_tabs1=history - see that you're on the latest version as shown in its liferay-releng.changelog file here: https://github.com/liferay/liferay-plugins/blob/6.2.x/portlets/youtube-portlet/docroot/WEB-INF/liferay-releng.changelog and then see the git commit that produced it: it's commit 1077f05e0e0268b189e7c5d00d63d5376caa707d which can be seen here: https://github.com/liferay/liferay-plugins/commit/1077f05e0e0268b189e7c5d00d63d5376caa707d - so if you want to tweak this, simply 'git checkout 1077f05e0e0268b189e7c5d00d63d5376caa707d' and you'll have the source. Please sign in to reply. Reply as... Cancel Pasi Kössi James Falkner 8 Years Ago James, thanks for the explanation and comprehensive instructions.. I see the change log is also distributed with the bundled plugins. Please sign in to reply. Reply as... Cancel
Pasi Kössi Pasi Kössi 8 Years Ago And I meant the source code download link on the actual download page https://www.liferay.com/downloads/liferay-portal/available-releases. The link on this page seems to be OK, though. Sorry for the confusion. Please sign in to reply. Reply as... Cancel
James Falkner Pasi Kössi 8 Years Ago Hey Pasi - the source download link on the downloads page has been fixed - thanks!As for tagging the liferay-plugins repo - unfortunately github tags apply to the entire repo, but not all plugins in that repo are tested or delivered with each CE release. So while we could tag it on the day of release, it wouldn't correspond to the binary you see on the Marketplace.Each plugin has a liferay-releng.changelog file associated with it. If you look in that file you can see the github commits which produced the binary you see on Marketplace. So if you want to tweak, say, the youtube portlet - check out its changelog on Marketplace - https://www.liferay.com/marketplace/-/mp/application/15194204?_7_WAR_osbportlet_backURL=&_7_WAR_osbportlet_tabs1=history - see that you're on the latest version as shown in its liferay-releng.changelog file here: https://github.com/liferay/liferay-plugins/blob/6.2.x/portlets/youtube-portlet/docroot/WEB-INF/liferay-releng.changelog and then see the git commit that produced it: it's commit 1077f05e0e0268b189e7c5d00d63d5376caa707d which can be seen here: https://github.com/liferay/liferay-plugins/commit/1077f05e0e0268b189e7c5d00d63d5376caa707d - so if you want to tweak this, simply 'git checkout 1077f05e0e0268b189e7c5d00d63d5376caa707d' and you'll have the source. Please sign in to reply. Reply as... Cancel Pasi Kössi James Falkner 8 Years Ago James, thanks for the explanation and comprehensive instructions.. I see the change log is also distributed with the bundled plugins. Please sign in to reply. Reply as... Cancel
Pasi Kössi James Falkner 8 Years Ago James, thanks for the explanation and comprehensive instructions.. I see the change log is also distributed with the bundled plugins. Please sign in to reply. Reply as... Cancel
Federico Budassi 8 Years Ago I've seen Gradle included in the new Liferay 6.2 GA4 SDK. What is it for? It was not included in GA3. Please sign in to reply. Reply as... Cancel James Falkner Federico Budassi 8 Years Ago Hey @Federico, Gradle is a different (and in my opinion better) build infrastructure tool, sort of like ant and maven but better than both. You don't have to use it, but the Plugins SDK now wraps around and uses it. But you can still use ant or maven, we're just giving you more choice Please sign in to reply. Reply as... Cancel Federico Budassi James Falkner 8 Years Ago So, it's just support to use it in our own plugins. Great to know it!I've already checked it and seen that it's a lot let verbose and as powerful as maven. Please sign in to reply. Reply as... Cancel Marco Re Federico Budassi 8 Years Ago @Federico , @James Be aware that if you use gradle in Plugins SDK 6.2.3 you need to change many gradle files because at this moment liferay dependencies are hardcoded with the value of "7.0.0-SNAPSHOT"This is my PR: https://github.com/liferay/liferay-plugins/pull/177 on the master. You can check there the list of file changed to overcome the issue. Please sign in to reply. Reply as... Cancel James Falkner Marco Re 8 Years Ago @Marco - thanks for the heads-up and for the PR! We'll get it reviewed and fixed asap. Please sign in to reply. Reply as... Cancel Joseph Toman James Falkner 8 Years Ago That's great that the SDK now has Gradle support. However, since the SDK seems to be going the way of the dodo (true?) , will there be a stand alone Gradle plugin similar to the Maven plugin ? Please sign in to reply. Reply as... Cancel David Truong Joseph Toman 8 Years Ago @Joseph - The SDK will continue to live but it will begin migrating to gradle in the future to accomplish any packaging/building. We are also working on a different set of gradle plugins that are based on gradle conventions similar to Maven.We understand the SDK is not for everyone but we also know many people have already incorporated the SDK into their workflow so we will be providing options for both types of developers. Please sign in to reply. Reply as... Cancel Joseph Toman David Truong 8 Years Ago OK. I'm good with either, just needed the clarification. How much gradle support is is in the current ga4 SDK release? Please sign in to reply. Reply as... Cancel David Truong Joseph Toman 8 Years Ago Everything in there is just in alpha state and has not been tested much for 6.2. Things may or may not work so... Our goal is to finish it for 7.0 and then backport it properly to 6.2 Please sign in to reply. Reply as... Cancel
James Falkner Federico Budassi 8 Years Ago Hey @Federico, Gradle is a different (and in my opinion better) build infrastructure tool, sort of like ant and maven but better than both. You don't have to use it, but the Plugins SDK now wraps around and uses it. But you can still use ant or maven, we're just giving you more choice Please sign in to reply. Reply as... Cancel Federico Budassi James Falkner 8 Years Ago So, it's just support to use it in our own plugins. Great to know it!I've already checked it and seen that it's a lot let verbose and as powerful as maven. Please sign in to reply. Reply as... Cancel Marco Re Federico Budassi 8 Years Ago @Federico , @James Be aware that if you use gradle in Plugins SDK 6.2.3 you need to change many gradle files because at this moment liferay dependencies are hardcoded with the value of "7.0.0-SNAPSHOT"This is my PR: https://github.com/liferay/liferay-plugins/pull/177 on the master. You can check there the list of file changed to overcome the issue. Please sign in to reply. Reply as... Cancel James Falkner Marco Re 8 Years Ago @Marco - thanks for the heads-up and for the PR! We'll get it reviewed and fixed asap. Please sign in to reply. Reply as... Cancel Joseph Toman James Falkner 8 Years Ago That's great that the SDK now has Gradle support. However, since the SDK seems to be going the way of the dodo (true?) , will there be a stand alone Gradle plugin similar to the Maven plugin ? Please sign in to reply. Reply as... Cancel David Truong Joseph Toman 8 Years Ago @Joseph - The SDK will continue to live but it will begin migrating to gradle in the future to accomplish any packaging/building. We are also working on a different set of gradle plugins that are based on gradle conventions similar to Maven.We understand the SDK is not for everyone but we also know many people have already incorporated the SDK into their workflow so we will be providing options for both types of developers. Please sign in to reply. Reply as... Cancel Joseph Toman David Truong 8 Years Ago OK. I'm good with either, just needed the clarification. How much gradle support is is in the current ga4 SDK release? Please sign in to reply. Reply as... Cancel David Truong Joseph Toman 8 Years Ago Everything in there is just in alpha state and has not been tested much for 6.2. Things may or may not work so... Our goal is to finish it for 7.0 and then backport it properly to 6.2 Please sign in to reply. Reply as... Cancel
Federico Budassi James Falkner 8 Years Ago So, it's just support to use it in our own plugins. Great to know it!I've already checked it and seen that it's a lot let verbose and as powerful as maven. Please sign in to reply. Reply as... Cancel Marco Re Federico Budassi 8 Years Ago @Federico , @James Be aware that if you use gradle in Plugins SDK 6.2.3 you need to change many gradle files because at this moment liferay dependencies are hardcoded with the value of "7.0.0-SNAPSHOT"This is my PR: https://github.com/liferay/liferay-plugins/pull/177 on the master. You can check there the list of file changed to overcome the issue. Please sign in to reply. Reply as... Cancel James Falkner Marco Re 8 Years Ago @Marco - thanks for the heads-up and for the PR! We'll get it reviewed and fixed asap. Please sign in to reply. Reply as... Cancel
Marco Re Federico Budassi 8 Years Ago @Federico , @James Be aware that if you use gradle in Plugins SDK 6.2.3 you need to change many gradle files because at this moment liferay dependencies are hardcoded with the value of "7.0.0-SNAPSHOT"This is my PR: https://github.com/liferay/liferay-plugins/pull/177 on the master. You can check there the list of file changed to overcome the issue. Please sign in to reply. Reply as... Cancel James Falkner Marco Re 8 Years Ago @Marco - thanks for the heads-up and for the PR! We'll get it reviewed and fixed asap. Please sign in to reply. Reply as... Cancel
James Falkner Marco Re 8 Years Ago @Marco - thanks for the heads-up and for the PR! We'll get it reviewed and fixed asap. Please sign in to reply. Reply as... Cancel
Joseph Toman James Falkner 8 Years Ago That's great that the SDK now has Gradle support. However, since the SDK seems to be going the way of the dodo (true?) , will there be a stand alone Gradle plugin similar to the Maven plugin ? Please sign in to reply. Reply as... Cancel David Truong Joseph Toman 8 Years Ago @Joseph - The SDK will continue to live but it will begin migrating to gradle in the future to accomplish any packaging/building. We are also working on a different set of gradle plugins that are based on gradle conventions similar to Maven.We understand the SDK is not for everyone but we also know many people have already incorporated the SDK into their workflow so we will be providing options for both types of developers. Please sign in to reply. Reply as... Cancel Joseph Toman David Truong 8 Years Ago OK. I'm good with either, just needed the clarification. How much gradle support is is in the current ga4 SDK release? Please sign in to reply. Reply as... Cancel David Truong Joseph Toman 8 Years Ago Everything in there is just in alpha state and has not been tested much for 6.2. Things may or may not work so... Our goal is to finish it for 7.0 and then backport it properly to 6.2 Please sign in to reply. Reply as... Cancel
David Truong Joseph Toman 8 Years Ago @Joseph - The SDK will continue to live but it will begin migrating to gradle in the future to accomplish any packaging/building. We are also working on a different set of gradle plugins that are based on gradle conventions similar to Maven.We understand the SDK is not for everyone but we also know many people have already incorporated the SDK into their workflow so we will be providing options for both types of developers. Please sign in to reply. Reply as... Cancel Joseph Toman David Truong 8 Years Ago OK. I'm good with either, just needed the clarification. How much gradle support is is in the current ga4 SDK release? Please sign in to reply. Reply as... Cancel David Truong Joseph Toman 8 Years Ago Everything in there is just in alpha state and has not been tested much for 6.2. Things may or may not work so... Our goal is to finish it for 7.0 and then backport it properly to 6.2 Please sign in to reply. Reply as... Cancel
Joseph Toman David Truong 8 Years Ago OK. I'm good with either, just needed the clarification. How much gradle support is is in the current ga4 SDK release? Please sign in to reply. Reply as... Cancel David Truong Joseph Toman 8 Years Ago Everything in there is just in alpha state and has not been tested much for 6.2. Things may or may not work so... Our goal is to finish it for 7.0 and then backport it properly to 6.2 Please sign in to reply. Reply as... Cancel
David Truong Joseph Toman 8 Years Ago Everything in there is just in alpha state and has not been tested much for 6.2. Things may or may not work so... Our goal is to finish it for 7.0 and then backport it properly to 6.2 Please sign in to reply. Reply as... Cancel