Re: Another yearly bug squash

[Tibor Digana]

In Surefire I already made a cleanup.
Those open ones are still valid. Thx.

On Fri, Dec 25, 2015 at 12:05 AM, Michael Osipov <1983-01...@gmx.net> wrote:

> Hi folks,
>
> I'd like to do another bug squash like a did last year.
> We currently have 132 unresolved bugs which haven't been updated for
> more than three years. I hardly believe that they will be updated ever.
> Maybe they have been resolved with new versions automatically.
>
> Anyway, here is the query for: category = Maven AND updated <= -156w AND
> resolution = Unresolved ORDER BY created DESC
>
> Please have a look whether you see some of yours which are still valid
> or anything else. If you don't object, I will go ahead and close them
> as won't fix. Let me know by the end of the week.
>
> Michael
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Cheers
Tibor

[GitHub] maven-surefire pull request: [SUREFIRE-1135] Improve ignore messag...

[Tibor17]

Github user Tibor17 commented on the pull request:

https://github.com/apache/maven-surefire/pull/79#issuecomment-167356250
  
@mbocek This PR was merged with master. Thx for contributing. Please close 
it.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

MNG-5896: Speed up builds by parallel POM downloads

[Harald Wellmann]

When building a project with dependencies not yet available in the local 
repository, I noticed that Maven first downloads the dependency POMs 
sequentially and then proceeds downloading the dependency JARs with up 
to 5 threads in parallel, which is not optimal when the POMs are served 
by a high-latency repository manager.


There wasn't a lot of feedback on my enhancement request [1] or my 
original StackOverflow question [2], so I started digging into the 
source code and ended up with a patch [3].


The patch only affects Aether, not Maven Core, but since Aether is not 
the top-level project from the end user perspective and doesn't appear 
to be very active, I thought I'd better contact this mailing list first.


The basic idea of the patch is a clean separation of POM downloading 
from POM processing in DefaultDependencyCollector. Once these steps are 
separated, it is possible to download dependency POMs asynchronously and 
in parallel, while still processing the POM models sequentially to build 
the dependency graph in the correct order.


Since DefaultDependencyCollector holds a lot of global state and has 
rather long methods, I started by refactoring this class into smaller 
chunks to make the underlying logic more transparent. That's why the 
patch looks a bit large, but essentially it only affects a single 
original class.


I did a local build of Maven 3.4.0-SNAPSHOT using Aether 1.1.0-SNAPSHOT 
with my patch, with all tests passing.


I also ran maven-integration-testing on this patched Maven 
3.4.0-SNAPSHOT, with no new tests failing. (There is just one test which 
is broken since a recent change on trunk, see [4].)


Thanks for reading this far - it would be great if someone would take 
the time to look into the issue and the patch, and advise how to go on.



[1] https://issues.apache.org/jira/browse/MNG-5896
[2] 
http://stackoverflow.com/questions/32299902/parallel-downloads-of-maven-artifacts
[3] 
https://github.com/hwellmann/aether-core/commit/cdab4c40094ccf621370647f83ecda54684066ce
[4] 
https://builds.apache.org/job/maven-3.3-release-status-test-linux/lastCompletedBuild/testReport/


Regards,
Harald


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

Re: [VOTE] Release Apache Maven Shared Component: File Management Version 3.0.0

[Tibor Digana]

+1

On Fri, Dec 25, 2015 at 2:50 PM, Karl Heinz Marbaise-3 [via Maven] <
ml-node+s40175n5856227...@n5.nabble.com> wrote:

> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20fixVersion%20%3D%20file-management-3.0.0
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20file-management%20ORDER%20BY%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1239
>
> https://repository.apache.org/content/repositories/maven-1239/org/apache/maven/shared/file-management/3.0.0/file-management-3.0.0-source-release.zip
> Source release checksum(s):
> file-management-3.0.0-source-release.zip sha1:
> 0548bd0809dcd0092774cbc5d3e72539a251e827
>
> Staging site:
> http://maven.apache.org/shared-archives/file-management-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: [hidden email]
> 
> For additional commands, e-mail: [hidden email]
> 
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://maven.40175.n5.nabble.com/VOTE-Release-Apache-Maven-Shared-Component-File-Management-Version-3-0-0-tp5856227.html
> To start a new topic under Maven Developers, email
> ml-node+s40175n142166...@n5.nabble.com
> To unsubscribe from Maven Developers, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://maven.40175.n5.nabble.com/Re-VOTE-Release-Apache-Maven-Shared-Component-File-Management-Version-3-0-0-tp5856427.html
Sent from the Maven Developers mailing list archive at Nabble.com.

Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven Stylus Skin

[Olivier Lamy]

-0

I think we are still using fluido. And some users too. I don't mind the
others but this one is used a lot included by us.

So I don't understand such rush to retire that? I guess we are in an
Opensource foundation which we do not have pressure for maintenance etc...


On 25 December 2015 at 09:34, Michael Osipov <1983-01...@gmx.net> wrote:

> Hi,
>
> as previously suggested, it makes sense to retire those skins because
> they haven't been updated for a long time and we don't have the resources
> to maintain them properly [1].
>
> Last releases:
> Maven Application Skin: 2012-01-18
> Maven Classic Skin: 2012-01-18
> Maven Stylus Skin: 2012-07-30
>
> I therefore propose that we retire these skins.
>
> If this vote is successful I will make one final release of the skin,
> making
> it clear on the skin site that it has been retired. After that the source
> code
> will be moved into the "retired" area in our Subversion repository.
>
> The process for retiring a skin is described here:
> http://maven.apache.org/developers/retirement-plan-plugins.html
> (Though these aren't plugins, the process is universal)
>
> The vote is open for 72 hours.
>
> [ ] +1 Yes, it's about time
> [ ] -1 No, because...
>
> I would ask kindly those who have already cast their vote to revote to
> make it
> "official".
>
> [1]
> http://mail-archives.apache.org/mod_mbox/maven-dev/201512.mbox/%3Ctrinity-8ab6577c-ab69-4f9f-86e6-533e0b309a94-1450902628141%403capp-gmx-bs54%3E
>
> Michael
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven Stylus Skin

[Michael Osipov]

Nobody is retiring Fluido Skin but only those in the subject.

> Gesendet: Sonntag, 27. Dezember 2015 um 01:10 Uhr
> Von: "Olivier Lamy" 
> An: "Maven Developers List" 
> Betreff: Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven 
> Stylus Skin
>
> -0
> 
> I think we are still using fluido. And some users too. I don't mind the
> others but this one is used a lot included by us.
> 
> So I don't understand such rush to retire that? I guess we are in an
> Opensource foundation which we do not have pressure for maintenance etc...
> 
> 
> On 25 December 2015 at 09:34, Michael Osipov <1983-01...@gmx.net> wrote:
> 
> > Hi,
> >
> > as previously suggested, it makes sense to retire those skins because
> > they haven't been updated for a long time and we don't have the resources
> > to maintain them properly [1].
> >
> > Last releases:
> > Maven Application Skin: 2012-01-18
> > Maven Classic Skin: 2012-01-18
> > Maven Stylus Skin: 2012-07-30
> >
> > I therefore propose that we retire these skins.
> >
> > If this vote is successful I will make one final release of the skin,
> > making
> > it clear on the skin site that it has been retired. After that the source
> > code
> > will be moved into the "retired" area in our Subversion repository.
> >
> > The process for retiring a skin is described here:
> > http://maven.apache.org/developers/retirement-plan-plugins.html
> > (Though these aren't plugins, the process is universal)
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Yes, it's about time
> > [ ] -1 No, because...
> >
> > I would ask kindly those who have already cast their vote to revote to
> > make it
> > "official".
> >
> > [1]
> > http://mail-archives.apache.org/mod_mbox/maven-dev/201512.mbox/%3Ctrinity-8ab6577c-ab69-4f9f-86e6-533e0b309a94-1450902628141%403capp-gmx-bs54%3E
> >
> > Michael
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
> 
> 
> -- 
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
> 

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

Re: MNG-5896: Speed up builds by parallel POM downloads

[Stephen Connolly]

This is interesting. I think the plan I to move aether under the maven
project (at least I was asked to grant my contributions to aether to allow
dual licensing under ASL on the basis of moving the code here... Still not
sure what the status is) so I suspect until that gets resolved aether will
be a fixed point. Once it gets resolved then this sounds like a good
contribution, but I am on my phone so cannot say for sure.

Keep an eye out for news of aether's code landing here/elsewhere and
re-ping at that point if we have forgotten ;-)

On Saturday 26 December 2015, Harald Wellmann 
wrote:

> When building a project with dependencies not yet available in the local
> repository, I noticed that Maven first downloads the dependency POMs
> sequentially and then proceeds downloading the dependency JARs with up to 5
> threads in parallel, which is not optimal when the POMs are served by a
> high-latency repository manager.
>
> There wasn't a lot of feedback on my enhancement request [1] or my
> original StackOverflow question [2], so I started digging into the source
> code and ended up with a patch [3].
>
> The patch only affects Aether, not Maven Core, but since Aether is not the
> top-level project from the end user perspective and doesn't appear to be
> very active, I thought I'd better contact this mailing list first.
>
> The basic idea of the patch is a clean separation of POM downloading from
> POM processing in DefaultDependencyCollector. Once these steps are
> separated, it is possible to download dependency POMs asynchronously and in
> parallel, while still processing the POM models sequentially to build the
> dependency graph in the correct order.
>
> Since DefaultDependencyCollector holds a lot of global state and has
> rather long methods, I started by refactoring this class into smaller
> chunks to make the underlying logic more transparent. That's why the patch
> looks a bit large, but essentially it only affects a single original class.
>
> I did a local build of Maven 3.4.0-SNAPSHOT using Aether 1.1.0-SNAPSHOT
> with my patch, with all tests passing.
>
> I also ran maven-integration-testing on this patched Maven 3.4.0-SNAPSHOT,
> with no new tests failing. (There is just one test which is broken since a
> recent change on trunk, see [4].)
>
> Thanks for reading this far - it would be great if someone would take the
> time to look into the issue and the patch, and advise how to go on.
>
>
> [1] https://issues.apache.org/jira/browse/MNG-5896
> [2]
> http://stackoverflow.com/questions/32299902/parallel-downloads-of-maven-artifacts
> [3]
> https://github.com/hwellmann/aether-core/commit/cdab4c40094ccf621370647f83ecda54684066ce
> [4]
> https://builds.apache.org/job/maven-3.3-release-status-test-linux/lastCompletedBuild/testReport/
>
> Regards,
> Harald
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Sent from my phone

Re: Retiring Maven Skins

[Tibor Digana]

+1 no objections to:
Retire: Maven Application Skin, Maven Classic Skin, Maven Stylus Skin
Active: Maven Default Skin, Maven Fluido Skin

On Thu, Dec 24, 2015 at 10:50 PM, Mirko Friedenhagen-2 [via Maven] <
ml-node+s40175n5856095...@n5.nabble.com> wrote:

> +1
>
> Regards
> Mirko
> --
> Sent from my mobile
> Am 23.12.2015 21:30 schrieb "Michael Osipov" <[hidden email]
> >:
>
> > Hi folks,
> >
> > Hervé is quite busy right now preparing Doxia (Sitetools) 1.7 along with
> > Maven
> > Site Plugin 3.5. I have several tickets on my own I'd like to fix. Some
> of
> > these
> > changes will have impact on the skins we provide, they need to be
> adapted.
> >
> > If you take a close look at our skins [1], they haven't been updated for
> > years.
> > Active improvements happen on the Fluido Skin only.
> > Given the fact that probably no one will work on them and none of them
> > have been
> > changed for HTML5, I'd like to retire most of the skins and keep at most
> > two active.
> > That would ultimately mean that only those two will be updated for
> 1.7/3.5
> > and later
> > for HTML5.
> >
> > My proposal:
> >
> > Retire: Maven Application Skin, Maven Classic Skin, Maven Stylus Skin
> > Active: Maven Default Skin, Maven Fluido Skin
> >
> > Please share you opinion, if we agree I will start vote and retire them.
> >
> > Michael
> >
> >
> > [1] https://maven.apache.org/skins
> >
> > -
> > To unsubscribe, e-mail: [hidden email]
> 
> > For additional commands, e-mail: [hidden email]
> 
> >
> >
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://maven.40175.n5.nabble.com/Retiring-Maven-Skins-tp5856023p5856095.html
> To start a new topic under Maven Developers, email
> ml-node+s40175n142166...@n5.nabble.com
> To unsubscribe from Maven Developers, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://maven.40175.n5.nabble.com/Retiring-Maven-Skins-tp5856023p5856416.html
Sent from the Maven Developers mailing list archive at Nabble.com.

Re: Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven Stylus Skin

[Olivier Lamy]

haha so sorry for the noise :-)


On 27 December 2015 at 11:20, Michael Osipov <1983-01...@gmx.net> wrote:

> Nobody is retiring Fluido Skin but only those in the subject.
>
> > Gesendet: Sonntag, 27. Dezember 2015 um 01:10 Uhr
> > Von: "Olivier Lamy" 
> > An: "Maven Developers List" 
> > Betreff: Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin,
> Maven Stylus Skin
> >
> > -0
> >
> > I think we are still using fluido. And some users too. I don't mind the
> > others but this one is used a lot included by us.
> >
> > So I don't understand such rush to retire that? I guess we are in an
> > Opensource foundation which we do not have pressure for maintenance
> etc...
> >
> >
> > On 25 December 2015 at 09:34, Michael Osipov <1983-01...@gmx.net> wrote:
> >
> > > Hi,
> > >
> > > as previously suggested, it makes sense to retire those skins because
> > > they haven't been updated for a long time and we don't have the
> resources
> > > to maintain them properly [1].
> > >
> > > Last releases:
> > > Maven Application Skin: 2012-01-18
> > > Maven Classic Skin: 2012-01-18
> > > Maven Stylus Skin: 2012-07-30
> > >
> > > I therefore propose that we retire these skins.
> > >
> > > If this vote is successful I will make one final release of the skin,
> > > making
> > > it clear on the skin site that it has been retired. After that the
> source
> > > code
> > > will be moved into the "retired" area in our Subversion repository.
> > >
> > > The process for retiring a skin is described here:
> > > http://maven.apache.org/developers/retirement-plan-plugins.html
> > > (Though these aren't plugins, the process is universal)
> > >
> > > The vote is open for 72 hours.
> > >
> > > [ ] +1 Yes, it's about time
> > > [ ] -1 No, because...
> > >
> > > I would ask kindly those who have already cast their vote to revote to
> > > make it
> > > "official".
> > >
> > > [1]
> > >
> http://mail-archives.apache.org/mod_mbox/maven-dev/201512.mbox/%3Ctrinity-8ab6577c-ab69-4f9f-86e6-533e0b309a94-1450902628141%403capp-gmx-bs54%3E
> > >
> > > Michael
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven Stylus Skin

[Tibor Digana]

Oliver, it's not a pressure. Such activities have already started, like
retiring Maven 2, old parallel Maven 3 codelines, Eclipse plugin.
I guess this is very important because we would only concentrate on one
goal, for instance plugins @Java 1.6 and Maven 4.
Makes sense?
Of course we are opensource and we can keep all codelines, but you have
families and therefore you cannot make git push for every contributor even
if he made 99% of work.


On Sun, Dec 27, 2015 at 1:10 AM, olamy [via Maven] <
ml-node+s40175n5856440...@n5.nabble.com> wrote:

> -0
>
> I think we are still using fluido. And some users too. I don't mind the
> others but this one is used a lot included by us.
>
> So I don't understand such rush to retire that? I guess we are in an
> Opensource foundation which we do not have pressure for maintenance etc...
>
>
> On 25 December 2015 at 09:34, Michael Osipov <[hidden email]
> > wrote:
>
> > Hi,
> >
> > as previously suggested, it makes sense to retire those skins because
> > they haven't been updated for a long time and we don't have the
> resources
> > to maintain them properly [1].
> >
> > Last releases:
> > Maven Application Skin: 2012-01-18
> > Maven Classic Skin: 2012-01-18
> > Maven Stylus Skin: 2012-07-30
> >
> > I therefore propose that we retire these skins.
> >
> > If this vote is successful I will make one final release of the skin,
> > making
> > it clear on the skin site that it has been retired. After that the
> source
> > code
> > will be moved into the "retired" area in our Subversion repository.
> >
> > The process for retiring a skin is described here:
> > http://maven.apache.org/developers/retirement-plan-plugins.html
> > (Though these aren't plugins, the process is universal)
> >
> > The vote is open for 72 hours.
> >
> > [ ] +1 Yes, it's about time
> > [ ] -1 No, because...
> >
> > I would ask kindly those who have already cast their vote to revote to
> > make it
> > "official".
> >
> > [1]
> >
> http://mail-archives.apache.org/mod_mbox/maven-dev/201512.mbox/%3Ctrinity-8ab6577c-ab69-4f9f-86e6-533e0b309a94-1450902628141%403capp-gmx-bs54%3E
> >
> > Michael
> >
> > -
> > To unsubscribe, e-mail: [hidden email]
> 
> > For additional commands, e-mail: [hidden email]
> 
> >
> >
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://maven.40175.n5.nabble.com/VOTE-Retire-Maven-Application-Skin-Maven-Classic-Skin-Maven-Stylus-Skin-tp5856102p5856440.html
> To start a new topic under Maven Developers, email
> ml-node+s40175n142166...@n5.nabble.com
> To unsubscribe from Maven Developers, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://maven.40175.n5.nabble.com/VOTE-Retire-Maven-Application-Skin-Maven-Classic-Skin-Maven-Stylus-Skin-tp5856102p5856453.html
Sent from the Maven Developers mailing list archive at Nabble.com.

[GitHub] maven-plugins pull request: [MPMD-209] Upgrade to PMD 5.3.0

[adangel]

Github user adangel closed the pull request at:

https://github.com/apache/maven-plugins/pull/50


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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