Le mardi 4 septembre 2012 21:59:28 Dennis Lundberg a écrit :
> Hi all
>
> I'd like to try to get the Jenkins jobs maven-plugins-ITs-m2 and
> maven-plugins-ITs-m3 back on track a gain, but I'm not sure how to.
> Perhaps we can crack it together. Here's a summary of the current problems:
+1000 I'm t
I have no desire to keep a copy of the entire repo locally.
>From what I can see, the current SVN is well managed and well understood. I
see little value in changing, other than to pander to the current fad in
scm.
-Chris
On Wed, Sep 5, 2012 at 5:55 AM, Jason van Zyl wrote:
> How's Git doing a
On 4 September 2012 14:29, Mark Struberg wrote:
> just take as example that you like to checkout all maven core plugins in one
> go because you like to do some refactoring/checks/upgrade.
> That would require you to go into each plugin project and get the stuff from
> there. And where would you
it is possible to have them all in one git repo and still release
separately, we do it in a toolchain repository in jetty and use maven
release plugin for it as well
so its not _required_ that you split it all up by choosing git
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com
On Tue, Sep 4,
On Tue, Sep 4, 2012 at 5:29 PM, Mark Struberg wrote:
> just take as example that you like to checkout all maven core plugins in one
> go because you like to do some refactoring/checks/upgrade.
I see. So the fact that we have a single trunk in svn for all the
plugins is the thing that isn't conve
just take as example that you like to checkout all maven core plugins in one go
because you like to do some refactoring/checks/upgrade.
That would require you to go into each plugin project and get the stuff from
there. And where would you put the aggregator pom for CI and development builds?
Sa
Mark, I disagree. Any group of modules that is released together can
just have a git repo. What case do you have in mind where we'd need to
fight with the git submodule madness?
For others: if a project wants to move to git, the project must
provide a sacrificial victim volunteer to help with git
Back on this.
I wonder about changing a bit the distrib directory tree ?
The goal is to ease release.
For voting period the candidate files can be committed to the correct
tree here https://dist.apache.org/repos/dist/dev/ (instead of scp to
people.a.o)
Then once the vote has passed releasing is si
Op Tue, 04 Sep 2012 21:59:28 +0200 schreef Dennis Lundberg
:
Hi all
I'd like to try to get the Jenkins jobs maven-plugins-ITs-m2 and
maven-plugins-ITs-m3 back on track a gain, but I'm not sure how to.
Perhaps we can crack it together. Here's a summary of the current
problems:
maven-plugi
And the Seam guys and a few others got pretty much stuck because the
granularity level needs to be up front if you move to GIT.
GIT is cool, but it is not as modular as SVN. git-submodules are still a farce
and there is nothing else which allows modularisation.
Don't get me wrong, I really like
On 2012-09-04 22:10, Dennis Lundberg wrote:
> On 2012-09-04 21:55, Jason van Zyl wrote:
>> How's Git doing at Apache these days?
>
> A pilot was started some time ago, with a few volunteering projects. I
> have heard anything about its progress in a while. I'll ask over @infra
> and report back he
jenkins does it (1 plugin = 1 repo ) and I sincerely see no solution
to avoid that.
Each plugin or each lib has its own lifecycle and requires to have its
own git repo to be clean
That's why on jenkins we have the IRC bot to manage them
But it is easier on github because they provide many APIs to d
2012/9/4 Andrew Waterman :
> The drools guys did a really nice move from Subversion a few years back.
>
> http://blog.athico.com/2010/12/drools-migrated-to-git.html
>
> One of the key things they did, was reorganize their poms and project
> structure.
>
> I'd be willing to help out. I think there
The drools guys did a really nice move from Subversion a few years back.
http://blog.athico.com/2010/12/drools-migrated-to-git.html
One of the key things they did, was reorganize their poms and project structure.
I'd be willing to help out. I think there could be a lot more to this move than
j
On 2012-09-04 21:55, Jason van Zyl wrote:
> How's Git doing at Apache these days?
A pilot was started some time ago, with a few volunteering projects. I
have heard anything about its progress in a while. I'll ask over @infra
and report back here.
> Anyone interested in pursuing putting Maven in G
> -Original Message-
> From: Jason van Zyl
> Sent: Tuesday, September 04, 2012 15:55
>
> How's Git doing at Apache these days?
>
> Anyone interested in pursuing putting Maven in Git as the
> canonical SCM?
Comments from the peanut gallery: It would make it very nice to contribute back.
Hi all
I'd like to try to get the Jenkins jobs maven-plugins-ITs-m2 and
maven-plugins-ITs-m3 back on track a gain, but I'm not sure how to.
Perhaps we can crack it together. Here's a summary of the current problems:
maven-plugins-ITs-m2
We only have one plugin failing here, Maven Repository Plu
How's Git doing at Apache these days?
Anyone interested in pursuing putting Maven in Git as the canonical SCM?
Thanks,
Jason
--
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---
+1
Dan
On Sep 2, 2012, at 7:03 PM, Benson Margulies wrote:
> We solved 4 issues:
>
> ** Bug
>* [MSHADE-103] - maven-shade-plugin does not resolve from
> user-defined repositories
>* [MSHADE-124] - Need better plan for getting
> dependency-reduced-pom.xml out of basedir
>* [MSHADE
+1
LieGrue,
strub
- Original Message -
> From: Olivier Lamy
> To: Maven Developers List
> Cc:
> Sent: Tuesday, September 4, 2012 2:15 PM
> Subject: Re: [VOTE] Release maven-shade-plugin 2.0 -- attempt 2
>
> +1
>
> 2012/9/3 Benson Margulies :
>> We solved 4 issues:
>>
>> ** Bug
The Maven team is pleased to announce the release of the Maven EAR
Plugin, version 2.8
The plugin generates a JavaEE Enterprise Archive (EAR) file.
http://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugin
+1
2012/9/3 Benson Margulies :
> We solved 4 issues:
>
> ** Bug
> * [MSHADE-103] - maven-shade-plugin does not resolve from
> user-defined repositories
> * [MSHADE-124] - Need better plan for getting
> dependency-reduced-pom.xml out of basedir
> * [MSHADE-130] - Mark mojo as threadSafe
22 matches
Mail list logo