Re: How to handle aqua laf.jar?

Trying again... somebody has a clue? Wim Deblauwe wrote: > > Hi, > > I'm trying to get jide-oss project in the repository on dev.java.net. The > people of jidesoft have done this, but for Windows users, it does not > work. The jide-oss pom has only 1 depende

How to handle aqua laf.jar?

Hi, I'm trying to get jide-oss project in the repository on dev.java.net. The people of jidesoft have done this, but for Windows users, it does not work. The jide-oss pom has only 1 dependency: aqua aqua 5.0 system ${basedir}/libs/laf.jar Maven complains with

Re: Maven SCM ClearCase plugin issue

Hi Jonathan,the correct place is always the mailing list, so I put them in cc.This is a very good suggestion, but I currently have no time to work on it. Emmanuel or Dan, do you guys want to change this and give him a snapshot version to test it? regards,Wim2006/6/6, Jonathan Gray <[EMAIL PROTECTED

[jira] Commented: (MPMD-12) Use PMD 3.5

[ http://jira.codehaus.org/browse/MPMD-12?page=comments#action_57110 ] Wim Deblauwe commented on MPMD-12: -- http://jira.codehaus.org/browse/MEV-315 > Use PMD 3.5 > --- > > Key: MPMD-12 > URL: http://jira.codehaus.org

[jira] Created: (MEV-315) Upload PMD 3.5 to ibiblio

Upload PMD 3.5 to ibiblio - Key: MEV-315 URL: http://jira.codehaus.org/browse/MEV-315 Project: Maven Evangelism Type: Improvement Reporter: Wim Deblauwe Please add the new PMD version (3.5) to the central repository to this

[jira] Created: (MPMD-12) Use PMD 3.5

Use PMD 3.5 --- Key: MPMD-12 URL: http://jira.codehaus.org/browse/MPMD-12 Project: Maven 2.x Pmd Plugin Type: Improvement Reporter: Wim Deblauwe A new version of PMD has been released: 3.5 -- This message is automatically generated by JIRA. - If you

[jira] Updated: (SCM-108) JDK 1.5 code

[ http://jira.codehaus.org/browse/SCM-108?page=all ] Wim Deblauwe updated SCM-108: - Attachment: clearcase-108.patch > JDK 1.5 code > > > Key: SCM-108 > URL: http://jira.codehaus.org/browse/SCM-108 >

[jira] Created: (MNG-1845) PMD plugin should use latest PMD release

PMD plugin should use latest PMD release Key: MNG-1845 URL: http://jira.codehaus.org/browse/MNG-1845 Project: Maven 2 Type: Improvement Components: maven-pmd-plugin Reporter: Wim Deblauwe Currently, the PMD plugin

[jira] Commented: (SCM-113) Support persistent and transient clientspecs

[ http://jira.codehaus.org/browse/SCM-113?page=comments#action_53415 ] Wim Deblauwe commented on SCM-113: -- For ClearCase, we only support what you call a persistent clientspec. The scm url points to the location of the spec on some server. The

[jira] Commented: (SCM-114) Clientspec naming

[ http://jira.codehaus.org/browse/SCM-114?page=comments#action_53414 ] Wim Deblauwe commented on SCM-114: -- I can answer for Emmanuel, because I have asked the same question for ClearCase. It does not :(. For ClearCase, I implemented it with using the last

Re: Maven-SCM site

Thanks! The link http://maven.apache.org/scm/plugins/scms-overview.html does not seem to work for me?regards,Wim 2005/12/9, Emmanuel Venisse <[EMAIL PROTECTED]>: Added.EmmanuelMike Perham a écrit :> Looks real nice.  Good job, Wim.>> http://maven.apache.org/scm/perforce.htmlAn example of a perforce

[jira] Created: (SCM-96) [patch] Set default edit mode for ClearCase

[patch] Set default edit mode for ClearCase --- Key: SCM-96 URL: http://jira.codehaus.org/browse/SCM-96 Project: Maven SCM Type: Improvement Components: maven-scm-provider-clearcase Reporter: Wim Deblauwe Fix For

Re: ClearCase 'checkout' implementation

That is not true if you create a snapshot view. It can be in any directory. I already implemented and tested this. You can then do a 'cleartool update' and that will update the snapshot view. regards, Wim2005/12/1, dan tran <[EMAIL PROTECTED]>: After checkout, clearcase dictates to location of ch

Re: Documentation

Hi,I'm willing to add some documentation, because I want to get to know how to do it. Where is the source code of the site now?regards,Wim2005/12/1, Emmanuel Venisse < [EMAIL PROTECTED]>:Hi all,Actually maven-scm site is very poor. Are you volunteers to write some docs?We need :- explanations of sc

Re: ClearCase 'checkout' implementation

does not seem to take that into account. Is that a known bug? regards,Wim2005/12/1, Emmanuel Venisse <[EMAIL PROTECTED]>: I talk about file parsing in ${user.home}/.scm/Wim Deblauwe a écrit :>>> 2005/12/1, Emmanuel Venisse <[EMAIL PROTECTED]> [EMAIL PROTECTED]>>:>>

Re: ClearCase 'checkout' implementation

2005/11/30, dan tran <[EMAIL PROTECTED]>: On 11/30/05, Wim Deblauwe < [EMAIL PROTECTED] > wrote: Good suggestions there Dan! It is indeed platform dependant and following the maven 2 way, we should be able to put those things in the settings.xml. Is that possible? That way, it&

Re: PrepareReleaseMojo

ah, ok, thanks!2005/11/30, Emmanuel Venisse <[EMAIL PROTECTED]>: we have only one solution in code, the second.If you have those 2 solutions in your file, it's because you modify it befire you done an update offile and svn merge server content with your modifications. Run a "svn revert" to cancel y

[jira] Created: (MNG-1705) Release plugin loses namespace information from pom.xml

Release plugin loses namespace information from pom.xml --- Key: MNG-1705 URL: http://jira.codehaus.org/browse/MNG-1705 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Wim Deblauwe

Re: Example configuration for SCM Plugin with ClearCase

Hi Thomas, I have done some of the implementation of the ClearCase plugin. Currently, it should work with the release plugin doing release:prepare. You will need to build things from SVN since this code has not been released yet. The goal release:perform has not been implemented yet, because Clear

Re: [jira] Commented: (SCM-80) [patch] update for the release and clearcase plugins

im >  >>  > 2005/11/25, Emmanuel Venisse <[EMAIL PROTECTED]> [EMAIL PROTECTED]> >  > [EMAIL PROTECTED] [EMAIL PROTECTED]>>>:>  >>  > Wim, >  >>  > Can you test it with clearcase?>  >>   

[jira] Commented: (SCM-80) [patch] update for the release and clearcase plugins

[ http://jira.codehaus.org/browse/SCM-80?page=comments#action_51978 ] Wim Deblauwe commented on SCM-80: - Thanks a million Emmanuel! > [patch] update for the release and clearcase plug

[jira] Created: (MNG-1676) finalName not taken into account in install

finalName not taken into account in install --- Key: MNG-1676 URL: http://jira.codehaus.org/browse/MNG-1676 Project: Maven 2 Type: Bug Versions: 2.0 Reporter: Wim Deblauwe Hi, when I set in my pom.xml, the

Re: 'No such provider: perforce'

What problems does ClearCase show? It should work fine on a machine with no clearcase. regards, Wim2005/11/24, Mike Perham <[EMAIL PROTECTED]>: [INFO] [INFO] Reactor Summary:[INFO]

Re: release plugin not providing file name

ve it manually.Do you have test release:perform with clearcase? EmmanuelWim Deblauwe a écrit :> ok, cool.>> What about that release.properties file? Should that be deleted normally> by the release plugin?>> Wim>> 2005/11/23, Emmanuel Venisse < [EMAIL PROTECTED]> [EMAIL PRO

ScmHelper problem

Hi, I'm testing with the updated release plugin and ClearCase, but I still get a problem that pom.xml cannot be edited because it is read-only. I traced the problem to ScmHelper: public void edit( File file )     throws ScmException     {     ScmRepository repository = getScmRepository();

Re: release plugin update for clearcase

gt;> regards,> > Wim>> 2005/11/21, Emmanuel Venisse <[EMAIL PROTECTED]> [EMAIL PROTECTED]>>:> > I done changes.> You'll need to use -DuseEditMode=true with release:prepare>> Emmanuel>> Wim Deblauwe a écrit :>  > Well, we

Re: cvs provider tests failing

Hi, there are 2 tests that fail: junit.framework.AssertionFailedError: The cvs command failed. cvs [log aborted]: Failed to obtain lock on /.directory_history,v: FAIL Lock not within repository     at junit.framework.Assert.fail(Assert.java:47)     at org.apache.maven.scm.provider.cvslib.command

cvs provider tests failing

Hi, the cvs tests fail on my machine. They also run extremely slow. Are these tests trying to do real cvs operations perhaps? regards, Wim

Re: starteam test failing

you can use -Dmaven.test.skip=true, but should set to false for clearcase provider.   -D  On 11/21/05, Wim Deblauwe <[EMAIL PROTECTED] > wrote: Hi,currently, the StarteamChangeLogConsumerTest fails. Anybody willing to clean this up? regards, Wim

Re: Re: release plugin update for clearcase

that?>> regards,>> Wim>> 2005/11/21, Wim Deblauwe < [EMAIL PROTECTED]> [EMAIL PROTECTED]>>:>> Allright, here we go again. I have updated SCM-77 with a new patch.> Hopefully this one will satisfy all your needs :) >> if there are any things I

Re: release plugin update for clearcase

ok, thank you for fixing that. What I noticed is that you have not put the apache header on top of the source files. Shouldn't we do that do be correct? regards, Wim2005/11/21, Emmanuel Venisse <[EMAIL PROTECTED]>: I applied your new patch that contains some tabs and failure in add command test.

[jira] Created: (MNG-1622) Support for ClearCase in maven-scm

Support for ClearCase in maven-scm -- Key: MNG-1622 URL: http://jira.codehaus.org/browse/MNG-1622 Project: Maven 2 Type: Improvement Reporter: Wim Deblauwe Attachments: clearcase.patch Attached is the patch for a starter

Re: no such provider 'clearcase'

, Emmanuel Venisse <[EMAIL PROTECTED]>: Wim Deblauwe a écrit :>>> 2005/11/18, Emmanuel Venisse <[EMAIL PROTECTED]> [EMAIL PROTECTED] >>:>>>> Wim Deblauwe a écrit :>  > So, summarizing:>  >>  > 1) we need a lock/edit command in t

Re: Re: no such provider 'clearcase'

So, summarizing: 1) we need a lock/edit command in the ScmProvider interface, since the release plugin knows that interface. We then have 2 options: define a special property or let the release plugin call lock/edit always and provide an empty implementation in AbstractScmProvider for the non-clea

[jira] Created: (MNG-1619) bug using in a flat layout

bug using in a flat layout - Key: MNG-1619 URL: http://jira.codehaus.org/browse/MNG-1619 Project: Maven 2 Type: Bug Versions: 2.0 Reporter: Wim Deblauwe Attachments: modules.zip I have a problem using and I don&#

Re: [patch] javadoc for ScmProvider interface

use the version defined by the tag +     * @param lastUpdate +     * @return +     * @throws ScmException +     */ UpdateScmResult update( ScmRepository repository, ScmFileSet fileSet, String tag, Date lastUpdate ) throws ScmException;  } 2005/11/18, Wim Deblauwe <[EMAIL PROTECTED]&

[patch] javadoc for ScmProvider interface

Hi, what is the correct procedure to give a patch? I have added some javadoc to the ScmProvider class, but some of the methods still need some javadoc to make it clear what they should do exactly. This should make it easier for others to implement a provider. Anyway this is the patch. I hope that

[jira] Created: (MNG-1576) PMD does not work on dutch locale

PMD does not work on dutch locale - Key: MNG-1576 URL: http://jira.codehaus.org/browse/MNG-1576 Project: Maven 2 Type: Bug Components: maven-pmd-plugin Reporter: Wim Deblauwe I get the following error when running mvn site

[jira] Created: (MNG-1572) Locale problem in Clover plugin

Locale problem in Clover plugin --- Key: MNG-1572 URL: http://jira.codehaus.org/browse/MNG-1572 Project: Maven 2 Type: Bug Components: maven-clover-plugin Versions: 2.0 Reporter: Wim Deblauwe I get the following error

Re: ClearCase implementation

on on tags ( labels ). How is the tag name formed? We> have a naming convention at work here on how labels should be named. >> regards,>> Wim>> 2005/11/12, Wim Deblauwe <[EMAIL PROTECTED]> [EMAIL PROTECTED] >>:>>> ok.> What is th

Re: ClearCase implementation

rds, Wim2005/11/11, Wim Deblauwe <[EMAIL PROTECTED]>: Hey, found the pom.xml, it was right where it should be :) At work, we are using base UCM with dynamic views (not snapshot views). I'm currently at home, so I can't test anything yet. But I will first try to get to know the code. I do

[jira] Created: (CONTINUUM-437) Maven 2 parent project with cannot be build if parent is on same level as modules

Type: Bug Versions: 1.0 Reporter: Wim Deblauwe I'm testing with multiproject like this: root + project + moduleA + moduleB each one has a pom.xml defined. The pom of the project has a section as follows: ../moduleA ../moduleB When I try to add the pom of &qu

[jira] Commented: (MNG-1463) best practices: plugin inheritance for a multi project build

[ http://jira.codehaus.org/browse/MNG-1463?page=comments#action_50349 ] Wim Deblauwe commented on MNG-1463: --- This is the mail of Chris: Greetings, I am looking for guidance on POM inheritance. I know that I can set up a build system where all common

[jira] Created: (MNG-1266) Fatal error trying "mvn site"

Fatal error trying "mvn site" - Key: MNG-1266 URL: http://jira.codehaus.org/browse/MNG-1266 Project: Maven 2 Type: Bug Versions: 2.0 Environment: Windows XP Maven 2.0 Reporter: Wim Deblauwe Priority: Blocker

[jira] Commented: (SCM-26) Maven SCM ClearCase example help

[ http://jira.codehaus.org/browse/SCM-26?page=comments#action_48928 ] Wim Deblauwe commented on SCM-26: - Is it possible to add this information here: http://maven.apache.org/reference/plugins/scm/scmurl.html > Maven SCM ClearCase example h

[jira] Created: (MAVEN-1710) Multiproject failed build not working anymore

Multiproject failed build not working anymore - Key: MAVEN-1710 URL: http://jira.codehaus.org/browse/MAVEN-1710 Project: Maven Type: Bug Versions: 1.1-beta-1, 1.1-beta-2 Reporter: Wim Deblauwe after upgrading to

[jira] Created: (MPIDEA-44) Allow creation of the project and module files in a subdirectory

Environment: Maven 1.1beta2 Reporter: Wim Deblauwe I like to have my idea project and module files in a subdirectory called "ide". My Maven project.xml is in a directory called "build". Like this: + moduleroot + build + project.xml + project.properties + i

[jira] Created: (MPDASHBOARD-32) maven.dashboard.report.showempty property not honoured when using Maven 1.1b1

: Bug Versions: 1.8 Environment: Maven 1.1beta1 Windows XP Reporter: Wim Deblauwe When using the 'maven.dashboard.report.showempty' property, the dashboard overview still shows the empty reports. The problem seems to be with the isEmpty() call. The orginal code is lik

[jira] Created: (MPARTIFACT-59) allow configuring deploying a timedstamped artifact when using SNAPSHOT in the version

-plugin Type: New Feature Versions: 1.6 Environment: Maven 1.1b1 Reporter: Wim Deblauwe I just upgraded to 1.1b1 and version 1.6 of the artifact plugin. I see now that when I do jar:deploy, I get everything double in my repository. I get for example: myjar-1.0-SNAPSHOT.jar myjar-1.0

[jira] Created: (MPJDEPEND-5) java.lang.Exception: size() : null arg" when running with Maven 1.1beta1

nment: Windows XP Maven 1.1beta1 JDepend plugin 1.5 Reporter: Wim Deblauwe I get the following error when using the jdepend plugin with Maven 1.1beta1: --> maven maven-jdepend-plugin:report __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelli

[jira] Created: (MPPMD-19) Java language level not settable through plugin

Java language level not settable through plugin --- Key: MPPMD-19 URL: http://jira.codehaus.org/browse/MPPMD-19 Project: maven-pmd-plugin Type: New Feature Versions: 1.7 Environment: Windows XP Reporter: Wim

[jira] Created: (MPCLOVER-45) Allow specifying the "relative" property for clover-setup

nvironment: Maven 1.0.2 Reporter: Wim Deblauwe When using Clover in a distributed environment, you have several options of instrumenting your class files as presented here: http://www.cenqua.com/clover/doc/adv/distributed.html For option 2 you need to be able to specify the "relative

[jira] Created: (MPIDEA-34) Project.jelly should take "maven.multiproject.type" into account when deciding to link to a web module

/MPIDEA-34 Project: maven-idea-plugin Type: Bug Versions: 1.6 Environment: Maven 1.02 Reporter: Wim Deblauwe When generating iml and ipr files for my project, I got the following problem. The generated ipr file wants to link to a webmodule, although my module is not a webmodule.

[jira] Created: (MPPMD-17) Maven html report shows """ where it should display the " character

ronment: Maven 1.0.2 Reporter: Wim Deblauwe Priority: Minor When you have a violation of the "String literal appearing many times" rule, you get the following error message in the html report: The String literal "tag" appears 4 times in this file; the first occurrence

[jira] Commented: (MPPMD-16) Failure when using annotations in classes.

[ http://jira.codehaus.org/browse/MPPMD-16?page=comments#action_41849 ] Wim Deblauwe commented on MPPMD-16: --- You need to use the latest version of PMD. Full 1.5 support is only introduced in PMD 3.0. The current PMD release is 3.2, so I would recommend

[jira] Commented: (MPPMD-15) Upgrade pmd version to 3.0

[ http://jira.codehaus.org/browse/MPPMD-15?page=comments#action_41848 ] Wim Deblauwe commented on MPPMD-15: --- In the meanwhile, PMD 3.2 has been released. Please update! > Upgrade pmd version to 3.0 > -- > > K

[jira] Created: (MPIDEA-32) Allow ability to specify the compiler resource patterns

Allow ability to specify the compiler resource patterns --- Key: MPIDEA-32 URL: http://jira.codehaus.org/browse/MPIDEA-32 Project: maven-idea-plugin Type: Improvement Environment: Maven 1.0.2 Reporter: Wim

[jira] Commented: (MPIDEA-30) Allow multiproject processing that optionally doesn't link the modules

[ http://jira.codehaus.org/browse/MPIDEA-30?page=comments#action_41782 ] Wim Deblauwe commented on MPIDEA-30: I could use this also. Please apply this patch. > Allow multiproject processing that optionally doesn't link the

[jira] Commented: (MPJDEPEND-3) Allow exclusion of certain class files

[ http://jira.codehaus.org/browse/MPJDEPEND-3?page=comments#action_41779 ] Wim Deblauwe commented on MPJDEPEND-3: -- You can work around it by putting a jdepend.properties file in your home directory with this contents: ignore.clover=com_cenqua_clover

[jira] Created: (MAVEN-1610) failing inheritance for project.properties

failing inheritance for project.properties -- Key: MAVEN-1610 URL: http://jira.codehaus.org/browse/MAVEN-1610 Project: maven Type: Bug Versions: 1.0.2 Environment: Maven 1.0.2 Windows XP Reporter: Wim Deblauwe

[jira] Commented: (MPDASHBOARD-26) JUnit pass rate no longer showing

[ http://jira.codehaus.org/browse/MPDASHBOARD-26?page=comments#action_40235 ] Wim Deblauwe commented on MPDASHBOARD-26: - Move this line: above this line: Otherwise $doc is not yet initialized when you try to access it. > JUnit pass r

[jira] Created: (MPDASHBOARD-26) JUnit pass rate no longer showing

JUnit pass rate no longer showing - Key: MPDASHBOARD-26 URL: http://jira.codehaus.org/browse/MPDASHBOARD-26 Project: maven-dashboard-plugin Type: Bug Versions: 1.9 Environment: Maven 1.0.2 Dashboard 1.9 Reporter: Wim

[jira] Created: (MPDASHBOARD-25) Dashboard total for a percentage should take average

1.9 Reporter: Wim Deblauwe When a column uses % figures (like Clover coverage) the total shows 'N/A'. It would be better if the average of the percentages of all modules is shown. Even better would be if optionally a user could select to make this average depend on the number of lin

[jira] Created: (MPDASHBOARD-24) Multiproject independent navigation

Multiproject independent navigation --- Key: MPDASHBOARD-24 URL: http://jira.codehaus.org/browse/MPDASHBOARD-24 Project: maven-dashboard-plugin Type: Bug Versions: 1.7 Environment: Maven 1.0.2 Windows XP Reporter: Wim

[jira] Commented: (MPPMD-15) Upgrade pmd version to 3.0

[ http://jira.codehaus.org/browse/MPPMD-15?page=comments#action_38860 ] Wim Deblauwe commented on MPPMD-15: --- PMD version 3.1 has been released. I would say, go ahead with the update. > Upgrade pmd version to

[jira] Commented: (MPJAVADOC-34) Javadoc links don't work behind a proxy

[ http://jira.codehaus.org/browse/MPJAVADOC-34?page=comments#action_37811 ] Wim Deblauwe commented on MPJAVADOC-34: --- The javadoc.txt file contains the complete "maven-javadoc-plugin:report". Changes: added 'maven.javadoc.m

[jira] Updated: (MPJAVADOC-34) Javadoc links don't work behind a proxy

[ http://jira.codehaus.org/browse/MPJAVADOC-34?page=all ] Wim Deblauwe updated MPJAVADOC-34: -- Attachment: javadoc.txt This text file contains the complete "maven-javadoc-plugin:report" goal with my changes for bypassing the proxy. I hope s

[jira] Created: (MPIDEA-25) Project and module files should use relative paths true

Project and module files should use relative paths true --- Key: MPIDEA-25 URL: http://jira.codehaus.org/browse/MPIDEA-25 Project: maven-idea-plugin Type: Improvement Environment: Maven 1.0.2 Reporter: Wim

[jira] Commented: (MPCLOVER-34) Specifying the license file should only be done once

[ http://jira.codehaus.org/browse/MPCLOVER-34?page=comments#action_31592 ] Wim Deblauwe commented on MPCLOVER-34: -- ok, go ahead. I probably did something wrong because I re-tested this and now it seems to work fine. I have only been using Maven

[jira] Commented: (MAVEN-1258) Can't run replacetoken ant tag inside maven

[ http://jira.codehaus.org/browse/MAVEN-1258?page=comments#action_31561 ] Wim Deblauwe commented on MAVEN-1258: - Ran into the same problem today with Maven 1.0.2. Luckally, I could use the attributes of the ant task in stead of the nested elements

[jira] Commented: (MPCLOVER-32) clover:off does not reset the compiler to javac

[ http://jira.codehaus.org/browse/MPCLOVER-32?page=comments#action_31485 ] Wim Deblauwe commented on MPCLOVER-32: -- clover:off needs to disable the clover compiler like this: There is however a pitfall to this: Calling 'maven clover:o

[jira] Created: (MPTEST-48) test:match should support specifying an ant pattern style match

plugin 1.6.2 Reporter: Wim Deblauwe When using test:match, you can only match a certain name of a test class, because it is defined like this: I would like for example to match all unit test in a package called 'integration'. If I do: maven -Dtestmatch=**/i

[jira] Commented: (MPPMD-14) PMD should run on unit tests

[ http://jira.codehaus.org/browse/MPPMD-14?page=comments#action_31436 ] Wim Deblauwe commented on MPPMD-14: --- Got the same problem, hopefully this makes it into the next release. Maybe we should have a property called 'maven.pmd.includetestdi

[jira] Created: (MPCLOVER-34) Specifying the license file should only be done once

Specifying the license file should only be done once Key: MPCLOVER-34 URL: http://jira.codehaus.org/browse/MPCLOVER-34 Project: maven-clover-plugin Type: Bug Environment: Maven 1.0.2 Reporter: Wim Deblauwe

[jira] Commented: (MPPMD-15) Upgrade pmd version to 3.0

[ http://jira.codehaus.org/browse/MPPMD-15?page=comments#action_31322 ] Wim Deblauwe commented on MPPMD-15: --- There are some bugs in 3.0, I believe that a 3.1 will follow in a few weeks. Maybe we should wait on that one. Also the ant task will have a

[jira] Created: (MPCLOVER-33) There should be a property to turn off Clover

There should be a property to turn off Clover - Key: MPCLOVER-33 URL: http://jira.codehaus.org/browse/MPCLOVER-33 Project: maven-clover-plugin Type: Improvement Environment: Maven 1.0.2 Reporter: Wim Deblauwe It

[jira] Commented: (SCM-26) Maven SCM ClearCase example help

[ http://jira.codehaus.org/browse/SCM-26?page=comments#action_31232 ] Wim Deblauwe commented on SCM-26: - I could use some more explanation also. Also some extra info on how the change-log plugin should work with ClearCase would be nice > Maven

[jira] Created: (MPIDEA-24) Set language-level to 5.0 when JDK is 1.5.0 (or bigger)

Windows XP (SP1) Reporter: Wim Deblauwe When generating a project file, the language-level is not set according to the JDK version that is used. This requires a small change in the ProjectRootManager (in the project.jelly). I would propose the following mappings: * before 1.4: * after

[jira] Created: (MPJDEPEND-3) Allow exclusion of certain class files

version Reporter: Wim Deblauwe When using Clover with JDepend, I see all clover generated classes also in the JDepend report. I would like to be to exclude those. Preferably, there should be a property like: maven.jdepend.excludes=**/*_CLOVER_*.* Any matching class would be excluded from the

[jira] Commented: (MPJAVADOC-34) Javadoc links don't work behind a proxy

[ http://jira.codehaus.org/browse/MPJAVADOC-34?page=comments#action_30613 ] Wim Deblauwe commented on MPJAVADOC-34: --- Why doesn't the plugin take the values you already need to define to get to the remote repository? I have for instanc