[
http://jira.codehaus.org/browse/MNG-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107630
]
Mikko Koponen edited comment on MNG-2045 at 9/18/07 4:19 AM:
-
Attaching mng-2045-ittest.zip, which
[
http://jira.codehaus.org/browse/MNG-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikko Koponen updated MNG-2045:
---
Attachment: mng-2045-ittest.zip
Attaching mng-2045-ittest.zip, which contains an integration test reproducing
[
http://jira.codehaus.org/browse/MNG-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107556
]
Mikko Koponen edited comment on MNG-2045 at 9/17/07 7:24 AM:
-
We're also running into this problem,
[
http://jira.codehaus.org/browse/MNG-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107556
]
Mikko Koponen edited comment on MNG-2045 at 9/17/07 7:23 AM:
-
We're also running into this problem,
[
http://jira.codehaus.org/browse/MNG-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107556
]
Mikko Koponen commented on MNG-2045:
We're also running into this problem, which is that:
* We have project A with common t
[
http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105832
]
Mikko Koponen commented on MNG-1323:
Ugliest workaround yet:
Since we are mostly running into this when using the maven-ant
[
http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105828
]
Mikko Koponen commented on MNG-1323:
Sounds to me like plugin dependencies should be execution-specific?
> Plugin extensio
Make eclipse:rad work with manifests without "Class-Path:"-entries
--
Key: MECLIPSE-319
URL: http://jira.codehaus.org/browse/MECLIPSE-319
Project: Maven 2.x Eclipse Plugin
Issue
[
http://jira.codehaus.org/browse/MDEPLOY-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikko Koponen updated MDEPLOY-46:
-
Attachment: MDEPLOY-46.patch
Attaching a one-liner patch to fix this issue.
I ain't no maven expert, s
[ http://jira.codehaus.org/browse/ARCHETYPE-57?page=comments#action_81980 ]
Mikko Koponen commented on ARCHETYPE-57:
Disclaimer: "I ain't no maven expert, or committer for that matter"
But that patch took about 15 minutes. So one without
[ http://jira.codehaus.org/browse/ARCHETYPE-39?page=all ]
Mikko Koponen updated ARCHETYPE-39:
---
Attachment: ARCHETYPE-39.patch
One-liner to fix this.
Usage:
${dollarSign}{artifactId}
${dollarSign}{whatever.else}
> Add tool for working with escaping i
[ http://jira.codehaus.org/browse/ARCHETYPE-58?page=comments#action_81581 ]
Mikko Koponen commented on ARCHETYPE-58:
Also, custom properties for "ARCHETYPE-58-a-slightly-different-kind-of-patch"
are configured in a "slightly-more-maven-ki
[ http://jira.codehaus.org/browse/ARCHETYPE-58?page=all ]
Mikko Koponen updated ARCHETYPE-58:
---
Attachment: ARCHETYPE-58-a-slightly-different-kind-of-patch
Some sort of source formatting has been applied to the
"properties_and_conditions.patch".
As t
[ http://jira.codehaus.org/browse/ARCHETYPE-57?page=comments#action_81577 ]
Mikko Koponen commented on ARCHETYPE-57:
Argh. Typo in the example, should be:
Like so:
src/main/java/foo/bar/baz/
(Note the forward slash at the end)
> Suppo
[ http://jira.codehaus.org/browse/ARCHETYPE-57?page=all ]
Mikko Koponen updated ARCHETYPE-57:
---
Attachment: ARCHETYPE-57-patch
Here you go. A very simple patch to fix this.
Define empty directories by suffixing the path with a slash '/'.
Like so:
[ http://jira.codehaus.org/browse/MNG-2666?page=comments#action_81574 ]
Mikko Koponen commented on MNG-2666:
This happens _at least_ when the project is being generated has a parent pom.
> archetype:create strips out comments from the templa
16 matches
Mail list logo