I'd vote for Brett's approach that if he gets it fixed, great, otherwise
release it. The memory leak primarily affects large multiproject usages of
Maven, and in many ways, that is the part that really needs the stuff Jason
is working on to succeed. For building a single project, or just a couple
Hi all,
Now that the plugin download functionality works (fixed about a week ago)
when we get the next RC or 1.0 out we should mention in the ANNOUNCE emails
how to use it to download new plugins. This should help speed up adoption
of new plugins. For instance, for the JCoverage 1.0.2 version, t
It should be kept with Cocoon. If a plugin has very specific functionaliyt
like this one, then it should be kept with the project as they would be best
positioned to maintain it in the long run. Additionally, while right now
people may look to maven.apache.org for plugins, the plugins page will
e
I wrote a little plugin for my company that does just that.. When they call
upstate:deploy it figures out what kind or artifact it is. The only
ickyness is on deploying a plugin file..
Running ${maven.multiproject.type}:${maven.multiproject.type} for
${pom.name}
Do you have a patch/suggested class to use? It seems like here:
String encoding = null;
// check to see if sun's Base64 encoder is available.
try
{
sun.misc.BASE64Encoder encoder =
(sun.misc.BASE64Encoder) Class.forName(
I was pretty impressed with the NSIS plugin (NSIS in general).. It really
seemed to do the job. It would be great to use the plugin to create the
Maven installer.. It would make a good howto...
Eric
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesda
I think I was the guilty person on this one...
I wanted to run maven eclipse and get my cactus code registered as source
code. If this coupling is undesirable, then the property
maven.eclipse.classpath.include could be used instead:
maven.eclipse.classpath.include src/test-cactus
Eric
> -O
Out of curiosity, can Eclipse take in as the source a .tar.gz file? It
seems like what you want is to have the artifacts generated by 'maven dist'
be uploaded, which are either a .zip or a .tar.gz. However, .tar.gz seems
to come in a quarter the size, and if we are downloading sources, then
havin
0.7.1
http://maven-plugins.sourceforge.net/maven-findbugs-plugin/
plugin
Works great!
Eric Pugh
> -Original Message-
> From: Niclas Hedhman [mailto:[EMAIL PROTECTED]
> Sent: Sunday, April 04, 2004 8:28 AM
> To: Maven Developers List
> Subject: Re: O
I have actually thought about that as well.. Having not been doing much
Maven development in a while, and just starting to get back into it, I
wasn't going to rock the boat. However, I do think that to help increase
exposure etc, this plugin might be better under Hibernate as well.
Eric
>
; Anyone have a reason why I shouldn't tweak the SCM and
> CruiseControl plugins
> > to support Subversion? I am using a custom .jsl file to compile my
> > cruisecontrol configuration file, and the CruiseControl plugin calls the
> > scm:validate method which dies right now.
&
esday, June 08, 2004 5:40 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Adding SVN support to SCM and CruiseControl plugins
>
>
> On Mon, 2004-06-07 at 04:43, Eric Pugh wrote:
> > Thanks..
> >
> > I'll start trying to flesh things out some more.. What kind
> of
+1
Eric
> -Original Message-
> From: Michal Maczka [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 13, 2004 2:22 PM
> To: Maven Developers List
> Subject: Re: [VOTE] release various plugins
>
>
> On Sun, 2004-06-13 at 06:43, Brett Porter wrote:
> > As mentioned, can we formalize the relea
ncies, as well as which components I have use differeing versions of
dependencies.
Eric Pugh
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 13, 2004 9:30 PM
> To: Maven Developers List
> Subject: Re: Why do we need POMs in re
am familiar with, I can help out
on getting issues closed.
Do I need to request it on a plugin by plugin basis, or can I get karma for
them all?
Eric Pugh
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all,
I am looking at MPECLIPSE-5, and while in the bug the reporter refers to
maven.build.src as where generated source goes, and I think that is wrong,
is there a well known location for generated source? Something like
maven.build.src.generated? I am using xdoclet to build some "source" fil
Hi all,
I noticed a patch a while ago to the list from Konstantin Shaposhnikov which
converted the Hibernate plugin to use the SchemaExportTask that is now
available from the main Hibernate jar. I am going to update to using the
Ant task as the existing interface to SchemaExport hasn't kept up wi
rs List'
> Subject: RE: Hibernate plugin use Ant task instead of custom integration
>
>
>
> > -Original Message-
> > From: Eric Pugh [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, June 23, 2004 2:42 PM
> > To: Maven-Dev
> > Subject: Hibernate
nal Message-
> From: Konstantin Shaposhnikov [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 24, 2004 12:23 AM
> To: Maven Developers List
> Subject: Re: Hibernate plugin use Ant task instead of custom integration
>
>
> On 18:15 Wed 23 Jun , Eric Pugh wrote:
> >
; -Original Message-
> From: Konstantin Shaposhnikov [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 25, 2004 10:42 PM
> To: Maven Developers List
> Subject: Re: Hibernate plugin use Ant task instead of custom integration
>
>
> On 12:11 Fri 25 Jun , Eric Pugh wrote:
>
I like the idea.. Would the next logical step be to verify as well that
anything in plugin.properties was listed in the properties.xml file? It
seems that pretty much anything in plugin.properties should be documented.
You could also apply the same logic to goals as well.
Eric
> -Original M
Brett,
I noticed that some of the content that you cleaned was mine.. What steps
did you follow to do this? I try and keep with the existing format on xml
files, but find it hard sometimes..
Eric
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Saturday,
Hi all,
Maybe the answer is RTFM.. :-) However, I am hunting around trying to
setup versions for the MPHIBERNATE project in Jira, and I think I don't have
the juice to do it.. Can someone setup a couple versions?
And, just to reconfirm, since the Hibernate plugin is on 1.2-snapshot, that
means
Could someone create a couple versions for the CruiseControl plugin in JIRA?
Everything is under Unscheduled.
Thanks!
Eric
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1
> -Original Message-
> From: Heritier Arnaud [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 12, 2004 6:46 PM
> To: Maven Developers List
> Subject: RE: [VOTE] Carlos Sanchez as maven-plugins developers
>
>
> +1 from me.
>
> I already voted yesterday but I don't see my mail :-(
>
> #Ar
Hi all,
Can we add maven.gen.src=${maven.build.dest}/generated-sources?
I've been doing a bunch of work with the Hibernate, Xdoclet, and Eclipse
plugins for a client. One of the challenges we had was getting source code
generated via the Xdoclet and Hibernate plugins to play nice w/ a normal
Mav
> Sent: Saturday, July 10, 2004 12:44 PM
> To: Maven Developers List; [EMAIL PROTECTED]
> Subject: Re: JIRA and CruiseControl Plugin
>
>
> Shouldn't the currentVersion for the plugin be 1.4-SNAPSHOT?
>
> On Sat, 10 Jul 2004 12:20:08 +0100, Eric Pugh <[EMAIL PROTECT
: Re: maven.gen.src added to maven?
>
>
> Eric Pugh wrote:
> > Can we add maven.gen.src=${maven.build.dest}/generated-sources?
>
> This sounds alot like what http://jira.codehaus.org/browse/MAVEN-723
> talks about (albeit in a different context).
>
> If what you are
Hi,
I may have made a slight hash of applying MAVEN-1386. The submitter of the
patch was directed at using MAVEN-1_0-BRANCH. I saw the patch as an
improvement, not a bug fix, and attempted to apply it to CVS HEAD.
Can you clarify if I should apply his patch file to MAVEN-1_0-BRANCH since
it h
I'd volunteer to take Hibernate and CruiseControl if the current leads don't
want to keep the role. And, if no one else is chomping at the bit, Eclipse.
All three plugins are near and dear to my heart!
Eric
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Frida
y, except for clashes with the bits already applied.
> >
> > Stuff on the branch will get merged eventually if it does get
> committed there
> > -
> > but I'd appreciate not having to merge a whole bunch of duplicates if
> > possible! :)
> >
> > Th
Hi all,
I have a report that runs that checks a plugin to see if there are newer
versions, and if so, tells the user. I then saw the plugin-profile.xml
stuff in the main maven build, and thought that I could scroll through a
plugin profile to verify that I have all the plugins needed for a specif
; inside the plugin, just like that. Outside, use in conjunction
> with maven:get
>
> Quoting Eric Pugh <[EMAIL PROTECTED]>:
>
> > Hi all,
> >
> > I have a report that runs that checks a plugin to see if there are newer
> > versions, and if so, tells the user. I t
I would be interested in seeing this..
I have two projects that basically take a jar, add a bunch of scripts etc,
and then use the jar plugin to jar it up and then rename to zip. Not sure
if it needs a whole nother plugin though..
Of the top of my head, it feels like something that ought to be a
+1
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 29, 2004 7:30 PM
> To: 'Maven Developers List'
> Subject: RE: [VOTE] PMD Plugin Release
>
>
> +1
>
> > -Original Message-
> > From: Dion Gillard [mailto:[EMAIL PROTECTED]
> > Sent: je
The maven-plugins team is pleased to announce the FindBugs Plug-in 0.8.2
release!
http://maven-plugins.sourceforge.net
A plugin to automate FindBugs tasks
Changes in this version include:
New Features:
o Switch to maven friendly raw report format. Add new "pmd" style report.
o add maven.find
p track
> > > of
> > > goals run and don't run again them. Plugins should be able to override
> > > that,
> > > e.g. clover could set test:test as "not run".
> > >
> > > I don't know if this was thought for next releases and m2, can
Is this still valid? I fixed the error in the CC plugin, but it would be
good to have someone else confirm it!
Eric
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 29, 2004 5:20 PM
> To: [EMAIL PROTECTED]
> Subject: cvs commit: maven-plugin
maven announcement
6) mail list with annoucements.
7) bump version to next -SNAPSHOT
Is that about right?
I'm headed to Eastern Europe for 3 weeks of traveling starting the 15th, so
I'd like to get this taken care of before I go.
Eric Pugh
--
9, 2004 5:23 PM
> To: Maven Developers List; [EMAIL PROTECTED]
> Subject: Re: Time to release Eclipse and Hibernate plugins?
>
>
> On Mon, 9 Aug 2004 17:19:27 +0200, Eric Pugh <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > By my count there are 6 change
w Features:
o Add new properties to the maven cruisecontrol plugin. Issue:
MPCRUISECONTROL-11. Thanks to Alexandre Vivien.
o External link for report should not include artifactId. Issue:
MPCRUISECONTROL-8.
o Add support for projects building when dependent projects are built.
I
The maven-plugins team is pleased to announce the FindBugs Plug-in 0.8.4
release!
http://maven-plugins.sourceforge.net
A plugin to automate FindBugs tasks
Changes in this version include:
New Features:
o Add example Findbugs report to site docs.
Fixed bugs:
o Only include jar dependencie
The maven team is pleased to announce the Maven Eclipse Plugin 1.8 release!
http://maven.apache.org/reference/plugins/eclipse/
A plugin to generate various files for the Eclipse IDE and ease the use of
Maven within that environment.
Changes in this version include:
New Features:
o Add eclips
The maven team is pleased to announce the Maven Hibernate Plug-in 1.2
release!
http://maven.apache.org/reference/plugins/hibernate/
Changes in this version include:
New Features:
o New aggregate-mappings goal to aggregate multiple .hbm files into one
file.
Issue: MPHIBERNATE-6. Thanks to
The maven team is pleased to announce the Maven Cruise Control Plugin 1.5
release!
http://maven.apache.org/reference/plugins/cruisecontrol/
A plugin to handle the generating and maintaining of Cruise Control
configuration. Requires Maven 1.0.
Changes in this version include:
New Features:
o
Thanks.. I actually did look at the directions, but couldn't get the scm
stuff to work because I couldn't get cvs and ssh on my windows box to
cooperate. i am definitly going to look into updating the scm plugin to
work with the all java based stuff that artifact and plugin use.
I was going to
em out if
nothing happens in 6 months? Maybe attempting to have a bug list of 0 is
unrealistic, but it sure looks nice! There are quite a few very stagnant
issues for some of the plugins and make it seem like the plugin isn't
maintained.
Eric Pugh
--
.xml files:
I'm also playing around with just including the Jcoverage report and the
Junit report elements, as the xml generated by JCoverage is all that is
needed for Junit report to do it's thing.
Opinions?
Eric Pugh
is that I'm going
> to change the
> default session behaviour in maven 1.1 so that it only runs once.
> It's an easy
> fix, but it will break stuff.
>
> - Brett
>
> Quoting Eric Pugh <[EMAIL PROTECTED]>:
>
> > Hi all,
> >
> > I've b
Hi all,
I'm getting rid of the dreaded tag library requested not present error in
the maven xdoclet plugin.. I notice that some plugins give me this error,
and others don't.. Not quite sure why..
I thought it was b/c I needed a dependency on maven-1.0-rc2, but that seems
weird. Besides, the s
Re: POM parser in 1.1+1 for me too!
I was under the impression that hopefully these types of problems would be
automatically fixed when bumping the version? Same for changing to the
and structure as well?
Eric
-Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sen
Thanks Brett,
That clears things up a bit.. Unfortunantly, this doesn't seem as easy to
fix as I think it should.. ArtifactListBuilder is responsible for all the
setup
of the artifacts. However, ArtifactListBuilder properly updates the path
variable of the artifact. So, if I change my jelly in
Hi all,
I have been looking at "http://jira.codehaus.org/browse/MPECLIPSE-26 Add a
property to dependencies to link to source". It would be quite easy to add
some sort of property to each dependency specifing the name of a file that
would be in your repository. Something like:
I'll let it slide for a bit..
Eric
> -Original Message-
> From: Jörg Schaible [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 24, 2004 5:10 PM
> To: Maven Developers List; [EMAIL PROTECTED]
> Subject: RE: Adding sourcepath to Eclipse plugin..
>
>
>
ople often
> use it to test, because the jars are there though). It's actually
> usually in basedir.
>
> I suggest you do the following:
> - take lib.path
> - if it starts with ${maven.repo.local}, swap it for MAVEN_REPO
> - if it starts with ${basedir}/, remove it.
>
> So
Thanks! I was just thinking of tackling this one!
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 14, 2004 4:25 PM
> To: [EMAIL PROTECTED]
> Subject: cvs commit: maven-plugins/eclipse/xdocs changes.xml
>
>
> evenisse2004/10/14 08:24
Should this be using this syntax:
instead of the invokeStatic:
Not sure if there was a reason to not use this?
Eric
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 14, 2004 4:25 PM
> To: [EMA
8 AM
> To: Maven Developers List; [EMAIL PROTECTED]
> Subject: Re: cvs commit: maven-plugins/eclipse/xdocs changes.xml
>
>
> oh yes, sorry.
>
> Emmanuel
>
> ----- Original Message -
> From: "Eric Pugh" <[EMAIL PROTECTED]>
> To: "Maven Developer
I'll be honest.. I think JellySWT was someone playing around with Jelly and
see what could be done. I think you need to balance the relative maturity
of JellySWT, and how deeply involved you want to be in using it. At a
minimum, I would suggest that you'll really need to start supply patches for
See my other email (which was queued up in my outbox, ARGH!)
> -Original Message-
> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 19, 2004 3:19 PM
> To: Maven Developers List
> Subject: Re: cvs commit: maven-plugins/eclipse/xdocs changes.xml
>
>
> Why you do thi
we don't start
breaking everybodies builds.
Eric Pugh
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ver, because they both go from src/conf to /, this causes
> two records to
> > >be created in Eclipse. I think, what needs to done is that a
> map of all the
> > >possible sources needs to be made, and then we aggreagate
> together all the
> > &
Hi all,
the jxr plugin is dumping lots of these messages:
PackageManager -> parsing... com\upstate\commons\turbine\om\BaseObject.java
PackageManager -> parsing...
com\upstate\commons\turbine\pulltool\CustomerTool.java
PackageManager -> parsing...
com\upstate\commons\turbine\pulltool\FormatTool.j
t; To: Maven Developers List
> Subject: Re: Controlling Logging Output of Plugins?
>
>
> Any removal of System.out is a Good Thing.
>
> To customise log4j, you must override log4j.properties in maven.jar
> using the standard log4j initialisation technique (eg
> -Dlog4j.prope
Hi all,
A LOT of work has gone into the Eclipse plugin. And I think it is time to
release 1.9 so it can go in Maven 1.0.1. However, I'm looking for a
volunteer who has the right setup to do a release. My darn windows box is
on the blink, and I can't use the release plugin b/c of not having cvs/
ipse 1.9?
>
>
> I was going to ask about this, because I saw a large number of fix items.
>
> I can do it, but does MPECLIPSE-53 need to be fixed first?
>
> - Brett
>
>
> Eric Pugh wrote:
>
> >Hi all,
> >
> >A LOT of work has gone into the Eclips
Okay.. I was refrencing an earlier email from you that specified that we
should add preGoal/postGoals on clean:clean. I guess you meant that on a
project by project basis versus added to a core plugin.
Do you want me to roll this back?
Erc
> -Original Message-
> From: Brett Porter [ma
I'm trying it out today, building some large projects with reactor. At
first glance, seems good.
Eric
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 08, 2004 9:46 AM
> To: Maven Developers List
> Subject: final test release - Maven 1.0.1
>
>
I seem to have run into a glitch with maven 1.0.1. I am using the version
distributed by brett, with no changes or additions.
For the jakarta-turbine-fulcrum project[1], we have a root project.xml and
multiple components. The root project.xml contains two jar dependencies
that are shared by all
using the Ant build would
have checked out the project and have the jar on their local filesystem,
correct?
Eric Pugh
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ride
> > whenever it is set, regardless of where it points (remember that they
> > can be versions though, not necessarily a file!)
> >
> > so add ${maven.jar.foo} to the classpath instead of getting it for
> > dependency foo if jar.override is on and jar.foo is not nume
- what layout should we use by default? should we use the 'single
> project with one goal per testcase' or the 'multi-project with one
> project per testcase'?
I think that a good first place is even just letting people know that it is
possible, and linking to some good examples. Unless you are a
Oh.. You are right of course.. An assumption makes an ass of me. I
assumed that on *nix it would be .sh.
Thank you for the oversight!
Eric
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 16, 2004 7:02 PM
> To: Maven Developers List
> Sub
Corey, have you thought about submitting this to the xdoclet site instead?
If the maven project is really going to have the plugins typically supported
by the individual project, then we should redirect questions to those site's
mailing list. And same for content.
If you would like, send it to th
+1
Dashboard is starting to get interesting with the extra aggregators!
> -Original Message-
> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 26, 2004 5:24 PM
> To: Maven Developers List
> Subject: Re: Releasing dashboard v1.6...
>
>
>
> - Original Messag
I don't know how this affects your question, but my immediate use case for
maven-model is to load up a POM for a project, and then attempt to load up
each dependencies POM. I'd like to be able to generate a report that lets
me know that I am using the latest and greatest versioned artifact of each
Looks better, but I agree that the left nav is too long.. It's almost
overwhelming, I am not sure where to look...
So, some suggestions in no specific order:
1) Getting Maven and Getting Started seem like they should be the same
thing? I can't get started with out getting maven, and if I already
Hi all,
I noticed that http://www.mavenblogs.com/ has some good content, but only
from 5 writers.. I know I've written an entry or two about maven, and I
always like Carlos Sanchez's blog articles about Maven [1].. Is it possible
to contribute specific entries to Maven Blogs? Seems like it need
Here's an icky idea.. See what the exception thrown is when you run the
test on RedHat, and then just ignore it. I know, it sucks.. but it
works...
> -Original Message-
> From: Florin Vancea [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 03, 2004 11:27 AM
> To: Maven Developers Lis
I haven't had a chance to test it either, but I'd like to see it released as
well. I think the fixes are important. I wish I had more changes for
cruisecontrol plugin to release with it, but haven't had a chance to do
it...
ERic
> -Original Message-
> From: Brett Porter [mailto:[EMAIL P
Hi all,
Just getting back into working with Maven after extended vacation. Hope
this is right for maven-dev versus scm-dev. I am trying to pass
defaults into the scm:prepare-release goal for tagging the code. I
notice the jelly code looks like this:
Should the default for the versio
'd be
better to implement it here:
https://svn.apache.org/repos/asf/maven/maven-1/plugins/branches/scm-1.5-
plugin
I think this is similar: http://jira.codehaus.org/browse/MPSCM-39
Would you like to review that patch also?
Thanks,
Brett
Eric Pugh wrote:
>Hi all,
>
>Just getting bac
+1
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 11, 2005 3:02 PM
To: Maven Developers List
Subject: [vote] release maven-site-plugin 1.6
Hi,
I'd like to release site 1.6. Changes are here:
http://maven.apache.org/reference/plugins/site/changes-
Hi all,
I am kicking around adding two new features to the cruisecontrol.jsl
script for the Maven CruiseControl plugin:
Ability to have a recurring and a nightly build.
Right now you can specify to add either a recurring or a time based
build. However, what I would like is two projects. One c
The way we use Maven w/ Cruisecontrol, we regenerate the CC config.xml
file nightly by running "maven multiproject:goal -Dgoal=cruisecontrol"
and this reconfigs all the CC settings. Like nagemailaddress, mail
alias mappings, cvs, etc...
We would like to do the same thing for our Nant based buil
+1 from me
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 13, 2005 11:52 PM
To: Maven Developers List
Subject: [vote] Alex Karasulu as a Maven Plugins committer
Hi,
I'd like to propose Alex Karasulu as a committer on the Maven plugins
and plugin
See the xdoclet plugin's plugin.jelly for some great examples...
-Original Message-
From: Timo Wolf [mailto:[EMAIL PROTECTED]
Sent: Monday, January 24, 2005 12:09 PM
To: dev@maven.apache.org
Subject: Computation of plugin property names
Hi,
I am trying to develop a maven plugin, which
Hi all,
I was wondering if the eclipse:add-maven-repo goal was failing for
anyone else? I am scripting an install of Eclipse 3.0.1, and notice
that the plugin seems to be referring to the wrong path, maybe used in
one of the Eclipse 3.0 Milestone builds:
/.metadata/.plugins/org.eclipse.jdt.core/p
+1 Can't wait for all the new Maven goodness!
On Dec 4, 2005, at 1:10 PM, John Casey wrote:
Hi everyone,
I'd like to do the next release of the Maven core. We've fixed many
important bugs since 2.0, along with expanded plugin support, and a
new bootstrap. In total, we've resolved 125 issu
+1
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 17, 2005 6:13 AM
To: 'Maven Developers List'
Subject: [CruiseControl] Changing the default value for
maven.cruisecontrol.config
Hi,
I'd like to bring 2 changes to the default value of the
mave
I'd be happy to keep up with the latest CC. If you are a user who is
tied to an older version of the tool, then you can also just stick with
the older version of the plugin.
I think the "cost" to us to support multiple versions for many things
really doesn't provide enough "reward". Besides, we
Vincent,
I am glad you are taking a look at the CC plugin, based on your
reputation, feel free to plow ahead ;-)
I have been wrestling with the issue of making the plugin flexible
enough. On one project, I was lucky and was able to use the
configuration right out of the box, however, on another
Hi,
I was just testing commons-email which depends on javamail and
activiation jars, and via a Maven build it work! It downloaded the
javamail and activation jars from ibiblio. However, should those jars
be there? Aren't there redistribution issues with Sun that prevent
them?
If these have bee
at it was forbidden.
> Is there someone who can check who uploaded these files.
>
> Arnaud
>
> > -----Message d'origine-
> > De : Eric Pugh [mailto:[EMAIL PROTECTED]
> > Envoyé : jeudi 3 mars 2005 16:24
> > À : Maven-Dev
> > Objet : Jars on Ibiblio
Vincent,
I think that the change you made fro using the computed ${url} from
maven-scm-plugin isn't quite right, but I thought I would run it by you.
At least for CVS, I find that the ${url} property is only used to define
the cvsroot. Therefore it should be ${url} should equal ${root}, and
not
-1
Plugin tests are failing! I know we don't run them much, but I noticed
that Brett commented out the cruisecontrol plugin:test from being run as
part of the main Maven build, and that feels like a real "mark of
shame".
Would it be possible to hold on till the end of this week? I just fixed
a
My previous email about CC and CVSROOT went out today, I wrote it a
couple days ago, not sure why it didn't send. At any rate, I just
committed my fix, based on someone else finding the same issue, and I'll
work on the failing plugin tests tonight.
Eric
-Original Message-----
Hi all,
I have my project checked out as two branches. I have myproject and
myproject-M4. In both, the artifactId is "myproject", however the
version tags distingush between the two.
However, when I attempt to run multiproject over them, it doesn't pick
up the second "myproject-M4", I assume
+0
I think we need to address somewhere what M2 is. I talk to new people
all the time, and when they hear Maven2, they get nervous.. They
start wondering why learn M1 if M2 is coming down the pike.. And, for
early adopters, they need to know that M2 isn't baked the way M1 is,
and that thing
for you; if you tell me how you want it?
As a part of the Eclipse plugin, my suggestion is that we name the two
available goals:
eclipse:psf-checkout
eclipse:psf-update
Morten
From: "Eric Pugh" <[EMAIL PROTECTED]>
To:
<[EMAIL PROTECTED]>,
Subject: RE: [Maven-plugins-develo
1 - 100 of 185 matches
Mail list logo
