[jira] Commented: (MNG-3866) Plugin definitions from child and parent are not merged when version differs
[
http://jira.codehaus.org/browse/MNG-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155875#action_155875
]
Benjamin Bentmann commented on MNG-3866:
Another example parent POM snippet:
{code:xml}
org.apache.maven.plugins
maven-release-plugin
2.0-beta-7
deploy
{code}
Child POM snippet:
{code:xml}
org.apache.maven.plugins
maven-release-plugin
2.0-beta-8
{code}
Effective child POM for Maven 2.0.9:
{code:xml}
org.apache.maven.plugins
maven-release-plugin
2.0-beta-8
deploy
{code}
Effective child POM for Maven 3.x trunk:
{code:xml}
org.apache.maven.plugins
maven-release-plugin
2.0-beta-8
{code}
> Plugin definitions from child and parent are not merged when version differs
>
>
> Key: MNG-3866
> URL: http://jira.codehaus.org/browse/MNG-3866
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0-alpha-1
>Reporter: Benjamin Bentmann
> Attachments: plugin-model-container.patch
>
>
> Parent POM snippet
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
>
>
> PASSED
>
>
>
> {code}
> Child POM snippet:
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
> 2.1-SNAPSHOT
>
>
> {code}
> Effective child POM:
> {code:xml}
>
>
> org.apache.maven.its.plugins
> maven-it-plugin-configuration
> 2.1-SNAPSHOT
>
>
> {code}
> i.e. the configuration from the parent POM is completely lost.
--
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: (MAVENUPLOAD-2288) "net.sf.twip","mavens...@web.sourceforge.net/home/groups/t/tw/twip/htdocs/maven/repository","rsync_ssh","Snackbox","snack...@users.sourceforge.net",,
"net.sf.twip","[EMAIL PROTECTED]/home/groups/t/tw/twip/htdocs/maven/repository","rsync_ssh","Snackbox","[EMAIL PROTECTED]",, - Key: MAVENUPLOAD-2288 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2288 Project: Maven Upload Requests Issue Type: Wish Reporter: Snackbox -- 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-3878) maven2 cannot be built with plexus-container-default > 1.0-alpha-29
maven2 cannot be built with plexus-container-default > 1.0-alpha-29 --- Key: MNG-3878 URL: http://jira.codehaus.org/browse/MNG-3878 Project: Maven 2 Issue Type: Bug Components: Bootstrap & Build Affects Versions: 2.0.9 Environment: plexus-container-default 1.0-alpha-30 ... 1.0-beta-2 Reporter: Torsten Werner package org.codehaus.plexus.embed; has been removed in version 1.0-alpha-30 of plexus-container-default and the current version is 1.0-beta-2. It would be nice if maven can be built with a more recent version of plexus-container-default. -- 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: (SCM-262) scm:tag for subversion tagging from local version of code, not directly from repository
[ http://jira.codehaus.org/browse/SCM-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155881#action_155881 ] Yann Albou commented on SCM-262: Yes, I agree with you. But this worst scenario is not the most common. Another way, would be to get a svn lock and then release lock when the tag is done. > scm:tag for subversion tagging from local version of code, not directly from > repository > --- > > Key: SCM-262 > URL: http://jira.codehaus.org/browse/SCM-262 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn >Reporter: Stephan Heilner > Fix For: future > > > In theory, you shouldn't tag or branch from a local and potentially different > version of the code. From what I can tell, the scm:tag imports your existing > code into a new tag. With subversion, tagging is very lightweight if you do > a 'svn copy trunk_url tag_url'. The way it currently works make sense for > other repositories such as CVS but not for subversion. -- 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: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155882#action_155882
]
Yann Albou commented on SCM-406:
Why not using the SVN lock and then release lock when the tag is done ?
By doing this we will prevent others to commit changes during the tag.
> scm tag does not work with Subversion 1.5.1
> ---
>
> Key: SCM-406
> URL: http://jira.codehaus.org/browse/SCM-406
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.0
>Reporter: James William Dumay
> Fix For: 1.1.1
>
>
> scm:checkin does not work with Subversion 1.5.1
> On release:perform (which I assume calls scm:checkin) the following error
> occurs:
> {code}
> svn: File
> '/svn/private/atlassian/confluence/tags/confluence-project-2.10-m1/conf-acceptance-test/pom.xml'
> already exists
> {code}
> Using subversion 1.4.x is a good enough workaround.
--
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: (MCHANGES-142) Support Google Code
Support Google Code --- Key: MCHANGES-142 URL: http://jira.codehaus.org/browse/MCHANGES-142 Project: Maven 2.x Changes Plugin Issue Type: New Feature Components: other issue-trackers Reporter: Jeff Jensen Another tracker gaining popularity. Found this that someone had started: http://code.google.com/p/maven-googlecode/ -- 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: (SCM-262) scm:tag for subversion tagging from local version of code, not directly from repository
[ http://jira.codehaus.org/browse/SCM-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155903#action_155903 ] George Gastaldi commented on SCM-262: - Yann, I may be wrong, but I know that there are some OS (Windows, for instance) that do not allow locking in SVN. Also,locking the entire trunk would be overkill in a big team (take any apache project and you will see that). > scm:tag for subversion tagging from local version of code, not directly from > repository > --- > > Key: SCM-262 > URL: http://jira.codehaus.org/browse/SCM-262 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn >Reporter: Stephan Heilner > Fix For: future > > > In theory, you shouldn't tag or branch from a local and potentially different > version of the code. From what I can tell, the scm:tag imports your existing > code into a new tag. With subversion, tagging is very lightweight if you do > a 'svn copy trunk_url tag_url'. The way it currently works make sense for > other repositories such as CVS but not for subversion. -- 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: (MAVENUPLOAD-2289) Upload maven-jetty-pluto-embedded 1.0.1
Upload maven-jetty-pluto-embedded 1.0.1 --- Key: MAVENUPLOAD-2289 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2289 Project: Maven Upload Requests Issue Type: Wish Reporter: Nils-Helge Garli Please upload new version 1.0.1 of maven-jetty-pluto-embedded. -- 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] Reopened: (MARTIFACT-23) Log download duration and speed
[ http://jira.codehaus.org/browse/MARTIFACT-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reopened MARTIFACT-23: --- > Log download duration and speed > --- > > Key: MARTIFACT-23 > URL: http://jira.codehaus.org/browse/MARTIFACT-23 > Project: Maven Artifact > Issue Type: Improvement >Reporter: Igor Fedorenko > > It would be helpful if maven embedder log messages about time each download > from remote repository took as well as per-repository totals. This would help > users identify problems related to slow remote repositories. -- 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] Reopened: (MARTIFACT-24) make it possible to force redeployment of an artifact that already exists in the remote metadata
[ http://jira.codehaus.org/browse/MARTIFACT-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reopened MARTIFACT-24: --- > make it possible to force redeployment of an artifact that already exists in > the remote metadata > > > Key: MARTIFACT-24 > URL: http://jira.codehaus.org/browse/MARTIFACT-24 > Project: Maven Artifact > Issue Type: Improvement >Reporter: Brett Porter > > see MARTIFACT-6 for the original features. -- 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: (MARTIFACT-23) Log download duration and speed
[ http://jira.codehaus.org/browse/MARTIFACT-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MARTIFACT-23. - Resolution: Won't Fix setting a more appropriate resolution for maven-artifact > Log download duration and speed > --- > > Key: MARTIFACT-23 > URL: http://jira.codehaus.org/browse/MARTIFACT-23 > Project: Maven Artifact > Issue Type: Improvement >Reporter: Igor Fedorenko > > It would be helpful if maven embedder log messages about time each download > from remote repository took as well as per-repository totals. This would help > users identify problems related to slow remote repositories. -- 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: (MARTIFACT-7) Clear separation of local versus remote concerns
[ http://jira.codehaus.org/browse/MARTIFACT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MARTIFACT-7. Resolution: Won't Fix Fix Version/s: (was: 3.0) > Clear separation of local versus remote concerns > > > Key: MARTIFACT-7 > URL: http://jira.codehaus.org/browse/MARTIFACT-7 > Project: Maven Artifact > Issue Type: Improvement >Reporter: Jason van Zyl > > The resolution very much couples local with remote repositories. For example > simply querying for all available versions requires some twiddling and faking > out the resolver because the local metadata is always used but I only want to > know about remote repositories. We just need to be able to query remote > repositories easily. Getting all the remote versions to prevent redeployment > is a perfect use case. -- 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] Reopened: (MARTIFACT-6) The deployer should detect previous deployments of the same version and die if that's the case.
[ http://jira.codehaus.org/browse/MARTIFACT-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reopened MARTIFACT-6: -- This should still be dealt with for non-HTTP repositories IMO. I'm assuming Mercury will be the front-end facade for those. > The deployer should detect previous deployments of the same version and die > if that's the case. > --- > > Key: MARTIFACT-6 > URL: http://jira.codehaus.org/browse/MARTIFACT-6 > Project: Maven Artifact > Issue Type: Improvement >Affects Versions: 3.0-alpha-1 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-1 > > Attachments: test.zip > > > We simply have to die because giving people an option is just going to let > them continue with their bad practices. If you let the redeployment of > released binaries then it will happen, and it will cause problems. -- 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] Reopened: (MARTIFACT-7) Clear separation of local versus remote concerns
[ http://jira.codehaus.org/browse/MARTIFACT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reopened MARTIFACT-7: -- > Clear separation of local versus remote concerns > > > Key: MARTIFACT-7 > URL: http://jira.codehaus.org/browse/MARTIFACT-7 > Project: Maven Artifact > Issue Type: Improvement >Reporter: Jason van Zyl > > The resolution very much couples local with remote repositories. For example > simply querying for all available versions requires some twiddling and faking > out the resolver because the local metadata is always used but I only want to > know about remote repositories. We just need to be able to query remote > repositories easily. Getting all the remote versions to prevent redeployment > is a perfect use case. -- 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: (MAVENUPLOAD-2253) Upload Joda-Time 1.6
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Helger updated MAVENUPLOAD-2253: --- Attachment: pom.xml I tried to create a POM for version 1.6.0 It is based on the 1.5.2 POM and should work with a freshly checked out joda-time version. I use ant tasks to create the TZ data. The problem is just: I'm building it on a german Windows so the default tests fail, because they expect an english version of Windows. I therefore added some defines for the default Locale for running the tests. Somebody needs to confirm that the resulting jar and source.jar work properly. I tested it in a local Eclipse project and it seems to work fine... > Upload Joda-Time 1.6 > > > Key: MAVENUPLOAD-2253 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2253 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Stephen Colebourne > Attachments: pom.xml > > > http://joda-time.sourceforge.net/joda-time-1.6-bundle.jar > > http://joda-time.sourceforge.net > http://joda-time.sourceforge.net/team-list.html > > Please upload joda-time 1.6 -- 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-3879) Dependency map and documentation
Dependency map and documentation Key: MNG-3879 URL: http://jira.codehaus.org/browse/MNG-3879 Project: Maven 2 Issue Type: New Feature Components: Dependencies Affects Versions: 2.0.9 Reporter: benson margulies This JIRA proposes a feature. I'm willing to try to contribute it given a modicum of encouragement and guidance. Over at CXF, we get many questions from users who are completely confounded by the complex dependency graph that results from our many dependencies and their many dependencies. I think that they would be less confused by far if maven gave them a tiny bit of help. The first part of the idea requires an addition to the core POM, which is why I'm starting with a JIRA here. I propose to add an 'explanation' element to the dependency element. This would contain a human-readable string explaining why the dependency is here. The second part is a goal that I would propose to call 'dependency-map'. This would produce a formatted map of the dependency tree -- enriched, of course, by the comments in the first part. -- 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: (MECLIPSE-414) Not beeing @aggregator, eclipse plugin does not require executedProject
[
http://jira.codehaus.org/browse/MECLIPSE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155948#action_155948
]
Barrie Treloar commented on MECLIPSE-414:
-
After splattering in some debug code:
[ERROR]
executedProject.getCompileSourceRoots=[D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\project-11\src\main\java,
D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\project-11\target\generated-sources\modello]
[ERROR]
project.getCompileSourceRoots=[D:\ide\maven\maven-eclipse-plugin\target\test-classes\projects\project-11\src\main\java]
So you can see that the executeProject has additional targets.
m-eclipse-p is not in a reactor and my limited understanding is that other
plugins run prior to m-eclipse-p *contribute* to the current project. So not
sure why executedProject is being set and/or updated.
> Not beeing @aggregator, eclipse plugin does not require executedProject
> ---
>
> Key: MECLIPSE-414
> URL: http://jira.codehaus.org/browse/MECLIPSE-414
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: nicolas de loof
>Assignee: Barrie Treloar
> Fix For: 2.6
>
>
> The eclispe plugin uses both ${executedProject} and ${project}.
> Not beeing an aggregator plugin, ${project} is allways tghe currently
> executed project, and the projectDirectory is project.getBasedir().
> Having two attributes for same target makes the plugin harder to understand
--
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: (MECLIPSE-414) Not beeing @aggregator, eclipse plugin does not require executedProject
[
http://jira.codehaus.org/browse/MECLIPSE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155950#action_155950
]
Barrie Treloar commented on MECLIPSE-414:
-
While this isn't @aggregator it *is*
@execute phase="generate-resources"
which means a forked lifecycle and hence the use of executedProject
I'm looking into why it needs a forked lifecycle...
> Not beeing @aggregator, eclipse plugin does not require executedProject
> ---
>
> Key: MECLIPSE-414
> URL: http://jira.codehaus.org/browse/MECLIPSE-414
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: nicolas de loof
>Assignee: Barrie Treloar
> Fix For: 2.6
>
>
> The eclispe plugin uses both ${executedProject} and ${project}.
> Not beeing an aggregator plugin, ${project} is allways tghe currently
> executed project, and the projectDirectory is project.getBasedir().
> Having two attributes for same target makes the plugin harder to understand
--
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-3830) 3.0-alpha-1 release: upgrade to the new plexus container
[ http://jira.codehaus.org/browse/MNG-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-3830. -- Resolution: Fixed We'll stick with 1.0-beta-3.0.1. I'll update if we find something dire. > 3.0-alpha-1 release: upgrade to the new plexus container > > > Key: MNG-3830 > URL: http://jira.codehaus.org/browse/MNG-3830 > Project: Maven 2 > Issue Type: Sub-task >Reporter: Brian Fox >Assignee: Jason van Zyl > Fix For: 3.0-alpha-1 > > -- 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: (MAVENUPLOAD-2290) Clover2.4.2 artifact upload
Clover2.4.2 artifact upload --- Key: MAVENUPLOAD-2290 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2290 Project: Maven Upload Requests Issue Type: Task Reporter: Nick Pellow Assignee: Carlos Sanchez This bundle contains the Clover 2.3.1 core classes. The Maven Clover 2.3.1 plugin depends on this. Could you please upload this to your maven1 repository. -- 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: (MAVENUPLOAD-2291) Clover 2.4.2 core artifact upload request
Clover 2.4.2 core artifact upload request - Key: MAVENUPLOAD-2291 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2291 Project: Maven Upload Requests Issue Type: Task Reporter: Nick Pellow Please upload this to the maven1 repository. Clover 2.4.2 for Maven has support for Clover's Test Optimization. Clover is free for open source projects. -- 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: (MAVENUPLOAD-2290) Clover2.4.2 artifact upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Pellow closed MAVENUPLOAD-2290. Resolution: Incomplete clone FAIL > Clover2.4.2 artifact upload > --- > > Key: MAVENUPLOAD-2290 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2290 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Nick Pellow >Assignee: Carlos Sanchez > > This bundle contains the Clover 2.3.1 core classes. The Maven Clover 2.3.1 > plugin depends on this. > Could you please upload this to your maven1 repository. -- 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: (MAVENUPLOAD-2292) maven1 clover2 plugin bundle upload
maven1 clover2 plugin bundle upload --- Key: MAVENUPLOAD-2292 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2292 Project: Maven Upload Requests Issue Type: Task Reporter: Nick Pellow This is the actual maven1 plugin bundle - ready for deployment. The new: clover:test-optimize goal, will run an optimized test set, depending on what tests hit what code during the first full test run. -- 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-3874) Make sure Mercury builds with Maven 3.0.x
[ http://jira.codehaus.org/browse/MNG-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-3874. -- Resolution: Fixed Mercury is working with Maven 3.x. > Make sure Mercury builds with Maven 3.0.x > - > > Key: MNG-3874 > URL: http://jira.codehaus.org/browse/MNG-3874 > Project: Maven 2 > Issue Type: Bug >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.0-alpha-1 > > -- 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: (MNG-3874) Make sure Mercury builds with Maven 3.0.x
[
http://jira.codehaus.org/browse/MNG-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155967#action_155967
]
Oleg Gusakov commented on MNG-3874:
---
{code}
mvn -v
Maven version: 3.0-SNAPSHOT built on unknown
Java version: 1.5.0_16
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x" version: "10.5.5" arch: "i386" family: "unix"
{code}
*mvn clean install* worked fine on the project and ITs
> Make sure Mercury builds with Maven 3.0.x
> -
>
> Key: MNG-3874
> URL: http://jira.codehaus.org/browse/MNG-3874
> Project: Maven 2
> Issue Type: Bug
>Reporter: Jason van Zyl
>Assignee: Jason van Zyl
> Fix For: 3.0-alpha-1
>
>
--
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
