No where. one +1, nothing else.
On Sat, Mar 1, 2014 at 1:43 AM, Dan Tran wrote:
> how are we with this vote?
>
> -D
>
>
> On Sun, Feb 23, 2014 at 12:37 PM, Mark Derricutt wrote:
>
>> On 24 Feb 2014, at 5:12, Benson Margulies wrote:
>>
>> > Maven scm 1.9 does not necessarily correspond to git 1.
how are we with this vote?
-D
On Sun, Feb 23, 2014 at 12:37 PM, Mark Derricutt wrote:
> On 24 Feb 2014, at 5:12, Benson Margulies wrote:
>
> > Maven scm 1.9 does not necessarily correspond to git 1.9. You would need
> to look at those release notes.
>
> Git 1.8.x changed the output of the hum
Hi,
after reading and undestanding published the fixed page.
Kind regards
Karl-Heinz Marbaise
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
I still can't access jira.codehaus.org, so let me respond this way.
Mark, I think you're wrong here. The custom ruleset is added as a
dependency to the maven-checkstyle-plugin, not to the project. So it'll
always be used once Maven resolves the plugin dependencies, no matter the
scope (it´s
I think both of your issues should be fixed at wagon itself. btw, what is
wrong with https? as an input? certificate/connection related?
-Dan
On Fri, Feb 28, 2014 at 2:02 AM, Karl Heinz Marbaise wrote:
> Hi Dan,
>
>
>
> > wagon-maven-plugin and vfs-maven-plugin do this. vfs was introduce sinc
Hi Rob! :)
indeed it has been a very long while, so sorry for that :(
OK I understand your PoV, count on me if you want to co-operate - I need
that feature as well in order to make the release-plugin able to generate
that version using a tool, but without exposing such APIs that allow me
plugging
Hi Simone,
It's been a while, so I'll need to have another look at this.
At first glance I'm not yet happy with the suggested API.
I'd need to make some time so come with a final solution.
Robert
Op Fri, 28 Feb 2014 14:56:35 +0100 schreef Simone Tripodi
:
Hi all mates,
I am in a phase whe
Hi all mates,
I am in a phase where I could get benefit of that feature as well (and,
since I am still in the committer list, I can provide some help here) so I
would like to push it :P
@Robert: before merging the contribution we received in JIRA, I'd kindly
ask if you had a better idea if new AP
Yeah, I just wanted to show one example.
The point is that install mojo is not invoked for all projects in the
build, as expected, and will never kick in to install the accumulated
projects:
https://github.com/apache/maven-plugins/blob/8678f791e717c14f6b91b80fade0a376ac87625a/src/main/java/org/ap
Hi,
> Install at end of m-install-p has problems related to aggregator POMs
for example, here is an example plugin that will NOT install anything
than the aggregator POM (attached).
If you change that project into a multi -module build it will work.
An aggregator is something different than a
Install at end of m-install-p has problems related to aggregator POMs for
example, here is an example plugin that will NOT install anything than the
aggregator POM (attached).
If you have such set up, it will fail. Simply put, the m-install-p install
mojo blindly expects it will get invoked for _e
To make it more cleared here is the output
Writing Pack 2: izpack-demo01 für Linux
[ End ]
[INFO]
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @
demo-assembly ---
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @
demo-assembly ---
[INF
Hi,
i have question concerning a maven plugin which defines it's own
lifecycle (extensions true)...it produces artifacts without a problem...
I have observed an issue...this plugin does not work in relationship
with maven-install-plugin / maven-deploy-plugin in relationship with
installAtEnd
Hi Dan,
> wagon-maven-plugin and vfs-maven-plugin do this. vfs was introduce since
wagon-m-p is heavily depends on maven runtime. ( wagon-maven-plugin
currently not wokring with mvn 3.1 out of box due to missing jars at
maven/lib directory)
But the docs expresses that they do not support htt
14 matches
Mail list logo
