[jboss-jira] [JBoss JIRA] (DROOLS-298) kie-ci support for custom location of m2 local repository

Mon Oct 14 04:37:35 EDT 2013

    [ https://issues.jboss.org/browse/DROOLS-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12813801#comment-12813801 ] 

Lukáš Petrovický commented on DROOLS-298:
-----------------------------------------

This issue is actually a bit more severe than it seems:

1) When "user.home" property is not set (for whatever reason), MavenRepository may fail with an obscure exception:

java.lang.NoClassDefFoundError: Could not initialize class org.kie.scanner.MavenRepository
	at org.kie.scanner.ArtifactResolver.getMavenProjectForGAV(ArtifactResolver.java:78)

2) You will get the same exception when the POM you're trying to parse cannot be parsed. (Or when some of the dependencies cannot be located.) This comes from the way how .embedder.MavenProjectLoader parses the POM - when the parsing fails in the static inner class, you won't find out why (the POM error), you just get the above.

3) You should be able to provide a settings.xml to the parser; since that is (AFAIK) the only way to tell Maven that you have additional repositories with additional dependencies. (Think in-house applications.)

> kie-ci support for custom location of m2 local repository
> ---------------------------------------------------------
>
>                 Key: DROOLS-298
>                 URL: https://issues.jboss.org/browse/DROOLS-298
>             Project: Drools
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions:  6.0.0.CR4
>            Reporter: Maciej Swiderski
>            Assignee: Mario Fusco
>
> currently kie-ci assumes that local m2 repo is stored in ~/.m2/repository which is not always the case as it can be configured via settings.xml. This is common case in many organization due to limitations of data that can be stored in user home directory or backup routines. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira