So, if the scm stuff is in git, my original question still remains
unanswered.
What are the process steps needed to go through to be able to perform
meaningful work in terms of working on the maven-scm modules?
Has anyone actually documented what needs doing on the git side of things?
Creating a
+1 from me ..
Karl Heinz Marbaise wrote on 14.09.2014 11:19:
> Hi,
>
> We solved 3 issues:
> http://jira.codehaus.org/browse/MSHARED/fixforversion/19225
>
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-depend
+1 tested http://jira.codehaus.org/browse/WAGON-407 using maven-3.1.x and
maven-3.2.x
Thank you for looking harder into the shading issue fix.
-D
On Sun, Sep 14, 2014 at 6:56 PM, Olivier Lamy wrote:
> Hi,
> I'd like to release Apache Wagon 2.7
> We fixed 4 issues:
>
> http://jira.codehaus.or
Hi,
I'd like to release Apache Wagon 2.7
We fixed 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20560&styleName=Text&projectId=10335&Create=Create
Since last vote, the shading has been fixed for Dan issue.
Staging repository:
https://repository.apache.org/content/repositories
ok got it.
I just pushed a fix for that. (the shared-http lib need to be shaded as well)
I will start a second vote.
This vote is cancelled.
On 12 September 2014 11:37, Dan Tran wrote:
> that works because M2_HOME/lib has jsoup.jar, common-io.jar,
> commons-lang.jar ( those are NOT in 3.1.x)
>
+1
On 15 September 2014 04:19, Karl Heinz Marbaise wrote:
> Hi,
>
> We solved 3 issues:
> http://jira.codehaus.org/browse/MSHARED/fixforversion/19225
>
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-dependency-t
Le dimanche 14 septembre 2014 18:47:56 Karl Heinz Marbaise a écrit :
> BTW: Just a little question:
>
> If i take a look on this site:
> http://maven.apache.org/shared-archives/maven-reporting-impl-LATEST/plugin-m
> anagement.html
>
> it shows me a link to
> http://maven.apache.org/scm-archives/s
Hi,
We solved 3 issues:
http://jira.codehaus.org/browse/MSHARED/fixforversion/19225
http://jira.codehaus.org/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-dependency-tree%20ORDER%20BY%20priority%20DESC
Staging repo:
https://repository.
Hi Robert,
> SCM is a Git project and I think we will be punished
> if we remove tags
there.
So we should prevent to be bad guys ;-)...
Search for Maven-3.2.0 ...
Hm...Ok...
So we just let the tag in the history without having a real release
existing neither in Central etc.
Ki
SCM is a Git project and I think we will be punished if we remove tags
there.
Search for Maven-3.2.0 ...
Op Sun, 14 Sep 2014 19:15:32 +0200 schreef Karl Heinz Marbaise
:
Hi,
> Hi Benson,
I would suggest to send an offical makes it cleared and better to follow
on the list...
[CANCLE] [
The Apache Maven team is pleased to announce the release of the
Apache Maven Shared Component: Maven Dependency Analyzer Version 1.5
http://maven.apache.org/shared/maven-dependency-analyzer/
Analyzes the dependencies of a project for undeclared or unused artifacts.
org.apache.maven.shared
On Sat, Sep 13, 2014 at 2:55 PM, Robert Scholte
wrote:
> http://markmail.org/thread/owemhec7vfjdnvhc
>
> IIRC the bottom line is that some parts are hard to migrate.
> For instance: we prefer to keep the plugins together, but if it's 1 repo
> per release-cycle project, we need a huge number of se
Hi,
> Hi Benson,
I would suggest to send an offical makes it cleared and better to follow
on the list...
[CANCLE] [VOTE] message...
And yes i would delete the 1.9.2 tag from SVN...
The above is my opinion.
Do we have documented this kind of behaviour somewhere i couldn't
remember that
Hi Benson,
I would suggest to send an offical makes it cleared and better to follow
on the list...
[CANCLE] [VOTE] message...
And yes i would delete the 1.9.2 tag from SVN...
Kind regards
Karl-Heinz Marbaise
On 9/14/14 5:50 PM, Benson Margulies wrote:
On Sun, Sep 14, 2014 at 11:49 AM, Ben
Hi,
The vote has passed with the following result:
+1 (binding): Karl-Heinz Marbaise, Benson Margulies, Hervé Boutemy
+1 (non binding): none
I will promote the artifacts to the central repo.
Kind regards
Karl-Heinz Marbaise
-
Hi,
> Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=18319
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&status=1
Staging repo:
https://repository.apache.org/content/re
If you merge a PR from github, please remember to make sure that there is a
commit with the special comment that causes the asf daemon to close it. [1]
Just tossing in 'closes #nnn' does the job. If you forget, you need to make
an empty commit later; there's no other way to deal with the things.
On Sun, Sep 14, 2014 at 11:50 AM, Benson Margulies
wrote:
>
>
> On Sun, Sep 14, 2014 at 11:49 AM, Benson Margulies
> wrote:
>
>> I would like to pull back this vote, unless someone objects. On the one
>> hand, the problem with the release plugin and git is already addressed in
>> 1.9.1. On the o
Github user asfgit closed the pull request at:
https://github.com/apache/maven-scm/pull/7
---
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 is ena
Github user asfgit closed the pull request at:
https://github.com/apache/maven-scm/pull/14
---
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 is en
Github user asfgit closed the pull request at:
https://github.com/apache/maven-scm/pull/19
---
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 is en
Github user asfgit closed the pull request at:
https://github.com/apache/maven-scm/pull/17
---
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 is en
Here is the situation, as I've documented in MRELEASE-875:
Using the trunk of the maven-release-plugin + SCM 1.9.1, and using either
git 1.8.5.2 or git 2.1, the problem is fixed as I see it. The contents of
the pull request suggest that it was not fixed for the person who made the
pull request, bu
Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=18319
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&status=1
Staging repo:
https://repository.apache.org/content/repositori
On Sun, Sep 14, 2014 at 11:49 AM, Benson Margulies
wrote:
> I would like to pull back this vote, unless someone objects. On the one
> hand, the problem with the release plugin and git is already addressed in
> 1.9.1. On the other hand, there are some lingering pull requests, some of
> which look
I would like to pull back this vote, unless someone objects. On the one
hand, the problem with the release plugin and git is already addressed in
1.9.1. On the other hand, there are some lingering pull requests, some of
which look reasonable, so it seems unkind to release without them. I'll
wait un
+1
Regards,
Hervé
Le jeudi 11 septembre 2014 07:45:02 Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=191
> 51
>
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MSHARED%20AND%20status%
> 20%3D%20Open%
+1 binding.
On Sun, Sep 14, 2014 at 8:29 AM, Karl Heinz Marbaise
wrote:
> Hi,
>
> anyone else ?
>
> Kind regards
> Karl-Heinz
> On 9/11/14 7:45 AM, Karl Heinz Marbaise wrote:
>
>> Hi,
>>
>> We solved 4 issues:
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?
>> projectId=11761&version=19151
Hi,
anyone else ?
Kind regards
Karl-Heinz
On 9/11/14 7:45 AM, Karl Heinz Marbaise wrote:
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=19151
http://jira.codehaus.org/issues/?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20and%20com
See http://jira.codehaus.org/browse/MRELEASE-875.
You are right about 1.9.1, but I cannot repro whatever else was going on.
On Sun, Sep 14, 2014 at 7:01 AM, Benson Margulies
wrote:
>
>
> On Sun, Sep 14, 2014 at 6:33 AM, Robert Scholte
> wrote:
>
>> Hi Benson,
>>
>> there's actually still one
On Sun, Sep 14, 2014 at 6:33 AM, Robert Scholte
wrote:
> Hi Benson,
>
> there's actually still one thing bothering me (and which also blocked me
> for doing this release):
> How can it be that there's a PR (#17) on SCM when the issue is already
> fixed?
> From other issues I remember that for som
Hi Benson,
there's actually still one thing bothering me (and which also blocked me
for doing this release):
How can it be that there's a PR (#17) on SCM when the issue is already
fixed?
From other issues I remember that for some users upgrading to SCM-1.9.1
did help, though for others it d
32 matches
Mail list logo
