[jira] Commented: (MNG-710) Add ability to fork the maven-compiler-plugin

[ http://jira.codehaus.org/browse/MNG-710?page=comments#action_52044 ] Mark Proctor commented on MNG-710: -- Will this allow different java versions to be specified on a per module basis, in a multi module build? > Add ability to fork the maven-compiler-plug

[REPOCLEAN] Error(s) occurred while converting repository

Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/26-Nov-2005_12.30.30/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTE

[jira] Closed: (MEV-236) saaj-impl-1.2.1

[ http://jira.codehaus.org/browse/MEV-236?page=all ] Carlos Sanchez closed MEV-236: -- Assign To: Carlos Sanchez Resolution: Fixed I've added the pom for com.sun.xml saaj-impl 1.2.1_01, included in wsdp 1.6 and the one available for download versi

[jira] Closed: (MEV-235) saaj-1.2.1

[ http://jira.codehaus.org/browse/MEV-235?page=all ] Carlos Sanchez closed MEV-235: -- Assign To: Carlos Sanchez Resolution: Won't Fix The api is probably 1.2 (the one included in wsdp 1.6 is), the implementation may have changed > saaj-1.2.1 > --

[jira] Closed: (MEV-237) Sun artifactId naming mess

[ http://jira.codehaus.org/browse/MEV-237?page=all ] Carlos Sanchez closed MEV-237: -- Assign To: Carlos Sanchez Resolution: Fixed apis renamed to -api implementations moved to com.sun > Sun artifactId naming mess > -- > >

[jira] Updated: (MNG-1479) Improve pom annotations to create a great reference

[ http://jira.codehaus.org/browse/MNG-1479?page=all ] Jeff Jensen updated MNG-1479: - Attachment: MNG1479-1.patch Added a little info to descriptions for: - packaging element - relativePath - scope (added "system" to types list) - systemPath > Improve po

[jira] Commented: (MNG-1471) Module paths for system scope are relative to parent pom instead of its own

[ http://jira.codehaus.org/browse/MNG-1471?page=comments#action_52037 ] Jeff Jensen commented on MNG-1471: -- Brett, in your comment on 09/Nov/05, you say "systemPathwill acutally be rendered obsolete in 2.1". What is the planned feature that replaces th

[REPOCLEAN] Error(s) occurred while converting repository

Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/25-Nov-2005_08.31.13/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTE

[jira] Commented: (MEV-237) Sun artifactId naming mess

[ http://jira.codehaus.org/browse/MEV-237?page=comments#action_52036 ] Carlos Sanchez commented on MEV-237: jaxb-api -> javax.xml other jaxb jars -> com.sun.jaxb > Sun artifactId naming mess > -- > > Key: MEV-237 >

[jira] Closed: (MNG-1681) maven-rar-plugin can not install the generated rar file to the local repository

[ http://jira.codehaus.org/browse/MNG-1681?page=all ] Edwin Punzalan closed MNG-1681: --- Resolution: Fixed Fix Version: 2.0.1 Patch applied. Thanks! > maven-rar-plugin can not install the generated rar file to the local > repository > --

[maven2 build - SUCCESS - checkout] Sat Nov 26 00:15:04 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051126.001505.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051126.001505.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

[jira] Updated: (MNG-1682) Plugins do not honor the correct extension when run as a part of a multiproject build

[ http://jira.codehaus.org/browse/MNG-1682?page=all ] Brett Porter updated MNG-1682: -- Fix Version: 2.0.1 > Plugins do not honor the correct extension when run as a part of a > multiproject build > ---

Re: svn commit: r349047 - /maven/maven-1/plugins/trunk/announcement/plugin.jelly

I think you still need to rollback the other parts othat commit, sa they are what would be problematic: > > value="${stringUtils.replace(maven.announcement.mail.subject, '%VERSION%', versionVariable)}"/> [EMAIL PROTECTED] wrote: > Author: ltheussl > Date: Fri Nov 25 16:28:34 2005 > New Revis

[jira] Commented: (MNG-1643) Provide installer support like NSIS or InnoSetup

[ http://jira.codehaus.org/browse/MNG-1643?page=comments#action_52031 ] Brett Porter commented on MNG-1643: --- most likely - I haven't investigated the options but I had in mind if you could in affect cross compile a unix installer on windows (say, install a

[jira] Closed: (MEV-233) JSTL should list jsp-api as scope=provided

[ http://jira.codehaus.org/browse/MEV-233?page=all ] Brett Porter closed MEV-233: Resolution: Fixed reran it and has updated at the source > JSTL should list jsp-api as scope=provided > -- > > Key: MEV-2

[jira] Reopened: (MEV-233) JSTL should list jsp-api as scope=provided

[ http://jira.codehaus.org/browse/MEV-233?page=all ] Carlos Sanchez reopened MEV-233: Assign To: Brett Porter (was: Edwin Punzalan) There's a new update mechanism that was put in place lately Brett? > JSTL should list jsp-api as scope=provided >

Re: svn commit: r349037 - /maven/maven-1/plugins/trunk/announcement/plugin.jelly

I was thinking about this thread: http://www.mail-archive.com/dev@maven.apache.org/msg44176.html and thought I'd be on the safer side with maven:get. I didn't know about the problem with dots, I'll revert my commit. Thanks for the watch-out! -Lukas Arnaud HERITIER wrote: In theory if you

[jira] Commented: (MNG-1674) configure test-jar to include only special classes of the test source

[ http://jira.codehaus.org/browse/MNG-1674?page=comments#action_52028 ] Brett Porter commented on MNG-1674: --- added ability to link, and yes thats the related issue I was referring to. > configure test-jar to include only special classes of the test source

Re: download report was: svn commit: r322514

Thanks! Vincent Siveton wrote: > Hi Brett, > >> Vincent Siveton wrote: Can we move it to the sandbox, then talk about what information to add to the POM to make it effective? Perhaps elaboration next to >> downloadUrl in distributionManagement. >>> +1 >> Hi Vincent, >> >> Were you

Re: Maven 1.x Repository

Yes, but that's what's intended. You can't navigate it in the old layout, but old layout URLs will translate correctly. However, I discovered that Maven 1.0 and Maven 1.1 are both choking on the cross host redirects, so I'll need to look into that. That won't affect the final solution, but certain

Re: svn commit: r349037 - /maven/maven-1/plugins/trunk/announcement/plugin.jelly

In theory if you are reading properties in the current plugin you don't need to use maven:get You can access to them with ${my.property} But be careful it works only with properties for the current plugin If you need to create a new variable in your script you musn't use dots (.) in its name. Arn

Re: svn commit: r349037 - /maven/maven-1/plugins/trunk/announcement/plugin.jelly

Lukas, Are you sure this works? Dotted vars generally get treated as object references when used like below, I thought, and the blow is actually longer :) maven:get was really meant to peek and poke other plugins, not itself. Cheers, Brett [EMAIL PROTECTED] wrote: > Author: ltheussl > Date: Fri

[jira] Commented: (MPCLOVER-50) Add support for span

[ http://jira.codehaus.org/browse/MPCLOVER-50?page=comments#action_52025 ] Arnaud Heritier commented on MPCLOVER-50: - You can send us a patch but I'll wait for an opinion from Vincent before to apply it. > Add support for span >

Re: svn commit: r348837 - in /maven/maven-1/plugins/trunk/xdoc: project.xml xdocs/changes.xml

It only fails with 'maven announcement' but not with 'maven announcement:generate-all' which is called by xdoc for the downloads page. I'm on my way... -Lukas Arnaud HERITIER wrote: No idea in mind. I never saw this :-( Good hunt !! :-( Arnaud -Message d'origine- De : Lukas T

[jira] Created: (MNG-1687) Improved the default description that is used when no description is supplied in the pom

Improved the default description that is used when no description is supplied in the pom Key: MNG-1687 URL: http://jira.codehaus.org/browse/MNG-1687 Project: Maven 2 Type: Impro

RE: svn commit: r348837 - in /maven/maven-1/plugins/trunk/xdoc: project.xml xdocs/changes.xml

No idea in mind. I never saw this :-( Good hunt !! :-( Arnaud > -Message d'origine- > De : Lukas Theussl [mailto:[EMAIL PROTECTED] > Envoyé : vendredi 25 novembre 2005 22:53 > À : Maven Developers List > Objet : Re: svn commit: r348837 - in > /maven/maven-1/plugins/trunk/xdoc: projec

Re: svn commit: r348837 - in /maven/maven-1/plugins/trunk/xdoc: project.xml xdocs/changes.xml

I thought so, but when I remove the version entry, the announcement goal fails like: BUILD FAILED File.. /home/lukas/.maven/cache/maven-announcement-plugin-1.4-SNAPSHOT/plugin.jelly Element... ant:fail Line.. 102 Column -1 Missing "version" element in the POM for release 1.10-SNAP

[jira] Created: (MNG-1686) Updates to the site, in particular introduction-to-repositories

Updates to the site, in particular introduction-to-repositories --- Key: MNG-1686 URL: http://jira.codehaus.org/browse/MNG-1686 Project: Maven 2 Type: Improvement Components: documentation - introductions

[REPOCLEAN] Error(s) occurred while converting repository

Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/25-Nov-2005_04.31.02/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTE

RE: svn commit: r348837 - in /maven/maven-1/plugins/trunk/xdoc: project.xml xdocs/changes.xml

Hi Lukas, We never manually add version entries in the pom. It's automatically done when you release a plugin. Arnaud > -Message d'origine- > De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Envoyé : vendredi 25 novembre 2005 01:03 > À : commits@maven.apache.org > Obje

[jira] Commented: (MPSIMIAN-11) Includes/excludes pattern does not support multiple patterns

[ http://jira.codehaus.org/browse/MPSIMIAN-11?page=comments#action_52024 ] Arnaud Heritier commented on MPSIMIAN-11: - you can download the 1.6-snapshot if you want to test it. > Includes/excludes pattern does not support multiple patterns > -

[jira] Closed: (MNG-1685) NPE in release:prepare

[ http://jira.codehaus.org/browse/MNG-1685?page=all ] Emmanuel Venisse closed MNG-1685: - Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 2.0.1 Fixed. > NPE in release:prepare > -- > > Key: MNG-1685

Re: release:prepare broken

Fixed. Mike Perham a écrit : http://jira.codehaus.org/browse/MPRELEASE-15

[jira] Commented: (MNG-1562) Exception with dependencies that have and implied from parents

[ http://jira.codehaus.org/browse/MNG-1562?page=comments#action_52021 ] Arik Kfir commented on MNG-1562: Then I get this (error relates to POM_EAR): [EMAIL PROTECTED]:~/projects/crm/trunk$ mvn clean package [INFO] Scanning for projects... [INFO] ---

[jira] Commented: (SCM-79) Add remaining operations to Perforce provider

[ http://jira.codehaus.org/browse/SCM-79?page=comments#action_52019 ] mike perham commented on SCM-79: I'm finding that I'm being blocked by various release issues which are hampering full integration testing. Attached is my first pass at implementing all

[jira] Updated: (SCM-79) Add remaining operations to Perforce provider

[ http://jira.codehaus.org/browse/SCM-79?page=all ] mike perham updated SCM-79: --- Attachment: perforce.zip Zip of contents of maven-scm-provider-perforce. You should be able to unzip this on top of your existing perforce project, add the files and check them

[jira] Updated: (MNG-1685) NPE in release:prepare

[ http://jira.codehaus.org/browse/MNG-1685?page=all ] Lukas Theussl updated MNG-1685: --- Component: maven-release-plugin > NPE in release:prepare > -- > > Key: MNG-1685 > URL: http://jira.codehaus.org/browse/MNG-1685 >

[jira] Moved: (MNG-1685) NPE in release:prepare

[ http://jira.codehaus.org/browse/MNG-1685?page=all ] Lukas Theussl moved MPRELEASE-15 to MNG-1685: - Complexity: Intermediate Workflow: Maven (was: jira) Key: MNG-1685 (was: MPRELEASE-15) Project: Maven 2 (was: maven

release:prepare broken

http://jira.codehaus.org/browse/MPRELEASE-15

[jira] Created: (MPRELEASE-15) NPE in release:prepare

NPE in release:prepare -- Key: MPRELEASE-15 URL: http://jira.codehaus.org/browse/MPRELEASE-15 Project: maven-release-plugin Type: Bug Reporter: mike perham I believe this is due to a recent change to support multi-module builds: java.lang.N

[jira] Commented: (MEV-237) Sun artifactId naming mess

[ http://jira.codehaus.org/browse/MEV-237?page=comments#action_52015 ] Carlos Sanchez commented on MEV-237: > This does not even apply for the standalone packages from Sun. E.g. SAAJ > (http://java.sun.com/xml/downloads/saaj.html) is called saaj-1_2-fr-a

[jira] Commented: (MEV-232) DWR POM should list dependencies as optional

[ http://jira.codehaus.org/browse/MEV-232?page=comments#action_52014 ] Carlos Sanchez commented on MEV-232: Julien, would you say for 1.0 which of them are optional and what not? > DWR POM should list dependencies as optional > --

[jira] Created: (MAVENUPLOAD-609) maven taglib plugin 1.4.2 for maven 1

maven taglib plugin 1.4.2 for maven 1 - Key: MAVENUPLOAD-609 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-609 Project: maven-upload-requests Type: Task Reporter: fabrizio giustina -- This message is automatically gener

[jira] Commented: (MNG-1683) type zip for packaging ?

[ http://jira.codehaus.org/browse/MNG-1683?page=comments#action_52013 ] Olivier Lamy commented on MNG-1683: --- Hi, If you are interested, I can provide a maven-zip-plugin. For the moment, I provided his own lifecycle defined in his own META-INF/plexus/compon

Re: [vote] 2.0.1/2.1 dev process

Brett Porter wrote, On 11/24/2005 4:23 PM: My thoughts: - this is more risky that it will be missed if someone misses one This is not as likely if the commits are made to both lines at the same time. Also, there will be times when it will not make sense to apply the branch change in the tr

[jira] Closed: (MNG-1669) war-plugin feature

[ http://jira.codehaus.org/browse/MNG-1669?page=all ] Olivier Lamy closed MNG-1669: - Resolution: Duplicate Not apply patch. A bigger one will be provided with issue MNG-1683 > war-plugin feature > -- > > Key: MNG-1669 >

[jira] Commented: (MNG-1558) Manifest generation problems caused by valid POM information

[ http://jira.codehaus.org/browse/MNG-1558?page=comments#action_52009 ] Michal Stochmialek commented on MNG-1558: - I also had some problems connected with this issue. I had problems while running tests. Surefire was throwning NoClassDefFound for cla

[jira] Commented: (MEV-233) JSTL should list jsp-api as scope=provided

[ http://jira.codehaus.org/browse/MEV-233?page=comments#action_52008 ] Matt Raible commented on MEV-233: - Hmmm, it's been 15 hours and still no sign up an updated POM at http://www.ibiblio.org/maven2/javax/servlet/jstl/1.1.2/jstl-1.1.2.pom. > JSTL should li

[jira] Commented: (MNG-1643) Provide installer support like NSIS or InnoSetup

[ http://jira.codehaus.org/browse/MNG-1643?page=comments#action_52004 ] John Allen commented on MNG-1643: - brett, although i agree with you in terms of better componentisation of the design i cant think of a use case where anyone will want to make more than

[jira] Commented: (MNG-1531) add a report mojo to create a an effective pom and effective settings report (to be used in site generation)

[ http://jira.codehaus.org/browse/MNG-1531?page=comments#action_52003 ] John Allen commented on MNG-1531: - indeed regarding external publication of sensitive data but as many organisations use the maven generated project site to act as the a project's statu

[jira] Closed: (MNG-1360) Polish translation for maven-site-plugin

[ http://jira.codehaus.org/browse/MNG-1360?page=all ] Vincent Siveton closed MNG-1360: Resolution: Fixed Applied in SVN. Thanks > Polish translation for maven-site-plugin > > > Key: MNG-1360 >

RE: download report was: svn commit: r322514

Hi Brett, > Vincent Siveton wrote: > >> Can we move it to the sandbox, then talk about what information to add > >> to the POM to make it effective? Perhaps elaboration next to > downloadUrl > >> in distributionManagement. > > > > +1 > > Hi Vincent, > > Were you going to make this move? I'd like

[jira] Created: (MNG-1684) Problem with reactor when using attached goal

Problem with reactor when using attached goal - Key: MNG-1684 URL: http://jira.codehaus.org/browse/MNG-1684 Project: Maven 2 Type: Bug Components: maven-assembly-plugin Versions: 2.0 Reporter: Vincent Massol

[REPOCLEAN] Error(s) occurred while converting repository

Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/25-Nov-2005_08.32.21/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTE

Re: using ant within maven 2

Michael Wechner wrote: Hi What is the recommended way to use Ant within the Maven 2 Framework? Is there for instance an Ant plugin? http://maven.apache.org/plugins/maven-antrun-plugin/ http://maven.apache.org/guides/mini/guide-using-ant.html Please apologize if these questions might have be

[jira] Created: (MNG-1683) type zip for packaging ?

type zip for packaging ? Key: MNG-1683 URL: http://jira.codehaus.org/browse/MNG-1683 Project: Maven 2 Type: Improvement Environment: not significant Reporter: Olivier Lamy Hi, I don't know if the artifact type zip exists (I think not a

[jira] Updated: (MNG-1632) mvn.bat does not properly return the exit code of the java process

[ http://jira.codehaus.org/browse/MNG-1632?page=all ] David Hawkins updated MNG-1632: --- Attachment: MNG-1632-maven-core-2.patch Sorry for taking so long to respond on this. I have created a new patch, "MNG-1632-maven-core-2.patch", which handles the MAVEN

using ant within maven 2

Hi What is the recommended way to use Ant within the Maven 2 Framework? Is there for instance an Ant plugin? Please apologize if these questions might have been asked before, but I am bit confused if I read the Maven 2 website about this topic. Thanks Michi

[jira] Created: (MNG-1682) Plugins do not honor the correct extension when run as a part of a multiproject build

Plugins do not honor the correct extension when run as a part of a multiproject build - Key: MNG-1682 URL: http://jira.codehaus.org/browse/MNG-1682 Project: Maven 2 Type: Bug Compo

Re: [jira] Commented: (SCM-80) [patch] update for the release and clearcase plugins

Thanks, it's ok now. I do not have a project with modules. I would be nice if there was some simple project to test with. Maybe someone should create a archetype of a project with modules so we have something to test with? regards, Wim2005/11/25, Emmanuel Venisse <[EMAIL PROTECTED]>: You have a

[jira] Commented: (MEV-232) DWR POM should list dependencies as optional

[ http://jira.codehaus.org/browse/MEV-232?page=comments#action_51986 ] Julien Dubois commented on MEV-232: --- FYI, this issue is also tracked in the DWR issue tracker at : https://dwr.dev.java.net/issues/show_bug.cgi?id=95 > DWR POM should list dependencies

Re: [jira] Commented: (SCM-80) [patch] update for the release and clearcase plugins

if you can test with a simple project and with a project with modules, it will be great. Emmanuel Wim Deblauwe a écrit : Sure, do you have an example project with modules that I can test? Wim 2005/11/25, Emmanuel Venisse <[EMAIL PROTECTED] >: Wim, Can yo

Re: Maven 1.x Repository

Brett Porter wrote: We've set up for testing the following repository for Maven 1.x users: http://repo1.maven.org/maven This maps directly onto the Maven 2 repository, converting the layout on the fly. Being able to do this will reduce the amount of maintenance required and ensure libraries arr

[jira] Updated: (MNG-1630) Optional tag in dependencyManagement is not inherited in the children projects

[ http://jira.codehaus.org/browse/MNG-1630?page=all ] Edwin Punzalan updated MNG-1630: Attachment: MNG-1630-maven-project.patch > Optional tag in dependencyManagement is not inherited in the children projects > ---

[jira] Commented: (MNG-1632) mvn.bat does not properly return the exit code of the java process

[ http://jira.codehaus.org/browse/MNG-1632?page=comments#action_51980 ] Emmanuel Venisse commented on MNG-1632: --- Can you add a test on %MAVEN_TERMINATE_CMD%? if it's true, you must exit without /B We need it when we run mvn from a java process. > mvn.

[jira] Commented: (MEV-232) DWR POM should list dependencies as optional

[ http://jira.codehaus.org/browse/MEV-232?page=comments#action_51979 ] Julien Dubois commented on MEV-232: --- I'm the guy doing the DWR pom. We are indeed preparing a Maven 2 pom, as Carlos pointed out, which will be ready for DWR 1.1. If you want to use it

[jira] Commented: (SCM-80) [patch] update for the release and clearcase plugins

[ http://jira.codehaus.org/browse/SCM-80?page=comments#action_51978 ] Wim Deblauwe commented on SCM-80: - Thanks a million Emmanuel! > [patch] update for the release and clearcase plugins > > > Ke

[jira] Commented: (MEV-237) Sun artifactId naming mess

[ http://jira.codehaus.org/browse/MEV-237?page=comments#action_51977 ] Joerg Schaible commented on MEV-237: Needed some time to find it also: http://java.sun.com/webservices/archive.html See the versions.txt in the root of the installation (and compare wi

[jira] Closed: (MEV-225) Replace wrong surefire plugin name in poms

[ http://jira.codehaus.org/browse/MEV-225?page=all ] Edwin Punzalan closed MEV-225: -- Resolution: Fixed > Replace wrong surefire plugin name in poms > -- > > Key: MEV-225 > URL: http://jira.codeh

[jira] Updated: (MNG-1525) Allow environment variables to be referenced in pom.xml, settings.xml, etc.

[ http://jira.codehaus.org/browse/MNG-1525?page=all ] Edwin Punzalan updated MNG-1525: Attachment: MNG-1525-maven-project.patch > Allow environment variables to be referenced in pom.xml, settings.xml, etc. > --

[jira] Updated: (MNG-1630) Optional tag in dependencyManagement is not inherited in the children projects

[ http://jira.codehaus.org/browse/MNG-1630?page=all ] Edwin Punzalan updated MNG-1630: Attachment: MNG-1630-maven-artifact.patch > Optional tag in dependencyManagement is not inherited in the children projects > --

[jira] Updated: (MNG-1630) Optional tag in dependencyManagement is not inherited in the children projects

[ http://jira.codehaus.org/browse/MNG-1630?page=all ] Edwin Punzalan updated MNG-1630: Attachment: (was: MNG-1630-maven-artifact.patch) > Optional tag in dependencyManagement is not inherited in the children projects > ---

[jira] Updated: (MNG-1630) Optional tag in dependencyManagement is not inherited in the children projects

[ http://jira.codehaus.org/browse/MNG-1630?page=all ] Edwin Punzalan updated MNG-1630: Attachment: MNG-1630-maven-artifact.patch Please see attached patch... > Optional tag in dependencyManagement is not inherited in the children projects >