Hi,
It seems doing a maven -g nows lists *all* goals, even those that do
not have a description. Thus my question is: how do you make a goal
private (i.e. not visible by the end user)?
For example, typing maven -g get the following for the cactus plugin:
[cactus] ( NO DEFAULT GOAL )
compile
Hi,
I'd like to move the PMD plugin in the Maven CVS. Anyone against that?
If ok, I'll do it today.
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I will be 2000% for it.
What do you think?
Thanks
-Vincent
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 03 April 2003 18:46
To: Maven Developers List
Subject: Re: New PMD plugin?
On Thu, 2003-04-03 at 03:07, Vincent Massol wrote:
Hi,
I'd like
Hi,
Following Siegried's acceptance to move the PMD plugin from SourceForge
to the Maven CVS and following Maven committer's acceptation, I have
performed the move. I have started updating the plugin's POM.
ATM, the plugin is probably not working yet (I haven't tried it). I'll
try to make it
Hi dIon,
I have asked Siegfried who has told me he was +1 for the move (actually,
we had already discussed moving the plugin to Maven some 3-4 months ago
and my recall was that the PMD team was agreeable to that).
That said, when doing the move yesterday I have noticed that there is
another
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 04 June 2003 22:46
To: Maven Developers List
Subject: Re: Committers let's agree on how we make changes to a plugin
On Wed, 2003-06-04 at 08:49, Vincent Massol wrote:
Hi,
What do you think about
://www.mockobjects.com/wiki/FrontPage?action=formatmimetype=text/xm
l
(you might need to do a view source with IE).
-Vincent
Trygve
Vincent Massol wrote:
Hi,
Here are some facts:
- Our Maven web site contains lots of inaccuracies and would not
suffer
from additional documentation
- Some Maven users
As I'm preparing the new version of the Maven checkstyle plugin (that
will use checkstyle 3.1), I'm releasing version 1.1 of our checkstyle
plugin.
It's now done and tagged as MAVEN_CHECKSTYLE_1_1 in CVS.
I'll be committing checkstyle 2.0 later today.
Thanks
-Vincent
Fixed for Cactus and Checkstyle.
Thanks
-Vincent
-Original Message-
From: Florin Vancea [mailto:[EMAIL PROTECTED]
Sent: 05 June 2003 07:24
To: Maven Developers List
Subject: Re: cvs commit: maven/src/plugins-build/checkstyle
plugin.jelly
P.S.: I did a quick search for 'include
://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
-Original Message-
From: Ben Walding [mailto:[EMAIL PROTECTED]
Sent: 11 June 2003 23:47
To: Maven Developers List
Subject: Re: Does Jira email this group?
JIRA sends email to all maven committers from JIRA. I believe the
mailing list is configured to reject email from
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 12 June 2003 14:55
To: Maven Developers List
Subject: Re: Releasing Maven and plugin release
On Thu, 2003-06-12 at 07:55, Vincent Massol wrote:
Hi,
Is it possible to know one week in advance please when
Hi,
I've added a changes.xml file in maven/xdocs for all user-visible change
in the maven core.
Could you please use it if you make any user-visible change in the core?
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL
[...]
/resource
I'm curious to see what other think.
Thanks
-Vincent
- Brett
Vincent Massol wrote:
Hi,
I've just committed a new feature in CVS: filtering of runtime
resources
and test resources. I've also committed a sample project that shows
how
to use it, in src/plugins-build
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 16 June 2003 07:21
To: Maven Developers List
Subject: Re: New feature: filtering
Why is that? I never use the overwrite attribute and all my
filtering
work fine...
change a filter, but don't touch the
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 16 June 2003 08:07
To: Maven Developers List
Subject: Re: New feature: filtering
BTW, do you have any idea why the sample-filtering project in
plugin-builds/examples does not work WRT filtering?
You've
Applied. Can you please verify it works?
Thanks
-Vincent
-Original Message-
From: Konstantin Priblouda [mailto:[EMAIL PROTECTED]
Sent: 16 June 2003 11:46
To: Maven Developers List
Subject: SOLVED : Strange behavior of war plugin [EMAIL PROTECTED]
Well, I fould where problem was.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 16 June 2003 15:24
To: Maven Developers List
Subject: RE: New feature: filtering
On Mon, 2003-06-16 at 04:44, Vincent Massol wrote:
And you can re-use any of these without having to go through an XML
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 16 June 2003 15:47
To: Maven Developers List
Subject: RE: New feature: filtering
On Mon, 2003-06-16 at 09:39, Vincent Massol wrote:
Filtering is working right now for runtime and test resources... We
can
-Original Message-
From: Michal Maczka [mailto:[EMAIL PROTECTED]
Sent: 18 June 2003 10:01
To: 'Maven Developers List'
Subject: RE: Recent changes in war plugin
Yes.
I am still working on deployer.
That's the art which I want to use in this plugin to add missing
functionality.
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: 18 June 2003 17:45
To: 'Maven Developers List'
Subject: New WAR changes problems
Hi,
I have 2 problems with the new changes brought to the war plugin WRT
artifact deployment:
1/ When I run maven, I get
Hi,
The EJB plugin ejb:install goal installs its artifacts in
groupId/ejbs/artifactId-version.jar (note the jar extension).
However, the maven dependency resolver looks for a file named:
groupId/ejbs/artifactId-version.ejb (not the ejb extension)
Thus it fails to find the artifact...
Several
-Original Message-
From: Michal Maczka [mailto:[EMAIL PROTECTED]
Sent: 18 June 2003 19:53
To: Maven Developers List
Subject: RE: Problems of EJB plugin and Dependencies download
This is partially fixed in maven-new (Repository Layout Service)
So you can assign different layouts
-Original Message-
From: Michal Maczka [mailto:[EMAIL PROTECTED]
Sent: 18 June 2003 19:44
To: Maven Developers List
Subject: RE: New WAR changes problems
[snip]
there is no way to rename the war... One solution (not nice) would
to
perform a copy prior to calling
-Original Message-
From: Michal Maczka [mailto:[EMAIL PROTECTED]
Sent: 18 June 2003 12:44
To: 'Maven Developers List'
Subject: RE: Recent changes in war plugin
What's so magical in ant war task?
It's written, fully supports the war model and has gone through lots
-Original Message-
From: Michal Maczka [mailto:[EMAIL PROTECTED]
Sent: 18 June 2003 21:13
To: Maven Developers List
Subject: RE: Recent changes in war plugin
This already exists in Ant: it's called manifest
(http://ant.apache.org/manual/CoreTasks/manifest.html). And you can
-Original Message-
From: Michal Maczka [mailto:[EMAIL PROTECTED]
Sent: 18 June 2003 21:09
To: Maven Developers List
Subject: RE: New WAR changes problems
[snip]
artifact:install
artifact=foo
type=war
project=${pom}
-Vincent
-Original Message-
From: Michal Maczka [mailto:[EMAIL PROTECTED]
Sent: 18 June 2003 21:40
To: Maven Developers List
Subject: RE: Recent changes in war plugin
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 18, 2003 8:46
Michal,
I have committed a quick patch for EJB dependency handling so that
extensions for the EJB type artifacts is .jar and not .ejb.
I hope I haven't broken anything. I have tested it successfully on my
current project.
Thanks
-Vincent
-Original Message-
From: Michal Maczka
-Original Message-
From: Michal Maczka [mailto:[EMAIL PROTECTED]
Sent: 18 June 2003 22:01
To: Maven Developers List
Subject: RE: Recent changes in war plugin
[snip]
I think we're talking about the same thing. You can have a jelly
taglib
that wraps the Ant manifest task.
Hi Michal,
I've had a look at the source code for the new artifact plugin... and it
is really proof-of-concept code at this stage and I'm totally sure there
are lots of bugs (it is really far from production quality right now). I
don't mind that but I do mind using it in our WAR plugin at this
Hi,
Why is the java source directory named main for plugins (instead of
java)?
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
deploy and deploy-snapshot install-
snapshot
goals before
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 19, 2003 12:33 PM
To: 'Maven Developers List'
Subject: new Artifact plugin and WAR plugin war:install goal
Hi Michal
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 19 June 2003 15:02
To: Maven Developers List
Subject: Re: Why is the java source directory named main for
plugins?
On Thu, 2003-06-19 at 06:32, Vincent Massol wrote:
Hi,
Why is the java source directory
Hi,
I have just updated the jboss plugin to support bundling start/stop
script in the generated zip. The idea is that the generated zip is a
self-contained and executable jboss configuration.
I have also tried to make it work both on JBoss 3.0.x and JBoss 3.2.x.
However I haven't changed the JMX
Hi Trygve,
I have applied your patch but haven't tested it. I hope it works! :-)
Can you please verify it?
Thanks
-Vincent
-Original Message-
From: Cocell | Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: 22 June 2003 19:59
To: [EMAIL PROTECTED]
Subject: [patch] Generated
-Original Message-
From: James CE Johnson [mailto:[EMAIL PROTECTED]
Sent: 20 June 2003 02:51
To: Maven Developers List
Subject: Re: JBoss plugin - new modifications
[snip]
Perhaps there should be a maven.jboss.version property and a j:if tag
would check that in order to invoke
Tld bundling is supported right now by the war plugin. You can even put
them wherever you want provided it's under the webapp/ source directory.
I'm not sure adding a tld property helps a lot. I personally think it
makes this simple plugin more complex. Person who want more flexibility
(i.e.
Hi Aslak,
I love the idea of CPD/Simian. However, before we can commit anything
here we would need agreement from redhillconsulting.com that we can put
the simian jar in the Maven remote repository on ibiblio.
If we dont get this agreement, we could still store this plugin in the
SF
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 25 June 2003 02:32
To: Maven Developers List
Subject: Re: Responsibility - was [RE: Simian Plugin (fully documented
and
ready to use)\
[snip]
C - core - needed to perform basic tasks
M - actively
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 25 June 2003 03:02
To: Maven Developers List
Subject: Re: cvs commit: maven/src/test/java/org/apache/maven/project
ProjectInheritanceTest.java
I believe this is now fixed, and if someone can tell me how
Hi,
We are trying to Mavenize the cactus build and Cactus has the following
directory structure for the framework subproject:
framework
|_ src
|_ java
|_ j2ee12 (j2ee 1.2 specific source code)
|_ j2ee13 (j2ee 1.3 specific source code)
|- share (source code common to j2ee
+1 from me. However, I'd really like that email sending be turned on so
that I can subscribe to page changes.
BTW, I proposed the following some time ago and maybe someone can tell
me if it is possible/difficult to do:
- modify MoinMoin so that the generated XML matches our Maven xdoc
format
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 30 June 2003 17:39
To: Maven Developers List
Subject: RE: Proposal: Migrate wiki to codehaus
On Mon, 2003-06-30 at 11:36, Vincent Massol wrote:
+1 from me. However, I'd really like that email sending
Hi Michal,
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 01 July 2003 10:44
To: [EMAIL PROTECTED]
Subject: cvs commit: maven/src/plugins-build/war/xdocs changes.xml
[snip]
Index: changes.xml
of UseMod and html
tagging
in the documents, but will do so when time permits. Or someone else
can
do it :)
Phase 2 of the Project Mayhem can now commence.
Cheers,
Ben
Vincent Massol wrote:
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 30 June
Very cool Michal. I have a need for that. We did the same for our
project at work.
Thanks
-Vincent
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 03 July 2003 22:42
To: [EMAIL PROTECTED]
Subject: cvs commit: maven/src/plugins-build/multiproject
I think I'm -1 for making this change now. As you say there are just too
many who are using it the other way.
I'm +0 if you want to introduce a war plugin property such as:
maven.war.dependency.behavior=exclude|include
so that the current behavior is the default.
-Vincent
-Original
Hi,
Is it possible to activate the email notification in the user preference
page (as in http://www.mockobjects.com/wiki/UserPreferences, see
subscribed wiki pages)?
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
First the column says TZ offset. Then, I just computed it so that it
shows the correct time. See http://maven.apache.org/team-list.html
-Vincent
-Original Message-
From: Martin Skopp [mailto:[EMAIL PROTECTED]
Sent: 10 July 2003 10:06
To: Maven Developers
Subject: Re: cvs commit:
Hi Eric,
Can you add a comment mentioning that the code you have added needs to
be refactored so that there is no duplication. If you run Simian or
CPD on the plugin it will currently scream... :-)
Of course, if you could the refactoring... ;-)
An idea: use a jelly tag.
Thanks
-Vincent
(or the
artifact plugin). The nice thing is that it allows you seamlessly
declare XML attributes and have them passed to your jelly scriplet
inside your tag.
-Vincent
ERic
-Original Message-
From: Vincent Massol
To: 'Maven Developers List'
Sent: 7/10/03 8:35 AM
Subject: RE: cvs
Eric,
I'm not sure if you can break a task in small parts (never done that).
However, I don't understand why you need to break the cactus tag in
several parts rather than have a single jelly tag wrapping it. I don't
see a use case for that in the current features supports by the Cactus
plugin.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 11 August 2003 07:26
To: Maven Developers List
Subject: RE: cvs commit: maven/src/plugins-build/cactus/xdocs
changes.xml
Vincent Massol [EMAIL PROTECTED] wrote on 11/08/2003 02:57:48
PM:
Yeah
Yeah... The reasons are:
- I don't understand why we're doing it the reverse way, i.e. HEAD
should be the main branch and JASON_REFACTORING should the unstable
branch containing Jason's refactorings
- My environment is setup for HEAD right now and I haven't bothered
changing it
- Users will
dIon,
When you make updates like this one, do you test the plugin to see if it
still works? In this case, you would need to test the plugin on a
project which uses the Cactus/HttpUnit integration.
My point is that I don't believe this is right for you to make this
modification as I don't think
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 18 August 2003 09:14
To: Maven Developers List
Subject: RE: cvs commit: maven/src/plugins-build/cactus project.xml
Vincent Massol [EMAIL PROTECTED] wrote on 18/08/2003 05:03:43
PM:
dIon,
When you
Oh no please... I'm +1 to re-establish HEAD as the main development
branch.
Thanks
-Vincent
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 18 August 2003 09:23
To: 'Maven Developers List'
Subject: RE: branch merge strategy WAS: some cvs commit thread :)
So
Hi,
We have lots of very nice code quality reports: checkstyle, pmd, simian,
findbugs, activity, jdepend, clover, etc. However, having these reports
is not enough to make the problems go away.
One idea that may help is to provide a global dashboard for all projects
(as part of the multiproject
Thanks Tom. Very nice. It's a nice feature set for the future report
part of Multiproject/Continuum!
-Vincent
-Original Message-
From: Tom Copeland [mailto:[EMAIL PROTECTED]
Sent: 30 August 2003 19:00
To: 'Maven Developers List'
Subject: RE: [idea] Multiproject Dashboard
Anyway,
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 01 September 2003 05:43
To: 'Maven Developers List'
Subject: RE: plugin version upgrading/downgrading
[snip]
As I have mentioned before, we need to get a bit clearer about which
goals can have been touched
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 01 September 2003 07:36
To: 'Maven Developers List'
Subject: RE: plugin version upgrading/downgrading
What about making the goal public when it has a description
element defined? I had reported a bug (dunno
Hi dIon,
I've looked at the new strategy for rendering several websites for the
plugins (by storing the different versions in CVS). I think it can be
improved... :-)
Here are my ideas:
- I don't think it's normal to store history data in CVS. A SCM is meant
to do that for you. I won't
/a
* @author a href=mailto:[EMAIL PROTECTED]Vincent Massol/a
@@ -158,7 +160,7 @@
*/
public void setGroupId( String groupId )
{
-this.groupId = groupId;
+this.groupId = StringTool.trim(groupId);
}
/**
@@ -204,7 +206,7
Hi,
Brett mentioned in a an earlier email today that the idea of RC1 would
be a maven core containing core plugins and other plugins which would
not be part of the main maven distribution.
What I don't understand is the concept of code plugins. For me a
plugin is a plugin and they should all be
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 11 September 2003 15:01
To: Maven Developers List
Subject: Re: Core plugins?
On Thu, 2003-09-11 at 03:44, Vincent Massol wrote:
Hi,
Brett mentioned in a an earlier email today that the idea of RC1
would
Developers List
Subject: RE: Core plugins?
On Thu, 2003-09-11 at 09:19, Vincent Massol wrote:
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 11 September 2003 15:01
To: Maven Developers List
Subject: Re: Core plugins?
On Thu, 2003-09-11 at 03:44
versions...
-Vincent
-Original Message-
From: Norbert Pabi [mailto:[EMAIL PROTECTED]
Sent: 11 September 2003 17:06
To: Maven Developers List
Subject: Re: Core plugins?
Vincent Massol wrote:
What we seem to need is a way to prevent folks having to enter 20 plugin
dependencies
an
easy
plugin installation mechanism... However, uninstall is a bit of a
nuisance
as it needs to go from several places. That's another fix that needs
to be
made.
Cool :-)
Thanks for the hard work!
-Vincent
Cheers,
Brett
-Original Message-
From: Vincent Massol [mailto:[EMAIL
-Original Message-
From: Rafal Krzewski [mailto:[EMAIL PROTECTED]
Sent: 12 September 2003 14:29
To: Maven Developers List
Subject: Re: Core plugins?
Vincent Massol wrote:
I'd like to understand (I guess I should read the build script
code).
Could you please describe in more
Hi Florin,
Sorry about not answering this one. What happens is that I am not into
JMX at the moment and I would need to get involved in that to digest
your post. I really believe this is where we should go in Cactus, i.e.
JMX-ify all deployments, so this is certainly something we'll revisit in
Sorry. I meant to send this to the Cactus mailing list.
-Vincent
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: 13 September 2003 17:22
To: 'Maven Developers List'
Cc: [EMAIL PROTECTED]
Subject: RE: Controlling automated develop-time deployments to JBoss
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 15 September 2003 07:43
To: [EMAIL PROTECTED]
Subject: Next release?
Are we all in agreement that the next release should happen pretty
soon,
and be called 1.0-beta-11?
I'm +0 on that name vs 1.0-RC1,
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 15 September 2003 14:24
To: Maven Developers List
Subject: RE: Next release?
On Mon, 2003-09-15 at 04:21, Michal Maczka wrote:
-1 on calling it beta-11
+1 on calling it RC1
All right looks like
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 18 September 2003 10:05
To: Maven Developers List
Subject: Re: Several web site versions in CVS
Bringing this up again, as it needs to be resolved.
Vincent Massol [EMAIL PROTECTED] wrote on 04/09/2003
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 18 September 2003 11:20
To: Maven Developers List
Subject: RE: Several web site versions in CVS
Vincent Massol [EMAIL PROTECTED] wrote on 18/09/2003 06:21:35
PM:
You don't get me. I'm not saying we
Hi guys,
The statcvs team has done a wonderful job of outputting statcvs reports
in XML (this was a request I had opened some time ago so that we could
further integrate statcvs reports with the Maven look and feel and
they've implemented it!).
The result is available at:
-Original Message-
From: Luke Taylor [mailto:[EMAIL PROTECTED]
Sent: 19 September 2003 21:06
To: Maven Developers List
Subject: Re: StatCvs 2.0-SNAPSHOT is ready for trial...
Vincent Massol wrote:
for the repository and the projects I would like to run against
dIon,
Is it normal we have
src/test/plugin-test/src/main/org/...
in the checkstyle plugin?
Shouldn't it be:
src/test/main/org/...
?
Thanks
-Vincent
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Hi,
I'd like to change the way the aspectj plugin works. Here's what I'd
like to implement:
- make it a pre-goal of jar:jar
- verify if there are aspects present in the source tree
- if there are, weave the aspects on the *bytecode* (classes compiled by
the java plugin)
- the generated jar of
, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Vincent Massol [EMAIL PROTECTED] wrote on 20/09/2003 01:00:55
AM:
Hi,
Could some of you test the new statcvs plugin I have just committed
and
tell me if it works. I'd like to release it over the next 2 days so
-Original Message-
From: Michal Maczka [mailto:[EMAIL PROTECTED]
Sent: 21 September 2003 13:42
To: Maven Developers List
Subject: RE: [aspectj] Changing behavior of aspectj plugin, is it ok?
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent
. Perhaps
it
is what you meant by verify if there are aspects present in the
source
tree.
just my 2 cents..
-- gd
Michal Maczka wrote:
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 21, 2003 11:51 AM
To: 'Maven Developers List
it really hard to download as a plugin :-)
I meant is the plugin SNAPSHOT in ibiblio? If it is, RC1-SNAPSHOT
users
can just plugin:download it.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Vincent Massol [EMAIL PROTECTED] wrote on 21/09/2003 08:38
PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 21 September 2003 15:32
To: Maven Developers List
Subject: Re: recent move of tests in checkstyle plugin...
Vincent Massol [EMAIL PROTECTED] wrote on 20/09/2003 11:31:26
PM:
dIon,
Is it normal we have
src/test/plugin-test/src/main/org
Yes, it means I am the originator of it (i.e the idea and the first
implementation). The current version has exactly the same idea as on day
one. It is simply more elaborate. In any case, being the original
creator is something that stays whatever the product becomes
afterwards...
Cactus is no
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 21 September 2003 16:30
To: Maven Developers List
Subject: Re: [aspectj] Changing behavior of aspectj plugin, is it ok?
[snip]
Would that be ok?
I would take a glance at the issue raised by one of the
/people/dion/
Vincent Massol [EMAIL PROTECTED] wrote on 22/09/2003 12:31:12
AM:
I don't think so. What I'm doing is helping anyone else using
Eclipse.
Hence the reason I'm checking it in.
Is there any issue with having files in .cvsignore that I am not
aware
of?
Thanks
-Vincent
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 21 September 2003 16:55
To: Maven Developers List
Subject: RE: recent move of tests in checkstyle plugin...
Vincent Massol [EMAIL PROTECTED] wrote on 22/09/2003 12:31:12
AM:
Hmmm... It is not compiling
-Original Message-
From: Gilles Dodinet [mailto:[EMAIL PROTECTED]
Sent: 21 September 2003 16:55
To: Maven Developers List
Subject: Re: [aspectj] Changing behavior of aspectj plugin, is it ok?
Vincent,
Although it actually works fine when putting standard classes
containing
Hi,
Just to tell you that I am currently working on a revised aspectj plugin
which uses AspectJ 1.1 and performs binary weaving. I'm planning to
implement almost everything Wes has identified in:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-473
dIon,
I'd like to have some feedback on the new aspectj plugin I've committed
yesterday before we release rc1 (yeah, I know, it was very close to the
release...). At least one or 2 persons saying it works for them. That
shouldn't take more than a day.
Hey guys, come on, just give it a whirl! :-)
-Original Message-
From: Rafal Krzewski [mailto:[EMAIL PROTECTED]
Sent: 22 September 2003 07:28
To: Maven Developers List
Subject: Re: cvs commit: maven/src/plugins-build/aspectj .cvsignore
[EMAIL PROTECTED] wrote:
I can just see the IDEA, JBuilder and JDeveloper files
Hi,
While waiting for the future component-based Maven implementation...
What would you think about an interface plugin that would be used by
plugins when calling goals from other plugins. The interface plugin
would have properties to wire calls to Well-Known Goals (WKG) to the
implementation.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 29 September 2003 05:40
To: Maven Developers List
Subject: Re: RC1 announcement contents
On Sun, 2003-09-28 at 21:54, [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote on 29/09/2003 11:39:22 AM:
Do you
dIon,
I did this on purpose so that we don't have to change it every time.
Also the text does not say that we are pointing to the latest version
but to the release archive... I think it is best to point to the
archives instead of a specific version.
-Vincent
-Original Message-
From:
Hi (dIon),
The html2xdoc plugin generates target files in
src/test/plugin-test/target. I think a better solution is to tell the
spawned maven to generate them in the main target/ directory (by
changing the maven.build.dir value maybe). What do you think?
The other solution is to cvs ignore
Hi,
I'm trying to update my local copy of the maven-plugins CVS module but
it fails with a lock problem:
cvs server: failed to create lock directory for
`/home/cvs/maven-plugins/ashkelon'
(/home/cvs/maven-plugins/ashkelon/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in
-Original Message-
From: Nathan Coast [mailto:[EMAIL PROTECTED]
Sent: 02 October 2003 03:34
To: maven dev
Subject: plugin naming
just wondering,
the convention for plugin naming is
maven-[myplugin]-plugin
is the 'maven' bit supposed to indicate that it's a maven plugin
Hi Jason,
I'm fine with moving the following: Cactus, checkstyle, jboss, pmd,
statcvs and actually all the other remaining plugins... I still don't
understand why we need to keep any plugin at all in maven core. They can
be downloaded for bootstrapping (in the same way as all the other jars
are).
1 - 100 of 1391 matches
Mail list logo
