It seems that version of the jira-plugin still uses maven 1 (You've got a
project.xml file, not a pom.xml file), so maven 2 will not work on that plugin.
The trunk of the plugin is using m2 instead of m1, so you could try that one (I
don't know how stable the trunk is) or you could try using
: Cannot execute mojo: eclipse.
It seems that version of the jira-plugin still uses maven 1 (You've got a
project.xml file, not a pom.xml file), so maven 2 will not work on that plugin.
The trunk of the plugin is using m2 instead of m1, so you could try that one (I
don't know how stable
I can't exactly se how can that help me with my customization of the
plugin's code :-)
Attila.
On 2008.03.28., at 15:27, [EMAIL PROTECTED] wrote:
Otherwise, you could try the distribution of the plugin ;)
http://svn.atlassian.com/svn/public/contrib/jira/jira-calendar-plugin/distributions/
In the future, you might just go right to the source and ask the
originating team responsible for the code why it doesn't compile. So
in this case, ask Atlassian directly.
(IMO the Maven users list cannot possibly hope to support every single
developer who stumbles across an open-source project
On 2008.03.28., at 15:35, Wayne Fay wrote:
In the future, you might just go right to the source and ask the
originating team responsible for the code why it doesn't compile. So
in this case, ask Atlassian directly.
Not being able to run mvn eclipse:eclipse (and several other fairly
On 3/28/08, Attila Szegedi [EMAIL PROTECTED] wrote:
Again, the conclusion I reached based on the observed symptoms was
that this is a Maven issue. Actually, it *is* a Maven issue; why would
Maven2 be allowed to break in such an ugly manner when facing a Maven1-
compliant project? Some sort of
