[jira] Created: (MJAVADOC-326) docletPath configuration parameter is concatenated incorrectly
docletPath configuration parameter is concatenated incorrectly
--
Key: MJAVADOC-326
URL: https://jira.codehaus.org/browse/MJAVADOC-326
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.8
Reporter: Erik
No separator is added between path induced from docletArtifacts and docletPath.
This makes the docletPath parameter useless.
Here's a patch (svn diff):
Index: src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
===
--- src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
(revision 1170063)
+++ src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
(working copy)
@@ -2728,6 +2728,9 @@
if ( !StringUtils.isEmpty( docletPath ) )
{
+char tail = path.charAt(path.length()-1);
+if( tail != ':' || tail != ';')
+path.append(":");
path.append( JavadocUtil.unifyPathSeparator( docletPath ) );
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MJAVADOC-326) docletPath configuration parameter is concatenated incorrectly
[
https://jira.codehaus.org/browse/MJAVADOC-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=278615#comment-278615
]
Erik edited comment on MJAVADOC-326 at 9/13/11 2:48 AM:
I suck at jira, apparently.. Here's the svn diff again.
{code}
Index: src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
===
--- src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
(revision 1170063)
+++ src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
(working copy)
@@ -2728,6 +2728,9 @@
if ( !StringUtils.isEmpty( docletPath ) )
{
+char tail = path.charAt(path.length()-1);
+if( tail != ':' || tail != ';')
+path.append(":");
path.append( JavadocUtil.unifyPathSeparator( docletPath ) );
}
{code}
was (Author: one-man-bucket):
{code}
if ( !StringUtils.isEmpty( docletPath ) )
{
char tail = path.charAt(path.length()-1);
if( tail != ':' || tail != ';')
path.append(":");
path.append( JavadocUtil.unifyPathSeparator( docletPath ) );
}
{code}
> docletPath configuration parameter is concatenated incorrectly
> --
>
> Key: MJAVADOC-326
> URL: https://jira.codehaus.org/browse/MJAVADOC-326
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Erik
>
> No separator is added between path induced from docletArtifacts and
> docletPath. This makes the docletPath parameter useless.
> Here's a patch (svn diff):
> Index: src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
> ===
> --- src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
> (revision 1170063)
> +++ src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
> (working copy)
> @@ -2728,6 +2728,9 @@
>
> if ( !StringUtils.isEmpty( docletPath ) )
> {
> +char tail = path.charAt(path.length()-1);
> +if( tail != ':' || tail != ';')
> +path.append(":");
> path.append( JavadocUtil.unifyPathSeparator( docletPath ) );
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAVADOC-326) docletPath configuration parameter is concatenated incorrectly
[
https://jira.codehaus.org/browse/MJAVADOC-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=278615#comment-278615
]
Erik commented on MJAVADOC-326:
---
{code}
if ( !StringUtils.isEmpty( docletPath ) )
{
char tail = path.charAt(path.length()-1);
if( tail != ':' || tail != ';')
path.append(":");
path.append( JavadocUtil.unifyPathSeparator( docletPath ) );
}
{code}
> docletPath configuration parameter is concatenated incorrectly
> --
>
> Key: MJAVADOC-326
> URL: https://jira.codehaus.org/browse/MJAVADOC-326
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Erik
>
> No separator is added between path induced from docletArtifacts and
> docletPath. This makes the docletPath parameter useless.
> Here's a patch (svn diff):
> Index: src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
> ===
> --- src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
> (revision 1170063)
> +++ src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
> (working copy)
> @@ -2728,6 +2728,9 @@
>
> if ( !StringUtils.isEmpty( docletPath ) )
> {
> +char tail = path.charAt(path.length()-1);
> +if( tail != ':' || tail != ';')
> +path.append(":");
> path.append( JavadocUtil.unifyPathSeparator( docletPath ) );
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MJAVADOC-326) docletPath configuration parameter is concatenated incorrectly
[
https://jira.codehaus.org/browse/MJAVADOC-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MJAVADOC-326.
--
Resolution: Fixed
Fix Version/s: 2.8.1
Assignee: Herve Boutemy
fixed in [r1170082|http://svn.apache.org/viewvc?rev=1170082&view=rev]
I added a configuration in ITs to see the bug then bugfix in action, even if I
didn't update corresponding verify.bsh scripts to automate the check
thanks for the report
> docletPath configuration parameter is concatenated incorrectly
> --
>
> Key: MJAVADOC-326
> URL: https://jira.codehaus.org/browse/MJAVADOC-326
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Erik
>Assignee: Herve Boutemy
> Fix For: 2.8.1
>
>
> No separator is added between path induced from docletArtifacts and
> docletPath. This makes the docletPath parameter useless.
> Here's a patch (svn diff):
> Index: src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
> ===
> --- src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
> (revision 1170063)
> +++ src/main/java/org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java
> (working copy)
> @@ -2728,6 +2728,9 @@
>
> if ( !StringUtils.isEmpty( docletPath ) )
> {
> +char tail = path.charAt(path.length()-1);
> +if( tail != ':' || tail != ';')
> +path.append(":");
> path.append( JavadocUtil.unifyPathSeparator( docletPath ) );
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-695) Problem of path for additionalConfig with sub-modules
Problem of path for additionalConfig with sub-modules
-
Key: MECLIPSE-695
URL: https://jira.codehaus.org/browse/MECLIPSE-695
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Workspace settings
Affects Versions: 2.8
Reporter: Alexandre Garnier
When defining path to additionalConfig files in parent pom (relative to pom.xml
location), sub-modules did not find them.
{code:language=xml}
[...]
module
[...]
org.apache.maven.plugins
maven-eclipse-plugin
.settings/org.eclipse.core.resources.prefs
settings/org.eclipse.core.resources.prefs
[...]
{code}
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-eclipse-plugin:2.8:eclipse (default-cli) on
project module: Unable to resolve resource location:
settings/org.eclipse.core.resources.prefs
{code}
It works fine in 2.7.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHARED-167) dependency:tree omits batik-js
[
https://jira.codehaus.org/browse/MSHARED-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=278762#comment-278762
]
David Tombs commented on MSHARED-167:
-
This issue just caused me some grief. Could this discrepancy between
dependency:tree and the actual tree used possibly be documented in the
dependency:tree docs?
> dependency:tree omits batik-js
> --
>
> Key: MSHARED-167
> URL: https://jira.codehaus.org/browse/MSHARED-167
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
>Affects Versions: maven-dependency-tree-1.2
> Environment: Maven 3.0, Ubuntu, JDK 6.
>Reporter: Jesse Glick
> Attachments:
> test_test-dependency-tree_jar_1.0-SNAPSHOT_101018-185145.zip
>
>
> (Not sure what the right place to file this is. {{maven-dependency-tree 1.2}}
> gives {{MNG}} as the JIRA component by inheritance.)
> {{mvn dependency:tree}} on the attached project lists {{batik-script}} by way
> of {{batik-bridge}} as expected, but then fails to show {{batik-js}} as a
> dependency of that. If you list {{batik-script}} as a direct dependency,
> {{batik-js}} is correctly shown.
> Possibly related is that Maven 2.2.1 also fails to find {{batik-js}} in
> {{MavenProject.getRuntimeArtifacts}}, so {{clean package}} fails, whereas
> this works fine under Maven 3.0. Yet just running the dependency plugin under
> M3 does not suffice to pick up this fix, wherever it was - MNG-4690?
> Although the Batik JARs are built from an odd source tree, the artifacts as
> present in the local repository look normal enough; all of the dependencies
> involved are simple compile scope without exclusions etc.
> Marking "major" since this seems to cause MNBMODULE-102 (producing build
> errors for certain projects); also I have noticed that the dependency graph
> feature in the NB IDE omits {{batik-js}}, and there may be other user-visible
> effects of this bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-443) Web doc for doxia modules omits docbook
Web doc for doxia modules omits docbook --- Key: DOXIA-443 URL: https://jira.codehaus.org/browse/DOXIA-443 Project: Maven Doxia Issue Type: Bug Components: Book Affects Versions: 1.2 Reporter: Benson Margulies http://maven.apache.org/doxia/doxia/doxia-modules/index.html doesn't seem to mention docbook. http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-docbook-simple/ points up to it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-575) Assembly does not use same dependencies as Maven 3.x itself
Assembly does not use same dependencies as Maven 3.x itself --- Key: MASSEMBLY-575 URL: https://jira.codehaus.org/browse/MASSEMBLY-575 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2.1 Environment: Maven 3.0.3 JDK 1.6.0_20 on Linux x86_64 Reporter: David Tombs Attachments: sample-project.tar.gz The dependencies used by do not match Maven 3's updated dependency resolution used in compilation, etc. Please see the attached project for an example. When you run 'mvn -X package', you can see that Maven prints the following dependency tree: [DEBUG] sample:sample-project:jar:1.0-SNAPSHOT [DEBUG]org.apache.camel:camel-core:jar:2.8.0:compile [DEBUG] org.slf4j:slf4j-api:jar:1.6.1:compile [DEBUG] org.fusesource.commonman:commons-management:jar:1.0:compile [DEBUG] com.sun:tools:jar:1.5.0:system [DEBUG]org.apache.camel:camel-spring:jar:2.8.0:compile [DEBUG] org.springframework:spring-aop:jar:3.0.5.RELEASE:compile [DEBUG] aopalliance:aopalliance:jar:1.0:compile [DEBUG] org.springframework:spring-tx:jar:3.0.5.RELEASE:compile [DEBUG]org.springframework:spring-context:jar:3.0.6.RELEASE:compile [DEBUG] org.springframework:spring-beans:jar:3.0.6.RELEASE:compile [DEBUG] org.springframework:spring-core:jar:3.0.6.RELEASE:compile [DEBUG] commons-logging:commons-logging:jar:1.1.1:compile [DEBUG] org.springframework:spring-expression:jar:3.0.6.RELEASE:compile [DEBUG] org.springframework:spring-asm:jar:3.0.6.RELEASE:compile [DEBUG]org.slf4j:slf4j-log4j12:jar:1.6.1:compile [DEBUG]log4j:log4j:jar:1.2.16:compile While the assembly plugin uses the following: [DEBUG] sample:sample-project:jar:1.0-SNAPSHOT (selected for null) [DEBUG] org.apache.camel:camel-core:jar:2.8.0:compile (selected for compile) [DEBUG] org.slf4j:slf4j-api:jar:1.6.1:compile (selected for compile) [DEBUG] org.fusesource.commonman:commons-management:jar:1.0:compile (selected for compile) [DEBUG] com.sun:tools:jar:1.5.0:system (selected for system) [DEBUG] org.apache.camel:camel-spring:jar:2.8.0:compile (selected for compile) [DEBUG] org.springframework:spring-context:jar:3.0.5.RELEASE:compile (selected for compile) [DEBUG] org.springframework:spring-aop:jar:3.0.5.RELEASE:compile (selected for compile) [DEBUG] aopalliance:aopalliance:jar:1.0:compile (selected for compile) [DEBUG] org.springframework:spring-asm:jar:3.0.5.RELEASE:compile (selected for compile) [DEBUG] org.springframework:spring-beans:jar:3.0.5.RELEASE:compile (selected for compile) [DEBUG] org.springframework:spring-core:jar:3.0.5.RELEASE:compile (selected for compile) [DEBUG] commons-logging:commons-logging:jar:1.1.1:compile (selected for compile) [DEBUG] org.springframework:spring-core:jar:3.0.5.RELEASE:compile (selected for compile) [DEBUG] commons-logging:commons-logging:jar:1.1.1:compile (selected for compile) [DEBUG] org.springframework:spring-beans:jar:3.0.5.RELEASE:compile (selected for compile) [DEBUG] org.springframework:spring-core:jar:3.0.5.RELEASE:compile (selected for compile) [DEBUG] commons-logging:commons-logging:jar:1.1.1:compile (selected for compile) [DEBUG] org.springframework:spring-expression:jar:3.0.5.RELEASE:compile (selected for compile) [DEBUG] org.springframework:spring-asm:jar:3.0.5.RELEASE:compile (selected for compile) [DEBUG] org.springframework:spring-aop:jar:3.0.5.RELEASE:compile (selected for compile) [DEBUG] aopalliance:aopalliance:jar:1.0:compile (selected for compile) [DEBUG] org.springframework:spring-tx:jar:3.0.5.RELEASE:compile (selected for compile) [DEBUG] org.springframework:spring-context:jar:3.0.6.RELEASE:compile (range restricted from: [3.0.0.RELEASE,) and: 3.0. [DEBUG] org.springframework:spring-context:jar:3.0.5.RELEASE:compile (selected for compile) [DEBUG] org.springframework:spring-aop:jar:3.0.6.RELEASE:compile (removed - nearer found: 3.0.5.RELEASE) [DEBUG] org.springframework:spring-beans:jar:3.0.6.RELEASE:compile (selected for compile) [DEBUG] org.springframework:spring-core:jar:3.0.6.RELEASE:compile (selected for compile) [DEBUG] org.springframework:spring-asm:jar:3.0.6.RELEASE:compile (selected for compile) [DEBUG] commons-logging:commons-logging:jar:1.1.1:compile (selected for compile) [DEBUG] org.springframework:spring-core:jar:3.0.6.RELEASE:compile (selected for compile) [DEBUG] org.springframework:spring-asm:jar:3.0.6.RELEASE:compile (selected for compile) [DEBUG] commons-logging:commons-logging:jar:1.1.1:compile (selected for compile) [DEBUG] org.springframework:spring-expression:jar:3.0.6.RELEASE:compile (selected for compile) [DEBUG] org.springframework:spr
[jira] Created: (DOXIA-444) Doc for doxia docbook doesn't warn user that it's not in the site plugin by default
Doc for doxia docbook doesn't warn user that it's not in the site plugin by default --- Key: DOXIA-444 URL: https://jira.codehaus.org/browse/DOXIA-444 Project: Maven Doxia Issue Type: Bug Components: Module - Docbook Simple Affects Versions: 1.2 Reporter: Benson Margulies While the doxia doc isn't specific to the maven-site-plugin, users read it to try to use the formats in maven. Thus, it makes sense to me to warn users that this isn't part of the default environment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIA-444) Doc for doxia docbook doesn't warn user that it's not in the site plugin by default
[ https://jira.codehaus.org/browse/DOXIA-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed DOXIA-444. -- Resolution: Fixed Fix Version/s: 1.3 r1170295 > Doc for doxia docbook doesn't warn user that it's not in the site plugin by > default > --- > > Key: DOXIA-444 > URL: https://jira.codehaus.org/browse/DOXIA-444 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Docbook Simple >Affects Versions: 1.2 >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 1.3 > > > While the doxia doc isn't specific to the maven-site-plugin, users read it to > try to use the formats in maven. Thus, it makes sense to me to warn users > that this isn't part of the default environment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIA-443) Web doc for doxia modules omits docbook
[ https://jira.codehaus.org/browse/DOXIA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed DOXIA-443. -- Resolution: Not A Bug Apparently I can't read. > Web doc for doxia modules omits docbook > --- > > Key: DOXIA-443 > URL: https://jira.codehaus.org/browse/DOXIA-443 > Project: Maven Doxia > Issue Type: Bug > Components: Book >Affects Versions: 1.2 >Reporter: Benson Margulies >Assignee: Benson Margulies > > http://maven.apache.org/doxia/doxia/doxia-modules/index.html doesn't seem to > mention docbook. > http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-docbook-simple/ > points up to it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-5173) Include other XML files from POM
Include other XML files from POM Key: MNG-5173 URL: https://jira.codehaus.org/browse/MNG-5173 Project: Maven 2 & 3 Issue Type: Wish Components: General Affects Versions: 3.0.3 Environment: All Environments Reporter: Ravi K Users should have the ability to include XML files in pom files. Ex: If I have execution blocks in a seperate xml file ex: . In the main pom file I just want to include the xml file in the same folder.. This will reduce the size of the pom file and also automation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MDEP-295) Add ability to strip classifier
[ https://jira.codehaus.org/browse/MDEP-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ee updated MDEP-295: Attachment: good.patch Ups, this is the good patch. Please ignore the previous one. > Add ability to strip classifier > --- > > Key: MDEP-295 > URL: https://jira.codehaus.org/browse/MDEP-295 > Project: Maven 2.x Dependency Plugin > Issue Type: Improvement >Reporter: Jason Smith >Assignee: Brian Fox > Attachments: > 0002-stripClassifier-option-added-to-the-copy-dependency-.patch, good.patch > > > In addition to the ability to specify that the version be stripped from the > artifact it would be helpful to be able to specify that the classifier be > stripped also. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-576) addClasspath broken in new single goal
addClasspath broken in new single goal
--
Key: MASSEMBLY-576
URL: https://jira.codehaus.org/browse/MASSEMBLY-576
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2.1
Environment: Maven 3.0.3
Ubuntu 11.04
Sun java 6 (1.6.0_26)
Reporter: James Davis
Priority: Blocker
According to the documentation, using true in
archive/manifest, should place the generated classpath in to the manifest.
This works with assembly:assembly (now deprecated), but is broken in
assembly:single
Here is my plugin definition section:
org.apache.maven.plugins
maven-assembly-plugin
src/main/assembly/assembly.xml
com.example.Main
true
lib/
package
single
and the custom assembly file:
full
jar
false
false
runtime
true
lib/
${project.build.outputDirectory}
/
I'm not sure if this is just because the documentation does not correctly
address how to do this or if it is actually just broken. I did check the docs
and this is how the docs claim you should be able to do this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-707) release plugin does not use neither ${project.scm.connection} nor ${project.scm.developerConnection}
[
https://jira.codehaus.org/browse/MRELEASE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=278885#comment-278885
]
Timothy Soehnlin commented on MRELEASE-707:
---
I am currently running into this issue as well. I really want to centralize
the SCM access to our CI environment, and not have the developers accidentally
committing/updating from the maven command line.
> release plugin does not use neither ${project.scm.connection} nor
> ${project.scm.developerConnection}
>
>
> Key: MRELEASE-707
> URL: https://jira.codehaus.org/browse/MRELEASE-707
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
>Affects Versions: 2.2.1
> Environment: ArchLinux
> Maven 3.0.3
> Mercurial 1.9.1
>Reporter: Alexander Betaev
>
> Use case: I don't want to include section in all my POM's since I want
> to perform releases only using CI software. It seems for me to be more useful
> configuration for distributed SCM's than using release plugins locally.
> So I am providing '-Dproject.scm.connection=scm:hg:file://${basedir}/../' and
> '-Dproject.scm.developerConnection=scm:hg:file://${basedir}/../' to Maven's
> JVM. But it does not affect anything in maven-release-plugin. Also I did not
> find any property which I should use instead of project.scm.connection.
> The error message I receive looks like I forgot to configure maven-scm-plugin:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.2.1:prepare (default-cli) on
> project parent: Missing required setting: scm connection or
> developerConnection must be specified. -> [Help 1]
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5173) Include other XML files from POM
[ https://jira.codehaus.org/browse/MNG-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-5173. - Resolution: Won't Fix Assignee: Brett Porter including arbitrary files would break the POM when it is deployed into the remote repository. What you might be looking for is MNG-5102 > Include other XML files from POM > > > Key: MNG-5173 > URL: https://jira.codehaus.org/browse/MNG-5173 > Project: Maven 2 & 3 > Issue Type: Wish > Components: General >Affects Versions: 3.0.3 > Environment: All Environments >Reporter: Ravi K >Assignee: Brett Porter > > Users should have the ability to include XML files in pom files. Ex: If I > have execution blocks in a seperate xml file ex: > . > In the main pom file I just want to include the xml file in the same folder.. > This will reduce the size of the pom file and also automation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
