RE: [Fwd: A proposed change to the PMD plugin....]

+1 (a bit late) -Vincent > -Original Message- > From: Tom Copeland [mailto:[EMAIL PROTECTED] > Sent: 16 June 2003 23:09 > To: [EMAIL PROTECTED] > Subject: [Fwd: A proposed change to the PMD plugin] > > Hearing no objections this change is checked in now. > > Thanks, > > Tom >

Results of clean bootstrap at 20030616-2231

Last 200 lines of an clean bootstrap build of maven at 20030616-2231 [exec] [junit] Running org.apache.maven.jelly.tags.maven.DependencyResolverTest [exec] [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.862 sec [exec] [junit] dir attribute ignored if

[jira] Updated: (MAVEN-460) Overhaul of docbook plugin

The following issue has been updated: Updater: dion gillard (mailto:[EMAIL PROTECTED]) Date: Tue, 17 Jun 2003 12:01 AM Comment: dIon's version of the docbook plugin. Issues: 1) Hard codes use of jimi, should be a dependency 2) Doesn't work. Changes: Attachment changed

Re: cvs commit: maven/src/plugins-build/artifact/src/plugin-resources/templatesmanifest.vm

> Generic code for: > >- deployment of artifact to remote repositry > > - installaton of artifact to local repository > This seems like code that is duplicating the repository and deploy plugins. Why do we want a third way of doing this Can you please change the others to use

[jira] Commented: (MAVEN-460) Overhaul of docbook plugin

The following comment has been added to this issue: Author: dion gillard Created: Mon, 16 Jun 2003 9:28 PM Body: I've also 'fixed' the project.xml supplied so that it extends the parent project.xml and removed the entire section ---

[jira] Commented: (MAVEN-489) Checkstyle Error - "Got an exception - java.lang.ClassCastException "

The following comment has been added to this issue: Author: Incze Lajos Created: Mon, 16 Jun 2003 7:19 PM Body: As someone pointed out the ' problem was a false ring, it is a predefined XML entity. Further investigations show, that the real problem is some sort of influence (not o

[jira] Created: (MAVEN-492) Link Check incorrectly reports relative links in Source XRef

Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-492 Here is an overview of the issue: --

[jira] Created: (MAVEN-491) Link Check incorrectly reports redirects as link failures.

Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-491 Here is an overview of the issue: --

Re: [jira] Commented: (MAVEN-489) Checkstyle Error - "Got an exception- java.lang.ClassCastException "

On Mon, Jun 16, 2003 at 07:17:40PM +0200, Incze Lajos wrote: >> Then I changed the order of the jedepend and the checkstyle report. >> >> >> maven-checkstyle-plugin >> maven-jdepend-plugin >> maven-changes-plugin >> maven-changelog-plugin >> maven-developer-activity-plugin

Re: New feature: filtering

I'm not fussy about the syntax but I do not want to bind the filtering to Ant. Why don't we keep @...@ syntax by default, but allow configuration (as does Ant). I think we can reuse the POM definition to configure Ant filtersets for those that want to use it, but if we remove and replace it wit

Re: [jira] Commented: (MAVEN-489) Checkstyle Error - "Got an exception - java.lang.ClassCastException "

On Mon, Jun 16, 2003 at 07:17:40PM +0200, Incze Lajos wrote: > On Mon, Jun 16, 2003 at 05:32:24PM +0200, Vincent Massol wrote: > [...] > > > You are right, I didn't remember that apos is among the default > > entities. > > > But funnily enough the method described worked for me. Now, I've made > >

[Fwd: A proposed change to the PMD plugin....]

Hearing no objections this change is checked in now. Thanks, Tom -Forwarded Message- > From: Tom Copeland <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: A proposed change to the PMD plugin > Date: 16 Jun 2003 15:58:09 -0400 > > I'd like to check in a change to > mav

cvs commit: maven/src/plugins-build/pmd plugin.properties

tcopeland2003/06/16 13:57:23 Modified:src/plugins-build/pmd plugin.properties Log: Modified to run a smaller subset of the PMD rules; this will prevent an avalanche of rule violations that will drown the first-time user Revision ChangesPath 1.3 +1 -1 maven/src

cvs commit: maven/src/plugins-build/jar/src/plugin-resources/templates manifest.vm

michal 2003/06/16 13:41:36 Modified:src/plugins-build/jar plugin.jelly Removed: src/plugins-build/jar/src/plugin-resources/templates manifest.vm Log: Rollback to version 1.9 Revision ChangesPath 1.11 +1 -41 maven/src/plugins-build/j

RE: JBoss plugin - new modifications

> -Original Message- > From: Michal Maczka [mailto:[EMAIL PROTECTED] > Sent: 16 June 2003 21:42 > To: Maven Developers List > Subject: RE: JBoss plugin - new modifications [snip] > > > Question: > > > In this project for jboss all dependecies will be bundled, right? > > > Why to mark th

A proposed change to the PMD plugin....

I'd like to check in a change to maven/src/plugins-build/pmd/plugin.properties - I'd like to reduce the standard set of rulesets to basic.xml, unusedcode.xml, and imports.xml. Here's why - right now the PMD plugin runs every ruleset that PMD has. This includes rulesets that have conflicting

RE: JBoss plugin - new modifications

> -Original Message- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, June 16, 2003 8:54 PM > To: 'Maven Developers List' > Subject: RE: JBoss plugin - new modifications > > > > > > -Original Message- > > From: Michal Maczka [mailto:[EMAIL PROTECTED] > > Sent: 16 J

RE: JBoss plugin - new modifications

> -Original Message- > From: Michal Maczka [mailto:[EMAIL PROTECTED] > Sent: 16 June 2003 19:14 > To: Maven Developers List > Subject: RE: JBoss plugin - new modifications > > > > > -Original Message- > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > Sent: Monday, June 16,

RE: JBoss plugin - new modifications

> -Original Message- > From: Willie Vu [mailto:[EMAIL PROTECTED] > Sent: 16 June 2003 18:55 > To: Maven Developers List > Subject: RE: JBoss plugin - new modifications > > Vincent, > > Here is my 2 cents. > > Maven is designed to have one artifact per project. If a project produces >

RE: [jira] Commented: (MAVEN-489) Checkstyle Error - "Got an exception- java.lang.ClassCastException "

Vincent, >> This error is a know error due to some Antlr version 2.7.1 present in >> the classpath. Checkstyle 3.1 requires Antlr 2.7.2. I think that was one error. When rebuilt Maven after your patch, I then got a different error. (With antlr 2.7.1, it was "Got an exception - java.lang.NoSuchF

Re: [jira] Commented: (MAVEN-489) Checkstyle Error - "Got an exception - java.lang.ClassCastException "

On Mon, Jun 16, 2003 at 05:32:24PM +0200, Vincent Massol wrote: [...] > > You are right, I didn't remember that apos is among the default > entities. > > But funnily enough the method described worked for me. Now, I've made > a > > "maven clean site:deploy" to be sure to work from scratch and see,

RE: JBoss plugin - new modifications

> -Original Message- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, June 16, 2003 6:33 PM > To: 'Maven Developers List' > Subject: JBoss plugin - new modifications > > > Hi, > > I don't like the way the jboss plugin works. ATM, it assumes the EAR and > the jboss packa

RE: JBoss plugin - new modifications

Vincent, Here is my 2 cents. Maven is designed to have one artifact per project. If a project produces more than one artifact, imagine what will happen when 2 artifacts from the same project are referenced as dependencies. foo ejb SNAPSHOT foo ear SNAPSHOT

JBoss plugin - new modifications

Hi, I don't like the way the jboss plugin works. ATM, it assumes the EAR and the jboss packaging is done in the same project. I think they are 2 separate activities that should be done in 2 separate projects. Why? Because packaging something in JBoss can mean packaging several modules: An EAR mod

Failure to Download SNAPSHOTs and issue MAVEN-412

Issue MAVEN-412 was opened to cover problems with SNAPSHOT download failures apparently caused by locking of JAR files in Windows. Corrective changes were made to HttpUtils and the issue was closed. Subsequently, the changes were removed (rolled back to B8 level) from HttpUtils. I'm wondering if

RE: [jira] Commented: (MAVEN-489) Checkstyle Error - "Got an exception - java.lang.ClassCastException "

> -Original Message- > From: Incze Lajos [mailto:[EMAIL PROTECTED] > Sent: 16 June 2003 17:23 > To: Maven Developers List > Subject: Re: [jira] Commented: (MAVEN-489) Checkstyle Error - "Got an > exception - java.lang.ClassCastException " > > On Mon, Jun 16, 2003 at 12:32:46PM +0100, Bri

Re: [jira] Commented: (MAVEN-489) Checkstyle Error - "Got an exception - java.lang.ClassCastException "

On Mon, Jun 16, 2003 at 12:32:46PM +0100, Brian Ewins wrote: > This diagnosis doesn't seem right. > > > And this is the bad news: ' is good for html but bad for > > XML. So, the result file is not well formed. And yes, now > > I tested that this was the real problem, you can do it, too: > > Th

cvs commit: maven/src/plugins-build/war plugin.jelly

michal 2003/06/16 07:40:25 Modified:src/plugins-build/war plugin.jelly Log: Added deploy, install goals Revision ChangesPath 1.17 +129 -57 maven/src/plugins-build/war/plugin.jelly Index: plugin.jelly =

cvs commit: maven/src/plugins-build/artifact/src/plugin-resources/templates manifest.vm

michal 2003/06/16 07:26:02 Added: src/plugins-build/artifact project.properties plugin.properties .cvsignore project.xml plugin.jelly src/plugins-build/artifact/src/main/org/apache/maven/artifact/deployer

cvs commit: maven/src/plugins-build/artifact/src/main/org/apache/maven/artifact/deployer - New directory

michal 2003/06/16 07:25:48 maven/src/plugins-build/artifact/src/main/org/apache/maven/artifact/deployer - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven/src/plugins-build/artifact/src/plugin-resources/templates - New directory

michal 2003/06/16 07:25:48 maven/src/plugins-build/artifact/src/plugin-resources/templates - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven/src/plugins-build/artifact/src/main/org/apache/maven/artifact - New directory

michal 2003/06/16 07:25:48 maven/src/plugins-build/artifact/src/main/org/apache/maven/artifact - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven/src/plugins-build/artifact/src/main - New directory

michal 2003/06/16 07:25:47 maven/src/plugins-build/artifact/src/main - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven/src/plugins-build/artifact/src/main/org/apache/maven/artifact/deployer/deploy - New directory

michal 2003/06/16 07:25:48 maven/src/plugins-build/artifact/src/main/org/apache/maven/artifact/deployer/deploy - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven/src/plugins-build/artifact/src/plugin-resources - New directory

michal 2003/06/16 07:25:48 maven/src/plugins-build/artifact/src/plugin-resources - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven/src/plugins-build/artifact/src/main/org - New directory

michal 2003/06/16 07:25:47 maven/src/plugins-build/artifact/src/main/org - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven/src/plugins-build/artifact/src/main/org/apache/maven - New directory

michal 2003/06/16 07:25:47 maven/src/plugins-build/artifact/src/main/org/apache/maven - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven/src/plugins-build/artifact/src - New directory

michal 2003/06/16 07:25:47 maven/src/plugins-build/artifact/src - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven/src/plugins-build/artifact/src/main/org/apache - New directory

michal 2003/06/16 07:25:47 maven/src/plugins-build/artifact/src/main/org/apache - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven/src/plugins-build/artifact - New directory

michal 2003/06/16 07:25:47 maven/src/plugins-build/artifact - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: New feature: filtering

On Mon, 2003-06-16 at 09:48, Vincent Massol wrote: > > > > I don't have the full picture of what you're doing though... > > > > I'm trying to trace down the memory leak and sequentially going > through > > a list of suspect points of leakage. > > That's cool :-) Yes, well I'm trying but so far

RE: New feature: filtering

> -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...

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 > get the release out the door (on this subject). I don't see how > rewriting our filtering support and in addition writing some additional > java code can help improve the

RE: New feature: filtering

> -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

Re: Maven.log - bootstrap build

>> On Fri, Jun 13, 2003 at 07:05:37PM +0100, [EMAIL PROTECTED] wrote: >> > >> > Has anyone had a look lately at their maven.log when bootstrap building >> > maven? >> > >> > I dont know whether its something particular to my machine - but the log >> > file has literally thousands of null

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 > script file of course. Why would you want to reinvent the wheel? Because everytime I take this line of thought I end up spending monumental amounts of time because I run into

Re: [jira] Commented: (MAVEN-489) Checkstyle Error - "Got an exception- java.lang.ClassCastException "

This diagnosis doesn't seem right. > And this is the bad news: ' is good for html but bad for > XML. So, the result file is not well formed. And yes, now > I tested that this was the real problem, you can do it, too: This isn't correct. see "All XM

RE: SOLVED : Strange behavior of war plugin #*@!

--- Vincent Massol <[EMAIL PROTECTED]> wrote: > Applied. Can you please verify it works? > perfectly. thanks. regards, = [ Konstantin Pribluda ( ko5tik ) ] Zu Verstärkung meines Teams suche ich ab Sofort einen Softwareentwickler[In] für die Festanstellung. Arbeitsort

[jira] Closed: (MAVEN-474) war plugin doesn't support lists of includes/excludes

Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-474 Here is an overview of the issue: --

RE: SOLVED : Strange behavior of war plugin #*@!

There's already a patch in jira for this: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-474 Regards, Tim > -Original Message- > From: Konstantin Priblouda [mailto:[EMAIL PROTECTED] > Sent: Monday, 16 June 2003 7:46 PM > To: Maven Developers List > Subject: SOLVED : Strange be

RE: SOLVED : Strange behavior of war plugin #*@!

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 proble

cvs commit: maven/src/plugins-build/war plugin.jelly

vmassol 2003/06/16 03:06:47 Modified:src/plugins-build/war plugin.jelly Log: Fixed includes and excludes for classes files so that a comma-separated list works. Thanks to Konstantin Priblouda. Revision ChangesPath 1.16 +6 -8 maven/src/plugins-build/war/plugin.j

SOLVED : Strange behavior of war plugin #*@!

Well, I fould where problem was. I said in my project.properties: --%<-- maven.war.classes.includes=**/*.properties , **/*.class ---%<- and this just lead to omission of everything from this directory. I see from plugin.jelly that this results in: ---%<--

RE: Strange behavior of war plugin

> > What's wrong with Ant's war task? You cannot override/extend it. Only way of making any extra processing e.g including some resources generated by other goal (e.g. by XDoclet) anyway requires two phases of processing. Say that we will realize the scenario with more complex dependencies, whic

RE: Strange behavior of war plugin

> -Original Message- > From: Michal Maczka [mailto:[EMAIL PROTECTED] > Sent: 16 June 2003 10:31 > To: 'Maven Developers List' > Subject: RE: Strange behavior of war plugin > > My teammate has also strange problems with war plugin. > For him just java files are included in war. > > FYI:

RE: New feature: filtering

> -Original Message- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: 16 June 2003 10:35 > To: Maven Developers List > Subject: Re: New feature: filtering > > On Mon, 2003-06-16 at 03:20, Brett Porter wrote: > > > oh, ok. I thought you wanted to put the filter in the POM... If it'

Re: New feature: filtering

On Mon, 2003-06-16 at 03:20, Brett Porter wrote: > > oh, ok. I thought you wanted to put the filter in the POM... If it's > > just the filtersets, then, yes I agree. However, I'm not sure I like the > > format: > > > > > > > > my.filters > > ${basedir}/../filters > > > > **/

RE: Strange behavior of war plugin

My teammate has also strange problems with war plugin. For him just java files are included in war. FYI: I am working on generic java code for installing and deploying artifacts and generating manifest file. I am almost done with that I am rewriting also WAR plugin to use this code. I plan to

Strange behavior of war plugin

Hi all, I'm experiencing strange behaviour of war plugin. It just stopped to include classes into war. I' just using war:war, and here is maven -X output ---%< [war] [DEBUG] ZipFileSet: Setup scanner in dir /home/konstantin/.maven/repository/odmg/jars with patternSet{ includes:

cvs commit: maven/src/test/touchstone-build maven.xml

jvanzyl 2003/06/16 01:04:20 Modified:src/test/touchstone-build maven.xml Log: o I have moved these tests into the unit tests proper. Revision ChangesPath 1.36 +0 -21 maven/src/test/touchstone-build/maven.xml Index: maven.xml ===

Re: New feature: filtering

Although I don't quite agree, I've applied it for now. The part that I don't like is that copying will be done all the time when there are filters, even if the file or the filter value have not changed... This has always been an issue with ant filtering. The only option you have is to set up some

RE: New feature: filtering

> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: 16 June 2003 09:21 > To: Maven Developers List > Subject: Re: New feature: filtering > > > oh, ok. I thought you wanted to put the filter in the POM... If it's > > just the filtersets, then, yes I agree. However,

cvs commit: maven/src/conf driver.jelly

vmassol 2003/06/16 00:50:38 Modified:src/conf driver.jelly Log: Always perform the copy when filtering is used. This is to ensure that the filtered file is always up to date with the filter definition. Revision ChangesPath 1.15 +2 -1 maven/src/conf/driver.jelly

Re: New feature: filtering

oh, ok. I thought you wanted to put the filter in the POM... If it's just the filtersets, then, yes I agree. However, I'm not sure I like the format: my.filters ${basedir}/../filters **/*.properties my.filters base.filters ... [...]

cvs commit: maven/src/plugins-build/examples/simple-filtering/src/conf test-nofilter.properties

vmassol 2003/06/16 00:17:30 Modified:src/plugins-build/examples/simple-filtering/src/conf test-nofilter.properties Log: Added a filter in the properties file that is not filtered, to verify that it is indeed not filtered... :-) Revision ChangesPath

RE: New feature: filtering

> -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? >

cvs commit: maven/src/conf driver.jelly

vmassol 2003/06/16 00:03:41 Modified:src/conf driver.jelly Log: oops... typo Revision ChangesPath 1.14 +1 -1 maven/src/conf/driver.jelly Index: driver.jelly === RCS file: /home/cvs/maven/sr

RE: New feature: filtering

> -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