Create one jira ticket for each project and create a 'depends on' link
between the issues.
K
8. jan. 2014 22:14 skrev "Jeffrey E Care" følgende:
> Today I created an enhancement request for the assembly plugin (
> http://jira.codehaus.org/browse/MASSEMBLY-680).
>
> I would like to submit a patch
+1, non-binding.
PS : FTR, I suppose we're talking about
the fa42b42693571297b323f474f9228ce99ffaf662 git sha1 tag.
2014/1/8 Robert Scholte
> +1 (binding)
>
> Robert
>
> Op Tue, 07 Jan 2014 19:22:38 +0100 schreef domi :
>
>
> Hi,
>>
>> We fixed 11 issues. The new feature is the jgit provide
Today I created an enhancement request for the assembly plugin (
http://jira.codehaus.org/browse/MASSEMBLY-680).
I would like to submit a patch for this issue, but in my investigation
I've discovered that I would likely need to touch at least two
(plexus-archiver, maven-assembly-plugin), possibl
With spring, you can say:
@Component
class X implements Y,Z
And at call site:
@Inject
private Y y;
@Inject
private Z z;
And expect (scope dependent) to get the same instance of X in both y and z.
Can I achieve this in m3.2 core ?
Kristian
+1 (binding)
Robert
Op Tue, 07 Jan 2014 19:22:38 +0100 schreef domi :
Hi,
We fixed 11 issues. The new feature is the jgit provider (based on jgit).
Details:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&version=18783
Staging repository:
https://repository.apache.org/conten
Oh, before I forget... the take 2 SCM tag was pushed to ASF git servers, so
perhaps we should push the fa42b42 tag with a distinguishing tag name.
Github seems to be smart enough to pick up that the tag changed:
https://github.com/apache/maven-scm/tree/maven-scm-1.9 but others who
checked out from
Tests performed by me:
* Source release SHA1 sum matches in email => PASS
* RAT report is same or better than previous release => 0 files, so PASS
* Source bundle builds successfully => PASS
These are all the tests I have time to run right now, but on this basis I
am happy to vote
+1 (binding)
