Re: Need translation help into French for PMD Plugin
and I am ready for Italian of course, if needed! all the best, TIA! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Wed, Jan 11, 2012 at 11:39 PM, Dennis Lundberg wrote: > Thanks to both of you! > > On 2012-01-11 22:36, Robert Scholte wrote: >> I'll add a dutch translation for both reports too. >> By the way, it looks like some cpd-report properties have an incorrect >> value for report.cpd.cpdlink >> It refers to PMD instead of CPD, or am I missing something? >> >> -Robert >> >> On Wed, 11 Jan 2012 22:26:36 +0100, Olivier Lamy wrote: >> >>> Hello, >>> I think I can :-) >>> >>> 2012/1/11 Dennis Lundberg : Hi I'm preparing a release of maven-pmd-plugin, and when going through the code I found out that the French localization is only done for the PMD report, but not for the CPD report. It would be great if someone could add maven-pmd-plugin/src/main/resources/cpd-report_fr.properties and translate the 9 properties into French for the CPD report. -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > > > -- > Dennis Lundberg > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: JDK 5 needed for Performing a Maven Project Release?
On Wed, Jan 11, 2012 at 10:08 PM, Barrie Treloar wrote: > http://maven.apache.org/developers/release/maven-project-release-procedure.html > says "you have JDK 5 installed and on your shell's path." > > I was about to try out the new laptop, which is a Macbook Air, and the > is the first time I've used a Mac. > It comes with JDK 6. > > Are we happy that compiler options will correctly build JDK 5 classes? > (Things like > http://docs.oracle.com/javase/6/docs/api/java/lang/String.html#isEmpty%28%29 > break binary backwards compatibility.) I don't know of any reliable way to install 5 on a recent mac, and I've released about 10 things on my mac in the last year using 1.6. I'm perfectly happy the JVM version options -- it's the library functions that could get us. That (as Brett points out) is where the animal sniffer comes in -- or building with 1.7, which has stronger options for library compat than 1.5. > > Or do I need to work out how to install JDK 5? > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Intention to release Maven EAR Plugin 2.7
I'm doing a quick sweep over plexus-io/archiver aiming for a .1 bump on both; you might consider doing a joint release EAR/maven-archiver release to get these included. I'll be watching general issues/patches on plexus specifically until you say it's time to press release ;) (Btw; I have a commit coming up for PLXCOMP-192, thanks to your excellent analysis) Kristian 2012/1/9 Stephen Connolly > On 9 January 2012 17:07, Robert Scholte wrote: > > To use Maven 2.2.1 you need at least jdk5, not the other way around > (i.e. to > > use jdk5 you need at least maven 2.2.1). > > Using Maven 2.0.9 with jdk5 works just as fine. > > Let me put this another way, if a plugin is using Java 1.5 code, then > in my view, it should specify Maven 2.2.1 as a minimum prereq as that > is the first version of Maven to require Java 1.5... > > I don't see any point in genericification of the plugin source code > unless we are using 2.2.1 as the pre-req. > > > > > And there are still a lot of companies which use Maven 2, because it > works: > > there's no need to spend time or money to upgrade to Maven 3. > > > > IMHO this should be fixed for Maven 2 as well, but I agree that the patch > > needs some finetuning. > > > > -Robert > > > > > > On Mon, 09 Jan 2012 09:50:08 +0100, Stephen Connolly > > wrote: > > > >> Well IMHO, the patch is perhaps somewhat misguided. > >> > >> in m3, there will be resolution from the reactor as priority, so this > >> patch should only be required in m2... and in order to keep consistent > >> behaviour, the patch should not be switchable and the reactor search > >> should have priority. Other than that, the patch might not be a bad > >> thing... > >> > >> on the other hand, since we have moved to java 1.5, I presume we are > >> switching to maven 2.2.1 at least as a minimum... we could just bump > >> it to 3.0 and the issue would be "gone" > >> > >> -Stephen > >> > >> On 8 January 2012 20:52, Robert Scholte > wrote: > >>> > >>> Hi, > >>> > >>> I've been cleaning up the pom a bit. > >>> It looks like we can't upgrade the value for mavenFilterVersion due to > >>> regression, so we have to stay at 1.0-beta-2 > >>> Somehow the escaping character is ignored. > >>> And the sources now use generics. > >>> > >>> The title of MEAR-107 is kind of misleading, it's actually asking for > >>> reactorProjects support. > >>> It has a patch, no IT and 3 votes. > >>> Maybe worth adding? > >>> > >>> -Robert > >>> > >>> [1] http://jira.codehaus.org/browse/MEAR-107 > >>> > >>> > >>> On Sun, 08 Jan 2012 16:51:34 +0100, Jason van Zyl > wrote: > >>> > > On Jan 8, 2012, at 6:10 AM, Dennis Lundberg wrote: > > > Hi, > > > > After working on two rather large issues for the EAR plugin I'm going > > to > > release a new version shortly. If there are any more issues that you > > want to work on and want included in this release please let me know. > > > > There are currently two unresolved issues scheduled for the 2.7 > > release. > > Unless someone is willing to work on them, I'm going to push them to > a > > later release. > > > > Sounds reasonable. > > Thanks for the heads up. > > > > > > > > http://jira.codehaus.org/browse/MEAR#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel > > > > -- > > Dennis Lundberg > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > To do two things at once is to do neither. > -—Publilius Syrus, Roman slave, first century B.C. > > > > >>> > >>> - > >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >>> For additional commands, e-mail: dev-h...@maven.apache.org > >>> > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [PROPOSAL] Reporting plugins should require Maven 2.2.1
Hi Can it work? I haven't had much experience with shading, but I was under the impression that it is a way to hide classes from Maven's class loader. What we really want in this case is a way to *insert* newer versions of classes into Maven's class loader. Don't know if that can be done... On 2012-01-12 00:12, Robert Scholte wrote: > What about plugins containing both build and report goals? > If the suggested shading of Doxia will work, I'd prefer that option. > > -Robert > > On Wed, 11 Jan 2012 23:53:57 +0100, Barrie Treloar > wrote: > >> On Thu, Jan 12, 2012 at 9:15 AM, Stephen Connolly >> wrote: >>> +1 >> >> +1 >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Intention to release Maven EAR Plugin 2.7
Hi Kristian Thanks for looking at those components. It'll be great to finally fix that WAR Plugin bug. I'll go ahead and release the EAR plugin as is, without an updated maven-archiver. I'd like for this version to be as similar as possible to the previous version, except for the new features. It makes chasing down bugs easier. On 2012-01-12 13:23, Kristian Rosenvold wrote: > I'm doing a quick sweep over plexus-io/archiver aiming for a .1 bump on > both; you might consider > doing a joint release EAR/maven-archiver release to get these included. > > I'll be watching general issues/patches on plexus specifically until you > say it's time to press release ;) > > (Btw; I have a commit coming up for PLXCOMP-192, thanks to your excellent > analysis) > > > Kristian > > > > 2012/1/9 Stephen Connolly > >> On 9 January 2012 17:07, Robert Scholte wrote: >>> To use Maven 2.2.1 you need at least jdk5, not the other way around >> (i.e. to >>> use jdk5 you need at least maven 2.2.1). >>> Using Maven 2.0.9 with jdk5 works just as fine. >> >> Let me put this another way, if a plugin is using Java 1.5 code, then >> in my view, it should specify Maven 2.2.1 as a minimum prereq as that >> is the first version of Maven to require Java 1.5... >> >> I don't see any point in genericification of the plugin source code >> unless we are using 2.2.1 as the pre-req. >> >>> >>> And there are still a lot of companies which use Maven 2, because it >> works: >>> there's no need to spend time or money to upgrade to Maven 3. >>> >>> IMHO this should be fixed for Maven 2 as well, but I agree that the patch >>> needs some finetuning. >>> >>> -Robert >>> >>> >>> On Mon, 09 Jan 2012 09:50:08 +0100, Stephen Connolly >>> wrote: >>> Well IMHO, the patch is perhaps somewhat misguided. in m3, there will be resolution from the reactor as priority, so this patch should only be required in m2... and in order to keep consistent behaviour, the patch should not be switchable and the reactor search should have priority. Other than that, the patch might not be a bad thing... on the other hand, since we have moved to java 1.5, I presume we are switching to maven 2.2.1 at least as a minimum... we could just bump it to 3.0 and the issue would be "gone" -Stephen On 8 January 2012 20:52, Robert Scholte >> wrote: > > Hi, > > I've been cleaning up the pom a bit. > It looks like we can't upgrade the value for mavenFilterVersion due to > regression, so we have to stay at 1.0-beta-2 > Somehow the escaping character is ignored. > And the sources now use generics. > > The title of MEAR-107 is kind of misleading, it's actually asking for > reactorProjects support. > It has a patch, no IT and 3 votes. > Maybe worth adding? > > -Robert > > [1] http://jira.codehaus.org/browse/MEAR-107 > > > On Sun, 08 Jan 2012 16:51:34 +0100, Jason van Zyl >> wrote: > >> >> On Jan 8, 2012, at 6:10 AM, Dennis Lundberg wrote: >> >>> Hi, >>> >>> After working on two rather large issues for the EAR plugin I'm going >>> to >>> release a new version shortly. If there are any more issues that you >>> want to work on and want included in this release please let me know. >>> >>> There are currently two unresolved issues scheduled for the 2.7 >>> release. >>> Unless someone is willing to work on them, I'm going to push them to >> a >>> later release. >>> >> >> Sounds reasonable. >> >> Thanks for the heads up. >> >>> >>> >>> >> http://jira.codehaus.org/browse/MEAR#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel >>> >>> -- >>> Dennis Lundberg >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >> >> Thanks, >> >> Jason >> >> -- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> - >> >> To do two things at once is to do neither. >> -—Publilius Syrus, Roman slave, first century B.C. >> >> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apac
SCM Website Suggestion
Hi, I wanted to pass along a suggestion to make the SCM website a bit better but wasn't sure who to contact. So I'm sending to this list. Hopefully that's okay. On the bootstrapping example page (http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html) there's a "Configuring Authentication" section. It seems to me that this section would be better placed on the usage page (http://maven.apache.org/scm/maven-scm-plugin/usage.html) as it looks to be more general configuration and not specific to bootstrapping. Thanks!
[VOTE] Release Maven EAR Plugin version 2.7
Hi, We solved 4 issues, including [MEAR-60] Improve support for skinny war files which has 50 votes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132&styleName=Html&version=17293 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11132&status=1 Staging repo: https://repository.apache.org/content/repositories/maven-060/ Staging site: http://maven.apache.org/plugins/maven-ear-plugin-2.7/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Eclipse Plugin version 2.9
Hi, We solved 25 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11133&version=16240 There are still a large backlog of issues left in JIRA: (extra support would be appreciated) http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+MECLIPSE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-061/ Staging site: (not yet synced) http://maven.apache.org/plugins/maven-eclipse-plugin-2.9/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[jira] Subscription: Design & Best Practices
Issue Subscription
Filter: Design & Best Practices (24 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
https://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
https://jira.codehaus.org/browse/MNG-612
MNG-1563how to write integration tests
https://jira.codehaus.org/browse/MNG-1563
MNG-474 performance improvement for forked lifecycles
https://jira.codehaus.org/browse/MNG-474
MNG-4656Declarative plugins similar to "jsp tags" or "jsf composites"
https://jira.codehaus.org/browse/MNG-4656
MNG-139 server definitions should be reusable - review use of repository IDs
https://jira.codehaus.org/browse/MNG-139
MNG-1381best practices: testing strategies
https://jira.codehaus.org/browse/MNG-1381
MNG-1950Ability to introduce new lifecycles phases
https://jira.codehaus.org/browse/MNG-1950
MNG-2125[doc] when and how to define plugins in a pom
https://jira.codehaus.org/browse/MNG-2125
MNG-2381improved control over the repositories in the POM
https://jira.codehaus.org/browse/MNG-2381
MNG-4713${basedir} variable makes portable builds overly difficult
https://jira.codehaus.org/browse/MNG-4713
MNG-367 best practices: multi-user installation
https://jira.codehaus.org/browse/MNG-367
MNG-41 best practices: site management
https://jira.codehaus.org/browse/MNG-41
MNG-868 Use uniform format for and other tags
https://jira.codehaus.org/browse/MNG-868
MNG-1425best practices: the location of configuration files vs resources
https://jira.codehaus.org/browse/MNG-1425
MNG-1463best practices: plugin inheritance for a multi project build
https://jira.codehaus.org/browse/MNG-1463
MNG-125 guarded mojo execution
https://jira.codehaus.org/browse/MNG-125
MNG-416 best practices: multiple profile deployments
https://jira.codehaus.org/browse/MNG-416
MNG-657 possible chicken and egg problem with extensions
https://jira.codehaus.org/browse/MNG-657
MNG-1423best practices: setting up multi-module build
https://jira.codehaus.org/browse/MNG-1423
MNG-1441Starting thinking about a proper distributed repository mechanism a
la CPAN
https://jira.codehaus.org/browse/MNG-1441
MNG-1468best practices: version management in multi project builds
https://jira.codehaus.org/browse/MNG-1468
MNG-1569Make build process info read-only to mojos, and provide mechanism
for explicit out-params for mojos to declare
https://jira.codehaus.org/browse/MNG-1569
MNG-1867deprecate system scope, analyse other use cases
https://jira.codehaus.org/browse/MNG-1867
You may edit this subscription at:
https://jira.codehaus.org/secure/FilterSubscription!default.jspa?subId=10341&filterId=11471
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: SCM Website Suggestion
The best way to report bugs and enhancement requests is to file a jira ticket [1]. Providing a patch (or at least detailed text change suggestions like in this case) will increase the likelihood of getting it fixed. /Anders [1] http://jira.codehaus.org/browse/SCM On Thu, Jan 12, 2012 at 18:40, sdoca sdoca wrote: > Hi, > > I wanted to > pass along a suggestion to make the SCM website a bit better but wasn't > sure who to contact. So I'm sending to this list. Hopefully that's > okay. > > On the bootstrapping example page > (http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html) > there's a "Configuring Authentication" section. It seems to me that this > section would be better placed on the usage page > (http://maven.apache.org/scm/maven-scm-plugin/usage.html) as it looks to be > more general configuration and not specific to bootstrapping. > > Thanks! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
