ok, thanks. Arnaud
On 12/9/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 9 Dec 06, at 9:36 AM 9 Dec 06, Arnaud HERITIER wrote: > Jason, > > To fix MAVEN-1659 <http://jira.codehaus.org/browse/MAVEN-1659> we > need to > have the fix for WAGONHTTP-5 <http://jira.codehaus.org/browse/ > WAGONHTTP-5>. > Is it possible to release wagon http 1.0-beta-2 ASAP ?* > Yah, the 72 hours is almost up. I'll work with Joakim to get this out. I have several releases myself to get out. Jason. > *Arnaud* > * > On 12/9/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: >> >> Another thing which can help us, is to help to setup somewhere a >> CI like >> continuum to build maven from the bootstrap. We'll gain a lot of >> time. >> >> Arnaud >> >> On 12/9/06, Arnaud Héritier <[EMAIL PROTECTED]> wrote: >> > >> > Hi guys, >> > >> > >> > >> > I'm back. Sorry for the delay to reply to this emergency. >> > >> > >> > >> > As you certainly know we released the beta 3 at the beginning of >> > august. >> > >> > The next step for us it to release a first release candidate to >> > quickly have a final release. >> > >> > We are focusing on keeping the compatibility with maven 1.0.2 >> projects >> > but personally I stopped to try to have plug-ins compatibles >> with M1.0.xand >> > M1.1. It's too complicated to have something which works with >> all the >> > old bugs in Jelly ;-) >> > >> > Due to our current problems with the central repository for maven >> > 1.0.2 on ibiblio, it could be important to accelerate the >> development of >> > the RC1. Here is the list of the tasks that we think we have to >> do before a >> > release. >> > >> > >> > >> > Maven 1.1 core issues: >> > >> > >> > >> > Bugs >> > >> > >> > >> > MAVEN-1755 Backward Incompability : Usage of xml entities >> in the >> > POM doesn't work in maven 1.1 beta 1 & 2 >> > >> > I began to fix this one. I modified the maven-model to use a >> new one >> > which uses dom4j and not xpp3 (and it works). For that I also >> modified the >> > dom4j plugin in modello to add a read method with an url >> parameter. But >> > dom4j is slower than xpp3. I don't test it yet but it could be >> possible to >> > do it with the woodstox plugin which implements stax 2 [1]. It's >> not really >> > complicated to change it and to update the code in the core and >> in the >> > artifact plugin. When it will work we'll have to release modello >> and >> > maven-model 3.0.2. There's also the documentation about >> > incompatibilities to update. >> > >> > >> > >> > MAVEN-1789 Change the default repository to >> > http://repo1.maven.org/maven/ >> > >> > It's done int the code but we have to update the >> documentation to >> > use "central repository" instead of ibilio. >> > >> > >> > >> > MAVEN-1692 improve error when 1.0.2 was in path but >> MAVEN_HOME is >> > 1.1 >> > >> > MAVEN-1459 misleading error message >> > >> > MAVEN-1106 remove poor uses of system.err/out in core and >> plugins >> > >> > MAVEN-1816 Confusing console output on test failures >> > >> > MAVEN-1103 improve "goal not found" reporting >> > >> > All these issues are related to the logs produced by maven. >> It's >> > quite easy to fix. I began but I introduced MAVEN-1816 (I have >> some cleanup >> > to do before to close them) >> > >> > >> > >> > To check : >> > >> > MAVEN-1817 Maven doesn't try to find snapshots in all >> repositories >> > >> > I think that finally it's the correct behaviour. When maven >> find a >> > snapshot on a remote repository, it doesn't try to download it >> on another >> > repo because artifacts are generally deployed only in one >> repository. >> > >> > >> > >> > MAVEN-1814 if maven.repo.remote.enabled=true maven doesn't >> download >> > dependencies >> > >> > I didn't reproduced it. I'm not sure that it's not a bug in >> archiva. >> > >> > >> > >> > MAVEN-1659 Dependency jars are not downloading from remote >> > repository placed in Subversion with http access >> > >> > ?? Is annoying but not blocking. If it's not fixed by wagon I >> > propose to move it for a "future" release >> > >> > >> > >> > MAVEN-1656 Doco that explains the protocols required to allow >> > maven.xml or any plugin.jelly to inject values into or retrieve >> values >> > from another plugin >> > >> > MAVEN-1688 The ${pom.versions} List behaves differently when >> > running plugins under maven 1.1 and maven 1.0 >> > >> > MAVEN-1125 ant:java fork issues >> > >> > MAVEN-1440 Clearing maven.repo.remote results in incorrect >> > reporting of unsatisfied dependencies >> > >> > MAVEN-1660 DependencyVerifier class doesn't resolve an >> snapshot >> > artifact after attaining a first goal. >> > >> > Not yet analysed >> > >> > >> > >> > Nice to have : >> > >> > Those issues are planned because they can have a real added >> value with >> > few work on them >> > >> > >> > >> > MAVEN-1812 Add MAVEN_HOME/bin in the PATH >> > >> > >> > >> > MAVEN-1790 Fix headers sent to the repository >> > >> > It's a nice to have if wagon supports it. >> > >> > >> > >> > MAVEN-1808 Put MAVEN_HOME in the system environment >> variables if >> > the user has admin rights >> > >> > Easy to fix with the nsis plugin ... >> > >> > >> > >> > M1.1 Plugins to release : >> > >> > We planned to release some plugins to bundle them in the >> 1.1RC1release. >> > >> > MAVEN-1769 Upgrade plugins >> > >> > You can have a look at the roadmap of each plugin to see what >> we have >> > to fix. >> > >> > MAVEN-1777 Upgrade maven-artifact-plugin to v 1.8.1 (very >> important >> > to fix due to an incompatibility with the beta 3) >> > >> > MAVEN-1773 Upgrade maven-dist-plugin to v 1.7.1 >> > >> > MAVEN-1775 Upgrade maven-eclipse-plugin to v. 1.11.1 >> > >> > MAVEN-1774 Upgrade maven-ejb-plugin to v 1.7.3 >> > >> > MAVEN-1782 Upgrade maven-jdiff-plugin to v. 1.5.1 >> > >> > MAVEN-1810 Upgrade maven-nsis-plugin to v 2.1 >> > >> > MAVEN-1809 Upgrade maven-pdf-plugin to v 2.5.1 >> > >> > MAVEN-1780 Upgrade maven-test-plugin to v 1.8.1 >> > >> > MAVEN-1772 Upgrade maven-war-plugin to v 1.6.3 >> > >> > MAVEN-1771 Upgrade maven-xdoc-plugin to v 1.10.1 >> > >> > Those plugins use maven-model, thus it could be interesting to >> wait >> > for the release of maven-model 3.0.2 before to release them : >> > >> > maven:maven-artifact-plugin, maven:maven-changelog-plugin, >> > maven:maven-dist-plugin, maven:maven-eclipse-plugin, maven:maven- >> ejb-plugin, >> > maven:maven-linkcheck-plugin, maven:maven-multiproject-plugin, >> > maven:maven-source-plugin, maven:maven-xdoc-plugin, >> > >> > >> > >> > >> > >> > Please help. Take the lead where you want, the more important >> is to >> > fix issues. >> > >> > >> > >> > Thanks a lot. >> > >> > >> > >> > Cheers, >> > >> > >> > >> > Arnaud >> > >> > >> > >> > >> > >> > >> > >> > [1] >> > http://woodstox.codehaus.org/3.0.2/javadoc/org/codehaus/stax2/ >> XMLInputFactory2.html#createXMLStreamReader(java.net.URL)<http:// >> woodstox.codehaus.org/3.0.2/javadoc/org/codehaus/stax2/ >> XMLInputFactory2.html#createXMLStreamReader%28java.net.URL%29> >> > >> > >> > >> > >> > >> > >> > >> > >> > .......................................................... >> > >> > *Arnaud Heritier* >> > *Architecte* >> > >> > *OCTO Technology* >> > >> > .......................................................... >> > >> > 50, Avenue des Champs-Elysées >> > >> > 75008 Paris >> > >> > Tél : (33) 1 58 56 10 00 >> > >> > Fax : (33) 1 58 56 10 01 >> > >> > GSM : (33) 6 03 52 71 31 >> > >> > www.octo.com/ >> > >> > ........................................................... >> > >> > >> > >> > >> > >> > >> > >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
