Re: Committers let's agree on how we make changes to a plugin
+1 on that one too -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au Jason van Zyl <[EMAIL PROTECTED]> wrote on 05/06/2003 10:34:11 PM: > On Thu, 2003-06-05 at 04:04, Rafal Krzewski wrote: > > Jason van Zyl wrote: > > > > > Document it and it will more than likely be followed. > > > > I wish it would be so simple. Humans are lazy and forgetful, even the > > best documenation won't change that. The most common case is that some > > a person wants to apply just a tiny little fix to a plugin. > > > > I think that public scolding people that break the rules will be > > neccessary addition to the documentation... > > Personally I would like a tool to help, but that will be a dream for > some time. The releases for example: I don't think you can make quick, > consistent and safe releases without a tool that performs all sorts of > checks and helps you do most of the work. I realize how hard these tools > are to write but ultimately will be the only real solution. > > > R. > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://tambora.zenplex.org > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > - > 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: RC1 release plans
Sorry, newbie protocol question wrt > 3) Submit an issue and hope someone takes notice. No guarantees. I'd like to find a committer for Maven-473, but I assume that one should not email committers directly and that this mailing list is not the place to plead for attention (as I've just done). So... Any committers interested in Maven-473? (doh! I did it again!) http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-473 Should non-committers do something other than mail this list to find committers? Thanks - Wes Ben Walding wrote: After the scathing blame-storming attack by Nick (just kidding), we've decided to prepare for a Maven RC1 release. You can track progress on our attempt to get everything ready for an RC1 via JIRA. All bugs attached to MAVEN-401 will be processed prior to the release OR I will mail to the user / dev lists if I remove dependent issues (highly unlikely). If you have something that positively must be fixed you have one of three choices 1) Find a compliant committer who will fix the problem for you. No guarantees. 2) ***BEST PLAN*** Submit a tested patch and then find a committer who will apply the patch and test it 3) Submit an issue and hope someone takes notice. No guarantees. Changes to core functionality will probably not be considered at this stage as we just want to clean up what we have, run it for a few days and then release it. Please note: If it's not logged in JIRA, the problem does not exist. By all means post to the dev list to find out if it is known and listed somewhere else, but ultimately, don't expect that mailing to the dev list will get it fixed. IT MUST BE PUT INTO JIRA. (Committers: Can you funnel changes to the MAVEN-401 dependant issues through me please - Under NO circumstances unlink issues from MAVEN-401) We'll be looking to lock down for release end of this week with an internal release after the weekend and a public release mid week (all things permitting). Cheers, Ben - 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]
RC1 WAS: [jira] Closed: (MAVEN-379) ...
> As I understand it, you just volunteered to fix MAVEN-472? :) Sure thing, it was on my list of stuff to look at after I got through the other stuff you gave me :) My nightly builds are currently most affected by 442 and 472. I'll move it up the list. I'll try knocking off MAVEN-442 first - its more important to me. Can we make that a blocker of RC1? It relates to relative directory handling and the reactor. What is the lifespan of fixes to these? Are they maven-old only, and likely to be rwritten for maven-new, or do they need to be consistent for both? I ask because the only solution I can think of right now for 442 that might work after previous tests have failed is to have the POM reading mechanism take in basedir and put it front of resource.directory and then canonicalise it. This might mess up the interface to the pom reading, but I imagine we can do something better for a new version. Don't know how much time I'll have to work on it, so if someone else is going to have a look, just drop me a note here, in jira or at [EMAIL PROTECTED] and we can compare notes. Thanks, Brett Ben Walding wrote: I aim to create nightly build system as part of this release. This should remove the need to build everything all the time. Brett Porter wrote: Doesn't help my poor 128mb laptop that thrashes to death :) I just build individual plugins as they change now though, and use maven maven:jar-install. Looking forward to maven-new then! Cheers, Brett Ben Walding wrote: This problem is no longer a problem - in so far that the bootstrap works - you just have to feed it a lot of memory. I've raised another bug - MAVEN-472 to cover off your concerns. It is attached to MAVEN-379 and MAVEN-401 Cheers, Ben - 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] -- Web Developer f2 network ~ everything essential 02 8596 4437 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sun JARs
I sent this about 4 hours ago, but it doesn't seem to have made it through (apologies if it appears twice)... Michal Maczka wrote: Is there a chance for: JAXB JAX-RPC JAXB is distributed in Java Web Services Developer Pack http://java.sun.com/webservices/downloads/webservicespack.html ... Ooops. I forgot this was Sun stuff too - there's the "SOAP with Attachments API for Java" saaj.jar in there too... (Not that I've used it but it's used in the JBoss build :-). cheers, Luke. -- Luke Taylor. Monkey Machine Ltd. PGP Key ID: 0x57E9523Chttp://www.monkeymachine.ltd.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RC1 release plans
After the scathing blame-storming attack by Nick (just kidding), we've decided to prepare for a Maven RC1 release. You can track progress on our attempt to get everything ready for an RC1 via JIRA. All bugs attached to MAVEN-401 will be processed prior to the release OR I will mail to the user / dev lists if I remove dependent issues (highly unlikely). If you have something that positively must be fixed you have one of three choices 1) Find a compliant committer who will fix the problem for you. No guarantees. 2) ***BEST PLAN*** Submit a tested patch and then find a committer who will apply the patch and test it 3) Submit an issue and hope someone takes notice. No guarantees. Changes to core functionality will probably not be considered at this stage as we just want to clean up what we have, run it for a few days and then release it. Please note: If it's not logged in JIRA, the problem does not exist. By all means post to the dev list to find out if it is known and listed somewhere else, but ultimately, don't expect that mailing to the dev list will get it fixed. IT MUST BE PUT INTO JIRA. (Committers: Can you funnel changes to the MAVEN-401 dependant issues through me please - Under NO circumstances unlink issues from MAVEN-401) We'll be looking to lock down for release end of this week with an internal release after the weekend and a public release mid week (all things permitting). Cheers, Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Closed: (MAVEN-379) Maven build fails with out of memoryerror
I aim to create nightly build system as part of this release. This should remove the need to build everything all the time. As I understand it, you just volunteered to fix MAVEN-472? :) Brett Porter wrote: Doesn't help my poor 128mb laptop that thrashes to death :) I just build individual plugins as they change now though, and use maven maven:jar-install. Looking forward to maven-new then! Cheers, Brett Ben Walding wrote: This problem is no longer a problem - in so far that the bootstrap works - you just have to feed it a lot of memory. I've raised another bug - MAVEN-472 to cover off your concerns. It is attached to MAVEN-379 and MAVEN-401 Cheers, Ben - 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: [jira] Closed: (MAVEN-379) Maven build fails with out of memoryerror
Doesn't help my poor 128mb laptop that thrashes to death :) I just build individual plugins as they change now though, and use maven maven:jar-install. Looking forward to maven-new then! Cheers, Brett Ben Walding wrote: This problem is no longer a problem - in so far that the bootstrap works - you just have to feed it a lot of memory. I've raised another bug - MAVEN-472 to cover off your concerns. It is attached to MAVEN-379 and MAVEN-401 Cheers, Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Closed: (MAVEN-379) Maven build fails with out of memoryerror
This problem is no longer a problem - in so far that the bootstrap works - you just have to feed it a lot of memory. I've raised another bug - MAVEN-472 to cover off your concerns. It is attached to MAVEN-379 and MAVEN-401 Cheers, Ben Vincent Massol wrote: I don't agree with this "resolution"... Unless it means the "old" Maven is thrown to the garbage which is not the case right now. I have increased by memory to 1GB and I still can't build my projects... This bug should be added as a known bug to the Maven release note if we don't plan to fix it for Maven 1.0. I think this bug should be left open. Thanks -Vincent -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 10 June 2003 16:25 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [jira] Closed: (MAVEN-379) Maven build fails with out of memory error Message: The following issue has been closed. Resolver: Ben Walding Date: Tue, 10 Jun 2003 9:25 AM We've increased the amount of memory in the bootstrap process. Basically the reactor doesn't release memory properly. Giving the reactor more memory is a temporary solution. The permanent solution is Maven 2 which will not be allowed to leak like a sieve. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-379 Here is an overview of the issue: - Key: MAVEN-379 Summary: Maven build fails with out of memory error Type: Bug Status: Closed Priority: Blocker Resolution: FIXED Time Spent: Unknown Estimate: 0 minutes Project: maven Fix Fors: 1.0-beta-10 Versions: 1.0-beta-9 Assignee: Ben Walding Reporter: Konstantin Pribluda Created: Mon, 7 Apr 2003 3:50 AM Updated: Tue, 10 Jun 2003 9:25 AM Environment: Linux box 2.4.19-4GB #1 Fri Sep 13 13:14:56 UTC 2002 i686 unknown Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01) Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) Description: maven build fails with put of memory error. This has nothing to do with linkcheck plugin itself ( seems to me ) because removing directory of linkcheck plugin does not help - another plugin fails with the same error... ---%< [exec] plugin: [exec] java:prepare-filesystem: [exec] [mkdir] Created dir: /home/konstantin/maven- src/maven/src/plugins-build/linkcheck/target/classes [exec] java:compile: [exec] [javac] Compiling 11 source files to /home/konstantin/maven-src/maven/src/plugins- build/linkcheck/target/classes [exec] The system is out of resources. [exec] Consult the following stack trace for details. [exec] java.lang.OutOfMemoryError [exec] BUILD FAILED [exec] com.werken.werkz.UnattainableGoalException: Unable to obtain goal [plugin] -- null:14:34: null:62:48: Compile failed; see the compiler error output for details. [exec] at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:379) [exec] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) [exec] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) [exec] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) [exec] at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116) [exec] at com.werken.werkz.Goal.fire(Goal.java:639) [exec] at com.werken.werkz.Goal.attain(Goal.java:575) [exec] at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394 ) [exec] at org.apache.maven.MavenSession.attainGoals(MavenSession.java:357) [exec] at org.apache.maven.cli.App.doMain(App.java:524) [exec] at org.apache.maven.cli.App.main(App.java:1080) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: 39) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im pl.java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at com.werken.forehead.Forehead.run(Forehead.java:543) [exec] at com.werken.forehead.Forehead.main(Forehead.java:573) [exec] org.apache.commons.jelly.JellyTagException: null:14:34: null:62:48: Compile failed; see the compiler error output for details. [exec] at org.apache.maven.jelly.tags.werkz.LazyAttainGoalTag.doTag(
Re: Sun JARs
On Tue, 2003-06-10 at 17:46, Stephen McConnell wrote: > Jason van Zyl wrote: > > >Hi, > > > >I have updated the sun-licensing-journey.xml file in the xdocs/ > >directory. I have started an initial list of JARs that we would like > >permission to scrape off their sites. If anyone can add to this list > >that would be appreciated. > > > > > > JNLP (WebStart) > http://java.sun.com/products/javawebstart/ Will do. > Steve. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/xdocs sun-licensing-journey.xml
jvanzyl 2003/06/10 14:57:31 Modified:xdocssun-licensing-journey.xml Log: o Adding jnlp Revision ChangesPath 1.8 +1 -0 maven/xdocs/sun-licensing-journey.xml Index: sun-licensing-journey.xml === RCS file: /home/cvs/maven/xdocs/sun-licensing-journey.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- sun-licensing-journey.xml 10 Jun 2003 19:04:48 - 1.7 +++ sun-licensing-journey.xml 10 Jun 2003 21:57:31 - 1.8 @@ -49,6 +49,7 @@ jhall jms jndi + jnlp jsr-94 jta jts - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sun JARs
Jason van Zyl wrote: Hi, I have updated the sun-licensing-journey.xml file in the xdocs/ directory. I have started an initial list of JARs that we would like permission to scrape off their sites. If anyone can add to this list that would be appreciated. JNLP (WebStart) http://java.sun.com/products/javawebstart/ Steve. -- Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/clover/xdocs changes.xml
bwalding2003/06/10 13:58:09 Modified:src/plugins-build/clover project.xml src/plugins-build/clover/xdocs changes.xml Log: Only version 1.2, not 1.3 Revision ChangesPath 1.12 +2 -2 maven/src/plugins-build/clover/project.xml Index: project.xml === RCS file: /home/cvs/maven/src/plugins-build/clover/project.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- project.xml 10 Jun 2003 13:22:47 - 1.11 +++ project.xml 10 Jun 2003 20:58:09 - 1.12 @@ -5,7 +5,7 @@ 3 maven-clover-plugin Maven Clover Plug-in - 1.3-SNAPSHOT + 1.2-SNAPSHOT Java Project Management Tools http://maven.apache.org/reference/plugins/clover/ @@ -18,7 +18,7 @@ 1.2 1.2 - HEAD + NEVER RELEASED 1.4 +1 -1 maven/src/plugins-build/clover/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven/src/plugins-build/clover/xdocs/changes.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- changes.xml 10 Jun 2003 13:25:25 - 1.3 +++ changes.xml 10 Jun 2003 20:58:09 - 1.4 @@ -6,7 +6,7 @@ - + Upgrade to Clover 1.2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Sun JARs
On Tue, 2003-06-10 at 14:53, Michal Maczka wrote: > Is there a chance for: > JAXB > JAX-RPC > > JAXB is distributed in Java Web Services Developer Pack > > http://java.sun.com/webservices/downloads/webservicespack.html > > which contains ... a lot of Jakarta products (tomcat, ant). > > Michal > > P.S. > > Is this list going to be approved as a whole or each item will be considered > separately. > If it is the second option...well at least it is nice to try. I'll send the whole list to Tom Kincaid and he'll see what he can do. He said it didn't seem like it would be a problem as long as somewhere in the process the user agreed to the license. > Michal > > > > > -Original Message- > > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, June 10, 2003 4:42 PM > > To: Maven Developers List > > Subject: Sun JARs > > > > > > Hi, > > > > I have updated the sun-licensing-journey.xml file in the xdocs/ > > directory. I have started an initial list of JARs that we would like > > permission to scrape off their sites. If anyone can add to this list > > that would be appreciated. Once the list is complete, I will send the > > list off to Tom Kincaid and await official approval to use the scraper. > > > > -- > > jvz. > > > > Jason van Zyl > > [EMAIL PROTECTED] > > http://tambora.zenplex.org > > > > In short, man creates for himself a new religion of a rational > > and technical order to justify his work and to be justified in it. > > > > -- Jacques Ellul, The Technological Society > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- > > Sportowy portal INTERIA.PL >>> http://link.interia.pl/f1730 > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sun JARs
On Tue, 2003-06-10 at 13:13, Luke Taylor wrote: > Jason van Zyl wrote: > > > Hi, > > > > I have updated the sun-licensing-journey.xml file in the xdocs/ > > directory. I have started an initial list of JARs that we would like > > permission to scrape off their sites. If anyone can add to this list > > that would be appreciated. Once the list is complete, I will send the > > list off to Tom Kincaid and await official approval to use the scraper. > > > > JTS is another one Ok. > http://java.sun.com/products/jts/ -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/xdocs sun-licensing-journey.xml
jvanzyl 2003/06/10 12:04:48 Modified:xdocssun-licensing-journey.xml Log: o Adding more JARs Revision ChangesPath 1.7 +3 -0 maven/xdocs/sun-licensing-journey.xml Index: sun-licensing-journey.xml === RCS file: /home/cvs/maven/xdocs/sun-licensing-journey.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- sun-licensing-journey.xml 10 Jun 2003 16:12:39 - 1.6 +++ sun-licensing-journey.xml 10 Jun 2003 19:04:48 - 1.7 @@ -42,6 +42,8 @@ activation javamail + jaxb + jax-rpc jce jdbc jhall @@ -49,6 +51,7 @@ jndi jsr-94 jta + jts ejb resolver 1.1 XML Entity and URI Resolvers (by Norman Walsh) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Sun JARs
Is there a chance for: JAXB JAX-RPC JAXB is distributed in Java Web Services Developer Pack http://java.sun.com/webservices/downloads/webservicespack.html which contains ... a lot of Jakarta products (tomcat, ant). Michal P.S. Is this list going to be approved as a whole or each item will be considered separately. If it is the second option...well at least it is nice to try. Michal > -Original Message- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 10, 2003 4:42 PM > To: Maven Developers List > Subject: Sun JARs > > > Hi, > > I have updated the sun-licensing-journey.xml file in the xdocs/ > directory. I have started an initial list of JARs that we would like > permission to scrape off their sites. If anyone can add to this list > that would be appreciated. Once the list is complete, I will send the > list off to Tom Kincaid and await official approval to use the scraper. > > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://tambora.zenplex.org > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- > Sportowy portal INTERIA.PL >>> http://link.interia.pl/f1730 > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: unable to enter new maven bug
On Tue, 10 Jun 2003, Wes Isberg wrote: > For me, the Project combo box for > >http://jira.codehaus.org/secure/CreateIssue!default.jspa > > contains: > >commons attributes >configkit >Enterprise Object Broker >io >phoenix >spice-site >threadpool > > but not maven or any components thereof. > > Am I at the wrong URL? Nope, maven just requires you to be authenticated with Jira before posting a bug. So, log in. -bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
unable to enter new maven bug
For me, the Project combo box for http://jira.codehaus.org/secure/CreateIssue!default.jspa contains: commons attributes configkit Enterprise Object Broker io phoenix spice-site threadpool but not maven or any components thereof. Am I at the wrong URL? Thanks - Wes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sun JARs
Jason van Zyl wrote: Hi, I have updated the sun-licensing-journey.xml file in the xdocs/ directory. I have started an initial list of JARs that we would like permission to scrape off their sites. If anyone can add to this list that would be appreciated. Once the list is complete, I will send the list off to Tom Kincaid and await official approval to use the scraper. JTS is another one http://java.sun.com/products/jts/ -- Luke Taylor. Monkey Machine Ltd. PGP Key ID: 0x57E9523Chttp://www.monkeymachine.ltd.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Process for releasing plugins
On Tue, 2003-06-10 at 12:40, Vincent Massol wrote: > > -Original Message- > > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > > Sent: 10 June 2003 16:41 > > To: Maven Developers List > > Subject: Re: Process for releasing plugins > > > > On Tue, 2003-06-10 at 10:32, Vincent Massol wrote: > > > Hi Maven developers, > > > > > > I have started a guide for releasing plugins: > > > http://nagoya.apache.org/wiki/apachewiki.cgi?Maven/ReleasingPlugins > > > > > > What do you think about following it? > > > > +1 > > > > Do you think you could actually make that an xdoc and not have it in > the > > wiki? > > Sure but wiki is a good start to discuss it and tune it... Let's wait > for a week more and turn it in an xdoc then. Sounds good. > -Vincent > > > > > > Comments on its content? > > > > > > Note that the guide on the Maven development process pages > > > (http://maven.apache.org/development/release-process.html) is very > high > > > level. Maybe we should update it... or reference this new one? > > > > > > Thanks > > > -Vincent > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > -- > > jvz. > > > > Jason van Zyl > > [EMAIL PROTECTED] > > http://tambora.zenplex.org > > > > In short, man creates for himself a new religion of a rational > > and technical order to justify his work and to be justified in it. > > > > -- Jacques Ellul, The Technological Society > > > > > > - > > 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] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [jira] Closed: (MAVEN-379) Maven build fails with out ofmemory error
> -Original Message- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: 10 June 2003 16:29 > To: Maven Developers List > Subject: RE: [jira] Closed: (MAVEN-379) Maven build fails with out > ofmemory error > > On Tue, 2003-06-10 at 10:24, Vincent Massol wrote: > > I don't agree with this "resolution"... Unless it means the "old" Maven > > is thrown to the garbage which is not the case right now. I have > > increased by memory to 1GB and I still can't build my projects... > > > > This bug should be added as a known bug to the Maven release note if we > > don't plan to fix it for Maven 1.0. > > > > I think this bug should be left open. > > The problem is with the interpolation, in your 300+ builds could you do > without interpolation or is it necessary? If it is not I could add a > switch not to interpolate the POM. Do not worry too much, we have found a temporary solution: We spawn a new Maven process for each build (for the generation of the sites). It's a bit longer but it works. Still, the problem is not solved :-) Thanks -Vincent > > > > Thanks > > -Vincent > > > > > -Original Message- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Sent: 10 June 2003 16:25 > > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; > > [EMAIL PROTECTED]; > > > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > > > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > > > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > > > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > > > [EMAIL PROTECTED]; [EMAIL PROTECTED]; > > [EMAIL PROTECTED]; > > > [EMAIL PROTECTED] > > > Subject: [jira] Closed: (MAVEN-379) Maven build fails with out of > > memory > > > error > > > > > > Message: > > > > > >The following issue has been closed. > > > > > >Resolver: Ben Walding > > >Date: Tue, 10 Jun 2003 9:25 AM > > > > > > We've increased the amount of memory in the bootstrap process. > > > > > > Basically the reactor doesn't release memory properly. Giving the > > reactor > > > more memory is a temporary solution. The permanent solution is Maven > > 2 > > > which will not be allowed to leak like a sieve. > > > - > > > View the issue: > > > > > > http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-379 > > > > > > > > > Here is an overview of the issue: > > > - > > > Key: MAVEN-379 > > > Summary: Maven build fails with out of memory error > > >Type: Bug > > > > > > Status: Closed > > >Priority: Blocker > > > Resolution: FIXED > > > > > > Time Spent: Unknown > > >Estimate: 0 minutes > > > > > > Project: maven > > >Fix Fors: > > > 1.0-beta-10 > > >Versions: > > > 1.0-beta-9 > > > > > >Assignee: Ben Walding > > >Reporter: Konstantin Pribluda > > > > > > Created: Mon, 7 Apr 2003 3:50 AM > > > Updated: Tue, 10 Jun 2003 9:25 AM > > > Environment: Linux box 2.4.19-4GB #1 Fri Sep 13 13:14:56 UTC 2002 i686 > > > unknown > > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01) > > > Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) > > > > > > > > > Description: > > > maven build fails with put of memory error. > > > This has nothing to do with linkcheck plugin itself ( seems to me ) > > > because removing directory of linkcheck plugin does not help - > > > another plugin fails with the same error... > > > > > > > > > ---%< > > > [exec] plugin: > > > [exec] java:prepare-filesystem: > > > [exec] [mkdir] Created dir: /home/konstantin/maven- > > > src/maven/src/plugins-build/linkcheck/target/classes > > > > > > [exec] java:compile: > > > [exec] [javac] Compiling 11 source files to > > > /home/konstantin/maven-src/maven/src/plugins- > > > build/linkcheck/target/classes > > > > > > > > > [exec] The system is out of resources. > > > [exec] Consult the following stack trace for details. > > > [exec] java.lang.OutOfMemoryError > > > [exec] BUILD FAILED > > > > > > [exec] com.werken.werkz.UnattainableGoalException: Unable to > > obtain > > > goal [plugin] -- null:14:34: null:62:48: > > Compile > > > failed; see the compiler error output for details. > > > [exec] at > > > > > org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:379) > > > [exec] at > > > org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > > > [exec] at > > > org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > > > [exec] at > > > org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) > > > [exec] at > > > com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116) > > > [exec] at com.werken.werkz.Goal.fire(Goal.java:639) > > > [exec] at com.werken.werkz.Goal.
RE: Process for releasing plugins
> -Original Message- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: 10 June 2003 16:41 > To: Maven Developers List > Subject: Re: Process for releasing plugins > > On Tue, 2003-06-10 at 10:32, Vincent Massol wrote: > > Hi Maven developers, > > > > I have started a guide for releasing plugins: > > http://nagoya.apache.org/wiki/apachewiki.cgi?Maven/ReleasingPlugins > > > > What do you think about following it? > > +1 > > Do you think you could actually make that an xdoc and not have it in the > wiki? Sure but wiki is a good start to discuss it and tune it... Let's wait for a week more and turn it in an xdoc then. -Vincent > > > Comments on its content? > > > > Note that the guide on the Maven development process pages > > (http://maven.apache.org/development/release-process.html) is very high > > level. Maybe we should update it... or reference this new one? > > > > Thanks > > -Vincent > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://tambora.zenplex.org > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > - > 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]
cvs commit: maven/xdocs sun-licensing-journey.xml
jvanzyl 2003/06/10 09:12:39 Modified:xdocssun-licensing-journey.xml Log: o Adding a couple more jars. Revision ChangesPath 1.6 +2 -0 maven/xdocs/sun-licensing-journey.xml Index: sun-licensing-journey.xml === RCS file: /home/cvs/maven/xdocs/sun-licensing-journey.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- sun-licensing-journey.xml 10 Jun 2003 15:51:05 - 1.5 +++ sun-licensing-journey.xml 10 Jun 2003 16:12:39 - 1.6 @@ -44,11 +44,13 @@ javamail jce jdbc + jhall jms jndi jsr-94 jta ejb + resolver 1.1 XML Entity and URI Resolvers (by Norman Walsh) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sun JARs
Hi Jason, On Tue, 2003-06-10 at 16:42, Jason van Zyl wrote: > If anyone can add to this list > that would be appreciated. Once the list is complete, I will send the > list off to Tom Kincaid and await official approval to use the scraper. Have no commit right (yet?) so I send you my wishes here via dev list. * jhall (java help) * resolver 1.1 XML Entity and URI Resolvers (by Norman Walsh) http://wwws.sun.com/software/xml/developers/resolver/article/ Thanks for adding it Jason, OT: btw, jason, is jakarta-commons-sql still alive? The homepage sucks a little bit... (e.g. mailing lists are wrong, no release yet, eclipse files in CVS are out of sync to project.xml etc) -- Martin Skopp Riege Software International GmbH Support: mailto:[EMAIL PROTECTED], Information: http://www.riege.com This email is intended to be viewed with a nonproportional font. Public Key on http://www.keyserver.net, Key-ID: 3D4027B5 Fingerprint: 1970 C78D 9A1D 99FA 5CE4 5C0D 29E6 6A95 3D40 27B5 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/xdocs sun-licensing-journey.xml
jvanzyl 2003/06/10 08:51:06 Modified:xdocssun-licensing-journey.xml Log: o Rules Engine JSR for bob. Revision ChangesPath 1.5 +1 -0 maven/xdocs/sun-licensing-journey.xml Index: sun-licensing-journey.xml === RCS file: /home/cvs/maven/xdocs/sun-licensing-journey.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- sun-licensing-journey.xml 10 Jun 2003 15:48:07 - 1.4 +++ sun-licensing-journey.xml 10 Jun 2003 15:51:05 - 1.5 @@ -46,6 +46,7 @@ jdbc jms jndi + jsr-94 jta ejb - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/xdocs sun-licensing-journey.xml
jvanzyl 2003/06/10 08:48:07 Modified:xdocssun-licensing-journey.xml Log: o Adding jms Revision ChangesPath 1.4 +1 -0 maven/xdocs/sun-licensing-journey.xml Index: sun-licensing-journey.xml === RCS file: /home/cvs/maven/xdocs/sun-licensing-journey.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- sun-licensing-journey.xml 10 Jun 2003 14:39:13 - 1.3 +++ sun-licensing-journey.xml 10 Jun 2003 15:48:07 - 1.4 @@ -44,6 +44,7 @@ javamail jce jdbc + jms jndi jta ejb - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cvs commit: maven/src/plugins-build/clover/xdocs properties.xml changes.xml
Hi Ben,
It seems you have not released version 1.2 before starting work on
1.3... The changes.xml files says that both releases are in CVS...
I have just created a release guide on
http://nagoya.apache.org/wiki/apachewiki.cgi?Maven/ReleasingPlugins
Note that the guide on the Maven development process pages
(http://maven.apache.org/development/release-process.html) is very high
level. Maybe we should update it...
Do you think you could be the first to experiment it? :-)
Thanks
-Vincent
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 10 June 2003 15:25
> To: [EMAIL PROTECTED]
> Subject: cvs commit: maven/src/plugins-build/clover/xdocs
properties.xml
> changes.xml
>
> bwalding2003/06/10 06:25:25
>
> Modified:src/plugins-build/clover/xdocs properties.xml
changes.xml
> Log:
> Doco updates
>
> PR: MAVEN-372
>
> Revision ChangesPath
> 1.3 +1 -8
maven/src/plugins-build/clover/xdocs/properties.xml
>
> Index: properties.xml
> ===
> RCS file: /home/cvs/maven/src/plugins-
> build/clover/xdocs/properties.xml,v
> retrieving revision 1.2
> retrieving revision 1.3
> diff -u -r1.2 -r1.3
> --- properties.xml 10 Jun 2003 13:22:47 - 1.2
> +++ properties.xml 10 Jun 2003 13:25:25 - 1.3
> @@ -44,14 +44,7 @@
>Specifies the location of the Clover database. The
default
> value is
>${maven.build.dir}/clover/database.
>
> -
> -
> - name="maven.clover.report.format">maven.clover.report.format
> - No (default "html")
> -
> -Specifies the format of the Clover report output
> -
> -
> +
>
>
>
>
>
>
> 1.3 +6 -0
maven/src/plugins-build/clover/xdocs/changes.xml
>
> Index: changes.xml
> ===
> RCS file:
/home/cvs/maven/src/plugins-build/clover/xdocs/changes.xml,v
> retrieving revision 1.2
> retrieving revision 1.3
> diff -u -r1.2 -r1.3
> --- changes.xml 4 Jun 2003 13:51:26 - 1.2
> +++ changes.xml 10 Jun 2003 13:25:25 - 1.3
> @@ -6,6 +6,12 @@
>
>
>
> +
> +
> + Upgrade to Clover 1.2
> +
> +
> +
>
>
>Make sure that test failures or errors do not stop the
> generation
>
>
>
>
> -
> 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: cvs commit: maven/xdocs sun-licensing-journey.xml
Could you also add JMS to that list please? Thanks, Tim > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 11 June 2003 12:39 AM > To: [EMAIL PROTECTED] > Subject: cvs commit: maven/xdocs sun-licensing-journey.xml > > > jvanzyl 2003/06/10 07:39:13 > > Modified:xdocssun-licensing-journey.xml > Log: > o Catching up with discussions with Tom Kincaid. > > Revision ChangesPath > 1.3 +23 -2 maven/xdocs/sun-licensing-journey.xml > > Index: sun-licensing-journey.xml > === > RCS file: /home/cvs/maven/xdocs/sun-licensing-journey.xml,v > retrieving revision 1.2 > retrieving revision 1.3 > diff -u -r1.2 -r1.3 > --- sun-licensing-journey.xml 21 Feb 2003 14:50:15 - 1.2 > +++ sun-licensing-journey.xml 10 Jun 2003 14:39:13 - 1.3 > @@ -17,16 +17,37 @@ > > > > -[ 18 Feb 2002 ] Geir has contacted Bill Shannon and asked > +[ 18 Feb 2003 ] Geir has contacted Bill Shannon and asked >what could be done about the JavaMail license. > Geir explained that >Maven doesn't use JavaMail directly but on behalf > of project and >though even technically the license is violated > the spirit of >the license is not. > > > -[ 18 Feb 2002 ] Bill Shannon responds that Maven's > use is in the > +[ 18 Feb 2003 ] Bill Shannon responds that Maven's > use is in the >spirit of the license though not technically > allowed. He directs >us to Tom Kinkaid who is the manager of JavaMail. > + > + > +[ 30 April 2003 ] I had a long discussion with Tom > Kincaid about > +the licensing issues and we will not be able to > distribute the Sun > +JARs from ibiblio but that the scraper would be a > workable solution. > +I have to get Tom a list of JARs that we would > like to be able to > +retrieve with the scraper and he would commit to > checking with > +each of the people within Sun responsible for the > said package. > + > + > +[ 10 June 2003 ] The following is a list of JARs > that we would > +like Tom Kincaid to check into: > + > + activation > + javamail > + jce > + jdbc > + jndi > + jta > + ejb > + > > > > > > > > - > 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]
Sun JARs
Hi, I have updated the sun-licensing-journey.xml file in the xdocs/ directory. I have started an initial list of JARs that we would like permission to scrape off their sites. If anyone can add to this list that would be appreciated. Once the list is complete, I will send the list off to Tom Kincaid and await official approval to use the scraper. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Process for releasing plugins
On Tue, 2003-06-10 at 10:32, Vincent Massol wrote: > Hi Maven developers, > > I have started a guide for releasing plugins: > http://nagoya.apache.org/wiki/apachewiki.cgi?Maven/ReleasingPlugins > > What do you think about following it? +1 Do you think you could actually make that an xdoc and not have it in the wiki? > Comments on its content? > > Note that the guide on the Maven development process pages > (http://maven.apache.org/development/release-process.html) is very high > level. Maybe we should update it... or reference this new one? > > Thanks > -Vincent > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/xdocs sun-licensing-journey.xml
jvanzyl 2003/06/10 07:39:13 Modified:xdocssun-licensing-journey.xml Log: o Catching up with discussions with Tom Kincaid. Revision ChangesPath 1.3 +23 -2 maven/xdocs/sun-licensing-journey.xml Index: sun-licensing-journey.xml === RCS file: /home/cvs/maven/xdocs/sun-licensing-journey.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- sun-licensing-journey.xml 21 Feb 2003 14:50:15 - 1.2 +++ sun-licensing-journey.xml 10 Jun 2003 14:39:13 - 1.3 @@ -17,16 +17,37 @@ -[ 18 Feb 2002 ] Geir has contacted Bill Shannon and asked +[ 18 Feb 2003 ] Geir has contacted Bill Shannon and asked what could be done about the JavaMail license. Geir explained that Maven doesn't use JavaMail directly but on behalf of project and though even technically the license is violated the spirit of the license is not. -[ 18 Feb 2002 ] Bill Shannon responds that Maven's use is in the +[ 18 Feb 2003 ] Bill Shannon responds that Maven's use is in the spirit of the license though not technically allowed. He directs us to Tom Kinkaid who is the manager of JavaMail. + + +[ 30 April 2003 ] I had a long discussion with Tom Kincaid about +the licensing issues and we will not be able to distribute the Sun +JARs from ibiblio but that the scraper would be a workable solution. +I have to get Tom a list of JARs that we would like to be able to +retrieve with the scraper and he would commit to checking with +each of the people within Sun responsible for the said package. + + +[ 10 June 2003 ] The following is a list of JARs that we would +like Tom Kincaid to check into: + + activation + javamail + jce + jdbc + jndi + jta + ejb + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Process for releasing plugins
Hi Maven developers, I have started a guide for releasing plugins: http://nagoya.apache.org/wiki/apachewiki.cgi?Maven/ReleasingPlugins What do you think about following it? Comments on its content? Note that the guide on the Maven development process pages (http://maven.apache.org/development/release-process.html) is very high level. Maybe we should update it... or reference this new one? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [jira] Closed: (MAVEN-379) Maven build fails with out ofmemory error
On Tue, 2003-06-10 at 10:24, Vincent Massol wrote: > I don't agree with this "resolution"... Unless it means the "old" Maven > is thrown to the garbage which is not the case right now. I have > increased by memory to 1GB and I still can't build my projects... > > This bug should be added as a known bug to the Maven release note if we > don't plan to fix it for Maven 1.0. > > I think this bug should be left open. The problem is with the interpolation, in your 300+ builds could you do without interpolation or is it necessary? If it is not I could add a switch not to interpolate the POM. > Thanks > -Vincent > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: 10 June 2003 16:25 > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED]; > > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > > [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED]; > > [EMAIL PROTECTED] > > Subject: [jira] Closed: (MAVEN-379) Maven build fails with out of > memory > > error > > > > Message: > > > >The following issue has been closed. > > > >Resolver: Ben Walding > >Date: Tue, 10 Jun 2003 9:25 AM > > > > We've increased the amount of memory in the bootstrap process. > > > > Basically the reactor doesn't release memory properly. Giving the > reactor > > more memory is a temporary solution. The permanent solution is Maven > 2 > > which will not be allowed to leak like a sieve. > > - > > View the issue: > > > > http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-379 > > > > > > Here is an overview of the issue: > > - > > Key: MAVEN-379 > > Summary: Maven build fails with out of memory error > >Type: Bug > > > > Status: Closed > >Priority: Blocker > > Resolution: FIXED > > > > Time Spent: Unknown > >Estimate: 0 minutes > > > > Project: maven > >Fix Fors: > > 1.0-beta-10 > >Versions: > > 1.0-beta-9 > > > >Assignee: Ben Walding > >Reporter: Konstantin Pribluda > > > > Created: Mon, 7 Apr 2003 3:50 AM > > Updated: Tue, 10 Jun 2003 9:25 AM > > Environment: Linux box 2.4.19-4GB #1 Fri Sep 13 13:14:56 UTC 2002 i686 > > unknown > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01) > > Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) > > > > > > Description: > > maven build fails with put of memory error. > > This has nothing to do with linkcheck plugin itself ( seems to me ) > > because removing directory of linkcheck plugin does not help - > > another plugin fails with the same error... > > > > > > ---%< > > [exec] plugin: > > [exec] java:prepare-filesystem: > > [exec] [mkdir] Created dir: /home/konstantin/maven- > > src/maven/src/plugins-build/linkcheck/target/classes > > > > [exec] java:compile: > > [exec] [javac] Compiling 11 source files to > > /home/konstantin/maven-src/maven/src/plugins- > > build/linkcheck/target/classes > > > > > > [exec] The system is out of resources. > > [exec] Consult the following stack trace for details. > > [exec] java.lang.OutOfMemoryError > > [exec] BUILD FAILED > > > > [exec] com.werken.werkz.UnattainableGoalException: Unable to > obtain > > goal [plugin] -- null:14:34: null:62:48: > Compile > > failed; see the compiler error output for details. > > [exec] at > > > org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:379) > > [exec] at > > org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > > [exec] at > > org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > > [exec] at > > org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) > > [exec] at > > com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116) > > [exec] at com.werken.werkz.Goal.fire(Goal.java:639) > > [exec] at com.werken.werkz.Goal.attain(Goal.java:575) > > [exec] at > > > org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394 > ) > > [exec] at > > org.apache.maven.MavenSession.attainGoals(MavenSession.java:357) > > [exec] at org.apache.maven.cli.App.doMain(App.java:524) > > [exec] at org.apache.maven.cli.App.main(App.java:1080) > > [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > > Method) > > [exec] at > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav > a: > > 39) > > [exec] at > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > Im > > pl.java
RE: [jira] Closed: (MAVEN-379) Maven build fails with out of memory error
I don't agree with this "resolution"... Unless it means the "old" Maven is thrown to the garbage which is not the case right now. I have increased by memory to 1GB and I still can't build my projects... This bug should be added as a known bug to the Maven release note if we don't plan to fix it for Maven 1.0. I think this bug should be left open. Thanks -Vincent > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: 10 June 2003 16:25 > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: [jira] Closed: (MAVEN-379) Maven build fails with out of memory > error > > Message: > >The following issue has been closed. > >Resolver: Ben Walding >Date: Tue, 10 Jun 2003 9:25 AM > > We've increased the amount of memory in the bootstrap process. > > Basically the reactor doesn't release memory properly. Giving the reactor > more memory is a temporary solution. The permanent solution is Maven 2 > which will not be allowed to leak like a sieve. > - > View the issue: > > http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-379 > > > Here is an overview of the issue: > - > Key: MAVEN-379 > Summary: Maven build fails with out of memory error >Type: Bug > > Status: Closed >Priority: Blocker > Resolution: FIXED > > Time Spent: Unknown >Estimate: 0 minutes > > Project: maven >Fix Fors: > 1.0-beta-10 >Versions: > 1.0-beta-9 > >Assignee: Ben Walding >Reporter: Konstantin Pribluda > > Created: Mon, 7 Apr 2003 3:50 AM > Updated: Tue, 10 Jun 2003 9:25 AM > Environment: Linux box 2.4.19-4GB #1 Fri Sep 13 13:14:56 UTC 2002 i686 > unknown > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01) > Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) > > > Description: > maven build fails with put of memory error. > This has nothing to do with linkcheck plugin itself ( seems to me ) > because removing directory of linkcheck plugin does not help - > another plugin fails with the same error... > > > ---%< > [exec] plugin: > [exec] java:prepare-filesystem: > [exec] [mkdir] Created dir: /home/konstantin/maven- > src/maven/src/plugins-build/linkcheck/target/classes > > [exec] java:compile: > [exec] [javac] Compiling 11 source files to > /home/konstantin/maven-src/maven/src/plugins- > build/linkcheck/target/classes > > > [exec] The system is out of resources. > [exec] Consult the following stack trace for details. > [exec] java.lang.OutOfMemoryError > [exec] BUILD FAILED > > [exec] com.werken.werkz.UnattainableGoalException: Unable to obtain > goal [plugin] -- null:14:34: null:62:48: Compile > failed; see the compiler error output for details. > [exec] at > org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:379) > [exec] at > org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > [exec] at > org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > [exec] at > org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) > [exec] at > com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116) > [exec] at com.werken.werkz.Goal.fire(Goal.java:639) > [exec] at com.werken.werkz.Goal.attain(Goal.java:575) > [exec] at > org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394 ) > [exec] at > org.apache.maven.MavenSession.attainGoals(MavenSession.java:357) > [exec] at org.apache.maven.cli.App.doMain(App.java:524) > [exec] at org.apache.maven.cli.App.main(App.java:1080) > [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > [exec] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a: > 39) > [exec] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Im > pl.java:25) > [exec] at java.lang.reflect.Method.invoke(Method.java:324) > [exec] at com.werken.forehead.Forehead.run(Forehead.java:543) > [exec] at com.werken.forehead.Forehead.main(Forehead.java:573) > [exec] org.apache.commons.jelly.JellyTagException: null:14:34: > null:62:48: Compile failed; see the compiler > error output for details. > [exec] at > org.apache.maven.jelly.tags.werkz.LazyAttainGoalTag.doTag(LazyAttainGoal Ta > g.java:111) > [exec] at > or
cvs commit: maven/xdocs/reference developer-guide.xml
bwalding2003/06/10 07:17:21 Modified:xdocs/reference developer-guide.xml Log: Documentation patch PR:MAVEN-434 Submitted by: Brett Porter Revision ChangesPath 1.8 +51 -0 maven/xdocs/reference/developer-guide.xml Index: developer-guide.xml === RCS file: /home/cvs/maven/xdocs/reference/developer-guide.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- developer-guide.xml 30 Mar 2003 22:59:57 - 1.7 +++ developer-guide.xml 10 Jun 2003 14:17:21 - 1.8 @@ -194,6 +194,57 @@ + +When writing plugins, you will need to control the class loaders that + are used to load your specified dependencies. The following table + shows the classloaders available: + + + +Class loader +Description + + ++ + This class loader is used if none is specified in the dependency. + This means that the dependency is loaded into the plugin's class + loader, making it available to the plugin only. + + + +root + + This is the Ant class loader, and the most common override used in + a plugin. Use this if you need to specify a dependency used by a + custom Ant task used in the plugin. + + + +root.maven + + This is the Maven class loader. Use it if you wish to have the + dependency available to the Maven core. + + + +To specify a classloader for a dependency, add a section similar to + the following to your plugin's project.xml: + + +You should also note that the same properties can be used in your + projects, not just plugins. This may be required if you are writing + custom scripts in maven.xml. + + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/bootstrap/org/apache/maven BootstrapTask.java
bwalding2003/06/10 07:16:08
Modified:src/bootstrap/org/apache/maven BootstrapTask.java
Log:
Patch to make BootstrapTask a bit more robust / more logging.
PR:MAVEN-434
Submitted by: Brett Porter
Revision ChangesPath
1.15 +23 -10maven/src/bootstrap/org/apache/maven/BootstrapTask.java
Index: BootstrapTask.java
===
RCS file: /home/cvs/maven/src/bootstrap/org/apache/maven/BootstrapTask.java,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- BootstrapTask.java10 Feb 2003 14:54:00 - 1.14
+++ BootstrapTask.java10 Jun 2003 14:16:08 - 1.15
@@ -57,8 +57,6 @@
*/
import java.io.File;
-import java.net.URL;
-
import java.util.Iterator;
import java.util.List;
import java.util.ArrayList;
@@ -353,14 +351,29 @@
directory.mkdirs();
}
-HttpUtils.getFile( baseUrl + file,
- destinationFile,
- ignoreErrors,
- useTimestamp,
- proxyHost,
- proxyPort,
- proxyUserName,
- proxyPassword);
+log( "Downloading dependency: " + baseUrl + file );
+
+int numRetries = 3;
+while ( numRetries >= 0 )
+{
+try
+{
+HttpUtils.getFile( baseUrl + file,
+ destinationFile,
+ ignoreErrors,
+ useTimestamp,
+ proxyHost,
+ proxyPort,
+ proxyUserName,
+ proxyPassword);
+break;
+}
+catch (Exception e)
+{
+numRetries--;
+continue;
+}
+}
}
catch (Exception e)
{
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/xdoc/src/plugin-resources site.jsl
bwalding2003/06/10 06:50:20 Modified:src/plugins-build/xdoc/src/plugin-resources site.jsl Log: The simple and neat solution. Only sub elements of the xdoc head element are placed into the resulting html file PR: MAVEN-396 Submitted by: Brett Porter Revision ChangesPath 1.26 +1 -5 maven/src/plugins-build/xdoc/src/plugin-resources/site.jsl Index: site.jsl === RCS file: /home/cvs/maven/src/plugins-build/xdoc/src/plugin-resources/site.jsl,v retrieving revision 1.25 retrieving revision 1.26 diff -u -r1.25 -r1.26 --- site.jsl 23 Apr 2003 15:57:05 - 1.25 +++ site.jsl 10 Jun 2003 13:50:20 - 1.26 @@ -67,7 +67,7 @@ - + @@ -443,10 +443,6 @@ - - - - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/messages messages_zh_CN.properties
bwalding2003/06/10 06:40:40
Added: src/messages messages_zh_CN.properties
Log:
Chinese? messages. Tried to spell check them, but word kept complaining.
PR: MAVEN-376
Revision ChangesPath
1.1 maven/src/messages/messages_zh_CN.properties
Index: messages_zh_CN.properties
===
# --
# ÏîÄ¿ÑéÖ¤
# --
failed.download.warning=¾¯¸æ£º ${1} ÏÂÔØʧ°Ü¡£
remote.repository.disabled.warning=½ûֹʹÓÃÔ¶³Ì×ÊÔ´²Ö¿â¡£
directory.nonexistant.warning=Ŀ¼ ${1} ²»´æÔÚ¡£ ³¢ÊÔн¨ÖС¡
not.directory.warning=${1} ²»ÊÇĿ¼¡£
not.writable.warning=${1} Ö»¶Á¡£
cannot.create.directory.warning=´´½¨Ä¿Â¼ ${1} ʧ°Ü¡£
maven.repo.local.unset.warning=ûÓÐÉèÖà maven.repo.local ÊôÐÔ¡£
single.unsatisfied.dependency.error=ÓÉÓÚÒÔϵÄÒÀÀµÈ±ÉÙ£¬´´½¨²»ÄܽøÐУº
multiple.unsatisfied.dependency.error=ÓÉÓÚÒÔϵÄÒÀÀµÈ±ÉÙ£¬´´½¨²»ÄܽøÐУº
offline.snapshot.warning=ÀëÏßʱ´´½¨£¬¿ÉÄÜ ${1} ¹ýÆÚ£¡
download.message=³¢ÊÔÏÂÔØ ${1}¡¡
plugin.loading.error=×°Èë plugin ${1} ʧ°Ü¡£
empty.descriptor.error=Îļþ ${1} µÄ³¤¶ÈΪ0¡£
checksum.verification.error=ÒÔÏÂ×ÊÔ´Òѱ»ÆÆ»µ£º${1}¡£
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/clover/xdocs properties.xml changes.xml
bwalding2003/06/10 06:25:25
Modified:src/plugins-build/clover/xdocs properties.xml changes.xml
Log:
Doco updates
PR: MAVEN-372
Revision ChangesPath
1.3 +1 -8 maven/src/plugins-build/clover/xdocs/properties.xml
Index: properties.xml
===
RCS file: /home/cvs/maven/src/plugins-build/clover/xdocs/properties.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- properties.xml10 Jun 2003 13:22:47 - 1.2
+++ properties.xml10 Jun 2003 13:25:25 - 1.3
@@ -44,14 +44,7 @@
Specifies the location of the Clover database. The default value is
${maven.build.dir}/clover/database.
-
-
- maven.clover.report.format
- No (default "html")
-
-Specifies the format of the Clover report output
-
-
+
1.3 +6 -0 maven/src/plugins-build/clover/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven/src/plugins-build/clover/xdocs/changes.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- changes.xml 4 Jun 2003 13:51:26 - 1.2
+++ changes.xml 10 Jun 2003 13:25:25 - 1.3
@@ -6,6 +6,12 @@
+
+
+ Upgrade to Clover 1.2
+
+
+
Make sure that test failures or errors do not stop the generation
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/clover/xdocs properties.xml
bwalding2003/06/10 06:22:47
Modified:src/plugins-build/clover project.xml plugin.jelly
plugin.properties
src/plugins-build/clover/xdocs properties.xml
Log:
I'm not going to pretend that this works very well.
* Flushpolicy - it's just a hack that we have a 500ms flush interval. Should be
allowed to flush with an ant task
* Basically clover 1.2 sort of works, want to check something that reasonably works
in before I break it again.
PR: MAVEN-372
Revision ChangesPath
1.11 +3 -10 maven/src/plugins-build/clover/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven/src/plugins-build/clover/project.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- project.xml 4 Jun 2003 13:51:26 - 1.10
+++ project.xml 10 Jun 2003 13:22:47 - 1.11
@@ -5,7 +5,7 @@
3
maven-clover-plugin
Maven Clover Plug-in
- 1.2-SNAPSHOT
+ 1.3-SNAPSHOT
Java Project Management Tools
http://maven.apache.org/reference/plugins/clover/
@@ -72,17 +72,10 @@
clover
- 1.0
+ 1.2
root
-
-
- velocity
- 1.3
-
-root.maven
-
-
+
1.7 +57 -63maven/src/plugins-build/clover/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven/src/plugins-build/clover/plugin.jelly,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- plugin.jelly 4 Jun 2003 13:51:26 - 1.6
+++ plugin.jelly 10 Jun 2003 13:22:47 - 1.7
@@ -4,35 +4,28 @@
xmlns:j="jelly:core"
xmlns:ant="jelly:ant"
xmlns:maven="jelly:maven"
+ xmlns:java="java"
+ xmlns:test="test"
xmlns:doc="doc">
-
-
+
+
+
+
+
+
+
+
-
+
@@ -58,36 +51,44 @@
-
+description="Create the needed directory structure">
+
+
+
+
-
${pom.getContext().setVariable('build.compiler',"org.apache.tools.ant.taskdefs.CloverCompilerAdapter")}
+ Setting Clover compiler
+
+ Now using primary build.compiler : ${build.compiler}
+
${pom.getContext().removeVariable('build.compiler')}
-
-
-
+
+
+
-
+
+
+
-
${pom.getPluginContext('maven-java-plugin').setVariable('maven.build.dest',tmp)}
+
${pom.getPluginContext('maven-test-plugin').setVariable('maven.build.dest',tmp)}
-
@@ -98,43 +99,37 @@
description="Generate HTML test coverage reports with Clover"
prereqs="clover:html-report"/>
-
-
-
+
+
+
+
-
+
+
-
+
+
+
+
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
@@ -144,7 +139,6 @@
-
1.2 +0 -9 maven/src/plugins-build/clover/plugin.properties
Index: plugin.properties
===
RCS file: /home/cvs/maven/src/plugins-build/clover/plugin.properties,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- plugin.properties 24 Jan 2003 03:45:04 - 1.1
+++ plugin.properties 10 Jun 2003 13:22:47 - 1.2
@@ -7,13 +7,4 @@
maven.build.clover = ${maven.build.dir}/clover
maven.build.clover.classes = ${maven.build.clover}/classes
-#maven.build.clover.src = ${maven.build.clover}/src
-#clover.tmpdir = ${maven.build.clover.src}
-
-# Location of Clover database
-# (used only if maven.compile.clover = true)
maven.clover.database.dir = ${maven.build.clover}/database
-
-clover.preserve=true
-clover.flushpolicy=interval
-clover.flushpolicy.interval=10
1.2 +7 -0 maven/src/plugins-build/clover/xdocs/properties.xml
Index: properties.xml
===
RCS file: /home/cvs/maven/src/plugins-build/clover/xdocs/properties.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- properties.xml24 Jan 2003 03:45:06 - 1.1
+++ properties.xml10 Jun 2003 13:22:47 - 1.2
@@ -45,6 +45,13 @@
${maven.build.dir}/clover/database.
cvs commit: maven/src/plugins-build/eclipse plugin.jelly
bwalding2003/06/10 03:17:26 Modified:src/plugins-build/test plugin.jelly src/plugins-build/eclipse plugin.jelly Log: Try and have some kind of "standard" for the hacks that allow the plugins to be reliably loaded from another plugin PR: MAVEN-372 Revision ChangesPath 1.10 +6 -9 maven/src/plugins-build/test/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven/src/plugins-build/test/plugin.jelly,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- plugin.jelly 16 Apr 2003 12:48:10 - 1.9 +++ plugin.jelly 10 Jun 2003 10:17:25 - 1.10 @@ -5,15 +5,6 @@ xmlns:resources="resources" xmlns:define="jelly:define"> - - - - - - - @@ -309,4 +300,10 @@ + + + + + + 1.18 +1 -1 maven/src/plugins-build/eclipse/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven/src/plugins-build/eclipse/plugin.jelly,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- plugin.jelly 26 May 2003 13:36:05 - 1.17 +++ plugin.jelly 10 Jun 2003 10:17:26 - 1.18 @@ -5,7 +5,7 @@ xmlns:ant="jelly:ant" xmlns:test="test"> - + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/java plugin.jelly
bwalding2003/06/10 03:13:55
Modified:src/plugins-build/java plugin.jelly
Log:
Allows the clover plugin to hook onto and alter compilation settings on the fly.
PR: MAVEN-372
Revision ChangesPath
1.17 +8 -1 maven/src/plugins-build/java/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven/src/plugins-build/java/plugin.jelly,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- plugin.jelly 26 Apr 2003 09:56:23 - 1.16
+++ plugin.jelly 10 Jun 2003 10:13:54 - 1.17
@@ -3,6 +3,7 @@
@@ -42,7 +43,7 @@
-
+Compiling to ${maven.build.dest}
+
+
+
+
+
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Committers let's agree on how we make changes to a plugin
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: 10 June 2003 09:42 > To: Maven Developers List > Subject: Re: Committers let's agree on how we make changes to a plugin > > Big +1 from meLet's get it documented somewhere!!! Done here: http://nagoya.apache.org/wiki/apachewiki.cgi?Maven/PluginModificationGui delines and linked in the "development process" page. -Vincent > -- > dIon Gillard, Multitask Consulting > Blog: http://blogs.codehaus.org/people/dion/ > Work: http://www.multitask.com.au > > > "Vincent Massol" <[EMAIL PROTECTED]> wrote on 04/06/2003 10:49:15 PM: > > > Hi, > > > > What do you think about the following process for making changes to a > > plugin (and for accepting patches): > > > > 1/ Update xdocs/changes.xml (create it if it does not exist) and > > describe the change > > 2/ Update the goals.xml/properties.xml and more generally the plugin > > documentation if changes affecting users have been made > > 3/ Ensure that the version in plugin.xml is a SNAPSHOT version (i.e. not > > delivered). Unless you're making a release of the plugin. > > 4/ Make sure the section of project.xml is up to date > > > > Almost everytime I make changes to a plugin I find that these simple > > rules are not followed (Note: I know dIon is also careful about them). > > > > What do you think? > > > > 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]
Re: Committers let's agree on how we make changes to a plugin
Big +1 from meLet's get it documented somewhere!!! -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au "Vincent Massol" <[EMAIL PROTECTED]> wrote on 04/06/2003 10:49:15 PM: > Hi, > > What do you think about the following process for making changes to a > plugin (and for accepting patches): > > 1/ Update xdocs/changes.xml (create it if it does not exist) and > describe the change > 2/ Update the goals.xml/properties.xml and more generally the plugin > documentation if changes affecting users have been made > 3/ Ensure that the version in plugin.xml is a SNAPSHOT version (i.e. not > delivered). Unless you're making a release of the plugin. > 4/ Make sure the section of project.xml is up to date > > Almost everytime I make changes to a plugin I find that these simple > rules are not followed (Note: I know dIon is also careful about them). > > What do you think? > > 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]
