On 31 May 2015 at 08:18, Jason van Zyl wrote:
> I’m sure those responsible for the migration of the Mojo project monorepo
> into the separated repos will help us.
I ask because I'm going to be facing the same thing at work soon-ish, so
there is a good chance of finding some capacity during work
+1 from me, too! Well said.
On Sun, May 31, 2015 at 6:09 AM, Michael Osipov wrote:
> Am 2015-05-30 um 17:17 schrieb Jason van Zyl:
>
>> If they have truly separate development cycles, then I think it best to
>> try and move toward meaningful (semantic) versioning for each component.
>> Which mea
Github user andrewgaul closed the pull request at:
https://github.com/apache/maven-plugins/pull/53
---
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 featu
I’m sure those responsible for the migration of the Mojo project monorepo into
the separated repos will help us.
> On May 30, 2015, at 6:33 PM, Barrie Treloar wrote:
>
> On 30 May 2015 at 21:29, Jason van Zyl wrote:
>
>> Nothing will give me greater joy than removing the last traces of SVN fr
On 30 May 2015 at 21:29, Jason van Zyl wrote:
> Nothing will give me greater joy than removing the last traces of SVN from
> the Maven project.
>
> Did someone already start a list of what to convert? If so I’ll use that
> as a starting point, if not I’ll make one.
>
> Have we already discussed b
GitHub user andrewgaul opened a pull request:
https://github.com/apache/maven-plugins/pull/53
MCHECKSTYLE-297: Add licenses stanza
This allows license compliance tools like VersionEye to categorize
dependencies.
You can merge this pull request into a Git repository by running:
Am 2015-05-30 um 17:17 schrieb Jason van Zyl:
If they have truly separate development cycles, then I think it best to try and
move toward meaningful (semantic) versioning for each component. Which means
they have their own version and are released individually.
As part of the Git migration I t
+1 for moving to git.
Regards
Mirko
--
Sent from my mobile
Am 29.05.2015 13:23 schrieb "Jason van Zyl" :
> I think it's time for a full migration of all our repositories to Git. I
> just see the email with Dennis struggling to merge a simple pull request
> and I think it's just time to switch co
If they have truly separate development cycles, then I think it best to try and
move toward meaningful (semantic) versioning for each component. Which means
they have their own version and are released individually.
As part of the Git migration I think putting components that have their own
un
I've been wondering if we should just give every component in maven-shared
the same version number and always release all of the modules at the same
time ? (this would influence an upcoming git migration)
Kristian
I updated the page with facts about the aggregators causing git migration not
so easy
https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration#GitMigration-Migratinganaggregatortreeintoacollectionofgitrepos
given figures, testing the migration for skins (5) or doxia-tools (5) would be
wi
Unittests fixed with http://svn.apache.org/r1682598
Op Sun, 03 May 2015 21:27:37 +0200 schreef Robert Scholte
:
Op Fri, 01 May 2015 22:59:05 +0200 schreef Dennis Lundberg
:
Hi,
After doing some work on the Checkstyle Plugin today, I noticed that
several of our Jenkins jobs for plugins a
https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
On 30 May 2015 at 21:59, Jason van Zyl wrote:
> Nothing will give me greater joy than removing the last traces of SVN from
> the Maven project.
>
> Did someone already start a list of what to convert? If so I’ll use that
> as a sta
Nothing will give me greater joy than removing the last traces of SVN from the
Maven project.
Did someone already start a list of what to convert? If so I’ll use that as a
starting point, if not I’ll make one.
Have we already discussed breaking monorepos like shared and plugins into their
indi
14 matches
Mail list logo
