[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 in build/resources resource targetPathMETA-INF/targetPath includes includeNOTICE.txt/include /includes /resource which is causing it to fail validation in maven 2.0.1 builds NB: this pom is not present in svn://svn.codehaus.org/maven/scm/repository so I was not able to do a diff from that repo (as per instructions here http://maven.apache.org/guides/mini/guide-maven-evangelism.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 wtp-1.0.1 but they have not investigated yet, see comments in bug). Anyone know when they plan 1.0.1 ? This bug relates to a failure to deploy externally defined artifacts to the the target WEB-INF/lib in server container. Thus it is a regression from m6, IIRC. In other words project dependency jars that are defined to be in MAVEN_REPO are not deployed to server using Publish action. You might want to add a comment regarding importance to maven users or add a vote. IMHO this is a show stopper for easy (ie parrallel) use of m2 and wtp-1.0. As a work around can we extend the standard maven 'deploy' to doa specific 'clean' and then 'resource' copy of the required artifacts to a nominated server location eg for Tomcat 5.5 it is WORKSPACE/.metadata/.plugins/org.eclipse.wst.server.core/tmpN/webapps/finalName/WEB-INF/lib ? Planning support for wtp 1.0 Key: MNG-1377 URL: http://jira.codehaus.org/browse/MNG-1377 Project: Maven 2 Type: Improvement Components: maven-eclipse-plugin Reporter: fabrizio giustina Priority: Minor while approaching the 1.0 release WTP changed completely the project descriptors for modules. The eclipse plugin should let users choose the version of WTP and generate different files (wtp will anyway automatically migrate 0.7 projects starting from M9, according to eclipse plans) Changes tracked for wtp 1.0 (partially working in current WTP builds): - .wtpmodules is renamed to .component and moved to the .settings folder - the .wtpmodules format is unchanged, except for the module type which is not there anymore (should be verified in M9) - a new .settings/org.eclipse.wst.common.project.facet.core.prefs file is written (property file) with server/module type information (server is now specified in containerClasspath, need to be fixed) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 using a *default* configuration. [snap] Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Marmalade plugin - how to use ant namespace
Hey thanks for the prompt response John, it all makes sense. Looking forward to the next cut, appreciate your work. daivdv John Casey wrote: 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 is not configured when m2 attempts to execute a marmalade-mojo. This means that the Ant functionality will never be recognized. I'm going to try to get a stop-gap fix in place for the next release of m2 that will fix this shortcoming. Once that's done, you should be able to: 1. declare the ant namespace using mojo xmlns:ant=ant:ant 2. add a project dependency on: dependency groupIdmarmalade/groupId artifactIdmarmalade-compat-ant/artifactId version1.0-alpha-3/version /dependency A couple of notes: * The reason we're not using the marmalade:ant namespace for Ant compatibility is to leave room for native-marmalade ports of Ant tasks. * Under the marmalade configuration used by m2, any tag that cannot be found is dumped to the logs for lack of anything better to 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. 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: mojo xmlns=marmalade:mojo xmlns:ant=marmalade:ant ... [snip] ... execute ant:echotest echo/ant:echo /execute /mojo As well as just in the ant tag: ant:echo xmlns:ant=marmalade:anttest echo/ant:echo but neither work. The whole tag just gets copied to standard out. Is there an example maven plugin anywhere that uses the marmalade ant compatibility layer ? thanks for any pointers davidv - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-492) Fix mmld taglib discovery strategy for Ant compatibility
Fix mmld taglib discovery strategy for Ant compatibility Key: MNG-492 URL: http://jira.codehaus.org/browse/MNG-492 Project: Maven 2 Type: Bug Components: maven-plugins Versions: 2.0-alpha-2 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 is not configured when m2 attempts to execute a marmalade-mojo. This means that the Ant functionality will never be recognized. I'm going to try to get a stop-gap fix in place for the next release of m2 that will fix this shortcoming. Once that's done, you should be able to: 1. declare the ant namespace using mojo xmlns:ant=ant:ant 2. add a project dependency on: dependency groupIdmarmalade/groupId artifactIdmarmalade-compat-ant/artifactId version1.0-alpha-3/version /dependency -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 would be beneficial for everyone to be working together, and getting the full picture. I also anticipate that the user list can field both m1 and m2 questions. We'll do this counting a majority in 24 hours. [ ] +1, move all m2-dev mails back to [EMAIL PROTECTED] [ ] +0 [ ] -1, Keep them seperate (give reasons) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
