How can I remove dependencies pom.xml from shaded jar in elegant way?

[Tibor Digana]

Hi ,

How can I remove dependencies pom.xml from shaded jar in elegant way?
See https://issues.apache.org/jira/browse/SUREFIRE-1298

Cheers
Tibor

[GitHub] maven issue #94: MNG-5889 - adding logic that looks for the file argument an...

[hboutemy]

Github user hboutemy commented on the issue:

https://github.com/apache/maven/pull/94
  
IT moved to its own suite in 
https://github.com/apache/maven-integration-testing/commit/3311f4e345fe7e6c343fae737631b727aba5b910
 to avoid running this IT with Maven 3.3.x, as it will fail


---
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

[GitHub] maven issue #94: MNG-5889 - adding logic that looks for the file argument an...

[hboutemy]

Github user hboutemy commented on the issue:

https://github.com/apache/maven/pull/94
  
IT added 
https://github.com/apache/maven-integration-testing/commit/2e74409fc2593b4478c40f28c7fdabc60202c06b
no change on existing ITs, just added an additional run with different 
execution state: current dir = parent, mvn run with -f client/pom.xml
of course, it is currently failing: I let Tibor or Michael apply the fix


---
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

[GitHub] maven issue #94: MNG-5889 - adding logic that looks for the file argument an...

[jvanzyl]

Github user jvanzyl commented on the issue:

https://github.com/apache/maven/pull/94
  
Please do not change an existing test. The conditions under which this IT 
passes should be left as-is and should continue running as it is in exactly the 
form it runs now. Making purely additional logic is fine, or copy that IT and 
make another test all together, do not change the logic or resources of the 
existing IT. It captures behavior that is currently deployed in released 
versions and so it should remain as a representation of that.


---
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

[GitHub] maven issue #94: MNG-5889 - adding logic that looks for the file argument an...

[rpatrick00]

Github user rpatrick00 commented on the issue:

https://github.com/apache/maven/pull/94
  
I took a quick look at the MNG-5771 IT and it's not obvious to me exactly 
what I need to do so if you can add this in a few minutes, that is probably the 
best thing to do.  If not, I will try to look at it as I can and try some tests 
to figure out how it works...


---
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

[GitHub] maven issue #94: MNG-5889 - adding logic that looks for the file argument an...

[hboutemy]

Github user hboutemy commented on the issue:

https://github.com/apache/maven/pull/94
  
I know core ITs are intimidating: it took me years to really dig into the 
code!
This case seems a simple one (what I didn't really expect when thinking at 
it initially), since it's only improving existing MNG-5771 IT with just 
different launch conditions

if it is still too much intimidating, tell me: I'll do the IT showing the 
failure, and you'll add the fix :)


---
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

Re: MNG-5805 and 3.4.0-SNAPSHOT

[Mirko Friedenhagen]

Thanks Stuart, I will check this :-)
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/


On Sat, Nov 12, 2016 at 11:27 PM, Stuart McCulloch  wrote:
> Also note the MNG-5805 style of lifecycle configuration should go inside:
>
>   
> 
>   
> foo
>  
>
> rather than:
>
>   
> 
>   
> foo
>  
>
> There was a bug in Maven 3.3.9 where it accepted MNG-5805 style configuration 
> using  but this broke backwards compatibility with plugins like 
> flexmojos:
>
> https://issues.apache.org/jira/browse/MNG-5958
>
> If you stick with  then your MNG-5805 lifecycle 
> configuration will work with 3.3.9 and 3.4.0+
>
> --
> Cheers, Stuart
>
>
> On Saturday, 12 November 2016 at 22:07, Stuart McCulloch wrote:
>
>> Hi Mirko,
>>
>> Could you provide more details on how to recreate this?
>>
>> While 3.4.0-SNAPSHOT uses a different version of sisu-plexus to 3.3.9 (0.3.3 
>> vs 0.3.2) the XML conversion code didn't change between those versions.
>>
>> There have been changes to the Maven lifecycle components since 3.3.9 which 
>> could influence parsing - but I’d need a sample build/testcase to narrow it 
>> down further.
>>
>> --
>> Cheers, Stuart
>>
>> On Saturday, 12 November 2016 at 21:33, Mirko Friedenhagen wrote:
>>
>> > Hello,
>> >
>> > I am playing with MNG-5805 which works fine with Maven 3.3.9. However
>> > with a late SNAPSHOT from 2016-10-31 I get the following:
>> >
>> > 9180 [INFO] 1788 [WARNING] Expected TEXT, not XML: START_TAG seen
>> > .. @3:217
>> >
>> > 9180 [INFO] java.lang.Throwable
>> >
>> > 9181 [INFO] at 
>> > org.eclipse.sisu.plexus.PlexusXmlBeanConverter.parseBean(PlexusXmlBeanConverter.java:267)
>> >
>> >
>> > Regards Mirko
>> > https://issues.apache.org/jira/browse/MNG-5805
>> >
>> > Apache Maven 3.4.0-SNAPSHOT (a277f6f43a9b52c17b6aa2af069554edd2b0e42e;
>> > 2016-10-31T21:53:43+01:00)
>> > --
>> > http://illegalstateexception.blogspot.com/
>> > https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
>> > https://bitbucket.org/mfriedenhagen/
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org 
>> > (mailto:dev-unsubscr...@maven.apache.org)
>> > For additional commands, e-mail: dev-h...@maven.apache.org 
>> > (mailto:dev-h...@maven.apache.org)
>> >
>> >
>> >
>>
>>
>

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

[VOTE] Release Apache Maven Resources Plugin version 3.0.2

[Christian Schulte]

Hi,

We solved 3 issues:
* [MRESOURCES-230] - Can't escape the escape string
* [MRESOURCES-233] - Upgrade of plexus-interpolation 1.24 to correct
escaping issue.
* [MRESOURCES-234] - Upgrade of commons-io to 2.5 and correction of
invalid scope.

There are still a couple of issues left in JIRA:


Staging repo:



Source release checksum(s):
maven-resources-plugin-3.0.2-source-release.zip sha1:
8a123adc7057303b1f9909516103d71259e2c5c4

Staging site:
https://maven.apache.org/plugins-archives/maven-resources-plugin-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

[GitHub] maven issue #94: MNG-5889 - adding logic that looks for the file argument an...

[michael-o]

Github user michael-o commented on the issue:

https://github.com/apache/maven/pull/94
  
@hboutemy Thanks for helping out!


---
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

Re: maven-3.x Jigsaw - Build # 10 - Fixed

[Robert Scholte]

Pushing this job to the next java 9 ea... (#139 -> #142)

And I'll create another Java9 job, let's try plugin tools.

On Sun, 13 Nov 2016 19:05:03 +0100,  wrote:


yay!

- Mail original -
De: "Apache Jenkins Server" 
À: schu...@apache.org, micha...@apache.org, rfscho...@apache.org,  
notificati...@maven.apache.org

Envoyé: Samedi 12 Novembre 2016 21:43:19
Objet: maven-3.x Jigsaw - Build # 10 - Fixed

The Apache Jenkins build system has built maven-3.x Jigsaw (build #10)

Status: Fixed

Check console output at  
https://builds.apache.org/job/maven-3.x%20Jigsaw/10/ to view the results.


-
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: Releasing maven-resources-plugin 3.0.2

[Christian Schulte]

I also have huge problems when downloading snapshots from that
repository. That also is *very* slow here.


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

Re: Releasing maven-resources-plugin 3.0.2

[Christian Schulte]

[INFO] [WARNING] Could not transfer metadata
org.apache.maven.artifact.repository.metadata.MetadataBridge@31da0344
from/to apache.releases.https
(https://repository.apache.org/service/local/staging/deploy/maven2):
Connect to repository.apache.org:443
[repository.apache.org/207.244.88.143] failed: Operation timed out
[INFO] [INFO]

[INFO] [INFO] BUILD FAILURE
[INFO] [INFO]

[INFO] [INFO] Total time: 8:03.559s
[INFO] [INFO] Finished at: Sun Nov 13 20:08:16 CET 2016
[INFO] [INFO] Final Memory: 40M/135M
[INFO] [INFO]

[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
(default-deploy) on project maven-resources-plugin: Failed to retrieve
remote metadata
org.apache.maven.artifact.repository.metadata.MetadataBridge@31da0344:
Could not transfer metadata
org.apache.maven.artifact.repository.metadata.MetadataBridge@31da0344
from/to apache.releases.https
(https://repository.apache.org/service/local/staging/deploy/maven2):
Connect to repository.apache.org:443
[repository.apache.org/207.244.88.143] failed: Operation timed out ->
[Help 1]
[INFO] [ERROR]
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven
with the -e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
logging.
[INFO] [ERROR]
[INFO] [ERROR] For more information about the errors and possible
solutions, please read the following articles:
[INFO] [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 8:24.862s
[INFO] Finished at: Sun Nov 13 20:08:17 CET 2016
[INFO] Final Memory: 12M/43M
[INFO]



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

Re: Releasing maven-resources-plugin 3.0.2

[Christian Schulte]

Am 11/13/16 um 19:56 schrieb Christian Schulte:
> Am 11/13/16 um 19:42 schrieb Christian Schulte:
>> Am 11/13/16 um 18:53 schrieb herve.bout...@free.fr:
>>> seems you missed 
>>> https://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
>>>
> 
> Wait. I have
> 
> -Djava.net.useSystemProxies=true
> -Dhttp.keepAlive=false
> -Dcom.sun.jndi.dns.timeout.initial=2000
> -Dcom.sun.jndi.dns.timeout.retries=2
> 
> in my ~/.mavenrc.

Hmm. No. Any ideas?

[INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @
maven-resources-plugin ---
[INFO] Uploading:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/maven/plugins/maven-resources-plugin/3.0.2/maven-resources-plugin-3.0.2.jar
[INFO] 2/31 KB
[INFO] 4/31 KB
[INFO] 6/31 KB
[INFO] 8/31 KB
[INFO] 10/31 KB
[INFO] 12/31 KB
[INFO] 14/31 KB
[INFO] 16/31 KB
[INFO] 18/31 KB
[INFO] 20/31 KB
[INFO] 22/31 KB
[INFO] 24/31 KB
[INFO] 26/31 KB
[INFO] 28/31 KB
[INFO] 30/31 KB
[INFO] 31/31 KB
[INFO] [WARNING] Failed to upload MD5 checksum for
/home/schulte/Sources/apache.org/plugins/maven-resources-plugin/target/checkout/target/maven-resources-plugin-3.0.2.jar:
Connect to repository.apache.org:443
[repository.apache.org/207.244.88.143] failed: Operation timed out
[INFO] org.apache.maven.wagon.TransferFailedException: Connect to
repository.apache.org:443 [repository.apache.org/207.244.88.143] failed:
Operation timed out
[INFO]  at
org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:646)
[INFO]  at
org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:541)
[INFO]  at
org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:523)
[INFO]  at
org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:517)
[INFO]  at
org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.putFromStream(AbstractHttpClientWagon.java:511)
[INFO]  at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:886)
[INFO]  at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861)
[INFO]  at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:818)
[INFO]  at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467)
[INFO]  at
org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274)
[INFO]  at
org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211)
[INFO]  at
org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443)
[INFO]  at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137)
[INFO]  at
org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:171)
[INFO]  at
org.apache.maven.plugin.deploy.DeployMojo.deployProject(DeployMojo.java:250)
[INFO]  at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:169)
[INFO]  at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
[INFO]  at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
[INFO]  at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
[INFO]  at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[INFO]  at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
[INFO]  at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
[INFO]  at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
[INFO]  at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
[INFO]  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
[INFO]  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
[INFO]  at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
[INFO]  at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
[INFO]  at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
[INFO]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[INFO]  at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[INFO]  at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[INFO]  at java.lang.reflect.Method.invoke(Method.java:606)
[INFO]  at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
[INFO]  at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
[INFO]  at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
[INFO]  at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)

Re: Releasing maven-resources-plugin 3.0.2

[Christian Schulte]

Am 11/13/16 um 19:42 schrieb Christian Schulte:
> Am 11/13/16 um 18:53 schrieb herve.bout...@free.fr:
>> seems you missed 
>> https://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
>>

Wait. I have

-Djava.net.useSystemProxies=true
-Dhttp.keepAlive=false
-Dcom.sun.jndi.dns.timeout.initial=2000
-Dcom.sun.jndi.dns.timeout.retries=2

in my ~/.mavenrc.



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

Re: Releasing maven-resources-plugin 3.0.2

[Christian Schulte]

Am 11/13/16 um 18:53 schrieb herve.bout...@free.fr:
> seems you missed 
> https://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
> 

Settings should be fine. I already tried to increase the timeouts like
so in every server declaration.

  

  

  
http.authentication.preemptive
%b,true
  

30
30
  

  

It does upload the files. But it produces tons of stacktraces during
deployment. See below. Lots of "Operation timed out". The files are in
the staging repository. Just let it proceed that way?


[INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @
maven-resources-plugin ---
[INFO] Uploading:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/maven/plugins/maven-resources-plugin/3.0.2/maven-resources-plugin-3.0.2.jar
[INFO] 2/31 KB
[INFO] 4/31 KB
[INFO] 6/31 KB
[INFO] 8/31 KB
[INFO] 10/31 KB
[INFO] 12/31 KB
[INFO] 14/31 KB
[INFO] 16/31 KB
[INFO] 18/31 KB
[INFO] 20/31 KB
[INFO] 22/31 KB
[INFO] 24/31 KB
[INFO] 26/31 KB
[INFO] 28/31 KB
[INFO] 30/31 KB
[INFO] 31/31 KB
[INFO] [WARNING] Failed to upload MD5 checksum for
/home/schulte/Sources/apache.org/plugins/maven-resources-plugin/target/checkout/target/maven-resources-plugin-3.0.2.jar:
Connect to repository.apache.org:443
[repository.apache.org/207.244.88.143] failed: Operation timed out
[INFO] org.apache.maven.wagon.TransferFailedException: Connect to
repository.apache.org:443 [repository.apache.org/207.244.88.143] failed:
Operation timed out
[INFO]  at
org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:646)
[INFO]  at
org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:541)
[INFO]  at
org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:523)
[INFO]  at
org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:517)
[INFO]  at
org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.putFromStream(AbstractHttpClientWagon.java:511)
[INFO]  at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:886)
[INFO]  at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861)
[INFO]  at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:818)
[INFO]  at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467)
[INFO]  at
org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274)
[INFO]  at
org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211)
[INFO]  at
org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443)
[INFO]  at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137)
[INFO]  at
org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:171)
[INFO]  at
org.apache.maven.plugin.deploy.DeployMojo.deployProject(DeployMojo.java:250)
[INFO]  at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:169)
[INFO]  at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
[INFO]  at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
[INFO]  at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
[INFO]  at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[INFO]  at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
[INFO]  at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
[INFO]  at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
[INFO]  at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
[INFO]  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
[INFO]  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
[INFO]  at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
[INFO]  at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
[INFO]  at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
[INFO]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[INFO]  at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[INFO]  at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[INFO]  at java.lang.reflect.Method.invoke(Method.java:606)
[INFO]  at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
[INFO]  at

[GitHub] maven issue #94: MNG-5889 - adding logic that looks for the file argument an...

[hboutemy]

Github user hboutemy commented on the issue:

https://github.com/apache/maven/pull/94
  
let's help: I dug into core-its, to find what existing IT to extend, since 
.mvn feature should have an IT already
=> found mng-5771-core-extensions IT, which already tests 3 conditions: I 
think it's the right place to add one more
here are the pointers:
- the IT source: 
https://github.com/apache/maven-integration-testing/blob/master/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5771CoreExtensionsTest.java
- associated test projects: 
https://github.com/apache/maven-integration-testing/tree/master/core-it-suite/src/test/resources/mng-5771-core-extensions/client

I suppose writing the IT will simply require to copy testCoreExtension() 
method and not setting basedir on the Verifier, but add the new option

here is core-its intro: http://maven.apache.org/core-its/core-it-suite/

do you want to try? Or I do it (now that I had a look and found existing 
IT, seems easy)


---
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

Re: maven-3.x Jigsaw - Build # 10 - Fixed

[herve . boutemy]

yay!

- Mail original -
De: "Apache Jenkins Server" 
À: schu...@apache.org, micha...@apache.org, rfscho...@apache.org, 
notificati...@maven.apache.org
Envoyé: Samedi 12 Novembre 2016 21:43:19
Objet: maven-3.x Jigsaw - Build # 10 - Fixed

The Apache Jenkins build system has built maven-3.x Jigsaw (build #10)

Status: Fixed

Check console output at https://builds.apache.org/job/maven-3.x%20Jigsaw/10/ to 
view the results.

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

Re: Releasing maven-resources-plugin 3.0.2

[herve . boutemy]

seems you missed 
https://www.apache.org/dev/publishing-maven-artifacts.html#dev-env

Regards,

Hervé

- Mail original -
De: "Christian Schulte" 
À: "Maven Developers List" 
Envoyé: Dimanche 13 Novembre 2016 17:56:30
Objet: Releasing maven-resources-plugin 3.0.2

Hi,

this is the first time I am releasing a plugin. I've read the release
process documentation and am currently at the 'release:perform' step.
It's not possible for me to deploy to the repository. I tried it several
times now. It always fails with:

[INFO] [WARNING] Could not transfer metadata
org.apache.maven.artifact.repository.metadata.MetadataBridge@5866389d
from/to apache.releases.https
(https://repository.apache.org/service/local/staging/deploy/maven2):
Connect to repository.apache.org:443
[repository.apache.org/207.244.88.143] failed: Operation timed out

[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
(default-deploy) on project maven-resources-plugin: Failed to retrieve
remote metadata
org.apache.maven.artifact.repository.metadata.MetadataBridge@5866389d:
Could not transfer metadata
org.apache.maven.artifact.repository.metadata.MetadataBridge@5866389d
from/to apache.releases.https
(https://repository.apache.org/service/local/staging/deploy/maven2):
Connect to repository.apache.org:443
[repository.apache.org/207.244.88.143] failed: Operation timed out ->
[Help 1]

Is there something else I need to know/do?

Regards,
-- 
Christian

-
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

[GitHub] maven issue #94: MNG-5889 - adding logic that looks for the file argument an...

[rpatrick00]

Github user rpatrick00 commented on the issue:

https://github.com/apache/maven/pull/94
  
@michael-o, while I have no problem contributing, I have no familiarity 
with the maven-integration-test project so it will likely take me some time to 
reverse engineer it enough to figure out how to create an integration test for 
the shell scripts and the various use cases that should be tested.  I would 
hate to see this fix gated by the requirement for me to accomplish this given 
the demands of my day job... 


---
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

Releasing maven-resources-plugin 3.0.2

[Christian Schulte]

Hi,

this is the first time I am releasing a plugin. I've read the release
process documentation and am currently at the 'release:perform' step.
It's not possible for me to deploy to the repository. I tried it several
times now. It always fails with:

[INFO] [WARNING] Could not transfer metadata
org.apache.maven.artifact.repository.metadata.MetadataBridge@5866389d
from/to apache.releases.https
(https://repository.apache.org/service/local/staging/deploy/maven2):
Connect to repository.apache.org:443
[repository.apache.org/207.244.88.143] failed: Operation timed out

[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
(default-deploy) on project maven-resources-plugin: Failed to retrieve
remote metadata
org.apache.maven.artifact.repository.metadata.MetadataBridge@5866389d:
Could not transfer metadata
org.apache.maven.artifact.repository.metadata.MetadataBridge@5866389d
from/to apache.releases.https
(https://repository.apache.org/service/local/staging/deploy/maven2):
Connect to repository.apache.org:443
[repository.apache.org/207.244.88.143] failed: Operation timed out ->
[Help 1]

Is there something else I need to know/do?

Regards,
-- 
Christian

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

Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #1762

[Christian Schulte]

Am 11/13/16 um 13:26 schrieb Guillaume Boué:
> Hi,
> 
> About the OS name printed, it's a bug in Java 7, that is fixed for 9 and 
> was backported down to 8u60, see 
> https://bugs.openjdk.java.net/browse/JDK-8066504. This is what I have on 
> my machine with Java 8u102:
> 
> Apache Maven 3.4.0-SNAPSHOT 
> (NON-CANONICAL_2016-11-12T18:53:10+01:00_Guillaume; 
> 2016-11-12T18:53:10+01:00)
> Maven home: C:\apache-maven-3.4.0-SNAPSHOT\bin\..
> Java version: 1.8.0_102, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_102\jre
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> 
> So it correctly shows "windows 10".
> 
> About the ITs, they don't fail with 3.4.0-SNAPSHOT, but they do with 
> 3.3.9 on Windows. This was fixed in 3.4.0 with 
> https://issues.apache.org/jira/browse/MNG-5962. On other systems, they 
> work fine for both 3.3.9 and current 3.4.0-SNAPSHOT.
> 
> Guillaume

Thanks. That explains it.

Regards,
-- 
Christian



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

[GitHub] maven-surefire pull request #131: [SUREFIRE-1301] add note for changing syst...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/maven-surefire/pull/131


---
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

Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #1762

[Guillaume Boué]

Hi,

About the OS name printed, it's a bug in Java 7, that is fixed for 9 and 
was backported down to 8u60, see 
https://bugs.openjdk.java.net/browse/JDK-8066504. This is what I have on 
my machine with Java 8u102:


Apache Maven 3.4.0-SNAPSHOT 
(NON-CANONICAL_2016-11-12T18:53:10+01:00_Guillaume; 
2016-11-12T18:53:10+01:00)

Maven home: C:\apache-maven-3.4.0-SNAPSHOT\bin\..
Java version: 1.8.0_102, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_102\jre
Default locale: fr_FR, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

So it correctly shows "windows 10".

About the ITs, they don't fail with 3.4.0-SNAPSHOT, but they do with 
3.3.9 on Windows. This was fixed in 3.4.0 with 
https://issues.apache.org/jira/browse/MNG-5962. On other systems, they 
work fine for both 3.3.9 and current 3.4.0-SNAPSHOT.


Guillaume


Le 13/11/2016 à 06:02, Christian Schulte a écrit :

Is there something special about

OS name: "windows server 2012 r2", version: "6.3", arch: "amd64",
family: "windows"

?

I verified the ITs do pass using

Apache Maven 3.4.0-SNAPSHOT (a6f8bd1712a5ae30068424651bac35d2909dc4c1;
2016-11-12T22:15:03+01:00)
Maven home: C:\Users\schulte\Anwendungen\apache-maven-3.4.0-SNAPSHOT\bin\..
Java version: 1.7.0_80, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_80\jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"

That's what gets printed for Windows 10 Pro (Microsoft Windows [Version
10.0.14393]), BTW. Someone knows what is failing on Jenkins?

Am 13.11.2016 um 04:02 schrieb Apache Jenkins Server:

See 

Changes:

[schulte] [MRESOURCES-234] Upgrade of commons-io to 2.5 and correction of 
invalid scope.

[schulte] [MWAR-398] Upgrade of plexus-interpolation to 1.24 to correct 
escaping issue.

[schulte] [MRESOURCES-233] Upgrade of plexus-interpolation 1.24 to correct 
escaping issue.

[schulte] [MRRESOURCES-99] Upgrade of plexus-interpolation to 1.24.

[schulte] [MRAR-66] Upgrade of plexus-interpolation to 1.24.

[gboue] [MPH-105] Effective pom aggregation is not triggered

When the plugin is invoked from the command-line, always show all effective 
POMs for all projects in the reactor. When it is invoked from the lifecycle, 
only show all effective POMs for the head project in the reactor (see commit 
497785 and resolution of MPH-21); otherwise, show the effective POM for the 
current project only.

[schulte] [MPIR-350] Upgrade of plexus-interpolation to 1.24.

[schulte] [MPDF-79] Upgrade of plexus-interpolation to 1.24.

[schulte] [MINVOKER-212] Upgrade of plexus-interpolation to 1.24.

[schulte] [MEJB-107] Upgrade of plexus-interpolation to 1.24.

[schulte] [MEAR-245] Upgrade of plexus-interpolation to 1.24.

[schulte] [MDOAP-48] Upgrade of plexus-interpolation to 1.24.

[schulte] [MCHANGES-377] Upgrade of plexus-interpolation to 1.24.

[schulte] [MDEP-544] Upgrade of plexus-interpolation to 1.24.

[schulte] [MCHECKSTYLE-331] Upgrade of plexus-interpolation to 1.24.

[schulte] [MACR-41] Upgrade of plexus-interpolation 1.24 to correct escaping 
issue.

--
[...truncated 11465 lines...]
[INFO] Installing 
F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-checkstyle-plugin\target\maven-checkstyle-plugin-2.18-SNAPSHOT.jar
 to 
F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-dependency-plugin\target\local-repo\org\apache\maven\plugins\maven-checkstyle-plugin\2.18-SNAPSHOT\maven-checkstyle-plugin-2.18-SNAPSHOT.jar
[INFO] Installing 
F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-checkstyle-plugin\pom.xml
 to 
F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-dependency-plugin\target\local-repo\org\apache\maven\plugins\maven-checkstyle-plugin\2.18-SNAPSHOT\maven-checkstyle-plugin-2.18-SNAPSHOT.pom
[INFO] Installing 
F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-pmd-plugin\pom.xml
 to 
F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-dependency-plugin\target\local-repo\org\apache\maven\plugins\maven-pmd-plugin\3.8-SNAPSHOT\maven-pmd-plugin-3.8-SNAPSHOT.pom
[INFO] Installing 
F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-pmd-plugin\target\maven-pmd-plugin-3.8-SNAPSHOT.jar
 to 
F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-dependency-plugin\target\local-repo\org\apache\maven\plugins\maven-pmd-plugin\3.8-SNAPSHOT\maven-pmd-plugin-3.8-SNAPSHOT.jar
[INFO] Installing 
F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-pmd-plugin\pom.xml
 to 
F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-dependency-plugin\target\local-repo\org\apache\maven\plugins\maven-pmd-plugin\3.8-SNAPSHOT\maven-pmd-plugin-3.8-SNAPSHOT.pom
[INFO] Installing 

Re: [VOTE] Release Apache Maven Site Plugin version 3.6

[Michael Osipov]

Am 2016-11-13 um 09:18 schrieb herve.bout...@free.fr:

no MSITE issue was created AFAIK this is classical issue with
dependencies: how to clearly show what is fixed by dependencies and
what is fixed directly by the released code if you have ideas on how
to better show this without giving too much work (abolutely requiring
to create one MSITE issue each time we find an issue that we know is
in DOXIASITETOOLS isn't an option to me), I'm open to discussion (on
another thread)


I am aware that creating issue for every upgrade is a daunting task, but
you have to see it from the user's perspective: they have everything
they need to see what has really changed.

We have two cases where dependency updates can/have to be documented in
JIRA:
1. Just to update the dependency: it may introduce a regression (which
we have seen)
2. Some bug in the plugin itself which is caused by a backend issue. The
plugin's issue spawns a new issue which is dependent upon. This properly
satisfies the upgrade note.

But this is purely my opinion, and I am not criticizing.

There is no silver bullet to this problem.

Michael


- Mail original - De: "Michael Osipov" 
À: "Maven Developers List"  Envoyé: Dimanche 13
Novembre 2016 00:30:24 Objet: Re: [VOTE] Release Apache Maven Site
Plugin version 3.6

Am 2016-11-13 um 00:23 schrieb herve.bout...@free.fr:

Hi,

We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12335570=Text





Did the JIRA issue for Doxia Sitetools 1.7.4 disappear? That was the
 reason to cancel the previous vote.

Michael


-



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






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

Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #1762

[herve . boutemy]

perhaps there are issue in how Maven sees some Windows OS: I don't have such 
machines at hand to clearly tell how each precise OS version is displayed
Perhaps a Wiki page to have people fill cases could be useful
At least now, I see there are 2 versions that require precise tests: Windows 10 
Pro vs Windows Server 2012

Then why is the IT failing on Jenkins server is something strange: that's the 
classical issue when something works on your machine but not on a build server, 
ie discovering where the isue is... Sorry no idea on this one

Regards,

Hervé

- Mail original -
De: "Christian Schulte" 
À: dev@maven.apache.org
Envoyé: Dimanche 13 Novembre 2016 06:02:32
Objet: Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #1762

Is there something special about

OS name: "windows server 2012 r2", version: "6.3", arch: "amd64",
family: "windows"

?

I verified the ITs do pass using

Apache Maven 3.4.0-SNAPSHOT (a6f8bd1712a5ae30068424651bac35d2909dc4c1;
2016-11-12T22:15:03+01:00)
Maven home: C:\Users\schulte\Anwendungen\apache-maven-3.4.0-SNAPSHOT\bin\..
Java version: 1.7.0_80, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_80\jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"

That's what gets printed for Windows 10 Pro (Microsoft Windows [Version
10.0.14393]), BTW. Someone knows what is failing on Jenkins?

Am 13.11.2016 um 04:02 schrieb Apache Jenkins Server:
> See 
> 
> Changes:
> 
> [schulte] [MRESOURCES-234] Upgrade of commons-io to 2.5 and correction of 
> invalid scope.
> 
> [schulte] [MWAR-398] Upgrade of plexus-interpolation to 1.24 to correct 
> escaping issue.
> 
> [schulte] [MRESOURCES-233] Upgrade of plexus-interpolation 1.24 to correct 
> escaping issue.
> 
> [schulte] [MRRESOURCES-99] Upgrade of plexus-interpolation to 1.24.
> 
> [schulte] [MRAR-66] Upgrade of plexus-interpolation to 1.24.
> 
> [gboue] [MPH-105] Effective pom aggregation is not triggered
> 
> When the plugin is invoked from the command-line, always show all effective 
> POMs for all projects in the reactor. When it is invoked from the lifecycle, 
> only show all effective POMs for the head project in the reactor (see commit 
> 497785 and resolution of MPH-21); otherwise, show the effective POM for the 
> current project only.
> 
> [schulte] [MPIR-350] Upgrade of plexus-interpolation to 1.24.
> 
> [schulte] [MPDF-79] Upgrade of plexus-interpolation to 1.24.
> 
> [schulte] [MINVOKER-212] Upgrade of plexus-interpolation to 1.24.
> 
> [schulte] [MEJB-107] Upgrade of plexus-interpolation to 1.24.
> 
> [schulte] [MEAR-245] Upgrade of plexus-interpolation to 1.24.
> 
> [schulte] [MDOAP-48] Upgrade of plexus-interpolation to 1.24.
> 
> [schulte] [MCHANGES-377] Upgrade of plexus-interpolation to 1.24.
> 
> [schulte] [MDEP-544] Upgrade of plexus-interpolation to 1.24.
> 
> [schulte] [MCHECKSTYLE-331] Upgrade of plexus-interpolation to 1.24.
> 
> [schulte] [MACR-41] Upgrade of plexus-interpolation 1.24 to correct escaping 
> issue.
> 
> --
> [...truncated 11465 lines...]
> [INFO] Installing 
> F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-checkstyle-plugin\target\maven-checkstyle-plugin-2.18-SNAPSHOT.jar
>  to 
> F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-dependency-plugin\target\local-repo\org\apache\maven\plugins\maven-checkstyle-plugin\2.18-SNAPSHOT\maven-checkstyle-plugin-2.18-SNAPSHOT.jar
> [INFO] Installing 
> F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-checkstyle-plugin\pom.xml
>  to 
> F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-dependency-plugin\target\local-repo\org\apache\maven\plugins\maven-checkstyle-plugin\2.18-SNAPSHOT\maven-checkstyle-plugin-2.18-SNAPSHOT.pom
> [INFO] Installing 
> F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-pmd-plugin\pom.xml
>  to 
> F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-dependency-plugin\target\local-repo\org\apache\maven\plugins\maven-pmd-plugin\3.8-SNAPSHOT\maven-pmd-plugin-3.8-SNAPSHOT.pom
> [INFO] Installing 
> F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-pmd-plugin\target\maven-pmd-plugin-3.8-SNAPSHOT.jar
>  to 
> F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-dependency-plugin\target\local-repo\org\apache\maven\plugins\maven-pmd-plugin\3.8-SNAPSHOT\maven-pmd-plugin-3.8-SNAPSHOT.jar
> [INFO] Installing 
> F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-pmd-plugin\pom.xml
>  to 
> F:\jenkins\jenkins-slave\workspace\maven-plugins-ITs-m3-windows\maven-dependency-plugin\target\local-repo\org\apache\maven\plugins\maven-pmd-plugin\3.8-SNAPSHOT\maven-pmd-plugin-3.8-SNAPSHOT.pom
> [INFO] Installing 
> 

Re: [VOTE] Release Apache Maven Site Plugin version 3.6

[herve . boutemy]

no MSITE issue was created AFAIK
this is classical issue with dependencies: how to clearly show what is fixed by 
dependencies and what is fixed directly by the released code
if you have ideas on how to better show this without giving too much work 
(abolutely requiring to create one MSITE issue each time we find an issue that 
we know is in DOXIASITETOOLS isn't an option to me), I'm open to discussion (on 
another thread)

Regards,

Hervé

- Mail original -
De: "Michael Osipov" 
À: "Maven Developers List" 
Envoyé: Dimanche 13 Novembre 2016 00:30:24
Objet: Re: [VOTE] Release Apache Maven Site Plugin version 3.6

Am 2016-11-13 um 00:23 schrieb herve.bout...@free.fr:
> Hi,
>
> We solved 14 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12335570=Text

Did the JIRA issue for Doxia Sitetools 1.7.4 disappear? That was the 
reason to cancel the previous vote.

Michael


-
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