Am 2014-02-03 22:59, schrieb Hervé BOUTEMY:
I just updated some plugins
now, we have:
$ mvn versions:display-plugin-updates
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building The Apache Software Foundation 14-SN
The Apache Maven team is pleased to announce the release of the Apache Maven
SCM Publish Plugin, version 1.0
The maven-scm-publish-plugin is a utility plugin to allow publishing Maven
website to any supported SCM. The primary goal was to have an utility plugin
to allow Apache projects to publis
OK, I'm getting the dependencies to resolve and I can amend the classpath,
but I think I've hit a road block for multi module builds.
LifeCycleParticipant is only ever called once at the root. This means that
if I have a project with 2 modules where ModuleB depends on ModuleA then
I'm not going to
Igor,
I've worked out how to modify the project classpath (pretty trivial). But
I'm struggling to get the project dependencies resolved during
LifeCycleParticipant#afterProjectsRead.
I tried using the TychoDependencyResolver to #setupProject and
#resolveProject but that isn't causing the projects
The only plugin I know that does this is my jszip plugin... It's messy... I
intend refactoring it to something easier to reuse
On Monday, 3 February 2014, Dessie K wrote:
> In my Mojo how can I programmatically reload poms in my multi-module
> project in Maven 3?
>
> I need to do this after my M
Hi,
The vote has passed with the following result:
+1 (binding): Robert Scholte, Stephen Connolly,
Mark Struberg, Olivier Lamy, Hervé Boutemy
I will promote the artifacts to the central repo.
In my Mojo how can I programmatically reload poms in my multi-module
project in Maven 3?
I need to do this after my Mojo switches to a different Git branch
Hi again,
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-install-plugin/src/main/java/org/apache/maven/plugin/install/InstallMojo.java
/**
* @deprecated either use project.getFile() or
reactorProjects.get(i).getFile()
*/
@Parameter( defaultValue = "${project.file}",
I just updated some plugins
now, we have:
$ mvn versions:display-plugin-updates
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building The Apac
here is my +1
Regards,
Hervé
Le vendredi 31 janvier 2014 23:28:51 Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12730&styleName=H
> tml&version=18940
>
> There are still 1 issue left in JIRA:
> http://jira.codehaus.org/secure
hi,
Hi Robert,
The install:install goal[1] doesn't have the the pomFile parameter,
however the install:install-file[2] does.
I am aware of that.
So I'm not sure which goal you are actually using.
I am using the install goal. And it honors the pomFile parameter in
version 2.3.1 just as I wro
+1
--
Olivier
On Feb 1, 2014 9:29 AM, "Hervé BOUTEMY" wrote:
> Hi,
>
> We solved 6 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12730&styleName=Html&version=18940
>
> There are still 1 issue left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=tru
+1
LieGrue,
strub
> On Monday, 3 February 2014, 11:21, Stephen Connolly
> wrote:
> > +1
>
> spot checks to confirm that Robert beat me to my standard tests: pass
>
>
>
> On 2 February 2014 11:11, Robert Scholte wrote:
>
>> +1
>>
>> rat: only approved licenses
>> sha1: correct
>>
GitHub user kevinarpe opened a pull request:
https://github.com/apache/maven-surefire/pull/31
Fixed tiny doc bug
* Example for TestNG <= 5.11 was using version 6.3.1.
** Fixed to use 5.11
You can merge this pull request into a Git repository by running:
$ git pull https://g
+1
spot checks to confirm that Robert beat me to my standard tests: pass
On 2 February 2014 11:11, Robert Scholte wrote:
> +1
>
> rat: only approved licenses
> sha1: correct
> zip build: correct
> usage (with -Dscmpublish.skipCheckin): 'svn add' and 'svn remove' confirmed
>
> regards,
>
> Robe
15 matches
Mail list logo