Build Failure

[Patrick Simpson]

Hi all,

Just installed Sakai 10 on my Mac(10.11.5), I believe Tomcat and Maven are up and running. I got through the whole process but get the following error during the build and deployment.

Everything is installed in /Users/Patrick..

[ERROR] Failed to execute goal org.sakaiproject.maven.plugins:sakai:1.4.3:deploy (default-cli) on project sakai-component-manager: Execution default-cli of goal org.sakaiproject.maven.plugins:sakai:1.4.3:deploy failed: basedir /pathto/tomcathome/lib does not exist -> [Help 1]

Any ideas?



Thanks in advance.

[JAMES NORMAN]

Error messages are your friend - let's take a look:

deploy failed: basedir /pathto/tomcathome/lib does not exist

Does your tomcat home folder have a subfolder called "lib" in it? It probably also needs some others too.

[Patrick Simpson]

Got the path issue sorted, just needed to add the correct path to Tomcat however, when I tried the build again I got this message

"Failed to execute goal pl.project13.maven:git-commit-id-plugin:2.2.1:revision (default) on project configuration-bundles: .git directory is not found! Please specify a valid [dotGitDirectory] in your pom.xml -> [Help 1]"

Any ideas?

[James Norman Scoble]

Well, it wants to know where your .git folder is.

Try opening the pom.xml file in an editor and looking for "dotGitDirectory".

--
You received this message because you are subscribed to the Google Groups "Sakai Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sakai-dev+unsubscribe@apereo.org.
To post to this group, send email to saka...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/sakai-dev/.

[Austin]

Anyone else run into this error while building the config module in sakai 11.2?

"[ERROR] Failed to execute goal pl.project13.maven:git-commit-id-plugin:2.2.1:revision (default) on project configuration-bundles: .git directory is not found! Please specify a valid [dotGitDirectory] in your pom.xml -> [Help 1]"

I'm seeing this error while trying to build 11.2 and the 11.x branch.  I thought that maybe it was because I didn't have git installed, but after installing it I'm still seeing this error.  Tried a mvn clean as well, but no luck.   Tried maven 3.2.3 and the latest 3.3.9 as welll, but that didn't help either.  Also, would it matter if I downloaded the source as a zip vs. checking the code out with git?

James mentioned looking for "dotGitDirectory", but I don't see that config anywhere in the 11.x code.  Although there's a mention about it in https://github.com/ktoso/maven-git-commit-id-plugin

But I'm guessing that since it's not in the sakai code, it hasn't been needed for other people to build successfully.

Also, I didn't have this problem building 11.1 (a long time ago, probably last summer), but I see that the pl.project13.maven was newly added in 11.2's config -> configuration -> bundles -> pom.xml

Thanks,

Austin

[Brad Szabo]

Hi, Austin.

This issue means that you must have a source directory that does not include the git repository (i.e. if you obtained it via an archive file vs git clone). The git-commit-id-plugin is looking for the .git location so it can extract all of the information to use in the build, which is its entire purpose.

If Sakai source is provided via an archive without the full source repository, then the build configuration should have that plugin quietly skip doing its repository metadata extraction tasks and not fail as it currently is, by changing the plugin default property:

<failOnNoGitDirectory>true</failOnNoGitDirectory>

to

<failOnNoGitDirectory>false</failOnNoGitDirectory>

That plugin unfortunately does not expose an expression that you can pass on the command line, so you will need to edit the configuration:

diff --git a/config/configuration/bundles/pom.xml b/config/configuration/bundles/pom.xml
index 8aef928..14560d4 100644
--- a/config/configuration/bundles/pom.xml
+++ b/config/configuration/bundles/pom.xml

                        <plugin>
                                <groupId>pl.project13.maven</groupId>
                                <artifactId>git-commit-id-plugin</artifactId>
                                <version>2.2.1</version>
+                              <configuration>
+                                  <failOnNoGitDirectory>false</failOnNoGitDirectory>
+                              </configuration>
                                <executions>
                                        <execution>
                                                <goals>
                                                        <goal>revision</goal>
                                                </goals>
                                        </execution>
                                </executions>
                        </plugin>

So either clone Sakai from git to avoid this and insure that the version info is available for use, or skip by doing above.

Thanks,

Brad

---

From: "Austin" <aust...@hawaii.edu>
To: "James Norman Scoble" <jsc...@uwc.ac.za>
Cc: "Patrick Simpson" <pwmsim...@gmail.com>, "Sakai Development" <saka...@apereo.org>
Sent: Thursday, February 2, 2017 1:56:26 PM
Subject: Re: [sakai-dev] Re: Build Failure

To unsubscribe from this group and stop receiving emails from it, send an email to sakai-dev+...@apereo.org.

To post to this group, send email to saka...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/sakai-dev/.

--
You received this message because you are subscribed to the Google Groups "Sakai Development" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sakai-dev+...@apereo.org.

To post to this group, send email to saka...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/sakai-dev/.

--
You received this message because you are subscribed to the Google Groups "Sakai Development" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sakai-dev+...@apereo.org.

[Austin]

Thanks Brad,  cloning sakai from git (instead of downloading the archive) worked!

To unsubscribe from this group and stop receiving emails from it, send an email to sakai-dev+unsubscribe@apereo.org.

To post to this group, send email to saka...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/sakai-dev/.

--
You received this message because you are subscribed to the Google Groups "Sakai Development" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sakai-dev+unsubscribe@apereo.org.

To post to this group, send email to saka...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/sakai-dev/.

--
You received this message because you are subscribed to the Google Groups "Sakai Development" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sakai-dev+unsubscribe@apereo.org.

[Matthew Buckett]

Sorry about this and nice catch Brad, it looks like there's an
existing issue out for this problem:

https://jira.sakaiproject.org/browse/SAK-31502

I've created a pull request that switches to a different plugin that
handles the no .git folder better (allows providing a default value),
but until this is in an actual source download brad's fix is the best
suggestion.

On 2 February 2017 at 23:52, Austin <aust...@hawaii.edu> wrote:
> Thanks Brad, cloning sakai from git (instead of downloading the archive)
> worked!
>
> On Thu, Feb 2, 2017 at 11:59 AM, Brad Szabo <bsz...@unicon.net> wrote:
>>

Matthew Buckett
VLE Developer

WebLearn, Academic IT
IT Services, University of Oxford
13 Banbury Road, OX2 6NN
Tel: 01865 283349