[
https://issues.apache.org/jira/browse/USERGRID-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14031974#comment-14031974
]
George Reyes commented on USERGRID-176:
---------------------------------------
Currently the problem seems to exist in 3.2 where it cannot find the correct
.jar file when using a more up to date plugin. Instead of looking for the
ROOT.war which is generated, it looks for the snapshot name. Below is the
offending plug in that fails when moved to version 2.5.1 in the usergrid-rest
pom.xml file.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-install-plugin</artifactId>
<version>2.5.1</version>
<executions>
<execution>
<id>install jar</id>
<phase>install</phase>
<goals>
<goal>install-file</goal>
</goals>
<configuration>
<packaging>jar</packaging>
<artifactId>${project.artifactId}</artifactId>
<groupId>${project.groupId}</groupId>
<version>${project.version}</version>
<file>
${project.build.directory}/${project.artifactId}-${project.version}.jar
</file>
</configuration>
</execution>
</executions>
</plugin>
The question that remains is that why is it fine with using the ROOT.war as
default but enforces the directory when upgraded to 2.5.1
> Fix Usergrid so that it works with maven 3.2
> --------------------------------------------
>
> Key: USERGRID-176
> URL: https://issues.apache.org/jira/browse/USERGRID-176
> Project: Usergrid
> Issue Type: Bug
> Reporter: George Reyes
> Assignee: George Reyes
>
> Currently usergrid doesn't work with the latest stable build of maven. ( 3.2
> or 3.1 ) This ticket will track the effort that is being made to correct that
> issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
