mvn install:install fails in amp project

[Bindu Wavell]

I'm trying to work through the best way to configure IntelliJ to work with the allinoneproject. IntelliJ is able to run goals but not lifecycle phases as pre-steps for running a tomcat instance.

Any idea what is needed to get mvn install:install to work in amp projects?

Many Thanks!

[Gabriele Columbro]

Actually the phase that runs the amp is 'integration-test' which is just before install. So ideally it's all you need.

But if you want to make sure you get the latest AMP code installed (e.g. the repo amp sample in the all-in-one) you need an install to make sure the latest dep is picked up.

HTH and sorry for the long msg approval time, was on the road for the last weeks and this must have slipped in my email.

Gab

--
You received this message because you are subscribed to the Google Groups "Maven Alfresco Lifecycle Discussion Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maven-alfresc...@googlegroups.com.
To post to this group, send email to maven-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/maven-alfresco?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Gabriele Columbro
Principal Architect, Consulting Services
Alfresco Software
twitter: @mindthegabz
blog: http://mindthegab.com
mobile: +31627565013

[Bindu Wavell]

Hi Gab,

I'm by no means a maven ninja, just fumbling along at this point. I'm trying to integrate the allinone/amp archetypes into Eclipse and IntelliJ so that we can use these tools for rapid development. I'm running into different issues with each of the IDEs related to "non-standard" (I say that lightly of course) features in the alfresco lifecycle stuff.

So for example the m2e maven infrastructure in eclipse is having a hard time with the setversion lifecycle introduced by the maven-alfresco-plugin (seems like I should be able to work around this but so far have failed, although I think I'm on the right track.) It's also having a hard time with the jetty.xml file which requires filtering to bring in the alfresco db properties. I think the XML validator is freaking out because the ${} syntax is not XML friendly... but I could be wrong about that...

In IntelliJ I run into different issues. It seems to completely fail to understand the amp packaging type provided by the maven-alfresco-plugin. What I've been trying to do is to cause maven to actually do the build of that project rather than whatever maven wrapper they have in IntelliJ. I've setup an app server configuration in IntelliJ and configured appropriate webapps based on the modules created by the allinone archetype. This mostly works except for the amp module, where I have to get the amp installed... prior to the alfresco module building... IntelliJ provides the ability to run maven goals and a pre-build step like this, but they do not provide the ability to run a lifecycle phase at this point. I've worked around this by defining an external tool that simply runs "mvn install" in the amp module.

For the IntelliJ effort, it seems like I need the install phase to complete so that the amp is installed in the local repo, such that when I go to package the alfresco module it can pull the amp out of the repo?

No problem on the late reply :) I didn't see these replies either ;) Just came and looked manually to see what discussions were going on here and saw your responses.

-- Bindu