[jira] Created: (MEV-283) joda-time-1.2 has invalid pom

joda-time-1.2 has invalid pom - Key: MEV-283 URL: http://jira.codehaus.org/browse/MEV-283 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: david varnes the pom deployed to ibiblio has the following snippet

[jira] Commented: (MNG-1377) Planning support for wtp 1.0

[ http://jira.codehaus.org/browse/MNG-1377?page=comments#action_53119 ] david varnes commented on MNG-1377: --- Note that the WTP team have deferred fixing eclipse bug 116783 ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=116783 ) until post wtp-1.0 (maybe

Cargo M2 plugin [was] Re: [M2][Proposal] J2EE builds ...

Hi Vincent, Is the Cargo M2 plugin released anywhere, or is it only available in the beetlejuice ci 0.7-snapshot builds ? thanks davidv Vincent Massol wrote: [snip] > OTOH, it is possible to use tools like the Cargo m2 plugin in the WAR or EAR > component projects to perform integration tests

[jira] Created: (MNG-492) Fix mmld taglib discovery strategy for Ant compatibility

Environment: linux / m2-alpha-2 / jdk1.5.0_03 Reporter: david varnes Quote from John Casey on dev list (20 Jun 05): The short answer is that there is currently a bug in the m2 integration of marmalade. Last night I figured out that the taglib discovery strategy used for the Ant compatibility mode

Re: [m2] Marmalade plugin - how to use ant namespace

do. By no > accident, this is similar to Jelly's behavior in similar circumstances. > > Sorry for the confusion. > > -john > > david varnes wrote: > >>>Question for John, >>> >>>I am trying to use the marmalade ant compatibility layer. >&

[m2] Marmalade plugin - how to use ant namespace

Question for John, I am trying to use the marmalade ant compatibility layer. Using the downloaded m2-alpha-2 binaries. Questions: * Do I need to explicitly declare a plugin dependency on the marmalade-ant-compat jar ? * How do I register the ant namespace in the .mmld script? I have tried:

[jira] Created: (MNG-488) Default values for marmalade plugin parameters are ignored

: 2.0-alpha-2 Environment: * linux * jdk1.5.0_03 * downloaded m2 alpha2 Reporter: david varnes In my own marmalade plugin, and the maven-hello-plugin (from HEAD) I get this behaviour. $m2 hello:hello [INFO] maven-plugin-parent: resolved to version 2.0-20050414.001413-4 from

Re: [vote] bring m2-dev back to dev@maven.apache.org

+1 davidv Brett Porter wrote: Some time back, m2-dev@maven.apache.org was established for all Maven 2.x related traffic. The purpose of this was to reduce the noise on [EMAIL PROTECTED] As components of m2 will be used in Maven 1.x, and as m2 becomes the primary platform going forward, I think it w