[jira] Commented: (MCOMPILER-65) Intelligent fork or bootclasspath based on desired target JDK
[ http://jira.codehaus.org/browse/MCOMPILER-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133396#action_133396 ] Benjamin Bentmann commented on MCOMPILER-65: bq. Does this replace the compiler plugin somehow? No, the toolchains will only help the Compiler Plugin to locate a JDK (javac, boot class path). For more information/questions, please use the comments thread of the wiki article, where Milos Klient, the author of the proposal, can hopefully shed some more light on your concerns. > Intelligent fork or bootclasspath based on desired target JDK > - > > Key: MCOMPILER-65 > URL: http://jira.codehaus.org/browse/MCOMPILER-65 > Project: Maven 2.x Compiler Plugin > Issue Type: Improvement >Reporter: David Smiley > > I work with Maven on a few projects, some jdk 1.4, some jdk 1.5. The only > way to get a consistent compiled build is to fork the compiler so that a > particular jdk is used, it's not necessarily enough to set the "source" and > "target" params on the compiler plugin ( see > http://madbean.com/2006/target14/ ) for an explanation. I say not > necessarily in part not just on the info in that referred URL, but we really > can't and shouldn't assume that maven itself is using a particular jdk > either. I think this is a big deal and I would guess that the maven team > would also think it's a big deal based on a cornerstone philosophy of > repeatable builds. -- Builds that shouldn't come with special instructions > to do some magic (like run maven in a certain VM or set certain system > properties). > This issue needs to be more prominently displayed in the maven documentation, > both for the plugin and most certainly this FAQ entry: > http://maven.apache.org/general.html#Compiling-J2SE-5 -- if only it were > that simple. > I have an idea for a solution that involves only forking when necessary and > if not that possibly setting the bootclasspath. The idea is to avoid > forking, and to avoid setting bootclasspath if neither are necessary. And of > course the result is a compiler configuration that can and should be as > simple as setting the "target" param to get a repeatable build no matter what > JDK maven is running under. > 1. Standardize on the system property names for the java homes, i.e. > JAVA_1_4_HOME JAVA_1_5_HOME etc. Furthermore... this *should* be set in the > user's settings.xml. Yes this means installation requires another step but I > see no way around that unless maven were to try and figure out these based on > operating-specific logic. > 2. Based on the "source" and "target" parameters, determine wether (a) > Maven's current VM can be used as-is without setting bootclasspath for javac > (b) Maven's current VM can be used but needs to set the bootclasspath for > javac, or (c) fork and use an external javac. If (a) can be chosen then the > standardized property names don't need to be consulted. In (b) the java home > is needed for the bootclasspath, and in (c) to fork javac. Also, ensure that > the choice of a,b,c is somehow displayed in the maven output so the developer > knows. > Implementation note: I noticed that the maven compiler plugin uses Ant > heavily to do its job. In light of that, implementing this feature might > instead involve enhancing the ant side to have this feature and then making > minor changes on the maven side to accommodate them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MINVOKER-34) Warn about usage of platform encoding
[ http://jira.codehaus.org/browse/MINVOKER-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MINVOKER-34. - Assignee: Benjamin Bentmann Resolution: Fixed Done in [r653019|http://svn.apache.org/viewvc?view=rev&revision=653019]. > Warn about usage of platform encoding > - > > Key: MINVOKER-34 > URL: http://jira.codehaus.org/browse/MINVOKER-34 > Project: Maven 2.x Invoker Plugin > Issue Type: Improvement >Affects Versions: 1.1 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 1.2 > > > Relying on the platform encoding makes a build platform-dependent and > threatens build reproducibility. Users should be warned about this danger. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MINVOKER-30) Allow to configure file encoding for verifications scripts
[
http://jira.codehaus.org/browse/MINVOKER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MINVOKER-30.
-
Resolution: Fixed
Done in [r653017|http://svn.apache.org/viewvc?view=rev&revision=653017].
> Allow to configure file encoding for verifications scripts
> --
>
> Key: MINVOKER-30
> URL: http://jira.codehaus.org/browse/MINVOKER-30
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
>Affects Versions: 1.1
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
> Fix For: 1.2
>
> Attachments: file-encoding.patch
>
>
> Right now, the {{verify.bsh}} is read using the platform's default encoding,
> making the tests platform-dependent. We should enrich the plugin
> configuration to allow the user to lock down the encoding and ensure
> reproducible tests.
> The same applies to the {{goals.txt}} and {{profiles.txt}}.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MINVOKER-35) Make run mojo bind to phase integration-test by default
Make run mojo bind to phase integration-test by default --- Key: MINVOKER-35 URL: http://jira.codehaus.org/browse/MINVOKER-35 Project: Maven 2.x Invoker Plugin Issue Type: Improvement Affects Versions: 1.1 Reporter: Benjamin Bentmann Priority: Minor Most POMs I have seen to far run the Invoker during the phase "integration-test", hence making this the default phase binding will reduce XML clutter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MINVOKER-35) Make run mojo bind to phase integration-test by default
[ http://jira.codehaus.org/browse/MINVOKER-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MINVOKER-35. - Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 1.2 Done in [r653037|http://svn.apache.org/viewvc?view=rev&revision=653037]. > Make run mojo bind to phase integration-test by default > --- > > Key: MINVOKER-35 > URL: http://jira.codehaus.org/browse/MINVOKER-35 > Project: Maven 2.x Invoker Plugin > Issue Type: Improvement >Affects Versions: 1.1 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 1.2 > > > Most POMs I have seen to far run the Invoker during the phase > "integration-test", hence making this the default phase binding will reduce > XML clutter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MARTIFACT-16) DefaultArtifactVersion.hashCode() violates general contract
DefaultArtifactVersion.hashCode() violates general contract
---
Key: MARTIFACT-16
URL: http://jira.codehaus.org/browse/MARTIFACT-16
Project: Maven Artifact
Issue Type: Bug
Affects Versions: 3.0-alpha-1
Reporter: Benjamin Bentmann
Attachments: default-artifact-version-hashcode.patch
Compare
[{{Object.hashCode()}}|http://java.sun.com/javase/6/docs/api/java/lang/Object.html#hashCode()]
and [Effective Java, Chapter 3, "Methods Common to All
Objects"|http://java.sun.com/docs/books/effective/chapters.html].
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCOMPILER-63) Provide specific default value for "encoding" parameter
[ http://jira.codehaus.org/browse/MCOMPILER-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MCOMPILER-63. -- Resolution: Won't Fix Fix Version/s: (was: 2.1) Reverted in [r653054|http://svn.apache.org/viewvc?view=rev&revision=653054]. > Provide specific default value for "encoding" parameter > --- > > Key: MCOMPILER-63 > URL: http://jira.codehaus.org/browse/MCOMPILER-63 > Project: Maven 2.x Compiler Plugin > Issue Type: Improvement >Affects Versions: 2.0.2 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Attachments: source-encoding.patch > > > As stated in the [javac > doc|http://java.sun.com/javase/6/docs/technotes/tools/windows/javac.html#standard], > the parameter "encoding" defaults to the platform's default encoding if not > specified. This might be a convenient feature when running javac directly > from the console prompt (less typing) but I consider this harmful for an > automated build. The platform's default encoding might easily differ between > machines/developers, causing unreliable build output. > Maven has "reproducible builds" on its banner and as such, locking down all > plugin versions has recently become a best practice. Likewise, the encoding > used to process source files should be locked down. As Maven furthermore > prefers convention over configuration, such a lockdown should be provided > out-of-the-box. > The attached patch adds a default value for the encoding that locks the > encoding down to "ISO-8859-1" if not explicitly overriden by the user in the > POM. I chose Latin-1 for consistency with the behavior of the Maven Site > Plugin although I personally would have preferred UTF-8. > Releasing the patch might break existing builds where users have relied on > their platform's default encoding for handling Non-ASCII sources. The group > of those people is hopefully small and their build can be easily fixed by > updating the POM. > Not emulatable would be the possibility to explicitly use the platform's > default encoding as now but I do not think that there is really somebody out > there playing russian roulette with the build output... Besides, now one > requested such a risky thing for the Maven Site Plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCOMPILER-73) Warn about usage of platform encoding
[ http://jira.codehaus.org/browse/MCOMPILER-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MCOMPILER-73. -- Assignee: Benjamin Bentmann Resolution: Fixed Done in [r653061|http://svn.apache.org/viewvc?view=rev&revision=653061]. > Warn about usage of platform encoding > - > > Key: MCOMPILER-73 > URL: http://jira.codehaus.org/browse/MCOMPILER-73 > Project: Maven 2.x Compiler Plugin > Issue Type: Improvement >Affects Versions: 2.0.2 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 2.1 > > > Relying on the platform encoding makes a build platform-dependent and > threatens build reproducibility. Users should be warned about this danger. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3562) Need documentation of command-line flags
Need documentation of command-line flags Key: MNG-3562 URL: http://jira.codehaus.org/browse/MNG-3562 Project: Maven 2 Issue Type: Bug Components: Documentation: General Reporter: SebbASF The Maven2 documentation does not seem to contain any description of the command-line flags. Perhaps the Maven 1 example could be adapted: http://maven.apache.org/maven-1.x/reference/command-line.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPMD-76) use ${project.build.sourceEncoding} as default value for "sourceEncoding" parameter
[
http://jira.codehaus.org/browse/MPMD-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MPMD-76.
-
Resolution: Fixed
Done in [r653065|http://svn.apache.org/viewvc?view=rev&revision=653065].
> use ${project.build.sourceEncoding} as default value for "sourceEncoding"
> parameter
> ---
>
> Key: MPMD-76
> URL: http://jira.codehaus.org/browse/MPMD-76
> Project: Maven 2.x PMD Plugin
> Issue Type: Improvement
> Components: CPD, PMD
>Affects Versions: 2.3
>Reporter: Herve Boutemy
>Assignee: Benjamin Bentmann
> Fix For: 2.4
>
>
> see
> http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPMD-79) Warn about usage of platform encoding
[ http://jira.codehaus.org/browse/MPMD-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MPMD-79. - Assignee: Benjamin Bentmann Resolution: Fixed Done in [r653071|http://svn.apache.org/viewvc?view=rev&revision=653071]. > Warn about usage of platform encoding > - > > Key: MPMD-79 > URL: http://jira.codehaus.org/browse/MPMD-79 > Project: Maven 2.x PMD Plugin > Issue Type: Improvement > Components: CPD, PMD >Affects Versions: 2.3 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 2.4 > > > Relying on the platform encoding makes a build platform-dependent and > threatens build reproducibility. Users should be warned about this danger. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPMD-64) verbose output not useful for inner classes
[ http://jira.codehaus.org/browse/MPMD-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MPMD-64: -- Fix Version/s: 2.4 > verbose output not useful for inner classes > --- > > Key: MPMD-64 > URL: http://jira.codehaus.org/browse/MPMD-64 > Project: Maven 2.x PMD Plugin > Issue Type: Improvement > Components: PMD >Affects Versions: 2.2 >Reporter: Sean Bridges >Priority: Minor > Fix For: 2.4 > > Attachments: version_update.txt > > > With verbose output on, a pmd error in an inner class will produce output > like, > [INFO] PMD Failure: foo.bar.Anonymous$1:182 > Rule:SignatureDeclareThrowsException Priority:3 A method/constructor > shouldn't explicitly throw java.lang.Exception. > Rather than printing the class name, it would be more useful to print out the > file name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRESOURCES-57) use ${project.build.sourceEncoding} as default value for "encoding" parameter
[
http://jira.codehaus.org/browse/MRESOURCES-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MRESOURCES-57:
Summary: use ${project.build.sourceEncoding} as default value for
"encoding" parameter (was: Provide specific default value for "encoding"
parameter)
> use ${project.build.sourceEncoding} as default value for "encoding" parameter
> -
>
> Key: MRESOURCES-57
> URL: http://jira.codehaus.org/browse/MRESOURCES-57
> Project: Maven 2.x Resources Plugin
> Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Benjamin Bentmann
>Assignee: Herve Boutemy
>Priority: Minor
> Fix For: 2.3
>
> Attachments: resource-encoding.patch
>
>
> The platform's default encoding may easily differ among machines/developers
> so relying on it breaks with the aim of reproducible builds. The encoding
> used should always be fixed for a particular plugin run, either explicitly by
> the user or implicitly by a known default value.
> See also MCOMPILER-63.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRESOURCES-57) use ${project.build.sourceEncoding} as default value for "encoding" parameter
[
http://jira.codehaus.org/browse/MRESOURCES-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MRESOURCES-57.
---
Resolution: Fixed
Done in [r653078|http://svn.apache.org/viewvc?view=rev&revision=653078].
> use ${project.build.sourceEncoding} as default value for "encoding" parameter
> -
>
> Key: MRESOURCES-57
> URL: http://jira.codehaus.org/browse/MRESOURCES-57
> Project: Maven 2.x Resources Plugin
> Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Benjamin Bentmann
>Assignee: Herve Boutemy
>Priority: Minor
> Fix For: 2.3
>
> Attachments: resource-encoding.patch
>
>
> The platform's default encoding may easily differ among machines/developers
> so relying on it breaks with the aim of reproducible builds. The encoding
> used should always be fixed for a particular plugin run, either explicitly by
> the user or implicitly by a known default value.
> See also MCOMPILER-63.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRESOURCES-39) Filtering fails for command line properties
[
http://jira.codehaus.org/browse/MRESOURCES-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133409#action_133409
]
Benjamin Bentmann commented on MRESOURCES-39:
-
We should have Milos or somebody with similiar skills in embedded development
review this issue. I doubt that directly using the system properties is the
correct approach. IIRC, there were execution properties from {{MavenSession}}
that should be used instead.
> Filtering fails for command line properties
> ---
>
> Key: MRESOURCES-39
> URL: http://jira.codehaus.org/browse/MRESOURCES-39
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Environment: maven-2.0.4 and maven-2.0.5
> Mac OS X
>Reporter: Matt Brozowski
>Priority: Critical
> Fix For: 2.3
>
> Attachments: filtering-bug.tar,
> maven-resources-plugin-prop-filtering-r630241.patch
>
>
> When passing a property on the command line to maven using -D it does not
> properly override values passed to filters.
> I have attached a sample project that defines a property in the pom.xml
> called 'filtered' This property is used as a filter in the
> filtered.properties file in src/main/filtered/filtered.properties. I have
> also included a test that gets passed the filtered property as a System
> property via the surefire plugin. It then loaded the filtered.properties
> file and tests to ensure the filters match.
> The tests pass when run as
> mvn test
> BUT if I run as
> mvn -Dfiltered=from-cmd-line teset
> They fail.
> I have also included the antrun plugin print its perspective on the value of
> the property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3563) Content of a property ending with .url gets overwritten with the content of from the pom.xml
Content of a property ending with .url gets overwritten with the content of
from the pom.xml
Key: MNG-3563
URL: http://jira.codehaus.org/browse/MNG-3563
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
Environment: Linux
Reporter: Stephan Kleine
If one creates a property e.g. named jdbc.url in a parent pom.xml and then
refers to that property via ${jdbc.url} in a resource file of a subproject
whose pom.xml is derived from the one that declares the jdbc.url property the
content is overwritten with the content of the tag during the filtering
step.
E.g.
com.example.project contains:
jdbc:mysql://localhost:3306/TestDB
in its pom.xml
com.example.subproject is derived from com.example.project and contains
url="${jdbc.url}
in some db setup file and
http://maven.apache.org
in its pom.xml
The resulting content, after the filtering step, will be
"url="http://maven.apache.org""; instead of
"url="jdbc:mysql://localhost:3306/TestDB"".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MIDEA-102) Module filepath is generated incorrectly for sibling parent
[ http://jira.codehaus.org/browse/MIDEA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133423#action_133423 ] gotama commented on MIDEA-102: -- Dennis, Have you made any headway on this? I'm sure a lot of people would appreciate this fix and a working 2.2 IDEA Maven2 plugin. How can we help? When you say the tests fail, are those checked in 2.2 junit tests? We should be able to do something like create a test project and a junit test, check them in, and then test it in all environments (XP/Cygwin, XP, Linux, OSX) until it passes. Is this already checked in? If it is, then contributors could try to fix it and we'd all agree on exactly what has to pass. Can we try to outline this? Thanks, Blaine > Module filepath is generated incorrectly for sibling parent > --- > > Key: MIDEA-102 > URL: http://jira.codehaus.org/browse/MIDEA-102 > Project: Maven 2.x IDEA Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: $ mvn -v > Maven version: 2.0.7 > Java version: 1.5.0_11 > OS name: "windows xp" version: "5.1" arch: "x86" > cygwin >Reporter: Joern Huxhorn >Assignee: Dennis Lundberg > Fix For: 2.2 > > Attachments: maven-idea-plugin-MIDEA-102.patch > > > I have a multi-module mvn project. > When I do an mvn idea:clean idea:idea, the following ProjectModuleManager > snippet in the top level .ipr is generated: > > > > >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/domain/gateway-domain.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/instruction-store/gateway-instruction-store.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/parser/gateway-parser.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/psrgeneration/gateway-psr-generation.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/output/gateway-output.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/destination-resolver/gateway-destination-resolver.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/choreography/gateway-choreography.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/presentation/gateway-presentation.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/assembly/gateway-assembly.iml"/> > > > The $PROJECT_DIR in this case is C:/dev/voca/gateway/. > But this path is being appended in a hard-coded fashion after the > $PROJECT_DIR entry. > The symptom in Intellij is the following error message: > Cannot load module: File > C:\dev\voca\gateway\C:\dev\voca\gateway\domain\gateway-domain.iml does not > exist > Would you like to remove the module from the project? > The workaround is to delete the extra appended file path from each module > entry in the above mentioned snippet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
