support-maven/pom.xml does contain hard coded value for distributionManagement repositories

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 6.0.3 GA
• Fix Version/s: 6.0.4 GA
• Component/s: WCM
• Labels: None
• Environment: Liferay trunk, Gentoo Linux 64bits
• Similar Issues: Show 5 results ; ;

  LPS-29664	Refactoring hard coded values in calendar portlet
  LPS-22858	DLProcessor's hard-coded into JSPs
  LPS-2083	CommandReceivers for FCKEditor are hard coded and not injectable
  LPS-11786	Hard-coded guest groupId in the summary portlet
  LPS-16991	Portletrequest properties does not contain request header values

Ideally in order to be able to deploy liferay archetypes to our private repository without having to edit support-maven/pom.xml to replace hard coded repositories this one should use repositories that are set from some properties/profile from ~/.m2/settings.xml or else.

[Thiago Leão Moreira]

There is no need to deploy the artifacts to local repositories anymore. Liferay's artifacts are now deployed to Central.

http://www.liferay.com/web/thiago.moreira/blog/-/blogs/liferay-s-artifact-are-now-mavenized

[Baptiste Grenier]

As no artifacts for 6.0.6 were deployed, if would be nice to have properties for the repositories IDs and locations like in the following patch (made against the 6.0.6 branch).

ndex: build-maven.xml
===================================================================
— build-maven.xml (révision 76974)
+++ build-maven.xml (copie de travail)
@@ -162,16 +162,16 @@
/>

<antcall target="deploy-artifacts">

• <param name="maven.repository.id" value="sonatype-staging" />
• <param name="maven.url" value="http://oss.sonatype.org/service/local/staging/deploy/maven2" />
  + <param name="maven.repository.id" value="$ {maven.repository.id}

  " />
  + <param name="maven.url" value="$

  {maven.url}

  " />
  <param name="maven.version" value="$

  {lp.version}" />
  </antcall>
  </target>
  
  <target name="deploy-snapshot-artifacts">
  <antcall target="deploy-artifacts">
  - <param name="maven.repository.id" value="sonatype-snapshot" />
  - <param name="maven.url" value="http://oss.sonatype.org/content/repositories/snapshots" />
  + <param name="maven.repository.id" value="${maven.snapshots.repository.id}" />
  + <param name="maven.url" value="${maven.snapshots.url}" />
  <param name="maven.version" value="${lp.version}

  -SNAPSHOT" />
  </antcall>
  </target>
  Index: release.properties
  ===================================================================

  • • release.properties (révision 76974)
      +++ release.properties (copie de travail)
      @@ -23,8 +23,10 @@
  1. Maven
     ##

• #maven.repository.id=liferay
• #maven.url=http://localhost/nexus/content/repositories/liferay
  + maven.repository.id=sonatype-staging
  + maven.url=http://oss.sonatype.org/service/local/staging/deploy/maven2
  + maven.snapshots.repository.id=sonatype-snapshot
  + maven.snapshots.url=http://oss.sonatype.org/content/repositories/snapshots
  #maven.version=$ {lp.version}

##

Regards,
Baptiste