AIUI, SVN is still required by Infra because of svnpubsub:
- for the dist repo (that is not a big deal)
- for websites (might cause some grief)
On 13 February 2014 03:37, Jason van Zyl wrote:
> Can we start the process of converting everything to Git. I don't really see
> any benefit in using S
Sounds like a plan.
On Feb 14, 2014, at 5:58 PM, Paul Benedict wrote:
> Okay. If that's the way to proceed, then I'd kindly recommend simply
> renaming the JIRA version (3.2.0 => 3.2.1) rather than leaving an empty
> version behind. What do you think?
>
>
> On Fri, Feb 14, 2014 at 4:54 PM, Jas
Okay. If that's the way to proceed, then I'd kindly recommend simply
renaming the JIRA version (3.2.0 => 3.2.1) rather than leaving an empty
version behind. What do you think?
On Fri, Feb 14, 2014 at 4:54 PM, Jason van Zyl wrote:
> I think they all need to be grouped under one version for the r
+1
Analyzer...
stagingUrl: https://repository.apache.org/content/repositories/maven-1006
groupId: org.apache.maven
artifactId: apache-maven
version: 3.2.1
Source ZIP url exists.
https://repository.apache.org/content/repositories/maven-1006/org/apache/maven/apache-maven/3.2.1/apache-maven-3.2.1-s
I think they all need to be grouped under one version for the release. If we
failed several times, I wouldn't always make an issue for regressions and if a
user went to look in JIRA at the 3.2.1 release and saw few issues it would
probably be confusing.
On Feb 14, 2014, at 5:44 PM, Paul Benedic
Thanks Jason. FWIW, there isn't a need to move the issues to the next patch
version when a re-spin is necessary. These tickets could have theoretically
stayed as 3.2.0 and then any new blockers that got fixed would be in the
3.2.1 queue. I think it's easier managing that way and clearer, otherwise
Hi,
+1 from me...
Checked with serveral plugin projects, with my own projects...
Checked the sha1 of the src package.
> Source release checksum(s):
> apache-maven-3.2.1-src.zip sha1: b801a145ea25c9277231030da81f36df522b7b8b
Kind regards
Karl Heinz Marbaise
> Hi,
Time to release Maven 3.2.1!
+1 all m2e tests pass
--
Regards,
Igor
On 2/14/2014, 12:58, Jason van Zyl wrote:
Hi,
Time to release Maven 3.2.1!
Here is a link to Jira with 33 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=20041
Staging repo:
https://repository.apache.org/conten
+1 from me. Works with ksoap2-android, android-maven-plugin and the samples.
manfred
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi,
Time to release Maven 3.2.1!
Here is a link to Jira with 33 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=20041
Staging repo:
https://repository.apache.org/content/repositories/maven-1006/
The distributable binaries and sources for testing can be
MRELEASE-862, which should fix MRELEASE-812 (both fixed for next release)
However, rumors go this fixes the Git Issue(s), but also that it doesn't.
No good feedback, so I'm not sure if this will be the N-th release in a
row with bad Git support.
Robert
[1] https://jira.codehaus.org/browse/MR
No, I'll put it on the list for 3.2.2.
On Feb 14, 2014, at 3:10 AM, Stuart McCulloch wrote:
> On 14 Feb 2014, at 04:39, Jason van Zyl wrote:
>
>> Ok, everything is in. Just running through my normal set of tests and I'll
>> try to get 3.2.1 staged later tonight or in the morning.
>
> Does th
On 14 Feb 2014, at 08:09, Baptiste Mathus wrote:
> Seems like this super pom is versioned at github under the sonatype
> organization (?).
>
> Cf. scm tag in
> http://repo1.maven.org/maven2/org/codehaus/codehaus-parent/4/codehaus-parent-4.pom
> But https://github.com/sonatype/codehaus-parent giv
Op Fri, 14 Feb 2014 09:01:14 +0100 schreef Karl Heinz Marbaise
:
Hi Anders,
> I reported this Codehaus parent issue a long time ago (HAUS-2245 [1]).
Good to know...
Unfortunately the codehaus-parent seems to be in a unmaintained state.
Who is responsible for the codehaus-parent ? Can we
+1
2014-02-14 10:17 GMT+01:00 Arnaud Héritier :
> +1
>
>
> On Fri, Feb 14, 2014 at 1:32 AM, Olivier Lamy wrote:
>
> > +1
> >
> > On 14 February 2014 02:14, Stephen Connolly
> > wrote:
> > > We have not made a release of Maven 2.x since 2.2.1 which was August
> > 2009.
> > >
> > > During that p
With myrepos one (or a team) can list many VCS repos in a config file and do
batch operations on all of the repos or selectively clone (checkout) repos.
http://myrepos.branchable.com
myrepos is written in perl and packaged in Debian:
http://packages.qa.debian.org/m/myrepos.html
Regards, Thomas
Same/similar issue with svn:externals today... IOW if there are unpinned
svn:externals m-r-p does not pin & unpin them during the release:prepare
stage.
I think the scm api may need some refactoring to enable these kind of mixed
repository actions
On 14 February 2014 08:33, Tomasz Krakowiak wrot
+1
On Fri, Feb 14, 2014 at 1:32 AM, Olivier Lamy wrote:
> +1
>
> On 14 February 2014 02:14, Stephen Connolly
> wrote:
> > We have not made a release of Maven 2.x since 2.2.1 which was August
> 2009.
> >
> > During that period no release manager has stepped up to cut a release.
> >
> > I would
We already know that maven-plugins is going to be a big PITA unless we just
decide to stay with the current git-svn clone and accept it structure.
Having done quite a few migrations I know I'd be spending a truckload of
time getting the filter-branch scripts and the rewrites working properly
(the
Right. It seems no one knows where the source is.
I think this is better to discuss in the JIRA ticket. It's not for this
list.
I'm sure that e.g. the Mojo team could take responsibility of
codehaus-parent. Just need Ben to set up a repo.
/Anders
On Fri, Feb 14, 2014 at 9:09 AM, Baptiste Mathus
OK.
But for the record, I was not (yet) proposing to release using the
submodule repo.
More the strategy proposed by Mark: use submodules 'just" to ease
retrieving a whole lot of projects under a working directory tree, and then
release project by project (=repo by repo) as-of today.
Anyway, I sup
Some of the converters/one of the converters correctly creates git tags
from svn branches, however I'm unsure what happens if the "tag" has been
committed to as sometimes happens with n00b devs in SVN land.
On Fri, Feb 14, 2014 at 9:31 PM, Lennart Jörelid
wrote:
> While I agree that the migratio
Are you aware that maven-release-plugin isn’t currently working with git
submodules because of http://jira.codehaus.org/browse/SCM-530 ?
(I’m just warning you, so you wouldn’t have painful surprise one day)
Wiadomość napisana przez Hervé BOUTEMY w dniu 14 lut
2014, o godz. 09:19:
> No doubt
While I agree that the migration from Subversion to Git can be somewhat
labour-intensive,
it can be an ongoing activity, simply migrating piece by piece.
Since there is a particular issue with the Maven release plugin creating
what is normally
interpreted as Git branches (as opposed to Git tags) o
git clone --recursive
https://github.com/Batmat/asciidoctor-maven-plugin-issue-494-html5-backend-not-working?
2014-02-14 9:21 GMT+01:00 Hervé BOUTEMY :
> found the doc: seems interesting
>
> any live example to show?
> or a demo on skins, for example, ie not much submodules, so it seems a good
>
I think the main problem with especially maven-plugins is the sheer amount
of work required to convert these to individual repositories, especially
due to the somewhat not-good structure of the current clone.
The others should be fairly straight forward, splitting maven-shared
included.
Kristian
found the doc: seems interesting
any live example to show?
or a demo on skins, for example, ie not much submodules, so it seems a good
cancidate for tests
Regards,
Hervé
Le vendredi 14 février 2014 08:46:32 Baptiste Mathus a écrit :
> +1 on the submodule solution. We started using it some mont
No doubt it can be done in general, but the question is on ASF (canonical) git
repo [1]
at the moment, everything seems flat
IMHO, some git expert should work with infra to make it more structured
Regards,
Hervé
[1] https://git-wip-us.apache.org/repos/asf
Le vendredi 14 février 2014 20:23:34 F
Seems like this super pom is versioned at github under the sonatype
organization (?).
Cf. scm tag in
http://repo1.maven.org/maven2/org/codehaus/codehaus-parent/4/codehaus-parent-4.pom
But https://github.com/sonatype/codehaus-parent gives a 404...
Anyone?
2014-02-14 9:01 GMT+01:00 Karl Heinz Ma
On 14 Feb 2014, at 04:39, Jason van Zyl wrote:
> Ok, everything is in. Just running through my normal set of tests and I'll
> try to get 3.2.1 staged later tonight or in the morning.
Does that include a fix for the issue Mark found building the dependency graph?
http://www.mail-archive.com/dev
Hi Anders,
> I reported this Codehaus parent issue a long time ago (HAUS-2245 [1]).
Good to know...
Unfortunately the codehaus-parent seems to be in a unmaintained state.
Who is responsible for the codehaus-parent ? Can we (or i) take the
issue and fix it ?
/Anders
[1] http://jira.code
31 matches
Mail list logo
