[jira] Updated: (MEV-355) Missing deps in jboss-common 4.0.2
[ http://jira.codehaus.org/browse/MEV-355?page=all ] Yann Le Du updated MEV-355: --- Attachment: jboss-common-4.0.2.pom > Missing deps in jboss-common 4.0.2 > -- > > Key: MEV-355 > URL: http://jira.codehaus.org/browse/MEV-355 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Yann Le Du > Attachments: jboss-common-4.0.2.pom > > > Index: jboss-common-4.0.2.pom > === > --- jboss-common-4.0.2.pom (révision 321) > +++ jboss-common-4.0.2.pom (copie de travail) > @@ -1,6 +1,32 @@ > - > + >4.0.0 >jboss >jboss-common > + jar > + JBoss Common >4.0.2 > + JBoss common framework. > + http://www.jboss.com/ > + > + > + GNU Lesser General Public License > + http://www.gnu.org/licenses/lgpl.txt > + repo > + > + > + > +http://anoncvs.forge.jboss.com/viewrep/JBoss/jboss-common > + > + > + > + slide > + webdavlib > + 2.0 > + > + > + xerces > + xercesImpl > + 2.6.2 > + > + > -- 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] Created: (MEV-356) Missing dep on jboss-common in jbossmq-client & jnp-client 4.0.2
Missing dep on jboss-common in jbossmq-client & jnp-client 4.0.2
Key: MEV-356
URL: http://jira.codehaus.org/browse/MEV-356
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: Yann Le Du
Since svn://svn.codehaus.org/maven/scm/repository/ is not up-to-date yet, I
cannot make a diff. The patch is to add the following in both jbossmq-client &
jnp-client POMs :
{code:xml}
jboss
jboss-common
4.0.2
{code}
--
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] Created: (MEV-355) Missing deps in jboss-common 4.0.2
Missing deps in jboss-common 4.0.2 -- Key: MEV-355 URL: http://jira.codehaus.org/browse/MEV-355 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Yann Le Du Index: jboss-common-4.0.2.pom === --- jboss-common-4.0.2.pom (révision 321) +++ jboss-common-4.0.2.pom (copie de travail) @@ -1,6 +1,32 @@ - + 4.0.0 jboss jboss-common + jar + JBoss Common 4.0.2 + JBoss common framework. + http://www.jboss.com/ + + + GNU Lesser General Public License + http://www.gnu.org/licenses/lgpl.txt + repo + + + +http://anoncvs.forge.jboss.com/viewrep/JBoss/jboss-common + + + + slide + webdavlib + 2.0 + + + xerces + xercesImpl + 2.6.2 + + -- 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: (MAVENUPLOAD-764) Please upload jbossha 4.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-764?page=comments#action_60289 ] Yann Le Du commented on MAVENUPLOAD-764: Thanks Carlos for the graph. I've made the following corrections (the bundles are up-to-date) : MAVENUPLOAD-764 (this one) for jbossha 4.0.2 : added dep on jgroups-all 2.2.7 MAVENUPLOAD-763 for jboss-j2ee 4.0.0 : added dep on jboss-common 4.0.0, for which I've created another bundle : http://yann.le.du.free.fr/maven/jboss-common-4.0.0-bundle.jar MAVENUPLOAD-762 for jboss-client 4.0.2 : following your graph, I should add a dep on tomcat55-service, but I'm not sure about this one, I believe it is only used for deployment I will also create MEV issues to correct other bundles I've uploaded. > Please upload jbossha 4.0.2 > --- > > Key: MAVENUPLOAD-764 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-764 > Project: maven-upload-requests > Type: Task > Reporter: Yann Le Du > Attachments: dep.png > > > This is JBoss High Availability and Clustering. -- 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] Created: (MAVENUPLOAD-764) Please upload jbossha 4.0.2
Please upload jbossha 4.0.2 --- Key: MAVENUPLOAD-764 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-764 Project: maven-upload-requests Type: Task Reporter: Yann Le Du This is JBoss High Availability and Clustering. -- 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: (MAVENUPLOAD-763) Please upload jboss-j2ee 4.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-763?page=comments#action_59838 ] Yann Le Du commented on MAVENUPLOAD-763: Erratum in description, this is jboss-j2ee 4.0.0 as stated in the bundle name > Please upload jboss-j2ee 4.0.2 > -- > > Key: MAVENUPLOAD-763 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-763 > Project: maven-upload-requests > Type: Task > Reporter: Yann Le Du > > > This is JBoss J2EE Implementation. -- 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] Created: (MAVENUPLOAD-763) Please upload jboss-j2ee 4.0.2
Please upload jboss-j2ee 4.0.2 -- Key: MAVENUPLOAD-763 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-763 Project: maven-upload-requests Type: Task Reporter: Yann Le Du This is JBoss J2EE Implementation. -- 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] Created: (MAVENUPLOAD-762) Please upload jboss-client 4.0.2
Please upload jboss-client 4.0.2 Key: MAVENUPLOAD-762 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-762 Project: maven-upload-requests Type: Task Reporter: Yann Le Du This is JBoss Application Server Client JBoss Application Server is a J2EE certified platform for developing and deploying enterprise Java applications, Web applications, and Portals. It provides the full range of J2EE 1.4 features as well as extended enterprise services including clustering, caching, and persistence. -- 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-2099) Anchors in http://maven.apache.org/maven-model/maven.html are broken
[ http://jira.codehaus.org/browse/MNG-2099?page=comments#action_59362 ] Yann Le Du commented on MNG-2099: - I don't get the problem with doxia trunk - anchors are correct. Maybe it's already corrected ?? Would it solve http://maven.apache.org/maven-model/maven.html also ? (I don't know how this page is generated from model) > Anchors in http://maven.apache.org/maven-model/maven.html are broken > > > Key: MNG-2099 > URL: http://jira.codehaus.org/browse/MNG-2099 > Project: Maven 2 > Type: Bug > Components: Documentation: General > Versions: 2.0.2 > Reporter: Yann Le Du > Priority: Minor > > > Anchors in http://maven.apache.org/maven-model/maven.html should be (e.g.) : > > instead of > -- 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-2099) Anchors in http://maven.apache.org/maven-model/maven.html are broken
[ http://jira.codehaus.org/browse/MNG-2099?page=comments#action_59355 ] Yann Le Du commented on MNG-2099: - I've noticed the same thing in FAQs, e.g. http://maven.apache.org/general.html Am I wrong or is it a problem with FML ? There is no # for name in HTML specs : http://www.w3.org/TR/html4/struct/links.html#edef-A > Anchors in http://maven.apache.org/maven-model/maven.html are broken > > > Key: MNG-2099 > URL: http://jira.codehaus.org/browse/MNG-2099 > Project: Maven 2 > Type: Bug > Components: Documentation: General > Versions: 2.0.2 > Reporter: Yann Le Du > Priority: Minor > > > Anchors in http://maven.apache.org/maven-model/maven.html should be (e.g.) : > > instead of > -- 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] Updated: (MNG-2103) Inheritance of overrides that of
[ http://jira.codehaus.org/browse/MNG-2103?page=all ] Yann Le Du updated MNG-2103: Attachment: test-inheritance-true.zip > Inheritance of overrides that of > - > > Key: MNG-2103 > URL: http://jira.codehaus.org/browse/MNG-2103 > Project: Maven 2 > Type: Bug > Reporter: Prasad Kashyap > Attachments: test-inheritance-true.zip, test-inheritance.zip > > > The settings of overrides that of it's > By convention, all top level configuration settings are usually overridden by > the settings in the lower levels. -- 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-2103) Inheritance of overrides that of
[ http://jira.codehaus.org/browse/MNG-2103?page=comments#action_59235 ] Yann Le Du commented on MNG-2103: - Hmm... In this case, I would understand the false as "don't inherit whatever is in ". So, in modules, is not inherited and both don't even exist. What do you think ? You can visualize that by running mvn help:effective-pom in parent project. > Inheritance of overrides that of > - > > Key: MNG-2103 > URL: http://jira.codehaus.org/browse/MNG-2103 > Project: Maven 2 > Type: Bug > Reporter: Prasad Kashyap > Attachments: test-inheritance.zip > > > The settings of overrides that of it's > By convention, all top level configuration settings are usually overridden by > the settings in the lower levels. -- 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] Created: (MNG-2099) Anchors in http://maven.apache.org/maven-model/maven.html are broken
Anchors in http://maven.apache.org/maven-model/maven.html are broken Key: MNG-2099 URL: http://jira.codehaus.org/browse/MNG-2099 Project: Maven 2 Type: Bug Components: Documentation: General Versions: 2.0.2 Reporter: Yann Le Du Priority: Minor Anchors in http://maven.apache.org/maven-model/maven.html should be (e.g.) : instead of -- 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: (MAVENUPLOAD-735) Please upload com.sun.xml:xalan 1.0.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-735?page=comments#action_58331 ] Yann Le Du commented on MAVENUPLOAD-735: 1.0.4 is the reference implementation version of JWSDP 1.5 : http://java.sun.com/webservices/docs/1.5/jaxb/ReleaseNotes.html (hence jax-impl, jaxb-libs and jaxb-xjc 1.0.4) This xalan is a lib endorsed in the JWSDP and is different from original xalan (it contains a com.sun package). So I thought storing it with group com.sun.xml and version 1.0.4 would be a good way to identify it. This is the same for xercesImpl in MAVENUPLOAD-736 > Please upload com.sun.xml:xalan 1.0.4 > - > > Key: MAVENUPLOAD-735 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-735 > Project: maven-upload-requests > Type: Task > Reporter: Yann Le Du > > > Part of the Java Web Services Developer Pack 1.5 > Bundle contains only the pom, JWSDP must be retrieved manually -- 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: (MAVENUPLOAD-725) Please upload displaytag 12 tld
[ http://jira.codehaus.org/browse/MAVENUPLOAD-725?page=comments#action_58329 ] Yann Le Du commented on MAVENUPLOAD-725: displaytag-1.0 (the jar, that also contains the tld in META-INF) can be downloaded at http://sourceforge.net/project/showfiles.php?group_id=73068&package_id=73060&release_id=293702 At first, I also thought the group should be displaytag but having 1.0 (jar) along 12 (tld) was potentially confusing. We could have group displaytag, but then we should use another artifactId for tld, as for Struts : http://www.ibiblio.org/maven2/struts/ (struts is jar, struts-bean and so on are tld) The idea of storing tld apart from jar is to have a dependency on the tld so that it is automatically retrieved it into webapp's WEB-INF/tld. The tld stored in jar's META-INF is not usable by Maven. > Please upload displaytag 12 tld > --- > > Key: MAVENUPLOAD-725 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-725 > Project: maven-upload-requests > Type: Task > Reporter: Yann Le Du > > > This is the tld distributed with displaytag 1.0 as displaytag-12.tld > I propose to store it as taglibs:displaytag:12 -- 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] Created: (MAVENUPLOAD-738) Please upload jnp-client 4.0.2
Please upload jnp-client 4.0.2 -- Key: MAVENUPLOAD-738 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-738 Project: maven-upload-requests Type: Task Reporter: Yann Le Du Part of JBoss application server 4.0.2 -- 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] Created: (MAVENUPLOAD-737) Please upload jbossmq-client 4.0.2
Please upload jbossmq-client 4.0.2 -- Key: MAVENUPLOAD-737 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-737 Project: maven-upload-requests Type: Task Reporter: Yann Le Du Part of JBoss application server 4.0.2 -- 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] Created: (MAVENUPLOAD-736) Please upload com.sun.xml:xercesImpl 1.0.4
Please upload com.sun.xml:xercesImpl 1.0.4 -- Key: MAVENUPLOAD-736 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-736 Project: maven-upload-requests Type: Task Reporter: Yann Le Du Part of the Java Web Services Developer Pack 1.5 Bundle contains only the pom, JWSDP must be retrieved manually -- 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] Created: (MAVENUPLOAD-735) Please upload com.sun.xml:xalan 1.0.4
Please upload com.sun.xml:xalan 1.0.4 - Key: MAVENUPLOAD-735 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-735 Project: maven-upload-requests Type: Task Reporter: Yann Le Du Part of the Java Web Services Developer Pack 1.5 Bundle contains only the pom, JWSDP must be retrieved manually -- 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] Created: (MAVENUPLOAD-734) Please upload jaxb-xjc 1.0.4
Please upload jaxb-xjc 1.0.4 Key: MAVENUPLOAD-734 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-734 Project: maven-upload-requests Type: Task Reporter: Yann Le Du Part of the Java Web Services Developer Pack 1.5 Bundle contains only the pom, JWSDP must be retrieved manually -- 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] Created: (MAVENUPLOAD-733) Please upload jaxb-libs 1.0.4
Please upload jaxb-libs 1.0.4 - Key: MAVENUPLOAD-733 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-733 Project: maven-upload-requests Type: Task Reporter: Yann Le Du Part of the Java Web Services Developer Pack 1.5 Bundle contains only the pom, JWSDP must be retrieved manually -- 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] Created: (MAVENUPLOAD-732) Please upload jaxb-impl 1.0.4
Please upload jaxb-impl 1.0.4 - Key: MAVENUPLOAD-732 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-732 Project: maven-upload-requests Type: Task Reporter: Yann Le Du Part of the Java Web Services Developer Pack 1.5 Bundle contains only the pom, JWSDP must be retrieved manually -- 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] Created: (MEV-325) Description of jaxb-api 1.0.1 is wrong
Description of jaxb-api 1.0.1 is wrong -- Key: MEV-325 URL: http://jira.codehaus.org/browse/MEV-325 Project: Maven Evangelism Type: Bug Reporter: Yann Le Du Index: jaxb-api-1.0.1.pom === --- jaxb-api-1.0.1.pom (révision 271) +++ jaxb-api-1.0.1.pom (copie de travail) @@ -5,7 +5,7 @@ 1.0.1 Java Architecture for XML Binding -Part of the Java Web Services Developer Pack 1.6 +Part of the Java Web Services Developer Pack 1.5 http://java.sun.com/webservices/jaxb/index.jsp -- 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] Created: (MAVENUPLOAD-725) Please upload displaytag 12 tld
Please upload displaytag 12 tld --- Key: MAVENUPLOAD-725 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-725 Project: maven-upload-requests Type: Task Reporter: Yann Le Du This is the tld distributed with displaytag 1.0 as displaytag-12.tld I propose to store it as taglibs:displaytag:12 -- 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: (CONTINUUM-256) trace memory leak with yourkit
[ http://jira.codehaus.org/browse/CONTINUUM-256?page=comments#action_57130 ] Yann Le Du commented on CONTINUUM-256: -- If it can help : I made a few tests on our server. We currently have about 70 M2 projects on Continuum. Running the builds causes no memory leak. But, oftenly, when you click on 'Show projects', the JVM takes some tenths of Mo that are never given back, until it comes to the -Xmx. > trace memory leak with yourkit > -- > > Key: CONTINUUM-256 > URL: http://jira.codehaus.org/browse/CONTINUUM-256 > Project: Continuum > Type: Bug > Components: Core system > Reporter: Brett Porter > Fix For: 1.1 > > > continuum has been spitting OOME in our test environment -- 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
[jira] Created: (MNG-2006) Module SCM URL is resolved as [...]/parent/module regardless of relativePath
Module SCM URL is resolved as [...]/parent/module regardless of relativePath Key: MNG-2006 URL: http://jira.codehaus.org/browse/MNG-2006 Project: Maven 2 Type: Bug Components: Inheritence and Interpolation Versions: 2.0.2 Environment: Maven 2.0.2 Continuum 1.0.2 with maven-scm-*-1.0-beta-3-20060115.041342-*.jar Reporter: Yann Le Du Quoting Emmanuel Venisse from user list : Ok, it's a bug in http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/inheritance/DefaultModelInheritanceAssembler.java?rev=306518&view=markup in assembleScmInheritance method. This method append parent scm connection url and artifactId without look at relativePath. For detailed description see http://www.nabble.com/-m2-Multiprojects-and-inherited-SCM-URLs-t951105.html Project structure : PROJECT PROJECT/parent PROJECT/parent/pom.xml PROJECT/module PROJECT/module/pom.xml parent/pom.xml : scm:svn:svn://host/PROJECT/parent/ ../module module/pom.xml : ../parent/pom.xml When I add module in Continuum, its url is resolved as : scm:svn:svn://host/PROJECT/parent/module -- 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: (WAGON-30) wagon-file failed when used by maven-site-plugin
[ http://jira.codehaus.org/browse/WAGON-30?page=comments#action_56747 ] Yann Le Du commented on WAGON-30: - Maybe the trick would be to use -p : -p, --parents no error if existing, make parent directories as needed > wagon-file failed when used by maven-site-plugin > > > Key: WAGON-30 > URL: http://jira.codehaus.org/browse/WAGON-30 > Project: wagon > Type: Bug > Versions: 1.0-alpha-6 > Reporter: Gilles Scokart > Assignee: Brett Porter > Fix For: 1.0-alpha-7 > Attachments: wagon-file-1.0-alpha-7-SNAPSHOT.jar, wagon-file.patch, > wagon-provider-test.patch > > > When maven-site-plugin try a deploy on a file URL, an error is triggered. > This is because maven-site-plugin call "wagon.putDirectory( inputDirectory, > "." );" which fails. > See > http://www.nabble.com/With-maven-2.0.2-site%3Adeploy-doesn%27t-work-t934716.html > In attachment, you can find a patch adding a test case, and the patch fixing > the bug. -- 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: (WAGON-30) wagon-file failed when used by maven-site-plugin
[ http://jira.codehaus.org/browse/WAGON-30?page=comments#action_56640 ] Yann Le Du commented on WAGON-30: - Even with the patch, wagon-file fails for directories that don't already exist. If you can, first create required directories then run deploy again. > wagon-file failed when used by maven-site-plugin > > > Key: WAGON-30 > URL: http://jira.codehaus.org/browse/WAGON-30 > Project: wagon > Type: Bug > Versions: 1.0-alpha-6 > Reporter: Gilles Scokart > Attachments: wagon-file-1.0-alpha-7-SNAPSHOT.jar, wagon-file.patch, > wagon-provider-test.patch > > > When maven-site-plugin try a deploy on a file URL, an error is triggered. > This is because maven-site-plugin call "wagon.putDirectory( inputDirectory, > "." );" which fails. > See > http://www.nabble.com/With-maven-2.0.2-site%3Adeploy-doesn%27t-work-t934716.html > In attachment, you can find a patch adding a test case, and the patch fixing > the bug. -- 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] Created: (MNGECLIPSE-38) Please correct update site in http://m2eclipse.codehaus.org/Installing_Maven_2.0_plugin_for_Eclipse.html
Please correct update site in http://m2eclipse.codehaus.org/Installing_Maven_2.0_plugin_for_Eclipse.html Key: MNGECLIPSE-38 URL: http://jira.codehaus.org/browse/MNGECLIPSE-38 Project: Maven 2.x Plug-in for Eclipse Type: Bug Reporter: Yann Le Du Assigned to: Eugene Kuleshov Priority: Minor According to MNGECLIPSE-37, update site has changed. Please correct this in the Flash demo : http://m2eclipse.codehaus.org/Installing_Maven_2.0_plugin_for_Eclipse.html Thx -- 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: (MEV-282) Please relocate jspapi:jsp-api to javax.servlet:jsp-api
[ http://jira.codehaus.org/browse/MEV-282?page=comments#action_55423 ] Yann Le Du commented on MEV-282: Honestly, I don't know about this public draft version (only mere 2.0 is available at Sun's now), but as there already was a 2.0.public_draft in javax.servlet, I thought that one could be relocated as well. > Please relocate jspapi:jsp-api to javax.servlet:jsp-api > --- > > Key: MEV-282 > URL: http://jira.codehaus.org/browse/MEV-282 > Project: Maven Evangelism > Type: Improvement > Reporter: Yann Le Du > Assignee: Edwin Punzalan > > > Since these versions are available in the correct javax.servlet groupId, they > should be relocated, to avoid problems like > http://www.mail-archive.com/users@maven.apache.org/msg31444.html > Please add these lines to the POMs : > > > javax.servlet > jsp-api > > > Thx -- 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] Created: (MEV-282) Please relocate jspapi:jsp-api to javax.servlet:jsp-api
Please relocate jspapi:jsp-api to javax.servlet:jsp-api --- Key: MEV-282 URL: http://jira.codehaus.org/browse/MEV-282 Project: Maven Evangelism Type: Improvement Reporter: Yann Le Du Since these versions are available in the correct javax.servlet groupId, they should be relocated, to avoid problems like http://www.mail-archive.com/users@maven.apache.org/msg31444.html Please add these lines to the POMs : javax.servlet jsp-api Thx -- 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: (CONTINUUM-401) cannot delete project (stuck on 'in progress')
[ http://jira.codehaus.org/browse/CONTINUUM-401?page=comments#action_54773 ] Yann Le Du commented on CONTINUUM-401: -- Using these parameters in continuum/bin/linux/wrapper.conf solved the "out of memory error" for us : ... # Initial Java Heap Size (in MB) wrapper.java.initmemory=64 # Maximum Java Heap Size (in MB) wrapper.java.maxmemory=256 ... About the other cases of restart, it finally seems the cause was a concurrent backup process on our server... So, in conclusion, I'd say we have no more stability problem with 1.0.2. And if any, thanks to CONTINUUM-478, the projects aren't stuck. > cannot delete project (stuck on 'in progress') > -- > > Key: CONTINUUM-401 > URL: http://jira.codehaus.org/browse/CONTINUUM-401 > Project: Continuum > Type: Bug > Versions: 1.0 > Environment: running on linux debian > trying to access from winXP > Reporter: Adam Kiezun > Attachments: palulustuck.JPG, wrapper-2005-11-25.log, wrapper-2005-12-21.log > > > one of my projects got stuck in the 'in progress' state and cannot be deleted > from the web interface. > it's been in this state for > 24 hrs so it seems permanent. > attaching screenshot. > let me know if i should attach a log (and which one) -- 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
[jira] Commented: (MNG-1703) is not propagated to child POMs
[ http://jira.codehaus.org/browse/MNG-1703?page=comments#action_54251 ] Yann Le Du commented on MNG-1703: - Hi Edwin, sorry, I wanted to post yesterday, but JIRA was down. You were right, is inherited. Yet, is not, hence my test failure. Should I close this issue and create another one for ? mvn help:effective-pom gives : ~ ~ ~ ~ maven-antrun-plugin ~ ~ ~ process-resources ~ ~run ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ant ~ ant-nodeps ~ 1.6.5 ~ ~ ~ ~ ~ ~ ~ ~maven-antrun-plugin ~ ~ ~process-resources ~ ~ run ~ ~ ~ ~ ~ ~ ~ ~ ~ > is not propagated to child POMs > -- > > Key: MNG-1703 > URL: http://jira.codehaus.org/browse/MNG-1703 > Project: Maven 2 > Type: Bug > Components: POM > Versions: 2.0 > Reporter: Yann Le Du > Assignee: Edwin Punzalan > Fix For: 2.0.3 > > > section in isn't propagated to child POMs (as > is). > The workaround is to use with true > Is this on purpose ? -- 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] Updated: (CONTINUUM-401) cannot delete project (stuck on 'in progress')
[ http://jira.codehaus.org/browse/CONTINUUM-401?page=all ] Yann Le Du updated CONTINUUM-401: - Attachment: wrapper-2005-12-21.log > cannot delete project (stuck on 'in progress') > -- > > Key: CONTINUUM-401 > URL: http://jira.codehaus.org/browse/CONTINUUM-401 > Project: Continuum > Type: Bug > Versions: 1.0 > Environment: running on linux debian > trying to access from winXP > Reporter: Adam Kiezun > Attachments: palulustuck.JPG, wrapper-2005-11-25.log, wrapper-2005-12-21.log > > > one of my projects got stuck in the 'in progress' state and cannot be deleted > from the web interface. > it's been in this state for > 24 hrs so it seems permanent. > attaching screenshot. > let me know if i should attach a log (and which one) -- 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
[jira] Created: (MEV-262) commons-email contains wrong dependencies
commons-email contains wrong dependencies - Key: MEV-262 URL: http://jira.codehaus.org/browse/MEV-262 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Yann Le Du javamail --> should be javax.mail javamail --> should be mail 1.3.3 activation --> should be javax.activation activation 1.0.2 Thx -- 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-1703) is not propagated to child POMs
[ http://jira.codehaus.org/browse/MNG-1703?page=comments#action_53561 ] Yann Le Du commented on MNG-1703: - I tried with a brand new Maven 2.0.1 installation and got the same thing. What I'm trying to do is to run an Ant script at process-resources phase. Currently, I use the following conf. Moving it to pluginManagement would allow it not to be executed also for the parent. maven-antrun-plugin process-resources run ant ant-nodeps 1.6.5 true > is not propagated to child POMs > -- > > Key: MNG-1703 > URL: http://jira.codehaus.org/browse/MNG-1703 > Project: Maven 2 > Type: Bug > Components: POM > Versions: 2.0 > Reporter: Yann Le Du > Assignee: Edwin Punzalan > Fix For: 2.0.3 > > > section in isn't propagated to child POMs (as > is). > The workaround is to use with true > Is this on purpose ? -- 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] Created: (MEV-261) acegi-security 0.8.2 depends on spring 1.2-RC2 instead of 1.2-rc2
acegi-security 0.8.2 depends on spring 1.2-RC2 instead of 1.2-rc2 - Key: MEV-261 URL: http://jira.codehaus.org/browse/MEV-261 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Yann Le Du springframework spring 1.2-RC2 Please change version to 1.2-rc2 (uncapitalized) -- 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: (MAVENUPLOAD-637) Please upload Struts HTML Taglib 1.2.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-637?page=comments#action_53532 ] Yann Le Du commented on MAVENUPLOAD-637: Filed in Struts : http://issues.apache.org/bugzilla/show_bug.cgi?id=37927 > Please upload Struts HTML Taglib 1.2.4 > -- > > Key: MAVENUPLOAD-637 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-637 > Project: maven-upload-requests > Type: Task > Reporter: Yann Le Du > > -- 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] Created: (MAVENUPLOAD-640) Please upload Struts Tiles Taglib 1.2.4
Please upload Struts Tiles Taglib 1.2.4 --- Key: MAVENUPLOAD-640 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-640 Project: maven-upload-requests Type: Task Reporter: Yann Le Du -- 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] Created: (MAVENUPLOAD-639) Please upload Struts Nested Taglib 1.2.4
Please upload Struts Nested Taglib 1.2.4 Key: MAVENUPLOAD-639 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-639 Project: maven-upload-requests Type: Task Reporter: Yann Le Du -- 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] Created: (MAVENUPLOAD-638) Please upload Struts Logic Taglib 1.2.4
Please upload Struts Logic Taglib 1.2.4 --- Key: MAVENUPLOAD-638 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-638 Project: maven-upload-requests Type: Task Reporter: Yann Le Du -- 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] Created: (MAVENUPLOAD-637) Please upload Struts HTML Taglib 1.2.4
Please upload Struts HTML Taglib 1.2.4 -- Key: MAVENUPLOAD-637 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-637 Project: maven-upload-requests Type: Task Reporter: Yann Le Du -- 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] Created: (MAVENUPLOAD-636) Please upload Struts Bean Taglib 1.2.4
Please upload Struts Bean Taglib 1.2.4 -- Key: MAVENUPLOAD-636 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-636 Project: maven-upload-requests Type: Task Reporter: Yann Le Du -- 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] Created: (MNG-1735) Ability to pass all prompted information as parameters in release:prepare
Ability to pass all prompted information as parameters in release:prepare - Key: MNG-1735 URL: http://jira.codehaus.org/browse/MNG-1735 Project: Maven 2 Type: Wish Components: maven-release-plugin Versions: 2.0 Reporter: Yann Le Du Priority: Minor In release:prepare, it would be nice that all prompted information can also be passed as parameters : * tag name (already available, -Dtag) * release version * new development version It would allow to call the plugin in real non-interactive mode - that is, without being forced to accept default values. -- 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] Updated: (MNG-1736) list-style-position: ouside; in maven-base.css
[ http://jira.codehaus.org/browse/MNG-1736?page=all ] Yann Le Du updated MNG-1736: Attachment: MNG-1736-maven-site-plugin.patch Changed ouside to outside Correction is harmless since outside is the default value > list-style-position: ouside; in maven-base.css > -- > > Key: MNG-1736 > URL: http://jira.codehaus.org/browse/MNG-1736 > Project: Maven 2 > Type: Bug > Components: maven-site-plugin > Versions: 2.0.1 > Reporter: Yann Le Du > Priority: Trivial > Attachments: MNG-1736-maven-site-plugin.patch > > > maven-base.css contains incorrect property value : > list-style-position: ouside; -- 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] Created: (MNG-1736) list-style-position: ouside; in maven-base.css
list-style-position: ouside; in maven-base.css -- Key: MNG-1736 URL: http://jira.codehaus.org/browse/MNG-1736 Project: Maven 2 Type: Bug Components: maven-site-plugin Versions: 2.0.1 Reporter: Yann Le Du Priority: Trivial maven-base.css contains incorrect property value : list-style-position: ouside; -- 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] Created: (MNG-1738) Long words in left column overflows
Long words in left column overflows --- Key: MNG-1738 URL: http://jira.codehaus.org/browse/MNG-1738 Project: Maven 2 Type: Bug Components: maven-site-plugin Versions: 2.0.1 Environment: Mozilla Firefox 1.5 Reporter: Yann Le Du Priority: Minor Attachments: before.png In the left column, if you put text with long words - such as project names - text overflows (see before.png) -- 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] Updated: (MNG-1738) Long words in left column overflows
[ http://jira.codehaus.org/browse/MNG-1738?page=all ] Yann Le Du updated MNG-1738: Attachment: after.png MNG-1738-maven-site-plugin.patch In #leftColumn, added : overflow: auto; See after.png > Long words in left column overflows > --- > > Key: MNG-1738 > URL: http://jira.codehaus.org/browse/MNG-1738 > Project: Maven 2 > Type: Bug > Components: maven-site-plugin > Versions: 2.0.1 > Environment: Mozilla Firefox 1.5 > Reporter: Yann Le Du > Priority: Minor > Attachments: MNG-1738-maven-site-plugin.patch, after.png, before.png > > > In the left column, if you put text with long words - such as project names - > text overflows (see before.png) -- 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-1543) pom.xml information automatically included in META-INF during jar
[ http://jira.codehaus.org/browse/MNG-1543?page=comments#action_52517 ]
Yann Le Du commented on MNG-1543:
-
My previous comment can be a bit confusing because I forgot to mention
something. In order to get full dependency information in the deployed POM, I :
* call 'package' to generate the exported POM
* replace the project POM with the exported POM
* call 'deploy'
Of course, this is a temporary hack, while waiting for stable release-plugin.
But I guess the absolute path thing is also present in release-pom ?
> pom.xml information automatically included in META-INF during jar
> --
>
> Key: MNG-1543
> URL: http://jira.codehaus.org/browse/MNG-1543
> Project: Maven 2
> Type: Improvement
> Components: maven-jar-plugin
> Versions: 2.0
> Reporter: Jorg Heymans
> Assignee: John Casey
> Fix For: 2.0.1
> Attachments: MNG-1543-maven-archiver.patch
>
>
> The jar plugin automatically adds a pom.xml in META-INF, which makes sense.
> But this pom.xml also contains local paths ie
>
>
> d:\src\excalibur-trunk\framework\api\src\java
> src/main/scripts
>
> d:\src\excalibur-trunk\framework\api\src\test
>
> d:\src\excalibur-trunk\framework\api\target\classes
>
> d:\src\excalibur-trunk\framework\api\target\test-classes
>
>
> META-INF
> d:\src\excalibur-trunk\framework\api\..\..
>
> LICENSE.txt
> NOTICE.txt
>
>
>
>
>
>
> d:\src\excalibur-trunk\framework\api\src\test\resources
> I don't see how this information could be useful to anyone else, and i'ld
> rather not have my local paths in distribution jars - call me paranoid :)
> Conversation log from IRC :
> jorgis there a way to tell maven not to include the pom.xml in
> META-INF when creating jars ?
> jesse hm, not that I know of
> jesse might be a boolean to control it in there somewhere
> jorgi looked at the jar plugin config .. didn't seem like it
> jorgit's not a real problem, just funny that this is done by default
> jesse I don't know, it makes it easier down the road to have
> automated things interrogate the jar for dependencies of the things inside
> trygvis yeah, you're right there jesse
> jorgmmm well yes that makes sense ...
> jorgthanks !
> trygvis jorg: it's useful for the application itself
> trygvis like reading out the version number from pom.properties
> jorgtrygvis: yes, but the pom also had my local paths in it for
> and stuff, that's why i found it a bit strange
> trygvis makes it easier making versioning-aware application and gives a
> thigh integration with your project management tool (aka maven)
> trygvis hm
> trygvis that should possibly be changed indeed
> trygvis File properties should be made relative to ${basedir} again
> trygvis when writing out the pom that is
> jorgi can understand about the dependencies , but the build
> configuration probably shouldn't be in there
> jorg
> d:\src\excalibur-trunk\framework\api\..\..
> trygvis jorg: file an issue, it should be relative to ${basedir} if
> there at all
> trygvis IMO the parts of a pom could be stripped from the repo
--
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-1543) pom.xml information automatically included in META-INF during jar
[ http://jira.codehaus.org/browse/MNG-1543?page=comments#action_52515 ]
Yann Le Du commented on MNG-1543:
-
Please see linked issue MNG-1715. My concern is also about the POM that is
deploy-ed *along* the JAR, that we'd like to be :
* effective-pom-like, particurlarly with full dependency information
* without absolute path
Simply including the project POM in META-INF will surely solve the present
issue.
Still, IMHO, the best would be to get rid of absolute paths in exported POM...
so that the exported POM could be used in META-INF *and* for deployment along
the JAR. This would solve both issues.
> pom.xml information automatically included in META-INF during jar
> --
>
> Key: MNG-1543
> URL: http://jira.codehaus.org/browse/MNG-1543
> Project: Maven 2
> Type: Improvement
> Components: maven-jar-plugin
> Versions: 2.0
> Reporter: Jorg Heymans
> Assignee: John Casey
> Fix For: 2.0.1
> Attachments: MNG-1543-maven-archiver.patch
>
>
> The jar plugin automatically adds a pom.xml in META-INF, which makes sense.
> But this pom.xml also contains local paths ie
>
>
> d:\src\excalibur-trunk\framework\api\src\java
> src/main/scripts
>
> d:\src\excalibur-trunk\framework\api\src\test
>
> d:\src\excalibur-trunk\framework\api\target\classes
>
> d:\src\excalibur-trunk\framework\api\target\test-classes
>
>
> META-INF
> d:\src\excalibur-trunk\framework\api\..\..
>
> LICENSE.txt
> NOTICE.txt
>
>
>
>
>
>
> d:\src\excalibur-trunk\framework\api\src\test\resources
> I don't see how this information could be useful to anyone else, and i'ld
> rather not have my local paths in distribution jars - call me paranoid :)
> Conversation log from IRC :
> jorgis there a way to tell maven not to include the pom.xml in
> META-INF when creating jars ?
> jesse hm, not that I know of
> jesse might be a boolean to control it in there somewhere
> jorgi looked at the jar plugin config .. didn't seem like it
> jorgit's not a real problem, just funny that this is done by default
> jesse I don't know, it makes it easier down the road to have
> automated things interrogate the jar for dependencies of the things inside
> trygvis yeah, you're right there jesse
> jorgmmm well yes that makes sense ...
> jorgthanks !
> trygvis jorg: it's useful for the application itself
> trygvis like reading out the version number from pom.properties
> jorgtrygvis: yes, but the pom also had my local paths in it for
> and stuff, that's why i found it a bit strange
> trygvis makes it easier making versioning-aware application and gives a
> thigh integration with your project management tool (aka maven)
> trygvis hm
> trygvis that should possibly be changed indeed
> trygvis File properties should be made relative to ${basedir} again
> trygvis when writing out the pom that is
> jorgi can understand about the dependencies , but the build
> configuration probably shouldn't be in there
> jorg
> d:\src\excalibur-trunk\framework\api\..\..
> trygvis jorg: file an issue, it should be relative to ${basedir} if
> there at all
> trygvis IMO the parts of a pom could be stripped from the repo
--
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-1543) pom.xml information automatically included in META-INF during jar
[ http://jira.codehaus.org/browse/MNG-1543?page=comments#action_52408 ]
Yann Le Du commented on MNG-1543:
-
Edwin, do you mean that the patch will be : "Do not generate an
exported-pom.xml and use the original pom.xml instead " ?
> pom.xml information automatically included in META-INF during jar
> --
>
> Key: MNG-1543
> URL: http://jira.codehaus.org/browse/MNG-1543
> Project: Maven 2
> Type: Improvement
> Components: maven-jar-plugin
> Versions: 2.0
> Reporter: Jorg Heymans
> Assignee: John Casey
> Fix For: 2.0.1
> Attachments: MNG-1543-maven-archiver.patch
>
>
> The jar plugin automatically adds a pom.xml in META-INF, which makes sense.
> But this pom.xml also contains local paths ie
>
>
> d:\src\excalibur-trunk\framework\api\src\java
> src/main/scripts
>
> d:\src\excalibur-trunk\framework\api\src\test
>
> d:\src\excalibur-trunk\framework\api\target\classes
>
> d:\src\excalibur-trunk\framework\api\target\test-classes
>
>
> META-INF
> d:\src\excalibur-trunk\framework\api\..\..
>
> LICENSE.txt
> NOTICE.txt
>
>
>
>
>
>
> d:\src\excalibur-trunk\framework\api\src\test\resources
> I don't see how this information could be useful to anyone else, and i'ld
> rather not have my local paths in distribution jars - call me paranoid :)
> Conversation log from IRC :
> jorgis there a way to tell maven not to include the pom.xml in
> META-INF when creating jars ?
> jesse hm, not that I know of
> jesse might be a boolean to control it in there somewhere
> jorgi looked at the jar plugin config .. didn't seem like it
> jorgit's not a real problem, just funny that this is done by default
> jesse I don't know, it makes it easier down the road to have
> automated things interrogate the jar for dependencies of the things inside
> trygvis yeah, you're right there jesse
> jorgmmm well yes that makes sense ...
> jorgthanks !
> trygvis jorg: it's useful for the application itself
> trygvis like reading out the version number from pom.properties
> jorgtrygvis: yes, but the pom also had my local paths in it for
> and stuff, that's why i found it a bit strange
> trygvis makes it easier making versioning-aware application and gives a
> thigh integration with your project management tool (aka maven)
> trygvis hm
> trygvis that should possibly be changed indeed
> trygvis File properties should be made relative to ${basedir} again
> trygvis when writing out the pom that is
> jorgi can understand about the dependencies , but the build
> configuration probably shouldn't be in there
> jorg
> d:\src\excalibur-trunk\framework\api\..\..
> trygvis jorg: file an issue, it should be relative to ${basedir} if
> there at all
> trygvis IMO the parts of a pom could be stripped from the repo
--
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] Created: (MNG-1715) Absolute paths in exported-pom.xml
Absolute paths in exported-pom.xml -- Key: MNG-1715 URL: http://jira.codehaus.org/browse/MNG-1715 Project: Maven 2 Type: Bug Components: Plugins and Lifecycle Versions: 2.0 Reporter: Yann Le Du Priority: Minor The exported-pom.xml generated by the 'package' phase contains absolute paths in the section - and also some relative ones, as . Is this behaviour on purpose ? This exported-pom.xml is used for the 'deploy' phase - and also maybe for the maven-release-plugin. Although these absolute paths are not used when the deployed POM is used for a dependency, they : * can be a security issue, as we don't want to show full information about our development environment * are, unless I'm mistaken, useless information -- 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] Created: (MNG-1703) is not propagated to child POMs
is not propagated to child POMs -- Key: MNG-1703 URL: http://jira.codehaus.org/browse/MNG-1703 Project: Maven 2 Type: Bug Components: POM Versions: 2.0 Reporter: Yann Le Du section in isn't propagated to child POMs (as is). The workaround is to use with true Is this on purpose ? -- 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: (CONTINUUM-401) cannot delete project (stuck on 'in progress')
[ http://jira.codehaus.org/browse/CONTINUUM-401?page=comments#action_51637 ] Yann Le Du commented on CONTINUUM-401: -- Actually I fortunaltely kept the old 1.0.1 directory. There was no error or exception in the log during the night. Are the builds sequenced in a certain way (e.g., based on dependencies between projects), or are they totally independent ? > cannot delete project (stuck on 'in progress') > -- > > Key: CONTINUUM-401 > URL: http://jira.codehaus.org/browse/CONTINUUM-401 > Project: Continuum > Type: Bug > Versions: 1.0 > Environment: running on linux debian > trying to access from winXP > Reporter: Adam Kiezun > Attachments: palulustuck.JPG > > > one of my projects got stuck in the 'in progress' state and cannot be deleted > from the web interface. > it's been in this state for > 24 hrs so it seems permanent. > attaching screenshot. > let me know if i should attach a log (and which one) -- 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
[jira] Commented: (MNG-1253) Plugin versions are populated in next iteration POM
[ http://jira.codehaus.org/browse/MNG-1253?page=comments#action_50974 ] Yann Le Du commented on MNG-1253: - Just noticed a related issue that makes this one duplicate, I think : http://jira.codehaus.org/browse/MNG-1100 > Plugin versions are populated in next iteration POM > --- > > Key: MNG-1253 > URL: http://jira.codehaus.org/browse/MNG-1253 > Project: Maven 2 > Type: Bug > Components: maven-release-plugin > Versions: 2.0 (RC) > Environment: maven-release-plugin 2.0-beta-2 > Reporter: Yann Le Du > Fix For: 2.0.1 > > > Note : this is with maven-release-plugin 2.0-beta-2 (had problems with beta-3) > Last iteration POM (before release) : > > maven-homemade-plugin > > [...] > I omit the plugin version because I use pluginManagement in parent POM > Next iteration POM (after release) : > > maven-homemade-plugin > 1.0.0 > > [...] > I don't want this, because this will override my parent's pluginManagement -- 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: (MEV-183) Move common-test to its correct directory
[ http://jira.codehaus.org/browse/MEV-183?page=comments#action_50293 ] Yann Le Du commented on MEV-183: The changes are not effective on ibiblio... Maybe the directories need a "touch" or something ? > Move common-test to its correct directory > - > > Key: MEV-183 > URL: http://jira.codehaus.org/browse/MEV-183 > Project: Maven Evangelism > Type: Bug > Reporter: Yann Le Du > Assignee: Edwin Punzalan > > > commons-test : commons-test : 0.1 is currently stored in : > commons-test / commons / test-0.1 > Please change this to : > commons-test / commons-test / 0.1 > Note : The maven-metadata's are also incorrect and need being generated again. > The POM is correct. > Thx -- 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] Created: (MEV-184) emma 2.0.latest : how do we handle this ?
emma 2.0.latest : how do we handle this ? - Key: MEV-184 URL: http://jira.codehaus.org/browse/MEV-184 Project: Maven Evangelism Type: Bug Reporter: Yann Le Du Versions of emma:emma are in the form 2.0.build directory-network:mina expresses a dependency on emma as : emma emma 2.0.latest ... which doesn't work What is the preferred way to handle such a case ? -- 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] Created: (MEV-183) Move common-test to its correct directory
Move common-test to its correct directory - Key: MEV-183 URL: http://jira.codehaus.org/browse/MEV-183 Project: Maven Evangelism Type: Bug Reporter: Yann Le Du commons-test : commons-test : 0.1 is currently stored in : commons-test / commons / test-0.1 Please change this to : commons-test / commons-test / 0.1 Note : The maven-metadata's are also incorrect and need being generated again. The POM is correct. Thx -- 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] Created: (MEV-182) Replace ${pom.currentVersion} with ${pom.version} in apache-ldapber-provider
Replace ${pom.currentVersion} with ${pom.version} in apache-ldapber-provider
Key: MEV-182
URL: http://jira.codehaus.org/browse/MEV-182
Project: Maven Evangelism
Type: Bug
Reporter: Yann Le Du
Please replace ${pom.currentVersion} with ${pom.version} in dependencies :
ldap-common
Thx
--
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] Created: (MEV-181) Replace ${pom.currentVersion} with ${pom.version} in apacheds-main
Replace ${pom.currentVersion} with ${pom.version} in apacheds-main
--
Key: MEV-181
URL: http://jira.codehaus.org/browse/MEV-181
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: Yann Le Du
Please replace ${pom.currentVersion} with ${pom.version} in dependencies :
asn1-codec
Thx
--
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: (MEV-181) Replace ${pom.currentVersion} with ${pom.version} in apacheds-main
[ http://jira.codehaus.org/browse/MEV-181?page=comments#action_50197 ]
Yann Le Du commented on MEV-181:
My bad, title should be "Replace ${pom.currentVersion} with ${pom.version} in
asn1-ber"
> Replace ${pom.currentVersion} with ${pom.version} in apacheds-main
> --
>
> Key: MEV-181
> URL: http://jira.codehaus.org/browse/MEV-181
> Project: Maven Evangelism
> Type: Bug
> Components: Dependencies
> Reporter: Yann Le Du
>
>
> Please replace ${pom.currentVersion} with ${pom.version} in dependencies :
> asn1-codec
> Thx
--
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] Created: (MEV-180) Replace ${pom.currentVersion} with ${pom.version} in apacheds-main
Replace ${pom.currentVersion} with ${pom.version} in apacheds-main
--
Key: MEV-180
URL: http://jira.codehaus.org/browse/MEV-180
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: Yann Le Du
Please replace ${pom.currentVersion} with ${pom.version} for dependencies :
apacheds-shared
apacheds-core
Thx
--
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: (MEV-169) Relocated dependency for tagsoup in xom
[ http://jira.codehaus.org/browse/MEV-169?page=comments#action_50169 ] Yann Le Du commented on MEV-169: Seems to be OK the way it is (as far as I'm concerned...) http://www.ibiblio.org/maven2/org/ccil/cowan/tagsoup/tagsoup/0.9.7/ is complete http://www.ibiblio.org/maven2/tagsoup/tagsoup/0.9.7/tagsoup-0.9.7.pom relocates to org.ccil.cowan.tagsoup:tagsoup > Relocated dependency for tagsoup in xom > --- > > Key: MEV-169 > URL: http://jira.codehaus.org/browse/MEV-169 > Project: Maven Evangelism > Type: Improvement > Components: Dependencies > Reporter: Yann Le Du > Assignee: Edwin Punzalan > > > Important : must be done only after MAVENUPLOAD-573 is achieved > Please change tagsoup dependency to : > org.ccil.cowan.tagsoup > tagsoup > Thx -- 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: (MEV-174) Wrong apacheds-main dependency groupId in acegi-security POM
[ http://jira.codehaus.org/browse/MEV-174?page=comments#action_50051 ] Yann Le Du commented on MEV-174: Oh, and BTW, 0.9-SNAPSHOT should be changed to 0.9 > Wrong apacheds-main dependency groupId in acegi-security POM > > > Key: MEV-174 > URL: http://jira.codehaus.org/browse/MEV-174 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Yann Le Du > > > In > > apache-directory > apacheds-main > 0.9-SNAPSHOT > > please change groupId to > directory > Thx -- 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] Created: (MEV-174) Wrong apacheds-main dependency groupId in acegi-security POM
Wrong apacheds-main dependency groupId in acegi-security POM Key: MEV-174 URL: http://jira.codehaus.org/browse/MEV-174 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Yann Le Du In apache-directory apacheds-main 0.9-SNAPSHOT please change groupId to directory Thx -- 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] Created: (MEV-169) Relocated dependency for tagsoup in xom
Relocated dependency for tagsoup in xom --- Key: MEV-169 URL: http://jira.codehaus.org/browse/MEV-169 Project: Maven Evangelism Type: Improvement Components: Dependencies Reporter: Yann Le Du Important : must be done only after MAVENUPLOAD-573 is achieved Please change tagsoup dependency to : org.ccil.cowan.tagsoup tagsoup Thx -- 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: (MEV-35) XOM POM references tagsoup which is not in the repo
[ http://jira.codehaus.org/browse/MEV-35?page=comments#action_49914 ] Yann Le Du commented on MEV-35: --- Filed an upload request for this one : MAVENUPLOAD-573 > XOM POM references tagsoup which is not in the repo > --- > > Key: MEV-35 > URL: http://jira.codehaus.org/browse/MEV-35 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Vincent Massol > Attachments: tagsoup-0.9.7.jar > > > Downloading: > http://repo1.maven.org/maven2/tagsoup/tagsoup/0.9.7/tagsoup-0.9.7.pom > [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Main Error: > Unable to read the metadata file > tagsoup:tagsoup:0.9.7:jar > from the specified remote repositories: > http://repo1.maven.org/maven2 > Path to dependency: > 1) com.xpn.xwiki:xwiki:war:0.9-SNAPSHOT > 2) dom4j:dom4j:jar:1.6 > 3) jaxen:jaxen:jar:1.1-beta-4 > 4) xom:xom:jar:1.0b3 > Root error: > Unable to download the artifact from any repository -- 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] Created: (MAVENUPLOAD-573) Please upload tagsoup 0.9.7
Please upload tagsoup 0.9.7 --- Key: MAVENUPLOAD-573 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-573 Project: maven-upload-requests Type: Task Reporter: Yann Le Du Here is also a bundle for the relocation POM in tagsoup:tagsoup : http://yann.le.du.free.fr/maven/tagsoup/tagsoup.0.9.7-bundle.jar -- 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] Created: (MEV-166) Incorrect dependency for icu4j in xom
Incorrect dependency for icu4j in xom - Key: MEV-166 URL: http://jira.codehaus.org/browse/MEV-166 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Yann Le Du Please change icu4j dependency to : com.ibm.icu icu4j ...in both versions 1.0b3 & 1.1d2 Related to MEV-34 Thx -- 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: (MEV-34) XOM POM references icu4j which is not in the repo
[ http://jira.codehaus.org/browse/MEV-34?page=comments#action_49905 ] Yann Le Du commented on MEV-34: --- Great, but you put it on groupId icu, whereas the groupId referenced in xom is icu4j I'll file an issue to update xom (a quick search shows that icu4j is used nowhere else) > XOM POM references icu4j which is not in the repo > - > > Key: MEV-34 > URL: http://jira.codehaus.org/browse/MEV-34 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Vincent Massol > Assignee: Carlos Sanchez > Attachments: icu4j_2_6_1.jar, normalizer-2.6.1.jar, normalizer_license.html > > > Downloading: http://repo1.maven.org/maven2/icu4j/icu4j/2.6.1/icu4j-2.6.1.pom > [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Main Error: > Unable to read the metadata file > icu4j:icu4j:2.6.1:jar > from the specified remote repositories: > http://repo1.maven.org/maven2 > Path to dependency: > 1) com.xpn.xwiki:xwiki:war:0.9-SNAPSHOT > 2) dom4j:dom4j:jar:1.6 > 3) jaxen:jaxen:jar:1.1-beta-4 > 4) xom:xom:jar:1.0b3 > Root error: > Unable to download the artifact from any repository -- 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-1398) site report generates an 'empty' target/site/apidocs/index.html
[ http://jira.codehaus.org/browse/MNG-1398?page=comments#action_49819 ] Yann Le Du commented on MNG-1398: - See MNG-1249 > site report generates an 'empty' target/site/apidocs/index.html > --- > > Key: MNG-1398 > URL: http://jira.codehaus.org/browse/MNG-1398 > Project: Maven 2 > Type: Bug > Components: maven-javadoc-plugin > Versions: 2.0 (RC) > Reporter: John Allen > > > javadoc site report generates an 'empty' target/site/apidocs/index.html > > > ... > > > > > > > > > > © > 2005 > Acme Org > > > > > > > -- 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] Created: (MNG-1399) release-pom.xml does not contain inherited dependency exclusions
release-pom.xml does not contain inherited dependency exclusions Key: MNG-1399 URL: http://jira.codehaus.org/browse/MNG-1399 Project: Maven 2 Type: Bug Components: maven-release-plugin Versions: 2.0 Reporter: Yann Le Du maven-release-plugin 2.0-beta-2 My project depends upon org.hibernate:hibernate:3.0.5 hibernate depends upon dom4j, but excludes a bunch of dom4j dependencies m2 release:prepare on my project produces a tag release-pom.xml that contains dependency upon dom4j, but without -- 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] Created: (MPCHANGES-26) default xmlPath should be the same in changes-report and announcement-generate
default xmlPath should be the same in changes-report and announcement-generate
--
Key: MPCHANGES-26
URL: http://jira.codehaus.org/browse/MPCHANGES-26
Project: maven-changes-plugin
Type: Improvement
Versions: 1.5.1
Reporter: Yann Le Du
changes-maven-plugin 2.0-beta-1
Default xmlPath is
* in changes-report : ${basedir}/src/changes/changes.xml
* in announcement-generate : ${basedir}/src/main/changes.xml
It would be nice they be the same.
--
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] Created: (MNG-1253) Plugin versions are populated in next iteration POM
Plugin versions are populated in next iteration POM --- Key: MNG-1253 URL: http://jira.codehaus.org/browse/MNG-1253 Project: Maven 2 Type: Bug Components: maven-release-plugin Versions: 2.0 (RC) Environment: maven-release-plugin 2.0-beta-2 Reporter: Yann Le Du Note : this is with maven-release-plugin 2.0-beta-2 (had problems with beta-3) Last iteration POM (before release) : maven-homemade-plugin [...] I omit the plugin version because I use pluginManagement in parent POM Next iteration POM (after release) : maven-homemade-plugin 1.0.0 [...] I don't want this, because this will override my parent's pluginManagement -- 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] Created: (MNG-1249) External Javadoc report apidocs/index.html is overwritten
External Javadoc report apidocs/index.html is overwritten - Key: MNG-1249 URL: http://jira.codehaus.org/browse/MNG-1249 Project: Maven 2 Type: Bug Components: maven-reports Versions: 2.0 (RC) Reporter: Yann Le Du Priority: Minor MNG-650 is happening again -- 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-678) scp intermittently failing deploying artifact
[ http://jira.codehaus.org/browse/MNG-678?page=comments#action_48842 ] Yann Le Du commented on MNG-678: I switched to 2.0-RC (thus jsch-0.1.23), and I'm encountering these failures (90% of the time)... although I had no problem with 2.0-beta-3 :) [INFO] [site:deploy] scp://host.corp.com/devef/maven/site/COMMON/common-framework - Session: Opened Executing command: mkdir -p /devef/maven/site/COMMON/common-framework/. Executing command: mkdir -p /devef/maven/site/COMMON/common-framework/. scp://host.corp.com/devef/maven/site/COMMON/common-framework - Session: Disconnecting scp://host.corp.com/devef/maven/site/COMMON/common-framework - Session: Disconnected [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error uploading site Embedded error: Error performing commands for file transfer session is down [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:544) [...] Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading site at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:142) [...] Caused by: org.apache.maven.wagon.TransferFailedException: Error performing commands for file transfer at org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:91) [...] Caused by: org.apache.maven.wagon.CommandExecutionException: Cannot execute remote command: mkdir -p /devef/maven/site/COMMON/common-framework/. at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.executeCommand(AbstractSshWagon.java:292) [...] Caused by: com.jcraft.jsch.JSchException: session is down at com.jcraft.jsch.Session.openChannel(Unknown Source) [...] > scp intermittently failing deploying artifact > - > > Key: MNG-678 > URL: http://jira.codehaus.org/browse/MNG-678 > Project: Maven 2 > Type: Bug > Components: maven-artifact > Versions: 2.0-alpha-3 > Environment: JDK 1.5, Red Hat 9 > Reporter: Joe Futrelle > Assignee: Brett Porter > Fix For: 2.0 (RC) > > > Some of the time, deploying artifacts fails during the scp transfer. The > bottom of the stack trace is reproduced below. If I run the m2 deploy enough > times, it succeeds; not sure why. > This is not an unknown issue with Jsch; apparently client code can cause > behavior like this if it doesn't dispose of connections properly. Possibly a > plugin that's runs before the deploy phase is messing up the connection state > somehow? > Caused by: org.apache.maven.wagon.TransferFailedException: Error occured > while deploying 'ncsa/gsbt/1.0-SNAPSHOT/gsbt-1.0-20050728.190330-38.pom.sha1' > to remote repository: scp://chasm.ncsa.uiuc.edu//home/futrelle/m2/repository > at > org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:331) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:167) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:91) > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:73) > ... 17 more > Caused by: com.jcraft.jsch.JSchException: session is down > at com.jcraft.jsch.Channel.connect(Unknown Source) > at > org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:271) > ... 20 more -- 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] Created: (MNG-1188) release:prepare changes incorrectly tag pom scm if tagbase not standard
release:prepare changes incorrectly tag pom scm if tagbase not standard --- Key: MNG-1188 URL: http://jira.codehaus.org/browse/MNG-1188 Project: Maven 2 Type: Bug Components: maven-release-plugin Versions: 2.0-beta-3 Reporter: Yann Le Du /COMMON/trunk/maven-plugins/maven-deps-plugin/pom.xml : scm:svn:svn://host:3691/COMMON/trunk/maven-plugins/maven-deps-plugin/ scm:svn:svn://host:3691/COMMON/trunk/maven-plugins/maven-deps-plugin/ http://host.corp.com/viewcvs/COMMON/trunk/maven-plugins/maven-deps-plugin/ [...] maven-release-plugin 2.0-beta-2 svn://host:3691/COMMON/tags/ m2 release:prepare tags creates correctly a tag in /COMMON/tags/maven-deps-plugin_V1.0.0, but the tag pom.xml contains : scm:svn:svn://host:3691/COMMON/tags/maven-deps-plugin_V1.0.0/maven-plugins/maven-deps-plugin/ scm:svn:svn://host:3691/COMMON/tags/maven-deps-plugin_V1.0.0/maven-plugins/maven-deps-plugin/ http://host.corp.com/viewcvs/COMMON/tags/maven-deps-plugin_V1.0.0/maven-plugins/maven-deps-plugin/ ...that is, maven-plugins/maven-deps-plugin/ is concatenated at the end of URLs, although we don't expect it. The tag release-pom.xml and repo POMs contain correct trunk URLs. -- 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-916) RELEASE gets selected as a version
[ http://jira.codehaus.org/browse/MNG-916?page=comments#action_48219 ] Yann Le Du commented on MNG-916: Unless I'm mistaken, the issue is still there in beta-3, i.e. Maven still looks for the RELEASE version of my home-made plugin in my corp. repository. Let me know if you need more info to debug. > RELEASE gets selected as a version > -- > > Key: MNG-916 > URL: http://jira.codehaus.org/browse/MNG-916 > Project: Maven 2 > Type: Bug > Components: maven-artifact > Reporter: Brett Porter > Assignee: Brett Porter > Fix For: 2.0-beta-3 > > Original Estimate: 1 hour >Time Spent: 5 minutes > Remaining: 0 minutes > > if the metadata fails while searching for the released version, the string > RELEASE is stored in the local metadata as the selected version. This should > never happen, and it results in looking for the text string RELEASE instead > of resolving a version. -- 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] Created: (MNG-1114) install:install-file makes reactor parse subprojects
install:install-file makes reactor parse subprojects Key: MNG-1114 URL: http://jira.codehaus.org/browse/MNG-1114 Project: Maven 2 Type: Bug Components: maven-install-plugin Versions: 2.0-beta-3 Reporter: Yann Le Du Priority: Trivial When you execute m2 install:install-file -DgroupId=jdbc -DartifactId=jdbc -Dversion=2.0 -Dpackaging=jar -Dfile=/home/maven/repository-manual/jdbc/jdbc/2.0/jdbc-2.0.jar in a parent project, the reactor executes it again in every subproject. Harmless, but unexpected. Maybe somehow related to MNG-432 ? -- 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-897) allows use of Ant build files
[ http://jira.codehaus.org/browse/MNG-897?page=comments#action_47331 ] Yann Le Du commented on MNG-897: Apart from avoiding writing a Maven plugin when you don't know how, I see two reasons why you would want to call Ant scripts from Maven : * You have an Ant script which configures your project for the developement environment. The production team uses the same Ant script to configure the project for the production environment, and they * won't * use Maven. Obviously, you don't want to duplicate your scripting into an Ant script AND a Maven plugin, because you would have to synchronize every modification. So you will go on with the Ant script. * You want to quickly "mavenize" a highly-Ant-dependent project - and prove this is worth and painless :) In a first phase, you only want to write POMs, and keep all your existing do-some-obscure-tasks Ant scripts (but keeping in mind that you'll replace them by Maven plugins later) In both cases, it would be great to leave the existing Ant script alone, and only write some calling code. It seems to me that John's foo-build.xml and foo-build.bindings.xml fully fills this need. foo-build.xml could as well be an existing Ant script... Am I wrong ? > allows use of Ant build files > - > > Key: MNG-897 > URL: http://jira.codehaus.org/browse/MNG-897 > Project: Maven 2 > Type: Improvement > Components: maven-ant-plugin > Versions: 2.0-alpha-3 > Reporter: Chris Berry > Assignee: John Casey > Fix For: 2.0-beta-3 > Attachments: antfile.zip > > Original Estimate: 8 hours >Time Spent: 8 hours > Remaining: 1 hour > > Per John Casey, This is logged to that it stays on the radar. > Please consider incorporating my antfile plugin. > I have included the following in the ZIP > maven-antrun-plugin --> the basic antrun w/ a few small mods > maven-antfile-plugin > maven-axisant-plugin --> an example plugin using the antfile plugin > axis-master --> a "grouping" plugin for axis example > my-app --> an example app using the axisant plugin. > Cheers, > -- Chris -- 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: (CONTINUUM-243) Ability to mass edit projects or define default goal
[ http://jira.codehaus.org/browse/CONTINUUM-243?page=comments#action_47163 ] Yann Le Du commented on CONTINUUM-243: -- The custom default goal could be the one defined in POM's , see http://jira.codehaus.org/browse/MNG-1011 > Ability to mass edit projects or define default goal > > > Key: CONTINUUM-243 > URL: http://jira.codehaus.org/browse/CONTINUUM-243 > Project: Continuum > Type: New Feature > Components: continuum-web > Versions: 1.0-alpha-3 > Reporter: Yann Le Du > Priority: Minor > > > At the moment, the default goal for a new project is "clean:clean install". > Say we want to make it "clean:clean install site:site site:deploy" for one > project --> OK. But say for 10 or more projects... > The idea would be to : > * either to mass edit project goals > * either to define a custom default goal for new projects > Hope it is clear enough... -- 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
[jira] Created: (MNG-943) Can't access to corp. repo snapshots by mirroring central
Can't access to corp. repo snapshots by mirroring central - Key: MNG-943 URL: http://jira.codehaus.org/browse/MNG-943 Project: Maven 2 Type: Bug Components: maven-project Versions: 2.0-beta-1 Reporter: Yann Le Du Priority: Critical I have set a corp. repository, and want local users to use this repo to download latest corp. artifacts. Altering the local settings.xml with ~ ~ central ~ http://repo.corp.com/maven/repository ~ allows downloading only releases, not snapshots. Adding a mirror for "snapshots" doesn't change anything. For the moment, my workaround is to alter each POM with these lines : ~ ~ central ~ http://repo.corp.com/maven/repository ~ always ~ -- 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] Created: (CONTINUUM-314) Remove border for company logo
Remove border for company logo -- Key: CONTINUUM-314 URL: http://jira.codehaus.org/browse/CONTINUUM-314 Project: Continuum Type: Wish Components: continuum-web Versions: 1.0-alpha-4 Reporter: Yann Le Du Priority: Minor Attachments: CONTINUUM-314.txt Patch attached -- 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
[jira] Created: (MNG-931) In site.html, extra images are said to be available via resources/images
In site.html, extra images are said to be available via resources/images Key: MNG-931 URL: http://jira.codehaus.org/browse/MNG-931 Project: Maven 2 Type: Bug Components: documentation Versions: 2.0-beta-1 Reporter: Yann Le Du Attachments: MNG-931.txt http://maven.apache.org/maven2/site.html, section 'Adding Extra Resources' The file pic1.jpg will be available via a relative reference to the <<< resources/images >>> directory from any page in your site. --> should be <<< images >>> Patch attached -- 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: (MEV-85) JetSpeed:portlet-api dependency in DisplayTag 1.0 POM
[ http://jira.codehaus.org/browse/MEV-85?page=comments#action_46519 ] Yann Le Du commented on MEV-85: --- portlet-api is under ibiblio, but with the groupId portlet-api Also, the dependency jdk:tools:1.3 is a problem. Is it meant in the way of http://jira.codehaus.org/browse/MNG-806 or ?... Locally, I just deleted this dependency and things go well. > JetSpeed:portlet-api dependency in DisplayTag 1.0 POM > - > > Key: MEV-85 > URL: http://jira.codehaus.org/browse/MEV-85 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Pablo Muñiz > > > http://www.ibiblio.org/maven2/displaytag/displaytag/1.0/displaytag-1.0.pom > has an error on jetspeed:portlet-api dependency > > jetspeed > portlet-api > unknown > > version value seems to be invalid. -- 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] Created: (MAVENUPLOAD-518) Please upload opencms 5.0.1
Please upload opencms 5.0.1 --- Key: MAVENUPLOAD-518 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-518 Project: maven-upload-requests Type: Task Reporter: Yann Le Du thx -- 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: (MAVENUPLOAD-515) Please upload tm-extractors 0.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-515?page=comments#action_46304 ] Yann Le Du commented on MAVENUPLOAD-515: My mistake, could not find a license on the site, but the downloaded zip contained one. The bundle URL is up-to-date. Sorry... > Please upload tm-extractors 0.4 > --- > > Key: MAVENUPLOAD-515 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-515 > Project: maven-upload-requests > Type: Task > Reporter: Yann Le Du > > > http://www.textmining.org/ > Could not find a license, so provided an empty one -- 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] Created: (MAVENUPLOAD-515) Please upload tm-extractors 0.4
Please upload tm-extractors 0.4 --- Key: MAVENUPLOAD-515 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-515 Project: maven-upload-requests Type: Task Reporter: Yann Le Du http://www.textmining.org/ Could not find a license, so provided an empty one -- 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] Created: (MEV-82) commons-digester
commons-digester Key: MEV-82 URL: http://jira.codehaus.org/browse/MEV-82 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Yann Le Du commons-digester-1.3.pom contains 1.0-dev commons-digester-1.5.pom contains 1.4.1 -- 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: (MEV-57) Invalid commons-beanutils:commons-beanutils versions
[ http://jira.codehaus.org/browse/MEV-57?page=comments#action_45397 ] Yann Le Du commented on MEV-57: --- Not sure on what to elaborate but... what I meant is (e.g. for the 1st one) : http://www.ibiblio.org/maven2/commons-beanutils/commons-beanutils/1.4/commons-beanutils-1.4.pom contains 1.0-dev ...while Maven would have expected : * either to have 1.4 instead * or to have the POM placed in directory 1.0-dev Hope it is clear enough - now :) > Invalid commons-beanutils:commons-beanutils versions > > > Key: MEV-57 > URL: http://jira.codehaus.org/browse/MEV-57 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Yann Le Du > > > 1.4 : 1.0-dev > 1.4.1 : 1.0-dev > 1.6 : 1.6-dev > 1.6.1 : 1.7-dev -- 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-554) site:site launched from parent project doesn't parse child custom site source sub-directories
[ http://jira.codehaus.org/browse/MNG-554?page=comments#action_43839 ]
Yann Le Du commented on MNG-554:
Some more info :
Prefixing siteDirectory with ${basedir}, i.e. :
${basedir}/site
...solves the issue
So I guess ${basedir} is not automatically prefixed when you are working in the
parent project.
The ${basedir} thing is also present in http://jira.codehaus.org/browse/MNG-694
> site:site launched from parent project doesn't parse child custom site source
> sub-directories
> -
>
> Key: MNG-554
> URL: http://jira.codehaus.org/browse/MNG-554
> Project: Maven 2
> Type: Bug
> Components: maven-plugins
> Versions: 2.0-alpha-3
> Environment: Windows XP
> Reporter: Yann Le Du
> Assignee: Vincent Siveton
> Fix For: 2.0-beta-1
> Attachments: common.zip
>
>
> Project A contains a module B. B's site source directory is different from
> the default one and contains a sub-directory apt :
> A / B / site / site.xml
> A / B / site / apt / index.apt
> ... so I've put this in the B / pom.xml plugins section :
> org.apache.maven.plugins
> maven-site-plugin
>
> site
>
> When I launch site:site from B directory, B's site is correclty built. But
> when I launch from A directory, B's index.html is missing. I guess that
> site.xml was correctly taken, but that apt sub-directory was ignored.
--
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] Created: (MEV-57) Invalid commons-beanutils:commons-beanutils versions
Invalid commons-beanutils:commons-beanutils versions Key: MEV-57 URL: http://jira.codehaus.org/browse/MEV-57 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Yann Le Du 1.4 : 1.0-dev 1.4.1 : 1.0-dev 1.6 : 1.6-dev 1.6.1 : 1.7-dev -- 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] Created: (MNG-694) war:war launched from parent doesn't find module web.xml
war:war launched from parent doesn't find module web.xml
Key: MNG-694
URL: http://jira.codehaus.org/browse/MNG-694
Project: Maven 2
Type: Bug
Components: maven-plugins
Versions: 2.0-alpha-3
Reporter: Yann Le Du
foo
+-- pom.xml
+-- foo-contact
+-- pom.xml
+-- contact
+-- WebContent
+-- WEB-INF
+-- web.xml
In foo-contact pom.xml :
org.apache.maven.plugins
maven-war-plugin
contact/WebContent
war:war launched from foo-contact is OK.
war:war launched from foo produces :
org.apache.maven.plugin.MojoExecutionException: Error assembling WAR
at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:224)
...
Caused by: org.codehaus.plexus.archiver.ArchiverException: Deployment
descriptor:
/devel/maven/src/RIC/trunk/ric-contact/target/contact/WEB-INF/web.xml does not
exist.
at
org.codehaus.plexus.archiver.war.WarArchiver.setWebxml(WarArchiver.java:70)
...
Adding contact/WebContent/WEB-INF/web.xml produces the same
message.
Adding ${basedir}/contact/WebContent/WEB-INF/web.xml solves
the issue.
I guess out two things here :
* when you launch war:war from parent, webXml does not default to
${warSourceDirectory}/WEB-INF/web.xml
* webXml isn't implicitly prefixed with ${basedir}/
See also
http://marc.theaimsgroup.com/?l=turbine-maven-user&m=111623705811553&w=2 for a
previous report of this issue.
--
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] Created: (MEV-54) Invalid odmg:odmg:3.0 POM
Invalid odmg:odmg:3.0 POM - Key: MEV-54 URL: http://jira.codehaus.org/browse/MEV-54 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Yann Le Du should be doesn't exist doesn't exist doesn't exist -- 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] Updated: (MNG-663) In Project Team page, developers organization URLs are not links
[ http://jira.codehaus.org/browse/MNG-663?page=all ] Yann Le Du updated MNG-663: --- Attachment: MNG-663.txt Here's the fix : MNG-663.txt > In Project Team page, developers organization URLs are not links > > > Key: MNG-663 > URL: http://jira.codehaus.org/browse/MNG-663 > Project: Maven 2 > Type: Improvement > Components: maven-plugins > Versions: 2.0-beta-1 > Environment: trunk build, rev. 225474 > Reporter: Yann Le Du > Priority: Minor > Fix For: 2.0-beta-1 > Attachments: MNG-663.txt > > > In this page, the developers organization URLs are not created as hyperlinks > ( while contributors ones are). -- 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] Created: (MNG-663) In Project Team page, developers organization URLs are not links
In Project Team page, developers organization URLs are not links Key: MNG-663 URL: http://jira.codehaus.org/browse/MNG-663 Project: Maven 2 Type: Improvement Components: maven-plugins Versions: 2.0-beta-1 Environment: trunk build, rev. 225474 Reporter: Yann Le Du Priority: Minor Fix For: 2.0-beta-1 In this page, the developers organization URLs are not created as hyperlinks ( while contributors ones are). -- 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] Created: (MNG-661) In parent site, automatically create link to modules sites and vice-versa
In parent site, automatically create link to modules sites and vice-versa - Key: MNG-661 URL: http://jira.codehaus.org/browse/MNG-661 Project: Maven 2 Type: Improvement Components: maven-plugins Versions: 2.0-alpha-3 Reporter: Yann Le Du Priority: Minor Say we have the following project structure : A +-- B +-- C +-- D It would be nice to have the following links in the left menu of the generated sites : A : Modules : B, D B : Parent : A Modules : C C : Parent : B D : Parent : A -- 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-554) site:site launched from parent project doesn't parse child custom site source sub-directories
[ http://jira.codehaus.org/browse/MNG-554?page=comments#action_43514 ] Yann Le Du commented on MNG-554: I just found something more precise : when you launch site:site from the parent project, it actually uses the parent site.xml also for the module site. That would explain why the index.html is incorrect. > site:site launched from parent project doesn't parse child custom site source > sub-directories > - > > Key: MNG-554 > URL: http://jira.codehaus.org/browse/MNG-554 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-alpha-3 > Environment: Windows XP > Reporter: Yann Le Du > Assignee: Vincent Siveton > Fix For: 2.0-beta-1 > Attachments: common.zip > > > Project A contains a module B. B's site source directory is different from > the default one and contains a sub-directory apt : > A / B / site / site.xml > A / B / site / apt / index.apt > ... so I've put this in the B / pom.xml plugins section : > org.apache.maven.plugins > maven-site-plugin > > site > > When I launch site:site from B directory, B's site is correclty built. But > when I launch from A directory, B's index.html is missing. I guess that > site.xml was correctly taken, but that apt sub-directory was ignored. -- 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-660) Project info reports plugin fails on unvalid SVN repository connection
[ http://jira.codehaus.org/browse/MNG-660?page=comments#action_43505 ] Yann Le Du commented on MNG-660: Erratum on my previous comment : [...] As a matter of fact, if I omit the second 'svn:', the generated Project Info [...] > Project info reports plugin fails on unvalid SVN repository connection > -- > > Key: MNG-660 > URL: http://jira.codehaus.org/browse/MNG-660 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-beta-1 > Reporter: Yann Le Du > > > Using the trunk build (rev. 225332) > My POM contains > > scm:svn:svn://host:3691/COMMON/trunk/commonframework/ > > and > [...] > org.apache.maven.plugins > maven-project-info-reports-plugin > > site:site fails with the following error : > [INFO] Generate "Source Repository" report. > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Diagnosis: Error during site generation > [INFO] > > [ERROR] Cause: org.apache.maven.plugin.MojoExecutionException: Error during > site generation > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:372) > ... > Caused by: java.lang.IllegalArgumentException: The SVN repository connection > is not valid. > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.getSvnRoot(ScmReport.java:427) > ... -- 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-660) Project info reports plugin fails on unvalid SVN repository connection
[ http://jira.codehaus.org/browse/MNG-660?page=comments#action_43504 ] Yann Le Du commented on MNG-660: The duplicate svn is on purpose. As described in http://maven.apache.org/reference/plugins/scm/scmurl.html, the first one is for the provider and the second one for the protocol (we use svn protocol and not http). As a matter of fact, the generated Project Info page displays the erroneous info : The source can be checked out anonymously from SVN with this command: $>svn checkout //host:3691/COMMON/trunk/common-framework common-framework > Project info reports plugin fails on unvalid SVN repository connection > -- > > Key: MNG-660 > URL: http://jira.codehaus.org/browse/MNG-660 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-beta-1 > Reporter: Yann Le Du > > > Using the trunk build (rev. 225332) > My POM contains > > scm:svn:svn://host:3691/COMMON/trunk/commonframework/ > > and > [...] > org.apache.maven.plugins > maven-project-info-reports-plugin > > site:site fails with the following error : > [INFO] Generate "Source Repository" report. > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Diagnosis: Error during site generation > [INFO] > > [ERROR] Cause: org.apache.maven.plugin.MojoExecutionException: Error during > site generation > at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:372) > ... > Caused by: java.lang.IllegalArgumentException: The SVN repository connection > is not valid. > at > org.apache.maven.report.projectinfo.ScmReport$ScmRenderer.getSvnRoot(ScmReport.java:427) > ... -- 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]
