Re: Important Notice for all users of the parallel build feature

[Maxim Solodovnik]

Is it possible to include this jar to maven distribution? Because it is not
always possible to change it on build servers .

On 19 October 2014 01:22, Kristian Rosenvold kristian.rosenv...@gmail.com
wrote:

 Thanks to an excellent testcase provided by a JIRA user, a significant
 source of thread safety bugs has been located and fixed. The problem
 has an extensive reach, and can be the source of practically *any*
 issue in parallel builds, and is probably the root cause of most JIRA
 issues filed wrt parallel build problems.

 Fortunately, there is a very simple fix by putting the following
 inside your plugin configuration:

 plugin
   ...
   dependencies
 dependency
   groupIdorg.codehaus.plexus/groupId
   artifactIdplexus-interpolation/artifactId
   version1.21/version
 /dependency
   /dependencies
 /plugin


 You should also put this jar file in the lib/ext folder of your maven
 installation:


 http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-interpolation/1.21/plexus-interpolation-1.21.jar


 Which plugins are affected ? It's almost easier to tell which is /not/
 affected. See the relates link on
 https://jira.codehaus.org/browse/PLXCOMP-258 to see which
 plugins/tools are affected.

 Kristian

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




-- 
WBR
Maxim aka solomax

Re: [VOTE] Change project logo and adopt owl as mascot

[Maxim Solodovnik]

+1

WBR, Maxim
(from mobile, sorry for the typos)
On Nov 25, 2014 5:31 PM, domi d...@fortysix.ch wrote:

 +1

 On 25.11.2014, at 11:57, Stephen Connolly stephen.alan.conno...@gmail.com
 wrote:

 


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

Re: [ANN] Apache Maven SCM Version 1.9.4 Released

[Maxim Solodovnik]

yfv ,jhtw yt ye;ty

On Thu, Apr 2, 2015 at 12:39 PM, Karl Heinz Marbaise khmarba...@apache.org
wrote:

 The Apache Maven team is pleased to announce the release of the
 Apache Maven SCM, version 1.9.4

 Maven SCM supports Maven 2.x plugins (e.g. maven-release-plugin) and other
 tools (e.g. Continuum) by providing them with a common API for doing SCM
 operations.

 http://maven.apache.org/scm/

 Release Notes - Maven SCM - Version 1.9.4

 Bugs:

  * [SCM-764] - username and credentials shown as INFO on commadline
  * [SCM-780] - Duplicate connection url's properties
  * [SCM-786] - Missing dependency on JUnit

 Improvements:

  * [SCM-778] - Upgrade junit and hamcrest
  * [SCM-793] - Upgrade maven-modello-plugin to 1.8.2
  * [SCM-794] - Configure maven release plugin to autoVersionSubmodules

 Task:

  * [SCM-789] - Upgrade to maven-parent version 26

 Wish:

  * [SCM-785] - Upgrade Plugin Required Maven Version to 2.2.1


 Enjoy,

 -The Apache Maven team

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




-- 
WBR
Maxim aka solomax

Re: [ANN] Apache Maven SCM Version 1.9.4 Released

[Maxim Solodovnik]

sorry for crappy message :(

On Thu, Apr 2, 2015 at 12:55 PM, Maxim Solodovnik solomax...@gmail.com
wrote:

 yfv ,jhtw yt ye;ty

 On Thu, Apr 2, 2015 at 12:39 PM, Karl Heinz Marbaise 
 khmarba...@apache.org wrote:

 The Apache Maven team is pleased to announce the release of the
 Apache Maven SCM, version 1.9.4

 Maven SCM supports Maven 2.x plugins (e.g. maven-release-plugin) and other
 tools (e.g. Continuum) by providing them with a common API for doing SCM
 operations.

 http://maven.apache.org/scm/

 Release Notes - Maven SCM - Version 1.9.4

 Bugs:

  * [SCM-764] - username and credentials shown as INFO on commadline
  * [SCM-780] - Duplicate connection url's properties
  * [SCM-786] - Missing dependency on JUnit

 Improvements:

  * [SCM-778] - Upgrade junit and hamcrest
  * [SCM-793] - Upgrade maven-modello-plugin to 1.8.2
  * [SCM-794] - Configure maven release plugin to autoVersionSubmodules

 Task:

  * [SCM-789] - Upgrade to maven-parent version 26

 Wish:

  * [SCM-785] - Upgrade Plugin Required Maven Version to 2.2.1


 Enjoy,

 -The Apache Maven team

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




 --
 WBR
 Maxim aka solomax




-- 
WBR
Maxim aka solomax

Re: Java 7 and 8 features

[Maxim Solodovnik]

We are just moved to java7 and start using new features
I personally don't like the idea of moving all code to new java, I move the
areas I currently work on

On Tue, Oct 27, 2015 at 10:57 PM, Gary Gregory 
wrote:

> Hi,
>
> What I see, is that most projects are struggling to move to Java 7, Java 8
> seems out of range. There are a lot of opinions and both sides of each Java
> version for and against. At the end of the day, it's about user feedback
> and committer community involvement. The projects I help on also lack
> manpower and maintaining more than one version is not I see folks wanting
> to do. For myself, I usually want to work on the current version in
> master/trunk and move that along. My work$ development is on Java 7 and
> slated to switch to Java 8 in 2016 I would guess.
>
> Gary
>
> On Tue, Oct 27, 2015 at 9:37 AM, Oliver B. Fischer <
> o.b.fisc...@swe-blog.net> wrote:
>
>> Hi Vinicius,
>>
>> it is mostly to allow people which are bound (for any reason) to older
>> JDK versions to use our software. There is a plenty number of projects
>> which are not able to use newer JDK versions. I know that this is a
>>  controversial topic I think that the majority of us would like to use all
>> these features. But we must not forget the people using our software in
>> their daily work.
>>
>> BYe,
>>
>> Oliver
>>
>> Am 27.10.15 um 16:49 schrieb Vinicius Corrêa de Almeida:
>>
>>> I analized some releases and i noticed that not using java 7 features
>>> like
>>> multi catch and in java 8 do not use lambda expressions and others
>>> features, so i came by this email to know why the developers not using
>>> this
>>> features?
>>>
>>>
>> --
>> N Oliver B. Fischer
>> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
>> P +49 30 44793251
>> M +49 178 7903538
>> E o.b.fisc...@swe-blog.net
>> S oliver.b.fischer
>> J oliver.b.fisc...@jabber.org
>> X http://xing.to/obf
>>
>>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
WBR
Maxim aka solomax

Re: Maven plugin for code signing @Apache

[Maxim Solodovnik]

Hello Hervé,

We are using "ASF key" to sign our webstart application, this way it is
started without error in modern Java
Currently we are using lots of manual steps to sign necessary jars using
ASF service
I thought maybe Maven can do it on my behalf :)

On Sun, Oct 18, 2015 at 12:14 PM, Hervé BOUTEMY <herve.bout...@free.fr>
wrote:

> Hi,
>
> Perhaps the "code signing" feature for jars should be explained, since we
> already have maven-gpg-plugin [1] to sign code, that is used for years with
> great success.
>
> From what I read on ASF signing, it adds a feature for Windows executables,
> that is checked by the OS at runtime and displayed to end-users.
>
> For jars, I don't see what we get better than gpg.
> What I suppose is that if a plugin is done, it will be an Apache-specific
> plugin: not same interest than doing a plugin for general public use.
>
> What do you expect from this signing feature for jars?
>
> Regards,
>
> Hervé
>
> [1] http://maven.apache.org/plugins/maven-gpg-plugin/
>
> Le jeudi 8 octobre 2015 12:26:57 Maxim Solodovnik a écrit :
> > Hello All,
> >
> > More than a year ago INFRA announce availability of code signing at
> Apache:
> > https://blogs.apache.org/infra/entry/code_signing_service_now_available
> >
> > but still there is no maven plugin for doing that :(
> > I never wrote maven plugins and need more time to write "Hello world"
> level
> > plugins before I can fix/create anything :)
> >
> > Maybe anyone is interested to write maven plugin so code can be signed at
> > Apache? :)
> >
> > Thanks in advance!
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
WBR
Maxim aka solomax

Re: Maven plugin for code signing @Apache

[Maxim Solodovnik]

Now I'm a little bit scared :)
Our release process is documented here [1]
part "Step3 - Sign web start application" describes the current process of
signing jar files. (all current stable releases uses ant, dev releases are
using maven)


[1] http://openmeetings.apache.org/ReleaseGuide.html

On Mon, Oct 19, 2015 at 4:58 PM, Tibor Digana <tibor.dig...@googlemail.com>
wrote:

> As I am reading your discussion, I am a little bit scared.
> Maxim you use your own ASK key?
>
> On Mon, Oct 19, 2015 at 8:02 AM, Maxim Solodovnik <solomax...@gmail.com>
> wrote:
>
> > Hello Hervé,
> >
> > We are using "ASF key" to sign our webstart application, this way it is
> > started without error in modern Java
> > Currently we are using lots of manual steps to sign necessary jars using
> > ASF service
> > I thought maybe Maven can do it on my behalf :)
> >
> > On Sun, Oct 18, 2015 at 12:14 PM, Hervé BOUTEMY <herve.bout...@free.fr>
> > wrote:
> >
> > > Hi,
> > >
> > > Perhaps the "code signing" feature for jars should be explained, since
> we
> > > already have maven-gpg-plugin [1] to sign code, that is used for years
> > with
> > > great success.
> > >
> > > From what I read on ASF signing, it adds a feature for Windows
> > executables,
> > > that is checked by the OS at runtime and displayed to end-users.
> > >
> > > For jars, I don't see what we get better than gpg.
> > > What I suppose is that if a plugin is done, it will be an
> Apache-specific
> > > plugin: not same interest than doing a plugin for general public use.
> > >
> > > What do you expect from this signing feature for jars?
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1] http://maven.apache.org/plugins/maven-gpg-plugin/
> > >
> > > Le jeudi 8 octobre 2015 12:26:57 Maxim Solodovnik a écrit :
> > > > Hello All,
> > > >
> > > > More than a year ago INFRA announce availability of code signing at
> > > Apache:
> > > >
> > https://blogs.apache.org/infra/entry/code_signing_service_now_available
> > > >
> > > > but still there is no maven plugin for doing that :(
> > > > I never wrote maven plugins and need more time to write "Hello world"
> > > level
> > > > plugins before I can fix/create anything :)
> > > >
> > > > Maybe anyone is interested to write maven plugin so code can be
> signed
> > at
> > > > Apache? :)
> > > >
> > > > Thanks in advance!
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>
>
>
> --
> Cheers
> Tibor
>



-- 
WBR
Maxim aka solomax

Maven plugin for code signing @Apache

[Maxim Solodovnik]

Hello All,

More than a year ago INFRA announce availability of code signing at Apache:
https://blogs.apache.org/infra/entry/code_signing_service_now_available

but still there is no maven plugin for doing that :(
I never wrote maven plugins and need more time to write "Hello world" level
plugins before I can fix/create anything :)

Maybe anyone is interested to write maven plugin so code can be signed at
Apache? :)

Thanks in advance!

-- 
WBR
Maxim aka solomax

Re: Maven plugin for code signing @Apache

[Maxim Solodovnik]

Thanks for the quick answer :)
You can contact INFRA on hipchat http://infra.chat/ to get test environment
for plugin :)

On Thu, Oct 8, 2015 at 12:32 PM, <e...@zusammenkunft.net> wrote:

> Hello,
>
> I think we have a plugin based on Eclipse sign infrastructure code in my
> company, I will check how custom it is an how the licensing looks like.
>
> [Sometimes I think a JCE/PkCS11 based solution (using ordinary jar signer)
> has (besides the missing mandatory archiving) its merits. This does work
> with hardware tokens installed in CI servers.]
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
>
> -Original Message-
> From: Maxim Solodovnik <solomax...@gmail.com>
> To: Maven Developers List <dev@maven.apache.org>
> Sent: Do., 08 Okt. 2015 8:26
> Subject: Maven plugin for code signing @Apache
>
> Hello All,
>
> More than a year ago INFRA announce availability of code signing at Apache:
> https://blogs.apache.org/infra/entry/code_signing_service_now_available
>
> but still there is no maven plugin for doing that :(
> I never wrote maven plugins and need more time to write "Hello world" level
> plugins before I can fix/create anything :)
>
> Maybe anyone is interested to write maven plugin so code can be signed at
> Apache? :)
>
> Thanks in advance!
>
> --
> WBR
> Maxim aka solomax
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
WBR
Maxim aka solomax

Re: Maven plugin for code signing @Apache

[Maxim Solodovnik]

OK thanks

On Mon, Oct 19, 2015 at 8:36 PM, Tibor Digana <tibordig...@apache.org>
wrote:

> csportal is not available for me, but these are two different things of
> signing. The gpg creates extra signature file, but webstart as typical
> webstart jar I know needs DSA or RSA signature inside jar file which can be
> accomplished by maven-jarsigner-plugin
> https://maven.apache.org/plugins/maven-jarsigner-plugin/usage.html
> You could open discussion in Users group.
>
> On Mon, Oct 19, 2015 at 1:14 PM, Maxim Solodovnik [via Maven] <
> ml-node+s40175n5849695...@n5.nabble.com> wrote:
>
> > Now I'm a little bit scared :)
> > Our release process is documented here [1]
> > part "Step3 - Sign web start application" describes the current process
> of
> > signing jar files. (all current stable releases uses ant, dev releases
> are
> > using maven)
> >
> >
> > [1] http://openmeetings.apache.org/ReleaseGuide.html
> >
> > On Mon, Oct 19, 2015 at 4:58 PM, Tibor Digana <[hidden email]
> > <http:///user/SendEmail.jtp?type=node=5849695=0>>
> > wrote:
> >
> > > As I am reading your discussion, I am a little bit scared.
> > > Maxim you use your own ASK key?
> > >
> > > On Mon, Oct 19, 2015 at 8:02 AM, Maxim Solodovnik <[hidden email]
> > <http:///user/SendEmail.jtp?type=node=5849695=1>>
> > > wrote:
> > >
> > > > Hello Hervé,
> > > >
> > > > We are using "ASF key" to sign our webstart application, this way it
> > is
> > > > started without error in modern Java
> > > > Currently we are using lots of manual steps to sign necessary jars
> > using
> > > > ASF service
> > > > I thought maybe Maven can do it on my behalf :)
> > > >
> > > > On Sun, Oct 18, 2015 at 12:14 PM, Hervé BOUTEMY <[hidden email]
> > <http:///user/SendEmail.jtp?type=node=5849695=2>>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > Perhaps the "code signing" feature for jars should be explained,
> > since
> > > we
> > > > > already have maven-gpg-plugin [1] to sign code, that is used for
> > years
> > > > with
> > > > > great success.
> > > > >
> > > > > From what I read on ASF signing, it adds a feature for Windows
> > > > executables,
> > > > > that is checked by the OS at runtime and displayed to end-users.
> > > > >
> > > > > For jars, I don't see what we get better than gpg.
> > > > > What I suppose is that if a plugin is done, it will be an
> > > Apache-specific
> > > > > plugin: not same interest than doing a plugin for general public
> > use.
> > > > >
> > > > > What do you expect from this signing feature for jars?
> > > > >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > > [1] http://maven.apache.org/plugins/maven-gpg-plugin/
> > > > >
> > > > > Le jeudi 8 octobre 2015 12:26:57 Maxim Solodovnik a écrit :
> > > > > > Hello All,
> > > > > >
> > > > > > More than a year ago INFRA announce availability of code signing
> > at
> > > > > Apache:
> > > > > >
> > > >
> > https://blogs.apache.org/infra/entry/code_signing_service_now_available
> > > > > >
> > > > > > but still there is no maven plugin for doing that :(
> > > > > > I never wrote maven plugins and need more time to write "Hello
> > world"
> > > > > level
> > > > > > plugins before I can fix/create anything :)
> > > > > >
> > > > > > Maybe anyone is interested to write maven plugin so code can be
> > > signed
> > > > at
> > > > > > Apache? :)
> > > > > >
> > > > > > Thanks in advance!
> > > > >
> > > > >
> > > > >
> > -
> > > > > To unsubscribe, e-mail: [hidden email]
> > <http:///user/SendEmail.jtp?type=node=5849695=3>
> > > > > For additional commands, e-mail: [hidden email]
> > <http:///user/SendEmail.jtp?type=node=5849695=4>
> > > > >
> > > > >
> > > >
> 

Re: [ANN] Apache Maven Version 3.3.9 Released

[Maxim Solodovnik]

it seems not all mirrors are ready for the update :(
this one
http://apache-mirror.rbc.ru/pub/apache/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz
gaves 404

On Wed, Nov 18, 2015 at 1:26 PM, Tony Chemit  wrote:

> On Wed, 18 Nov 2015 07:11:17 + (UTC)
> khmarba...@apache.org (Karl Heinz Marbaise) wrote:
>
> > The Apache Maven team is pleased to announce the release of
> > Apache Maven 3.3.9.
> >
> > http://maven.apache.org/
> >
> > You can download the appropriate sources etc. from the download page
> >
> > http://maven.apache.org/download.cgi
> >
> Hi,
>
> Good job for this new version, many thanks for it.
>
> The download page points to the 3.3.3 version!
>
> --
> Tony Chemit
> 
> tél: +33 (0) 2 40 50 29 28
> http://www.codelutin.com
> email: che...@codelutin.com
> twitter: https://twitter.com/tchemit
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
WBR
Maxim aka solomax

Re: [ANN] Apache Maven Version 3.3.9 Released

[Maxim Solodovnik]

Everything works as expected now :)

On Wed, Nov 18, 2015 at 11:16 PM, Karl Heinz Marbaise <khmarba...@gmx.de>
wrote:

> Hi,
>
> On 11/18/15 10:12 AM, Maxim Solodovnik wrote:
>
>> it seems not all mirrors are ready for the update :(
>> this one
>>
>> http://apache-mirror.rbc.ru/pub/apache/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz
>> gaves 404
>>
>
> I'm the culprit...I was not patient enough to wait for the sync...
> Sorry...
>
> Kind regards
> Karl Heinz Marbaise
>
>>
>> On Wed, Nov 18, 2015 at 1:26 PM, Tony Chemit <che...@codelutin.com>
>> wrote:
>>
>> On Wed, 18 Nov 2015 07:11:17 + (UTC)
>>> khmarba...@apache.org (Karl Heinz Marbaise) wrote:
>>>
>>> The Apache Maven team is pleased to announce the release of
>>>> Apache Maven 3.3.9.
>>>>
>>>> http://maven.apache.org/
>>>>
>>>> You can download the appropriate sources etc. from the download page
>>>>
>>>> http://maven.apache.org/download.cgi
>>>>
>>>> Hi,
>>>
>>> Good job for this new version, many thanks for it.
>>>
>>> The download page points to the 3.3.3 version!
>>>
>>> --
>>>
>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
WBR
Maxim aka solomax

Re: Apache OpenMeetings build fails on Maven 3.4-SNAPSHOT

[Maxim Solodovnik]

I'll keep this email and will double-check everything after 3.4 will be
released

On Mon, Sep 5, 2016 at 10:25 PM, Christian Schulte <c...@schulte.it> wrote:

> Am 09/05/16 um 16:48 schrieb Maxim Solodovnik:
> > I have merged your PR, Thanks! :))
>
> I cannot tell in what version this has stopped working. It will be
> working again in 3.4+. Maybe that PR isn't correct and the old behaviour
> really was intended years ago.
>
> Regards,
> --
> Christian
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
WBR
Maxim aka solomax

Re: Apache OpenMeetings build fails on Maven 3.4-SNAPSHOT

[Maxim Solodovnik]

I'm afraid I need to revert these changes
Without true I have duplicate jar files and weird
classloader issues while running OM
I'll check/fix it as soon as Maven 3.4 will be released and we will switch
to it

On Mon, Sep 5, 2016 at 10:46 PM, Behrooz Nobakht <nob...@gmail.com> wrote:

> Thanks, Christian. Is there a Maven ticket for this?
>
> On Mon, Sep 5, 2016 at 5:30 PM, Maxim Solodovnik <solomax...@gmail.com>
> wrote:
>
> > I'll keep this email and will double-check everything after 3.4 will be
> > released
> >
> > On Mon, Sep 5, 2016 at 10:25 PM, Christian Schulte <c...@schulte.it>
> wrote:
> >
> > > Am 09/05/16 um 16:48 schrieb Maxim Solodovnik:
> > > > I have merged your PR, Thanks! :))
> > >
> > > I cannot tell in what version this has stopped working. It will be
> > > working again in 3.4+. Maybe that PR isn't correct and the old
> behaviour
> > > really was intended years ago.
> > >
> > > Regards,
> > > --
> > > Christian
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>
>
>
> --
> -- Behrooz Nobakht
>



-- 
WBR
Maxim aka solomax

Re: Apache OpenMeetings build fails on Maven 3.4-SNAPSHOT

[Maxim Solodovnik]

I have merged your PR, Thanks! :))

On Mon, Sep 5, 2016 at 9:24 PM, Christian Schulte  wrote:

> 
>
> Am 09/05/16 um 14:39 schrieb Behrooz Nobakht:
> > Hi there,
> >
> > Trying to build Apache OpenMeetings with Apache Maven 3.4-SNAPSHOT[1]
> fails
> > with "Compilation failure" all with "package org.red5.x does not exist".
> >
> > The build is run on the trunk[2] with:
> >
> > ```
> > $ mvn -X clean install -l /tmp/om-mvn.log -PallModules
> > -Dmaven.buildNumber.skip=true
> > ```
> >
> > The same build with Maven 3.3.9 works fine.
> >
> > Hope this could be a feedback for both teams as I could not figure out
> what
> > specifically goes wrong during the build.
> >
> > The complete log is attached.
> >
> > Regards,
> > Behrooz
> >
> >
> > [1]: https://builds.apache.org/view/M-R/view/Maven/job/maven-
> 3.x/lastSuccessfulBuild/artifact/apache-maven/target/
> apache-maven-3.4.0-SNAPSHOT-bin.tar.gz
> > [2]: https://github.com/apache/openmeetings/tree/trunk
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
WBR
Maxim aka solomax

Re: Maven Site / Report Plugins

[Maxim Solodovnik]

Hello Karl,

I guess you can "skip" report for subproject?

On Mon, Mar 20, 2017 at 1:48 PM, Karl Heinz Marbaise  wrote:
> Hi Hervé,
>
> On 19/03/17 23:39, Hervé BOUTEMY wrote:
>>
>> That's the first time I see this part of the doc: defining an empty
>> reportSet
>> could remove a report plugin? I'm not convinced it ever worked.
>
>
> Me neither and made the experience that this will not work.
>
> But in the end this means a report can not being turned off in a sub
> project...which in contradiction is possible with plugins..
>
> So the question is: Should that be possible ?
>
> Kind regards
> Karl Heinz Marbaise
>
>
>>
>> to me, it is inconsistent with following documentation, associated to an
>> IT:
>> http://maven.apache.org/plugins/maven-site-plugin/
>> maven-3.html#Inheritance_of_reports_for_Maven_3_before_3.0.4
>>
>> Reports are additive: they were not in Maven 3.0 to 3.0.3, and it was
>> identified as a bug.
>>
>> Regards,
>>
>> Hervé
>>
>> Le dimanche 19 mars 2017, 11:28:06 CET Karl Heinz Marbaise a écrit :
>>>
>>> Hi,
>>>
>>> currently I stumbled over a thing which I don't understand.
>>>
>>> I have parent pom[1] which defines several parts of a site including
>>> some reports for example maven-changes-plugin with github-report..
>>>
>>> Now I inherit from that parent pom and of course I can do a mvn site.
>>>
>>> But now the important part.
>>>
>>> I would like to deactive maven-changes-plugin in particular
>>> github-report...cause this test project does not has a github repo which
>>> will fail the mvn site build..
>>>
>>> I have taken a look into the documentation[2] to find a way to deactive
>>> github-report or maven-changes-plugin at all...I tried to change
>>> maven-project-info-reports parts etc. but without any luck..
>>>
>>> Does someone has a good hint how to do this ?
>>>
>>> Kind regards
>>> Karl Heinz Marbaise
>>>
>>> [1]: https://github.com/khmarbaise/smpp/blob/master/pom.xml
>>> [2]: http://maven.apache.org/pom.html#Reporting
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
WBR
Maxim aka solomax

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Site / Report Plugins

[Maxim Solodovnik]

then maybe copy/paste a little:

configure all necessary reports in parent pom (exclude github-report)
Then add github-report to all child projects except one

On Mon, Mar 20, 2017 at 2:19 PM, Karl Heinz Marbaise <khmarba...@gmx.de> wrote:
> Hi,
>
>
> On 20/03/17 07:54, Maxim Solodovnik wrote:
>>
>> Hello Karl,
>>
>> I guess you can "skip" report for subproject?
>
>
> In this case this is not possible cause I want to have the site except for
> the maven-changes-plugin ...(github-report cause I don't have a github
> project for it).
>
> Kind regards
> Karl Heinz Marbaise
>>
>>
>> On Mon, Mar 20, 2017 at 1:48 PM, Karl Heinz Marbaise <khmarba...@gmx.de>
>> wrote:
>>>
>>> Hi Hervé,
>>>
>>> On 19/03/17 23:39, Hervé BOUTEMY wrote:
>>>>
>>>>
>>>> That's the first time I see this part of the doc: defining an empty
>>>> reportSet
>>>> could remove a report plugin? I'm not convinced it ever worked.
>>>
>>>
>>>
>>> Me neither and made the experience that this will not work.
>>>
>>> But in the end this means a report can not being turned off in a sub
>>> project...which in contradiction is possible with plugins..
>>>
>>> So the question is: Should that be possible ?
>>>
>>> Kind regards
>>> Karl Heinz Marbaise
>>>
>>>
>>>>
>>>> to me, it is inconsistent with following documentation, associated to an
>>>> IT:
>>>> http://maven.apache.org/plugins/maven-site-plugin/
>>>> maven-3.html#Inheritance_of_reports_for_Maven_3_before_3.0.4
>>>>
>>>> Reports are additive: they were not in Maven 3.0 to 3.0.3, and it was
>>>> identified as a bug.
>>>>
>>>> Regards,
>>>>
>>>> Hervé
>>>>
>>>> Le dimanche 19 mars 2017, 11:28:06 CET Karl Heinz Marbaise a écrit :
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> currently I stumbled over a thing which I don't understand.
>>>>>
>>>>> I have parent pom[1] which defines several parts of a site including
>>>>> some reports for example maven-changes-plugin with github-report..
>>>>>
>>>>> Now I inherit from that parent pom and of course I can do a mvn site.
>>>>>
>>>>> But now the important part.
>>>>>
>>>>> I would like to deactive maven-changes-plugin in particular
>>>>> github-report...cause this test project does not has a github repo
>>>>> which
>>>>> will fail the mvn site build..
>>>>>
>>>>> I have taken a look into the documentation[2] to find a way to deactive
>>>>> github-report or maven-changes-plugin at all...I tried to change
>>>>> maven-project-info-reports parts etc. but without any luck..
>>>>>
>>>>> Does someone has a good hint how to do this ?
>>>>>
>>>>> Kind regards
>>>>> Karl Heinz Marbaise
>>>>>
>>>>> [1]: https://github.com/khmarbaise/smpp/blob/master/pom.xml
>>>>> [2]: http://maven.apache.org/pom.html#Reporting
>>>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>
>>
>>
>



-- 
WBR
Maxim aka solomax

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Access Rights

[Maxim Solodovnik]

Maybe you can provide PR (no additional rights are required in this case)?

On Fri, May 25, 2018 at 4:57 PM, Petar Tahchiev  wrote:
> Hi guys,
>
> I just noted the maven archetype repository is now on github:
>
> https://github.com/apache/maven-archetype
>
> I was working on a fix for:
> https://issues.apache.org/jira/browse/ARCHETYPE-530 but I can't push my
> changes. Do you know who should I talk to, in order to get access rights
> (my github username is ptahchiev)?
>
> --
> Regards, Petar!
> Karlovo, Bulgaria.
> ---
> Public PGP Key at:
> http://pgp.mit.edu:11371/pks/lookup?op=get=0x19658550C3110611
> Key Fingerprint: A369 A7EE 61BC 93A3 CDFF  55A5 1965 8550 C311 0611



-- 
WBR
Maxim aka solomax

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Docker Images

[Maxim Solodovnik]

Hello,

here is the place for Apache docker images managed by infra and Apache
projects https://bintray.com/apache/ :)

On Fri, Oct 20, 2017 at 12:30 AM, Hervé BOUTEMY 
wrote:

> great idea
>
> ok, we need a git repo at ASF
>
> what else?
> Is there some sort of release process? some sort of source to release?
>
> Regards,
>
> Hervé
>
> Le jeudi 19 octobre 2017, 13:47:45 CEST Mike Drob a écrit :
> > Thanks for the pointer, Carlos! I had searched the archives, but maybe I
> > didn't go back far enough.
> >
> > I think moving these Dockerfiles into an ASF repo would be great for
> their
> > maintainability.
> >
> > Thanks,
> >
> > Mike
> >
> > On 2017-10-19 03:50, Carlos Sanchez  wrote:
> > > Arnaud is correct, I sent an email to users@ back on Fri, Nov 7,
> 2014,>
> > > 00:23 when I created the image>
> > >
> > >
> > > On Thu, Oct 19, 2017, 11:12 Arnaud H�ritier  wrote:>
> > >
> > > > These images are kindly managed by a PMC member of our project
> (Carlos)
> >
> > but>
> >
> > > > yes they aren't managed directly by the project>
> > > >
> > > > We can easily see with him to improve this IMO.>
> > > >
> > > > When he started that (several years ago) Docker wasn't what it is
> >
> > nowadays.>
> >
> > > > With docker being mainstream I agree that we can reconsider this.>
> > > >
> > > > The docker image build/distribution could perhaps be part of our
> >
> > release>
> >
> > > > process.>
> > > >
> > > > WDYT Carlos ?>
> > > >
> > > > On Thu, Oct 19, 2017 at 4:16 AM, Mike Drob 
> wrote:>
> > > >
> > > > > I guess the natural follow-on question is whether the Maven
> >
> > community>
> >
> > > > > would consider publishing an official set of images? Or
> >
> > alternatively>
> >
> > > > > whether they should send a takedown notice to protect their brand
> >
> > and>
> >
> > > > > trademarks...>
> > > > >
> > > > > On 2017-10-18 18:36, "Manfred Moser" 
> wrote:>
> > > > >
> > > > > > No. As you can see from the github URL this is NOT an apache
> URL.>
> > > > > >
> > > > > > https://github.com/carlossg/docker-maven>
> > > > > >
> > > > > >
> > > > > > Mike Drob wrote on 2017-10-18 16:32:>
> > > > > >
> > > > > > > Hello,>
> > > > > > >
> > > > > > > Are the images at https://hub.docker.com/r/_/maven/
> considered to
> >
> > be>
> >
> > > > > official>
> > > > >
> > > > > > > maven docker images and blessed/published by the PMC?>
> > > > > > >
> > > > > > > Thanks,>
> > > > > > > Mike>
> >
> > ->
> >
> > > > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org>
> > > > > > > For additional commands, e-mail: users-h...@maven.apache.org>
> >
> > ->
> >
> > > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org>
> > > > > > For additional commands, e-mail: users-h...@maven.apache.org>
> >
> > ->
> >
> > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org>
> > > > > For additional commands, e-mail: users-h...@maven.apache.org>
> > > >
> > > > -->
> > > > ->
> > > > Arnaud H�ritier>
> > > > http://aheritier.net>
> > > > Mail/GTalk: aheritier AT gmail DOT com>
> > > > Twitter/Skype : aheritier>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
WBR
Maxim aka solomax

Re: Maven Docker Images

[Maxim Solodovnik]

In this case dockerhub is preferable :)

On Fri, Oct 20, 2017 at 11:07 AM, Bindul Bhowmik <bindulbhow...@gmail.com>
wrote:

> Maxim,
>
> On Thu, Oct 19, 2017 at 7:54 PM, Maxim Solodovnik <solomax...@gmail.com>
> wrote:
> >
> > Hello,
> >
> > here is the place for Apache docker images managed by infra and Apache
> > projects https://bintray.com/apache/ :)
>
> From what I have seen, while there are 4 projects with docker
> repositories on bintray, there seem to be a lot more at dockerhub [1].
> I did a quick search on INFRA JIRA and found that infra has set a few
> projects up on dockerhub recently [2], for example INFRA-14756 [3] for
> bookkeeper.
>
> Bindul
>
> [1] https://hub.docker.com/r/apache/
> [2] https://issues.apache.org/jira/issues/?jql=component%20%
> 3D%20Docker%20AND%20project%20%3D%20INFRA
> [3] https://issues.apache.org/jira/browse/INFRA-14756
>
> >
> > On Fri, Oct 20, 2017 at 12:30 AM, Hervé BOUTEMY <herve.bout...@free.fr>
> > wrote:
> >
> > > great idea
> > >
> > > ok, we need a git repo at ASF
> > >
> > > what else?
> > > Is there some sort of release process? some sort of source to release?
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le jeudi 19 octobre 2017, 13:47:45 CEST Mike Drob a écrit :
> > > > Thanks for the pointer, Carlos! I had searched the archives, but
> maybe I
> > > > didn't go back far enough.
> > > >
> > > > I think moving these Dockerfiles into an ASF repo would be great for
> > > their
> > > > maintainability.
> > > >
> > > > Thanks,
> > > >
> > > > Mike
> > > >
> > > > On 2017-10-19 03:50, Carlos Sanchez <c...@apache.org> wrote:
> > > > > Arnaud is correct, I sent an email to users@ back on Fri, Nov 7,
> > > 2014,>
> > > > > 00:23 when I created the image>
> > > > >
> > > > >
> > > > > On Thu, Oct 19, 2017, 11:12 Arnaud H�ritier <ah...@gmail.com>
> wrote:>
> > > > >
> > > > > > These images are kindly managed by a PMC member of our project
> > > (Carlos)
> > > >
> > > > but>
> > > >
> > > > > > yes they aren't managed directly by the project>
> > > > > >
> > > > > > We can easily see with him to improve this IMO.>
> > > > > >
> > > > > > When he started that (several years ago) Docker wasn't what it is
> > > >
> > > > nowadays.>
> > > >
> > > > > > With docker being mainstream I agree that we can reconsider
> this.>
> > > > > >
> > > > > > The docker image build/distribution could perhaps be part of our
> > > >
> > > > release>
> > > >
> > > > > > process.>
> > > > > >
> > > > > > WDYT Carlos ?>
> > > > > >
> > > > > > On Thu, Oct 19, 2017 at 4:16 AM, Mike Drob <md...@apache.org>
> > > wrote:>
> > > > > >
> > > > > > > I guess the natural follow-on question is whether the Maven
> > > >
> > > > community>
> > > >
> > > > > > > would consider publishing an official set of images? Or
> > > >
> > > > alternatively>
> > > >
> > > > > > > whether they should send a takedown notice to protect their
> brand
> > > >
> > > > and>
> > > >
> > > > > > > trademarks...>
> > > > > > >
> > > > > > > On 2017-10-18 18:36, "Manfred Moser" <ma...@simpligility.com>
> > > wrote:>
> > > > > > >
> > > > > > > > No. As you can see from the github URL this is NOT an apache
> > > URL.>
> > > > > > > >
> > > > > > > > https://github.com/carlossg/docker-maven>
> > > > > > > >
> > > > > > > >
> > > > > > > > Mike Drob wrote on 2017-10-18 16:32:>
> > > > > > > >
> > > > > > > > > Hello,>
> > > > > > > > >
> > > > > > > > > Are the images at https://

Re: Maven Docker Images

[Maxim Solodovnik]

I would start with filing INFRA ticket :)

On Fri, Oct 20, 2017 at 12:40 PM, Hervé BOUTEMY <herve.bout...@free.fr>
wrote:

> awesome: there is some common practice we should get into
>
> do you know if there some docs somewhere?
> I suppose there are some credentials associated to publishing to Dockerhub
>
> Regards,
>
> Hervé
>
> Le vendredi 20 octobre 2017, 11:39:22 CEST Maxim Solodovnik a écrit :
> > In this case dockerhub is preferable :)
> >
> > On Fri, Oct 20, 2017 at 11:07 AM, Bindul Bhowmik <
> bindulbhow...@gmail.com>
> >
> > wrote:
> > > Maxim,
> > >
> > > On Thu, Oct 19, 2017 at 7:54 PM, Maxim Solodovnik <
> solomax...@gmail.com>
> > >
> > > wrote:
> > > > Hello,
> > > >
> > > > here is the place for Apache docker images managed by infra and
> Apache
> > > > projects https://bintray.com/apache/ :)
> > >
> > > From what I have seen, while there are 4 projects with docker
> > > repositories on bintray, there seem to be a lot more at dockerhub [1].
> > > I did a quick search on INFRA JIRA and found that infra has set a few
> > > projects up on dockerhub recently [2], for example INFRA-14756 [3] for
> > > bookkeeper.
> > >
> > > Bindul
> > >
> > > [1] https://hub.docker.com/r/apache/
> > > [2] https://issues.apache.org/jira/issues/?jql=component%20%
> > > 3D%20Docker%20AND%20project%20%3D%20INFRA
> > > [3] https://issues.apache.org/jira/browse/INFRA-14756
> > >
> > > > On Fri, Oct 20, 2017 at 12:30 AM, Hervé BOUTEMY <
> herve.bout...@free.fr>
> > > >
> > > > wrote:
> > > > > great idea
> > > > >
> > > > > ok, we need a git repo at ASF
> > > > >
> > > > > what else?
> > > > > Is there some sort of release process? some sort of source to
> release?
> > > > >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > > Le jeudi 19 octobre 2017, 13:47:45 CEST Mike Drob a écrit :
> > > > > > Thanks for the pointer, Carlos! I had searched the archives, but
> > >
> > > maybe I
> > >
> > > > > > didn't go back far enough.
> > > > > >
> > > > > > I think moving these Dockerfiles into an ASF repo would be great
> for
> > > > >
> > > > > their
> > > > >
> > > > > > maintainability.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Mike
> > > > > >
> > > > > > On 2017-10-19 03:50, Carlos Sanchez <c...@apache.org> wrote:
> > > > > > > Arnaud is correct, I sent an email to users@ back on Fri, Nov
> 7,
> > > > >
> > > > > 2014,>
> > > > >
> > > > > > > 00:23 when I created the image>
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Oct 19, 2017, 11:12 Arnaud H�ritier <ah...@gmail.com>
> > >
> > > wrote:>
> > >
> > > > > > > > These images are kindly managed by a PMC member of our
> project
> > > > >
> > > > > (Carlos)
> > > > >
> > > > > > but>
> > > > > >
> > > > > > > > yes they aren't managed directly by the project>
> > > > > > > >
> > > > > > > > We can easily see with him to improve this IMO.>
> > > > > > > >
> > > > > > > > When he started that (several years ago) Docker wasn't what
> it
> > > > > > > > is
> > > > > >
> > > > > > nowadays.>
> > > > > >
> > > > > > > > With docker being mainstream I agree that we can reconsider
> > >
> > > this.>
> > >
> > > > > > > > The docker image build/distribution could perhaps be part of
> our
> > > > > >
> > > > > > release>
> > > > > >
> > > > > > > > process.>
> > > > > > > >
> > > > > > > > WDYT Carlos ?>
> > > > > > > >
> > > > > > > > On Thu, Oct 19, 2017 at 4:16 AM, Mik

Re: Maven Project Info Reports Plugin 3.0.1 release

[Maxim Solodovnik]

+1 :)
Will be happy to help with this release :)

BTW can someone take a look at this
https://issues.apache.org/jira/browse/MPIR-374 issue?
Or maybe any pointer on where to look? I spent some time trying to fix it,
but no luck :(

On Tue, 18 Jun 2019 at 00:31, Peter Somogyi  wrote:

> Hi,
>
> I'd like to ask if there are any plans to release version 3.0.1 from Maven
> Project Info Reports Plugin in the near future.
>
> There is a bug in 3.0.0 which generates the email links incorrectly. As a
> result, the mailing list subscribe URLs give 404 error message on HBase's
> Mailing Lists page. This bug was fixed in MPIR-380 <
> https://issues.apache.org/jira/browse/MPIR-380> back in February but there
> was no release since then.
>
> HBase is using this version via the latest ASF parent pom <
>
> https://github.com/apache/maven-apache-parent/blob/apache-21/pom.xml#L210-L214
> >
>
> Thanks,
> Peter
>


-- 
WBR
Maxim aka solomax

Re: Maven Project Info Reports Plugin 3.0.1 release

[Maxim Solodovnik]

Thanks a lot Robert

Finally I was able to get back to this task :)

The test was created and fails successfully :) [1]
Then I tried to replace ProjectBuilder with ModelBuilder
Unfortunately it seems impossible :(

ProjectBuilder has method build(artifact)
ModelBuilder doesn't have it :(

Maybe it is possible to pass bundle plugin to projectBuilder somehow?

[1] 
https://github.com/solomax/maven-project-info-reports-plugin/tree/master/src/it/MPIR-374-dependencymanagement-bundle

On Wed, 19 Jun 2019 at 03:34, Robert Scholte  wrote:
>
> [ERROR] Unknown packaging: bundle @ line 6, column 16 at 
> org.apache.maven.project.DefaultProjectBuilder.build 
> (DefaultProjectBuilder.java:205) at 
> org.apache.maven.project.DefaultProjectBuilder.build 
> (DefaultProjectBuilder.java:340) at 
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
>  (RepositoryUtils.java:125) at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow
>  (DependencyManagementRenderer.java:253)
>
> Based on this stacktrace the root cause is in Maven.
>
> So a little bit more details: the code tries to gather all licenses, see the 
> code of the getDependencyRow method. Because of the inheritence it can't 
> simply read the pom, it must respect all its parents too.
> My first impression is that using a ProjectBuilder comes with too much 
> overhead. Instead I would try to use a ModelBuilder instead. It's result will 
> be an effective model containing all licenses.
>
> To guide you in the right direction:
> I'd suggest to make an integrationtest under 
> src/it/MPIR-374-dependencymanagement-bundle with only a pom, containing only 
> dependencyManagement for 
> com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.9.5
> Also add the following verify.groovy script:
>   def buildLog = new File( basedir, 'build.log' )
>   assert !( buildLog.text =~ /\[ERROR\] Unknown packaging: bundle/ )
>
> Now run it with mvn verify -Prun-its -Dinvoker.test=MPIR-374*
> It should fail because the build.log contains the error message.
>
> I hope this is enough information to continue and hopefully fix this issue.
>
> thanks
> Robert
>
>
> On 18-6-2019 04:29:06, Maxim Solodovnik  wrote:
> +1 :)
> Will be happy to help with this release :)
>
> BTW can someone take a look at this
> https://issues.apache.org/jira/browse/MPIR-374 issue?
> Or maybe any pointer on where to look? I spent some time trying to fix it,
> but no luck :(
>
> On Tue, 18 Jun 2019 at 00:31, Peter Somogyi wrote:
>
> > Hi,
> >
> > I'd like to ask if there are any plans to release version 3.0.1 from Maven
> > Project Info Reports Plugin in the near future.
> >
> > There is a bug in 3.0.0 which generates the email links incorrectly. As a
> > result, the mailing list subscribe URLs give 404 error message on HBase's
> > Mailing Lists page. This bug was fixed in MPIR-380
> > https://issues.apache.org/jira/browse/MPIR-380> back in February but there
> > was no release since then.
> >
> > HBase is using this version via the latest ASF parent pom
> >
> > https://github.com/apache/maven-apache-parent/blob/apache-21/pom.xml#L210-L214
> > >
> >
> > Thanks,
> > Peter
> >
>
>
> --
> WBR
> Maxim aka solomax



-- 
WBR
Maxim aka solomax

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [RESULT][DISCUSS] Make Jira issues viewable.

[Maxim Solodovnik]

The filter is private actually

On Fri, 11 Sep 2020 at 17:50, Arnaud Héritier  wrote:

> It's not a blocker if it works without the filter parameter but the
> behavior is strange (I never saw this myself)
>
> On Fri, Sep 11, 2020 at 12:25 PM Robert Scholte 
> wrote:
>
> > Clear, it is not an issue, just a matter of using the correct URL.
> >
> > Robert
> >
> > On 11-9-2020 11:18:45, Enrico Olivelli  wrote:
> > I agree with Bindul
> >
> > I have never seen such blocks
> >
> > Enrico
> >
> > Il Ven 11 Set 2020, 10:38 Bindul Bhowmik ha
> > scritto:
> >
> > > Hi,
> > >
> > > If I may chime in, the Maven (and most Apache) JIRA issues don't
> > > require a login to view. I believe the issue is that Amelia added a
> > > filter to the URL pasted in the tweet, and the filter requires a
> > > login.
> > > So: https://issues.apache.org/jira/browse/MNG-6928 is viewable without
> > > a login https://issues.apache.org/jira/browse/MNG-6928?filter=-2 is
> > > not.
> > >
> > > Bindul
> > >
> > > On Fri, Sep 11, 2020 at 12:54 AM Maarten Mulders
> > > wrote:
> > > >
> > > > Agreed. If there's anything that is too deliberate to discuss in the
> > > > open, there's the mailing list, direct email or what not.
> > > >
> > > > Maarten
> > > >
> > > > On 11/09/2020 09:51, Robert Scholte wrote:
> > > > > Based on the
> > > https://twitter.com/ameliaeiras/status/1303815661307613184 and the
> > > responses of Marten Deinum I agree that it makes sense to make issues
> > > viewable for all.
> > > > >
> > > > > If there is no strong reason to keep it as it is, I'll ask our Jira
> > > administrator if our scheme can be updated.
> > > > > (looks like the Maven projects are missing an explicit Issue
> Security
> > > scheme)
> > > > >
> > > > > thanks,
> > > > > Robert
> > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >
>
>
> --
> Arnaud Héritier
> Twitter/Skype : aheritier
>


-- 
Best regards,
Maxim

Re: [VOTE] Release Apache Maven version 3.8.0

[Maxim Solodovnik]

Hello,

Moving might not do what is expected
the binaries are already in http://archive.apache.org/dist/maven/maven-3/3.8.0/

On Fri, 26 Mar 2021 at 11:25, Olivier Lamy  wrote:
>
> Yes you're right that shouldn't be there as this has been mirrored in all
> Apache mirrors as a real release...
>
> The procedure
> http://maven.apache.org/developers/release/maven-core-release.html says:
> "
>
> For non-alpha/beta releases, release candidates are produced before the
> actual release.
>
> Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then create
> the necessary directory tree.
>
> "
>
> @Robert I moved the binaries. As the vote is not finished they shouldn;t be
> in the official Apache release download area
>
> svn mv https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0
> https://dist.apache.org/repos/dist/dev/maven/maven-3/
>
> Committing transaction...
>
> Committed revision 46741.
>
> On Fri, 26 Mar 2021 at 13:18, Mark Derricutt  wrote:
>
> > I notice in the vote email we have mentioned:
> >
> >
> > dist.apache.org/repos/dist/release/maven/maven–3/3.8.0/binaries/apache-maven–3.8.0-bin.zip
> > 
> > <
> > http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> > >
> >
> > which doesn’t really highlight anywhere that this is a staging/unreleased
> > version.
> >
> > Tho changing that probably won’t change too much here.
> >
> > *ponders*
> >
> >
> >
> >
> > From: Gary Gregory  
> > Reply: Maven Developers List  
> > Date: 26 March 2021 at 2:13:05 PM
> > To: Maven Developers List  
> > Subject:  Re: [VOTE] Release Apache Maven version 3.8.0
> >
> > It's pretty clear to me that the Maven release process is broken when
> > people are getting new versions they think are real and valid when in fact
> > it is a release candidate vote in in progress. Gary
> >
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy



-- 
Best regards,
Maxim

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven version 3.8.0

[Maxim Solodovnik]

On Fri, 26 Mar 2021 at 14:24, Guillaume Nodet  wrote:
>
> And that's expected as archive.apache.org keeps all releases that are not
> current, i.e. those that have been removed from dist.apache.org.

Actually release is added to the archive as soon as the release is
uploaded (not removed :)

> The release process should really be fixed and the commit to dist.apache.org
> should really happen after the vote.
> I suggest sending an email to infra to see if the binaries can be removed
> from archive.apache.org.
>
> In any case, I'm -0 on this release.  I'm also concerned about the leap in
> the release numbering.  You need to balance how many people will wonder why
> 3.7.0 can not be found vs the number of people who were expecting a feature
> in 3.7.0 (which they would expect to be in 3.8.0 anyway).  A failed attempt
> should not lead to a missing release number either, as the failure stays in
> the dev community, so I don't think the larger user audience cares about
> those...
>
>
>
> Le ven. 26 mars 2021 à 08:17, Maxim Solodovnik  a
> écrit :
>
> > Hello,
> >
> > Moving might not do what is expected
> > the binaries are already in
> > http://archive.apache.org/dist/maven/maven-3/3.8.0/
> >
> > On Fri, 26 Mar 2021 at 11:25, Olivier Lamy  wrote:
> > >
> > > Yes you're right that shouldn't be there as this has been mirrored in all
> > > Apache mirrors as a real release...
> > >
> > > The procedure
> > > http://maven.apache.org/developers/release/maven-core-release.html says:
> > > "
> > >
> > > For non-alpha/beta releases, release candidates are produced before the
> > > actual release.
> > >
> > > Checkout https://dist.apache.org/repos/dist/dev/maven/maven-3 then
> > create
> > > the necessary directory tree.
> > >
> > > "
> > >
> > > @Robert I moved the binaries. As the vote is not finished they shouldn;t
> > be
> > > in the official Apache release download area
> > >
> > > svn mv https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0
> > > https://dist.apache.org/repos/dist/dev/maven/maven-3/
> > >
> > > Committing transaction...
> > >
> > > Committed revision 46741.
> > >
> > > On Fri, 26 Mar 2021 at 13:18, Mark Derricutt  wrote:
> > >
> > > > I notice in the vote email we have mentioned:
> > > >
> > > >
> > > >
> > dist.apache.org/repos/dist/release/maven/maven–3/3.8.0/binaries/apache-maven–3.8.0-bin.zip
> > <http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip>
> > > > <
> > http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> > >
> > > > <
> > > >
> > http://dist.apache.org/repos/dist/release/maven/maven%E2%80%933/3.8.0/binaries/apache-maven%E2%80%933.8.0-bin.zip
> > > > >
> > > >
> > > > which doesn’t really highlight anywhere that this is a
> > staging/unreleased
> > > > version.
> > > >
> > > > Tho changing that probably won’t change too much here.
> > > >
> > > > *ponders*
> > > >
> > > >
> > > >
> > > >
> > > > From: Gary Gregory  
> > > > Reply: Maven Developers List  <
> > dev@maven.apache.org>
> > > > Date: 26 March 2021 at 2:13:05 PM
> > > > To: Maven Developers List   > >
> > > > Subject:  Re: [VOTE] Release Apache Maven version 3.8.0
> > > >
> > > > It's pretty clear to me that the Maven release process is broken when
> > > > people are getting new versions they think are real and valid when in
> > fact
> > > > it is a release candidate vote in in progress. Gary
> > > >
> > >
> > >
> > > --
> > > Olivier Lamy
> > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
> >
> >
> > --
> > Best regards,
> > Maxim
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> --
> 
> Guillaume Nodet



-- 
Best regards,
Maxim

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [ANN] Maven Checkstyle Plugin 3.2.2 released

[Maxim Solodovnik]

Hello,

For whatever reason both 3.2.1 and 3.2.2 are released with

9.3

While latest version ATM 10.9.3

Why to release with outdated dependency?

from mobile (sorry for typos ;)


On Fri, Apr 21, 2023, 02:04 Michael Osipov  wrote:

> The Apache Maven team is pleased to announce the release of the Maven
> Checkstyle Plugin, version 3.2.2.
>
> https://maven.apache.org/plugins/maven-checkstyle-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> 
>org.apache.maven.plugins
>>maven-checkstyle-plugin
>3.2.2
> 
>
>
> Release Notes - Maven Checkstyle Plugin - Version 3.2.2
>
> ** Bug
>  * [MCHECKSTYLE-432] - Inline configuration does not work when
> creating site reports with multiple locales
>
> ** Improvement
>  * [MCHECKSTYLE-426] - Don't use Sink#figure()/Sink#figureCaption()
> since it distorts the output
>
> ** Dependency upgrade
>  * [MCHECKSTYLE-427] - Upgrade m-invoker-plugin to 3.5.0
>
>
> Enjoy,
>
> -The Apache Maven team
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Change to the voting process

[Maxim Solodovnik]

Hello Tamás,

The ASF rule "vote open for at least 72h" only limits lower bound
i.e. the VOTE can't be closed earlier than 72 hours are over but can
last longer :))

On Fri, 12 May 2023 at 16:33, Tamás Cservenák  wrote:
>
> Howdy,
>
> I'd like to propose a change to the ASF Maven voting process (in line with
> ASF guidelines):
> CHANGE the current "vote open for at least 72h" window to "vote open for at
> least 30 days, or more".
>
> Reasoning:
> According to paperwork (ASF stats) we have more than 90 voters available
> (PMCs + committers).
> Still, multiple release votes recently were able to pass the "doorstep"
> only by "hunting down" voters and pulling their sleeves (apologies and
> thanks to them). This makes it clear that ONLY 72h is totally
> anti-community and disrespectful. Nobody's sleeve should be pulled. That's
> disrespectful for sleeves as well (except if you wear a T-shirt). We must
> serve our project community in the best manner, and let our voters be able
> to cast well thought votes in a timely manner, hence increasing the
> irrationally short window of opportunity for casting votes IS A MUST. And
> leave the sleeves alone.
>
> Sorry, but the vote is open for at least 72 hours ONLY.
>
> [ ] +1
> [ ] +0
> [ ] -1



-- 
Best regards,
Maxim

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Change to the voting process

[Maxim Solodovnik]

On Fri, 12 May 2023 at 16:39, Tamás Cservenák  wrote:
>
> Howdy Maxim,
> yes, I am aware of it, the vote is hence "aligned with ASF process".
> I just propose to immediately make it 30 days, that is as you say, in line
> with the ASF process :)

It would be sad if all releases will MUST wait for 30 days :(
So you can't do quick release ...

>
> Thanks
> T
>
> On Fri, May 12, 2023 at 11:37 AM Maxim Solodovnik 
> wrote:
>
> > Hello Tamás,
> >
> > The ASF rule "vote open for at least 72h" only limits lower bound
> > i.e. the VOTE can't be closed earlier than 72 hours are over but can
> > last longer :))
> >
> > On Fri, 12 May 2023 at 16:33, Tamás Cservenák  wrote:
> > >
> > > Howdy,
> > >
> > > I'd like to propose a change to the ASF Maven voting process (in line
> > with
> > > ASF guidelines):
> > > CHANGE the current "vote open for at least 72h" window to "vote open for
> > at
> > > least 30 days, or more".
> > >
> > > Reasoning:
> > > According to paperwork (ASF stats) we have more than 90 voters available
> > > (PMCs + committers).
> > > Still, multiple release votes recently were able to pass the "doorstep"
> > > only by "hunting down" voters and pulling their sleeves (apologies and
> > > thanks to them). This makes it clear that ONLY 72h is totally
> > > anti-community and disrespectful. Nobody's sleeve should be pulled.
> > That's
> > > disrespectful for sleeves as well (except if you wear a T-shirt). We must
> > > serve our project community in the best manner, and let our voters be
> > able
> > > to cast well thought votes in a timely manner, hence increasing the
> > > irrationally short window of opportunity for casting votes IS A MUST. And
> > > leave the sleeves alone.
> > >
> > > Sorry, but the vote is open for at least 72 hours ONLY.
> > >
> > > [ ] +1
> > > [ ] +0
> > > [ ] -1
> >
> >
> >
> > --
> > Best regards,
> > Maxim
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >



-- 
Best regards,
Maxim

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Change to the voting process

[Maxim Solodovnik]

On Fri, 12 May 2023 at 17:02, Tamás Cservenák  wrote:
>
> Howdy,
>
> Lazy consensus?
>
> Again, my main goal is to stir voters up.
> And if unclear, of course I expect negative votes, but I DO EXPECT votes :D

Makes sense :)))

-1 (non-binding)
IMO there should be chance to make "fast" release :)

>
> T
>
> On Fri, May 12, 2023 at 11:58 AM Maxim Solodovnik 
> wrote:
>
> > from mobile (sorry for typos ;)
> >
> >
> > On Fri, May 12, 2023, 16:53 Tamás Cservenák  wrote:
> >
> > > Howdy Romain,
> > >
> > > So here is a catch: this is a completely valid vote started by a member
> > of
> > > PMC.
> > > The reason for it is exactly to shake up things a bit.
> > > Otherwise, if nobody votes, this vote according to ASF voting guidelines
> > > will pass.
> > >
> >
> > To pass the VOTE needs at least 3 +1
> > And more positive votes than negative
> >
> > How vote can pass if nobody votes?
> >
> >
> > > Thanks
> > > T
> > >
> > > On Fri, May 12, 2023 at 11:43 AM Romain Manni-Bucau <
> > rmannibu...@gmail.com
> > > >
> > > wrote:
> > >
> > > > Hi Tamas, I don't share the analyzis (and if I would have to vote it
> > > would
> > > > be rather negative).
> > > > Concretely I don't think "This makes it clear that ONLY 72h is totally
> > > > anti-community and disrespectful."  is accurate, less than an off day
> > > > (sunday) can be but 3 days is generally okish.
> > > >
> > > > That said, nobody prevents you to keep a vote running for 1 month, will
> > > > likely makes it even less interesting, more blocking between projects
> > and
> > > > ultimately harder to follow for voters from my experience so I tend to
> > > > think that even if I strongly share the intent, the solution is not
> > that
> > > > great and does not address the actual issue...in particular cause it
> > > always
> > > > had been allowed by asf to do so, 3 days is a min.
> > > >
> > > > Keep in mind maven is a very split ecosystem and you can rarely vote on
> > > > everything either by knowledge or by time. Ultimately it could makes
> > > sense
> > > > to think to split the community/decrease the number of repos/...
> > > (thinking
> > > > out loud trying to find solution to the issue you describe).
> > > >
> > > > So maybe start by a check of the last votes you consider being bad, and
> > > ask
> > > > why people didnt vote and if there is a way to make them more included
> > or
> > > > if the issue is something else (on a personal side I know I tend to
> > > ignore
> > > > the votes on projects I never use/contribute to for ex).
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://rmannibucau.metawerx.net/> | Old Blog
> > > > <http://rmannibucau.wordpress.com> | Github <
> > > > https://github.com/rmannibucau> |
> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > > > <
> > > >
> > >
> > https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > > >
> > > >
> > > >
> > > > Le ven. 12 mai 2023 à 11:32, Tamás Cservenák  a
> > > écrit
> > > > :
> > > >
> > > > > Howdy,
> > > > >
> > > > > I'd like to propose a change to the ASF Maven voting process (in line
> > > > with
> > > > > ASF guidelines):
> > > > > CHANGE the current "vote open for at least 72h" window to "vote open
> > > for
> > > > at
> > > > > least 30 days, or more".
> > > > >
> > > > > Reasoning:
> > > > > According to paperwork (ASF stats) we have more than 90 voters
> > > available
> > > > > (PMCs + committers).
> > > > > Still, multiple release votes recently were able to pass the
> > "doorstep"
> > > > > only by "hunting down" voters and pulling their sleeves (apologies
> > and
> > > > > thanks to them). This makes it clear that ONLY 72h is totally
> > > > > anti-community and disrespectful. Nobody's sleeve should be pulled.
> > > > That's
> > > > > disrespectful for sleeves as well (except if you wear a T-shirt). We
> > > must
> > > > > serve our project community in the best manner, and let our voters be
> > > > able
> > > > > to cast well thought votes in a timely manner, hence increasing the
> > > > > irrationally short window of opportunity for casting votes IS A MUST.
> > > And
> > > > > leave the sleeves alone.
> > > > >
> > > > > Sorry, but the vote is open for at least 72 hours ONLY.
> > > > >
> > > > > [ ] +1
> > > > > [ ] +0
> > > > > [ ] -1
> > > > >
> > > >
> > >
> >



-- 
Best regards,
Maxim

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Change to the voting process

[Maxim Solodovnik]

from mobile (sorry for typos ;)


On Fri, May 12, 2023, 16:53 Tamás Cservenák  wrote:

> Howdy Romain,
>
> So here is a catch: this is a completely valid vote started by a member of
> PMC.
> The reason for it is exactly to shake up things a bit.
> Otherwise, if nobody votes, this vote according to ASF voting guidelines
> will pass.
>

To pass the VOTE needs at least 3 +1
And more positive votes than negative

How vote can pass if nobody votes?


> Thanks
> T
>
> On Fri, May 12, 2023 at 11:43 AM Romain Manni-Bucau  >
> wrote:
>
> > Hi Tamas, I don't share the analyzis (and if I would have to vote it
> would
> > be rather negative).
> > Concretely I don't think "This makes it clear that ONLY 72h is totally
> > anti-community and disrespectful."  is accurate, less than an off day
> > (sunday) can be but 3 days is generally okish.
> >
> > That said, nobody prevents you to keep a vote running for 1 month, will
> > likely makes it even less interesting, more blocking between projects and
> > ultimately harder to follow for voters from my experience so I tend to
> > think that even if I strongly share the intent, the solution is not that
> > great and does not address the actual issue...in particular cause it
> always
> > had been allowed by asf to do so, 3 days is a min.
> >
> > Keep in mind maven is a very split ecosystem and you can rarely vote on
> > everything either by knowledge or by time. Ultimately it could makes
> sense
> > to think to split the community/decrease the number of repos/...
> (thinking
> > out loud trying to find solution to the issue you describe).
> >
> > So maybe start by a check of the last votes you consider being bad, and
> ask
> > why people didnt vote and if there is a way to make them more included or
> > if the issue is something else (on a personal side I know I tend to
> ignore
> > the votes on projects I never use/contribute to for ex).
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn  | Book
> > <
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> >
> >
> > Le ven. 12 mai 2023 à 11:32, Tamás Cservenák  a
> écrit
> > :
> >
> > > Howdy,
> > >
> > > I'd like to propose a change to the ASF Maven voting process (in line
> > with
> > > ASF guidelines):
> > > CHANGE the current "vote open for at least 72h" window to "vote open
> for
> > at
> > > least 30 days, or more".
> > >
> > > Reasoning:
> > > According to paperwork (ASF stats) we have more than 90 voters
> available
> > > (PMCs + committers).
> > > Still, multiple release votes recently were able to pass the "doorstep"
> > > only by "hunting down" voters and pulling their sleeves (apologies and
> > > thanks to them). This makes it clear that ONLY 72h is totally
> > > anti-community and disrespectful. Nobody's sleeve should be pulled.
> > That's
> > > disrespectful for sleeves as well (except if you wear a T-shirt). We
> must
> > > serve our project community in the best manner, and let our voters be
> > able
> > > to cast well thought votes in a timely manner, hence increasing the
> > > irrationally short window of opportunity for casting votes IS A MUST.
> And
> > > leave the sleeves alone.
> > >
> > > Sorry, but the vote is open for at least 72 hours ONLY.
> > >
> > > [ ] +1
> > > [ ] +0
> > > [ ] -1
> > >
> >
>

Re: [ANN] Maven Checkstyle Plugin 3.2.2 released

[Maxim Solodovnik]

ping? :)

On Fri, 21 Apr 2023 at 08:39, Maxim Solodovnik  wrote:
>
> Hello,
>
> For whatever reason both 3.2.1 and 3.2.2 are released with
>
> 9.3
>
> While latest version ATM 10.9.3
>
> Why to release with outdated dependency?
>
> from mobile (sorry for typos ;)
>
>
> On Fri, Apr 21, 2023, 02:04 Michael Osipov  wrote:
>>
>> The Apache Maven team is pleased to announce the release of the Maven
>> Checkstyle Plugin, version 3.2.2.
>>
>> https://maven.apache.org/plugins/maven-checkstyle-plugin/
>>
>> You should specify the version in your project's plugin configuration:
>>
>> 
>>org.apache.maven.plugins
>>>maven-checkstyle-plugin
>>3.2.2
>> 
>>
>>
>> Release Notes - Maven Checkstyle Plugin - Version 3.2.2
>>
>> ** Bug
>>  * [MCHECKSTYLE-432] - Inline configuration does not work when
>> creating site reports with multiple locales
>>
>> ** Improvement
>>  * [MCHECKSTYLE-426] - Don't use Sink#figure()/Sink#figureCaption()
>> since it distorts the output
>>
>> ** Dependency upgrade
>>  * [MCHECKSTYLE-427] - Upgrade m-invoker-plugin to 3.5.0
>>
>>
>> Enjoy,
>>
>> -The Apache Maven team
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>


-- 
Best regards,
Maxim

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [ANN] Maven Checkstyle Plugin 3.2.2 released

[Maxim Solodovnik]

On Fri, 5 May 2023 at 11:34, Mark Derricutt  wrote:
>
> On 5 May 2023, at 16:21, Maxim Solodovnik wrote:
>
> While latest version ATM 10.9.3
>
> Checkstyle 10.x requires Java 9+ which is good enough reason in my mind to 
> not update it officially (yet).

Understood, thanks for the explanaitions!

>
> You can however update the check style version by adding a  
> declaration in the plugin.

Already did it :)

>
> 
>
> "The ease with which a change can be implemented has no relevance at all to 
> whether it is the right change for the (Java) Platform for all time." — Mark 
> Reinhold.
>
> Mark Derricutt
> http://www.chaliceofblood.net
> http://www.theoryinpractice.net
> http://twitter.com/talios
> http://facebook.com/mderricutt



-- 
Best regards,
Maxim

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org