[x] +1 Release these artifacts
Building OK from git commit with `mvn clean test install site` with
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_265, vendor: Private Build, runtime:
/usr/lib/j
[x] +1 Release these artifacts
Building OK from git commit with `mvn clean test install site` with
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_265, vendor: Private Build, runtime:
/usr/lib/jvm
May I have PMC reviews please?
Gary
On Fri, Aug 28, 2020 at 4:35 PM Gary Gregory wrote:
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Crypto 1.0.0 was released, so I would like to release
> Apache Commons Crypto 1.1.0.
>
> Apache Commons Crypto
Le jeu. 27 août 2020 à 13:22, Gilles Sadowski a écrit :
>
> Le jeu. 27 août 2020 à 10:06, Mark Thomas a écrit :
> >
> > On 27/08/2020 00:21, Gilles Sadowski wrote:
> > > Hi.
> > >
> > > Something happening recently (apparently unrelated to changes
> > > in the repository):
> > >
> > > https://
I have a script which downloads
https://gitbox.apache.org/repositories.json and picks out the commons
repositories.
For each one, there is another script that can check out the component repos.
It's then pretty easy to quickly scan files in all the subdirectories,
e.g. to check on pom settings.
I
@Gary Gregory
Hi gary.
Please see https://github.com/XenoAmess/commons-proper
Especially see the github-actions log.
Is this the exact function what you are looking for?
:)
Right now I only added 3 commons repos into this toolchain, means
bcel,beanutils,bsf
And the ci will fail only because bsf wi
+1
mvn -V clean package
Apache Maven 3.6.3
Maven home: /usr/share/maven
Java version: 1.8.0_265, vendor: Private Build, runtime:
/usr/lib/jvm/java-8-openjdk-arm64/jre
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-1021-aws", arch: "aarch64", family: "unix"
On Sun
> On Aug 31, 2020, at 8:24 AM, Ralph Goers wrote:
>
>
>
>> On Aug 31, 2020, at 7:01 AM, Gary Gregory wrote:
>>
>> My target use case here is: I want an easy way to work on all of Commons in
>> a new VM or a new machine, so I'd like to be able to check out all of
>> Commons in one go from any
> On Aug 31, 2020, at 7:01 AM, Gary Gregory wrote:
>
> My target use case here is: I want an easy way to work on all of Commons in
> a new VM or a new machine, so I'd like to be able to check out all of
> Commons in one go from any level for example here is an imaginary git
> submodule tree:
>
The use case you're describing is fairly well handled by the git
subtree command. There are some git plugins that add more complex
workflows on top of that, but the base command is what you're looking
for. Git submodules, in my experience, are far more useful when
pointing to release commits and tr
On Mon, Aug 31, 2020 at 10:15 AM Gary Gregory
wrote:
> On Sun, Aug 30, 2020 at 9:24 AM Gary Gregory
> wrote:
>
>> I'm talking about girl's own submodules:
>>
>> https://git-scm.com/book/en/v2/Git-Tools-Submodules
>>
>
> I think the on-line book above has been updated since 2014 (as seen on the
>
On Sun, Aug 30, 2020 at 9:24 AM Gary Gregory wrote:
> I'm talking about girl's own submodules:
>
> https://git-scm.com/book/en/v2/Git-Tools-Submodules
>
I think the on-line book above has been updated since 2014 (as seen on the
front page https://git-scm.com/book/en/v2) so the reference page
htt
I'll try if I can solve your goal using maven-plugin tonight.
If I succeed I will let you know :)
Xeno Amess 于2020年8月31日周一 下午10:06写道：
> > Right now I am checking out each and every repo one at a time. Yes, we
> > could stash OS-specific scripts some place.
> >
> > I was hoping to start at the Ap
> Right now I am checking out each and every repo one at a time. Yes, we
> could stash OS-specific scripts some place.
>
> I was hoping to start at the Apache Commons Proper level. If I need a
> script to update each submodule to the latest HEAD, then this is less
> elegant but understandable from
On Mon, Aug 31, 2020 at 9:59 AM Xeno Amess wrote:
> BTW.
> From my own view, we might need a testing maven project (or a github repo),
> for ensuring all commons repos can be used together, free of dependency
> hell, or other internal errors about using different versions of a same
> dependency.
On Mon, Aug 31, 2020 at 9:51 AM John Patrick wrote:
> On Mon, 31 Aug 2020 at 14:16, Gary Gregory wrote:
> >
> > On Mon, Aug 31, 2020 at 9:11 AM Matt Sicker wrote:
> >
> > > Git submodules are pointers to other git commits. Therefore, any
> component
> > > changes made don’t affect the mono repo
As example for dependency-hell, slf4j 1 and 2 use same namespace, means if
some dependency use slf4j1 and another use slf4j2, some really disgusting
thing will happen.
I suffered from that, once.
Xeno Amess 于2020年8月31日周一 下午9:59写道：
> BTW.
> From my own view, we might need a testing maven project
BTW.
>From my own view, we might need a testing maven project (or a github repo),
for ensuring all commons repos can be used together, free of dependency
hell, or other internal errors about using different versions of a same
dependency.
But I admit that will really be a time-costing work, and be r
If you want to point to something less specific than a commit, take a
look at git subtree instead:
https://www.atlassian.com/git/tutorials/git-subtree
On Mon, 31 Aug 2020 at 08:51, John Patrick wrote:
>
> On Mon, 31 Aug 2020 at 14:16, Gary Gregory wrote:
> >
> > On Mon, Aug 31, 2020 at 9:11 AM M
On Mon, 31 Aug 2020 at 14:16, Gary Gregory wrote:
>
> On Mon, Aug 31, 2020 at 9:11 AM Matt Sicker wrote:
>
> > Git submodules are pointers to other git commits. Therefore, any component
> > changes made don’t affect the mono repo until you update said mono repo to
> > point to the new commit. If
On Mon, Aug 31, 2020 at 9:11 AM Matt Sicker wrote:
> Git submodules are pointers to other git commits. Therefore, any component
> changes made don’t affect the mono repo until you update said mono repo to
> point to the new commit. If you do this to point at the latest release
> tags, this makes
Git submodules are pointers to other git commits. Therefore, any component
changes made don’t affect the mono repo until you update said mono repo to
point to the new commit. If you do this to point at the latest release
tags, this makes for less updates. Otherwise, you’ll want to figure out a
CI s
On Sun, 30 Aug 2020 at 15:01, Gary Gregory wrote:
>
> On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins wrote:
>
> >
> >
> > > On Aug 30, 2020, at 9:44 AM, sebb wrote:
> > >
> > > Some questions:
> > >
> > > - does it affect any existing usage?
> > > i.e. can people continue to use the individual re
23 matches
Mail list logo
