Re: [vote] Nicolas de Loof as a committer
+1 :) On Nov 21, 2007 5:08 PM, Brett Porter <[EMAIL PROTECTED]> wrote: > I'd like to call a vote for Nicolas de Loof as a committer, based > primarily on his work for Archiva, but also from being active in the > general Maven community for quite some time. He has been relentlessly > testing and identifying issues and providing patches recently. > > +1 from me > > - Brett > > -- > Brett Porter - [EMAIL PROTECTED] > Blog: http://www.devzuz.org/blogs/bporter/ > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Maven PMC welcomes Deng Ching
Congratulations Deng and welcome! :-) - John On 8/21/07, allan ramirez <[EMAIL PROTECTED]> wrote: > Deng!!! Congratz :D > > On 8/21/07, Maria Odea Ching <[EMAIL PROTECTED]> wrote: > > > > Thanks everyone! :-) > > > > -Deng > > > > Henry Isidro wrote: > > > Wow! Congratulations Deng! > > > > > > On 8/21/07, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > >> Welcome, Deng! > > >> > > >> Congrats - it's great to have you on board. > > >> > > >> Cheers, > > >> Brett > > >> > > >> On 21/08/2007, at 9:19 AM, Wendy Smoak wrote: > > >> > > >> > > >>> I'm pleased to announce that the Maven PMC has voted to add Deng Ching > > >>> to the PMC. Please join me in welcoming her! > > >>> > > >>> -- > > >>> Wendy > > >>> > > >>> - > > >>> 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] > > >> > > >> > > >> > > > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > == > - alramirez > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Olivier Lamy as Continuum committer
+1 On 8/14/07, Fabrice Bellingard <[EMAIL PROTECTED]> wrote: > +1 > > Fabrice > > On 8/13/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I'd like to give to Olivier commit access to Continuum. > > He provided lot of good patches, implemented new features > > (installations/profiles) and help users on the mailing lists > > > > here, my +1 > > > > Emmanuel > > > > > > - > > 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 Maven PMC welcomes Wendy Smoak
Congratulations Wendy and welcome! :-) On 5/29/07, Jesse McConnell <[EMAIL PROTECTED]> wrote: \o/ On 5/28/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote: > Congrats! and Welcome! > > -Joakim > > Brett Porter wrote: > > Hi all, > > > > The Maven PMC has voted to add Wendy Smoak to the PMC. Please join me > > in welcoming her! > > > > Cheers, > > Brett > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- > - Joakim Erdfelt > [EMAIL PROTECTED] > Open Source Software (OSS) Developer > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jesse mcconnell [EMAIL PROTECTED] - 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: [Vote] Move plugin site.xml up to Maven or Shared
+1 [ X ] Move to Maven Pom On 4/3/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: Currently only plugins get a nice looking skin that matches the main maven.apache.org page because the site.xml exists in the plugin project. Other things like shared get a homely looking default skin. I see two options here: 1. Move the site.xml up to the maven pom. This is preferred so that all submodules of maven can get the standard skin and override it if they choose. 2. Copy the site.xml over to the shared pom. This is less intrusive but doesn't cover all submodules that come along. Vote: [ X ] Move to Maven Pom [ ] Copy to shared Vote is open for 72 hrs. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven Ant Tasks 2.0.6
+1 On 4/3/07, John Casey <[EMAIL PROTECTED]> wrote: +1 On 4/2/07, Jason Dillon <[EMAIL PROTECTED]> wrote: > > +1 > > --jason > > > On Apr 1, 2007, at 10:36 AM, Jason van Zyl wrote: > > > Hi, > > > > The staging repository is here: > > > > http://people.apache.org/~jvanzyl/staging-repository/maven-ant- > > tasks-2.0.6/ > > > > The uber jar that people will want to try is here: > > > > http://people.apache.org/~jvanzyl/staging-repository/maven-ant- > > tasks-2.0.6/org/apache/maven/maven-ant-tasks/2.0.6/ > > > > Road map: > > > > http://jira.codehaus.org/secure/IssueNavigator.jspa? > > reset=true&&pid=11533&fixfor=13351&sorter/field=issuekey&sorter/ > > order=DESC > > > > Thanks, > > > > Jason. > > > > > > > > - > > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [WIKI] Archiva Roadmap & Design
Hi Joakim, I'd like to add a web application to deploy new artifacts into the repository (MRM-305). This matches #3 in http://docs.codehaus.org/display/MAVENUSER/Archiva+Requirements. It appears that no one's been doing something like this but I could be mistaken. Also, there are differences in the Design's (http://docs.codehaus.org/display/MAVENUSER/The+Design+of+Archiva) directory structure and the svn directory structure. Are you referring to a different directory structure in the document or is this a plan to reorganize the current grouping of the sub projects? Thanks, John On 3/20/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote: Just a quick note to other Archiva Developers that the Product Roadmap and Design docs are being updated on wiki (Confluence) The Roadmap:: http://docs.codehaus.org/display/MAVENUSER/Archiva+Roadmap I think we might need to split up the roadmap to 1.0-alpha, 1.0-beta, 1.0-rc, and finally 1.0. WDYT? The Design Docs:: http://docs.codehaus.org/display/MAVENUSER/The+Design+of+Archiva As usual, these documents are ongoing and fluid. Comments are appreciated. - Joakim
Re: Link to JavaBlackBelt exam on Maven2?
+1 On 3/10/07, neeraj bisht <[EMAIL PROTECTED]> wrote: gr +3 On 3/10/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > Woo hoo! I have a black belt. > > -Original Message- > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Sent: Friday, March 09, 2007 4:47 AM > To: Maven Developers List > Subject: Re: Link to JavaBlackBelt exam on Maven2? > > +1 > > Emmanuel > > Vincent Massol a écrit : > > Hi everyone, > > > > I'd like to know what people would think about putting a link to > > http://www.javablackbelt.com/QuestionnaireDefDisplay.wwa?questPublicId > > =01559 somewhere on the maven web site. This is the Maven2 exam at > > JavaBlackBelt (it's built collaboratively by contributors). I have > > kicked started it a long time but have not been active on it for a > > very long time. JBB asked me if we could link to it somewhere. > > > > I think it's fair to put a link to it, seen that we're already linking > > books, etc. > > > > WDYT? > > > > Thanks > > -Vincent > > > > > > - > > 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] > > > - > 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: [vote] Trying to use standard versioning
+1 On 3/2/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: Hi, The impetus for this is wanting to release the surefire plugin that has a tiny bug in it. We are versioning our Maven release major.minor.micro so why don't we do the same with our plugin and treat everything like we're going to do small incremental releases like we should be doing. I would like to change all the versions on plugin to follow the major.minor.micro format starting with the surefire plugin. Thanks, Jason. - 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: Release Reports
Hi Robert, Can you have a plexus component for the license header auditing then? I can hook it up to the plugin when it's ready. Only two information are needed: - check result (a boolean value) and - output file where the reports can link to Thanks, John On 1/12/07, robert burrell donkin <[EMAIL PROTECTED]> wrote: On 1/11/07, John Tolentino <[EMAIL PROTECTED]> wrote: > Not yet. Still looking for existing maven plugins that might be doing > this already. Not sure if the verifier plugin could do this for us. there's quite a few wrinkles to release auditing which aren't immediately obvious RAT code's rubbish (i hacked it to automate checking of incubator releases) but i've learnt a lot about what a tool needs to be able to do. > I'm sure everyone would be happy to have new people to help out. perhaps too many around here know me too well to be too excited ;-) - robert - 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: Moving site plugin webapp to another plugin
+1 I'd rather download only what I need. I have 512Kpbs (max). Other people here in Asia have slower connections because of the recent earthquake--fiber optic cables were cut if you haven't heard the news yet. On 1/12/07, Brett Porter <[EMAIL PROTECTED]> wrote: On 12/01/2007, at 1:14 AM, Kenney Westerhof wrote: > I imagine most developers have at least a 2Mbit > downlink You have quite an imagination :) I recently upgraded back up to a 1.5Mbit connection from 512Kbit. It's the highest I can get in my region, and usually is significantly more expensive. I expect there are developers in less prosperous places that don't have even that luxury. - Brett - 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: Release Reports
It appears he'll stick with mojo. But couldn't speak for him. I'll update everyone when I get a patch and have him take a look at it. On 1/12/07, robert burrell donkin <[EMAIL PROTECTED]> wrote: On 1/11/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > On 11 Jan 07, at 3:42 PM 11 Jan 07, robert burrell donkin wrote: > > > On 1/11/07, John Tolentino <[EMAIL PROTECTED]> wrote: > >> Hi Everyone, > > > > hi john > > > >> You can now generate release reports using the maven-swizzle-plugin. > > > > have you implemented your header checked yet? > > > > i'm interested in collaborating on release auditing (in particular > > for apache) > > > > Joakim has scanning tools, and Jochen actually made a RAT plugin over > at Mojo. I would make a plexus component of it I it were to be > integrated. jochen's looking for a new home for that plugin ATM - robert - 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: Release Reports
Was thinking of integrating both docck and rat plugins by calling their execute() methods. Docck throws a MojoFailureException when documentation tests fails and test results could be redirected to a file through the output parameter. So integration with this plugin is straightforward. Although the results of rat-maven-plugin can be redirected to a file, I don't see the same behavior when test failures are encountered. I'll talk to Jochen if we could apply the same behavior to his plugin. On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: On 11 Jan 07, at 3:42 PM 11 Jan 07, robert burrell donkin wrote: > On 1/11/07, John Tolentino <[EMAIL PROTECTED]> wrote: >> Hi Everyone, > > hi john > >> You can now generate release reports using the maven-swizzle-plugin. > > have you implemented your header checked yet? > > i'm interested in collaborating on release auditing (in particular > for apache) > Joakim has scanning tools, and Jochen actually made a RAT plugin over at Mojo. I would make a plexus component of it I it were to be integrated. Jason. > - robert > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release Reports
Not yet. Still looking for existing maven plugins that might be doing this already. Not sure if the verifier plugin could do this for us. I'm sure everyone would be happy to have new people to help out. On 1/12/07, robert burrell donkin <[EMAIL PROTECTED]> wrote: On 1/11/07, John Tolentino <[EMAIL PROTECTED]> wrote: > Hi Everyone, hi john > You can now generate release reports using the maven-swizzle-plugin. have you implemented your header checked yet? i'm interested in collaborating on release auditing (in particular for apache) - robert - 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: Release Reports
By the way, for this example, the changes I made to
maven-source-plugin's POM to generate the report is:
[...]
maven-swizzle-plugin
MPSOURCE
RELEASE
${basedir}/src/site/xdoc/release-report.xml
495351
true
docck-successful.txt
false
license-failed.txt
scm:svn:http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-source-plugin
http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-source-plugin/2.0.2-SNAPSHOT/
http://maven.apache.org/plugins/maven-source-plugin/
On 1/12/07, John Tolentino <[EMAIL PROTECTED]> wrote:
Here's the example report:
http://people.apache.org/~jtolentino/staging_site/maven-swizzle-plugin/release-report.html
On 1/12/07, Mike Perham <[EMAIL PROTECTED]> wrote:
> John, can you give us a sample of what the final report looks like?
>
> On 1/11/07, John Tolentino <[EMAIL PROTECTED]> wrote:
> > Hi Everyone,
> >
> > You can now generate release reports using the maven-swizzle-plugin.
> > Here's the related documentation:
> >
> >
http://people.apache.org/~jtolentino/staging_site/maven-swizzle-plugin/examples/generating-release-report.html
> >
> > This is an implementation on what's discussed in this thread:
> >
> >
http://www.nabble.com/Feedback-Needed-on-Release-Reporting-Tool-tf2843851s177.html
> >
> > Thanks,
> > John
> >
> > -
> > 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]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release Reports
Here's the example report: http://people.apache.org/~jtolentino/staging_site/maven-swizzle-plugin/release-report.html On 1/12/07, Mike Perham <[EMAIL PROTECTED]> wrote: John, can you give us a sample of what the final report looks like? On 1/11/07, John Tolentino <[EMAIL PROTECTED]> wrote: > Hi Everyone, > > You can now generate release reports using the maven-swizzle-plugin. > Here's the related documentation: > > http://people.apache.org/~jtolentino/staging_site/maven-swizzle-plugin/examples/generating-release-report.html > > This is an implementation on what's discussed in this thread: > > http://www.nabble.com/Feedback-Needed-on-Release-Reporting-Tool-tf2843851s177.html > > Thanks, > John > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Release Reports
Hi Everyone, You can now generate release reports using the maven-swizzle-plugin. Here's the related documentation: http://people.apache.org/~jtolentino/staging_site/maven-swizzle-plugin/examples/generating-release-report.html This is an implementation on what's discussed in this thread: http://www.nabble.com/Feedback-Needed-on-Release-Reporting-Tool-tf2843851s177.html Thanks, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Collapse Maven permission groups
Brett Porter wrote: [ ] +1 for the full proposal - collapse all groups (implies a vote for the next option if vote doesn't pass) [X] +1 for the partial proposal - retain subproject access restrictions [ ] 0 abstain from vote [ ] -1 do not alter the current permissions - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Establish a list of emeritus committers
+1 On 1/4/07, Mike Perham <[EMAIL PROTECTED]> wrote: +1 On 1/4/07, Brett Porter <[EMAIL PROTECTED]> wrote: > Hi, > > Vote to operate as > - requiring 2/3rds of the PMC to vote (13), with a majority within > those votes for it to pass (ie, add them all and if the result is > > 0). Other votes would be welcome with reasons as advisory, but not > binding. > - Votes can be changed at any time before result is posted. > - Vote is open for at least 72 hours, completing once enough have > voted after that. > > I propose to establish a list of emeritus committers. > - Someone can request to be made emeritus at any time they want > - They will be listed as past members of the team (we will set up a > special page for this), but have no karma. > - An emeritus committer can request commit access again at any time > they feel they can be active, and a vote will be held to accept them > or not. > - PMC members will not be made emeritus (unless they chose to stand > down from the PMC). > > To start with, anyone who hasn't committed in 12 months will be made > automatically emeritus. ie, this vote is to make the following people > emeritus: > - Pete Kazmier > - Peter Lynch > - Tom Copeland > - Dan Diephouse > - Alex Karasulu > - Ben Walding > - Daniel Rall > - David Eric Pugh > - Geir Magnusson Jr > - Kasper Nielsen > - Kurt Schrader > - Stephane Mor > - Bob McWhirter > - Peter Donald > - Peter Royal > - Johnny R. Ruiz III > > [ ] +1, establish list of emeritus committers > [ ] +0, abstain > [ ] -1, do not establish a list of emeritus committers > > Cheers, > Brett > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Barrie Treloar as a Maven Plugins committer
+1 On 1/4/07, Fabrizio Giustina <[EMAIL PROTECTED]> wrote: +1 fabrizio On 1/4/07, Brett Porter <[EMAIL PROTECTED]> wrote: > I'd like to propose we make Barrie a committer. He has contributed a > lot of small patches, and recently seems to be the "does it work on > Windows?" watchdog. He in particular has done a lot with the assembly > plugin and has also dug into some of the components in Plexus to fix > things where necessary. Very active on the developer and users lists. > > [ ] +1 Yes > [ ] 0 Abstain > [ ] -1 No/not yet > > Cheers, > Brett > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Maven PMC welcomes John Tolentino
Thanks everyone! I'm just happy to work with a diverse group of competent people and be involved in project that I believe in. :-) Regards, John On 1/3/07, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: Welcome John. All my congrats. Arnaud On 1/3/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: > > Congrats John! > > Stéphane > > On 1/3/07, Brett Porter <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > The Maven PMC has voted to add John Tolentino to the PMC. Please > > join me in welcoming him! > > > > Cheers, > > Brett > > > > - > > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Feedback Needed on Release Reporting Tool
I see. So if a project is using CVS, they have to rely on their process having to tag a revision first. I used the revision on the checkout instructions in the mock reports, but like you said, this is only applicable to SVN. On 12/23/06, Brett Porter <[EMAIL PROTECTED]> wrote: I don't think we can really do much special with the label - it just needs to be something that won't change in that system (under the assumption the user doesn't deliberately change it, we can't guard against it). So, an SVN revision number is valid, but so is a URL to a tag, as is a CVS tag, or the equivalent in another system. We can't rely on the system having a unique repository revision (since CVS doesn't). - Brett On 23/12/2006, at 10:18 AM, John Tolentino wrote: > By the way, I need some help with the "labels" for the SCM. I'm not > familiar with other SCM tools and would appreciate some suggestions on > how to generally approach this one. > > On 12/23/06, John Tolentino <[EMAIL PROTECTED]> wrote: >> Here's version 2: >> >> http://people.apache.org/~jtolentino/release-reports/ >> MockReport2.html >> >> You can also find the corresponding xdoc here: >> >> http://people.apache.org/~jtolentino/release-reports/ >> MockReport2.xml >> >> I didn't change the left navigation yet as we're still deciding on >> which reports gets linked to and which will be included within the >> page. >> >> On 12/23/06, John Tolentino <[EMAIL PROTECTED]> wrote: >> > I see what you mean. I'll post the second version of the mock >> report >> > and let's group it from there. :-) >> > >> > On 12/23/06, Brett Porter <[EMAIL PROTECTED]> wrote: >> > > >> > > On 23/12/2006, at 9:13 AM, John Tolentino wrote: >> > > >> > > > >> > > > The vote is an indicator that we're prioritizing what the >> community >> > > > needs/wants to get fixed. I think this would be of interest >> for those >> > > > making a vote for the release, if the issues they want fixed >> will go >> > > > in. >> > > > >> > > >> > > I think these really should be two separate, but related >> reports. The >> > > stable would be: >> > > >> > > - build status report (for developers, from Continuum, things >> that >> > > need immediate attention like broken build, failing tests, >> failing >> > > ITs, failing checks) >> > > - development priorities report (for developers, information >> on what >> > > needs attention at any time) >> > > - release readiness report (for developers, information on >> what needs >> > > attention before a release can be cut) >> > > - changes/release report (for users, information on what was >> in the >> > > last release. Could also include announcement text, download >> links, >> > > etc). >> > > >> > > I think the key differences between 2 and 3 are different >> handling of >> > > JIRA. An issue with 1024 votes needs to be scheduled, but it >> still >> > > shouldn't block a release (eg, it's a feature, and the release in >> > > question is only a point release). However, a scheduled issue >> for the >> > > point release will block that release and so needs to be >> considered. >> > > >> > > WDYT? >> > > >> > > - Brett >> > > >> > > >> - >> > > 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] - 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: Feedback Needed on Release Reporting Tool
By the way, I need some help with the "labels" for the SCM. I'm not familiar with other SCM tools and would appreciate some suggestions on how to generally approach this one. On 12/23/06, John Tolentino <[EMAIL PROTECTED]> wrote: Here's version 2: http://people.apache.org/~jtolentino/release-reports/MockReport2.html You can also find the corresponding xdoc here: http://people.apache.org/~jtolentino/release-reports/MockReport2.xml I didn't change the left navigation yet as we're still deciding on which reports gets linked to and which will be included within the page. On 12/23/06, John Tolentino <[EMAIL PROTECTED]> wrote: > I see what you mean. I'll post the second version of the mock report > and let's group it from there. :-) > > On 12/23/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > On 23/12/2006, at 9:13 AM, John Tolentino wrote: > > > > > > > > The vote is an indicator that we're prioritizing what the community > > > needs/wants to get fixed. I think this would be of interest for those > > > making a vote for the release, if the issues they want fixed will go > > > in. > > > > > > > I think these really should be two separate, but related reports. The > > stable would be: > > > > - build status report (for developers, from Continuum, things that > > need immediate attention like broken build, failing tests, failing > > ITs, failing checks) > > - development priorities report (for developers, information on what > > needs attention at any time) > > - release readiness report (for developers, information on what needs > > attention before a release can be cut) > > - changes/release report (for users, information on what was in the > > last release. Could also include announcement text, download links, > > etc). > > > > I think the key differences between 2 and 3 are different handling of > > JIRA. An issue with 1024 votes needs to be scheduled, but it still > > shouldn't block a release (eg, it's a feature, and the release in > > question is only a point release). However, a scheduled issue for the > > point release will block that release and so needs to be considered. > > > > WDYT? > > > > - Brett > > > > - > > 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: Feedback Needed on Release Reporting Tool
Here's version 2: http://people.apache.org/~jtolentino/release-reports/MockReport2.html You can also find the corresponding xdoc here: http://people.apache.org/~jtolentino/release-reports/MockReport2.xml I didn't change the left navigation yet as we're still deciding on which reports gets linked to and which will be included within the page. On 12/23/06, John Tolentino <[EMAIL PROTECTED]> wrote: I see what you mean. I'll post the second version of the mock report and let's group it from there. :-) On 12/23/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > On 23/12/2006, at 9:13 AM, John Tolentino wrote: > > > > > The vote is an indicator that we're prioritizing what the community > > needs/wants to get fixed. I think this would be of interest for those > > making a vote for the release, if the issues they want fixed will go > > in. > > > > I think these really should be two separate, but related reports. The > stable would be: > > - build status report (for developers, from Continuum, things that > need immediate attention like broken build, failing tests, failing > ITs, failing checks) > - development priorities report (for developers, information on what > needs attention at any time) > - release readiness report (for developers, information on what needs > attention before a release can be cut) > - changes/release report (for users, information on what was in the > last release. Could also include announcement text, download links, > etc). > > I think the key differences between 2 and 3 are different handling of > JIRA. An issue with 1024 votes needs to be scheduled, but it still > shouldn't block a release (eg, it's a feature, and the release in > question is only a point release). However, a scheduled issue for the > point release will block that release and so needs to be considered. > > WDYT? > > - Brett > > - > 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: Feedback Needed on Release Reporting Tool
I see what you mean. I'll post the second version of the mock report and let's group it from there. :-) On 12/23/06, Brett Porter <[EMAIL PROTECTED]> wrote: On 23/12/2006, at 9:13 AM, John Tolentino wrote: > > The vote is an indicator that we're prioritizing what the community > needs/wants to get fixed. I think this would be of interest for those > making a vote for the release, if the issues they want fixed will go > in. > I think these really should be two separate, but related reports. The stable would be: - build status report (for developers, from Continuum, things that need immediate attention like broken build, failing tests, failing ITs, failing checks) - development priorities report (for developers, information on what needs attention at any time) - release readiness report (for developers, information on what needs attention before a release can be cut) - changes/release report (for users, information on what was in the last release. Could also include announcement text, download links, etc). I think the key differences between 2 and 3 are different handling of JIRA. An issue with 1024 votes needs to be scheduled, but it still shouldn't block a release (eg, it's a feature, and the release in question is only a point release). However, a scheduled issue for the point release will block that release and so needs to be considered. WDYT? - Brett - 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: Feedback Needed on Release Reporting Tool
On 12/23/06, Brett Porter <[EMAIL PROTECTED]> wrote: I like it, especially all being on one page as Jason said. Just trying to get to the bottom of the requirements... so this is something that would always be generated and would measure "releasability"? ie, you look at the page and see that there are still 5 issues open for the current version and docck is failing so it can't be released. I like it. That's the idea, so we'd have more regular releases. For now, the person calling for the release would have to generate the site and stage it somewhere for people to see. I agree, I'd basically go for this approach: - table at the top with all the things in the report that are being checked, either with a "PASSED" or "FAILED". - subsections for each thing, linked from the summary. Include actual failures here for quick investigation, but for success (as well as failures) show the link to the actual report I get what you mean. For the JIRA side, I'm not sure about showing # votes. I think that's a separate report that let's you find out what to work on when you aren't even considering a release. Also, I wouldn't show a list of closed issues (though link to it) - that's what the changes report should be for. The vote is an indicator that we're prioritizing what the community needs/wants to get fixed. I think this would be of interest for those making a vote for the release, if the issues they want fixed will go in. I'm thinking this is an aggregation of other reports, so we might consider how best to construct this, but the prototype is a great thing to start using now and work towards that. How does this sound? Working on version 2 of the mock reports now. Will post it again when I'm done consolidating the feedbacks but I'm almost done. - Brett On 19/12/2006, at 2:19 PM, John Tolentino wrote: > Hi Everyone, > > Been working on a tool to generate reports for release candidates and > this is a mock of what it should look like: > http://people.apache.org/~jtolentino/release-reports/MockReport.html > > We can send this generated page to the dev list when we call for a > release. > > I appreciate any feedback so I can improve the reporting (and before I > go further into implementation). > > Thanks, > John > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Feedback Needed on Release Reporting Tool
On 12/20/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: John Just a few small suggestions: In the menu on the far left: Overview Introduction Usage FAQ Examples Generating Votes Report Generating Resolved Issues Report Generating A Custom Report suggest: Overview Introduction Usage FAQs Examples Generating a Votes Report Generating a Resolved Issues Report Generating a Custom Report http://maven.apache.org/ and other plugin sites uses FAQ. I just followed the convention. On the the descriptor for: License Header Results -- relabeling to: Artifact License Info Also, for consistency -- some casing changes: Issues Resolved For This Release -- List of Issues Resolved in this Release List of deliverables -- List of Release Deliverables Ok Lastly, how about using one of the newer Built by Maven logos? This was generated by the maven site plugin from an xdoc file, also used in http://maven.apache.org/ Working now on the second mock version of this report. Thanks for the feedback. :-) --- Original Message --- From: "John Tolentino" <[EMAIL PROTECTED]> To: "Maven Developers List" Date: Tue, 19 Dec 2006 11:19:44 +0800 Subject: Feedback Needed on Release Reporting Tool Hi Everyone, Been working on a tool to generate reports for release candidates and this is a mock of what it should look like: http://people.apache.org/~jtolentino/release-reports/MockReport.html We can send this generated page to the dev list when we call for a release. I appreciate any feedback so I can improve the reporting (and before I go further into implementation). Thanks, John - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Feedback Needed on Release Reporting Tool
On 12/20/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote: Hi, some more comments: First: very nice, extremely handy for voting. Jason van Zyl wrote: > On 18 Dec 06, at 10:19 PM 18 Dec 06, John Tolentino wrote: > >> Hi Everyone, >> >> Been working on a tool to generate reports for release candidates and >> this is a mock of what it should look like: >> http://people.apache.org/~jtolentino/release-reports/MockReport.html >> >> We can send this generated page to the dev list when we call for a >> release. >> >> I appreciate any feedback so I can improve the reporting (and before I >> go further into implementation). >> > > I would link the "Issues Resolved for This Release" to the roadmap in > the issue tracking system. > I agree. Maybe even use a JIRA/whateverIssueSystem embedded report (rss feed for the jira changelog formatted in the site's style). > I would also link each of the resolved issues to the issue tracking > system so you can navigate from the report to the exact issue. Right. Ah! +1 That would be nice. > Maybe some SCM information, what system is being used and the "label" > instead of revision which is SVN specific and a link, if possible, to > that revision in the SCM. For SVN and CVS this is easy with ViewCVS. John's comment about labels: agreed. I only know 1 system that supports labels and that's Clearcase; labels don't specify a fixed version. Perhaps a revision number is better, or a tag/branch. Though all those can change. For CVS, each file has it's own version history, so you should list all source files and their versions, though there's no easy way to check that out. Perhaps a CVS timestamp works best in that case - there can never be 2 commits with the same timestamp AFAIK. > > That's all I can see at first glance. Though I think that getting > everything easy to see in one page is a good goal. We can link to things > like the docck report and the expanded view of deliverables. Get it all > on one page and link. If the results are OK then people most likely > won't look at them, but they can if they want. One clear page of the > state of the release would be nice. Right. I personally don't like raw maven output on such a page - the docck report plugin should just generate a normal report page, preferrably embed it in this page. I'll see what I can do on translating docck return values into a suitable report. What's the 'download link' for? I can see how that's useful for assembly releases, like maven-2.0.x-bin.tar.gz, but for plugins/other loose artifacts, would it point to the jar in the repository? Is that useful? When asking for a vote, we're expected to supply binaries of the release candidate. This URL would point to that staging site. 'Release date: 12/10/1815' wow, i didn't think they had computers back then ;) Agusta Ada Byron's birthday :D (I'd prefer ISO dates or a tztimestamp btw: 2006/12/10 or 2006/12/10 13:14:15 CEST) I see what you mean. Another thought about the docck report: should we list that on the page at all? I think that, and the license header stuff are just plugins that fail the build if the project is not compliant. So we should assume that when those plugins are enabled/used, the project satisfies the requirements. A link to the project (staging)site which already contains all the reports should be enough, right? We've created standards on documenting plugins. I think it would be good for people to know that effort is being made to keep to those standards. Would also make developers mindful that we should help on the documentation of our work as well. Other than the plugins, it's not required, but i know would really be appreciated by its users. On the license, aren't this required by apache since October--or earlier if my memory has failed me? Again, optional for other projects. We could make it an expandable section as well to keep things simple and users interested in the detailed report could click on it for viewing. Also - when the release is made, will this page be available on the project site somewhere? So people can see the project history, examine changelogs, etc. I think it would be handy for people to know what fixes/new features are included. Can be added in the Project Reports section. -- Kenney > > Jason. > >> Thanks, >> John >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail
Re: Publishing plugin sites
I'd like having the version number added. I don't usually know (or keep track of) when something gets released. And it's not always obvious that I'm reading a new feature... and we don't want to stop eager people in contributing documentation ALONG with their code patches right? :-) On 12/8/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote: On 12/8/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > Just a reminder and in case it needs more discussion: we are now > publishing the latest plugin docs from svn, and not waiting for a > release to do it. Can't we add the version of the plugin matching the status of the documentation? Even if we have @since tags, it would be better to clearly state the documentation is for version X.Y-SNAPSHOT. WDYT? Stéphane PS: Personnaly I forgot to add those tags to the EAR plugin and I am probably not the only one. Will fix it ASAP. > > Here's a link to the beginning of this thread, in case anyone missed > it the first time around: > >http://www.nabble.com/Publishing-plugin-sites-t2584348.html > > Thanks, > -- > Wendy > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Feedback Needed on Release Reporting Tool
Hi Everyone, Been working on a tool to generate reports for release candidates and this is a mock of what it should look like: http://people.apache.org/~jtolentino/release-reports/MockReport.html We can send this generated page to the dev list when we call for a release. I appreciate any feedback so I can improve the reporting (and before I go further into implementation). Thanks, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r487139 - /maven/sandbox/plugins/maven-swizzle-plugin/pom.xml
I see. I assume that this (passing the profile) is a temporary fix until a permanent resolution to the circular dependency is found. It feels like I'm doing mvn test -Dmaven.test.skip=true. Thanks for the clarification. On 12/14/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: John Tolentino wrote: > Hi Dennis, > > Thanks for the edits. Docck checks for the two reporting (javadoc and > jxr) plugins though. Should docck exclude the two reporting plugins > from the check/list of errors then? No I don't think so. These two plugins had to be moved to a profile because of the "circular dependency" issue. This is only necessary for our maven-plugins though. Any other project that uses docck does not have this problem. To avoid the errors from docck when working on maven-plugins (i.e org.apache.maven.plugins) you just need to add the profile, like this: mvn -Preporting docck:check > Regards, > John > > On 12/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> Author: dennisl >> Date: Thu Dec 14 00:50:11 2006 >> New Revision: 487139 >> >> URL: http://svn.apache.org/viewvc?view=rev&rev=487139 >> Log: >> o Remove reporting plugins that are available in >> maven-plugin-surrogate-parent. You use "mvn -Preporting ..." to >> activate those plugins. >> >> Modified: >> maven/sandbox/plugins/maven-swizzle-plugin/pom.xml >> >> Modified: maven/sandbox/plugins/maven-swizzle-plugin/pom.xml >> URL: >> http://svn.apache.org/viewvc/maven/sandbox/plugins/maven-swizzle-plugin/pom.xml?view=diff&rev=487139&r1=487138&r2=487139 >> >> == >> >> --- maven/sandbox/plugins/maven-swizzle-plugin/pom.xml (original) >> +++ maven/sandbox/plugins/maven-swizzle-plugin/pom.xml Thu Dec 14 >> 00:50:11 2006 >> @@ -1,83 +1,71 @@ >> - >> - >> -http://maven.apache.org/POM/4.0.0"; >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >> http://maven.apache.org/maven-v4_0_0.xsd";> >> - >> -maven-plugins >> -org.apache.maven.plugins >> -4 >> - >> - 4.0.0 >> - maven-swizzle-plugin >> - maven-plugin >> - 1.0-SNAPSHOT >> - maven-swizzle-plugin Maven Mojo >> - http://maven.apache.org >> - >> - >> - >> -org.apache.maven.plugins >> -maven-site-plugin >> - >> - >> org/codehaus/plexus/swizzle/*.vm >> - >> - >> - >> - >> - >> - >> - >> -org.apache.maven.plugins >> -maven-javadoc-plugin >> - >> - >> -org.apache.maven.plugins >> -maven-jxr-plugin >> - >> - >> - >> - >> - >> - org.apache.maven >> - maven-plugin-api >> - 2.0 >> - >> - >> - junit >> - junit >> - 3.8.1 >> - test >> - >> - >> - org.codehaus.plexus >> - plexus-swizzle >> - 1.0-SNAPSHOT >> - >> - >> - org.apache.maven.shared >> - maven-plugin-testing-harness >> - 1.0-beta-1 >> - test >> - >> - >> - >> + >> + >> +http://maven.apache.org/POM/4.0.0"; >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >> http://maven.apache.org/maven-v4_0_0.xsd";> >> + >> +maven-plugins >> +org.apache.maven.plugins >> +4 >> + >> + 4.0.0 >> + maven-swizzle-plugin >> + maven-plugin >> + 1.0-SNAPSHOT >> + maven-swizzle-plugin Maven Mojo >> + http://maven.apache.org >> + >> + >> + >> +org.apache.maven.plugins >> +maven-site-plugin >> + >> + >> org/codehaus/plexus/swizzle/*.vm >> + >> + >> + >> + >> + >> + >> + org.apache.maven >> + maven-plugin-api >> + 2.0 >> + >> + >> + junit >> + junit >> + 3.8.1 >> + test >> + >> + >> + org.codehaus.plexus >> + plexus-swizzle >> + 1.0-SNAPSHOT >> + >> + >> + org.apache.maven.shared >> + maven-plugin-testing-harness >> + 1.0-beta-1 >> + test >> + >> + >> + >> >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Dennis Lundberg - 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: svn commit: r487139 - /maven/sandbox/plugins/maven-swizzle-plugin/pom.xml
Hi Dennis, Thanks for the edits. Docck checks for the two reporting (javadoc and jxr) plugins though. Should docck exclude the two reporting plugins from the check/list of errors then? Regards, John On 12/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Author: dennisl Date: Thu Dec 14 00:50:11 2006 New Revision: 487139 URL: http://svn.apache.org/viewvc?view=rev&rev=487139 Log: o Remove reporting plugins that are available in maven-plugin-surrogate-parent. You use "mvn -Preporting ..." to activate those plugins. Modified: maven/sandbox/plugins/maven-swizzle-plugin/pom.xml Modified: maven/sandbox/plugins/maven-swizzle-plugin/pom.xml URL: http://svn.apache.org/viewvc/maven/sandbox/plugins/maven-swizzle-plugin/pom.xml?view=diff&rev=487139&r1=487138&r2=487139 == --- maven/sandbox/plugins/maven-swizzle-plugin/pom.xml (original) +++ maven/sandbox/plugins/maven-swizzle-plugin/pom.xml Thu Dec 14 00:50:11 2006 @@ -1,83 +1,71 @@ - - -http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> - -maven-plugins -org.apache.maven.plugins -4 - - 4.0.0 - maven-swizzle-plugin - maven-plugin - 1.0-SNAPSHOT - maven-swizzle-plugin Maven Mojo - http://maven.apache.org - - - -org.apache.maven.plugins -maven-site-plugin - - org/codehaus/plexus/swizzle/*.vm - - - - - - - -org.apache.maven.plugins -maven-javadoc-plugin - - -org.apache.maven.plugins -maven-jxr-plugin - - - - - - org.apache.maven - maven-plugin-api - 2.0 - - - junit - junit - 3.8.1 - test - - - org.codehaus.plexus - plexus-swizzle - 1.0-SNAPSHOT - - - org.apache.maven.shared - maven-plugin-testing-harness - 1.0-beta-1 - test - - - + + +http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> + +maven-plugins +org.apache.maven.plugins +4 + + 4.0.0 + maven-swizzle-plugin + maven-plugin + 1.0-SNAPSHOT + maven-swizzle-plugin Maven Mojo + http://maven.apache.org + + + +org.apache.maven.plugins +maven-site-plugin + + org/codehaus/plexus/swizzle/*.vm + + + + + + + org.apache.maven + maven-plugin-api + 2.0 + + + junit + junit + 3.8.1 + test + + + org.codehaus.plexus + plexus-swizzle + 1.0-SNAPSHOT + + + org.apache.maven.shared + maven-plugin-testing-harness + 1.0-beta-1 + test + + + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release Remote Resources Plugin / JavaDoc Plugin / Source Plugin
+1 On 11/30/06, Jesse McConnell <[EMAIL PROTECTED]> wrote: I like it, nice way to solve the problem I think. I notice the javadoc plugin also addresses a problem I had with it a couple of months ago so I am all for releasing it. +1 jesse On 11/29/06, Jason van Zyl <[EMAIL PROTECTED]> wrote: > I have fixed all the headers and checked them in. > > jason. > > On 29 Nov 06, at 6:54 PM 29 Nov 06, Joakim Erdfelt wrote: > > > Once the headers are fixed, +1 > > > > - Joakim > > > > Daniel Kulp wrote: > >> Jason, > >> > >> The files still don't have the proper Apache header on them. You > >> added > >> the old style (with the copyright date) instead of the new style > >> documented at: > >> http://www.apache.org/legal/src-headers.html > >> Those need to change. > >> > >> Also, the pom.xml files need to have the header as well. Note: > >> there is > >> a bug in maven/jdom that may discard the header at deploy time. > >> Thus, > >> it may need to go INSIDE the tag. > >> > >> The other files in "src" also need it (fml/faq.fml for example, > >> possibly > >> the properties files as well). > >> > >> Dan > >> > >> > >> On Wednesday November 29 2006 10:38 am, Jason van Zyl wrote: > >> > >>> Hi, > >>> > >>> This is a group release to attempt to deal with the licensing > >>> resources that need to be packaged up in all the archives we > >>> distribute. This is, in particular, and attempt to deal with the > >>> JARs > >>> we release. Namely the binary, source, and javadoc JARs we create > >>> with the JAR, Source, and JavaDoc plugins respectively. > >>> > >>> I have created the Remote Resources Plugin which is documented here: > >>> > >>> http://people.apache.org/~jvanzyl/maven-remote-resources-plugin/ > >>> > >>> And I have created a diagram of the process that is currently > >>> happening as a result of the changes I have made to the Source, and > >>> JavaDoc plugins: > >>> > >>> http://idisk.maven.org/jvanzyl/Public/RemoteResourcesHandling.png > >>> > >>> Essentially the remote resources plugins creates a directory of > >>> resources and modifies the POM at runtime so it carries with it the > >>> information about this directory. The other archiving plugins then > >>> look for this resource and insert it into the archives they > >>> create if > >>> found. Ideally the Resource element should have a unique id but the > >>> directory name will do for now. > >>> > >>> You can see here that I've created a profile which will enable the > >>> remote resources plugins and pull down the bundle that contains the > >>> standard license and notice files: > >>> > >>> http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml > >>> > >>> And I have deployed all the plugins above with this tool chain so > >>> you > >>> can see them here: > >>> > >>> http://people.apache.org/repo/m2-snapshot-repository/org/apache/ > >>> maven/ > >>> plugins/maven-remote-resources-plugin/1.0-SNAPSHOT/ > >>> http://people.apache.org/repo/m2-snapshot-repository/org/apache/ > >>> maven/ > >>> plugins/maven-source-plugin/2.0.2-SNAPSHOT/ > >>> http://people.apache.org/repo/m2-snapshot-repository/org/apache/ > >>> maven/ > >>> plugins/maven-javadoc-plugin/2.2-SNAPSHOT/ > >>> > >>> If I can release these plugins then I think we can solve most of the > >>> licensing/resource doldrums. > >>> > >>> Jason. > >>> > >>> > >>> > >>> > >>> > >>> > >>> - > >>> 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] > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jesse mcconnell [EMAIL PROTECTED] - 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: [VOTE] Release MWAR Plugin
afaik, Jason is working on resolving the parent pom issue--this is related to the licensing I mentioned earlier. This will definitely be done before doing the release. On MWAR-60, as I mentioned in http://www.nabble.com/Planning-a-release-of-Maven-War-Plugin-tf2714187s177.html, I suggest we move this to a later date so we don't keep the other resolved issues from being released. On 11/28/06, Fabrice Bellingard <[EMAIL PROTECTED]> wrote: Hi John, what about the issue "http://jira.codehaus.org/browse/MWAR-60";? At the time I commented the issue, I expected some other people to give their point of view on that before working on it. IMHO, this represents a bug that is a regression between 2.0 and 2.0.1, and therefore that needs to be fixed before 2.0.2 is released. What do you think of this? Fabrice. On 11/28/06, John Tolentino <[EMAIL PROTECTED]> wrote: > > Hi Everyone, > > The latest version (2.0.2-SNAPSHOT) of the maven-war-plugin is now > deployed to the snapshot repo. We'll also have the license stuff > resolved before doing any release. > > For your reference of features included in this release: > > http://www.nabble.com/Planning-a-release-of-Maven-War-Plugin-tf2714187s177.html > > I now like to call a vote for Releasing the Maven WAR Plugin. > > Here's my +1. > > Thanks, > John > > - > 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]
[VOTE] Release MWAR Plugin
Hi Everyone, The latest version (2.0.2-SNAPSHOT) of the maven-war-plugin is now deployed to the snapshot repo. We'll also have the license stuff resolved before doing any release. For your reference of features included in this release: http://www.nabble.com/Planning-a-release-of-Maven-War-Plugin-tf2714187s177.html I now like to call a vote for Releasing the Maven WAR Plugin. Here's my +1. Thanks, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] commit access to maven core for Andy Williams
+1 On 11/28/06, John Casey <[EMAIL PROTECTED]> wrote: Late, but here's my +1 Jason van Zyl wrote: > Hi, > > Andy Williams, on his holidays no less, did an amazing job helping me go > up/down the entire stack of Maven of dependencies and getting the new > classworlds/plexus working which he also helped to refactory quite > nicely. He's been creating tons of patches which display core level > knowledge from everything from ClassWorlds to Maven and I'm tired of > applying his patches :-) > > +1 > > Jason. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- John Casey --- Maven Developer (http://maven.apache.org) --- Website: http://www.commonjava.org Blog: http://www.ejlife.net/blogs/john - 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]
Planning a release of Maven War Plugin
Hi Everyone, It's been a while since we've done a release of the maven-war-plugin and there are a number of issues that have been resolved for this version: * [MWAR-63] Online available docu (corresponds to 2.0.2) is not in sync with released version 2.0.1 on ibiblio * [MWAR-48] review plugin documentation * [MWAR-54] add targetPath support on the webResources plugin parameter * [MWAR-55] Overlay war can overwrite main project web.xml * [MWAR-57] Unable to add custom manifest entries to war file via the pom.xml * [MWAR-58] consider the artifact classifier when checking for duplicated artifacts * [MWAR-59] artifact extension set incorrectly in a multi-module build * [MWAR-60] Source Excludes are being applied to WAR file * [MWAR-61] Document how to set manifest classpath and exclude dependency from WEB-INF/lib * [MWAR-67] webResource filtering needs filter * [MWAR-85] FAQ documentation Only two issues are open that are scheduled for the 2.0.2 release. (1) MWAR-63 is related to documentation which will be resolved when we do a release. (2) There isn't any recent activity or easy fix for MWAR-60 so I suggest we reschedule this for a later release. The current dev version builds and passes unit tests as well as the docck plugin. I'll do a deploy of the latest version so everyone could test it then I'll ask for a vote. Thanks, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Checkstyle Plugin
+1 On 11/6/06, Fabrice Bellingard <[EMAIL PROTECTED]> wrote: +1 ! :o) Fabrice. On 11/6/06, Joakim Erdfelt <[EMAIL PROTECTED]> wrote: > > Hi, > > It has been 5 months since the last release of the > maven-checkstyle-plugin, > Since then, there have been numerous fixes to correct various site > generation failures, updated maven ruleset, some cleanup of the report > layout, header refactoring, revised documentation, alignment with plugin > documentation standards, better integration with jxr, and a host of > non-english speaking improvements. > > I would like to call a vote for Releasing the Checkstyle Plugin. > > Here's my +1. > > Standard 72 hour voting window. > > Joakim Erdfelt > [EMAIL PROTECTED] > > - > 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: [VOTE] Release PMD Plugin
+1 On 11/6/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: +1 Emmanuel Joakim Erdfelt a écrit : > Hi, > > It has been 3 months since the last release of the maven-pmd-plugin, > Since then, there has been a refactoring of the excludes logic to bring > harmony to the pmd and cpd reports, been numerous fixes to correct various site > generation failures, updates to allow for build output of pmd violations, updates > to the documentation to bring it inline with the plugin documentation effort, and > the ability to perform a pmd:check based on severity level. > > I would like to call a vote for Releasing the PMD Plugin. > > Here's my +1. > > Standard 72 hour voting window. > > Joakim Erdfelt > [EMAIL PROTECTED] > > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r471487 - in /maven/plugins/trunk/maven-war-plugin/src: main/java/org/apache/maven/plugin/war/AbstractWarMojo.java test/java/org/apache/maven/plugin/war/WarExplodedMojoTest.java
I see. Then a better solution would be the one presented in MWAR-58.
It uses the getClassifier method of the artifact handler.
On 11/6/06, Brett Porter <[EMAIL PROTECTED]> wrote:
The artifact handler can already take care of this by calling
getClassifier on it.
- Brett
On 06/11/2006, at 5:22 AM, [EMAIL PROTECTED] wrote:
> Author: jtolentino
> Date: Sun Nov 5 10:22:37 2006
> New Revision: 471487
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=471487
> Log:
> [MWAR-59] Resolution of ejb artifact final name. Now uses "-client"
> when artifact type is "ejb-client". Fix and test case modification
> submitted by Andreas Wuest.
>
> Modified:
> maven/plugins/trunk/maven-war-plugin/src/main/java/org/apache/
> maven/plugin/war/AbstractWarMojo.java
> maven/plugins/trunk/maven-war-plugin/src/test/java/org/apache/
> maven/plugin/war/WarExplodedMojoTest.java
>
> Modified: maven/plugins/trunk/maven-war-plugin/src/main/java/org/
> apache/maven/plugin/war/AbstractWarMojo.java
> URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-war-
> plugin/src/main/java/org/apache/maven/plugin/war/
> AbstractWarMojo.java?view=diff&rev=471487&r1=471486&r2=471487
> ==
>
> --- maven/plugins/trunk/maven-war-plugin/src/main/java/org/apache/
> maven/plugin/war/AbstractWarMojo.java (original)
> +++ maven/plugins/trunk/maven-war-plugin/src/main/java/org/apache/
> maven/plugin/war/AbstractWarMojo.java Sun Nov 5 10:22:37 2006
> @@ -1025,8 +1025,17 @@
> */
> private String getDefaultFinalName( Artifact artifact )
> {
> -return artifact.getArtifactId() + "-" + artifact.getVersion
> () + "." +
> -artifact.getArtifactHandler().getExtension();
> +String type = artifact.getType();
> +if ( "ejb-client".equals( type ) )
> +{
> +return artifact.getArtifactId() + "-" +
> artifact.getVersion() + "-" + "client" + "." +
> +artifact.getArtifactHandler().getExtension();
> +}
> +else
> +{
> +return artifact.getArtifactId() + "-" +
> artifact.getVersion() + "." +
> + artifact.getArtifactHandler().getExtension();
> +}
> }
>
>
>
> Modified: maven/plugins/trunk/maven-war-plugin/src/test/java/org/
> apache/maven/plugin/war/WarExplodedMojoTest.java
> URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-war-
> plugin/src/test/java/org/apache/maven/plugin/war/
> WarExplodedMojoTest.java?view=diff&rev=471487&r1=471486&r2=471487
> ==
>
> --- maven/plugins/trunk/maven-war-plugin/src/test/java/org/apache/
> maven/plugin/war/WarExplodedMojoTest.java (original)
> +++ maven/plugins/trunk/maven-war-plugin/src/test/java/org/apache/
> maven/plugin/war/WarExplodedMojoTest.java Sun Nov 5 10:22:37 2006
> @@ -405,6 +405,7 @@
> File expectedWebSource2File = new File( webAppDirectory,
> "org/web/app/last-exile.jsp" );
> // final name form is -.
> File expectedEJBArtifact = new File( webAppDirectory, "WEB-
> INF/lib/ejbartifact-0.0-Test.jar" );
> +// File expectedEJBArtifact = new File( webAppDirectory,
> "WEB-INF/lib/ejbartifact-0.0-Test.jar" );
>
> assertTrue( "source files not found: " +
> expectedWebSourceFile.toString(), expectedWebSourceFile.exists() );
> assertTrue( "source files not found: " +
> expectedWebSource2File.toString(), expectedWebSource2File.exists() );
> @@ -478,7 +479,7 @@
> File expectedWebSourceFile = new File( webAppDirectory,
> "pansit.jsp" );
> File expectedWebSource2File = new File( webAppDirectory,
> "org/web/app/last-exile.jsp" );
> // final name form is -.
> -File expectedEJBArtifact = new File( webAppDirectory, "WEB-
> INF/lib/ejbclientartifact-0.0-Test.jar" );
> +File expectedEJBArtifact = new File( webAppDirectory, "WEB-
> INF/lib/ejbclientartifact-0.0-Test-client.jar" );
>
> assertTrue( "source files not found: " +
> expectedWebSourceFile.toString(), expectedWebSourceFile.exists() );
> assertTrue( "source files not found: " +
> expectedWebSource2File.toString(), expectedWebSource2File.exists() );
>
-
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: Releasing Maven 2.0.5
Here's my +1 :-) On 11/2/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: I know it's lame to throw out a pet issue that's unfixed, but I'm going to do it anyway because it's been such a big problem for me. http://jira.codehaus.org/browse/MNG-2340 is a critical regression issue that was introduced in 2.0.4 that has made using mvn eclipse:eclipse (or the Netbeans plugin) nearly unusable for me and my coworkers. I don't know if this issues hasn't gotten enough attention/support/votes because not a lot of people use dependencyManagement with child overrides, or just because it was very difficult to troubleshoot & determine what was happening. But I hate to think that, as long as this problem has been around, it might have to wait for yet another release cycle... - Stephen On 11/2/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote: > Hi, > > I've talked to several users in the past period about issues in maven 2.0.4. > It's getting frustrating to see users having the same problems over and over again > due to bugs that were fixed 5 months ago. > > There are 53 issues resolved for 2.0.5, and Looking at the number of open issues > for 2.0.5, and still 178 to go. With the current rate of resolving issues, 2.0.5 > won't be out at least for another 178 / 53 * 6 months = 20 months. > > I feel that there are enough critical issues resolved for 2.0.5 to warrant > a release. Could we start planning a 2.0.6 release and move most of the open > issues from 2.0.5 to 2.0.6? > > Here's my +1. > > -- Kenney > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com - 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: [vote] commit access for Dan Fabulich
+1 On 10/20/06, Vincent Massol <[EMAIL PROTECTED]> wrote: +1 -Vincent > -Original Message- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: jeudi 19 octobre 2006 16:58 > To: Maven Developers List > Subject: [vote] commit access for Dan Fabulich > > Hi, > > Over the last month Dan has been helping a great deal with the Maven > bootstrap and integration testing which are not for the faint of > heart. He's been great at communicating solutions and has done a lot > of work and submitted many patches to make our bootstrap and > integration testing much easier to understand and use. He's created a > simple Ant bootstrap mechanism, created a nice and clean integration > testing setup and is working on a archetype for ITs to try and make > it easier for others to contribute ITs. Dan also has many pending > patches in JIRA for many other fixes and I wold like him to be able > to integrate those himself. He's demonstrated to me that he > understands Maven very well and is great to work with so I'd like to > invite him to the team. > > +1 > > Jason. ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Demandez à ceux qui savent sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - 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]
Review of maven-release-plugin documentation
maven-release-plugin documentation is now ready for review. Staging site can be found here: http://people.apache.org/~jtolentino/maven-release-plugin/ jira issue: http://jira.codehaus.org/browse/MRELEASE-141 Thanks, John Tolentino - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Proposal] Documenting Maven
John Casey wrote: [SNIP] It will come as no surprise that I think you should encourage more user-contributed documentation. (Aside from submitting patches for the apt source-- that's too high a barrier if you just want to share a plugin configuration example that works for you.) Agreed. I'd like to see if we can find effective ways to bring people deeper into the Maven community. IMO, we do need to start focusing more on making the answers to common questions available in a persistent format. Not just a FAQ, but good documentation, shared experiences, and examples...all of which should stick around longer than the time taken to replace the 100-item queue on gmail. :-) The "real world" examples you want for each plugin might come from the early adopters who are using snapshots... but we need a visible place to store these, or no one knows they exist. As I mentioned in another thread, I'd really like to see a link to a MAVENUSER wiki page for each plugin. I think this is a pretty good idea. Sort of linking in an interactive space to each part of static reference... Cheers, John +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r410201 - /maven/repository-manager/trunk/maven-repository-artifact-applet/pom.xml
The default is snapshots are disabled. Checked the http://www.ibiblio.org/maven2/org/apache/apache/1/apache-1.pom and maven-repository-artifact-applet wasn't downloading the snapshot maven-jar-plugin. Brett Porter wrote: That's the default? [EMAIL PROTECTED] wrote: Author: jtolentino Date: Tue May 30 00:09:00 2006 New Revision: 410201 URL: http://svn.apache.org/viewvc?rev=410201&view=rev Log: Enabled plugin snapshot downloading. Modified: maven/repository-manager/trunk/maven-repository-artifact-applet/pom.xml Modified: maven/repository-manager/trunk/maven-repository-artifact-applet/pom.xml URL: http://svn.apache.org/viewvc/maven/repository-manager/trunk/maven-repository-artifact-applet/pom.xml?rev=410201&r1=410200&r2=410201&view=diff == --- maven/repository-manager/trunk/maven-repository-artifact-applet/pom.xml (original) +++ maven/repository-manager/trunk/maven-repository-artifact-applet/pom.xml Tue May 30 00:09:00 2006 @@ -39,6 +39,9 @@ apache.snapshots Apache Snapshot Repository http://svn.apache.org/maven-snapshot-repository + +true + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Standards for documenting plugins
Hi, We're creating APT docs for the plugins. Currently there are no standards on the format and content of a maven plugin site documentation. Anybody have suggestions? Regards, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [result] Re: [vote] John Tolentino as a Maven Plugins and Repository Manager committer
Thanks everyone! :-) Regards, John Brett Porter wrote: Welcome, John! +1: Brett, Jason, John, Carlos, Lukas, Vincent M, Vincent S, Edwin, Stephane, Emmanuel, Arnaud, Fabrizio, Brian non-binding +1: Brian K. Wallace Brett Porter wrote: Hi, John has been helping out on the users list, plugins and the repository manager for some time. I'd like to propose we give him commit access. [ ] +1 [ ] +0 [ ] -1 Cheers, Brett - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-99) Use RepositoryIndexSearchLayer for searching in Packages
Use RepositoryIndexSearchLayer for searching in Packages Key: MRM-99 URL: http://jira.codehaus.org/browse/MRM-99 Project: Maven Repository Manager Type: Bug Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Update PackageSearchAction to use RepositoryIndexSearchLayer and change search result page to use SearchResult class. -- 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: (MRM-98) Use the plexus configuration for index and repository path
Use the plexus configuration for index and repository path -- Key: MRM-98 URL: http://jira.codehaus.org/browse/MRM-98 Project: Maven Repository Manager Type: Improvement Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Attachments: maven-repository-webapp.diff Use same plexus configuration code in GeneralSearch for PackageSearchAction. -- 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: (MRM-81) Search web user interface
[ http://jira.codehaus.org/browse/MRM-81?page=all ] John Tolentino updated MRM-81: -- Attachment: MRM-81-maven-repository-webapp.diff > Search web user interface > - > > Key: MRM-81 > URL: http://jira.codehaus.org/browse/MRM-81 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-81-maven-repository-indexer.diff, > MRM-81-maven-repository-webapp.diff > > Original Estimate: 16 hours >Time Spent: 14 hours > Remaining: 2 hours > > General search page and search result page. -- 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: (MRM-81) Search web user interface
[ http://jira.codehaus.org/browse/MRM-81?page=all ] John Tolentino updated MRM-81: -- Attachment: (was: MRM-81-maven-repository-webapp.diff) > Search web user interface > - > > Key: MRM-81 > URL: http://jira.codehaus.org/browse/MRM-81 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-81-maven-repository-indexer.diff, > MRM-81-maven-repository-webapp.diff > > Original Estimate: 16 hours >Time Spent: 14 hours > Remaining: 2 hours > > General search page and search result page. -- 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: (MRM-81) Search web user interface
[ http://jira.codehaus.org/browse/MRM-81?page=all ] John Tolentino updated MRM-81: -- Attachment: MRM-81-maven-repository-webapp.diff > Search web user interface > - > > Key: MRM-81 > URL: http://jira.codehaus.org/browse/MRM-81 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-81-maven-repository-indexer.diff, > MRM-81-maven-repository-webapp.diff > > Original Estimate: 16 hours >Time Spent: 6 hours > Remaining: 10 hours > > General search page and search result page. -- 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: (MRM-81) Search web user interface
[ http://jira.codehaus.org/browse/MRM-81?page=all ] John Tolentino updated MRM-81: -- Attachment: MRM-81-maven-repository-indexer.diff > Search web user interface > - > > Key: MRM-81 > URL: http://jira.codehaus.org/browse/MRM-81 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-81-maven-repository-indexer.diff > > Original Estimate: 16 hours >Time Spent: 6 hours > Remaining: 10 hours > > General search page and search result page. -- 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] Reopened: (MRM-41) discover standalone POMs
[ http://jira.codehaus.org/browse/MRM-41?page=all ] John Tolentino reopened MRM-41: --- Test data which was included in the patch was not applied to committed code. This causes build failure on clean checkout. Please reapply patch. > discover standalone POMs > > > Key: MRM-41 > URL: http://jira.codehaus.org/browse/MRM-41 > Project: Maven Repository Manager > Type: Task > Components: discovery > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-41-maven-repository-discovery.diff, > MRM-41-maven-repository-discovery.diff, > MRM-41-maven-repository-discovery.diff, repository-manager.diff > > Time Spent: 21 hours >Remaining: 0 minutes > > where the pom is the artifact -- 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: (MRM-41) discover standalone POMs
[ http://jira.codehaus.org/browse/MRM-41?page=all ] John Tolentino updated MRM-41: -- Attachment: MRM-41-maven-repository-discovery.diff > discover standalone POMs > > > Key: MRM-41 > URL: http://jira.codehaus.org/browse/MRM-41 > Project: Maven Repository Manager > Type: Task > Components: discovery > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-41-maven-repository-discovery.diff, > MRM-41-maven-repository-discovery.diff, > MRM-41-maven-repository-discovery.diff, repository-manager.diff > > Time Spent: 18 hours >Remaining: 0 minutes > > where the pom is the artifact -- 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] Closed: (MRM-70) Browse by Group/Artifact/Version
[ http://jira.codehaus.org/browse/MRM-70?page=all ] John Tolentino closed MRM-70: - Resolution: Duplicate Code already exists (see MRM-74). > Browse by Group/Artifact/Version > > > Key: MRM-70 > URL: http://jira.codehaus.org/browse/MRM-70 > Project: Maven Repository Manager > Type: Task > Components: browser > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > > Original Estimate: 8 hours > Remaining: 8 hours > -- 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: (MRM-38) add a background task scheduler
[ http://jira.codehaus.org/browse/MRM-38?page=all ] John Tolentino updated MRM-38: -- Attachment: MRM-38-maven-repository-webapp.diff > add a background task scheduler > --- > > Key: MRM-38 > URL: http://jira.codehaus.org/browse/MRM-38 > Project: Maven Repository Manager > Type: New Feature > Components: scheduling > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-38-maven-repository-webapp.diff, > maven-repository-webapp.diff > > Time Spent: 6 hours, 3 minutes >Remaining: 0 minutes > > we need to be able to schedule tasks. We should use quartz, and reuse code > from Continuum that does similarly. > There needs to be a way to add/remove/configure scheduled tasks such as > indexing, report execution and syncing -- 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: (MRM-38) add a background task scheduler
[ http://jira.codehaus.org/browse/MRM-38?page=all ] John Tolentino updated MRM-38: -- Attachment: maven-repository-webapp.diff > add a background task scheduler > --- > > Key: MRM-38 > URL: http://jira.codehaus.org/browse/MRM-38 > Project: Maven Repository Manager > Type: New Feature > Components: scheduling > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: maven-repository-webapp.diff > > Time Spent: 3 hours, 3 minutes >Remaining: 3 hours > > we need to be able to schedule tasks. We should use quartz, and reuse code > from Continuum that does similarly. > There needs to be a way to add/remove/configure scheduled tasks such as > indexing, report execution and syncing -- 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: (MRM-83) Reports should be passed a listener to be able to log their discoveries
[ http://jira.codehaus.org/browse/MRM-83?page=all ] John Tolentino updated MRM-83: -- Assign To: John Tolentino Due Date: 22/Feb/06 > Reports should be passed a listener to be able to log their discoveries > --- > > Key: MRM-83 > URL: http://jira.codehaus.org/browse/MRM-83 > Project: Maven Repository Manager > Type: Task > Components: reporting > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > > Original Estimate: 16 hours > Remaining: 16 hours > > - There will be different types of listeners passed in - web page, mail, etc. > - There may be more than one listener, which can be achieved through an > aggregate listener rather than crowding the interface with collections -- 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: (MRM-70) Browse by Group/Artifact/Version
[ http://jira.codehaus.org/browse/MRM-70?page=all ] John Tolentino updated MRM-70: -- Due Date: 17/Feb/06 > Browse by Group/Artifact/Version > > > Key: MRM-70 > URL: http://jira.codehaus.org/browse/MRM-70 > Project: Maven Repository Manager > Type: Task > Components: browser > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > > Original Estimate: 8 hours > Remaining: 8 hours > -- 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: (MRM-71) Traverse Dependencies
[ http://jira.codehaus.org/browse/MRM-71?page=all ] John Tolentino updated MRM-71: -- Due Date: 20/Feb/06 > Traverse Dependencies > - > > Key: MRM-71 > URL: http://jira.codehaus.org/browse/MRM-71 > Project: Maven Repository Manager > Type: Task > Components: browser > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > > Original Estimate: 8 hours > Remaining: 8 hours > -- 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: (MRM-58) create a search result class for returning from search
[ http://jira.codehaus.org/browse/MRM-58?page=all ] John Tolentino updated MRM-58: -- Due Date: 15/Feb/06 Remaining Estimate: 6 hours Original Estimate: 6 hours > create a search result class for returning from search > -- > > Key: MRM-58 > URL: http://jira.codehaus.org/browse/MRM-58 > Project: Maven Repository Manager > Type: Bug > Components: indexing > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > > Original Estimate: 6 hours > Remaining: 6 hours > > instead of returning artifacts, return a search result class including > artifact, classes, packages and files -- 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: (MRM-38) add a background task scheduler
[ http://jira.codehaus.org/browse/MRM-38?page=comments#action_58529 ] John Tolentino commented on MRM-38: --- Created a components.xml based on the one existing in Continuum. This components.xml uses org.codehaus.plexus.scheduler.Scheduler with DefaultScheduler of the same package for its implementation. Still need to know which properties are configurable for MRM scheduling. > add a background task scheduler > --- > > Key: MRM-38 > URL: http://jira.codehaus.org/browse/MRM-38 > Project: Maven Repository Manager > Type: New Feature > Components: scheduling > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > > Time Spent: 2 hours, 3 minutes >Remaining: 4 hours > > we need to be able to schedule tasks. We should use quartz, and reuse code > from Continuum that does similarly. > There needs to be a way to add/remove/configure scheduled tasks such as > indexing, report execution and syncing -- 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: (MRM-38) add a background task scheduler
[ http://jira.codehaus.org/browse/MRM-38?page=all ] John Tolentino updated MRM-38: -- Due Date: 10/Feb/06 > add a background task scheduler > --- > > Key: MRM-38 > URL: http://jira.codehaus.org/browse/MRM-38 > Project: Maven Repository Manager > Type: New Feature > Components: scheduling > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > > Time Spent: 2 hours, 3 minutes >Remaining: 4 hours > > we need to be able to schedule tasks. We should use quartz, and reuse code > from Continuum that does similarly. > There needs to be a way to add/remove/configure scheduled tasks such as > indexing, report execution and syncing -- 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: (MRM-75) Caching web user interface
[ http://jira.codehaus.org/browse/MRM-75?page=all ] John Tolentino updated MRM-75: -- Remaining Estimate: 1 hour (was: 16 hours) Original Estimate: 1 hour (was: 16 hours) I agree. Forgot that the java code had a seperate jira issue. Adjusted the estimate. > Caching web user interface > -- > > Key: MRM-75 > URL: http://jira.codehaus.org/browse/MRM-75 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 1 hour > Remaining: 1 hour > -- 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: (MRM-78) Repository Indexing web user interface
[ http://jira.codehaus.org/browse/MRM-78?page=comments#action_57933 ] John Tolentino commented on MRM-78: --- This is for manual reindexing of artifacts. Also for setting the schedule when the discovery should reindex. > Repository Indexing web user interface > -- > > Key: MRM-78 > URL: http://jira.codehaus.org/browse/MRM-78 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 8 hours > Remaining: 8 hours > -- 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: (MRM-76) Front End web user interface for configuring multiple repository proxy
[ http://jira.codehaus.org/browse/MRM-76?page=all ] John Tolentino updated MRM-76: -- Summary: Front End web user interface for configuring multiple repository proxy (was: Front End web user interface) Web app for configuring multiple repository proxy. > Front End web user interface for configuring multiple repository proxy > -- > > Key: MRM-76 > URL: http://jira.codehaus.org/browse/MRM-76 > Project: Maven Repository Manager > Type: Task > Reporter: John Tolentino > > > For configuring multiple repository proxy. -- 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: (MRM-75) Caching web user interface
[ http://jira.codehaus.org/browse/MRM-75?page=comments#action_57931 ] John Tolentino commented on MRM-75: --- Yes. This is exactly that. A page with a "flush cache" button. This issue was created so we won't forget the requirement. > Caching web user interface > -- > > Key: MRM-75 > URL: http://jira.codehaus.org/browse/MRM-75 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 16 hours > Remaining: 16 hours > -- 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: (MRM-74) Browse web user interface
[ http://jira.codehaus.org/browse/MRM-74?page=comments#action_57920 ] John Tolentino commented on MRM-74: --- MRM-70 is specific to back-end (java class). MRM-74 is for the web component that links the java code to a web app user interface. > Browse web user interface > - > > Key: MRM-74 > URL: http://jira.codehaus.org/browse/MRM-74 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 1 day, 16 hours > Remaining: 1 day, 16 hours > -- 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: (MRM-87) Place a lockfile to prevent repository operations when there is a long ongoing process
[ http://jira.codehaus.org/browse/MRM-87?page=all ] John Tolentino updated MRM-87: -- Version: 1.0-alpha-1 Component: repository interface Remaining Estimate: 1 day Original Estimate: 1 day > Place a lockfile to prevent repository operations when there is a long > ongoing process > -- > > Key: MRM-87 > URL: http://jira.codehaus.org/browse/MRM-87 > Project: Maven Repository Manager > Type: Task > Components: repository interface > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 1 day > Remaining: 1 day > > Place a lockfile in the root of the repository that prevents deployment or > other repository operations when there is a long, ongoing process. -- 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: (MRM-86) The operations on the repository must be transactional
[ http://jira.codehaus.org/browse/MRM-86?page=all ] John Tolentino updated MRM-86: -- Remaining Estimate: 20 hours Original Estimate: 20 hours > The operations on the repository must be transactional > -- > > Key: MRM-86 > URL: http://jira.codehaus.org/browse/MRM-86 > Project: Maven Repository Manager > Type: Task > Components: repository interface > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 20 hours > Remaining: 20 hours > -- 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: (MRM-85) Repository access should be done through Wagon
[ http://jira.codehaus.org/browse/MRM-85?page=all ] John Tolentino updated MRM-85: -- Remaining Estimate: 8 hours Original Estimate: 8 hours > Repository access should be done through Wagon > -- > > Key: MRM-85 > URL: http://jira.codehaus.org/browse/MRM-85 > Project: Maven Repository Manager > Type: Task > Components: repository interface > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 8 hours > Remaining: 8 hours > > Most likely using the file wagon. > When wagon doesn't handle something, we need to make a call on whether to add > it to its interface, or write custom handling based on local filesystem. -- 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: (MRM-87) Place a lockfile to prevent repository operations when there is a long ongoing process
Place a lockfile to prevent repository operations when there is a long ongoing process -- Key: MRM-87 URL: http://jira.codehaus.org/browse/MRM-87 Project: Maven Repository Manager Type: Task Reporter: John Tolentino Place a lockfile in the root of the repository that prevents deployment or other repository operations when there is a long, ongoing process. -- 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: (MRM-86) The operations on the repository must be transactional
The operations on the repository must be transactional -- Key: MRM-86 URL: http://jira.codehaus.org/browse/MRM-86 Project: Maven Repository Manager Type: Task Components: repository interface Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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: (MRM-85) Repository access should be done through Wagon
Repository access should be done through Wagon -- Key: MRM-85 URL: http://jira.codehaus.org/browse/MRM-85 Project: Maven Repository Manager Type: Task Components: repository interface Versions: 1.0-alpha-1 Reporter: John Tolentino Most likely using the file wagon. When wagon doesn't handle something, we need to make a call on whether to add it to its interface, or write custom handling based on local filesystem. -- 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: (MRM-84) Basic statistics
[ http://jira.codehaus.org/browse/MRM-84?page=all ] John Tolentino updated MRM-84: -- Remaining Estimate: 16 hours Original Estimate: 16 hours > Basic statistics > > > Key: MRM-84 > URL: http://jira.codehaus.org/browse/MRM-84 > Project: Maven Repository Manager > Type: Task > Components: reporting > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 16 hours > Remaining: 16 hours > -- 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: (MRM-83) Reports should be passed a listener to be able to log their discoveries
[ http://jira.codehaus.org/browse/MRM-83?page=all ] John Tolentino updated MRM-83: -- Remaining Estimate: 16 hours Original Estimate: 16 hours > Reports should be passed a listener to be able to log their discoveries > --- > > Key: MRM-83 > URL: http://jira.codehaus.org/browse/MRM-83 > Project: Maven Repository Manager > Type: Task > Components: reporting > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 16 hours > Remaining: 16 hours > > - There will be different types of listeners passed in - web page, mail, etc. > - There may be more than one listener, which can be achieved through an > aggregate listener rather than crowding the interface with collections -- 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: (MRM-82) Reports should be components of their own so that new ones can be dropped in
[ http://jira.codehaus.org/browse/MRM-82?page=all ] John Tolentino updated MRM-82: -- Remaining Estimate: 16 hours Original Estimate: 16 hours > Reports should be components of their own so that new ones can be dropped in > > > Key: MRM-82 > URL: http://jira.codehaus.org/browse/MRM-82 > Project: Maven Repository Manager > Type: Task > Components: reporting > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 16 hours > Remaining: 16 hours > -- 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: (MRM-83) Reports should be passed a listener to be able to log their discoveries
Reports should be passed a listener to be able to log their discoveries --- Key: MRM-83 URL: http://jira.codehaus.org/browse/MRM-83 Project: Maven Repository Manager Type: Task Components: reporting Versions: 1.0-alpha-1 Reporter: John Tolentino - There will be different types of listeners passed in - web page, mail, etc. - There may be more than one listener, which can be achieved through an aggregate listener rather than crowding the interface with collections -- 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: (MRM-84) Basic statistics
Basic statistics Key: MRM-84 URL: http://jira.codehaus.org/browse/MRM-84 Project: Maven Repository Manager Type: Task Components: reporting Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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: (MRM-82) Reports should be components of their own so that new ones can be dropped in
Reports should be components of their own so that new ones can be dropped in Key: MRM-82 URL: http://jira.codehaus.org/browse/MRM-82 Project: Maven Repository Manager Type: Task Components: reporting Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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: (MRM-79) Repository Interface web user interface
[ http://jira.codehaus.org/browse/MRM-79?page=all ] John Tolentino updated MRM-79: -- Remaining Estimate: 4 hours Original Estimate: 4 hours > Repository Interface web user interface > --- > > Key: MRM-79 > URL: http://jira.codehaus.org/browse/MRM-79 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 4 hours > Remaining: 4 hours > > Manual removal of lockfile can be done here. -- 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: (MRM-77) Reporting web user interface
[ http://jira.codehaus.org/browse/MRM-77?page=all ] John Tolentino updated MRM-77: -- Remaining Estimate: 1 day, 16 hours Original Estimate: 1 day, 16 hours > Reporting web user interface > > > Key: MRM-77 > URL: http://jira.codehaus.org/browse/MRM-77 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 1 day, 16 hours > Remaining: 1 day, 16 hours > -- 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: (MRM-75) Caching web user interface
[ http://jira.codehaus.org/browse/MRM-75?page=all ] John Tolentino updated MRM-75: -- Remaining Estimate: 16 hours Original Estimate: 16 hours > Caching web user interface > -- > > Key: MRM-75 > URL: http://jira.codehaus.org/browse/MRM-75 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 16 hours > Remaining: 16 hours > -- 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: (MRM-78) Repository Indexing web user interface
[ http://jira.codehaus.org/browse/MRM-78?page=all ] John Tolentino updated MRM-78: -- Remaining Estimate: 8 hours Original Estimate: 8 hours > Repository Indexing web user interface > -- > > Key: MRM-78 > URL: http://jira.codehaus.org/browse/MRM-78 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 8 hours > Remaining: 8 hours > -- 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: (MRM-74) Browse web user interface
[ http://jira.codehaus.org/browse/MRM-74?page=all ] John Tolentino updated MRM-74: -- Remaining Estimate: 1 day, 16 hours Original Estimate: 1 day, 16 hours > Browse web user interface > - > > Key: MRM-74 > URL: http://jira.codehaus.org/browse/MRM-74 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 1 day, 16 hours > Remaining: 1 day, 16 hours > -- 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: (MRM-73) Artifact Management web user interface
[ http://jira.codehaus.org/browse/MRM-73?page=all ] John Tolentino updated MRM-73: -- Remaining Estimate: 18 hours Original Estimate: 18 hours > Artifact Management web user interface > -- > > Key: MRM-73 > URL: http://jira.codehaus.org/browse/MRM-73 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 18 hours > Remaining: 18 hours > -- 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: (MRM-81) Search web user interface
[ http://jira.codehaus.org/browse/MRM-81?page=all ] John Tolentino updated MRM-81: -- Remaining Estimate: 16 hours Original Estimate: 16 hours > Search web user interface > - > > Key: MRM-81 > URL: http://jira.codehaus.org/browse/MRM-81 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 16 hours > Remaining: 16 hours > > General search page and search result page. -- 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: (MRM-81) Search web user interface
Search web user interface - Key: MRM-81 URL: http://jira.codehaus.org/browse/MRM-81 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino General search page and search result page. -- 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: (MRM-80) Scheduling web user interface
[ http://jira.codehaus.org/browse/MRM-80?page=all ] John Tolentino updated MRM-80: -- Remaining Estimate: 8 hours Original Estimate: 8 hours > Scheduling web user interface > - > > Key: MRM-80 > URL: http://jira.codehaus.org/browse/MRM-80 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 8 hours > Remaining: 8 hours > > Should allow user to set schedule for checking of repository changes. -- 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: (MRM-80) Scheduling web user interface
Scheduling web user interface - Key: MRM-80 URL: http://jira.codehaus.org/browse/MRM-80 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Should allow user to set schedule for checking of repository changes. -- 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: (MRM-79) Repository Interface web user interface
Repository Interface web user interface --- Key: MRM-79 URL: http://jira.codehaus.org/browse/MRM-79 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Manual removal of lockfile can be done here. -- 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: (MRM-78) Repository Indexing web user interface
Repository Indexing web user interface -- Key: MRM-78 URL: http://jira.codehaus.org/browse/MRM-78 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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: (MRM-77) Reporting web user interface
Reporting web user interface Key: MRM-77 URL: http://jira.codehaus.org/browse/MRM-77 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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: (MRM-76) Front End web user interface
Front End web user interface Key: MRM-76 URL: http://jira.codehaus.org/browse/MRM-76 Project: Maven Repository Manager Type: Task Reporter: John Tolentino For configuring multiple repository proxy. -- 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: (MRM-75) Caching web user interface
Caching web user interface -- Key: MRM-75 URL: http://jira.codehaus.org/browse/MRM-75 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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: (MRM-74) Browse web user interface
Browse web user interface - Key: MRM-74 URL: http://jira.codehaus.org/browse/MRM-74 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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: (MRM-73) Artifact Management web user interface
Artifact Management web user interface -- Key: MRM-73 URL: http://jira.codehaus.org/browse/MRM-73 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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: (MRM-72) Administration web user interface
[ http://jira.codehaus.org/browse/MRM-72?page=all ] John Tolentino updated MRM-72: -- Remaining Estimate: 8 hours Original Estimate: 8 hours > Administration web user interface > - > > Key: MRM-72 > URL: http://jira.codehaus.org/browse/MRM-72 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 8 hours > Remaining: 8 hours > -- 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: (MRM-72) Administration web user interface
Administration web user interface - Key: MRM-72 URL: http://jira.codehaus.org/browse/MRM-72 Project: Maven Repository Manager Type: Task Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino -- 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]
