[jira] (MRELEASE-812) "prepare" does not commit before tagging and therefore deploys snapshot instead of release

[ https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342102#comment-342102 ] Aleksandr Tarutin commented on MRELEASE-812: I run into an issue where release:prepar

[jira] Created: (MEV-603) easyconf-0.9.5 is referencing missing artifacts

easyconf-0.9.5 is referencing missing artifacts --- Key: MEV-603 URL: http://jira.codehaus.org/browse/MEV-603 Project: Maven Evangelism Issue Type: Bug Components: Dependencies

[jira] Commented: (MRM-501) Saving configuration fails through the webapp.

[ http://jira.codehaus.org/browse/MRM-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107395 ] Aleksandr Tarutin commented on MRM-501: --- It seems like this is a part of a larger problem. After I manually created the f

[jira] Created: (MRM-501) Saving configuration fails through the webapp.

Saving configuration fails through the webapp. -- Key: MRM-501 URL: http://jira.codehaus.org/browse/MRM-501 Project: Archiva Issue Type: Bug Components: web application Affects Versio

[jira] Created: (MRM-497) Incomplete deployment descriptor

Incomplete deployment descriptor Key: MRM-497 URL: http://jira.codehaus.org/browse/MRM-497 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-2 R

[jira] Created: (MECLIPSE-179) Revise dependency configuration for WTP 1.5 EAR projects

Revise dependency configuration for WTP 1.5 EAR projects - Key: MECLIPSE-179 URL: http://jira.codehaus.org/browse/MECLIPSE-179 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement

[jira] Created: (MNG-2620) Guide to Building Maven 2.0 needs to be updated to reflect the real process

Guide to Building Maven 2.0 needs to be updated to reflect the real process --- Key: MNG-2620 URL: http://jira.codehaus.org/browse/MNG-2620 Project: Maven 2 Issue Type:

[jira] Updated: (MIDEA-33) Use path variables instead of absolute path to the Maven repository

[ http://jira.codehaus.org/browse/MIDEA-33?page=all ] Aleksandr Tarutin updated MIDEA-33: --- Attachment: maven-idea-plugin-1.patch > Use path variables instead of absolute path to the Maven repository > ---

[jira] Commented: (MIDEA-36) Multi-module vs. Single-module projects

[ http://jira.codehaus.org/browse/MIDEA-36?page=comments#action_61098 ] Aleksandr Tarutin commented on MIDEA-36: I can see your point but I never tried that setup with IDEA. It seems like the root pom is the only file worth including in the global co

[jira] Created: (MIDEA-37) Add functionality to create EAR modules.

Add functionality to create EAR modules. Key: MIDEA-37 URL: http://jira.codehaus.org/browse/MIDEA-37 Project: Maven 2.x Idea Plugin Type: Improvement Reporter: Aleksandr Tarutin Add functionality to create EAR modules a

[jira] Created: (MIDEA-36) Multi-module vs. Single-module projects

Multi-module vs. Single-module projects --- Key: MIDEA-36 URL: http://jira.codehaus.org/browse/MIDEA-36 Project: Maven 2.x Idea Plugin Type: Bug Reporter: Aleksandr Tarutin In IDEA's single module project the module files (.

[jira] Commented: (MIDEA-36) Multi-module vs. Single-module projects

[ http://jira.codehaus.org/browse/MIDEA-36?page=comments#action_61038 ] Aleksandr Tarutin commented on MIDEA-36: The plugin always creates module file in project directory. > Multi-module vs. Single-module projects > -

[jira] Commented: (MIDEA-34) Add resources to source folders instead of module libraries

[ http://jira.codehaus.org/browse/MIDEA-34?page=comments#action_61037 ] Aleksandr Tarutin commented on MIDEA-34: Nice! It works for me. > Add resources to source folders instead of module libraries > --

[jira] Created: (MIDEA-33) Use path variables instead of absolute path to the Maven repository

Use path variables instead of absolute path to the Maven repository --- Key: MIDEA-33 URL: http://jira.codehaus.org/browse/MIDEA-33 Project: Maven 2.x Idea Plugin Type: New Feature Reporter: Aleksan