[jira] Created: (MRESOURCES-91) File last modified property is changed when copied as resource
File last modified property is changed when copied as resource -- Key: MRESOURCES-91 URL: http://jira.codehaus.org/browse/MRESOURCES-91 Project: Maven 2.x Resources Plugin Issue Type: Bug Affects Versions: 2.3 Environment: Ubuntu 9.04 x64 Sun JDK 1.6.0_12 Maven 2.1.0 Reporter: Noam Y. Tenne This occurs when no filter is being used. When a resource is copied to the target directory, the file's last modified property is changed to the time of copy. -- 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: (MINVOKER-87) Invoker install goal fails when used in eclipse
[
http://jira.codehaus.org/browse/MINVOKER-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177838#action_177838
]
Benjamin Bentmann commented on MINVOKER-87:
---
bq. Artifact is not fully assembled:
/Users/Lee/Documents/workspace/c-builds/cbuild-utils/target/classes
Well, what's the plugin supposed to install if there is no artifact? We could
output a warning and skip the artifact, leaving the risk of the sub builds
failing due to missing artifacts in the local repo, but apart from this I don't
see much choice.
> Invoker install goal fails when used in eclipse
> ---
>
> Key: MINVOKER-87
> URL: http://jira.codehaus.org/browse/MINVOKER-87
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.3
>Reporter: Lee Thompson
>
> Using maven-invoker-plugin works great on the command line.
> When used with eclipse, the install goal will fail to install a previous
> module's jar file into "localRepositoryPath". A workaround is to use
> maven-install-plugin instead.
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-invoker-plugin:1.3:install' -->
> [DEBUG] (f) localRepository =
> Repository[local|file:///Users/Lee/.m2/repository]
> [DEBUG] (f) localRepositoryPath =
> /Users/Lee/Documents/workspace/c-builds/plugins/patch-maven-plugin/target/it-repo
> [DEBUG] (f) project = MavenProject:
> org.codehaus.mojo:patch-maven-plugin:1.0-beta-1-SNAPSHOT @
> /Users/Lee/Documents/workspace/c-builds/plugins/patch-maven-plugin/pom.xml
> [DEBUG] (f) reactorProjects = [MavenProject:
> org.codehaus.mojo:cbuild-parent:1.0-beta-1-SNAPSHOT @
> /Users/Lee/Documents/workspace/c-builds/pom.xml, MavenProject:
> org.codehaus.mojo:cbuild-tool-parent:1.0-beta-1-SNAPSHOT @
> /Users/Lee/Documents/workspace/c-builds/downloader/pom.xml, MavenProject:
> org.codehaus.mojo:cbuild-utils:1.0-beta-1-SNAPSHOT @
> /Users/Lee/Documents/workspace/c-builds/cbuild-utils/pom.xml, MavenProject:
> org.codehaus.mojo:cbuild-plugin-parent:1.0-beta-1-SNAPSHOT @
> /Users/Lee/Documents/workspace/c-builds/plugins/pom.xml, MavenProject:
> org.codehaus.mojo:cbuild-lifecycles:1.0-beta-1-SNAPSHOT @
> /Users/Lee/Documents/workspace/c-builds/plugins/cbuild-lifecycles/pom.xml,
> MavenProject: org.codehaus.mojo:rpm-cbuild-maven-plugin:1.0-beta-1-SNAPSHOT @
> /Users/Lee/Documents/workspace/c-builds/plugins/rpm-cbuild-maven-plugin/pom.xml,
> MavenProject: org.codehaus.mojo:patch-maven-plugin:1.0-beta-1-SNAPSHOT @
> /Users/Lee/Documents/workspace/c-builds/plugins/patch-maven-plugin/pom.xml,
> MavenProject: org.codehaus.mojo:make-maven-plugin:1.0-beta-1-SNAPSHOT @
> /Users/Lee/Documents/workspace/c-builds/plugins/make-maven-plugin/pom.xml,
> MavenProject: org.codehaus.mojo:shell-maven-plugin:1.0-beta-1-SNAPSHOT @
> /Users/Lee/Documents/workspace/c-builds/plugins/shell-maven-plugin/pom.xml,
> MavenProject:
> org.codehaus.mojo:build-on-demand-maven-plugin:1.0-beta-1-SNAPSHOT @
> /Users/Lee/Documents/workspace/c-builds/plugins/build-on-demand-maven-plugin/pom.xml]
> [DEBUG] -- end configuration --
> [INFO] [invoker:install {execution: integration-test}]
> [DEBUG] On Install: Using artifact file for POM:
> org.codehaus.mojo:patch-maven-plugin:pom:1.0-beta-1-SNAPSHOT
> [DEBUG] WARNING: Artifact:
> org.codehaus.mojo:patch-maven-plugin:pom:1.0-beta-1-SNAPSHOT does not have
> project-builder metadata (ProjectBuilderConfiguration) associated with it.
> Cannot access CLI properties for version transformation.
> [INFO] Installing
> /Users/Lee/Documents/workspace/c-builds/plugins/patch-maven-plugin/target/pom-transformed.xml
> to
> /Users/Lee/Documents/workspace/c-builds/plugins/patch-maven-plugin/target/it-repo/org/codehaus/mojo/patch-maven-plugin/1.0-beta-1-SNAPSHOT/patch-maven-plugin-1.0-beta-1-SNAPSHOT.pom
> [INFO] Installing
> /Users/Lee/Documents/workspace/c-builds/plugins/patch-maven-plugin/target/patch-maven-plugin-1.0-beta-1-SNAPSHOT.jar
> to
> /Users/Lee/Documents/workspace/c-builds/plugins/patch-maven-plugin/target/it-repo/org/codehaus/mojo/patch-maven-plugin/1.0-beta-1-SNAPSHOT/patch-maven-plugin-1.0-beta-1-SNAPSHOT.jar
> [DEBUG] On Install: Using artifact file for POM:
> org.codehaus.mojo:cbuild-plugin-parent:pom:1.0-beta-1-SNAPSHOT
> [INFO] Installing
> /Users/Lee/Documents/workspace/c-builds/plugins/target/pom-transformed.xml to
> /Users/Lee/Documents/workspace/c-builds/plugins/patch-maven-plugin/target/it-repo/org/codehaus/mojo/cbuild-plugin-parent/1.0-beta-1-SNAPSHOT/cbuild-plugin-parent-1.0-beta-1-SNAPSHOT.pom
> [DEBUG] On Install: Using artifact file for POM:
> org.codehaus.mojo:cbuild-parent:pom:1.0-beta-1-SNAPSHOT
> [INFO] Installing
> /Users/Lee/Documents/workspace/c-builds/target/pom-transformed.xml to
> /Users/Lee/Documents/workspace/c-builds/plugins/patch-maven-plugin/target/it-repo/
[jira] Created: (WAGON-266) Wagon ftp error using Mac OS
Wagon ftp error using Mac OS Key: WAGON-266 URL: http://jira.codehaus.org/browse/WAGON-266 Project: Maven Wagon Issue Type: Bug Components: wagon-ftp Environment: Mac OS Reporter: Daniel Maier Hi, I tried to upload my site using wagon-ftp. With windows it works without problems. But if I use Mac OS, I get the following Error Message: [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection()V [INFO] [INFO] Trace java.lang.AbstractMethodError: org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection()V at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106) at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:184) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 10 seconds [INFO] Finished at: Tue May 19 11:09:12 CEST 2009 [INFO] Final Memory: 32M/63M Any hints what causes this error? Thanks Daniel Maier -- 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: (MPIR-157) Artifact ###### has no file error.
[ http://jira.codehaus.org/browse/MPIR-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177853#action_177853 ] Herve Boutemy commented on MPIR-157: can you provide a pom.xml that produces the reported error? I can't reproduce, neither with Maven 2.0.10 or Maven 2.1.0 > Artifact ## has no file error. > -- > > Key: MPIR-157 > URL: http://jira.codehaus.org/browse/MPIR-157 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 2.1.1 > Environment: maven 2.1.0 >Reporter: Stevo Slavic > Attachments: > maven-project-info-reports-downloading-transitive-deps.zip, > maven_log_snippet.txt > > > Issue initially created on maven site plugin JIRA ( MSITE-397 ) so please > see description of the issue there. > I'm attaching additional maven debug log output snippet which will hopefully > shed more light to the issue. > Will have to investigate if this happens only for modules with pom packaging. > What I did notice via attached example trivial project, in 2.1.1 info reports > plugin for dependencies report for every build plugin downloads transitive > dependencies - in 2.1 this at least is not logged if it is being done at all. -- 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: (MPIR-157) Artifact ###### has no file error.
[ http://jira.codehaus.org/browse/MPIR-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPIR-157. -- Resolution: Duplicate please continue on MPIR-158 (= the old MSITE-397 renamed in MPIR instead of MSITE) > Artifact ## has no file error. > -- > > Key: MPIR-157 > URL: http://jira.codehaus.org/browse/MPIR-157 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 2.1.1 > Environment: maven 2.1.0 >Reporter: Stevo Slavic > Attachments: > maven-project-info-reports-downloading-transitive-deps.zip, > maven_log_snippet.txt > > > Issue initially created on maven site plugin JIRA ( MSITE-397 ) so please > see description of the issue there. > I'm attaching additional maven debug log output snippet which will hopefully > shed more light to the issue. > Will have to investigate if this happens only for modules with pom packaging. > What I did notice via attached example trivial project, in 2.1.1 info reports > plugin for dependencies report for every build plugin downloads transitive > dependencies - in 2.1 this at least is not logged if it is being done at all. -- 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: (MPIR-158) Artifact ###### has no file error.
[ http://jira.codehaus.org/browse/MPIR-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPIR-158: --- Component/s: dependencies > Artifact ## has no file error. > -- > > Key: MPIR-158 > URL: http://jira.codehaus.org/browse/MPIR-158 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 2.1.1 > Environment: Windows xp, tomcat 5.5 server >Reporter: Damian Sinczak >Priority: Minor > > During 'mvn site' command on project i receive some strange errors. Their are > no critical, but they are still errors. > Console dump: > [ERROR] Artifact: org.apache.abdera:abdera-core:jar:0.4.0-incubating has no > file > . > [ERROR] Artifact: > org.apache.abdera:abdera-extensions-json:jar:0.4.0-incubating > has no file. > [ERROR] Artifact: > org.apache.abdera:abdera-extensions-main:jar:0.4.0-incubating > has no file. > [ERROR] Artifact: org.apache.abdera:abdera-i18n:jar:0.4.0-incubating has no > file > . > [ERROR] Artifact: org.apache.abdera:abdera-parser:jar:0.4.0-incubating has no > fi > le. > [ERROR] Artifact: org.apache.cxf:cxf-api:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-common-schemas:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-common-utilities:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-bindings-soap:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-bindings-xml:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-core:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-frontend-simple:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-ws-addr:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-tools-common:jar:2.2 has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0 > .2 has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-annotation_1.0_spec:jar:1.1 > .1 has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.5 h > as no file. > [ERROR] Artifact: org.apache.geronimo.specs:geronimo-jaxws_2.1_spec:jar:1.0 > has > no file. > [ERROR] Artifact: org.apache.geronimo.specs:geronimo-servlet_2.5_spec:jar:1.2 > ha > s no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1 > has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-ws-metadata_2.0_spec:jar:1. > 1.2 has no file. > [ERROR] Artifact: org.apache.neethi:neethi:jar:2.0.4 has no file. > [ERROR] Artifact: org.apache.ws.commons.axiom:axiom-api:jar:1.2.7 has no file. > [ERROR] Artifact: org.apache.ws.commons.axiom:axiom-impl:jar:1.2.7 has no > file. > [ERROR] Artifact: org.apache.ws.commons.schema:XmlSchema:jar:1.4.4 has no > file. > [ERROR] Artifact: org.apache.xmlbeans:xmlbeans:jar:2.3.0 has no file. > [ERROR] Artifact: org.codehaus.jettison:jettison:jar:1.0.1 has no file. > [ERROR] Artifact: org.codehaus.woodstox:wstx-asl:jar:3.2.6 has no file. > [ERROR] Artifact: org.hibernate:ejb3-persistence:jar:1.0.1.GA has no file. > [ERROR] Artifact: org.hibernate:hibernate-commons-annotations:jar:3.0.0.ga > has n > o file. > [ERROR] Artifact: org.mortbay.jetty:jetty:jar:6.1.15 has no file. > [ERROR] Artifact: org.mortbay.jetty:jetty-util:jar:6.1.15 has no file. > [ERROR] Artifact: org.slf4j:slf4j-api:jar:1.3.1 has no file. > [ERROR] Artifact: org.slf4j:slf4j-jdk14:jar:1.3.1 has no file. > [ERROR] Artifact: org.springframework:spring-beans:jar:2.5.5 has no file. > [ERROR] Artifact: org.springframework:spring-context:jar:2.5.5 has no file. > [ERROR] Artifact: org.springframework:spring-core:jar:2.5.5 has no file. > [ERROR] Artifact: org.springframework:spring-web:jar:2.5.5 has no file. > [ERROR] Artifact: wsdl4j:wsdl4j:jar:1.6.2 has no file. > [ERROR] Artifact: xalan:xalan:jar:2.6.0 has no file. > [ERROR] Artifact: xerces:xercesImpl:jar:2.6.2 has no file. > [ERROR] Artifact: xerces:xmlParserAPIs:jar:2.6.2 has no file. > [ERROR] Artifact: xml-apis:xml-apis:jar:1.3.02 has no file. > [ERROR] Artifact: xml-resolver:xml-resolver:jar:1.2 has no file. > [ERROR] Artifact: xom:xom:jar:1.0 has no file. > [INFO] Generating "Project Team" report. > [INFO] Generating "Project License" report. > [INFO] Generating "Project Plugins" report. > [INFO] Generating "Maven Surefire Report" report. > [INFO] Generating "FindBugs Report" report. > [INFO] Using source root: > [INFO] C:\edys_workspace\edystok\target\classes > [INFO] Using test source root: > [INFO] C:\edys_workspace\edystok\target\test-classes > [INFO] No effort provided, using default effort. > [INFO] Adding Source Directory: C:\edys_workspace\edystok\src\main\java > [INFO] No threshold provided, us
[jira] Created: (MNG-4172) Project POM artifact returned as dependency if project has no dependencies
Project POM artifact returned as dependency if project has no dependencies
--
Key: MNG-4172
URL: http://jira.codehaus.org/browse/MNG-4172
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 3.0-alpha-3
Reporter: Benjamin Bentmann
Priority: Minor
For a POM that declares no dependencies at all, the {{MavenProject}}
erroneously reports its corresponding POM artifact as a dependency.
--
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: (MNG-4172) Project POM artifact returned as dependency if project has no dependencies
[
http://jira.codehaus.org/browse/MNG-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4172.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 3.0-alpha-3
Fixed in [r778240|http://svn.eu.apache.org/viewvc?view=rev&revision=778240].
> Project POM artifact returned as dependency if project has no dependencies
> --
>
> Key: MNG-4172
> URL: http://jira.codehaus.org/browse/MNG-4172
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0-alpha-3
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 3.0-alpha-3
>
>
> For a POM that declares no dependencies at all, the {{MavenProject}}
> erroneously reports its corresponding POM artifact as a dependency.
--
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-4173) Remove automatic version resolution for POM plugins
Remove automatic version resolution for POM plugins --- Key: MNG-4173 URL: http://jira.codehaus.org/browse/MNG-4173 Project: Maven 2 Issue Type: Task Components: Plugins and Lifecycle Affects Versions: 3.0-alpha-3 Reporter: Benjamin Bentmann Maven 3.x will no longer try to automatically find the version for plugins specified in the POM, i.e. the effective POM must declare a version for each plugin used for the sake of reproducible builds. Omitting the plugin version will raise in error. -- 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: (MNG-4173) Remove automatic version resolution for POM plugins
[ http://jira.codehaus.org/browse/MNG-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4173. -- Assignee: Jason van Zyl Resolution: Fixed Fix Version/s: 3.0-alpha-3 Done in [r774327|http://svn.apache.org/viewvc?view=rev&revision=774327]. > Remove automatic version resolution for POM plugins > --- > > Key: MNG-4173 > URL: http://jira.codehaus.org/browse/MNG-4173 > Project: Maven 2 > Issue Type: Task > Components: Plugins and Lifecycle >Affects Versions: 3.0-alpha-3 >Reporter: Benjamin Bentmann >Assignee: Jason van Zyl > Fix For: 3.0-alpha-3 > > > Maven 3.x will no longer try to automatically find the version for plugins > specified in the POM, i.e. the effective POM must declare a version for each > plugin used for the sake of reproducible builds. Omitting the plugin version > will raise in error. -- 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: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects
[ http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177892#action_177892 ] Maria Odea Ching commented on MRELEASE-261: --- Additional fix for determining the common path which was failing in windows was committed to trunk -r778269. > release:prepare shouls support flat directory multimodule projects > -- > > Key: MRELEASE-261 > URL: http://jira.codehaus.org/browse/MRELEASE-261 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: prepare > Environment: linux / maven2 / svn >Reporter: paul.whe...@gmail.com >Assignee: Maria Odea Ching > Fix For: 2.0-beta-10 > > Attachments: flatProject.main.patch, flatProject.test.patch, > MRELEASE-261-with-its-v3.patch, MRELEASE-261-with-its.patch, > MRELEASE-261.patch, PrepareReleaseMojo.patch > > > What I mean by flat file structure firstly. > parent/pom.xml > module1/pom.xml > module2/pom.xml > . > . > . > module15/pom.xml > the parent references the modules like so > > ../module1 > ../module2 > . > . > . > ../module15 > > When i release:prepare only the parent project is tagged the modules > projects versions are incremented etc but the modules are not tagged in svn. > I use this structure as i use eclipse as my IDE. > I would love to see a fix for the issue marked as closed here > http://jira.codehaus.org/browse/MRELEASE-138. I am currenrly tagging by hand > each submodule of the projects but it would be so nice to have the release > plugin do this for me. > forgive my english. -- 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
