Re: Repository purge (MRM-294 and MRM-275)
Brett Porter wrote: On 25/07/2007, at 8:54 PM, Maria Odea Ching wrote: 3. artifact count to be retained is this within the given version? ie, keep X builds of this snapshot. I think this would be specified for all snapshots, not per version. It would be a long list if it would be for each version. Sorry, I must have misunderstood what you meant. So you mean, if the number kept is 5, then it would keep 5 in total of the latest, no matter how many versions there are? - Brett Sorry, I think I confused you more. Anyway, that's what I meant by #3 :-) So if I specified 5, then it would keep 5 in total of the latest if the snapshot's count in the repo is more than 5. If the total number of that snapshot in the repo didn't reach 5, then it would keep all of them. Thanks, Deng
Re: Repository purge (MRM-294 and MRM-275)
On 25/07/2007, at 9:09 PM, Maria Odea Ching wrote: Sorry, I think I confused you more. Anyway, that's what I meant by #3 :-) So if I specified 5, then it would keep 5 in total of the latest if the snapshot's count in the repo is more than 5. If the total number of that snapshot in the repo didn't reach 5, then it would keep all of them. I think we're saying the same thing - can you just clarify for me are you saying 5 are: a) 1.1-SNAPSHOT, 1.2-SNAPSHOT, 1.3-SNAPSHOT, 1.4-SNAPSHOT, 1.5- SNAPSHOT; or b) 1.1-20070506.121113-1, 1.1-20070506.121113-2, 1.1-20070506.121113-3, 1.1-20070506.121113-4, 1.1-20070506.121113-5 I was thinking it's (b), since (a) is taken care of by the delete anything that's released rule. Cheers, Brett
Re: Repository purge (MRM-294 and MRM-275)
On 7/25/07, Maria Odea Ching [EMAIL PROTECTED] wrote: I'm trying to fix up MRM-294, and I need your input/comments :-) Should the configuration for the repository purge be for each repository? If so, I think it can be consolidated with the repository scanning schedule and set up as another consumer which would be executed during repository scanning. I think you and Brett have worked out the details, so I just want to confirm that this will be configurable in archiva.xml prior to starting the app. -- Wendy
Re: [Reporting] UI via JasperReports
Hi Guys, I've attached a couple of patches for this on MRM-329. :) Comments are very much welcome... -Teody Maria Odea Ching wrote: I don't really know about its licensing though.. -Deng Brett Porter wrote: Me too - 2 years ago, I did both the html paging, and emailing pdfs of the same thing, plus letting people write their own reports to run. how does the licensing fit these days? On 19/07/2007, at 12:53 PM, Maria Odea Ching wrote: I had some experience with JasperReports and iReport. I'll be happy to help out, though I may have to polish up on that. It's been 2 years since I last used it. -Deng Joakim Erdfelt wrote: I'm about to integrate JasperReports into archiva for report presentation in archiva. This will be a learning experience for me. I'd love to have some help with this effort. Anyone here have any experience with JasperReports on webapps? (things like HTML output with paging) - Joakim
Re: some issues for rescheduling?
Thanks Brett, I'll review them. Emmanuel Brett Porter a écrit : Hi, I took a look through future for things that could be adjusted, and came up with the following list. I didn't want to 'just do it', since I'm not that close to the status of the project right now, so if someone could review these it'd be much appreciated. to close: CONTINUUM-933 (acegi branch) CONTINUUM-450 (the wagon notifier does this?) CONTINUUM-37 (superceded) CONTINUUM-516 (can't see why it's neeeded, enqueue is fast) CONTINUUM-924 (already exists?) CONTINUUM-841 (duplicate of 678, no longer an issue) CONTINUUM-1112 (seems fixed already) CONTINUUM-882 (from acegi) CONTINUUM-938 (I think it no longer applies - test and close) CONTINUUM-960 (out of date) CONTINUUM-128 (no longer needed) CONTINUUM-640 (I think it dupes 347?) CONTINUUM-467 (I think it dupes 347?) CONTINUUM-344 (out of date) CONTINUUM-721 (out of date) CONTINUUM-737 (out of date) CONTINUUM-660 (out of date) CONTINUUM-751 (out of date?) CONTINUUM-752 (out of date?) CONTINUUM-1176 (out of date) CONTINUUM-1247 (not a Continuum bug?) CONTINUUM-1248 (not a Continuum bug?) CONTINUUM-1249 (not a Continuum bug?) CONTINUUM-1253 (won't fix - use mvn deploy instead) to schedule for 1.1: CONTINUUM-692 (possibly - talks about profile dependency being the only blocker) CONTINUUM-347 (documentation) CONTINUUM-815 (documentation) CONTINUUM-1063 (just do it) CONTINUUM-618 (it's really annoying, and simple to fix) CONTINUUM-1037 (seems a fatal flaw in Ant use) CONTINUUM-811 (documentation) CONTINUUM-1079 (the feature exists, it's just not visible due to this problem and probably related security issues) CONTINUUM-1310 (goes with above) CONTINUUM-1333 CONTINUUM-1265 (NPE should generally be fixable) CONTINUUM-1255 (is ugly, should be easy to disable) Thanks, Brett
Re: [vote] release continuum 1.1-beta-1
On 7/24/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: It seems I have the same conf for the resources plugin in Continuum and in Archiva The config was the same, but it was in pluginManagement rather than plugins. It's fixed in r559411. -- Wendy
Re: [vote] release continuum 1.1-beta-1
Cool. Do not forget to add something in the release note regarding the UTF-8 problem with Mysql. Cheers, Stéphane On 7/25/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: The vote has passed with 4 binding +1's from PMC members: Jesse, Wendy, Trygve, me 2 non-binding +1's from committers: Deng, Stephane I started to deployed all things and I'll send an announcement when all will be ready for users. Thanks, Emmanuel Emmanuel Venisse a écrit : Hi, I'd like to do a release of the 1.1-beta-1 This version is very stable and usable in production. Highlights are: - Continuum Profiles definition linked to build definitions. - multi-builddefinitions on a project Release notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10540styleName=Htmlversion=13432 I have staged it in this repo: http://people.apache.org/~evenisse/stage/continuum-repo/ This repo include too the continuum plugin and th xml-rpc client API Standalone version: http://people.apache.org/~evenisse/stage/continuum-repo/org/apache/maven/continuum/continuum-plexus-runtime/1.1-beta-1/ Webapp version: http://people.apache.org/~evenisse/stage/continuum-repo/org/apache/maven/continuum/continuum-webapp/1.1-beta-1/continuum-webapp-1.1-beta-1.war The site will be updated in the next beta, only the download page will be updated for this version. My +1 Emmanuel -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck -- S.Yegge
Re: [vote] release continuum 1.1-beta-1
On 7/25/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: The vote has passed with 4 binding +1's from PMC members: Jesse, Wendy, Trygve, me 2 non-binding +1's from committers: Deng, Stephane Correction: 4 binding +1's from PMC members: Jesse, Stephane, Trygve, Emmanuel Stephane is on the PMC according to [1], and I was just discussing the NOTICE files and didn't vote. :) [1] http://maven.apache.org/team-list.html -- Wendy
Re: [vote] release continuum 1.1-beta-1
Wendy Smoak a écrit : On 7/25/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: The vote has passed with 4 binding +1's from PMC members: Jesse, Wendy, Trygve, me 2 non-binding +1's from committers: Deng, Stephane Correction: 4 binding +1's from PMC members: Jesse, Stephane, Trygve, Emmanuel Stephane is on the PMC according to [1], and I was just discussing the NOTICE files and didn't vote. :) [1] http://maven.apache.org/team-list.html Ooops, sorry
Re: [vote] release continuum 1.1-beta-1
The vote has passed with 4 binding +1's from PMC members: Jesse, Wendy, Trygve, me 2 non-binding +1's from committers: Deng, Stephane I started to deployed all things and I'll send an announcement when all will be ready for users. Thanks, Emmanuel Emmanuel Venisse a écrit : Hi, I'd like to do a release of the 1.1-beta-1 This version is very stable and usable in production. Highlights are: - Continuum Profiles definition linked to build definitions. - multi-builddefinitions on a project Release notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10540styleName=Htmlversion=13432 I have staged it in this repo: http://people.apache.org/~evenisse/stage/continuum-repo/ This repo include too the continuum plugin and th xml-rpc client API Standalone version: http://people.apache.org/~evenisse/stage/continuum-repo/org/apache/maven/continuum/continuum-plexus-runtime/1.1-beta-1/ Webapp version: http://people.apache.org/~evenisse/stage/continuum-repo/org/apache/maven/continuum/continuum-webapp/1.1-beta-1/continuum-webapp-1.1-beta-1.war The site will be updated in the next beta, only the download page will be updated for this version. My +1 Emmanuel
[Announce] Continuum 1.1-beta-1 is released
Hi, The maven/Continuum team is pleased to announce the first beta of Continuum 1.1 Highlights are: * Continuum profiles to define JDK/maven/ANT to use in a build definition * many bug fixes and ui improvements. You can grab the latest release from: http://maven.apache.org/continuum/download.html Next up we are going to have another beta release in a month, or ideally before to have a final release in 1.5 month Anyway, below is the jira release notes for this release. Release Notes - Continuum - Version 1.1-alpha-2 Bug * [CONTINUUM-530] - HTML encode the build output * [CONTINUUM-691] - Build Numbers are obscured by the queuing/building icon * [CONTINUUM-706] - XML-RPC Server does not support addition of BuildDefinitions * [CONTINUUM-709] - Runtime error during recording in datanase * [CONTINUUM-723] - strange trouble on solaris * [CONTINUUM-817] - The generated output in the Working Copy page displays the wrong content * [CONTINUUM-821] - The Project.getBuildResults() method returns an empty list * [CONTINUUM-963] - Derby Database initialization error on Webapp restarts on Jetty * [CONTINUUM-1094] - Continuum does not build with Sun JDK 6 * [CONTINUUM-1119] - Creating a Group with an existing id errors * [CONTINUUM-1191] - editProject: NoSuchMethodException: * [CONTINUUM-1194] - Project is stuck in the Build in Progress state if the associated exception has more than 8192 chars * [CONTINUUM-1226] - Second build definitions on a project is never triggered with CVS * [CONTINUUM-1228] - OgnlException while setting property 'projectGroupId' on redirect * [CONTINUUM-1235] - Continuum 1.1-SNAPSHOT fails to check out projects from CVS when kicking off the build * [CONTINUUM-1241] - Schedule fails to start due to derby database column being too small * [CONTINUUM-1244] - project group name is not validated when left blank in Edit Project Group page, resulting to an error * [CONTINUUM-1308] - error moving projects to a new group * [CONTINUUM-1314] - NPE in DefaultContinuum.java - isInBuildingQueue * [CONTINUUM-1316] - Hitting 'Add' button repetitively in adding an Ant, Shell and Schedule using empty string only accumulates validation prompts in IE browser * [CONTINUUM-1320] - DefaultBuildController.makeAndStoreBuildResult cannot save build result due to maximum size of COMMAND_LINE * [CONTINUUM-1337] - NPE during profile creation * [CONTINUUM-1338] - field name in class org.apache.maven.continuum.model.scm is too small * [CONTINUUM-1339] - Deleting a project group does not delete related build output directories * [CONTINUUM-1340] - After adding a ant project to the default project group (default project group is not displayed) * [CONTINUUM-1341] - Adding a Maven 2 POM from secure SVN on a non-standard port does not work Improvement * [CONTINUUM-774] - Better support for multiprojects * [CONTINUUM-1002] - build email cleanup * [CONTINUUM-1113] - Continuum doesn't work with MySQL * [CONTINUUM-1184] - Ability to pre-configure the Jetty port in conf/plexus.xml * [CONTINUUM-1350] - Documentation on Build profiles New Feature * [CONTINUUM-44] - multiple profiles * [CONTINUUM-614] - Enable auto-refresh for the build results page * [CONTINUUM-761] - Ability to delete results * [CONTINUUM-991] - Add meta refresh header to summary pages * [CONTINUUM-1178] - In Add New Maven 2 Project woudl like opportunity not to load modules * [CONTINUUM-1222] - usage of an alternative maven2-executable * [CONTINUUM-1291] - In a special configuration the report mail can contains false java version used for the build Task * [CONTINUUM-977] - Create web UI tests for Add m1 m2 projects pages Test * [CONTINUUM-978] - add web ui tests for all pages related to schedules * [CONTINUUM-1223] - Ability to choose JVM (export JAVA_HOME) for different projects Wish * [CONTINUUM-1224] - Ability to set MAVEN_OPTS for Maven2 build definitions * [CONTINUUM-1258] - Configure the possibility of resolving or not the search of build executables (maven, ant ...) Emmanuel
[m2-javadoc] MJAVADOC-116 fix?
Hi all! Sorry if I seem rude, but I wish you to know, if you didn't notice it, that I attached a small test case in MJAVADOC-116: http://jira.codehaus.org/browse/MJAVADOC-116 Moreover, this issue has 15 votes, so I think it deserves some attention. I wish to collaborate in the resolution, but I don't know where to start. Thanks Antonio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Julia Antonova/Tumlare is out of the office.
I will be out of the office starting 18-07-2007 and will not return until 01-08-2007. I will respond to your message when I return. Pls. forward all messages to [EMAIL PROTECTED]
Re: [m2-javadoc] MJAVADOC-116 fix?
Hi Antonio, I am aware with it and I already tried it. Thanks! Unfortunately, I have no time to investigate on it. Patch are always welcome! Cheers, Vincent 2007/7/25, Antonio Petrelli [EMAIL PROTECTED]: Hi all! Sorry if I seem rude, but I wish you to know, if you didn't notice it, that I attached a small test case in MJAVADOC-116: http://jira.codehaus.org/browse/MJAVADOC-116 Moreover, this issue has 15 votes, so I think it deserves some attention. I wish to collaborate in the resolution, but I don't know where to start. Thanks Antonio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Julia Antonova/Tumlare is out of the office.
Is there any chance of unsubscribing Ms Antonova? I think we are now all aware just when she's back from vacation... Julia Antonova wrote: I will be out of the office starting 18-07-2007 and will not return until 01-08-2007. I will respond to your message when I return. Pls. forward all messages to [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2-javadoc] MJAVADOC-116 fix?
I spent a little time looking into a similar issue a while ago. The issue seems to be with the inter-module dependency resolution when a plugin uses both @aggregator and @requiresDependencyResolution. http://jira.codehaus.org/browse/MJAVADOC-119 Antonio Petrelli wrote: Hi all! Sorry if I seem rude, but I wish you to know, if you didn't notice it, that I attached a small test case in MJAVADOC-116: http://jira.codehaus.org/browse/MJAVADOC-116 Moreover, this issue has 15 votes, so I think it deserves some attention. I wish to collaborate in the resolution, but I don't know where to start. Thanks Antonio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The stage plugin blues
On 25 Jul 07, at 12:34 PM 25 Jul 07, Dennis Lundberg wrote: It's time again... time for the stage plugin blues :( I just used the stage plugin and this time it failed on me. The previous runs had gone fine. Note that I'm using my locally patched version to be able to supply a different username. Why don't you push that in? This time it got almost all the way. It copied all the artifacts and their checksums and sinatures to the right place and then seemed to hang after that. That's in the middle of running the rename script. That's bad. It's looks like people have different umasks. And I'm not doing any group swizzling when the file is dropped on to the system. We'll need to chmod that rewrite script that gets dumped into the system. I had a look at people.a.o and found something interesting: [EMAIL PROTECTED]:/www/people.apache.org/repo/m2-ibiblio-rsync- repository l total 34 -rw-rw-r-- 1 apsite apcvs 2552 Feb 9 18:50 README.txt drwxrwxr-x 3 jochen apcvs512 Feb 20 03:31 commons- fileupload/ drwxr-xr-x 3 cdoremusapcvs512 Mar 19 19:51 javax/ -rw-rw-r-- 1 jvanzyl apcvs 62 Apr 13 08:52 maven- repository.properties drwxrwxr-x 3 apsite apcvs512 Dec 26 2005 org/ -rw-r--r-- 1 jmcconnell apcvs 1597 Apr 16 16:33 staging- plugin-1-rename.sh -rw-r--r-- 1 jdcasey apcvs823 Jul 17 15:58 staging- plugin-1.0-rename.sh -rw-rw-r-- 1 evenisseapcvs 13233 Jul 25 11:19 staging- plugin-1.1-beta-1-rename.sh -rwxr-xr-x 1 dennisl apcvs855 Jul 25 20:44 staging- plugin-2.1-rename.sh * -rw-r--r-- 1 vsivetonapcvs839 Jul 21 06:37 staging- plugin-2.3-rename.sh It seems that I'm not the first one to run into this :-/ The interesting thing to note here are the file permissions. Except for staging-plugin-2.1-rename.sh (which I changed manually to be able to run it) none of the rename scripts have execute permissions. Don't know if that is needed. Probably not - since we do sh scriptname. Anyway, I then ran the rename script manually: Yah, doens't need to be executable. [EMAIL PROTECTED]:/www/people.apache.org/repo/m2-ibiblio-rsync- repository sh staging-plugin-2.1-rename.sh mv: rename org/apache/maven/plugins/maven-changelog-plugin/2.1.rip to org/apache/maven/plugins/maven-changelog-plugin/2.1/2.1.rip: No such file or directory override rw-r--r-- jvanzyl/apcvs for org/apache/maven/plugins/ maven-changelog-plugin/maven-metadata.xml.md5? (y/n [n]) y override rw-r--r-- jvanzyl/apcvs for org/apache/maven/plugins/ maven-changelog-plugin/maven-metadata.xml? (y/n [n]) y override rw-r--r-- jvanzyl/apcvs for org/apache/maven/plugins/ maven-changelog-plugin/maven-metadata.xml.sha1? (y/n [n]) y The first line had obviously already been run (the artifacts). I confirmed this before running the script manually. After that I had to answer y for each of the metadata files. Is this because of wrong file permissions on those files? Or do we have to add some kind of force switch on the mv command? I can add one. Here are the contents of my rename script: [EMAIL PROTECTED]:/www/people.apache.org/repo/m2-ibiblio-rsync- repository more staging-plugin-2.1-rename.sh mv org/apache/maven/plugins/maven-changelog-plugin/2.1.rip org/ apache/maven/plugins/maven-changelog-plugin/2.1 mv org/apache/maven/plugins/maven-changelog-plugin/maven- metadata.xml.md5.rip org/apache/maven/plugins/maven-changelog- plugin/maven-metadata.xml.md5 mv org/apache/maven/plugins/maven-changelog-plugin/maven- metadata.xml.rip org/apache/maven/plugins/maven-changelog-plugin/ maven-metadata.xml mv org/apache/maven/plugins/maven-changelog-plugin/maven- metadata.xml.sha1.rip org/apache/maven/plugins/maven-changelog- plugin/maven-metadata.xml.sha1 mv org/apache/maven/plugins/maven-metadata.xml.md5.rip org/apache/ maven/plugins/maven-metadata.xml.md5 mv org/apache/maven/plugins/maven-metadata.xml.rip org/apache/maven/ plugins/maven-metadata.xml mv org/apache/maven/plugins/maven-metadata.xml.sha1.rip org/apache/ maven/plugins/maven-metadata.xml.sha1 The good thing here was that I was at least able to manually finish the job. Yah, I leave everything lying around. But this experience shows two things. That we really need an application sitting on the accepting end of a release, and secondly that it probably would have been have been wiser in the repository layout to make a version atomic i.e. everything for a new version sit under one directory instead of multiple. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com --
Re: svn commit: r559221 - /maven/site/trunk/src/site/apt/users/getting-help.apt
Hi Dennis, Sounds very useful for users. Thanks! My only comment is where to put a link! FAQ? Renamed the Getting Support page to it, with a link to mail-lists.html? Cheers, Vincent 2007/7/24, [EMAIL PROTECTED] [EMAIL PROTECTED]: Author: dennisl Date: Tue Jul 24 14:22:55 2007 New Revision: 559221 URL: http://svn.apache.org/viewvc?view=revrev=559221 Log: o First draft of a more user-oriented guide to how users can help us help them. Please comment on this. [SNIP] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Repository purge (MRM-294 and MRM-275)
Wendy Smoak wrote: On 7/25/07, Maria Odea Ching [EMAIL PROTECTED] wrote: I'm trying to fix up MRM-294, and I need your input/comments :-) Should the configuration for the repository purge be for each repository? If so, I think it can be consolidated with the repository scanning schedule and set up as another consumer which would be executed during repository scanning. I think you and Brett have worked out the details, so I just want to confirm that this will be configurable in archiva.xml prior to starting the app. Yep, it'll be configurable in archiva.xml :) Thanks, Deng
The stage plugin blues
It's time again... time for the stage plugin blues :( I just used the stage plugin and this time it failed on me. The previous runs had gone fine. Note that I'm using my locally patched version to be able to supply a different username. This time it got almost all the way. It copied all the artifacts and their checksums and sinatures to the right place and then seemed to hang after that. That's in the middle of running the rename script. I had a look at people.a.o and found something interesting: [EMAIL PROTECTED]:/www/people.apache.org/repo/m2-ibiblio-rsync-repository l total 34 -rw-rw-r-- 1 apsite apcvs 2552 Feb 9 18:50 README.txt drwxrwxr-x 3 jochen apcvs512 Feb 20 03:31 commons-fileupload/ drwxr-xr-x 3 cdoremusapcvs512 Mar 19 19:51 javax/ -rw-rw-r-- 1 jvanzyl apcvs 62 Apr 13 08:52 maven-repository.properties drwxrwxr-x 3 apsite apcvs512 Dec 26 2005 org/ -rw-r--r-- 1 jmcconnell apcvs 1597 Apr 16 16:33 staging-plugin-1-rename.sh -rw-r--r-- 1 jdcasey apcvs823 Jul 17 15:58 staging-plugin-1.0-rename.sh -rw-rw-r-- 1 evenisseapcvs 13233 Jul 25 11:19 staging-plugin-1.1-beta-1-rename.sh -rwxr-xr-x 1 dennisl apcvs855 Jul 25 20:44 staging-plugin-2.1-rename.sh * -rw-r--r-- 1 vsivetonapcvs839 Jul 21 06:37 staging-plugin-2.3-rename.sh It seems that I'm not the first one to run into this :-/ The interesting thing to note here are the file permissions. Except for staging-plugin-2.1-rename.sh (which I changed manually to be able to run it) none of the rename scripts have execute permissions. Don't know if that is needed. Probably not - since we do sh scriptname. Anyway, I then ran the rename script manually: [EMAIL PROTECTED]:/www/people.apache.org/repo/m2-ibiblio-rsync-repository sh staging-plugin-2.1-rename.sh mv: rename org/apache/maven/plugins/maven-changelog-plugin/2.1.rip to org/apache/maven/plugins/maven-changelog-plugin/2.1/2.1.rip: No such file or directory override rw-r--r-- jvanzyl/apcvs for org/apache/maven/plugins/maven-changelog-plugin/maven-metadata.xml.md5? (y/n [n]) y override rw-r--r-- jvanzyl/apcvs for org/apache/maven/plugins/maven-changelog-plugin/maven-metadata.xml? (y/n [n]) y override rw-r--r-- jvanzyl/apcvs for org/apache/maven/plugins/maven-changelog-plugin/maven-metadata.xml.sha1? (y/n [n]) y The first line had obviously already been run (the artifacts). I confirmed this before running the script manually. After that I had to answer y for each of the metadata files. Is this because of wrong file permissions on those files? Or do we have to add some kind of force switch on the mv command? Here are the contents of my rename script: [EMAIL PROTECTED]:/www/people.apache.org/repo/m2-ibiblio-rsync-repository more staging-plugin-2.1-rename.sh mv org/apache/maven/plugins/maven-changelog-plugin/2.1.rip org/apache/maven/plugins/maven-changelog-plugin/2.1 mv org/apache/maven/plugins/maven-changelog-plugin/maven-metadata.xml.md5.rip org/apache/maven/plugins/maven-changelog-plugin/maven-metadata.xml.md5 mv org/apache/maven/plugins/maven-changelog-plugin/maven-metadata.xml.rip org/apache/maven/plugins/maven-changelog-plugin/maven-metadata.xml mv org/apache/maven/plugins/maven-changelog-plugin/maven-metadata.xml.sha1.rip org/apache/maven/plugins/maven-changelog-plugin/maven-metadata.xml.sha1 mv org/apache/maven/plugins/maven-metadata.xml.md5.rip org/apache/maven/plugins/maven-metadata.xml.md5 mv org/apache/maven/plugins/maven-metadata.xml.rip org/apache/maven/plugins/maven-metadata.xml mv org/apache/maven/plugins/maven-metadata.xml.sha1.rip org/apache/maven/plugins/maven-metadata.xml.sha1 The good thing here was that I was at least able to manually finish the job. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT][VOTE] Release maven-changelog-plugin 2.1 (take 2)
Here are the results of this vote: +1: Dennis Lundberg, Jason van Zyl, Stephane Nicoll +1 (non-binding): Fabrice Bellingard +0 (non-binding): Tim O'Brian I'll proceed with the release. Dennis Lundberg wrote: Hi, This is a second try to release maven-changelog-plugin 2.1. All issues in JIRA have been closed, including MCHANGELOG-66 which came in during the last vote. Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11211styleName=Htmlversion=12587 Tag: http://svn.apache.org/repos/asf/maven/plugins/tags/maven-changelog-plugin-2.1/ Staged at: http://people.apache.org/~dennisl/staging-repository-changelog-plugin/ Staged site at: http://people.apache.org/~dennisl/maven-changelog-plugin/index.html The vote will be open for 72 hours. Here is my +1 PS. I forgot to remove the staging repo from the last vote, before I did release:perform. So I did these steps, hope that is correct. If not please let me know. * Nuked the staging-repo on people.a.o * Went down into the directory target/checkout, that was just created * Ran mvn deploy -Prelease -DaltDeploymentRepository=same-as-in-settings.xml -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: APTEditor + Doxia
Hi Math! I recently add a pointer on your tool, so I am aware about your tool. 2007/7/25, Mathieu Avoine [EMAIL PROTECTED]: Hi everyone, I'm developing an Eclipse plugin called APT Editor which, like its name suggests, is an editor/viewer for APT files. Basically, it offers an edit pane to update the contents of the document, and a view pane to preview the formatted version of the document in HTML. It is a great tool for dev. We could have a live renderer. The project page is http://apteditor.sf.net Some people asked me if it was possible to offer the possibility to use Maven Doxia's parser/renderer instead of the original code from pixware. Sounds like a good idea to me, however not being a Doxia developer (not even a Maven user to be honest) I wouldn't know where to look. I'd appreciate if someone could give me some pointers as to how I could integrate Doxia with the APT Editor. To summarize, I'd need to know what libraries to load and what methods to invoke to generate an HTML version of a given APT file into a chosen directory. First, I suggest you to do a smart co of the doxia site http://svn.apache.org/repos/asf/maven/doxia/site We added lot of documentations these days. And another co from the full doxia project The apt parser is here: https://svn.apache.org/repos/asf/maven/doxia/doxia/trunk/doxia-modules/doxia-module-apt FYI, Lukas started an issue to see the differences between pixware APT parser and doxia one: DOXIA-138 Cheers, Vincent Thanks for your help! Math
Re: Repository purge (MRM-294 and MRM-275)
Yep, I'm also saying (b) :) Thanks, Deng Brett Porter wrote: On 25/07/2007, at 9:09 PM, Maria Odea Ching wrote: Sorry, I think I confused you more. Anyway, that's what I meant by #3 :-) So if I specified 5, then it would keep 5 in total of the latest if the snapshot's count in the repo is more than 5. If the total number of that snapshot in the repo didn't reach 5, then it would keep all of them. I think we're saying the same thing - can you just clarify for me are you saying 5 are: a) 1.1-SNAPSHOT, 1.2-SNAPSHOT, 1.3-SNAPSHOT, 1.4-SNAPSHOT, 1.5-SNAPSHOT; or b) 1.1-20070506.121113-1, 1.1-20070506.121113-2, 1.1-20070506.121113-3, 1.1-20070506.121113-4, 1.1-20070506.121113-5 I was thinking it's (b), since (a) is taken care of by the delete anything that's released rule. Cheers, Brett
