Re: [VOTE] Apache Maven Compiler Plugin 2.4
+1 non binding - from 5 minutes down to 3 for my multimodule build. w00t. On Sun Apr 29 11:06:18 2012, Hervé BOUTEMY wrote: +1 tested on Maven core: compile time reduced from 16 seconds to only 8 great! thank you Hervé Le vendredi 27 avril 2012 23:09:35 Olivier Lamy a écrit : Hi, I'd like to release Apache Maven Compiler Plugin 2.4. We fixed: 13 issues (http://s.apache.org/MCOMPILER-2.4) Staging repository: https://repository.apache.org/content/repositories/maven-008/ Staging site: http://maven.apache.org/plugins/maven-compiler-plugin-2.4 (wait sync). Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, - 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: [VOTE] Apache Maven Compiler Plugin 2.4
Hi, +1 (non binding) from me... tested on several projects no problems. Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Site Plugin version 3.1
Hi, +1 (non binding from me). tested on several projects without any problem.. Kind regards Karl-Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: aggregate modules with asf-svnpubsub-plugin
In the meantime, I just realize asf-svnpubsub-plugin has moved to maven-site-scm-publish-plugin I had a first issue after mvn asf-svnpubsub-plugin:perform -Dsvnpubsub.skipCheckin=true : All have have been removed from SVN because I didn't call mvn site between the clean and the perform. I reinvoked restarted everything (mvn asf-svnpubsub-plugin:clean mvan site mvn asf-svnpubsub-plugin:perform), but the resulting site but lacking the skin (or at least resources of the skin). I finally recommitted everything manually. Thx, Eric On 04/29/2012 05:06 PM, Eric Charles wrote: Hi, I am trying the asf-svnpubsub-plugin 1.0-SNAPSHOT with a multimodule project, and it checkouts the whole pubScmUrl in each submodule, which takes time and is not useful for me (I only need to generate and publish on the top module). Is this the expected behavior? I searched the result of -help but didn't find a configuration for this, instead, I read ...here that an entire directory in svn is dedicated to the publication process for this project. In the aggregate case, this is going to take some doing. Thx, -- eric | http://about.echarles.net | @echarles - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven SCM 1.7
Here my +1 2012/4/26 Olivier Lamy ol...@apache.org: Hi, I'd like to release Apache Maven SCM 1.7. We fixed 18 issues ( http://s.apache.org/SCM-1.7 ) One new feature is the support of Jazz Scm (thanks to Chris Graham !) The staging repository is available here: https://repository.apache.org/content/repositories/maven-112/ The staging site: http://maven.apache.org/scm-1.7/ (the full content is not yet sync). [+1] [0] [-1] Vote open for 72H. Thanks -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT][VOTE] Release Apache Maven SCM 1.7
Hi, The vote has passed with the following result: +1 (binding): Emmanuel Venisse, Robert Scholte, Hervé Boutemy, Mark Struberg, Olivier Lamy. I will continue the release process. Thanks -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Compiler Plugin 2.4
+1 Den 27. apr. 2012 kl. 22:09 skrev Olivier Lamy ol...@apache.org: Hi, I'd like to release Apache Maven Compiler Plugin 2.4. We fixed: 13 issues (http://s.apache.org/MCOMPILER-2.4) Staging repository: https://repository.apache.org/content/repositories/maven-008/ Staging site: http://maven.apache.org/plugins/maven-compiler-plugin-2.4 (wait sync). Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - 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: [VOTE] Release Maven Site Plugin version 3.1
+1 2012/4/27 Dennis Lundberg denn...@apache.org: Hi, We solved 19 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleName=Htmlversion=16489 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11146status=1 Staging repo: https://repository.apache.org/content/repositories/maven-009/ Staging site: http://maven.apache.org/plugins/maven-site-plugin-3.1/ 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 -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Compiler Plugin 2.4
+1 Stéphane On Fri, Apr 27, 2012 at 11:09 PM, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release Apache Maven Compiler Plugin 2.4. We fixed: 13 issues (http://s.apache.org/MCOMPILER-2.4) Staging repository: https://repository.apache.org/content/repositories/maven-008/ Staging site: http://maven.apache.org/plugins/maven-compiler-plugin-2.4 (wait sync). Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Changes Plugin version 2.7
+1 2012/4/27 Benson Margulies bimargul...@gmail.com: Hi, We resolved 9 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=ACIO-CAVI-QX7G-9IAS%7Cb183085c89ca85abde86540c1f02cb433b8719dd%7Cloutversion=17447styleName=TextprojectId=11212Create=Create There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+MCHANGES+AND+status+%3D+Open+ORDER+BY+priority+DESCmode=hide Staging repo: https://repository.apache.org/content/repositories/maven-005/ Staging site: http://maven.apache.org/plugins/maven-changes-plugin-2.7/ There may be a delay while this copies itself. Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 /to save people a click, here's the issue list/ Release Notes - Maven 2.x Changes Plugin - Version 2.7 ** Bug * [MCHANGES-237] - The goal jira-report always results in HTTP 400 error when accessing https://*.jira.com * [MCHANGES-261] - Mail sender specification pointlessly difficult * [MCHANGES-262] - Using custom issue types mapping (MCHANGES-245) throws a llegalArgumentException ** Improvement * [MCHANGES-213] - Update Velocity 1.7 * [MCHANGES-264] - [PATCH] Migration from obsolete plexus-maven-plugin to plexus-containers-component-metadata * [MCHANGES-279] - ability to skip for Jira is offlince ** New Feature * [MCHANGES-76] - Add an option to hava an aggregated Changes Report * [MCHANGES-272] - Please add an option to the 'changes-check' goal to allow skipping release date checks of snapshot versions. * [MCHANGES-275] - versionPrefix configurable by expression 'changes.versionPrefix' - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Invoker Plugin 1.6 (take 2)
Yes, I will. Will not happen until Wednesday though. (Holidays here in Sweden.) Regarding the flag, inheriting setitngs.xml by default from the invoking process if no settings.xml is specified in the flugin config is not implemented? I'm asking based on mine and Stephen's discussion. /Anders On Thu, Apr 26, 2012 at 15:01, Olivier Lamy ol...@apache.org wrote: ok in order to try make all happy :-) I will make that configurable. @Anders I have pushed a snapshot with a new flag called mergeUserSettings. Can you try with your use case ? 2012/4/26 Stephen Connolly stephen.alan.conno...@gmail.com: On 26 April 2012 13:57, Stephen Connolly stephen.alan.conno...@gmail.comwrote: On 26 April 2012 13:40, Anders Hammar and...@hammar.net wrote: I would argue that those are broken projects. You should pretty much always use mrm if you are using invoker for testing a maven plugin. There are cases where you might use invoker for something else, in which case you should not be specifying a custom settings.xml. I might be wrong, but this would be the case for most of the plugins at Apache Maven then. And all mojos at Codehaus Mojo. Correct. Everyone except versions-maven-plugin @ mojo is doing it wrong ;-) Some are using the old hack to refer to the default local repo from the invoking process, but with Maven 3 the assumptions that makes can be invalidated with IDE integrations. So, in short, if you specify a custom settings.xml then no merge by default. Ah, so could the rule be that if no settings.xml is specified use the one of the calling process. If one is specified, do not merge by default? That would be the correct thing to do IMHO Of course in that case you need to ensure that you use the same tricks that m-release-p uses to get the settings from the session as the assumption that settings.xml is even a file on disk is no longer valid in Maven 3 (not that I have seen anyone not store their settings in a settings.xml file, more that Maven 3 Embedder allows for the settings to be provided by a non-file mechanism /Anders That's why I want the calling process' settings-xml to be merged. And I argue that, at least in my use case :-), that would be the default behavior. I have no issue with being able to turn it on via the CLI if you know what you are doing, but where a project has provided a custom settings.xml it must be assumed that the reason for the custom settings.xml is because they want to control the invoker environment completely... if they are not using mrm then they are being foolish as there is no other way to lock down the invoker environment *and* work transparently behind a proxy at the present time. If this is not the default behavior but needs to be configured, it has to be able to turn on from command line as one shouldn't have to update the pom IMO. At least my couple of cents, /Anders On Thu, Apr 26, 2012 at 10:15, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I actually think the merge feature is a step backwards and I am toying with being -1 on the commit. for proxies I think mrm-maven-plugin @ mojo is the way to go. invoker is a different use case from release, so passing through the settings is, in general, a bad thing. If you make the merge an opt-in then that is OK, but personally I cannot see any good use case for it now that we have mrm-maven-plugin to solve the proxy issue On 26 April 2012 09:07, Olivier Lamy ol...@apache.org wrote: Good catch on the warning for activated profiles. They are activated in the maven build so the invoker plugin merge those setting with those eventually defined in the mojo configuration field (settingsFile ). What I can do is made this merge feature optional (off by default and add a debug flag to display it for debugging purpose). WDYT ? 2012/4/25 Karl Heinz Marbaise khmarba...@gmx.de: Hi, just an other question came to my mind What is the purpose of the http://maven.apache.org/plugins/maven-invoker-plugin-1.6/build-job.html This is the format of the file produced by invoker plugin and used by the report mojo. It's given as a link in the docs? But i can't find an explanation which intention it has ? May be i oversight it simply ? Can someone enlighten me? Thanks in advance... Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [RELEASE] sparse release:perform with DSCM and -DlocalCheckout=true
Hi Mark,
what the status of this proposal?
Do you have a JIRA-issue for it?
With the release of scm-1.7 I'd like to prepare a new release of the
m-release-p, so I'm just wondering what we should do here.
-Robert
Op Mon, 13 Feb 2012 22:46:53 +0100 schreef Mark Struberg
strub...@yahoo.de:
Hi maven folks!
I'm currently working on a fix for the ReleaseManager when doing a
release:perform with a sparse checkout using -DlocalCheckout=true.
We are already doing fine for DSCM (GIT, hg, ...) releases if you always
access the upstream repo. But this is not really git-like. 2 years ago I
hacked a quick fix to allow a local checkout with GIT (or other DSCMs)
by using a file file://${project.baseDirectory} URL instead.
The issue with this approach is that it doesn't work if the outermost
directory doesn't have any maven pom. We currently face this problem in
Apache DeltaSpike where we have multiple independent projects on the
outermost level in our GIT repo (site, build-tools, KEYS, etc ) in
addition to the project sources itself.
The outermost level doesn't contain any pom because we do not like to
have all those additional projects in our core source-release.
There are now 2 approaches to solve this issue.
a.) we could store the relative path info in the ReleaseDescriptor.
There is already a field named scmRelativePathProjectDirectory but
this seems to originally have been intended for a different purpose,
right? Is this still in use for that regard? Atm it get's set in the
shared CheckoutProjectFromScm phase. But this is obviously too late for
DSCMs when using localCheckout. Maybe we need a new parameter?
b.) In the CheckoutProjectFromScm phase we currently call
repository =
scmRepositoryConfigurator.getConfiguredRepository( releaseDescriptor,
releaseEnvironment.getSettings() );
provider = scmRepositoryConfigurator.getRepositoryProvider(
repository );
which will most probably cause an Exception if the repo URL doesn't
point to a valid SCM.
In this case we could itterarively cut down the last / part and re-try
to create the repo until we either hit consumed all parts of the SCM
repo URL (- Exception) or we found a valid SCM repo.
any additional ideas?
From my gut feeling a.) is a bit cleaner, but much harder to implement.
b.) is pretty much a hack but should work fine and is easy to implement.
LieGrue,
strub
-
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: [VOTE] Release Maven Site Plugin version 3.1
+1 Robert Op Sun, 29 Apr 2012 21:50:39 +0200 schreef Olivier Lamy ol...@apache.org: +1 2012/4/27 Dennis Lundberg denn...@apache.org: Hi, We solved 19 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleName=Htmlversion=16489 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11146status=1 Staging repo: https://repository.apache.org/content/repositories/maven-009/ Staging site: http://maven.apache.org/plugins/maven-site-plugin-3.1/ 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [RELEASE] sparse release:perform with DSCM and -DlocalCheckout=true
See MRELEASE-740.
It already works on Linux/Mac, but it seems to have a few issues on Win boxes.
I'm atm hanging on an openjpa issue I need in my company and will then fix the
few outstanding issues with MRELEASE-740.
Guess I will find time tomorrow evening.
After that, I'd hope we can get a release out of the door soon.
LieGrue,
strub
- Original Message -
From: Robert Scholte apa...@sourcegrounds.com
To: Maven Dev dev@maven.apache.org; Mark Struberg strub...@yahoo.de
Cc:
Sent: Sunday, April 29, 2012 11:11 PM
Subject: Re: [RELEASE] sparse release:perform with DSCM and
-DlocalCheckout=true
Hi Mark,
what the status of this proposal?
Do you have a JIRA-issue for it?
With the release of scm-1.7 I'd like to prepare a new release of the
m-release-p, so I'm just wondering what we should do here.
-Robert
Op Mon, 13 Feb 2012 22:46:53 +0100 schreef Mark Struberg
strub...@yahoo.de:
Hi maven folks!
I'm currently working on a fix for the ReleaseManager when doing a
release:perform with a sparse checkout using -DlocalCheckout=true.
We are already doing fine for DSCM (GIT, hg, ...) releases if you always
access the upstream repo. But this is not really git-like. 2 years ago I
hacked
a quick fix to allow a local checkout with GIT (or other DSCMs) by using a
file
file://${project.baseDirectory} URL instead.
The issue with this approach is that it doesn't work if the outermost
directory doesn't have any maven pom. We currently face this problem in
Apache DeltaSpike where we have multiple independent projects on the
outermost
level in our GIT repo (site, build-tools, KEYS, etc ) in addition to the
project
sources itself.
The outermost level doesn't contain any pom because we do not like to
have all those additional projects in our core source-release.
There are now 2 approaches to solve this issue.
a.) we could store the relative path info in the ReleaseDescriptor. There
is already a field named scmRelativePathProjectDirectory but this
seems to originally have been intended for a different purpose, right? Is
this
still in use for that regard? Atm it get's set in the shared
CheckoutProjectFromScm phase. But this is obviously too late for DSCMs when
using localCheckout. Maybe we need a new parameter?
b.) In the CheckoutProjectFromScm phase we currently call
repository = scmRepositoryConfigurator.getConfiguredRepository(
releaseDescriptor,
releaseEnvironment.getSettings() );
provider = scmRepositoryConfigurator.getRepositoryProvider(
repository );
which will most probably cause an Exception if the repo URL doesn't
point to a valid SCM.
In this case we could itterarively cut down the last / part and re-try to
create the repo until we either hit consumed all parts of the SCM repo URL
(- Exception) or we found a valid SCM repo.
any additional ideas?
From my gut feeling a.) is a bit cleaner, but much harder to implement. b.)
is pretty much a hack but should work fine and is easy to implement.
LieGrue,
strub
-
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: svn commit: r1331837 - in /maven/plugin-tools/branches/MPLUGIN-189: ./ maven-plugin-tools-annotations/ maven-plugin-tools-annotations/src/ maven-plugin-tools-annotations/src/main/ maven-plugin-too
Is there a specific problem that requires a dedicated ThreadSafe annotation instead of a simple attribute in the Mojo annotation? BTW, Goal annotation instead of Mojo? Regards, Hervé Le samedi 28 avril 2012 21:23:11 ol...@apache.org a écrit : Author: olamy Date: Sat Apr 28 21:23:10 2012 New Revision: 1331837 URL: http://svn.apache.org/viewvc?rev=1331837view=rev Log: [MPLUGIN-189] add java 5 annotations support to mark Mojo sources Added: maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/pom. xml (with props) maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/Component.java (with props) maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/Execute.java (with props) maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/Goal.java (with props) maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/LifecyclePhase.java (with props) maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/Parameter.java (with props) maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/ThreadSafe.java (with props) Modified: maven/plugin-tools/branches/MPLUGIN-189/pom.xml Added: maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/pom. xml URL: http://svn.apache.org/viewvc/maven/plugin-tools/branches/MPLUGIN-189/maven- plugin-tools-annotations/pom.xml?rev=1331837view=auto === === --- maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/pom. xml (added) +++ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/pom. xml Sat Apr 28 21:23:10 2012 @@ -0,0 +1,14 @@ +?xml version=1.0 encoding=UTF-8? +project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; + modelVersion4.0.0/modelVersion + parent +groupIdorg.apache.maven.plugin-tools/groupId +artifactIdmaven-plugin-tools/artifactId +version3.0-SNAPSHOT/version + /parent + + artifactIdmaven-plugin-tools-annotations/artifactId + + nameMaven Plugin Tools Annotations/name + +/project Propchange: maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/pom. xml --- --- svn:eol-style = native Propchange: maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/pom. xml --- --- svn:keywords = Author Date Id Revision Added: maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/Component.java URL: http://svn.apache.org/viewvc/maven/plugin-tools/branches/MPLUGIN-189/maven- plugin-tools-annotations/src/main/java/org/apache/maven/tools/plugin/annotat ions/Component.java?rev=1331837view=auto === === --- maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/Component.java (added) +++ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/Component.java Sat Apr 28 21:23:10 2012 @@ -0,0 +1,40 @@ +package org.apache.maven.tools.plugin.annotations; +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or
Re: svn commit: r1331837 - in /maven/plugin-tools/branches/MPLUGIN-189: ./ maven-plugin-tools-annotations/ maven-plugin-tools-annotations/src/ maven-plugin-tools-annotations/src/main/ maven-plugin-too
2012/4/29 Hervé BOUTEMY herve.bout...@free.fr: Is there a specific problem that requires a dedicated ThreadSafe annotation instead of a simple attribute in the Mojo annotation? Agree all are attribute in mojo annotation so ThreadSafe can be an attribute too. BTW, Goal annotation instead of Mojo? Ah yup the wiki page talked about both, so I was confused. I will change to Mojo. Regards, Hervé Le samedi 28 avril 2012 21:23:11 ol...@apache.org a écrit : Author: olamy Date: Sat Apr 28 21:23:10 2012 New Revision: 1331837 URL: http://svn.apache.org/viewvc?rev=1331837view=rev Log: [MPLUGIN-189] add java 5 annotations support to mark Mojo sources Added: maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/pom. xml (with props) maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/Component.java (with props) maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/Execute.java (with props) maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/Goal.java (with props) maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/LifecyclePhase.java (with props) maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/Parameter.java (with props) maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/ThreadSafe.java (with props) Modified: maven/plugin-tools/branches/MPLUGIN-189/pom.xml Added: maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/pom. xml URL: http://svn.apache.org/viewvc/maven/plugin-tools/branches/MPLUGIN-189/maven- plugin-tools-annotations/pom.xml?rev=1331837view=auto === === --- maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/pom. xml (added) +++ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/pom. xml Sat Apr 28 21:23:10 2012 @@ -0,0 +1,14 @@ +?xml version=1.0 encoding=UTF-8? +project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; + modelVersion4.0.0/modelVersion + parent + groupIdorg.apache.maven.plugin-tools/groupId + artifactIdmaven-plugin-tools/artifactId + version3.0-SNAPSHOT/version + /parent + + artifactIdmaven-plugin-tools-annotations/artifactId + + nameMaven Plugin Tools Annotations/name + +/project Propchange: maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/pom. xml --- --- svn:eol-style = native Propchange: maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/pom. xml --- --- svn:keywords = Author Date Id Revision Added: maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/Component.java URL: http://svn.apache.org/viewvc/maven/plugin-tools/branches/MPLUGIN-189/maven- plugin-tools-annotations/src/main/java/org/apache/maven/tools/plugin/annotat ions/Component.java?rev=1331837view=auto === === --- maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/ main/java/org/apache/maven/tools/plugin/annotations/Component.java (added) +++ maven/plugin-tools/branches/MPLUGIN-189/maven-plugin-tools-annotations/src/
aggregate modules with asf-svnpubsub-plugin
Hi, I am trying the asf-svnpubsub-plugin 1.0-SNAPSHOT with a multimodule project, and it checkouts the whole pubScmUrl in each submodule, which takes time and is not useful for me (I only need to generate and publish on the top module). Is this the expected behavior? I searched the result of -help but didn't find a configuration for this, instead, I read ...here that an entire directory in svn is dedicated to the publication process for this project. In the aggregate case, this is going to take some doing. Thx, -- eric | http://about.echarles.net | @echarles - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: discussion on MNG-4637 : -pl switch negates recursion into sub projects
On Sat, Apr 28, 2012 at 12:12 PM, Hilco Wijbenga hilco.wijbe...@gmail.comwrote: On 27 April 2012 18:20, Chris Graham chrisgw...@gmail.com wrote: On Sat, Apr 28, 2012 at 11:06 AM, Hilco Wijbenga hilco.wijbe...@gmail.comwrote: On 27 April 2012 17:51, Chris Graham chrisgw...@gmail.com wrote: On Sat, Apr 28, 2012 at 7:04 AM, Hilco Wijbenga hilco.wijbe...@gmail.comwrote: Actually, I've been working on a Maven extension that uses checksums to determine whether a particular project needs to be rebuilt (taking all its dependencies into account). We are currently using a Bash script for that purpose. It simply invokes Maven for each project that needs to be (re)built but, obviously, doing this from Maven directly is much easier, faster, and more reliable. Use Hudson/Jenkins for this, that's what I use. This is for local development. The build server isn't in the picture yet. It would not be smart to have the build server skip parts of the build anyway. No, that's not true. If the project build resolution is deterministic, ie it will always result in the same build result. This is good or standard SCM practice. What isn't true? You are not seriously suggesting we now do all local development via the build server, are you? That would be insanely inefficient. Not to mention the total chaos that would ensue. The opposite. If you trust what you're doing locally, it should be used on the CI server. The point is simple: If you don't trust it, don't use it. Local development is *local*, on your local machine, it hasn't reached anything or anyone else yet. I don't think we are talking about the same thing. :-) Or at least, I hope so. ;-) Jenkins fingerprinting (not that I've used that one much) or M2 job type (that I have almost always used) dependency analysis does exactly this. In my experience, Jenkins' dependency analysis only works if nothing (POM wise) has changed. As soon as you add/delete/move dependencies, it gets confused and builds things in the wrong order resulting in failed builds. Given that it doesn't know about all changes at the same time, this is not entirely unexpected, I suppose. But now we're veering off topic. :-) I've never seen this behaviour. However, by definition, a release build, would (and should) result in a full build. -Chris - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: aggregate modules with asf-svnpubsub-plugin
On Sun, Apr 29, 2012 at 11:06 AM, Eric Charles eric.char...@u-mangate.com wrote: Hi, I am trying the asf-svnpubsub-plugin 1.0-SNAPSHOT with a multimodule project, and it checkouts the whole pubScmUrl in each submodule, which takes time and is not useful for me (I only need to generate and publish on the top module). Is this the expected behavior? I searched the result of -help but didn't find a configuration for this, instead, I read ...here that an entire directory in svn is dedicated to the publication process for this project. In the aggregate case, this is going to take some doing. I haven't worked out the multi-module cases entirely. Thx, -- eric | http://about.echarles.net | @echarles - 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: aggregate modules with asf-svnpubsub-plugin
On 04/30/2012 03:05 AM, Benson Margulies wrote: ... Is this the expected behavior? I searched the result of -help but didn't find a configuration for this, instead, I read ...here that an entire directory in svn is dedicated to the publication process for this project. In the aggregate case, this is going to take some doing. I haven't worked out the multi-module cases entirely. Thx for the precision Benson. Eric Thx, -- eric | http://about.echarles.net | @echarles - 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 -- eric | http://about.echarles.net | @echarles - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven SCM 1.7
On Thu, 26 Apr 2012 18:23:13 +0200 Olivier Lamy ol...@apache.org wrote: +1 (non binding) thanks, tony Hi, I'd like to release Apache Maven SCM 1.7. We fixed 18 issues ( http://s.apache.org/SCM-1.7 ) One new feature is the support of Jazz Scm (thanks to Chris Graham !) The staging repository is available here: https://repository.apache.org/content/repositories/maven-112/ The staging site: http://maven.apache.org/scm-1.7/ (the full content is not yet sync). [+1] [0] [-1] Vote open for 72H. Thanks -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
