Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.8

[Hervé BOUTEMY]

+1

Regards,

Hervé

Le dimanche 14 janvier 2018, 17:39:05 CET Robert Scholte a écrit :
> Hi,
> 
> We solved 3 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922
> rsion=12340500=Text
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20
> component%20%3D%20maven-dependency-analyzer%20AND%20status%20%3D%20Open%20OR
> DER%20BY%20key%20DESC%2C%20priority%20DESC
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1389/
> https://repository.apache.org/service/local/repositories/maven-1389/content/
> org/apache/maven/shared/maven-dependency-analyzer/1.8/maven-dependency-analy
> zer-1.8-source-release.zip
> 
> Source release checksum(s):
> maven-dependency-analyzer-1.8-source-release.zip sha1:
> 9dc09c3ab71c2f25430fa51f73f19dfd208f9b6c
> 
> Staging site:
> https://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/
> 
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for at least 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> -
> 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

Edit / contribute maven wiki

[Nichols, Roger M]

Dear "friendly administrator"

I am requesting permission to contribute (e.g. comment & edit) the Maven Wiki.

The specific page that I am interested in is: 
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException

That URL is spit out by maven, but the cases listed on that page (last updated 
in 2010) don't cover the circumstances that caused that error message to be 
spat out.

I am not looking to use the wiki as a 'help' forum, but rather to document the 
specific case where this error occurs.

Alternately, if there was some way to contact the article's author (Benjamin 
Bentmann), I would be happy to approach him instead.

My confluence user id is: pointlookoutresident, or perhaps 'Roger Nichols' or 
even 'rnich...@hotmail.com' - there is no confluence user id listed on the 
profile page.

Thank you,

Roger. M. Nichols
Engineering Specialist
Manufacturing Engineering
[pd.and.s_logo.long.sm]
Tel: 586 214 6734
Fax: 586 825 7148

--
This is an e-mail from General Dynamics Land Systems. It is for the intended 
recipient only and may contain confidential and privileged information.  No one 
else may read, print, store, copy, forward or act in reliance on it or its 
attachments.  If you are not the intended recipient, please return this message 
to the sender and delete the message and any attachments from your computer. 
Your cooperation is appreciated.

Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.8

[Mark Raynsford]

+0.5 (non binding)

I haven't tested, but I'd like to see the dependency plugin move
forward, and this is needed to do it!

-- 
Mark Raynsford | http://www.io7m.com



pgp4RJWgRf8Fi.pgp
Description: OpenPGP digital signature

Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.8

[Tibor Digana]

+1

On Sun, Jan 14, 2018 at 5:39 PM, Robert Scholte 
wrote:

> Hi,
>
> We solved 3 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12317922=12340500=Text
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%
> 2012317922%20AND%20component%20%3D%20maven-dependency-
> analyzer%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%
> 20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1389/
> https://repository.apache.org/service/local/repositories/mav
> en-1389/content/org/apache/maven/shared/maven-dependency-ana
> lyzer/1.8/maven-dependency-analyzer-1.8-source-release.zip
>
> Source release checksum(s):
> maven-dependency-analyzer-1.8-source-release.zip sha1:
> 9dc09c3ab71c2f25430fa51f73f19dfd208f9b6c
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.8

[Sylwester Lachiewicz]

+1 (non binding)

I found only minor issues:
- link to Jira is not valid in pom
https://issues.apache.org/jira/browse/MSHARED/component/12326428 404 error
- links to download KEYS and signatures are not secured by ssl - general
issue to shared-components

Sylwester

wt., 16 sty 2018 o 19:53 użytkownik Robert Scholte 
napisał:

> +1
>
> On Sun, 14 Jan 2018 17:39:05 +0100, Robert Scholte 
> wrote:
>
> > Hi,
> >
> > We solved 3 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12340500=Text
> >
> > There are still a couple of issues left in JIRA:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20component%20%3D%20maven-dependency-analyzer%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1389/
> >
> https://repository.apache.org/service/local/repositories/maven-1389/content/org/apache/maven/shared/maven-dependency-analyzer/1.8/maven-dependency-analyzer-1.8-source-release.zip
> >
> > Source release checksum(s):
> > maven-dependency-analyzer-1.8-source-release.zip sha1:
> > 9dc09c3ab71c2f25430fa51f73f19dfd208f9b6c
> >
> > Staging site:
> >
> https://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for at least 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > -
> > 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
>
>

Re: Surefire 2.21 release date ?

[Enrico Olivelli]

Il gio 11 gen 2018, 22:26 Tibor Digana  ha scritto:

> I was busy at work but now I am free.
> I need to have a help with investigating a bug
> https://issues.apache.org/jira/browse/SUREFIRE-1450
> I should fix branches which are already in progress: UnicodeTestNamesIT and
> JaCoCO (SUREFIRE-1455).
>

I can pick one on these, just tell me which is the best

Then all ITs setup with JDK 9.
>
> On Wed, Jan 10, 2018 at 11:17 AM, Enrico Olivelli 
> wrote:
>
> > (resending)
> >
> > Hi Tibor,
> > Do you have any plan about the release date of surefire 2.21.0 ?
> >
> > If you have some tasks to do I will be happy to help.
> >
> > Cheers
> >
> > Enrico
> >
>
-- 


-- Enrico Olivelli

Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.8

[Robert Scholte]

+1

On Sun, 14 Jan 2018 17:39:05 +0100, Robert Scholte   
wrote:



Hi,

We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12340500=Text

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20component%20%3D%20maven-dependency-analyzer%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1389/
https://repository.apache.org/service/local/repositories/maven-1389/content/org/apache/maven/shared/maven-dependency-analyzer/1.8/maven-dependency-analyzer-1.8-source-release.zip

Source release checksum(s):
maven-dependency-analyzer-1.8-source-release.zip sha1:  
9dc09c3ab71c2f25430fa51f73f19dfd208f9b6c


Staging site:
https://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1

-
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

Re: main-class + module-version

[Plamen Totev]

Hi Robert,

On 1/15/2018 10:10 PM, Robert Scholte wrote:
> Hi Plamen,
>
> Alan Bateman has provided some valuable information:

Thank you for sharing this. It's really helpful.

On 1/15/2018 10:10 PM, Robert Scholte wrote:
1. MR JARs weren't mentioned. The jar tool does validation to ensure 
that the API provided by the classes in the JAR file is the same for all 
versions.


Validation is indeed something I haven't dig in yet. It is interesting 
to know what is the impact of Maven not doing validation of modular JAR 
files.


On 1/15/2018 10:10 PM, Robert Scholte wrote:
2. The Module, ModulePackages, and ModuleMainClass class file attributes 
are specified in the JVMS. ASM supports them so the Archiver could use 
that. The ModulePackages attribute is optional. If this attribute is not 
present then the JAR file will be scanned to get the set of packages in 
the module.


If the JAR is scanned when ModulePackages is not present then for the 
time being is ok to not implement it.


On 1/15/2018 10:10 PM, Robert Scholte wrote:
The ModuleTarget, ModuleResolution, and ModuleHashes class file 
attributes are JDK-specific so you won't find these in the JVMS. The 
ModuleTarget attribute is documented in JEP 261, the others aren't there 
yet but ASM has support in org.objectweb.asm.commons for these 
attributes so you should be okay.


All of those could be set with ASM (I think) but setting them is the 
easy part. Calculating the hashes for ModuleHashes will require some 
work though.


On 1/15/2018 10:09 PM, Andreas Sewe wrote:
> Also, if two separate tools modify the JAR, the goal of reproducible
> builds is again a bit harder to accomplish. So, please try to use an
> internal, written-in-Java solution if possible.

This is a valid point. I don't think it would be possible to set the 
entries timestamps using the JDK jar tool. But a bit harder does not 
mean impossible. It could be achieved by "post-processing" the resulting 
jar file.


Another point I think we should have in mind is the fact that every time 
the class format version is increased we should update the ASM library 
and release a new version of the JAR plugin otherwise the build will 
fail. Also the users should update the JAR plugin version. That may 
prove to be a bit inconvenient.


From my point of view the trade-off is ease of maintainability vs 
flexibility and control.


Regards,
Plamen Totev

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