Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67605975
Rebased and then pushed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user asfgit closed the pull request at:
https://github.com/apache/maven-plugins/pull/40
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature i
Awesome!
I know there are plugins over at Codehaus Mojo that uses tools.jar.
/Anders
On Thu, Dec 18, 2014 at 10:58 PM, Robert Scholte
wrote:
>
> Hi all,
>
> small update: I've fixed MANIMALSNIFFER-49
> I've built Maven from trunk using the latest SNAPSHOT of the
> animalsniffer-maven-plugin and
Hi all,
small update: I've fixed MANIMALSNIFFER-49
I've built Maven from trunk using the latest SNAPSHOT of the
animalsniffer-maven-plugin and now it succeeds.
Next I'll search for a couple of plugins which now depend on the tools.jar
and see what we can do there.
thanks,
Robert
[1] https:
Github user michael-o commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67556876
It would be fine to reset the branch to the top of `origin/master`,
cherry-pick your changes, start `rebase -i HEAD~2` and the squash both.
---
If your project is set up
You could always clone repositories and do fixes locally and then submit
pull requests. What seems to be the problem?
Clearly, if you have questions these lists are the right place to ask.
On Thu, Dec 18, 2014 at 4:15 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
> I may have so
I may have some availability... But I can't guarantee
On Thursday, December 18, 2014, Ron Wheeler
wrote:
> I am willing to put in some time fixing the docs but I want to have a
> developer with commit privileges to work with me.
>
> I expect this person to commit changes to git that I write and
I am willing to put in some time fixing the docs but I want to have a
developer with commit privileges to work with me.
I expect this person to commit changes to git that I write and the read
and generate the site and get the revisions onto the maven.apache.org site.
It would be nice if they
+1
On Dec 18, 2014, at 7:10 AM, Igor Fedorenko wrote:
> Hi,
>
> We solved 1 issue:
> https://jira.codehaus.org/browse/MPLUGINTESTING-44
>
> There are no issues left in JIRA
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1106/
>
> http://repository.apache.org/con
Here is my count of the results:
A: Tony Chemit, Andreas Gudian, Manfred Moser, Tim Astle, Chris Graham, Dan
Rollo, Emilio Lopez, Matt Stephenson, Daniel Mark
B: Stephen Connolly, Anders Hammar, Stephen Krull, Martin Grigorov, Jeroen
Hoek, Graham Leggett, Cody Fyler, David Hoffer, Michael Osipov,
The polls are now closed
On Monday, December 15, 2014, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> After the run-off round, we are left with two names standing.
>
> This second vote will be a straight and simple majority wins.
>
> The vote will be open for at least 72 hours (with
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67459407
Are you referring to
git rebase -i upstream/master
then squash all commits and push that ?
---
If your project is set up for it, you can rep
Github user michael-o commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67453526
Christian, can you squash your commits please?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your pro
13 matches
Mail list logo
