[
https://issues.apache.org/jira/browse/SCM-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961142#comment-17961142
]
ASF GitHub Bot commented on SCM-353:
------------------------------------
jira-importer opened a new issue, #573:
URL: https://github.com/apache/maven-scm/issues/573
**[Jason
Harrop](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jharrop)**
opened
**[SCM-353](https://issues.apache.org/jira/browse/SCM-353?redirect=false)** and
commented
If I don't use the \<executions> element, the embedded configuration is used.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-scm-plugin</artifactId>
<version>1.0</version>
<configuration>
<connectionUrl>
scm:svn:http://dev.plutext.org/svn/docx4j/trunk/docx4j
</connectionUrl>
<checkoutDirectory>docx4j</checkoutDirectory>
<goals>validate</goals>
</configuration>
</plugin>
However, I would like to checkout 2 modules from each of 2 different
repositories.
If I introduce \<executions>, the plugin doesn't read the embedded
configuration. Instead, it falls back to what is defined in the \<scm> element
(or if none exists, the super pom).
Here is what I have trying:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-scm-plugin</artifactId>
<version>1.0</version>
<configuration>
<skipCheckoutIfExists />
</configuration>
<executions>
<execution>
<id>checkout-docx4j</id>
<configuration>
<connectionUrl>
scm:svn:http://dev.plutext.org/svn/docx4j/trunk/docx4j
</connectionUrl>
<checkoutDirectory>docx4j</checkoutDirectory>
</configuration>
<goals>
<goal>validate</goal>
</goals>
</execution>
<execution>
<id>checkout-jackrabbit-webapp</id>
<configuration>
<connectionUrl>
scm:svn:http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-webapp
</connectionUrl>
<checkoutDirectory>
jackrabbit-webapp
</checkoutDirectory>
</configuration>
<goals>
<goal>validate</goal>
</goals>
</execution>
</executions>
</plugin>
---
No further details from
[SCM-353](https://issues.apache.org/jira/browse/SCM-353?redirect=false)
> maven-scm-plugin configuration is ignored if executions present
> ---------------------------------------------------------------
>
> Key: SCM-353
> URL: https://issues.apache.org/jira/browse/SCM-353
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-plugin
> Environment: Maven version: 2.0.7
> Java version: 1.6.0_01
> Reporter: Jason Harrop
> Assignee: Dan Tran
> Priority: Minor
>
> If I don't use the <executions> element, the embedded configuration is used.
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-scm-plugin</artifactId>
> <version>1.0</version>
> <configuration>
> <connectionUrl>
>
> scm:svn:http://dev.plutext.org/svn/docx4j/trunk/docx4j
> </connectionUrl>
> <checkoutDirectory>docx4j</checkoutDirectory>
> <goals>validate</goals>
> </configuration>
> </plugin>
> However, I would like to checkout 2 modules from each of 2 different
> repositories.
> If I introduce <executions>, the plugin doesn't read the embedded
> configuration. Instead, it falls back to what is defined in the <scm>
> element (or if none exists, the super pom).
> Here is what I have trying:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-scm-plugin</artifactId>
> <version>1.0</version>
> <configuration>
> <skipCheckoutIfExists />
> </configuration>
> <executions>
> <execution>
> <id>checkout-docx4j</id>
> <configuration>
> <connectionUrl>
>
> scm:svn:http://dev.plutext.org/svn/docx4j/trunk/docx4j
> </connectionUrl>
>
> <checkoutDirectory>docx4j</checkoutDirectory>
> </configuration>
> <goals>
> <goal>validate</goal>
> </goals>
> </execution>
> <execution>
> <id>checkout-jackrabbit-webapp</id>
> <configuration>
> <connectionUrl>
>
> scm:svn:http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-webapp
> </connectionUrl>
> <checkoutDirectory>
> jackrabbit-webapp
> </checkoutDirectory>
> </configuration>
> <goals>
> <goal>validate</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
