Re: [M10N] fixing repo for cocoon
Antonio Gallardo wrote: No problem. Please download excalibur using the Release Tag or the revision number used for the release, add your maven2 poms and recompile. :-) mmm, can someone tell me how to move a file to a previous revision in SVN ? I've added the excalibur poms to trunk, but need them in a much earlier revision. Is this possible at all? Jorg
Re: [M10N] fixing repo for cocoon
Jorg Heymans wrote: Antonio Gallardo wrote: No problem. Please download excalibur using the Release Tag or the revision number used for the release, add your maven2 poms and recompile. :-) mmm, can someone tell me how to move a file to a previous revision in SVN ? I've added the excalibur poms to trunk, but need them in a much earlier revision. Is this possible at all? You cannot do that. The only thing you can do is to tag another revision with the same release tag. -- Leszek Gawron [EMAIL PROTECTED] IT Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: [M10N] fixing repo for cocoon
Jorg Heymans wrote: the fact that it depends on 2 saxons is a pain :) you can't have 2 dependencies with the same group and artifactid - even though they have different versions. That's why we have saxon and saxon7. I've brought most of excalibur-trunk under maven2 control yesterday, we will now finetune the poms and release them to ibiblio. This saves us from needing to exclude 15 libs for each avalon dependency. I fine tuned the poms yesterday a little bit (at least I hope that this was a fine tuning...) so we should try to get this up to ibiblio. Can you do this? Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [M10N] fixing repo for cocoon
Carsten Ziegeler wrote: Jorg Heymans wrote: the fact that it depends on 2 saxons is a pain :) you can't have 2 dependencies with the same group and artifactid - even though they have different versions. That's why we have saxon and saxon7. I've brought most of excalibur-trunk under maven2 control yesterday, we will now finetune the poms and release them to ibiblio. This saves us from needing to exclude 15 libs for each avalon dependency. I fine tuned the poms yesterday a little bit (at least I hope that this was a fine tuning...) so we should try to get this up to ibiblio. Can you do this? Please keep in mind that some of the excalibur jars contains changes included, right after the distro. How we are going to deal with this? Best Regards, Antonio Gallardo. Carsten
Re: [M10N] fixing repo for cocoon
Carsten Ziegeler wrote: I fine tuned the poms yesterday a little bit (at least I hope that this was a fine tuning...) so we should try to get this up to ibiblio. Can you do this? great thanks Carsten! I'll find out more about the sync'ing process, we will need this for Cocoon anyway. Jorg
Re: [M10N] fixing repo for cocoon
Vadim Gritsenko wrote: I see... You are right! Maven *is* a pain! I for one, welcome our new Maven Overlords ! :-P
Re: [M10N] fixing repo for cocoon
Antonio Gallardo wrote: Please keep in mind that some of the excalibur jars contains changes included, right after the distro. How we are going to deal with this? I think the dependencies have not changed since the last release, so we can just update the poms. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [M10N] fixing repo for cocoon
Antonio Gallardo wrote: Please keep in mind that some of the excalibur jars contains changes included, right after the distro. How we are going to deal with this? Yes I was wondering about this as well. ATM the poms are building from trunk, how can we make sure we have exactly the same revision as the libs that our out on ibiblio now? Or should we do a new release ourselves ... *shrugs* Jorg
Re: [M10N] fixing repo for cocoon
Carsten Ziegeler wrote:
Antonio Gallardo wrote:
Please keep in mind that some of the excalibur jars contains changes
included, right after the distro. How we are going to deal with this?
I think the dependencies have not changed since the last release, so we
can just update the poms.
Sorry, I though the excalibur sources changed since last release. I
remember the lastest release was before Sept, 1st:
$cd svn/excalibur
$svn log --verbose -r {2005-09-01}:{2005-11-09} | grep .java
The output shows instrument, logkit, pool, datasource, soureresolver,
avalon-fw-api and avalon-fw-impl have .java files changed.
Best Regards,
Antonio Gallardo.
Re: [M10N] fixing repo for cocoon
Jorg Heymans wrote: Antonio Gallardo wrote: Please keep in mind that some of the excalibur jars contains changes included, right after the distro. How we are going to deal with this? Yes I was wondering about this as well. ATM the poms are building from trunk, how can we make sure we have exactly the same revision as the libs that our out on ibiblio now? Or should we do a new release ourselves ... *shrugs* No problem. Please download excalibur using the Release Tag or the revision number used for the release, add your maven2 poms and recompile. :-) Best Regards, Antonio Gallardo.
Re: [M10N] fixing repo for cocoon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 9 Nov 2005, Carsten Ziegeler wrote: Date: Wed, 09 Nov 2005 09:05:26 +0100 From: Carsten Ziegeler [EMAIL PROTECTED] Reply-To: dev@cocoon.apache.org To: dev@cocoon.apache.org Subject: Re: [M10N] fixing repo for cocoon Jorg Heymans wrote: the fact that it depends on 2 saxons is a pain :) you can't have 2 dependencies with the same group and artifactid - even though they have different versions. That's why we have saxon and saxon7. I've brought most of excalibur-trunk under maven2 control yesterday, we will now finetune the poms and release them to ibiblio. This saves us from needing to exclude 15 libs for each avalon dependency. I fine tuned the poms yesterday a little bit (at least I hope that this was a fine tuning...) so we should try to get this up to ibiblio. Can you do this? Carsten I get a: Reason: Error getting POM for 'knopflerfish:knopflerfish-log_all' from the repository: Exit code: 1 - Host key verification failed. Any others as well? - -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDccroLNdJvZjjVZARArL+AKCY/5EHUUC2Ux1XamDsZ0K/1PiF9ACggWhp ylgQTnOOQF+rUzfmYdkePk4= =xvbi -END PGP SIGNATURE-
Re: [M10N] fixing repo for cocoon
Giacomo Pati wrote: I get a: Reason: Error getting POM for 'knopflerfish:knopflerfish-log_all' from the repository: Exit code: 1 - Host key verification failed. Any others as well? Yepp, I get the same error now - but didn't have to time to look into it :( Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [M10N] fixing repo for cocoon
Daniel Fagerstrom wrote: The lacking POMs are in the Apache Maven repository http://cvs.apache.org/repository. Yes they are there , but that doesn't explain the error IMO. ibiblio is not hosting these at all, and these poms on cvs.a.o haven't been modified since August. Jorg
Re: [M10N] fixing repo for cocoon
Antonio Gallardo wrote: No problem. Please download excalibur using the Release Tag or the revision number used for the release, add your maven2 poms and recompile. :-) http://svn.apache.org/viewcvs.cgi/excalibur/tags/ this will take a while, and to be honest I don't know when i'll have time to go through all of them ... *hint* ... :) Jorg
Re: [M10N] fixing repo for cocoon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 9 Nov 2005, Carsten Ziegeler wrote: Date: Wed, 09 Nov 2005 15:26:29 +0100 From: Carsten Ziegeler [EMAIL PROTECTED] Reply-To: dev@cocoon.apache.org To: dev@cocoon.apache.org Subject: Re: [M10N] fixing repo for cocoon Giacomo Pati wrote: I get a: Reason: Error getting POM for 'knopflerfish:knopflerfish-log_all' from the repository: Exit code: 1 - Host key verification failed. Any others as well? Yepp, I get the same error now - but didn't have to time to look into it :( I'd ould like to look into it but do not have a clue about which ley it is complaining !?!? But I'm happy I'm not the only one. Thanks. - -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDciROLNdJvZjjVZARAh9KAKCee68P0O9DfY8BuajBduF0mDYUCQCdHdki Z9yPhWrHw/umBlYXwobQpiA= =dEe4 -END PGP SIGNATURE-
Re: [M10N] fixing repo for cocoon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 9 Nov 2005, Daniel Fagerstrom wrote: Date: Wed, 09 Nov 2005 15:40:31 +0100 From: Daniel Fagerstrom [EMAIL PROTECTED] Reply-To: dev@cocoon.apache.org To: dev@cocoon.apache.org Subject: Re: [M10N] fixing repo for cocoon Carsten Ziegeler wrote: Giacomo Pati wrote: I get a: Reason: Error getting POM for 'knopflerfish:knopflerfish-log_all' from the repository: Exit code: 1 - Host key verification failed. Any others as well? Yepp, I get the same error now - but didn't have to time to look into it :( Carsten The lacking POMs are in the Apache Maven repository http://cvs.apache.org/repository. You mean M2 is just issuing a missleading messaging? The POM there is invalid? Actually I don't get what you mean! - -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDciUDLNdJvZjjVZARAsS3AJ9zGfuaq4xjLALIaPQgLg8uDMTuOACbBc18 88F4FswFtcUbdvA8uP81PFg= =Ri/u -END PGP SIGNATURE-
Re: [M10N] fixing repo for cocoon
Giacomo Pati wrote: ... The lacking POMs are in the Apache Maven repository http://cvs.apache.org/repository. You mean M2 is just issuing a missleading messaging? The POM there is invalid? Actually I don't get what you mean! I meant that when I tried to compile whiteboard/cocoon-flat-layout I got some error message related to knopflerfish which not is available in ibiblio but in http://cvs.apache.org/repository. After having added, repositories !-- Apache specific maven repositories available to all blocks -- repository idapache-cvs/id nameApache CVS Repository/name urlhttp://cvs.apache.org/repository/url layoutlegacy/layout /repository /repositories to the top level POM, that problem dissapeard. Still it doesn't compile complaining that javax.servlet doesn't exists. Haven't had time to do anything about it though. Don't know if this was related to your problem. /Daniel
Re: [M10N] fixing repo for cocoon
Daniel Fagerstrom wrote: repositories !-- Apache specific maven repositories available to all blocks -- repository idapache-cvs/id nameApache CVS Repository/name urlhttp://cvs.apache.org/repository/url layoutlegacy/layout /repository /repositories ugh that makes total sense. I had these libs in my local repo already that's why i didn't spot it. I'll fix this now. Note to self: build with a __clean__ local repo to make sure *everything* is downloadable. Jorg
Re: [M10N] fixing repo for cocoon
Jorg Heymans wrote: I had these libs in my local repo already that's why i didn't spot it. I'll fix this now. done. If you want to test it on an empty repository, edit the repo location in settings.xml and do mvn -s settings.xml install from the root. Note that it doesn't hurt running maven with the -cpu switch every now and then. This ensures you've got the latest release of the plugins used during your build. Jorg
Re: [M10N] fixing repo for cocoon
Daniel Fagerstrom wrote: The xmlutil have an enourmous amount of dependencies, any ideas why it use both saxon and saxon7 and even saxon7-sql? xmlutil provides avalon components (api) such as xpath *and* several implementations of those apis based on different libraries: saxon6/7, jaxen, etc. saxon6 and saxon7 has different api, hence excalibur has 2 implementations: one for users of saxon6 and another for saxon7. Vadim
Re: [M10N] fixing repo for cocoon
Vadim Gritsenko wrote: The xmlutil have an enourmous amount of dependencies, any ideas why it use both saxon and saxon7 and even saxon7-sql? xmlutil provides avalon components (api) such as xpath *and* several implementations of those apis based on different libraries: saxon6/7, jaxen, etc. saxon6 and saxon7 has different api, hence excalibur has 2 implementations: one for users of saxon6 and another for saxon7. the fact that it depends on 2 saxons is a pain :) you can't have 2 dependencies with the same group and artifactid - even though they have different versions. That's why we have saxon and saxon7. I've brought most of excalibur-trunk under maven2 control yesterday, we will now finetune the poms and release them to ibiblio. This saves us from needing to exclude 15 libs for each avalon dependency. Jorg
Re: [M10N] fixing repo for cocoon
Jorg Heymans wrote: the fact that it depends on 2 saxons is a pain :) you can't have 2 dependencies with the same group and artifactid - even though they have different versions. I see... You are right! Maven *is* a pain! :-P :-P Vadim
Re: [M10N] fixing repo for cocoon
I just tried the m2 build for the test structure in the whiteboard and get the following error: [INFO] Failed to resolve artifact. GroupId: saxon7 ArtifactId: saxon7 Version: 7.9.1 Reason: Unable to download the artifact from any repository saxon7:saxon7:7.9.1:jar Am I the only one getting this? Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [M10N] fixing repo for cocoon
Carsten Ziegeler wrote: I just tried the m2 build for the test structure in the whiteboard and get the following error: [INFO] Failed to resolve artifact. GroupId: saxon7 ArtifactId: saxon7 Version: 7.9.1 Reason: Unable to download the artifact from any repository saxon7:saxon7:7.9.1:jar Am I the only one getting this? I have the same problem for saxon7-jdom. And also for: GroupId: jaxen ArtifactId: jaxen Version: 1.0-FCS-full Reason: Unable to download the artifact from any repository jaxen:jaxen:1.0-FCS-full:jar /Daniel
Re: [M10N] fixing repo for cocoon
Carsten Ziegeler wrote: I just tried the m2 build for the test structure in the whiteboard and get the following error: [INFO] Failed to resolve artifact. GroupId: saxon7 ArtifactId: saxon7 Version: 7.9.1 Reason: Unable to download the artifact from any repository saxon7:saxon7:7.9.1:jar I'm pretty sure saxon was on cvs.apache.org already, who removed it ? The recommended maven way of solving this would be to nag to the project maintainers to get them to release to ibiblio. Jorg
Re: [M10N] fixing repo for cocoon
Carsten Ziegeler wrote: I just tried the m2 build for the test structure in the whiteboard and get the following error: [INFO] Failed to resolve artifact. GroupId: saxon7 ArtifactId: saxon7 Version: 7.9.1 Reason: Unable to download the artifact from any repository saxon7:saxon7:7.9.1:jar Am I the only one getting this? Carsten It is in the dependencies in excalibur-xmlutil-2.1, see: http://www.ibiblio.org/maven2/excalibur-xmlutil/excalibur-xmlutil/2.1/excalibur-xmlutil-2.1.pom The xmlutil have an enourmous amount of dependencies, any ideas why it use both saxon and saxon7 and even saxon7-sql? /Daniel
Re: [M10N] fixing repo for cocoon
Daniel Fagerstrom wrote: It is in the dependencies in excalibur-xmlutil-2.1, see: http://www.ibiblio.org/maven2/excalibur-xmlutil/excalibur-xmlutil/2.1/excalibur-xmlutil-2.1.pom The xmlutil have an enourmous amount of dependencies, any ideas why it use both saxon and saxon7 and even saxon7-sql? That pom is just plain dodgy. We should go through the excalibur libs and fix the poms once and for all. Can we do this ourselves or is there still a project maintainer to nag ? Jorg
Re: [M10N] fixing repo for cocoon
Jorg Heymans wrote: Daniel Fagerstrom wrote: It is in the dependencies in excalibur-xmlutil-2.1, see: http://www.ibiblio.org/maven2/excalibur-xmlutil/excalibur-xmlutil/2.1/excalibur-xmlutil-2.1.pom The xmlutil have an enourmous amount of dependencies, any ideas why it use both saxon and saxon7 and even saxon7-sql? That pom is just plain dodgy. We should go through the excalibur libs and fix the poms once and for all. Can we do this ourselves or is there still a project maintainer to nag ? We can do this ourselves I think - the best (but most time consuming)way would imho be to convert excalibur to use maven 2. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [M10N] fixing repo for cocoon
Carsten Ziegeler wrote: We can do this ourselves I think - the best (but most time consuming)way would imho be to convert excalibur to use maven 2. Well, the poms are partially converted so that's a big part done already. Provided the repository is somewhat properly organized, going through the poms and stripping them of unnecessary cruft shouldn't take too long - even though it's utterly boring! Is excalibur still being developed? Last svn commit seemed to be 3 days ago. Jorg
Re: [M10N] fixing repo for cocoon
Jorg Heymans wrote: Carsten Ziegeler wrote: We can do this ourselves I think - the best (but most time consuming)way would imho be to convert excalibur to use maven 2. Well, the poms are partially converted so that's a big part done already. Provided the repository is somewhat properly organized, going through the poms and stripping them of unnecessary cruft shouldn't take too long - even though it's utterly boring! :) But these are the low hanging fruits most people are waiting for, or? ;) Is excalibur still being developed? Last svn commit seemed to be 3 days ago. Yes; it's not that active anymore but from time to time minor features or bug fixes are added. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [M10N] fixing repo for cocoon
Jorg Heymans wrote: Carsten Ziegeler wrote: We can do this ourselves I think - the best (but most time consuming)way would imho be to convert excalibur to use maven 2. Well, the poms are partially converted so that's a big part done already. Provided the repository is somewhat properly organized, Excalibur is built with Maven1 so it should be properly organized. going through the poms and stripping them of unnecessary cruft shouldn't take too long - even though it's utterly boring! Is excalibur still being developed? Last svn commit seemed to be 3 days ago. It is maintained rather than developed. If you feel like taking care of it, just subscribe to dev@excalibur.apache.org and ask about M2. Even if the list isn't that active, many of the Excalibur and Avalon developers read it so you probably get respons. Before, Cocoon committers automatically got commit access to Excalibur, don't know if that is the case anymore. /Daniel
[M10N] fixing repo for cocoon
Hi: In a maven2 repo, we miss some .pom files: Downloading: http://cvs.apache.org/repository/eclipse/poms/jdtcore-3.0.2.pom [WARNING] Unable to get resource from repository apache-cvs (http://cvs.apache.org/repository) Downloading: http://repo1.maven.org/maven2/eclipse/jdtcore/3.0.2/jdtcore-3.0.2.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) Downloading: http://cvs.apache.org/repository/daisy/poms/daisy-util-1.1.pom [WARNING] Unable to get resource from repository apache-cvs (http://cvs.apache.org/repository) Downloading: http://repo1.maven.org/maven2/daisy/daisy-util/1.1/daisy-util-1.1.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) Downloading: http://cvs.apache.org/repository/nekohtml/poms/nekodtd-0.1.11.pom [WARNING] Unable to get resource from repository apache-cvs (http://cvs.apache.org/repository) Downloading: http://repo1.maven.org/maven2/nekohtml/nekodtd/0.1.11/nekodtd-0.1.11.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) How I can add the missing .pom files in http://cvs.apache.org/repository to avoid these warnings? Best Regards, Antonio Gallardo.
Re: [M10N] fixing repo for cocoon
Hi Antonio, Glad to see you've decided to get involved with M10N ;-) I've updated the cocoon maven page on daisy [1], see section the new dependency doesn't use maven yet, step 5 and 6 should be what you're looking for. Maybe this page should be made more accessible somehow, it's not linked from the main page anywhere. Note that creating the poms on cvs.apache.org is only a temporary measure, as ideally it are the projects themselves who need to do this on ibiblio. Thanks! Jorg [1] http://cocoon.zones.apache.org/daisy/documentation/756.html Antonio Gallardo wrote: Hi: In a maven2 repo, we miss some .pom files: Downloading: http://cvs.apache.org/repository/eclipse/poms/jdtcore-3.0.2.pom [WARNING] Unable to get resource from repository apache-cvs (http://cvs.apache.org/repository) Downloading: http://repo1.maven.org/maven2/eclipse/jdtcore/3.0.2/jdtcore-3.0.2.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) Downloading: http://cvs.apache.org/repository/daisy/poms/daisy-util-1.1.pom [WARNING] Unable to get resource from repository apache-cvs (http://cvs.apache.org/repository) Downloading: http://repo1.maven.org/maven2/daisy/daisy-util/1.1/daisy-util-1.1.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) Downloading: http://cvs.apache.org/repository/nekohtml/poms/nekodtd-0.1.11.pom [WARNING] Unable to get resource from repository apache-cvs (http://cvs.apache.org/repository) Downloading: http://repo1.maven.org/maven2/nekohtml/nekodtd/0.1.11/nekodtd-0.1.11.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) How I can add the missing .pom files in http://cvs.apache.org/repository to avoid these warnings? Best Regards, Antonio Gallardo.
Re: [M10N] fixing repo for cocoon
Jorg Heymans wrote:
Hi Antonio,
Glad to see you've decided to get involved with M10N ;-)
Just playing around! ;-)
I've updated the cocoon maven page on daisy [1], see section the new
dependency doesn't use maven yet, step 5 and 6 should be what you're
looking for. Maybe this page should be made more accessible somehow,
it's not linked from the main page anywhere.
Thanks for the hint. This is exactly what I was looking for!
(I was not aware that I have access there.) :-)
I just did the jdtcore-3.0.2.pom and jdtcore-3.0.2.pom.md5
Under The new dependency doesn't use maven (yet). Please add this info:
The poms need to be added under: $M2_REPO/{groupId}/{artifactId}/poms/
ie: for jdtcore. this dir is: $M2_REPO/eclipse/jdtcore/poms/
** Creating md5 **
For the md5, execute:
On BSD: md5 -q [artifactId]-[version].pom [artifactId]-[version].pom.md5
On Linux: md5sum [artifactId]-[version].pom [artifactId]-[version].pom.md5
For sha1, execute:
On BSD: sha1 -q [artifactId]-[version].pom [artifactId]-[version].pom.sha1
On Linux: sha1sum [artifactId]-[version].pom
[artifactId]-[version].pom.sha1
Note that creating the poms on cvs.apache.org is only a temporary
measure, as ideally it are the projects themselves who need to do this
on ibiblio.
Yep.
BTW, in the apache repo we have an artifact for jakarta-oro. We should
use instead oro. Or if posible, redirect the repo as maven2 do for the
servletapi.
I am not on the maven maillist. :-(
Best Regards,
Antonio Gallardo
