Excellent proposal Hervé, but how do we deal with jira-based
submissions ? I am probably @author of half my committs and @committer
of the rest ?
Kristian
2014-09-11 8:10 GMT+02:00 Hervé BOUTEMY :
> to me, it's clear we need some formal attribution to ASF from each major
> contributor, since th
I agree that it is about projects migrating dependencies - which can take
awhile, to put it mildly.
However, migrating package names at the same time as migrating groupIDs can
go a long way towards avoiding ClassCastExceptions.
That would - in turn - imply that a new major version number is requir
When/if we move these components I assume they will get a new groupId? Will
that not cause issues with duplicated plexus libraries (due to two
different sets of GA) until "everything" has moved over to the new
dependencies?
/Anders
On Thu, Sep 11, 2014 at 8:10 AM, Hervé BOUTEMY
wrote:
> to me,
to me, it's clear we need some formal attribution to ASF from each major
contributor, since the code was committed to Codehaus, not ASF, and Codehaus
is not an antity that can transfer the result to ASF
for the formal part, without being a lawyer, I suppose each constributor has
to confirm he i
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%20component%20%3D%20maven-dependency-analyzer%20ORDER%20BY%20priority%20DESC
Staging repo:
https:
+1
On 9 September 2014 05:47, Karl Heinz Marbaise wrote:
> Hi,
>
> We solved 5 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11143&version=18707
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MRAR%20AND%20status%2
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
Staging repository:
https://repository.apache.org/content/repositories/maven-1054/
Staging site: http://maven.apache.org/wagon-ar
+1
Regards,
Hervé
Le lundi 8 septembre 2014 21:47:06 Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 5 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11143&version=187
> 07
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/issues/?jql=proje
Sorry, I thought that the plugins, the scm ones in this case, had moved to
git? Still in SVN? If so, then no issues.
-Chris
On Thu, Sep 11, 2014 at 11:43 AM, Benson Margulies
wrote:
> For plugins, you need mostly to make an account on Codehaus JIRA, then you
> svn checkout as per the informatio
For plugins, you need mostly to make an account on Codehaus JIRA, then you
svn checkout as per the information in the plugin's page, and then you can
attach a patch to a JIRA.
On Wed, Sep 10, 2014 at 9:37 PM, Chris Graham wrote:
> Whilst not strictly related to this thread...
>
> Is there a do
Whilst not strictly related to this thread...
Is there a document that tells us what we need to do to contribute?
How/what repos we need to clone/setup, how to generate a patch/pull request
etc?
Thanks,
-Chris
On Thu, Sep 11, 2014 at 7:04 AM, Benson Margulies
wrote:
> Of course; I'm just tryi
Ideally yes, it would be wonderful to be able to create a WI as a part if the
release.
The problem Jazz/RTC at least is that there is no command line tool to
manipulate WI's. There is a feature request to do so, but it has not been
started.
That issue aside, there is also the case where the WI
For accomplishing this task, your configuration can be like this
org.apache.maven.plugins
maven-jarsigner-plugin
1.2
sign webcontent jars
prepare-package
sign
Of course; I'm just trying to help you get off the ground; is there
something else you'd like me to do?
On Wed, Sep 10, 2014 at 4:58 PM, Robert Scholte
wrote:
> I don't want to depend on external systems.
> you could add me (rfscholte) but that'll only be for reproducing the issue.
> and then I
I don't want to depend on external systems.
you could add me (rfscholte) but that'll only be for reproducing the issue.
and then I need isolate the problem and translate it to a unittest.
Op Wed, 10 Sep 2014 22:53:38 +0200 schreef Benson Margulies
:
Well, you'll need to push a clone where y
Well, you'll need to push a clone where you can write, or tell me your
github ID so I can add you as a collaborator.
On Wed, Sep 10, 2014 at 4:45 PM, Robert Scholte
wrote:
> The first step already fails on my machine.
>
> mvn release:prepare release:perform -B -DpushChanges=false
>
> I'm a bit s
The first step already fails on my machine.
mvn release:prepare release:perform -B -DpushChanges=false
I'm a bit surprised, because I see:
[INFO] Executing: cmd.exe /X /C "git push
g...@github.com:bimargulies/pom-file-name-tc.git
refs/heads/master:refs/heads/master"
Actual failure:
[ERROR]
Hi Chris,
I had to dive deep in my mail archive, but it seems that the day after my
attempt a colleague managed to release with my initial setup. So it
probably had to do with my rights, configuration or whatever. I'll ask the
status of that project and if the still can release successfully
Step 1: in the top level dir of the example, run mvn --batch-mode
release:prepare release:perform. All will be well. A repo will populate in
/tmp.
Step 2: modify pom in 'second' directory to use the just-release parent
pom, commit, push.
Step 3: mvn release:prepare in second directory.
No errors
I am going back and forth on this topic and its reference, and still not
able to get my singleton belonging to a jar to be shared across plugins.
Dirk how are you doing at your side?
Thanks
-Dan
On Fri, Aug 1, 2014 at 9:21 AM, Dan Tran wrote:
> So far it looks to me it is as simple as settin
that's just the beginning...
so: how did you execute it? what did you get? what would you expect?
Op Wed, 10 Sep 2014 20:54:49 +0200 schreef Benson Margulies
:
Aha, I have one for you.
https://github.com/bimargulies/pom-file-name-tc. I
attached it to a dup JIRA which I closed, or you can ta
Aha, I have one for you. https://github.com/bimargulies/pom-file-name-tc. I
attached it to a dup JIRA which I closed, or you can take it as you see it.
You may in general find MRELEASE-887 helpful in this respect.
On Wed, Sep 10, 2014 at 2:53 PM, Robert Scholte
wrote:
> Hi,
>
> IIRC I didn't hav
Hi,
IIRC I didn't have enough info to make a unittest, i.e. reproduce what
they get right now and what they would expect to be able to fix it.
That would take me too much time to find out, so I left this one open for
now.
thanks,
Robert
Op Wed, 10 Sep 2014 20:23:07 +0200 schreef Benson Mar
Yes, the remarks which dribbled off pointed to adapting the fix back into
the m-r-p.
On Wed, Sep 10, 2014 at 2:21 PM, Karl Heinz Marbaise
wrote:
> Hi Benson,
>
> > Is anyone working on a fix to MRELEASE-875?
>
>>
>>
> Based on JIRA it is assigned to Dominik Bartholdi which requested reviews
> f
Hi Benson,
> Is anyone working on a fix to MRELEASE-875?
Based on JIRA it is assigned to Dominik Bartholdi which requested
reviews from others on Github...
BTW: Not working on that...
Kind regards
Karl-Heinz Marbaise
--
Is anyone working on a fix to MRELEASE-875?
Sorry for the reply on list, my codehaus jira credentials seem to have gotten
messed up….
I would expect the best normal workflow would be to have the release plugin
create the work item, then attach the change sets to it. I have some evidence
that it is possible for external programs to do st
Here my +1
Kind regards
Karl-Heinz Marbaise
On 9/8/14 9:47 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11143&version=18707
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%
28 matches
Mail list logo
