[jira] Created: (MNG-3952) Create Deprecation Mechanism for Maven Artifacts

2009-01-03 Thread Immo Huneke (JIRA)
Create Deprecation Mechanism for Maven Artifacts Key: MNG-3952 URL: http://jira.codehaus.org/browse/MNG-3952 Project: Maven 2 Issue Type: Improvement Components: Artifacts and

[jira] Issue Comment Edited: (MECLIPSE-373) eclipse:to-maven cannot resolve Required-Bundle: system.bundle

2008-02-05 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MECLIPSE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121507 ] immohuneke edited comment on MECLIPSE-373 at 2/5/08 5:55 AM: -- Simpler workaround: modify the

[jira] Commented: (MECLIPSE-373) eclipse:to-maven cannot resolve Required-Bundle: system.bundle

2008-02-05 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MECLIPSE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122389 ] Immo Huneke commented on MECLIPSE-373: -- Suggested improvement to the maven-eclipse-plugin: when parsing the

[jira] Commented: (MECLIPSE-373) eclipse:to-maven cannot resolve Required-Bundle: system.bundle

2008-01-28 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MECLIPSE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121507 ] Immo Huneke commented on MECLIPSE-373: -- Simpler workaround: modify the MANIFEST.MF file of the affected plugins

[jira] Created: (MECLIPSE-373) eclipse:to-maven cannot resolve Required-Bundle: system.bundle

2008-01-25 Thread Immo Huneke (JIRA)
eclipse:to-maven cannot resolve Required-Bundle: system.bundle -- Key: MECLIPSE-373 URL: http://jira.codehaus.org/browse/MECLIPSE-373 Project: Maven 2.x Eclipse Plugin Issue Type:

[jira] Commented: (MPMD-54) excludes appears to be ignored under Linux, even though it works fine under Windows

2007-12-03 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MPMD-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115665 ] Immo Huneke commented on MPMD-54: - Hi Xavier, Sorry, that was many months ago and I have moved on to a different project. I

[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.

2007-04-16 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93014 ] Immo Huneke commented on MRESOURCES-29: --- I have tried using the XML escape for $ - #36; - but to no avail. I suspect

[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.

2007-04-16 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93015 ] Immo Huneke commented on MRESOURCES-29: --- Oops - the comment above interpreted the XML escape for $ as $. The actual

[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.

2007-04-16 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93016 ] Immo Huneke commented on MRESOURCES-29: --- No, actually I have verified that writing amp;#36; is PRECISELY equivalent

[jira] Commented: (ARCHETYPE-39) Add tool for working with escaping in Velocity templates

2007-04-16 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/ARCHETYPE-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93021 ] Immo Huneke commented on ARCHETYPE-39: -- Thanks Wendy - as ever, you are a goldmine of information. I'm trying to use

[jira] Commented: (MNG-2276) profile activation by property doesn't work with properties defined in settings.

2007-04-16 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MNG-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93026 ] Immo Huneke commented on MNG-2276: -- Moreover, profile activation based on environment variables doesn't seem to work at all.

[jira] Created: (MPMD-54) excludes appears to be ignored under Linux, even though it works fine under Windows

2007-04-11 Thread Immo Huneke (JIRA)
excludes appears to be ignored under Linux, even though it works fine under Windows - Key: MPMD-54 URL: http://jira.codehaus.org/browse/MPMD-54 Project: Maven 2.x

[jira] Commented: (MPMD-54) excludes appears to be ignored under Linux, even though it works fine under Windows

2007-04-11 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MPMD-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92575 ] Immo Huneke commented on MPMD-54: - The second and third examples above got garbled because the asterisks were interpreted as

[jira] Created: (MCHANGES-73) No longer integrates with JIRA

2007-04-02 Thread Immo Huneke (JIRA)
No longer integrates with JIRA -- Key: MCHANGES-73 URL: http://jira.codehaus.org/browse/MCHANGES-73 Project: Maven 2.x Changes Plugin Issue Type: Bug Affects Versions: 2.0-beta-2 Environment: Windows

[jira] Commented: (MIDEA-57) Plugin does not properly handle dependency version using set notation

2007-01-30 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MIDEA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86290 ] Immo Huneke commented on MIDEA-57: -- Please could someone make available a build of the fixed plugin. I would like to test

[jira] Created: (MIDEA-83) When creating the model file, the parent POM's version of a dependency is added to the IDEA project's Libraries instead of the project POM's version

2007-01-30 Thread Immo Huneke (JIRA)
When creating the model file, the parent POM's version of a dependency is added to the IDEA project's Libraries instead of the project POM's version

[jira] Commented: (MIDEA-57) Plugin does not properly handle dependency version using set notation

2007-01-30 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MIDEA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86292 ] Immo Huneke commented on MIDEA-57: -- OK, I have discovered that there is a build available at

[jira] Commented: (MIDEA-83) When creating the model file, the parent POM's version of a dependency is added to the IDEA project's Libraries instead of the project POM's version

2007-01-30 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MIDEA-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86310 ] Immo Huneke commented on MIDEA-83: -- Thanks to whoever built the 2.1-SNAPSHOT release of the IDEA plugin. I have tested this

[jira] Commented: (MIDEA-54) Fixed range versions in dependencies corrupt the module file

2007-01-12 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MIDEA-54?page=comments#action_84826 ] Immo Huneke commented on MIDEA-54: -- This is proving very inconvenient for us too. We have some components that can work with a range of versions of other components. Each

[jira] Commented: (MIDEA-54) Fixed range versions in dependencies corrupt the module file

2007-01-12 Thread Immo Huneke (JIRA)
[ http://jira.codehaus.org/browse/MIDEA-54?page=comments#action_84827 ] Immo Huneke commented on MIDEA-54: -- By the way, I don't understand why this issue is marked closed - it still seems broken to me just as the description above says. Fixed