Re: [mojo-dev] [DISCUSSION] Relax the procedure to push for 1.0

ble to create Mojo > projects. > Brett, are you always monitoring these tasks ? > > > On Fri, Sep 5, 2014 at 11:18 AM, Arnaud Héritier > wrote: > I just checked and there are very few admins around Ben Walding to manage > administrative tasks > * Bob McWhirter > * Bret

Re: [mojo-dev] codehaus svn auth errors

--------- > To unsubscribe from this list, please visit: > >http://xircles.codehaus.org/manage_email > > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

[mojo-dev] Re: [mojo-scm] [14684] trunk/mojo/exec-maven-plugin: Remove File.canExecute(), because this is a JDK6 feature, while this plugin is still based on JDK1.4

{ > -getLog().debug( "Can't execute " + > f.getAbsolutePath() + "; continue to search" ); > -} > +exec = ex; > +break; > } > } > } > > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter

[mojo-dev] Re: [mojo-scm] [15065] trunk/sandbox/mrm/: Mock Repository Manager

itory Manager > Added Paths > > • trunk/sandbox/mrm/ > Diff > > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/

Re: [mojo-dev] [mojo-scm] [15065] trunk/sandbox/mrm/: Mock Repository Manager

- Stephen > > --- > Sent from my Android phone, so random spelling mistakes, random nonsense > words and other nonsense are a direct result of using swype to type on the > screen > > On 13 Nov 2011 03:34, "Brett Porter" wrote: > What will you use for the issue key on JI

Re: [mojo-dev] [VOTE] Options for dealing with inactive projects (was Re: Project status)

; imagine that both Mark Struberg and I will take care of the sql-maven-plugin > If I get the chance I'll complete the list with plugins. > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter

Re: [mojo-dev] appassembler-plugin - beta Release ?

> > >> -- > > >> SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893 > > >> Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029 > > >> Hauptstrasse 177 USt.IdNr: DE191347579 > > >> 52146 Würselen http://www.soebes.de > > >> > > >> - > > >> To unsubscribe from this list, please visit: > > >> > > >> http://xircles.codehaus.org/manage_email > > >> > > >> > > > > - > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter

Re: [mojo-dev] [VOTE] Retire failsafe-maven-plugin

pproval to do > what is necessary to retire the failsafe-maven-plugin > > - Stephen > > P.S. My vote is +1 > > - > To unsubscribe from this list, please visit: > >http://xircles

[mojo-dev] [VOTE] Release Selenium Maven Plugin 1.0.1

cceed by lazy consensus. Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Re: [mojo-dev] [VOTE] Release Selenium Maven Plugin 1.0.1

gt;> On Tue, Feb 23, 2010 at 10:39 AM, Mark Struberg wrote: >>>> >>>> +1 >>>> >>>> LieGrue, >>>> strub >>>> >>>> --- Brett Porter schrieb am Mo, 22.2.2010: >>>> >>>>> Von: Brett Porter >

[mojo-dev] [RESULT] Release Selenium Maven Plugin 1.0.1

The vote has passed, I'll move forward with the release. On 23/02/2010, at 9:58 AM, Brett Porter wrote: > Hi, > > I'd like to release version 1.0.1 of the Selenium Maven Plugin. The primary > reason is to update to Selenium RC 1.0.2, as it works with Firefox on Mac OS

[mojo-dev] [ANN] Selenium Maven Plugin 1.0.1 Released

) * [MSELENIUM-59] - Selenium server could not be stopped from stop-server goal * [MSELENIUM-60] - Fails to run with Firefox 3.5 on OS X 10.6.2 * [MSELENIUM-58] - docu is outdated: there is no parameter multiWindow anymore Cheers, Brett -- Brett Porter br...@apache.org http

Re: [mojo-dev] [proposal] add launch4j to appassembler

ts? > > -Robert > > [1] http://jira.codehaus.org/browse/MOJO-176 > [2] http://mojo.codehaus.org/appassembler -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Re: [mojo-dev] A fix for MSITE-459 that needs to be tested

nel#action_235286 > > -- > Dennis Lundberg > > - > To unsubscribe from this list, please visit: > >http://xircles.codehaus.org/manage_email >

Re: [mojo-dev] [RESULT] Vote Mark Michaelis as a Mojo Committer

t; >> Thanks, >> -- >> Olivier >> http://twitter.com/olamy >> http://www.linkedin.com/in/olamy >> > > ----- > To unsubscribe from this list, plea

Re: [mojo-dev] Status of Sonar mojo versions

ly the first mojo which requires to be built with maven 3. > Is it a problem for the release (nexus staging, webdav deployment) ? Shouldn't be, but I haven't tried it :) - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ -

Re: [mojo-dev] Mojo Developer Cookbook and v3.0

ns). There's some talk about expanding the plugin API in future releases to enumerate a supported API for all these things, but it's not intended that you depend on Guice or Aether directly. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter

Re: [mojo-dev] Required Maven version for a plugin

che/maven/plugins/maven-compiler-plugin/2.0.2/maven-compiler-plugin-2.0.2.pom - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter

Re: [mojo-dev] Mojo Developer Cookbook and v3.0

.org/display/MAVENUSER/Mojo+Developer+Cookbook > > A quick note in the wiki would be great. > > > > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter

Re: [mojo-dev] Mojo Developer Cookbook and v3.0

gins compatible with both. It's probably best hammered out on the maven dev list... - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter

Re: [mojo-dev] despot action required

s and other nonsense are a direct result of using swype to type on the > screen > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter

Re: [mojo-dev] Cobertura: in codehaus or out

> published via ossrh? In other words, what's the advantage, to anyone, > of keeping this code at codehaus? > > --benson margulies > > ----- > To unsubscribe from this list, please visit: > >http://xircles.codehaus.org/manage_email > > -- Brett Por

Re: [mojo-dev] Cobertura: in codehaus or out

instances in Mojo where this needs to happen) - I can't find the email, but I'm quite sure Ben or Bob ok'd Maven plugins that depend on GPL from a policy PoV. We could ask again if there's any concerns. I don't think there's any reason to limit continui

[mojo-dev] Re: [mojo-scm] [13804] trunk/sandbox/chronos-maven-plugin: New copyright notice header

* Copyright (c) 2004, The Codehaus > - * > - * Permission is hereby granted, free of charge, to any person obtaining a > copy of > - * this software and associated documentation files (the "Software"), to > deal in > - * the Software without restriction, including without limitation the rights > to > - * use, copy, modify, merge, publish, distribute, sublicense, and/or sell > copies > - * of the Software, and to permit persons to whom the Software is furnished > to do > - * so, subject to the following conditions: > - * > - * The above copyright notice and this permission notice shall be included > in all > - * copies or substantial portions of the Software. > - * > - * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR > - * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, > - * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL > THE > - * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER > - * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING > FROM, > - * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN > THE > - * SOFTWARE.+ * Chronos - Copyright (C) 2011 National Board of e-Health > (NSI), Denmark (http://www.nsi.dk) > + * > + * All source code and information supplied as part of Chronos is > + * copyright to National Board of e-Health. > + * > + * The source code has been released under a dual license - meaning you can > + * use either licensed version of the library with your code. > + * > + * It is released under the LGPL (GNU Lesser General Public License), either > + * version 2.1 of the License, or (at your option) any later version. A copy > + * of which can be found at the link below. > + * http://www.gnu.org/copyleft/lesser.html > + * > + * $HeadURL$ > + * $Id$ */ > package org.codehaus.mojo.chronos.report; > > > -- > > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > -- Brett Porter http://brettporter.wordpress.com/

Re: [mojo-dev] Proposal: "Simple Project" Parent POM

gt; -- >> I Am What I Am And That's All What I Yam (Popeye) >> >> - >> To unsubscribe from this list, please visit: >> >>http://xircles.codehaus.org/manage_email >> >>

Re: [mojo-dev] Cobertura: in codehaus or out

ugin), that the licensing of cobertura is complicated and they should seek their own advice. However, I don't think we should make a habit of depending on GPL code, and let's not accept new plugins since there is already apache-extras, github, etc. for that. Do others agree?

Re: [mojo-dev] mojo for checking size of artifacts

provider. > > Please do let me know your comments / feedback. > > BR/ > Anadi Misra. -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter

Re: [mojo-dev] mojo for checking size of artifacts

running on CI ? > > BR/ > Anadi Misra. > > On Mon, Apr 11, 2011 at 5:22 PM, Brett Porter wrote: > I think this would be better as an enforcer rule - and could be very quickly > implemented using evaluateBeanshell. Existing scripting plugins (groovy, > jruby, etc.) could also d

Re: [mojo-dev] Cobertura: in codehaus or out

t; > -Robert > > Date: Fri, 8 Apr 2011 14:04:32 +0200 > From: julien.po...@gmail.com > To: dev@mojo.codehaus.org > Subject: Re: [mojo-dev] Cobertura: in codehaus or out > > +1 > > -- > Julien Ponge > > On Friday, April 8, 2011 at 12:12 PM, Olivier Lamy wrot

Re: [mojo-dev] License adjustments in cobertura plugin

s copyright, licensed BSD' notice around? > > - > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Brett Porter br...@apache.org http:

Re: [mojo-dev] [ANN] Release Buildnumber Plugin 1.0

>>> ** New Feature >>> * [MOJO-1294] - When used with SCM buildnumber could also provide >>> commit revision, author, and date. >>> >>> ** Wish >>> * [MOJO-1472] - Support for disabling buildScmBranch calculation >>> >>

Re: [mojo-dev] [gwt] preparing 2.3.0 release -> github

o >>>>>> https://github.com/gwt-maven-plugin/gwt-maven-plugin, anyone from this >>>>>> list >>>>>> with spare time and motivation is welcome :P >>>>>> Cheers, >>>>>> Nicolas >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Olivier Lamy >>>> http://twitter.com/olamy | http://www.linkedin.com/in/olamy >>>> >>>> - >>>> To unsubscribe from this list, please visit: >>>> >>>>http://xircles.codehaus.org/manage_email >>>> >>>> >>> >> >> > > > > -- > Olivier Lamy > http://twitter.com/olamy | http://www.linkedin.com/in/olamy > > - > To unsubscribe from this list, please visit: > >http://xircles.codehaus.org/manage_email > > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Re: [mojo-dev] [gwt] preparing 2.3.0 release -> github

hat way, side by side. We might want that anyway, as the technique used in that document (a straight svn clone) loses a lot of history (tags and branches) and leaves a lot of cruft behind. Not sure if the doc is just out of date though. - Brett -- Brett Porter br...@apache.org http://brettporte

Re: [mojo-dev] Re: selenium-maven-plugin

Akins >> http://twitter.com/akinsgre >> > > > > -- > Greg Akins > http://twitter.com/akinsgre > > - > To unsubscribe from this list, please visit: > >http://xircles.codehaus.or

Re: [mojo-dev] Weblogic Maven 2.0 plugin

Has anyone looked at this? I'm interested in seeing this available for m2, but have no recent Weblogic experience to be a good judge of it. - Brett Scott Ryan wrote: > I have ported much of the functionality of the Maven 1.0 Weblogic plugin > into the Maven 2.0 environment. I have posted the sou

Re: [mojo-dev] JavaNCSS maven2 plugin

Done. Thanks! jean-laurent de morlhon wrote: > Hi, > > I just want to draw a commiter attention that a major bug fix has been > provided for the JavaNCSS maven2 plugin in a patch attached to > MOJO-172 Jira issue. ( http://jira.codehaus.org/browse/MOJO-172 ) for > some times now. > > I have writte

Re: [mojo-dev] [vote] release dependency-maven-plugin 1.0

+1 Brian E. Fox wrote: > Dan Tran and I have been working quite a bit getting the dependency > plugin ready to release. It's been tested pretty thoroughly by Dan and > all known issues are resolved. Right now the plugin has 4 goals: > > copy - this takes a list of artifacts defined in the plugin

Re: [mojo-dev] Etiquette question

Nobody is going to be offended if you fix something - and folks are encouraged to branch out to other plugins if they can. Go for it! If you are unsure, feel free to ask, of course. Brian E. Fox wrote: > Same question for the mojo parent. I submitted a jira about the scp/scpexe > change, should I

Re: [mojo-dev] Etiquette question

e changed to use > scpexe in the meantime. Otherwise, each mojo needs to override to > deploy. > > -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 28, 2005 11:28 PM > To: dev@mojo.codehaus.org > Subject: Re: [mojo-dev]

Re: [mojo-dev] JSPC plugin fixed

I think we better ensure the old one works again in 2.0.2. There is an open issue. - Brett Jeff Genender wrote: > I had reports about the jspc plugin not working in maven 2.0.1. I > upgraded to maven 2.0.1 and sure enough it broke the jspc plugin due to > a change in the maven classloaders. I f

Re: [mojo-dev] JSPC plugin fixed

ill be more > classloader fun coming down ;-) > > Brett Porter wrote: > >> I think we better ensure the old one works again in 2.0.2. There is an >> open issue. >> >> - Brett >> >> Jeff Genender wrote: >> >>> I had reports about the jspc

Re: [mojo-dev] Sites with incorrect permissions

I've fixed all the permissions. Go ahead and redeploy :) - Brett Brian E. Fox wrote: > I tried to fix the non-sandbox sites as a lot of them have bad scm > urls on the project pages. I ran into a couple of projects that can't > be deployed because the group perms aren't set: > > jxr > jboss > a

Re: [mojo-dev] Mojo synch to ibiblio missing hashes

Yes, the scpexe has a bug that causes this permission problem that needs a manual fix. You should be able to do so. - Brett dan tran wrote: > Hi Brian, > > Did you change the permission after invoke maven deploy? I could be > that the sync between iliblio and codehaus staging area fails due >

Re: [mojo-dev] Release:prepare failing

Are you using the https checkout for mojo? (run svn info to check how it was checked out). We changed over to that and you need to have previously committed using https to cache the auth details. - Brett Brian E. Fox wrote: > repost under new subject: > > I'm trying the release plugin and I get

Re: [mojo-dev] Release:prepare failing

ommand line and it was ok. > > -Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Monday, January 02, 2006 3:48 PM > To: dev@mojo.codehaus.org > Subject: Re: [mojo-dev] Release:prepare failing > > Are you using the https checkout for mojo?

Re: [mojo-dev] Release:prepare failing

t; set, and > no 'editor-cmd' run-time configuration option was found > > If I add -m and a message, the commit goes through. Is the code setting > a msg or could that be the problem? > > -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Mo

Re: [mojo-dev] Deploy fails

Odd. what is your operating system? that's an empty error from the ssh executable... - Brett Brian E. Fox wrote: > Hey guys. Last night I was able to deploy the release of the dependency > plugin. Now that I went back and tried to do the release plugin, it's > failing. Both release:perform and de

Re: [mojo-dev] [vote] commit access for stephane nicoll

+1 Jason van Zyl wrote: > Hi, > > Stephane is a committer on m2 and would like to do some work on some > mojos. I think we can certainly allow him access! > > +1 >

Re: [mojo-dev] jaxb plugin

I'm not convinced this is endorsed by Sun, or even legal for the 1.0.5 JARs. Another thing I wanted to check - as I understand it the xjc plugin uses jaxme. Jaxme now has its own plugin - is there any chance they could be worked on together at JaxMe? - Brett Olivier Lamy wrote: > Hi all, > Infor

Re: [mojo-dev] [vote] commit privs for Mike Perham

+1 Jason van Zyl wrote: > Hi, > > Mike would like to contribute to the changes plugin so I propose we give > him access. Mike is a committer on Maven SCM and wants to use his Maven > SCM know-how to improve the changes plugin > > +1 >

Re: [mojo-dev] [vote] commit privs for Mike Perham

Stephane, Can we put that in the sandbox at Apache along with the issue stuff so it all stays together? You should do that since it is your work and you are a committer there. Mike can also work on it there. - Brett Stephane Nicoll wrote: > If mike wants to work on the changes plugin, I think he

Re: [mojo-dev] Commit access request (was: [vote] commit access for stephane nicoll)

Yep - we'll try and get this moving for all three of you at once. - Brett Fabrizio Giustina wrote: > On 1/9/06, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: >> +1, but I though that we said that any Maven 2 core or plug-in developer >> could simply request access for the Mojo project as we threat t

Re: [mojo-dev] [vote] Sandbox cleanup

Purely myth. See the build lifecycle doco for more info, but you can name it however you'd like. - Brett Brian E. Fox wrote: >> 2. Should we correct the plugin names? > > "+0 First dispel a rumor for me. Someone suggested that some of the > names > are that way to support handling of specific cu

Re: [mojo-dev] [Vote] Release build-helper-maven-plugin 1.0

+1, BUT I'm thinking this is significant enough to introduce to the Apache project. What do others think? - Brett dan tran wrote: > > I would like to make build-helper-maven-plugin official for my > production builds. > > This plugin allows user to: > > - Add more source, and test sou

Re: [mojo-dev] Re: [mojo-user] Write Mojos w/Groovy

Jason Dillon wrote: > I put my initial analysis of his work in the issue just after it was > brought to my attention. I think he went more towards the solution you had with some direction. He may have even used your stuff for all I know :) > I can take another peek to see if anything has change

[mojo-dev] Bringing plugins to Apache Maven

Some of the plugins that wound up in mojo seem better suited to the main Apache project due to a) originally coming from there b) having the core libraries located there c) being essential to the day to day use of the project. These are the ones I'm thinking of: - build helper - jxr report (jxr) -

Re: [mojo-dev] [vote] Sandbox cleanup

+1 to these, but let's make the sandbox plugins distinct. Let's also demote to the sandbox anything that hasn't had a release yet. - Brett Brian E. Fox wrote: > I've been looking at some plugins in the sandbox and I see some issues: > > 1. If sandbox plugins deploy sites, (as they probably sho

Re: [mojo-dev] sandbox snapshots

We should get ci.codehaus.org deploying it to a repository as well. Any volunteers? BTW, if minijar works well, do you think there is any scope for integrating it directly into the assembly plugin, or making it a type of archiver rather than an independant plugin? It wouldn't really change the co

Re: [mojo-dev] [vote] Sandbox cleanup

ion... > > There are 2 (jspc and jboss) that are becoming used pretty heavily...and > I think a demotion would be a negative...since they have been out in the > wild for some time now. > > So should I enable a vote for those in another thread? > > Jeff > > Brett

Re: [mojo-dev] Bringing plugins to Apache Maven

Vincent Massol wrote: > >> -Original Message- >> From: Brett Porter [mailto:[EMAIL PROTECTED] >> Sent: jeudi 12 janvier 2006 13:56 >> To: Mojo Developers >> Subject: [mojo-dev] Bringing plugins to Apache Maven >> >> Some of the plugins that wo

Re: [mojo-dev] Bringing plugins to Apache Maven

and does handle 95%, of your use cases...and right > now I don't see a maven plugin for other compilers that handle jsps. In > other words, you can always add in other compilers. > > Jeff > > Brett Porter wrote: >> Some of the plugins that wound up in mojo seem

Re: [mojo-dev] Hivedoc Plugin

Sorry for the long time between replies. Did anything happen here? Ben Gidley wrote: > Brett, > I thought Mojo looked a better place that hivemind because if I read the > document at > > correctly it implies to have a short

Re: [mojo-dev] Bringing plugins to Apache Maven

100, Vincent Massol wrote: >>> -Original Message- >>> From: Brett Porter [mailto:[EMAIL PROTECTED] >>> Sent: jeudi 12 janvier 2006 13:56 >>> To: Mojo Developers >>> Subject: [mojo-dev] Bringing plugins to Apache Maven >>> >>> S

Re: [mojo-dev] [Vote] Release build-helper-maven-plugin 1.0

dan tran wrote: > OK, we have 8 votes to release 1.0 at codehaus. > > Do we have enought vote to move it to apache, if so I will > rename it to Based on the other thread, I think we have enough votes, but its not totally decided. Can we wait a couple of days? The trick is, after you import it t

Re: [mojo-dev] [Vote] Release build-helper-maven-plugin 1.0

ts. > > Ofcourse, I will wait for a couple of days. > > -Dan > > > > On 1/15/06, *Brett Porter* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > wrote: > > dan tran wrote: > > OK, we have 8 votes to release 1.0 at codehaus. &g

Re: [mojo-dev] Vote: sablecc plugin release

+1 Jesse McConnell wrote: > > this plugin has been chugging along fine for a while with a number of > users so I would like to get it released out as version 1.0 or 2.0 since > I think there is a maven1 plugin for sablecc as well > > -- > jesse mcconnell > jesseDOTmcconnellATgmailDOTcom

Re: [mojo-dev] JLex plugin interest

Is there value in setting these up to all work off the same base? - Brett Anthony Vito wrote: > Good day everyone, > > I was wondering if there is any interest in a JLex plugin. I have > completed one that allows for the same functionality as the jlex ant > task, with the additional concepts (

Re: [mojo-dev] JLex plugin interest

Just to elaborate - I'm thinking whether we should just have a plexus-compiler-compiler component and maven-compiler-compiler-plugin (or something with a more sensisble name :) - Brett Brett Porter wrote: > Is there value in setting these up to all work off the same base? >

Re: [mojo-dev] sandbox - torque plugin

Wouldn't torque be interested in this contribution? Brian E. Fox wrote: > I've had luck using the hypersonic sql driver as an embedded db. It's on > ibiblio too. > > > *From:* Piéroni Raphaël [mailto:[EMAIL PROTECTED] > *Se

Re: [mojo-dev] sandbox - torque plugin

use hsqldb (or derby, but its bigger and slower to setup - would only be for if hsqldb is not sufficient). I have no problem with it starting here, but I think its worth getting torque folks involved. - Brett Raphaël Piéroni wrote: > > > Brett Porter a écrit : > >>

Re: [mojo-dev] sandbox - torque plugin

It just requires using a different JDBC URL - there are docs on the hsqldb site for that. - Brett Raphaël Piéroni wrote: > I now have a starting point using mysql. > > Brett, may you send me some code sample to embed hsqldb. Therefore i > will replace mysql by hsqldb. > > I have sent an email a

Re: [mojo-dev] Weblogic Maven 2.0 plugin

gt; this issue? I would love to get more feedback through JIRA as well as to >> additional functionality that is desired since the M1 plugin has a lot to >> be >> ported over still. >> >> I welcome comments and tips on how to get this moved into the sandbox. >> >> Scott Ryan

[mojo-dev] [vote] Give Scott Ryan commit access

He's been working on the weblogic plugin for a while. Shall we give sandbox commit to continue working on it here? [ ] +1 [ ] +0 [ ] -1 - Brett

Re: [mojo-dev] Weblogic Maven 2.0 plugin

I see Kris has been helping you out on the JIRA issue. Kris - any reason not to commit the work to date? Brett Porter wrote: > I'll start a vote to give you access. > > There is some other appc plugin around here - what is the difference? > > - Brett > > Scott Ryan wr

Re: [mojo-dev] maven-changes

I noticed Brian asked a similar question, and I have no idea. Check "svn log" and see who was involved. I think, as far as changes goes, it should be moved to the sandbox at apache and utilise the issue tracking library being built there (with changes.xml being a "provider" for issue tracking). -

Re: [mojo-dev] JasperReports plugin

You now have commit. With great power comes great responsibility. Add it to the sandbox and we can go from there. - Brett Grégory Joseph wrote: > Hi list, > > I know the guidelines propose to first ask if there's interest, but, > well, since I need the plugin myself anyways, I thought I'd go th

Re: [mojo-dev] Commit access request (was: [vote] commit access for stephane nicoll)

Fabrizio - please create a JIRA issue under the HAUS project for a new account. Provide: Full Name: Forwarding Email: Preferred Unix ID: Please attach your public key, or even better the URL to it at people.apache.org so that I can be sure its you :) - Brett Brett Porter wrote: > Yep - we

Re: [mojo-dev] Remove JIRA report from changes-maven-plugin

Hi Mike, I agree with splitting this up now, but would like to treat changes.xml as an "issue tracker". ie: maven-issue-provider-api maven-issue-provider-jira maven-issue-provider-file (changes.xml) maven-issue-provider-bugzilla|trac|clearquest|scarab|sourceforge Then: maven-issue-provider-plugi

Re: [mojo-dev] Remove JIRA report from changes-maven-plugin

around and see if I can't move Stephane's > maven-changes mojo code into the sandbox and get a > maven-issue-provider-file project up and running. > > mike > > -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Monday, January 23, 2

Re: [mojo-dev] izpack plugin

Interested - but I think installers are providers to the assembly plugin at Apache. For sure let us know what you are able to do. Thanks, Brett Miguel Griffa wrote: > hi all, > again me, I've seen that there's no m2 plugin for izpack, would you be > interested in adding such a plugin to the sandb

Re: [mojo-dev] [Vote] Release build-helper-maven-plugin 1.0

e 1.0 at codehaus. > > Do we have enought vote to move it to apache, if so I will > rename it to > >maven-build-helper-plugin > > -Dan > > > On 1/13/06, *Arnaud HERITIER* <[EMAIL PROTE

Re: [mojo-dev] deploying snapshots: do not have access to maven user on beaver

It shouldn't be necessary - the mojo group that you are in can write to the mojo area of the repo (if that's not the case, let me know). You should perform it as lacostej. - Brett jerome lacoste wrote: > Hi, > > kenney helped me trouble shoot my issues at deploying snapshots of > some mojo-sandm

Re: [mojo-dev] Release cobertura plugin

I'm looking at it now. By lots of questions, they're all from the same user. The cobertura plugin has never been released. It doesn't have a JIRA component because its in the sandbox. The Mojo JIRA projects haven't been created yet, but Jason was collecting the data. - Brett Carlos Sanchez wrote

Re: [mojo-dev] deploying snapshots: do not have access to maven user on beaver

jerome lacoste wrote: > On 1/31/06, Brett Porter <[EMAIL PROTECTED]> wrote: >> It shouldn't be necessary - the mojo group that you are in can write to >> the mojo area of the repo (if that's not the case, let me know). You >> should perform it as lacost

Re: [mojo-dev] deploying snapshots: do not have access to maven user on beaver

Fixed. jerome lacoste wrote: > On 1/31/06, jerome lacoste <[EMAIL PROTECTED]> wrote: >> On 1/31/06, Brett Porter <[EMAIL PROTECTED]> wrote: >>> It shouldn't be necessary - the mojo group that you are in can write to >>> the mojo area of the rep

Re: FW: [mojo-dev] Release cobertura plugin

rs to instrument but requires > nothing to actually run the instrumented code during tests. So I cloned > cobertura into a separate cobertura-runtime artifact and add that to the > project classpath instead of the cobertura artifact itself. It's a hack > but I don't know of any cleaner

Re: [mojo-dev] permission issues on beaver

Hmm. Which plugin? the permissions all look right to me. jerome lacoste wrote: > a group permission issue on beaver prevented me from deploying a > plugin today. That's the second time in 24 hours. > > - what cause the reasons? wrong umask? If so what do you use? 0002 ? > - can't this be 'fixed'

Re: [mojo-dev] APT editor eclipse plugin

Hi, I really think we should integrate this into the Maven IDE Plugin for Eclipse. How about attaching it to a new issue at MNGECLIPSE? Cheers, Brett Miguel Griffa wrote: > Hi all > I wanted to let you know I'm working in an eclipse plugin providing an > editor for APT files. > Currently I'm foc

Re: [mojo-dev] [Vote] Release build-helper-maven-plugin 1.0

This is a good point. I think that we can keep it here. The main thing I was interested in is the artifact attachment, but IMO that is something that should be made easier in a later version of Maven. - Brett jerome lacoste wrote: > On 1/30/06, Brett Porter <[EMAIL PROTECTED]> wrot

[mojo-dev] Re: [mojo-scm] [1445] trunk/mojo/mojo-sandbox/cobertura-maven-plugin: PR: MOJO-226

Mike? Brett Porter wrote: > Sorry, I don't understand this. > > If older ASM's work with Cobertura, why isn't Cobertura changed to use > the older ASM (or a range?) Why can't you use exclusions in the plugin, > even if not changing the cobertura POM? > &g

Re: [mojo-dev] Re: [mojo-scm] [1445] trunk/mojo/mojo-sandbox/cobertura-maven-plugin: PR: MOJO-226

Mike Perham wrote: > Brett, I'm not an expert in Cobertura's usage of ASM. The POM says it > requires 2.1 and I was not about to jump from 2.1 -> 1.5.3. Instead I > focused on Cobertura's own best practice which is simply to not put ASM > in the classpath during runtime. cool - I'm sure its an i

Re: [mojo-dev] Moving CSharp plugins to mojo project

I'd actually be open to discussing bringing this to Maven proper. I'd like to see core functionality in the main project, and I can see this becoming core functionality. There is also the beginnings of csharp support from Trygve in the Maven sandbox that this could replace. I'll leave that up to y

Re: [mojo-dev] [vote] aspectj plugin beta-1 release

I'm pretty sure Jeff's email isn't policy. People generally just document it as copyright of the ASF. Carlos Sanchez wrote: > This legal stuff drives me crazy ;) > I'll try to read that long mail, but my concern is the following, > let's suppose something contributed to the ASF (not mojo) > > If t

Re: [mojo-dev] [vote] aspectj plugin beta-1 release

Brett Porter wrote: > I'm pretty sure Jeff's email isn't policy. People generally just > document it as copyright of the ASF. erm, *the link* in Jeff's email isn't policy. :)

Re: [mojo-dev] [vote] aspectj plugin beta-1 release

Sorry, I should have omitted only from that sentence. Why are we talking about MPL, etc? Is there any code here that isn't BSD licensed, other than FindBugs and Cobertura? - Brett Carlos Sanchez wrote: > On 2/10/06, Brett Porter <[EMAIL PROTECTED]> wrote: >> I'm prett

Re: [mojo-dev] Licensing policy

> a) we allow people to own the copyright (Copyright bla bla Carlos Sanchez) > - that person needs to allow change of license > - when somebody contributes he should (or may want to) add his name to > the copyright > - if we move a plugin to ASF we can do it, adding the ASF and keeping > the old on

Re: [mojo-dev] Licensing policy

Carlos Sanchez wrote: > On 2/10/06, Brett Porter <[EMAIL PROTECTED]> wrote: >>> a) we allow people to own the copyright (Copyright bla bla Carlos Sanchez) >>> - that person needs to allow change of license >>> - when somebody contributes he should (or may want t

Re: [mojo-dev] org.codehaus.mojo:mojo version 7 deployed?

No. I'll do that now. - Brett dan tran wrote: > Hi yesterday I think Brett updated the pom to version 7 in svn. is it > deployed yet? > > -Dan

Re: [mojo-dev] IDEA ui designer plugin

sure jerome lacoste wrote: > Hi, > > I wrote a simple plugin that allows to control the IDEA ui designer. > This is a simple wrapper around the ant tasks jetbrains published that > perform the same job. The ant tasks are under the BSD license and part > of the redist/ directory under your IDEA in

Re: [mojo-dev] Weblogic Plugin Updates and Sandbox Web Site?

I thought I sent you a private message, but I can't find it. Must have hit the wrong button :) Please fill out: http://jira.codehaus.org/browse/HAUS-1085 and ping us here. Thanks, Brett Scott Ryan wrote: > Hi, > I have some updates to the Weblogic plugin and wondered where I should post > them.

  1   2   3   4   5   6   7   8   >