[jira] Commented: (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

[ http://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244032#action_244032 ] Arik Kfir commented on MNG-3092: +1 for including SNAPSHOTs in the version ranges if the artifact is in

[jira] Commented: (MRELEASE-318) Release plugin throws NullPointerException when using version range for dependency

[ http://jira.codehaus.org/browse/MRELEASE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235952#action_235952 ] Arik Kfir commented on MRELEASE-318: Brett, can you please elaborate about the "more general pr

[jira] Commented: (MRELEASE-519) release plugin fails on version ranges

[ http://jira.codehaus.org/browse/MRELEASE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231411#action_231411 ] Arik Kfir commented on MRELEASE-519: Hi, This happens to us too, using Maven 2.2.1 and version

[jira] Issue Comment Edited: (MDEPLOY-48) deploy:deploy-file does not support deploying sources jars too

[ http://jira.codehaus.org/browse/MDEPLOY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115012 ] arikkfir edited comment on MDEPLOY-48 at 11/27/07 4:10 AM: Note that deploy:deploy-file spews an

[jira] Issue Comment Edited: (MDEPLOY-48) deploy:deploy-file does not support deploying sources jars too

[ http://jira.codehaus.org/browse/MDEPLOY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115012 ] arikkfir edited comment on MDEPLOY-48 at 11/27/07 4:09 AM: Note that deploy:deploy-file spews an

[jira] Commented: (MDEPLOY-48) deploy:deploy-file does not support deploying sources jars too

[ http://jira.codehaus.org/browse/MDEPLOY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115012 ] Arik Kfir commented on MDEPLOY-48: -- Note that deploy:deploy-file spews an exceptions while deploying an artifact with the -

[jira] Commented: (MNG-3150) Command line -f option should propagate to module poms.

[ http://jira.codehaus.org/browse/MNG-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106823 ] Arik Kfir commented on MNG-3150: Why not use profiles for this? > Command line -f option should propagate to module poms. > --

[jira] Commented: (MEV-534) Dependencies of commons-logging should be optional

[ http://jira.codehaus.org/browse/MEV-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100701 ] Arik Kfir commented on MEV-534: --- Shouldn't log4j be optional too? > Dependencies of commons-logging should be optional >

[jira] Commented: (MAVENUPLOAD-1603) Upload JIDE Common Layer to maven repository

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99757 ] Arik Kfir commented on MAVENUPLOAD-1603: I don't see it either. > Upload JIDE Common Layer to maven repository

[jira] Commented: (MIDEA-86) [Patch] Add support for IDEA 7 (Selena) EJB/EAR modules

[ http://jira.codehaus.org/browse/MIDEA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95168 ] Arik Kfir commented on MIDEA-86: ok... > [Patch] Add support for IDEA 7 (Selena) EJB/EAR modules >

[jira] Reopened: (MEV-518) Google Juice POM has wrong "" - should be "jar" and not "pom"

[ http://jira.codehaus.org/browse/MEV-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arik Kfir reopened MEV-518: --- Problem seems to still exist, although the duplicated issue is marked as fixed. Packaging is still "pom" in the "pom.xml"

[jira] Created: (MEV-518) Google Juice POM has wrong "" - should be "jar" and not "pom"

Google Juice POM has wrong "" - should be "jar" and not "pom" Key: MEV-518 URL: http://jira.codehaus.org/browse/MEV-518 Project: Maven Evangelism Issue Type: Bug

[jira] Commented: (MNG-2715) Maven does not comply to XML rules regarding prefixes.

[ http://jira.codehaus.org/browse/MNG-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93797 ] Arik Kfir commented on MNG-2715: Seva, I don't think Jason meant Maven will *never* support namespaces; only the 2.0.x branch

[jira] Created: (MIDEA-86) [Patch] Add support for IDEA 7 (Selena) EJB/EAR modules

[Patch] Add support for IDEA 7 (Selena) EJB/EAR modules --- Key: MIDEA-86 URL: http://jira.codehaus.org/browse/MIDEA-86 Project: Maven 2.x Idea Plugin Issue Type: Improvement Affects Ve

[jira] Commented: (MIDEA-39) In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository

[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91703 ] Arik Kfir commented on MIDEA-39: This is definitly working for me in 2.1-SNAPSHOT. Caveat is to run "mvn idea:idea" in the mult

[jira] Commented: (MIDEA-82) [Patch] EJB module packaging is not generated correctly, and also does not support EJB 3.0

[ http://jira.codehaus.org/browse/MIDEA-82?page=comments#action_84277 ] Arik Kfir commented on MIDEA-82: Sure: $MAVEN_REPO$ - I guess you're right ;-) About 5: if we drop the MAVEN_REPO thing, then 5 is no longer required (replace all calls to

[jira] Commented: (MIDEA-82) [Patch] EJB module packaging is not generated correctly, and also does not support EJB 3.0

[ http://jira.codehaus.org/browse/MIDEA-82?page=comments#action_84267 ] Arik Kfir commented on MIDEA-82: Hi, The $MAVEN_REPO$ is a macro (idea feature, much like path variables in eclipse) which points to the local maven repository. The user has

[jira] Created: (MIDEA-82) [Patch] EJB module packaging is not generated correctly, and also does not support EJB 3.0

[Patch] EJB module packaging is not generated correctly, and also does not support EJB 3.0 -- Key: MIDEA-82 URL: http://jira.codehaus.org/browse/MIDEA-82 Project:

[jira] Commented: (MSITE-202) Language bundle not found for empty pom project

[ http://jira.codehaus.org/browse/MSITE-202?page=comments#action_83183 ] Arik Kfir commented on MSITE-202: - Ooops - strike that: I was accidently using Maven 2.1 (I know 2.1 had some problems with the site plugin lately... I think Jason is workin

[jira] Commented: (MSITE-202) Language bundle not found for empty pom project

[ http://jira.codehaus.org/browse/MSITE-202?page=comments#action_83181 ] Arik Kfir commented on MSITE-202: - This happens to me too. And the weird thing - it happens when I invoke "mvn clean install" - not even invoking the site plugin > Lang

[jira] Updated: (MEV-475) glazedlists 1.7.0 "-sources" JAR is built incorrectly

[ http://jira.codehaus.org/browse/MEV-475?page=all ] Arik Kfir updated MEV-475: -- Attachment: glazedlists_java15-1.7.0-sources.jar > glazedlists 1.7.0 "-sources" JAR is built incorrectly > - > >

[jira] Created: (MEV-475) glazedlists 1.7.0 "-sources" JAR is built incorrectly

glazedlists 1.7.0 "-sources" JAR is built incorrectly - Key: MEV-475 URL: http://jira.codehaus.org/browse/MEV-475 Project: Maven Evangelism Issue Type: Bug Reporter: Arik Kfir

[jira] Commented: (MSITE-186) Display version numbers in documentation, particularly for plugins

[ http://jira.codehaus.org/browse/MSITE-186?page=comments#action_78747 ] Arik Kfir commented on MSITE-186: - If the site.xml could be interpolated with macros such as "${project.version}" then this would be easy - one would simply add the ${versio

[jira] Commented: (MNG-3) MavenProject / pom listener

[ http://jira.codehaus.org/browse/MNG-3?page=comments#action_75691 ] Arik Kfir commented on MNG-3: - Hi, I still think this can make IDE integration easier, but for now - I think this issue shouldn't be marked as FIXED, but rather WON'T FIX, or incom

[jira] Commented: (MEAR-42) General setting of dependency filenames

[ http://jira.codehaus.org/browse/MEAR-42?page=comments#action_75398 ] Arik Kfir commented on MEAR-42: --- IMO this should also be the default... > General setting of dependency filenames > --- > > K

[jira] Commented: (MNG-2511) Need ability to redefine distribution management url

[ http://jira.codehaus.org/browse/MNG-2511?page=comments#action_72590 ] Arik Kfir commented on MNG-2511: Milos, It should work, but I think this JIRA refers to use-cases when the project at hand had not defined such a property. For example, we w

[jira] Commented: (MPIR-54) Team list table improvement

[ http://jira.codehaus.org/browse/MPIR-54?page=comments#action_72211 ] Arik Kfir commented on MPIR-54: --- I noticed that your patch creates two organization columns - one for the organization name ("Organization") and one for the organization URL ("

[jira] Commented: (MSITE-29) Imposible to generated UTF-8 site with APT

[ http://jira.codehaus.org/browse/MSITE-29?page=comments#action_70397 ] Arik Kfir commented on MSITE-29: I think this issue can be closed... > Imposible to generated UTF-8 site with APT > -- > >

[jira] Commented: (MNG-1258) Add option to redownload poms

[ http://jira.codehaus.org/browse/MNG-1258?page=comments#action_68763 ] Arik Kfir commented on MNG-1258: Hi, You could use the "If-Modified-Since" HTTP header when querying the repo. All HTTP servers support this (part of HTTP protocol). This essentially te

[jira] Commented: (SCM-195) Wrong SCM info put by the release plugin for modules

[ http://jira.codehaus.org/browse/SCM-195?page=comments#action_65273 ] Arik Kfir commented on SCM-195: --- emmanuel: when the release plugin writes the modified pom back into svn (with the released version, etc), it also writes a wrong scm url (under the tag).

[jira] Created: (MJAVADOC-69) javadoc plugin install fails when running "mvn install" from plugins dir

javadoc plugin install fails when running "mvn install" from plugins dir Key: MJAVADOC-69 URL: http://jira.codehaus.org/browse/MJAVADOC-69 Project: Maven 2.x Javadoc Plugin Type: Bug Environme

[jira] Commented: (MNG-1330) direct support for mock classes

[ http://jira.codehaus.org/browse/MNG-1330?page=comments#action_64410 ] Arik Kfir commented on MNG-1330: I disagree - there are too many source dirs already, and the test-jar works perfectly...no need to complicate things, IMO. > direct support for mock cla

[jira] Commented: (MNG-624) automatic parent versioning

[ http://jira.codehaus.org/browse/MNG-624?page=comments#action_64409 ] Arik Kfir commented on MNG-624: --- two more cents: imo the algoritm should do the following: (in specified order) 1. if a version is given, resolve it from reactor/repository 2. otherwise, if

[jira] Commented: (CONTINUUM-37) Add a professional user interface

[ http://jira.codehaus.org/browse/CONTINUUM-37?page=comments#action_64237 ] Arik Kfir commented on CONTINUUM-37: I think a better alternative would be a Swing interface to be launched via Java Web Start. > Add a professional user interface > ---

[jira] Commented: (MJAR-37) HttpJarSignClient - New goal "httpsign" which will sign jar files by submitting them to a signing service via HTTP Post

[ http://jira.codehaus.org/browse/MJAR-37?page=comments#action_63496 ] Arik Kfir commented on MJAR-37: --- Just an idea - this can be a cool Plexus component (JAR signing, that is...especially by HTTP) > HttpJarSignClient - New goal "httpsign" which will sign ja

[jira] Commented: (MINSTALL-17) Tests fail when running from parent

[ http://jira.codehaus.org/browse/MINSTALL-17?page=comments#action_63043 ] Arik Kfir commented on MINSTALL-17: --- Perhaps the fix can be somehow propagated to the plugin-testing-harness, so that this won't have to be specified repeatedly for each test... >

[jira] Created: (MINSTALL-17) Tests fail when running from parent

Tests fail when running from parent --- Key: MINSTALL-17 URL: http://jira.codehaus.org/browse/MINSTALL-17 Project: Maven 2.x Install Plugin Type: Bug Versions: 2.2 Environment: Fedora Core 5, JDK 1.5.0_06 Reporter: Arik K