Hi,
Tested with a project with dependency to Bouncycastle signed jar - really
faster.
IMHO would be good to release 3.2 not 3.1.1
I don't agree here, cause only Bug fixing, some tasks fixed and
dependency upgrades...No real functionality enhancements...that I see...
Kind regards
Karl
Le samedi 29 décembre 2018, 11:29:53 CET Robert Scholte a écrit :
> I've already introduces the concept of "plans"[1][2], which also include
> 'site' for documentation and 'release' to verify if the project is
> releasable (should probably change that name to prevent confusion).
+1 to change the
On Sat 29 Dec 2018 at 16:20, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
>
> On Sat 29 Dec 2018 at 15:18, Enrico Olivelli wrote:
>
>> Il sab 29 dic 2018, 15:17 Stephen Connolly <
>> stephen.alan.conno...@gmail.com>
>> ha scritto:
>>
>> > There is a security issue with building
On Sat 29 Dec 2018 at 18:06, Vladimir Sitnikov
wrote:
> Stephen> Nah. Once committers have approved the PR then the PR can be
> merged by the
> Stephen> creator of the PR even if not a committer... at least that’s
> the default
> Stephen> way GitHub PRs work
>
> By default one needs push rights
Stephen> Well on other GitHub orgs i’ve seen PR author has Merge
button once PR is
Stephen> approved by someone with push rights to the repo... until
they add a commit
Stephen> or the merge result changes
It does not work the way you describe.
1) By default GitHub defaults to "Base permissions"
Le samedi 29 décembre 2018, 09:57:30 CET Mickael Istria a écrit :
> On Mon, Dec 24, 2018 at 5:21 PM Karl Heinz Marbaise
>
> wrote:
> > Hi Mickael,
>
> Hi,
>
> I have to summarize this simply.
>
> > This is no lack of interest in any kind. It is simply a lack of time of
> > the
Hi Enrico,
On 29/12/18 11:01, Enrico Olivelli wrote:
Hi,
We solved 17 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220=12341358=text
There are still a couple of issues left in JIRA:
Le samedi 29 décembre 2018, 12:37:36 CET Mickael Istria a écrit :
> On Sat, Dec 29, 2018 at 12:01 PM Hervé BOUTEMY
>
> wrote:
> > But in both cases, currently, there is no automatic GitHub PR integration:
> > Maven committers need to create a branch in the official repository to
> > benefit
> >
Hervè,
This is the plugin
https://wiki.jenkins.io/display/JENKINS/GitHub+Branch+Source+Plugin?desktop=true=unmigrated-inline-wiki-markup
I see our "maven-box" is using some special "Scan Apache Hosted Git
Folder Triggers" source
(https://builds.apache.org/job/maven-box/configure)
In the Jenkins
There is a security issue with building PRs automatically.
I can see about adding PR discovery to the existing ASF gitbox plugin, but
we’d need committers to ok the build and have reviewed the code as the PR
could contain attacks to be run from ASF hardware... which is why we don’t
build PRs at
Stephen> Nah. Once committers have approved the PR then the PR can be
merged by the
Stephen> creator of the PR even if not a committer... at least that’s
the default
Stephen> way GitHub PRs work
By default one needs push rights on the repository to merge PRs.
"Approval" changes nothing. "PR
Hi Enrico,
On 29/12/18 09:14, Enrico Olivelli wrote:
Hi guys,
I am trying to release Maven Assembly Plugin and I see that there are
a few showstoppers due to javadocs and site generation.
Can you report which one?
Isn't it possible to run "javadoc:javadoc site" on CI ?
This way we won't
Hi Enrico,
On 29/12/18 09:53, Enrico Olivelli wrote:
Karl,
Il giorno sab 29 dic 2018 alle ore 09:41 Karl Heinz Marbaise
ha scritto:
Hi Enrico,
On 29/12/18 09:14, Enrico Olivelli wrote:
Hi guys,
I am trying to release Maven Assembly Plugin and I see that there are
a few showstoppers due
Le samedi 29 décembre 2018, 12:40:20 CET Enrico Olivelli a écrit :
> Il sab 29 dic 2018, 12:37 Mickael Istria ha scritto:
> > On Sat, Dec 29, 2018 at 12:01 PM Hervé BOUTEMY
> >
> > wrote:
> > > But in both cases, currently, there is no automatic GitHub PR
> >
> > integration:
> > > Maven
On Sat 29 Dec 2018 at 17:16, Enrico Olivelli wrote:
> Il sab 29 dic 2018, 17:25 Stephen Connolly <
> stephen.alan.conno...@gmail.com>
> ha scritto:
>
> > On Sat 29 Dec 2018 at 16:20, Stephen Connolly <
> > stephen.alan.conno...@gmail.com> wrote:
> >
> > >
> > >
> > > On Sat 29 Dec 2018 at 15:18,
On Sat 29 Dec 2018 at 18:19, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
>
> On Sat 29 Dec 2018 at 18:06, Vladimir Sitnikov <
> sitnikov.vladi...@gmail.com> wrote:
>
>> Stephen> Nah. Once committers have approved the PR then the PR can be
>> merged by the
>> Stephen> creator of
Hi,
also my +1
Tested with a project with dependency to Bouncycastle signed jar - really
faster.
IMHO would be good to release 3.2 not 3.1.1
BR
Sylwester
sob., 29 gru 2018 o 11:01 Enrico Olivelli napisał(a):
> Hi,
>
> We solved 17 issues:
>
>
Karl,
Il giorno sab 29 dic 2018 alle ore 09:41 Karl Heinz Marbaise
ha scritto:
>
> Hi Enrico,
>
> On 29/12/18 09:14, Enrico Olivelli wrote:
> > Hi guys,
> > I am trying to release Maven Assembly Plugin and I see that there are
> > a few showstoppers due to javadocs and site generation.
>
>
>
I've already introduces the concept of "plans"[1][2], which also include
'site' for documentation and 'release' to verify if the project is
releasable (should probably change that name to prevent confusion).
The jobs are getting more stable, so we might give it a try soon. Just
need to be
Il sab 29 dic 2018, 12:19 Karl Heinz Marbaise ha
scritto:
> Hi Mickael,
>
> On 29/12/18 09:57, Mickael Istria wrote:
> > On Mon, Dec 24, 2018 at 5:21 PM Karl Heinz Marbaise
> > wrote:
> >
> >> Hi Mickael,
> >>
> >
> > Hi,
> >
> > I have to summarize this simply.
> >
> > I was confused about how
Hi,
On 29/12/18 18:16, Enrico Olivelli wrote:
Il sab 29 dic 2018, 17:25 Stephen Connolly
ha scritto:
On Sat 29 Dec 2018 at 16:20, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
On Sat 29 Dec 2018 at 15:18, Enrico Olivelli
wrote:
Il sab 29 dic 2018, 15:17 Stephen Connolly
On Mon, Dec 24, 2018 at 5:21 PM Karl Heinz Marbaise
wrote:
> Hi Mickael,
>
Hi,
I have to summarize this simply.
> This is no lack of interest in any kind. It is simply a lack of time of
> the committers...cause there is very limited number of committers...
>
I understand that, and I hope I
The Apache Maven team is pleased to announce the release of the
Apache Maven Shared Component: Maven Dependency Analyzer Version 1.11.1
https://maven.apache.org/shared/maven-dependency-analzyer/
You should specify the version in your project:
org.apache.maven.shared
Il sab 29 dic 2018, 15:17 Stephen Connolly
ha scritto:
> There is a security issue with building PRs automatically.
>
> I can see about adding PR discovery to the existing ASF gitbox plugin, but
> we’d need committers to ok the build and have reviewed the code as the PR
> could contain attacks
Hi,
We solved 17 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220=12341358=text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MASSEMBLY%20AND%20status%20%3D%20Open
Staging repo:
Hi Mickael,
On 29/12/18 09:57, Mickael Istria wrote:
On Mon, Dec 24, 2018 at 5:21 PM Karl Heinz Marbaise
wrote:
Hi Mickael,
Hi,
I have to summarize this simply.
I was confused about how automated tests are running or not. If I look at
https://github.com/apache/maven/pull/194 , I do not
Il sab 29 dic 2018, 12:37 Mickael Istria ha scritto:
> On Sat, Dec 29, 2018 at 12:01 PM Hervé BOUTEMY
> wrote:
>
> > But in both cases, currently, there is no automatic GitHub PR
> integration:
> > Maven committers need to create a branch in the official repository to
> > benefit
> > from ASF
On Sat 29 Dec 2018 at 15:18, Enrico Olivelli wrote:
> Il sab 29 dic 2018, 15:17 Stephen Connolly <
> stephen.alan.conno...@gmail.com>
> ha scritto:
>
> > There is a security issue with building PRs automatically.
> >
> > I can see about adding PR discovery to the existing ASF gitbox plugin,
>
Il sab 29 dic 2018, 17:25 Stephen Connolly
ha scritto:
> On Sat 29 Dec 2018 at 16:20, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> >
> >
> > On Sat 29 Dec 2018 at 15:18, Enrico Olivelli
> wrote:
> >
> >> Il sab 29 dic 2018, 15:17 Stephen Connolly <
> >>
Hi,
here is my +1
Checked on Mac OS / JDK 11 / Maven 3.6.0 without any issue.
Kind regards
Karl Heinz Marbaise
On 29/12/18 11:01, Enrico Olivelli wrote:
Hi,
We solved 17 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220=12341358=text
There are still a
Hi,
here is my +1
Kind regards
Karl Heinz Marbaise
On 25/12/18 23:28, Karl Heinz Marbaise wrote:
Hi,
We solved 1 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12344667
There are still a couple of issues left in JIRA:
Hi,
The vote has passed with the following result:
+1 : Mark Raynsford, Vidar Breivik, Tibor Digana, Sylwester Lachieweicz,
Hervé Boutemy, Olivier Lamy, Karl Heinz Marbaise
PMC quorum: reached
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
On Sat, Dec 29, 2018 at 12:01 PM Hervé BOUTEMY
wrote:
> But in both cases, currently, there is no automatic GitHub PR integration:
> Maven committers need to create a branch in the official repository to
> benefit
> from ASF Jenkins build
>
Ah ok, I wasn't aware the GitHub repo was "unofficial"
Karl Heinz Marbaise > The user community is very big but unfortunately the
people who are
Karl Heinz Marbaise > willing to help is not that big...
Can I (ab)use the thread a bit?
One of the issues I run into with Maven is "it takes ages for repeated
build when nothing has changed".
Of course
Stephen > Are you sure?
I've just created a dummy account and "approval" does not make merge button
magically appear.
If you have a couple of minutes, please make a PR (I'll approve it shortly)
to https://github.com/vlsi/KE-complex_modifications
Note: you can click "edit" button in GitHub UI for
On 2018-12-29T21:04:33 +0100
Karl Heinz Marbaise wrote:
> Hi to all,
>
> I want to cut a Core Release within two weeks (about 14.01.2019) if that
> is Ok for everyone? If any objections please raise your hand.
One for Hervé: Where did we leave things with MNG-6059? I ran into that
issue a
Hi everyone,
I was doing some work on maven-release and I ran 'mvn clean install site'
on it (as I usually do), and the build fails with a velocity parsing error.
The fix was simple: upgrade fluido-skins from 1.3.1 to 1.7 in site.xml.
Looking at the jenkins build jobs, it looks like the site
I'mglad to see that PR build/merge discussed, it seems to have a good
potential value for many in simplifying it.
FWIW, at Eclipse Foundation, similar questions were faced and risks
identified. The result is that at the moment, all PRs from anyone can be
built on Eclipse infra without much
Hi Everyone,
I've finally managed to get back to some maven dev work! :)
In looking through the pom's I can see that some of the links for Jira and
Jenkins are broken.
Have the jenkins servers and jobs finally established a final URL?
For example, the maven-release plugin:
current git value:
Hi to all,
I want to cut a Core Release within two weeks (about 14.01.2019) if that
is Ok for everyone? If any objections please raise your hand.
currently I see in the JIRA the following issues open:
MNG-6530[1] which should be part of it (critical!)
MNG-6533[2]
MNG-6538[3] Upgrade to Maven
On Saturday, December 29, 2018, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
> I think we could easily use TravisCI or one of the cloud CI vendors to
> perform trial builds of PRs on GitHub.
Good. So at this point, it's only a matter of writing a .travis.yaml file
in the repo, or
> And, again, TravisCI also does the same in a decent way, with the benefit
> of worrying less about underlying infra and security, and only drawback of
> being discoupled from a specific infra (is it really a drawback?)
Just in case: Apache Calcite uses both Travis CI and AppVeryor. It just
On Sat, 29 Dec 2018 at 18:56, Vladimir Sitnikov
wrote:
> Stephen> Well on other GitHub orgs i’ve seen PR author has Merge
> button once PR is
> Stephen> approved by someone with push rights to the repo... until
> they add a commit
> Stephen> or the merge result changes
>
> It does not work the
Am 2018-12-27 um 23:21 schrieb Michael Osipov:
Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12344436
There are still a couple of issues left in JIRA:
On Sat, 29 Dec 2018 at 20:41, Mickael Istria wrote:
> I'mglad to see that PR build/merge discussed, it seems to have a good
> potential value for many in simplifying it.
>
> FWIW, at Eclipse Foundation, similar questions were faced and risks
> identified. The result is that at the moment, all
Hi guys,
I am trying to release Maven Assembly Plugin and I see that there are
a few showstoppers due to javadocs and site generation.
Isn't it possible to run "javadoc:javadoc site" on CI ?
This way we won't commit broken/unreleasable stuff
Enrico
46 matches
Mail list logo
