[maven2 build - FAILED - update] Tue Nov 1 07:45:00 GMT 2005

Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051101.074500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (MNG-764) pom with modules should fail if packaging is not pom or an aggregator

[ http://jira.codehaus.org/browse/MNG-764?page=all ] Brett Porter closed MNG-764: Resolution: Fixed applied, thanks. Note that if we later allow other packagings to aggregate, this will need to take it into account > pom with modules should fail if pa

[maven2 build - SUCCESS - update] Tue Nov 1 07:15:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051101.071500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051101.071500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

[jira] Closed: (MNG-1342) document surefire plugin

[ http://jira.codehaus.org/browse/MNG-1342?page=all ] Brett Porter closed MNG-1342: - Assign To: Brett Porter Resolution: Fixed Fix Version: 2.0.1 > document surefire plugin > > > Key: MNG-1342 > URL:

[jira] Closed: (MNG-1271) Maven 2 needs to give a warning when it is being run in a Maven 1 project and there isn't a pom.xml file

[ http://jira.codehaus.org/browse/MNG-1271?page=all ] Brett Porter closed MNG-1271: - Resolution: Fixed > Maven 2 needs to give a warning when it is being run in a Maven 1 project and > there isn't a pom.xml file > --

Re: bringing surefire and doxia to Maven

good idea. Kind regards, Dave Sag   Brett Porter <[EMAIL PROTECTED]> wrote on 01/11/2005 02:15:12 AM: > Hi, > > Doxia and Surefire were small projects started at Codehaus to experiment > with new technology that has since been used from Maven 2.0. > > With one recent exception the comm

[jira] Created: (CONTINUUM-407) screen after adding/removing a build definition or notifier should be the project View page

screen after adding/removing a build definition or notifier should be the project View page --- Key: CONTINUUM-407 URL: http://jira.codehaus.org/browse/CONTINUUM-407 Project: Continuum

[jira] Commented: (MNG-699) Add EJB3 support in a plugin

[ http://jira.codehaus.org/browse/MNG-699?page=comments#action_49720 ] Brett Porter commented on MNG-699: -- what is required to finish this? how do they compare/relate to MOJO-98/MOJO-99? > Add EJB3 support in a plugin > > >

[maven2 build - SUCCESS - update] Tue Nov 1 06:00:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051101.06.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051101.06.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

[jira] Updated: (MNG-1348) includes on resource tag not documented as being a list

[ http://jira.codehaus.org/browse/MNG-1348?page=all ] Brett Porter updated MNG-1348: -- Component: (was: maven-model) documentation - general Summary: includes on resource tag not documented as being a list (was: includes attribute n

[jira] Commented: (MNG-1347) Maven (plexus?) doesn't recognize Mojo parameter setters defined in a base class

[ http://jira.codehaus.org/browse/MNG-1347?page=comments#action_49719 ] Brett Porter commented on MNG-1347: --- the problem seems to be looking for Class instead of String > Maven (plexus?) doesn't recognize Mojo parameter setters defined in a base > class >

[jira] Closed: (MNG-1339) properties filtering treats idontexist.name as pom.name

[ http://jira.codehaus.org/browse/MNG-1339?page=all ] Brett Porter closed MNG-1339: - Assign To: Brett Porter Resolution: Duplicate > properties filtering treats idontexist.name as pom.name > --- >

[maven2 build - SUCCESS - update] Tue Nov 1 05:30:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051101.053000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051101.053000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

[jira] Reopened: (MPRELEASE-11) does not handle non-jar dependencies

[ http://jira.codehaus.org/browse/MPRELEASE-11?page=all ] Brett Porter reopened MPRELEASE-11: --- > does not handle non-jar dependencies > > > Key: MPRELEASE-11 > URL: http://jira.codehaus.org/browse

[jira] Closed: (MPRELEASE-11) does not handle non-jar dependencies

[ http://jira.codehaus.org/browse/MPRELEASE-11?page=all ] Brett Porter closed MPRELEASE-11: - Resolution: Fixed > does not handle non-jar dependencies > > > Key: MPRELEASE-11 > URL: http://jira.c

[maven2 build - SUCCESS - update] Tue Nov 1 05:00:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051101.05.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051101.05.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

Re: svn commit: r329958 - in /maven/maven-1/plugins/trunk/release: plugin.jelly xdocs/changes.xml

Won't fix was based on the fact the plugin was not being developed. It was a simple patch, and it seems you've got plans to rerelease it to update the dependencies. I will update JIRA. - Brett Arnaud HERITIER wrote: Hi Brett, Why did you finally apply a patch to fix an issue you clo

RE: svn commit: r329958 - in /maven/maven-1/plugins/trunk/release: plugin.jelly xdocs/changes.xml

Hi Brett, Why did you finally apply a patch to fix an issue you closed as "Won't fix" ? Arnaud > -Message d'origine- > De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Envoyé : mardi 1 novembre 2005 04:07 > À : commits@maven.apache.org > Objet : svn commit: r329958 - in > /

maven-one-plugin added to sandbox

Hi, I've added this to the sandbox, which was something I did to help Dain as he'll be working across m2 and m1 projects simultaneously. It enables m2 projects to build a maven 1.x plugin (so the m1 build doesn't need to be maintained), and also allows copying any artifact into a local maven

RE: bringing surefire and doxia to Maven

+1 Arnaud > -Message d'origine- > De : Brett Porter [mailto:[EMAIL PROTECTED] > Envoyé : mardi 1 novembre 2005 02:15 > À : Maven Developers List > Objet : bringing surefire and doxia to Maven > > Hi, > > Doxia and Surefire were small projects started at Codehaus to > experiment with n

[maven2 build - SUCCESS - update] Tue Nov 1 04:15:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051101.041500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051101.041500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

[maven2 build - SUCCESS - update] Tue Nov 1 03:30:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051101.033000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051101.033000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

[maven2 build - SUCCESS - update] Tue Nov 1 03:00:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051101.03.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051101.03.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

Re: svn commit: r329961 - /maven/components/trunk/maven-site/src/site/apt/guides/mini/guide-maven-evangelism.apt

Can you change the svn:eol-style to native? If this was your import, you might also need to check your autoprops and make sure .apt is included. - Brett [EMAIL PROTECTED] wrote: Author: carlos Date: Mon Oct 31 19:13:11 2005 New Revision: 329961 URL: http://svn.apache.org/viewcvs?rev=329961&

Maven evangelism guide

Hi, I've added a very first version of a maven evangelism guide with repository information, hopefully somebody will start helping with MEV issues. I'll add info to this guide as I have more free time. The guide is in svn under components\maven-site\src\site\apt\guides\mini\guide-maven-evangelism

[jira] Created: (MEV-163) Groovy pom has invalid dependencies

Groovy pom has invalid dependencies --- Key: MEV-163 URL: http://jira.codehaus.org/browse/MEV-163 Project: Maven Evangelism Type: Bug Reporter: Dain Sundstrom The groovy pom seems to be a blind conversion from the maven 1 project.xm

[maven2 build - SUCCESS - update] Tue Nov 1 02:00:01 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051101.020001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051101.020001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

Re: bringing surefire and doxia to Maven

On Tue, 2005-11-01 at 12:15 +1100, Brett Porter wrote: > Hi, > > Doxia and Surefire were small projects started at Codehaus to experiment > with new technology that has since been used from Maven 2.0. > > With one recent exception the committer set are entirely Maven committers. > > Doxia is th

[jira] Updated: (MNG-1245) Reactor projects sometimes used even with version mismatch

[ http://jira.codehaus.org/browse/MNG-1245?page=all ] John Casey updated MNG-1245: Remaining Estimate: 2 hours Original Estimate: 7200 will investigate. > Reactor projects sometimes used even with version mismatch >

[jira] Updated: (MNG-1205) dependency with scope:system & flag optional = true doesn't appear in the class path

[ http://jira.codehaus.org/browse/MNG-1205?page=all ] John Casey updated MNG-1205: Complexity: Expert (was: Intermediate) Remaining Estimate: 2 hours Original Estimate: 7200 just need to investigate this a bit. I'll hook up the debugger and

[jira] Updated: (MNG-1335) Artifact must be cloned too in MavenProject's constructor

[ http://jira.codehaus.org/browse/MNG-1335?page=all ] John Casey updated MNG-1335: Remaining Estimate: 30 minutes Original Estimate: 1800 > Artifact must be cloned too in MavenProject's constructor > -

Re: bringing surefire and doxia to Maven

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 Brett Porter wrote: | Hi, | | Doxia and Surefire were small projects started at Codehaus to experiment | with new technology that has since been used from Maven 2.0. | | With one recent exception the committer set are entirely Maven committers

[maven2 build - SUCCESS - update] Tue Nov 1 01:30:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051101.013000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051101.013000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

[jira] Commented: (MNG-1285) rename to help plugin

[ http://jira.codehaus.org/browse/MNG-1285?page=comments#action_49710 ] John Casey commented on MNG-1285: - Thanks for the patch, John T. ! :-) > rename to help plugin > - > > Key: MNG-1285 > URL: http://jira.codehaus.or

[jira] Closed: (MNG-1285) rename to help plugin

[ http://jira.codehaus.org/browse/MNG-1285?page=all ] John Casey closed MNG-1285: --- Resolution: Fixed applied documentation diffs in the attached patch, and renamed the plugin's package. I had already changed the plugin name previously. > rename to help

[jira] Commented: (MNG-1101) release pom, and next version, is missing pieces of pom

[ http://jira.codehaus.org/browse/MNG-1101?page=comments#action_49707 ] John Casey commented on MNG-1101: - it's set to warn if you try to release:perform with release-pom.xml, but it will allow deploying the release with non-standard POM files now. If you tr

[continuum build - FAILED - checkout] Tue Nov 1 01:30:00 GMT 2005

Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051101.013000.txt

Re: bringing surefire and doxia to Maven

+1 On 10/31/05, Brett Porter <[EMAIL PROTECTED]> wrote: > Hi, > > Doxia and Surefire were small projects started at Codehaus to experiment > with new technology that has since been used from Maven 2.0. > > With one recent exception the committer set are entirely Maven committers. > > Doxia is the

[jira] Closed: (MNG-1101) release pom, and next version, is missing pieces of pom

[ http://jira.codehaus.org/browse/MNG-1101?page=all ] John Casey closed MNG-1101: --- Resolution: Fixed > release pom, and next version, is missing pieces of pom > --- > > Key: MNG-1101 >

[maven2 build - SUCCESS - update] Tue Nov 1 01:15:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051101.011500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051101.011500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

[jira] Commented: (MNG-897) allows use of Ant build files

[ http://jira.codehaus.org/browse/MNG-897?page=comments#action_49705 ] John Casey commented on MNG-897: It's ready, but we need to work out the versioning for its release, and it will depend on a new release of the plugin-plugin, to use the new version of m

bringing surefire and doxia to Maven

Hi, Doxia and Surefire were small projects started at Codehaus to experiment with new technology that has since been used from Maven 2.0. With one recent exception the committer set are entirely Maven committers. Doxia is the underpinnings of the site plugin, and is used to generate document

[continuum build - SUCCESS - update] Tue Nov 1 01:00:00 GMT 2005

Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20051101.01.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051101.01.txt

[maven2 build - SUCCESS - update] Tue Nov 1 00:00:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051101.00.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051101.00.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

[jira] Commented: (MNG-1285) rename to help plugin

[ http://jira.codehaus.org/browse/MNG-1285?page=comments#action_49703 ] Brett Porter commented on MNG-1285: --- John C, what do you need to do beyond what John T has already provided? > rename to help plugin > - > > Key: MNG-128

[maven2 build - SKIPPED - checkout] Tue Nov 1 00:15:00 GMT 2005

ci.sh already running... exiting maven 12226 12190 0 00:00:02 ? 0:00 /bin/sh /export/home/maven/ci.sh update maven 12227 12226 0 00:00:02 ? 0:00 /bin/sh /export/home/maven/ci.sh update maven 12190 12167 0 00:00:01 ? 0:00 /bin/sh /export/home/maven/ci.

[jira] Commented: (MNG-1382) "duplicate files" exception

[ http://jira.codehaus.org/browse/MNG-1382?page=comments#action_49700 ] Brett Porter commented on MNG-1382: --- ok, I see you've actually fixed this recently. I thought it was the older issue. > "duplicate files" exception > --- > >

[jira] Commented: (MNG-1382) "duplicate files" exception

[ http://jira.codehaus.org/browse/MNG-1382?page=comments#action_49699 ] Brett Porter commented on MNG-1382: --- Vincent, shouldn't this be closed as a duplicate of the original? > "duplicate files" exception > --- > > Key: MNG

[jira] Commented: (MAVENUPLOAD-563) Add htmlparser

[ http://jira.codehaus.org/browse/MAVENUPLOAD-563?page=comments#action_49697 ] Carlos Sanchez commented on MAVENUPLOAD-563: jar inside has to be called htmlparser-1.6.jar (so the bundle cannot be called the same) license file has to be called LI

[jira] Commented: (MAVEN-1701) NEON][JDBC] Can't load scjd12ts.dll, file not found, eventhough on system path

[ http://jira.codehaus.org/browse/MAVEN-1701?page=comments#action_49695 ] blueeyes commented on MAVEN-1701: - Ensure the PATH for JAR related to 'scjd12ts.dll' (it may look like scjd12.jar) has been SPECIFIED in the Server's CLASSPATH. Double click on the Se

[jira] Closed: (MAVEN-1720) Documentation updates

[ http://jira.codehaus.org/browse/MAVEN-1720?page=all ] Arnaud Heritier closed MAVEN-1720: -- Resolution: Fixed Applied. Thanks. > Documentation updates > - > > Key: MAVEN-1720 > URL: http://jira.codehaus.org/br

[jira] Commented: (MNG-1360) Polish translation for maven-site-plugin

[ http://jira.codehaus.org/browse/MNG-1360?page=comments#action_49693 ] Vincent Siveton commented on MNG-1360: -- Thanks a lot! Could you translate the project-info-report.properties too? FYI: http://maven.apache.org/plugins/maven-site-plugin/i18n.html

[jira] Closed: (MNG-1382) "duplicate files" exception

[ http://jira.codehaus.org/browse/MNG-1382?page=all ] Vincent Siveton closed MNG-1382: Resolution: Fixed Added in SVN > "duplicate files" exception > --- > > Key: MNG-1382 > URL: http://jira.codehaus.org/br

[jira] Closed: (MPANNOUNCEMENT-17) I can not get the source code

[ http://jira.codehaus.org/browse/MPANNOUNCEMENT-17?page=all ] Lukas Theussl closed MPANNOUNCEMENT-17: --- Resolution: Fixed > I can not get the source code > - > > Key: MPANNOUNCEMENT-17 > URL: http:

[jira] Created: (MNG-1382) "duplicate files" exception

"duplicate files" exception --- Key: MNG-1382 URL: http://jira.codehaus.org/browse/MNG-1382 Project: Maven 2 Type: Bug Components: maven-site-plugin Reporter: Vincent Siveton Assigned to: Vincent Siveton Supposed that you have this si

[jira] Updated: (MAVENUPLOAD-563) Add htmlparser

[ http://jira.codehaus.org/browse/MAVENUPLOAD-563?page=all ] siegfried heintze updated MAVENUPLOAD-563: -- Attachment: htmlparser-1.6.jar Changed as per recent comments > Add htmlparser > -- > > Key: MAVENUPLOAD-563 >

[continuum build - FAILED - update] Mon Oct 31 22:30:00 GMT 2005

Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.223000.txt

[jira] Commented: (MAVENUPLOAD-563) Add htmlparser

[ http://jira.codehaus.org/browse/MAVENUPLOAD-563?page=comments#action_49689 ] Carlos Sanchez commented on MAVENUPLOAD-563: It should be like this 4.0.0 org.htmlparser htmlparser 1.6 And say what of the attachments, or the link

[jira] Commented: (MAVENUPLOAD-570) statx-utils

[ http://jira.codehaus.org/browse/MAVENUPLOAD-570?page=comments#action_49688 ] Carlos Sanchez commented on MAVENUPLOAD-570: Wrong groupId and missing 4.0.0 > statx-utils > --- > > Key: MAVENUPLOAD-570 > URL: http://j

[jira] Updated: (MAVENUPLOAD-563) Add htmlparser

[ http://jira.codehaus.org/browse/MAVENUPLOAD-563?page=all ] Carlos Sanchez updated MAVENUPLOAD-563: --- Comment: was deleted > Add htmlparser > -- > > Key: MAVENUPLOAD-563 > URL: http://jira.codehaus.org/browse/MAVENUPLO

[jira] Commented: (MAVENUPLOAD-569) maven taglib plugin 2.0 <>

[ http://jira.codehaus.org/browse/MAVENUPLOAD-569?page=comments#action_49687 ] Carlos Sanchez commented on MAVENUPLOAD-569: groupId should be net.sourceforge.maven-taglib Attach the metadata needed and I'll copy it manually > maven taglib plugin

[jira] Commented: (MAVENUPLOAD-563) Add htmlparser

[ http://jira.codehaus.org/browse/MAVENUPLOAD-563?page=comments#action_49686 ] Carlos Sanchez commented on MAVENUPLOAD-563: It should be like this org.htmlparser htmlparser 1.6 And say what of the attachments, or the link provide

[continuum build - FAILED - update] Mon Oct 31 22:00:00 GMT 2005

Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.220001.txt

[jira] Closed: (MAVENUPLOAD-568) Update asterisk-java to 0.2-rc2

[ http://jira.codehaus.org/browse/MAVENUPLOAD-568?page=all ] Carlos Sanchez closed MAVENUPLOAD-568: -- Assign To: Carlos Sanchez Resolution: Fixed > Update asterisk-java to 0.2-rc2 > --- > > Key: MAVENUPL

[jira] Commented: (MAVENUPLOAD-559) Mustang b56 jnlp-servlet library

[ http://jira.codehaus.org/browse/MAVENUPLOAD-559?page=comments#action_49685 ] Carlos Sanchez commented on MAVENUPLOAD-559: As I said before we may upload it to the same groupId as the webstart plugin > Mustang b56 jnlp-servlet library > ---

[jira] Commented: (MAVENUPLOAD-551) Please upload Click 0.14 JAR

[ http://jira.codehaus.org/browse/MAVENUPLOAD-551?page=comments#action_49684 ] Carlos Sanchez commented on MAVENUPLOAD-551: groupId shoould be net.sf.click > Please upload Click 0.14 JAR > > > Key: MAVENUPLO

Re: where to put projects/APIs that support mojos?

>~From typing this, I can see that it's likely I'm talking about two >different things. Mojo-supporting libraries, which should reside in one >umbrella project (akin to mojo.codehaus.org , or maybe within it?); I would say it ought to go into mojo for the time being and

[continuum build - FAILED - update] Mon Oct 31 21:30:00 GMT 2005

Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.213000.txt

RE: site nav

> > On Sun, 2005-10-30 at 23:57 +0100, Arnaud HERITIER wrote: > > > > > > On Thu, 2005-10-27 at 18:33 -0700, Brett Porter wrote: > > > > Hey, great job on the new sites for subprojects and the new > > > continuum > > > > logo everyone! > > > > > > > > I just noticed that the links on the m1 site

[jira] Updated: (CONTINUUM-365) add shell command execution

[ http://jira.codehaus.org/browse/CONTINUUM-365?page=all ] yo updated CONTINUUM-365: - Attachment: project_def.png build_def.png the project-confs as screenshot > add shell command execution > --- > > Key: CONTINU

RE: site nav

> > > > I didn't find articles in m2 site ? Is it already published ? > > http://maven.apache.org/articles.html > > But they weren't linked in. I'll link them into the > documentation page for now and deploy the site again. Ok, it's why I didn't find it. I didn't take a look at the docs in SVN

RE: standard form for commit messages

Ok for me, I'll try to not forget to use it ;-) Arnaud > -Message d'origine- > De : Brett Porter [mailto:[EMAIL PROTECTED] > Envoyé : vendredi 28 octobre 2005 03:46 > À : Maven Developers List > Objet : standard form for commit messages > > Hi, > > I've noticed a few things going in

[jira] Updated: (CONTINUUM-365) add shell command execution

[ http://jira.codehaus.org/browse/CONTINUUM-365?page=all ] yo updated CONTINUUM-365: - Attachment: continuum Kopie.log this is the log file. i had some problems with the svn config maybe thats interesting for you too. ill also atach a screenshot of my config. >

Re: [m2] Plugins that depend on other plugin goals

On 31/10/05, Brett Porter <[EMAIL PROTECTED]> wrote: > I see - you are right, that was by design. Thanks for clarifying, it seemed that way but wasn't sure if I was missing something. > I'll have to think about the best path forward on this. Can we move it > to the dev list? Sure, I've posted to

[continuum build - FAILED - update] Mon Oct 31 21:00:00 GMT 2005

Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.21.txt

Re: where to put projects/APIs that support mojos?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think the important considerations are to preserve the committer access that we have in mojo. That is, make sure it's not a major burder to commit a new commons(?) API/project when you're a mojo committer... Aside from that, we have to also conside

[jira] Closed: (MEV-162) stax pom is bogus

[ http://jira.codehaus.org/browse/MEV-162?page=all ] Carlos Sanchez closed MEV-162: -- Assign To: Carlos Sanchez Resolution: Fixed > stax pom is bogus > - > > Key: MEV-162 > URL: http://jira.codehaus.org/browse/MEV-

[jira] Created: (MEV-162) stax pom is bogus

stax pom is bogus - Key: MEV-162 URL: http://jira.codehaus.org/browse/MEV-162 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Dan Diephouse The stax pom here is bogus: http://www.ibiblio.org/maven2/stax/stax-api/1.0/stax

[continuum build - FAILED - update] Mon Oct 31 20:00:00 GMT 2005

Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.20.txt

Re: [m1] Using the latest xdoc and multiproject plugins together

Lukas asked about only updating the PDF plugin, but I don't think that's going to work. The fix we were waiting for in xdoc had to do with duplicate ids that FOP was choking on. (And will likely require updating some of the xml docs once we have the ability to specify the anchors rather tha

Re: where to put projects/APIs that support mojos?

how about in mojo as a mojo-util project that can be used as a dependency by whatever plugins exist in mojo? or it might make since to make a straight out mojo-core project that we could put wrappers on things that are used all over the place like those stale source scanners that I have in most of

[jira] Created: (MAVENUPLOAD-570) statx-utils

statx-utils --- Key: MAVENUPLOAD-570 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-570 Project: maven-upload-requests Type: Task Reporter: Matthew Pocock A bundle of stax-utils taken from https://stax-utils.dev.java.net/files/documents/1519/11894/stax-

Re: [m1] Using the latest xdoc and multiproject plugins together

From: "Arnaud HERITIER" <[EMAIL PROTECTED]> Wendy, Can you explain to me how you build the struts site. I saw that now there are a lot of subproject. Should I download each subproject ? I would like to reproduce the error you had. Check the whole thing out using the 'current' svn external defi

where to put projects/APIs that support mojos?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I have developed a few tools projects that I'm using to support multiple plugins, etc. I wanted to add the plugins to the mojo project, but I'm unsure of the proper place for these supporting projects. I'm not really inclined to add this typ

RE: [m1] Using the latest xdoc and multiproject plugins together

Hi, Wendy, Can you explain to me how you build the struts site. I saw that now there are a lot of subproject. Should I download each subproject ? I would like to reproduce the error you had. I also published the new SNAPSHOT for the xdoc plugin. Can you tes

RE: svn commit: r329875 - /maven/components/trunk/maven-site/src/site/apt/guides/mini/guide-ide-eclipse.apt

Some comments inside. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: lundi 31 octobre 2005 19:22 > To: commits@maven.apache.org > Subject: svn commit: r329875 - /maven/components/trunk/maven- > site/src/site/apt/guides/mini/guide-ide-eclipse.apt [snip] >

[continuum build - FAILED - update] Mon Oct 31 18:30:01 GMT 2005

Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.183001.txt

[jira] Created: (MEV-161) acegisecurity lacks dependency for oro and commons-codec

acegisecurity lacks dependency for oro and commons-codec Key: MEV-161 URL: http://jira.codehaus.org/browse/MEV-161 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Oliver Siegmar ac

[jira] Closed: (MPLICENSE-1) Documentation on how to enable this report is woeful/missing

[ http://jira.codehaus.org/browse/MPLICENSE-1?page=all ] Lukas Theussl closed MPLICENSE-1: - Resolution: Fixed > Documentation on how to enable this report is woeful/missing > > >

[maven2 build - SUCCESS - update] Mon Oct 31 18:15:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051031.181501.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051031.181501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

[jira] Closed: (MPLICENSE-2) Invalid form feed NCR () generated.

[ http://jira.codehaus.org/browse/MPLICENSE-2?page=all ] Lukas Theussl closed MPLICENSE-2: - Resolution: Won't Fix > Invalid form feed NCR () generated. > - > > Key: MPLICENSE-2 > URL: http:

[jira] Closed: (MPCASTOR-5) maven.castor.properties.dir is not added to the classpath

[ http://jira.codehaus.org/browse/MPCASTOR-5?page=all ] Lukas Theussl closed MPCASTOR-5: Resolution: Won't Fix > maven.castor.properties.dir is not added to the classpath > - > > Key:

[continuum build - FAILED - update] Mon Oct 31 18:00:00 GMT 2005

Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.18.txt

[jira] Updated: (CONTINUUM-404) add a way for admins to access the log from the web interface

[ http://jira.codehaus.org/browse/CONTINUUM-404?page=all ] Emmanuel Venisse updated CONTINUUM-404: --- Assign To: Emmanuel Venisse Fix Version: 1.1 > add a way for admins to access the log from the web interface > ---

[maven2 build - SUCCESS - update] Mon Oct 31 17:45:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051031.174500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051031.174500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

[m2] Functional test use cases

Hi everyone (and especially Kenney to whom I had promised this email), Here are some functional use cases I want to write for the Cargo m2 plugin. I'm currently using the m2 embedder in junit tests to do this. Kenney wanted to check what were the use cases so that we could disucss how the maven-it

[maven2 build - SUCCESS - update] Mon Oct 31 17:30:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051031.173000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051031.173000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

[jira] Closed: (CONTINUUM-405) no infrmation why build ended with error

[ http://jira.codehaus.org/browse/CONTINUUM-405?page=all ] Emmanuel Venisse closed CONTINUUM-405: -- Assign To: Emmanuel Venisse Resolution: Duplicate Fix Version: 1.1 Fixed in CONTINUUM-400 > no infrmation why build ended with error

[continuum build - FAILED - update] Mon Oct 31 17:30:00 GMT 2005

Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.173000.txt

[maven2 build - SUCCESS - update] Mon Oct 31 17:15:00 GMT 2005

Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051031.171500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051031.171500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comman

  1   2   >