Alfresco
  1. Alfresco
  2. ALF-11027

Enable deployments of artifacts to a Maven repository from the Ant build

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0.a Community
    • Fix Version/s: Future
    • Component/s: Build
    • Security Level: external (External user)
    • Labels:
      None
    • Environment:
      Any, backed by http://maven.alfresco.com

      Description

      As per mail conversation below:

      1. ALF-11027.patch
        25 kB
        Gabriele Columbro
      2. m2-bootstrap-34plus.sh
        10 kB
        Gabriele Columbro
      3. m2-deploy-34a.sh
        0.2 kB
        Gabriele Columbro
      4. mvndeploy.sh
        4 kB
        Samuel Langlois

        Issue Links

          Activity

          Hide
          Gabriele Columbro added a comment -

          I have an almost working solution against HEAD. It comprises:

          • a main goal called maven-deploy which works on the [projects/modules/enterpriseproject/enterprisemodules]/*/build/dist packages and deploys them
          • this goal depends on init,build-tomcat,deploy-solr,distribute-amps . TODO: Identify the best target to make sure all packages are there
          • 2 separate files called maven.xml, imported by main and enterpriseprojects build.xml
          • enterpriseprojects overrides targets according to the standard pattern and deploys enterprise only added packages

          Will commit on a branch, can I get the issue assigned?

          Details:
          Used artifact:mvn instead of artifact:deploy as it was giving some strange side effect. Can definitely be improved

          Show
          Gabriele Columbro added a comment - I have an almost working solution against HEAD. It comprises: a main goal called maven-deploy which works on the [projects/modules/enterpriseproject/enterprisemodules] /*/build/dist packages and deploys them this goal depends on init,build-tomcat,deploy-solr,distribute-amps . TODO: Identify the best target to make sure all packages are there 2 separate files called maven.xml, imported by main and enterpriseprojects build.xml enterpriseprojects overrides targets according to the standard pattern and deploys enterprise only added packages Will commit on a branch, can I get the issue assigned? Details: Used artifact:mvn instead of artifact:deploy as it was giving some strange side effect. Can definitely be improved
          Hide
          Derek Hulley added a comment -

          Not sure what the target fix version is here. I'll await instructions from PHH or MikeF before assigning.

          Show
          Derek Hulley added a comment - Not sure what the target fix version is here. I'll await instructions from PHH or MikeF before assigning.
          Hide
          Gabriele Columbro added a comment -

          Ok Derek, I'm mostly speeding this up for my talk at DevCon so I have something to show in this area. Progress is:

          Enterprise SNAPSHOT deployment tested successfully with:

          ant -f enterpriseprojects/build.xml maven-deploy

          Deployed to the (still private) http://maven.alfresco.com/nexus/content/repositories/enterprise-snapshots/.

          TODO: Fix enterprise specific deployment (seems overridden targets were not run).

          Show
          Gabriele Columbro added a comment - Ok Derek, I'm mostly speeding this up for my talk at DevCon so I have something to show in this area. Progress is: Enterprise SNAPSHOT deployment tested successfully with: ant -f enterpriseprojects/build.xml maven-deploy Deployed to the (still private) http://maven.alfresco.com/nexus/content/repositories/enterprise-snapshots/ . TODO: Fix enterprise specific deployment (seems overridden targets were not run).
          Hide
          Gabriele Columbro added a comment -

          Attached a tentative (still to be completed) patch to show the approach. Does NOT need maven installed since it will be automatically downloaded.

          Just committed this also to https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/BRANCHES/DEV/GCOLUMBRO/v4.0-MAVEN-DEPLOY/ at r31473.

          Show
          Gabriele Columbro added a comment - Attached a tentative (still to be completed) patch to show the approach. Does NOT need maven installed since it will be automatically downloaded. Just committed this also to https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/BRANCHES/DEV/GCOLUMBRO/v4.0-MAVEN-DEPLOY/ at r31473 .
          Hide
          Gabriele Columbro added a comment -

          Hey guys,

          couple of questions:

          1. Can you give me the definitive build instructions for producing a CE and a EE release (as we normally do it for our releases)? When I have that I can test the deployment script on a "real" release package built from the tag

          2. What is Odin? Any particular reason for rescheduling this? Did anyone review the deployment script?

          Thanks,
          Gab

          Show
          Gabriele Columbro added a comment - Hey guys, couple of questions: 1. Can you give me the definitive build instructions for producing a CE and a EE release (as we normally do it for our releases)? When I have that I can test the deployment script on a "real" release package built from the tag 2. What is Odin? Any particular reason for rescheduling this? Did anyone review the deployment script? Thanks, Gab
          Hide
          Gabriele Columbro added a comment - - edited

          Thanks Derek.

          I will continue working on this to define a final procedure. So running the two commands above would produce all the artifacts needed respectively for EE and CE releases.
          And same commands can be used at any time to deploy snapshots (nightlies) from trunk.

          To be able to test it locally (and ultimately in a Bamboo job), I would need a sample of the db_postgresql.properties mentioned in the cmd line. Can you point me to it?
          [DH: You don't need all that stuff; it's just for running unit tests, etc. You only need the build command of choice pointing to the correct build.xml.]

          Show
          Gabriele Columbro added a comment - - edited Thanks Derek. I will continue working on this to define a final procedure. So running the two commands above would produce all the artifacts needed respectively for EE and CE releases. And same commands can be used at any time to deploy snapshots (nightlies) from trunk. To be able to test it locally (and ultimately in a Bamboo job), I would need a sample of the db_postgresql.properties mentioned in the cmd line. Can you point me to it? [DH: You don't need all that stuff; it's just for running unit tests, etc. You only need the build command of choice pointing to the correct build.xml.]
          Hide
          Gabriele Columbro added a comment - - edited

          Thanks Derek.

          Can you then tell me which is the "correct" build command or commands (ant target) that I have to run to have all artifacts produced (ant distribute-something?) and packaged in build/dist, optimally skipping unit test run?

          I was unable to figure out

          [DH:
          <target name="distribute"
          description="Creates the distribution files for all platforms"
          depends="set-build-number,
          incremental,
          distribute-core,
          distribute-non-core,
          revert-changes" />
          ]

          [GC: You are the man! Apart from being the master of Jira Edits :P]

          Show
          Gabriele Columbro added a comment - - edited Thanks Derek. Can you then tell me which is the "correct" build command or commands (ant target) that I have to run to have all artifacts produced (ant distribute-something?) and packaged in build/dist, optimally skipping unit test run? I was unable to figure out [DH: <target name="distribute" description="Creates the distribution files for all platforms" depends="set-build-number, incremental, distribute-core, distribute-non-core, revert-changes" /> ] [GC: You are the man! Apart from being the master of Jira Edits :P]
          Hide
          Gabriele Columbro added a comment -

          Just as a final check. I'm trying to build Alfresco EE 4.0 beta from sources.

          So I'm now running:

          ant distribute -Dalf.build.number=570 -Dbuild.script=enterpriseprojects/build.xml -f continuous.xml

          from svn https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@r31332 (BTW can we tag this? I reconstructed this from Bamboo Build 570)

          Correct?

          (I added -f continuous.xml since with above instructions I got

          BUILD FAILED
          Target "distribute" does not exist in the project "alfresco".

          )

          Show
          Gabriele Columbro added a comment - Just as a final check. I'm trying to build Alfresco EE 4.0 beta from sources. So I'm now running: ant distribute -Dalf.build.number=570 -Dbuild.script=enterpriseprojects/build.xml -f continuous.xml from svn https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@r31332 (BTW can we tag this? I reconstructed this from Bamboo Build 570) Correct? (I added -f continuous.xml since with above instructions I got BUILD FAILED Target "distribute" does not exist in the project "alfresco". )
          Hide
          Gabriele Columbro added a comment -

          This build fails with /Users/mindthegab/Dev/alfresco/workspace/ALF-BINARIES/tomcat/apache-tomcat-5.5.25-virtserver-alfresco-1.1.zip .

          Do I need to have a the ALF-BINARIES folder checked out in that position (../../) for the build to work?

          Try to re-run now after

          cd ../../; svn co https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/BINARIES/ ALF-BINARIES

          Show
          Gabriele Columbro added a comment - This build fails with /Users/mindthegab/Dev/alfresco/workspace/ALF-BINARIES/tomcat/apache-tomcat-5.5.25-virtserver-alfresco-1.1.zip . Do I need to have a the ALF-BINARIES folder checked out in that position (../../) for the build to work? Try to re-run now after cd ../../; svn co https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/BINARIES/ ALF-BINARIES
          Hide
          Gabriele Columbro added a comment -

          Seems that the "distribute" target does NOT produce the DOD amps and that's mainly because the dependent target "distribute-amps" does not include anything to distribute the DOD as it does it for the other AMPs. Is there any workaround or shall I separately call the "incremental-dod5015" target from projects.xml ?

          Show
          Gabriele Columbro added a comment - Seems that the "distribute" target does NOT produce the DOD amps and that's mainly because the dependent target "distribute-amps" does not include anything to distribute the DOD as it does it for the other AMPs. Is there any workaround or shall I separately call the "incremental-dod5015" target from projects.xml ?
          Hide
          Gabriele Columbro added a comment -

          Hey guys can we trigger the discussion to get this actually merged? Has anyone reviewed / tested it? I did and worked fine for both EE and CE.

          Don't want this to be forgotten again ...

          Thanks!

          Show
          Gabriele Columbro added a comment - Hey guys can we trigger the discussion to get this actually merged? Has anyone reviewed / tested it? I did and worked fine for both EE and CE. Don't want this to be forgotten again ... Thanks!
          Hide
          Derek Hulley added a comment -

          Running trial build against the branch: http://bamboo.man.alfresco.com:8085/browse/BRANCH-SWIFTMAVEN

          Show
          Derek Hulley added a comment - Running trial build against the branch: http://bamboo.man.alfresco.com:8085/browse/BRANCH-SWIFTMAVEN
          Hide
          Mark Rogers added a comment -

          Once its implemented there will be no need for people to see this issue. Its the fact that its not done that's causing an issue. Would it make sense to manually deploy the Enterprise 4 and Community 4 c, and d bits and then worry about automating it after?

          Show
          Mark Rogers added a comment - Once its implemented there will be no need for people to see this issue. Its the fact that its not done that's causing an issue. Would it make sense to manually deploy the Enterprise 4 and Community 4 c, and d bits and then worry about automating it after?
          Hide
          Gabriele Columbro added a comment - - edited

          Yes, totally.

          So let's formalize this:

          • I will test my script on the 4.0c and 4.0d tags, deploying artifacts on maven.alfresco.com/nexus/content/groups/public
          • When it's there, can you validate whether we have all the main Community artifacts (JARs/WARs/AMPs/ZIPs) or there is anything obvious missing?
          • Done that, I can commit the final script and merge in trunk
          • Then I can work to test this in automation on our CI server (for SNAPSHOTs and then for releases, both for EE and CE)
          • Then I can write a quick README on how to manually / automatically deploy artifacts (also for Community users)

          Makes sense to you?

          Show
          Gabriele Columbro added a comment - - edited Yes, totally. So let's formalize this: I will test my script on the 4.0c and 4.0d tags, deploying artifacts on maven.alfresco.com/nexus/content/groups/public When it's there, can you validate whether we have all the main Community artifacts (JARs/WARs/AMPs/ZIPs) or there is anything obvious missing? Done that, I can commit the final script and merge in trunk Then I can work to test this in automation on our CI server (for SNAPSHOTs and then for releases, both for EE and CE) Then I can write a quick README on how to manually / automatically deploy artifacts (also for Community users) Makes sense to you?
          Hide
          Mark Rogers added a comment -

          Yes that makes sense.

          I note we are missing Community 3.4.d as well. (Which is the last stable 3.4 release.)

          As far as I can see there is only the alfresco.war in Maven. So should we have share.war in there? I'm going to have to learn about Maven.

          Show
          Mark Rogers added a comment - Yes that makes sense. I note we are missing Community 3.4.d as well. (Which is the last stable 3.4 release.) As far as I can see there is only the alfresco.war in Maven. So should we have share.war in there? I'm going to have to learn about Maven.
          Hide
          Gabriele Columbro added a comment -

          Ok will execute on that ASAP this week.

          Will have to deploy 3.4d as well I guess

          Actually the amount of artifacts I deploy is much bigger (also all WARs, JARs, AMPs are there), following this pattern:

          Alfresco WARs --> http://maven.alfresco.com/nexus/content/groups/public/org/alfresco/alfresco/
          Share WARs --> http://maven.alfresco.com/nexus/content/groups/public/org/alfresco/share/
          etc.

          Also you can login in the Nexus interface and use the GAV (groupId, artifactId, version) search:

          http://maven.alfresco.com/nexus/index.html#nexus-search;gav~org.alfresco~~4.0.b~~

          BTW, if you want to see exactly which artifacts get deployed you can check directly the pretty straightforward Ant files doing the deployment:

          https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/BRANCHES/DEV/GCOLUMBRO/v4.0-MAVEN-DEPLOY/root/maven.xml

          and the correspondent in the Enterprise Project folder.

          Show
          Gabriele Columbro added a comment - Ok will execute on that ASAP this week. Will have to deploy 3.4d as well I guess Actually the amount of artifacts I deploy is much bigger (also all WARs, JARs, AMPs are there), following this pattern: Alfresco WARs --> http://maven.alfresco.com/nexus/content/groups/public/org/alfresco/alfresco/ Share WARs --> http://maven.alfresco.com/nexus/content/groups/public/org/alfresco/share/ etc. Also you can login in the Nexus interface and use the GAV (groupId, artifactId, version) search: http://maven.alfresco.com/nexus/index.html#nexus-search;gav~org.alfresco~~4.0.b~~ BTW, if you want to see exactly which artifacts get deployed you can check directly the pretty straightforward Ant files doing the deployment: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/BRANCHES/DEV/GCOLUMBRO/v4.0-MAVEN-DEPLOY/root/maven.xml and the correspondent in the Enterprise Project folder.
          Hide
          Maurizio Pillitu added a comment -

          Would be very useful to deploy the *-src.zip files shipped with the SDK to the Maven repository so that devs can enable their IDE for remote debugging and source code inspection.

          Show
          Maurizio Pillitu added a comment - Would be very useful to deploy the *-src.zip files shipped with the SDK to the Maven repository so that devs can enable their IDE for remote debugging and source code inspection.
          Hide
          Daniele Segato added a comment -

          I totally agree with Maurizio.

          Being able to debug is a must, and that means having the source code attached to the maven artifacts.

          Show
          Daniele Segato added a comment - I totally agree with Maurizio. Being able to debug is a must, and that means having the source code attached to the maven artifacts.
          Hide
          Gabriele Columbro added a comment - - edited

          Fixed community vs enterprise and removed classifier on https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/BRANCHES/DEV/GCOLUMBRO/v4.0-MAVEN-DEPLOY/.

          Convention is:

          groupId: org.alfresco deployed on repository http://maven.alfresco.com/nexus/content/repositories/releases/ --> Community Artifacts
          groupId: org.alfresco.enterprise deployed on repository http://maven.alfresco.com/nexus/content/repositories/enterprise-releases/ --> Enterprise artifacts

          Obviously SNAPSHOTS will follow the same pattern but respectively deploy to:

          http://maven.alfresco.com/nexus/content/repositories/snapshots/

          and

          http://maven.alfresco.com/nexus/content/repositories/enterprise-snapshots/

          Also updated README-maven-deploy.txt in the root. Now proceeding with testing.

          Show
          Gabriele Columbro added a comment - - edited Fixed community vs enterprise and removed classifier on https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/BRANCHES/DEV/GCOLUMBRO/v4.0-MAVEN-DEPLOY/ . Convention is: groupId: org.alfresco deployed on repository http://maven.alfresco.com/nexus/content/repositories/releases/ --> Community Artifacts groupId: org.alfresco.enterprise deployed on repository http://maven.alfresco.com/nexus/content/repositories/enterprise-releases/ --> Enterprise artifacts Obviously SNAPSHOTS will follow the same pattern but respectively deploy to: http://maven.alfresco.com/nexus/content/repositories/snapshots/ and http://maven.alfresco.com/nexus/content/repositories/enterprise-snapshots/ Also updated README-maven-deploy.txt in the root. Now proceeding with testing.
          Hide
          Gabriele Columbro added a comment - - edited
          Show
          Gabriele Columbro added a comment - - edited Testing now Community SNAPSHOT deployment with: ant -f continuous.xml maven-deploy -Dmaven.custom.label=mvn- r35250 (maven.custom.label is NOT mandatory, just added to make sure it's clear this deployment does NOT come from trunk) Check results on http://maven.alfresco.com/nexus/content/repositories/snapshots/org/alfresco (UPDATE) Test was successful, see: http://maven.alfresco.com/nexus/content/repositories/snapshots/org/alfresco/alfresco/4.0.b-mvn-r35250-SNAPSHOT/ http://maven.alfresco.com/nexus/content/repositories/snapshots/org/alfresco/alfresco-core/4.0.b-mvn-r35250-SNAPSHOT/ http://maven.alfresco.com/nexus/content/repositories/snapshots/org/alfresco/alfresco-repository/4.0.b-mvn-r35250-SNAPSHOT/ ... etc etc etc ... Also AMPs have been deployed, see an example at: http://maven.alfresco.com/nexus/content/repositories/snapshots/org/alfresco/alfresco-wcm-quickstart-repo/4.0.b-mvn-r35250-SNAPSHOT/
          Show
          Gabriele Columbro added a comment - - edited Testing now Community RELEASE deployment with: ant -f continuous.xml maven-deploy -Dmaven.custom.label=mvn- r35250 -Dmaven.isRelease=true (maven.custom.label is NOT mandatory, just added to make sure it's clear this deployment does NOT come from trunk) Check results on http://maven.alfresco.com/nexus/content/repositories/releases/org/alfresco (UPDATE) Test was successful: http://maven.alfresco.com/nexus/content/repositories/releases/org/alfresco/alfresco/4.0.b-mvn-r35250/ http://maven.alfresco.com/nexus/content/repositories/releases/org/alfresco/alfresco-core/4.0.b-mvn-r35250/ http://maven.alfresco.com/nexus/content/repositories/releases/org/alfresco/alfresco-repository/4.0.b-mvn-r35250/ http://maven.alfresco.com/nexus/content/repositories/releases/org/alfresco/alfresco-repository/4.0.b-mvn-r35250/ etc..etc...
          Hide
          Vincent Jansen added a comment -

          Is there a difference between the 4.0.b and your 4.0.b-mvn-r35250 because the 4.0.b does not include the alfresco-web-service-client (see issue ALF-13439).
          Should we use the 4.0.b-mvn-r35250 instead of the 4.0.b or will the 4.0.d be released soon?

          Show
          Vincent Jansen added a comment - Is there a difference between the 4.0.b and your 4.0.b-mvn- r35250 because the 4.0.b does not include the alfresco-web-service-client (see issue ALF-13439 ). Should we use the 4.0.b-mvn- r35250 instead of the 4.0.b or will the 4.0.d be released soon?
          Hide
          Gabriele Columbro added a comment - - edited

          Yeah with the automated procedure I made sure also the web-service-client is available at: http://maven.alfresco.com/nexus/content/repositories/releases/org/alfresco/alfresco-web-service-client/4.0.b-mvn-r35250/

          But please avoid using mvn-r35250 artifacts, these are deployed from an outdated branch where I'm testing the deployment. As soon as we merge this we should make available all the "proper" release artifacts.

          A good thing would be for the Community/Alfrescans to check if I'm missing some key artifacts by looking at

          http://maven.alfresco.com/nexus/index.html#nexus-search;gav~org.alfresco~~4.0.b-mvn-r35250~~

          so that I can fix it before we merge this and start automatically distributing Maven artifacts.

          Show
          Gabriele Columbro added a comment - - edited Yeah with the automated procedure I made sure also the web-service-client is available at: http://maven.alfresco.com/nexus/content/repositories/releases/org/alfresco/alfresco-web-service-client/4.0.b-mvn-r35250/ But please avoid using mvn- r35250 artifacts, these are deployed from an outdated branch where I'm testing the deployment. As soon as we merge this we should make available all the "proper" release artifacts. A good thing would be for the Community/Alfrescans to check if I'm missing some key artifacts by looking at http://maven.alfresco.com/nexus/index.html#nexus-search;gav~org.alfresco~~4.0.b-mvn-r35250~~ so that I can fix it before we merge this and start automatically distributing Maven artifacts.
          Show
          dward added a comment - Created test build plans https://bamboo.alfresco.com/bamboo/browse/ALF-HEADCOMMMAVEN and https://bamboo.alfresco.com/bamboo/browse/ALF-HEADENTMAVEN
          Hide
          Jean-Rémy Revy added a comment -

          @Gabriele

          First, thanks for your job . I was following this JIRA for a few monthes, and I'm very pleased to see it move !

          I tried your script in order to put libraries into our company repository, and reading this post, I saw the conventions you chose.

          The fact that EE libs change from org.alfresco to org.alfresco.enterprise looks strange for me. Like a method name, in its signature, groupId and, artifactId are the most importants keys, contrary to version, classifier or type which are only parameters.

          I'm not able to find (quickly) a straight answer to this, only the clues given on maven doc : http://maven.apache.org/guides/getting-started/index.html

          I think a better approach, in a maven way, would be to add a classifier, like what is done for Alfresco CE versions. This could be EE, enterprise, ...
          Maybe there is a reason for you choice, but I don't see why at this moment.

          Regards.

          Show
          Jean-Rémy Revy added a comment - @Gabriele First, thanks for your job . I was following this JIRA for a few monthes, and I'm very pleased to see it move ! I tried your script in order to put libraries into our company repository, and reading this post, I saw the conventions you chose. The fact that EE libs change from org.alfresco to org.alfresco.enterprise looks strange for me. Like a method name, in its signature, groupId and, artifactId are the most importants keys, contrary to version, classifier or type which are only parameters. I'm not able to find (quickly) a straight answer to this, only the clues given on maven doc : http://maven.apache.org/guides/getting-started/index.html I think a better approach, in a maven way, would be to add a classifier, like what is done for Alfresco CE versions. This could be EE, enterprise, ... Maybe there is a reason for you choice, but I don't see why at this moment. Regards.
          Hide
          Samuel Langlois added a comment -

          @Jean-Rémy

          Thanks for your nice comment.

          Classifiers are not appropriate, because Community and Enterprise versions are not cut from the same set of sources. The tags are different, for instance.
          What we could have done is keep the same artifactId/groupId and use different versions, for instance: 4.0.0, 4.0.1, ... for EE and 4.0.c, 4.0.d, ... for CE.
          However, the versioning scheme changed several times in the past, and we wanted to be resilient from such changes.
          Since the groupId is the same for all Alfresco artifacts, you can set it in a property, and you have a nice and easy way to switch from Community to Enterprise.

          Hope this helps,

          Show
          Samuel Langlois added a comment - @Jean-Rémy Thanks for your nice comment. Classifiers are not appropriate, because Community and Enterprise versions are not cut from the same set of sources. The tags are different, for instance. What we could have done is keep the same artifactId/groupId and use different versions, for instance: 4.0.0, 4.0.1, ... for EE and 4.0.c, 4.0.d, ... for CE. However, the versioning scheme changed several times in the past, and we wanted to be resilient from such changes. Since the groupId is the same for all Alfresco artifacts, you can set it in a property, and you have a nice and easy way to switch from Community to Enterprise. Hope this helps,
          Hide
          Gabriele Columbro added a comment -

          This was merged in HEAD and works to deploy in build Alfresco versions. I'd say: can we configure that to deploy snapshots and then close this issue?

          Show
          Gabriele Columbro added a comment - This was merged in HEAD and works to deploy in build Alfresco versions. I'd say: can we configure that to deploy snapshots and then close this issue?
          Hide
          Gabriele Columbro added a comment -

          Relating to the natural follow up to this issue, AKA ALF-14390 - for publishing POMs.

          Show
          Gabriele Columbro added a comment - Relating to the natural follow up to this issue, AKA ALF-14390 - for publishing POMs.
          Hide
          Samuel Langlois added a comment -

          Community continuous builds are now automatically uploaded to our Artifacts repository.
          They can be accessed through this URL :
          https://artifacts.alfresco.com/nexus/content/groups/public-snapshots/

          Currently deployed version is 4.2.a-SNAPSHOT

          Hope this helps

          Show
          Samuel Langlois added a comment - Community continuous builds are now automatically uploaded to our Artifacts repository. They can be accessed through this URL : https://artifacts.alfresco.com/nexus/content/groups/public-snapshots/ Currently deployed version is 4.2.a-SNAPSHOT Hope this helps
          Hide
          Ravi Manthena added a comment -

          Use Head-QA build 187 to test this issue.

          Show
          Ravi Manthena added a comment - Use Head-QA build 187 to test this issue.
          Hide
          Alfresco QA Team added a comment -

          Hi, Samuel

          Can we close this improvement?

          Show
          Alfresco QA Team added a comment - Hi, Samuel Can we close this improvement?
          Hide
          Samuel Langlois added a comment -

          Please close it, definitely!
          Just make a search in http://artifacts.alfresco.com/ to see all the nice Alfresco artifacts that are available

          Show
          Samuel Langlois added a comment - Please close it, definitely! Just make a search in http://artifacts.alfresco.com/ to see all the nice Alfresco artifacts that are available
          Hide
          Alfresco QA Team added a comment -

          Closed.

          Show
          Alfresco QA Team added a comment - Closed.

            People

            • Assignee:
              Closed Issues
              Reporter:
              Gabriele Columbro
            • Votes:
              2 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Date of First Response: