[jira] [Commented] (MNG-6227) Handling multiple tags for a property that is only expecting one value
[
https://issues.apache.org/jira/browse/MNG-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000156#comment-16000156
]
Gili commented on MNG-6227:
---
Forwarding another comment from the plugin author:
{quote}
Just for posterity's sake; it would be good if Maven allowed for discerning
whether multiple tags of the same name were given, or reject it completely.
{quote}
> Handling multiple tags for a property that is only expecting one value
> --
>
> Key: MNG-6227
> URL: https://issues.apache.org/jira/browse/MNG-6227
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.5.0
>Reporter: Gili
>
> Following up on https://github.com/querydsl/apt-maven-plugin/issues/56, I am
> expecting Maven to fail the build, issue a warning, or allow plugins to do
> the same when users pass multiple values for a property that is expecting one
> value.
> Testcase: https://github.com/querydsl/apt-maven-plugin/issues/56
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (MNG-6210) can't load @SessionScoped/@MojoExecutionScoped components from .mvn/extensions.xml
[
https://issues.apache.org/jira/browse/MNG-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-6210.
---
Resolution: Fixed
Works flawlessly now. Thanks for the fix.
> can't load @SessionScoped/@MojoExecutionScoped components from
> .mvn/extensions.xml
> --
>
> Key: MNG-6210
> URL: https://issues.apache.org/jira/browse/MNG-6210
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.3.1, 3.3.3, 3.3.9
>Reporter: Igor Fedorenko
>Assignee: Igor Fedorenko
> Fix For: 3.5.1
>
>
> The build fails with the exception below if Maven core extensions defined in
> .mvn/extensions.xml includes any @SessionScoped or MojoExecutionScoped
> components
> {code}
> [WARNING]
> ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
> parent: ClassRealm[plexus.core, parent: null]]
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) No scope is bound to org.apache.maven.SessionScoped.
> at io.takari.maven.workspace.GenerationsWorkspaceReader.class(Unknown
> Source)
> at
> ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
> parent: ClassRealm[plexus.core, parent: null]] (via modules:
> org.eclipse.sisu.wire.WireModule ->
> org.eclipse.sisu.plexus.PlexusBindingModule)
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:466)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:155)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
> at com.google.inject.Guice.createInjector(Guice.java:96)
> at com.google.inject.Guice.createInjector(Guice.java:73)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481)
> at
> org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:460)
> at
> org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:435)
> at org.apache.maven.cli.MavenCli.container(MavenCli.java:568)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:287)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:205)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MNG-6210) can't load @SessionScoped/@MojoExecutionScoped components from .mvn/extensions.xml
[
https://issues.apache.org/jira/browse/MNG-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1697#comment-1697
]
Igor Fedorenko commented on MNG-6210:
-
These files don't exist in the git repository
https://git1-us-west.apache.org/repos/asf?p=maven-integration-testing.git;a=tree;f=core-it-suite/src/test/resources;h=ee55a631383994f02c25f1e67190b6c937297def;hb=HEAD.
> can't load @SessionScoped/@MojoExecutionScoped components from
> .mvn/extensions.xml
> --
>
> Key: MNG-6210
> URL: https://issues.apache.org/jira/browse/MNG-6210
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.3.1, 3.3.3, 3.3.9
>Reporter: Igor Fedorenko
>Assignee: Igor Fedorenko
> Fix For: 3.5.1
>
>
> The build fails with the exception below if Maven core extensions defined in
> .mvn/extensions.xml includes any @SessionScoped or MojoExecutionScoped
> components
> {code}
> [WARNING]
> ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
> parent: ClassRealm[plexus.core, parent: null]]
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) No scope is bound to org.apache.maven.SessionScoped.
> at io.takari.maven.workspace.GenerationsWorkspaceReader.class(Unknown
> Source)
> at
> ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
> parent: ClassRealm[plexus.core, parent: null]] (via modules:
> org.eclipse.sisu.wire.WireModule ->
> org.eclipse.sisu.plexus.PlexusBindingModule)
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:466)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:155)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
> at com.google.inject.Guice.createInjector(Guice.java:96)
> at com.google.inject.Guice.createInjector(Guice.java:73)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481)
> at
> org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:460)
> at
> org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:435)
> at org.apache.maven.cli.MavenCli.container(MavenCli.java:568)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:287)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:205)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MNG-6210) can't load @SessionScoped/@MojoExecutionScoped components from .mvn/extensions.xml
[
https://issues.apache.org/jira/browse/MNG-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1693#comment-1693
]
Michael Osipov commented on MNG-6210:
-
Looks way better now, but these are still too long:
{noformat}
error: unable to create file
core-it-suite/src/test/resources/mng-6210-core-extensions-custom-scopes/repo-src/maven-it-plugin-core-extensions-custom-scopes-client/src/main/java/org/apache/maven/its/core_extensions_custom_scopes/plugin/ValidateMojoExecutionScopedMojo.java:
Filename too long
error: unable to create file
core-it-suite/src/test/resources/mng-6210-core-extensions-custom-scopes/repo-src/maven-it-plugin-core-extensions-custom-scopes-client/src/main/java/org/apache/maven/its/core_extensions_custom_scopes/plugin/ValidateSessionScopedMojo.java:
Filename too long
error: unable to create file
core-it-suite/src/test/resources/mng-6210-core-extensions-custom-scopes/repo/org/apache/maven/its/it-core-extensions-custom-scopes/maven-it-plugin-core-extensions-custom-scopes-client/0.1/maven-it-plugin-core-extensions-custom-scopes-client-0.1.jar:
Filename too long
error: unable to create file
core-it-suite/src/test/resources/mng-6210-core-extensions-custom-scopes/repo/org/apache/maven/its/it-core-extensions-custom-scopes/maven-it-plugin-core-extensions-custom-scopes-client/0.1/maven-it-plugin-core-extensions-custom-scopes-client-0.1.pom:
Filename too long
{noformat}
they are longer than 240 chars. Leaving virtually no room for a short local
path.
> can't load @SessionScoped/@MojoExecutionScoped components from
> .mvn/extensions.xml
> --
>
> Key: MNG-6210
> URL: https://issues.apache.org/jira/browse/MNG-6210
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.3.1, 3.3.3, 3.3.9
>Reporter: Igor Fedorenko
>Assignee: Igor Fedorenko
> Fix For: 3.5.1
>
>
> The build fails with the exception below if Maven core extensions defined in
> .mvn/extensions.xml includes any @SessionScoped or MojoExecutionScoped
> components
> {code}
> [WARNING]
> ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
> parent: ClassRealm[plexus.core, parent: null]]
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) No scope is bound to org.apache.maven.SessionScoped.
> at io.takari.maven.workspace.GenerationsWorkspaceReader.class(Unknown
> Source)
> at
> ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
> parent: ClassRealm[plexus.core, parent: null]] (via modules:
> org.eclipse.sisu.wire.WireModule ->
> org.eclipse.sisu.plexus.PlexusBindingModule)
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:466)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:155)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
> at com.google.inject.Guice.createInjector(Guice.java:96)
> at com.google.inject.Guice.createInjector(Guice.java:73)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481)
> at
> org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:460)
> at
> org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:435)
> at org.apache.maven.cli.MavenCli.container(MavenCli.java:568)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:287)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:205)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MNG-6210) can't load @SessionScoped/@MojoExecutionScoped components from .mvn/extensions.xml
[
https://issues.apache.org/jira/browse/MNG-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1690#comment-1690
]
Igor Fedorenko commented on MNG-6210:
-
I've shortened the test project file names some, if you still can't clone the
repo I suggest using shorter local path, something like "/d/work/maven-its". I
also suggest you add MINGW64 build to Apache Maven Jenkins, which is really the
only way to guarantee MINGW64 does not regress in the future.
https://git1-us-west.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=a9857509453b42ad9b26fad80d5c421de0a2c50e
> can't load @SessionScoped/@MojoExecutionScoped components from
> .mvn/extensions.xml
> --
>
> Key: MNG-6210
> URL: https://issues.apache.org/jira/browse/MNG-6210
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.3.1, 3.3.3, 3.3.9
>Reporter: Igor Fedorenko
>Assignee: Igor Fedorenko
> Fix For: 3.5.1
>
>
> The build fails with the exception below if Maven core extensions defined in
> .mvn/extensions.xml includes any @SessionScoped or MojoExecutionScoped
> components
> {code}
> [WARNING]
> ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
> parent: ClassRealm[plexus.core, parent: null]]
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) No scope is bound to org.apache.maven.SessionScoped.
> at io.takari.maven.workspace.GenerationsWorkspaceReader.class(Unknown
> Source)
> at
> ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
> parent: ClassRealm[plexus.core, parent: null]] (via modules:
> org.eclipse.sisu.wire.WireModule ->
> org.eclipse.sisu.plexus.PlexusBindingModule)
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:466)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:155)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
> at com.google.inject.Guice.createInjector(Guice.java:96)
> at com.google.inject.Guice.createInjector(Guice.java:73)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481)
> at
> org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:460)
> at
> org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:435)
> at org.apache.maven.cli.MavenCli.container(MavenCli.java:568)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:287)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:205)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MNG-6210) can't load @SessionScoped/@MojoExecutionScoped components from .mvn/extensions.xml
[
https://issues.apache.org/jira/browse/MNG-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1641#comment-1641
]
Michael Osipov commented on MNG-6210:
-
Still not working. Cloning of the repo is still broken. Please fix otherwise I
will revert the commit and put it into a branch.
> can't load @SessionScoped/@MojoExecutionScoped components from
> .mvn/extensions.xml
> --
>
> Key: MNG-6210
> URL: https://issues.apache.org/jira/browse/MNG-6210
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
>Affects Versions: 3.3.1, 3.3.3, 3.3.9
>Reporter: Igor Fedorenko
>Assignee: Igor Fedorenko
> Fix For: 3.5.1
>
>
> The build fails with the exception below if Maven core extensions defined in
> .mvn/extensions.xml includes any @SessionScoped or MojoExecutionScoped
> components
> {code}
> [WARNING]
> ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
> parent: ClassRealm[plexus.core, parent: null]]
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) No scope is bound to org.apache.maven.SessionScoped.
> at io.takari.maven.workspace.GenerationsWorkspaceReader.class(Unknown
> Source)
> at
> ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
> parent: ClassRealm[plexus.core, parent: null]] (via modules:
> org.eclipse.sisu.wire.WireModule ->
> org.eclipse.sisu.plexus.PlexusBindingModule)
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:466)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:155)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
> at com.google.inject.Guice.createInjector(Guice.java:96)
> at com.google.inject.Guice.createInjector(Guice.java:73)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481)
> at
> org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:460)
> at
> org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:435)
> at org.apache.maven.cli.MavenCli.container(MavenCli.java:568)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:287)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:205)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (MSITE-793) MavenMultiPage example
[ https://issues.apache.org/jira/browse/MSITE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] QualiteSys QualiteSys closed MSITE-793. --- Resolution: Fixed Example found > MavenMultiPage example > -- > > Key: MSITE-793 > URL: https://issues.apache.org/jira/browse/MSITE-793 > Project: Maven Site Plugin > Issue Type: Wish > Components: doxia integration >Reporter: QualiteSys QualiteSys > > I am used to produce Maven Site static Html reports. I wish to produce multi > pages reports (one report page per source code for example). In version 2.1.1 > of org.apache.maven.reporting is defined the MavenMultiPageReport interface. > How to use it with the maven-site-plugin ? > Thanks for your help. > Didier -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MSITE-793) MavenMultiPage example
[
https://issues.apache.org/jira/browse/MSITE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1630#comment-1630
]
QualiteSys QualiteSys commented on MSITE-793:
-
I have been able to do it.
The main thing is to create a new sink for each additional page. The
siterenderer process will then create the html files, with the same left menu
as the orginal page.
Didier
Here is an example (using maven-site-plugin version 3.5)
package com.qualitesys.qcrmavenplugin;
/*
* Copyright 2001-2005 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
import java.io.File;
import java.util.List;
import java.util.Locale;
import java.util.Vector;
import org.apache.maven.reporting.MavenReportException;
import org.apache.maven.doxia.sink.Sink;
import org.apache.maven.reporting.AbstractMavenReport;
import org.apache.maven.project.MavenProject;
/**
* Generation of part 96 of qualitychecker report in the site phase, essai
rapport multi page
*
* @goal qcrgoalreporting96
*
* @phase site
*/
public class QcrReporting96Mojo
extends AbstractMavenReport
{
/**
* Language of the project.
* @parameter expression="${sonar.language}"
* @required
*/
private String language;
/**
* Location of the sourcedirectory
* @parameter expression="${project.build.sourceDirectory}"
* @required
*/
private String sourceDirectory;
/**
* Location of the file.
* @parameter expression="${project.build.directory}"
* @required
*/
private File outputDirectory;
/**
* Modele objet du projet Maven
* @parameter expression="${project}"
* @required
* @readonly
*/
private MavenProject project;
/**
* List of reportings to produce 0102030405 etc
* @parameter expression="${sonar.reporting}"
*/
private String reporting;
/*
* (non-Javadoc)
*
* @see org.apache.maven.reporting.AbstractMavenReport#getOutputDirectory()
*/
@Override
protected String getOutputDirectory() {
return outputDirectory.getAbsolutePath();
}
@Override
protected MavenProject getProject() {
return project;
}
@Override
public boolean canGenerateReport() {
boolean res = null==reporting
|| reporting.isEmpty()
|| reporting.contains("96")
;
return res;
}
@Override
public String getOutputName() {
return "QcrReportFile96";
}
@Override
public String getName(Locale arg0) {
return "QC96 Essai multipage";
}
@Override
public String getDescription(Locale arg0) {
return "Report for QualityChecker version "+QcrCommunDec.VERSION+"
according to CWE MITRE's repository see http://www.mitre.org/";;
}
// Constructeur pour forcer le outputDirectory voir code source de
AbstractMavenReport
public QcrReporting96Mojo() {
super();
if (null==outputDirectory) {
outputDirectory = new File("");
}
this.setReportOutputDirectory(outputDirectory);
}
private static final String MOI = "QcrReporting96Mojo::";
@Override
public void executeReport(Locale defaultLocale)
throws MavenReportException {
final String ROUTINE = "executeReport";
if (null == project) {
return;
}
if (null == project)
throw new MavenReportException( MOI+ROUTINE+"02 project non
initialized " );
if (null == outputDirectory) {
throw new MavenReportException( MOI+ROUTINE+"03 outputDirectory non
initialized " );
}
if (null == this.getOutputName()) {
throw new MavenReportException( MOI+ROUTINE+"06 outputName is null
" );
}
String lsFic = this.getReportOutputDirectory() + "/" +
this.getOutputName();
try {
List lesSinks = new Vector();
for (int liInt=0; liInt<4; liInt++) {
File lsDir = this.getReportOutputDirectory();
String lsOut = this.getOutputName()+liInt+".html";
lesSinks.add(this.getSinkFactory().createSink(
lsDir,
lsOut)
);
}
doProcess(lesSinks,lsFic);
} catch (Exception ex) {
}
// Ici le sink principal
Si
[jira] [Commented] (MNG-6227) Handling multiple tags for a property that is only expecting one value
[ https://issues.apache.org/jira/browse/MNG-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1608#comment-1608 ] Gili commented on MNG-6227: --- [~khmarbaise] You seem to have misread the comments. The author is saying exactly the opposite: > I just tested if we see multiple calls to setProcessor if the configuration > has multiple tags. > *This is not the case.* (Emphasis is mine) > Handling multiple tags for a property that is only expecting one value > -- > > Key: MNG-6227 > URL: https://issues.apache.org/jira/browse/MNG-6227 > Project: Maven > Issue Type: Bug > Components: POM >Affects Versions: 3.5.0 >Reporter: Gili > > Following up on https://github.com/querydsl/apt-maven-plugin/issues/56, I am > expecting Maven to fail the build, issue a warning, or allow plugins to do > the same when users pass multiple values for a property that is expecting one > value. > Testcase: https://github.com/querydsl/apt-maven-plugin/issues/56 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6227) Handling multiple tags for a property that is only expecting one value
[
https://issues.apache.org/jira/browse/MNG-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1602#comment-1602
]
Karl Heinz Marbaise commented on MNG-6227:
--
As already mentioned in the comments that there have been several calls to the
{{setProcessor}} method which you can identify in the plugin...why not doing
so? Furthermore what about offering a patch for this?
> Handling multiple tags for a property that is only expecting one value
> --
>
> Key: MNG-6227
> URL: https://issues.apache.org/jira/browse/MNG-6227
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.5.0
>Reporter: Gili
>
> Following up on https://github.com/querydsl/apt-maven-plugin/issues/56, I am
> expecting Maven to fail the build, issue a warning, or allow plugins to do
> the same when users pass multiple values for a property that is expecting one
> value.
> Testcase: https://github.com/querydsl/apt-maven-plugin/issues/56
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MNG-6227) Handling multiple tags for a property that is only expecting one value
Gili created MNG-6227: - Summary: Handling multiple tags for a property that is only expecting one value Key: MNG-6227 URL: https://issues.apache.org/jira/browse/MNG-6227 Project: Maven Issue Type: Bug Components: POM Affects Versions: 3.5.0 Reporter: Gili Following up on https://github.com/querydsl/apt-maven-plugin/issues/56, I am expecting Maven to fail the build, issue a warning, or allow plugins to do the same when users pass multiple values for a property that is expecting one value. Testcase: https://github.com/querydsl/apt-maven-plugin/issues/56 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6218) Jansi 1.13 does not recognize MinGW bash
[ https://issues.apache.org/jira/browse/MNG-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1554#comment-1554 ] Michael Osipov commented on MNG-6218: - I assume so, gboudet restructured the code. Would be nice if [~DannyNullZwo] could confirm this with a custom build. > Jansi 1.13 does not recognize MinGW bash > > > Key: MNG-6218 > URL: https://issues.apache.org/jira/browse/MNG-6218 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.5.0 > Environment: Windows Git Bash(MinGW) >Reporter: Daniel Heinrich >Priority: Minor > Original Estimate: 24h > Remaining Estimate: 24h > > Jansi checks if the platform is Windows to decide if coloring needs to be > handled differently. In the case that MinGW is detected it will handle > coloring as if it was running on Unix. > The test in Jansi 1.13 is if the enviroment variable TERM == "xterm", but > MinGW returns "xterm-256color". > Since Jansi 1.14 it checks if TERM starts with "xterm". > see: > https://github.com/fusesource/jansi/blob/jansi-project-1.14/jansi/src/main/java/org/fusesource/jansi/AnsiConsole.java#L123 > An upgrade to Jansi 1.14 or even 1.15 fixes this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6007) Aether IP Clearance
[ https://issues.apache.org/jira/browse/MNG-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1550#comment-1550 ] Hudson commented on MNG-6007: - SUCCESS: Integrated in Jenkins build maven-resolver #50 (See [https://builds.apache.org/job/maven-resolver/50/]) [MNG-6007] Aether IP Clearance (michaelo: [http://git-wip-us.apache.org/repos/asf/?p=maven-resolver.git&a=commit&h=5fae685d7e581797bed56ebdf3e9970f6cef7146]) * (edit) maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/TrackingFileManager.java > Aether IP Clearance > --- > > Key: MNG-6007 > URL: https://issues.apache.org/jira/browse/MNG-6007 > Project: Maven > Issue Type: Sub-task >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > > see http://incubator.apache.org/ip-clearance/maven-aether.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MRESOLVER-2) Add repository id to TransferResource
[ https://issues.apache.org/jira/browse/MRESOLVER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1545#comment-1545 ] Hudson commented on MRESOLVER-2: SUCCESS: Integrated in Jenkins build maven-resolver #49 (See [https://builds.apache.org/job/maven-resolver/49/]) [MRESOLVER-2] Add repository id to TransferResource (michaelo: [http://git-wip-us.apache.org/repos/asf/?p=maven-resolver.git&a=commit&h=d55d218cf31e4d3f89e9a9117254f082dcbc5d44]) * (edit) maven-resolver-impl/src/test/java/org/eclipse/aether/internal/impl/DefaultChecksumPolicyProviderTest.java * (edit) maven-resolver-impl/src/test/java/org/eclipse/aether/internal/impl/RecordingRepositoryConnector.java * (edit) maven-resolver-connector-basic/src/main/java/org/eclipse/aether/connector/basic/BasicRepositoryConnector.java * (edit) maven-resolver-api/src/main/java/org/eclipse/aether/transfer/TransferResource.java * (edit) maven-resolver-impl/src/test/java/org/eclipse/aether/internal/impl/WarnChecksumPolicyTest.java * (edit) maven-resolver-api/src/test/java/org/eclipse/aether/transfer/TransferEventTest.java * (edit) maven-resolver-impl/src/test/java/org/eclipse/aether/internal/impl/FailChecksumPolicyTest.java > Add repository id to TransferResource > - > > Key: MRESOLVER-2 > URL: https://issues.apache.org/jira/browse/MRESOLVER-2 > Project: Maven Resolver > Issue Type: New Feature > Components: resolver >Affects Versions: Aether 1.0.2, Maven Artifact Resolver 1.0.3 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: Maven Artifact Resolver 1.1.0 > > > Currently, it is impossible to get the repository id the given artifact is > being transfer to/from in a listener, leaving the URL only. When working with > many repository this is cumbersome. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (MNG-6218) Jansi 1.13 does not recognize MinGW bash
[ https://issues.apache.org/jira/browse/MNG-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1541#comment-1541 ] Hervé Boutemy edited comment on MNG-6218 at 5/7/17 4:58 PM: does it mean that JAnsi 1.16 will recognize MinGW bash or not? notice that the good question is not even of recognizing MinGW or not: it is more "will ANSI escape codes work with MinGW bash or not"? If MinGW bash does the ANSI escape codes rendering, the WIndows trick that JAnsi does is not useful was (Author: hboutemy): does it mean that JAnsi 1.16 will recognize MinGW bash or not? I hope so > Jansi 1.13 does not recognize MinGW bash > > > Key: MNG-6218 > URL: https://issues.apache.org/jira/browse/MNG-6218 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.5.0 > Environment: Windows Git Bash(MinGW) >Reporter: Daniel Heinrich >Priority: Minor > Original Estimate: 24h > Remaining Estimate: 24h > > Jansi checks if the platform is Windows to decide if coloring needs to be > handled differently. In the case that MinGW is detected it will handle > coloring as if it was running on Unix. > The test in Jansi 1.13 is if the enviroment variable TERM == "xterm", but > MinGW returns "xterm-256color". > Since Jansi 1.14 it checks if TERM starts with "xterm". > see: > https://github.com/fusesource/jansi/blob/jansi-project-1.14/jansi/src/main/java/org/fusesource/jansi/AnsiConsole.java#L123 > An upgrade to Jansi 1.14 or even 1.15 fixes this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6218) Jansi 1.13 does not recognize MinGW bash
[ https://issues.apache.org/jira/browse/MNG-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1541#comment-1541 ] Hervé Boutemy commented on MNG-6218: does it mean that JAnsi 1.16 will recognize MinGW bash or not? I hope so > Jansi 1.13 does not recognize MinGW bash > > > Key: MNG-6218 > URL: https://issues.apache.org/jira/browse/MNG-6218 > Project: Maven > Issue Type: Bug > Components: Command Line >Affects Versions: 3.5.0 > Environment: Windows Git Bash(MinGW) >Reporter: Daniel Heinrich >Priority: Minor > Original Estimate: 24h > Remaining Estimate: 24h > > Jansi checks if the platform is Windows to decide if coloring needs to be > handled differently. In the case that MinGW is detected it will handle > coloring as if it was running on Unix. > The test in Jansi 1.13 is if the enviroment variable TERM == "xterm", but > MinGW returns "xterm-256color". > Since Jansi 1.14 it checks if TERM starts with "xterm". > see: > https://github.com/fusesource/jansi/blob/jansi-project-1.14/jansi/src/main/java/org/fusesource/jansi/AnsiConsole.java#L123 > An upgrade to Jansi 1.14 or even 1.15 fixes this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MRESOLVER-2) Add repository id to TransferResource
[ https://issues.apache.org/jira/browse/MRESOLVER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MRESOLVER-2. -- Resolution: Fixed > Add repository id to TransferResource > - > > Key: MRESOLVER-2 > URL: https://issues.apache.org/jira/browse/MRESOLVER-2 > Project: Maven Resolver > Issue Type: New Feature > Components: resolver >Affects Versions: Aether 1.0.2, Maven Artifact Resolver 1.0.3 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: Maven Artifact Resolver 1.1.0 > > > Currently, it is impossible to get the repository id the given artifact is > being transfer to/from in a listener, leaving the URL only. When working with > many repository this is cumbersome. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (MRESOLVER-2) Add repository id to TransferResource
[ https://issues.apache.org/jira/browse/MRESOLVER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reopened MRESOLVER-2: > Add repository id to TransferResource > - > > Key: MRESOLVER-2 > URL: https://issues.apache.org/jira/browse/MRESOLVER-2 > Project: Maven Resolver > Issue Type: New Feature > Components: resolver >Affects Versions: Aether 1.0.2, Maven Artifact Resolver 1.0.3 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: Maven Artifact Resolver 1.1.0 > > > Currently, it is impossible to get the repository id the given artifact is > being transfer to/from in a listener, leaving the URL only. When working with > many repository this is cumbersome. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (MRESOLVER-2) Add repository id to TransferResource
[ https://issues.apache.org/jira/browse/MRESOLVER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1526#comment-1526 ] Michael Osipov edited comment on MRESOLVER-2 at 5/7/17 4:53 PM: Fixed with [d55d218cf31e4d3f89e9a9117254f082dcbc5d44|https://git-wip-us.apache.org/repos/asf?p=maven-resolver.git;a=commit;h=d55d218cf31e4d3f89e9a9117254f082dcbc5d44]. was (Author: michael-o): Fixed with [4111830c37fe343a46cf57f654339feb31780c91|https://git-wip-us.apache.org/repos/asf?p=maven-resolver.git;a=commit;h=4111830c37fe343a46cf57f654339feb31780c91]. > Add repository id to TransferResource > - > > Key: MRESOLVER-2 > URL: https://issues.apache.org/jira/browse/MRESOLVER-2 > Project: Maven Resolver > Issue Type: New Feature > Components: resolver >Affects Versions: Aether 1.0.2, Maven Artifact Resolver 1.0.3 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: Maven Artifact Resolver 1.1.0 > > > Currently, it is impossible to get the repository id the given artifact is > being transfer to/from in a listener, leaving the URL only. When working with > many repository this is cumbersome. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MRESOLVER-2) Add repository id to TransferResource
[ https://issues.apache.org/jira/browse/MRESOLVER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MRESOLVER-2. -- Resolution: Fixed Fixed with [4111830c37fe343a46cf57f654339feb31780c91|https://git-wip-us.apache.org/repos/asf?p=maven-resolver.git;a=commit;h=4111830c37fe343a46cf57f654339feb31780c91]. > Add repository id to TransferResource > - > > Key: MRESOLVER-2 > URL: https://issues.apache.org/jira/browse/MRESOLVER-2 > Project: Maven Resolver > Issue Type: New Feature > Components: resolver >Affects Versions: Aether 1.0.2, Maven Artifact Resolver 1.0.3 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: Maven Artifact Resolver 1.1.0 > > > Currently, it is impossible to get the repository id the given artifact is > being transfer to/from in a listener, leaving the URL only. When working with > many repository this is cumbersome. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MRESOLVER-2) Add repository id to TransferResource
[ https://issues.apache.org/jira/browse/MRESOLVER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRESOLVER-2: --- Affects Version/s: Maven Artifact Resolver 1.0.3 > Add repository id to TransferResource > - > > Key: MRESOLVER-2 > URL: https://issues.apache.org/jira/browse/MRESOLVER-2 > Project: Maven Resolver > Issue Type: New Feature > Components: resolver >Affects Versions: Aether 1.0.2, Maven Artifact Resolver 1.0.3 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: Maven Artifact Resolver 1.1.0 > > > Currently, it is impossible to get the repository id the given artifact is > being transfer to/from in a listener, leaving the URL only. When working with > many repository this is cumbersome. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MRESOLVER-2) Add repository id to TransferResource
[ https://issues.apache.org/jira/browse/MRESOLVER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRESOLVER-2: --- Fix Version/s: (was: Maven Artifact Resolver 1.2.0 pre-reset) Maven Artifact Resolver 1.1.0 > Add repository id to TransferResource > - > > Key: MRESOLVER-2 > URL: https://issues.apache.org/jira/browse/MRESOLVER-2 > Project: Maven Resolver > Issue Type: New Feature > Components: resolver >Affects Versions: Aether 1.0.2, Maven Artifact Resolver 1.0.3 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: Maven Artifact Resolver 1.1.0 > > > Currently, it is impossible to get the repository id the given artifact is > being transfer to/from in a listener, leaving the URL only. When working with > many repository this is cumbersome. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (MRESOLVER-2) Add repository id to TransferResource
[ https://issues.apache.org/jira/browse/MRESOLVER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1524#comment-1524 ] Michael Osipov edited comment on MRESOLVER-2 at 5/7/17 4:27 PM: Moving issue to 1.1 as seconded by [~hboutemy] in [MNG-5457|https://issues.apache.org/jira/browse/MNG-5457?focusedCommentId=15987870&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15987870]. was (Author: michael-o): Moving issue to 1.2 as seconded by [~hboutemy] in [MNG-5457|https://issues.apache.org/jira/browse/MNG-5457?focusedCommentId=15987870&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15987870]. > Add repository id to TransferResource > - > > Key: MRESOLVER-2 > URL: https://issues.apache.org/jira/browse/MRESOLVER-2 > Project: Maven Resolver > Issue Type: New Feature > Components: resolver >Affects Versions: Aether 1.0.2, Maven Artifact Resolver 1.0.3 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: Maven Artifact Resolver 1.1.0 > > > Currently, it is impossible to get the repository id the given artifact is > being transfer to/from in a listener, leaving the URL only. When working with > many repository this is cumbersome. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (MRESOLVER-2) Add repository id to TransferResource
[ https://issues.apache.org/jira/browse/MRESOLVER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reopened MRESOLVER-2: Moving issue to 1.2 as seconded by [~hboutemy] in [MNG-5457|https://issues.apache.org/jira/browse/MNG-5457?focusedCommentId=15987870&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15987870]. > Add repository id to TransferResource > - > > Key: MRESOLVER-2 > URL: https://issues.apache.org/jira/browse/MRESOLVER-2 > Project: Maven Resolver > Issue Type: New Feature > Components: resolver >Affects Versions: Aether 1.0.2 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: Maven Artifact Resolver 1.2.0 pre-reset > > > Currently, it is impossible to get the repository id the given artifact is > being transfer to/from in a listener, leaving the URL only. When working with > many repository this is cumbersome. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MRESOLVER-13) Exceptions are suppressed incorrectly when closing resources fails
[ https://issues.apache.org/jira/browse/MRESOLVER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MRESOLVER-13. --- Resolution: Fixed Assignee: Christian Schulte Already fixed by Christian. > Exceptions are suppressed incorrectly when closing resources fails > -- > > Key: MRESOLVER-13 > URL: https://issues.apache.org/jira/browse/MRESOLVER-13 > Project: Maven Resolver > Issue Type: Bug >Affects Versions: Maven Artifact Resolver 1.0.3 >Reporter: Christian Schulte >Assignee: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MRESOLVER-13) Exceptions are suppressed incorrectly when closing resources fails.
[ https://issues.apache.org/jira/browse/MRESOLVER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRESOLVER-13: Affects Version/s: Maven Artifact Resolver 1.0.3 > Exceptions are suppressed incorrectly when closing resources fails. > --- > > Key: MRESOLVER-13 > URL: https://issues.apache.org/jira/browse/MRESOLVER-13 > Project: Maven Resolver > Issue Type: Bug >Affects Versions: Maven Artifact Resolver 1.0.3 >Reporter: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (MRESOLVER-13) Exceptions are suppressed incorrectly when closing resources fails.
[ https://issues.apache.org/jira/browse/MRESOLVER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reopened MRESOLVER-13: - > Exceptions are suppressed incorrectly when closing resources fails. > --- > > Key: MRESOLVER-13 > URL: https://issues.apache.org/jira/browse/MRESOLVER-13 > Project: Maven Resolver > Issue Type: Bug >Affects Versions: Maven Artifact Resolver 1.0.3 >Reporter: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MRESOLVER-13) Exceptions are suppressed incorrectly when closing resources fails
[ https://issues.apache.org/jira/browse/MRESOLVER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRESOLVER-13: Summary: Exceptions are suppressed incorrectly when closing resources fails (was: Exceptions are suppressed incorrectly when closing resources fails.) > Exceptions are suppressed incorrectly when closing resources fails > -- > > Key: MRESOLVER-13 > URL: https://issues.apache.org/jira/browse/MRESOLVER-13 > Project: Maven Resolver > Issue Type: Bug >Affects Versions: Maven Artifact Resolver 1.0.3 >Reporter: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MRESOLVER-14) Statistics should be calculated using System.nanoTime() instead of System.currentTimeMillis()
[
https://issues.apache.org/jira/browse/MRESOLVER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MRESOLVER-14:
Summary: Statistics should be calculated using System.nanoTime() instead of
System.currentTimeMillis() (was: Statistics should be calculated using
System.nanoTime instead of System.currentTimeMillis.)
> Statistics should be calculated using System.nanoTime() instead of
> System.currentTimeMillis()
> -
>
> Key: MRESOLVER-14
> URL: https://issues.apache.org/jira/browse/MRESOLVER-14
> Project: Maven Resolver
> Issue Type: Improvement
>Affects Versions: Maven Artifact Resolver 1.0.3
>Reporter: Christian Schulte
> Fix For: Maven Artifact Resolver 1.1.0
>
>
> {{System.currentTimeMillis()}} is prone to clock changes whereas
> {{System.nanoTime()}} is not. All stats duration shall resolve in nanosecond
> precision.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (MRESOLVER-14) Statistics should be calculated using System.nanoTime() instead of System.currentTimeMillis()
[
https://issues.apache.org/jira/browse/MRESOLVER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRESOLVER-14.
---
Resolution: Fixed
Assignee: Christian Schulte
Already fixed by Christian.
> Statistics should be calculated using System.nanoTime() instead of
> System.currentTimeMillis()
> -
>
> Key: MRESOLVER-14
> URL: https://issues.apache.org/jira/browse/MRESOLVER-14
> Project: Maven Resolver
> Issue Type: Improvement
>Affects Versions: Maven Artifact Resolver 1.0.3
>Reporter: Christian Schulte
>Assignee: Christian Schulte
> Fix For: Maven Artifact Resolver 1.1.0
>
>
> {{System.currentTimeMillis()}} is prone to clock changes whereas
> {{System.nanoTime()}} is not. All stats duration shall resolve in nanosecond
> precision.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MRESOLVER-14) Statistics should be calculated using System.nanoTime instead of System.currentTimeMillis.
[
https://issues.apache.org/jira/browse/MRESOLVER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MRESOLVER-14:
Description: {{System.currentTimeMillis()}} is prone to clock changes
whereas {{System.nanoTime()}} is not. All stats duration shall resolve in
nanosecond precision.
> Statistics should be calculated using System.nanoTime instead of
> System.currentTimeMillis.
> --
>
> Key: MRESOLVER-14
> URL: https://issues.apache.org/jira/browse/MRESOLVER-14
> Project: Maven Resolver
> Issue Type: Improvement
>Affects Versions: Maven Artifact Resolver 1.0.3
>Reporter: Christian Schulte
> Fix For: Maven Artifact Resolver 1.1.0
>
>
> {{System.currentTimeMillis()}} is prone to clock changes whereas
> {{System.nanoTime()}} is not. All stats duration shall resolve in nanosecond
> precision.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MRESOLVER-14) Statistics should be calculated using System.nanoTime instead of System.currentTimeMillis.
[ https://issues.apache.org/jira/browse/MRESOLVER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRESOLVER-14: Issue Type: Improvement (was: Bug) > Statistics should be calculated using System.nanoTime instead of > System.currentTimeMillis. > -- > > Key: MRESOLVER-14 > URL: https://issues.apache.org/jira/browse/MRESOLVER-14 > Project: Maven Resolver > Issue Type: Improvement >Affects Versions: Maven Artifact Resolver 1.0.3 >Reporter: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MRESOLVER-14) Statistics should be calculated using System.nanoTime instead of System.currentTimeMillis.
[ https://issues.apache.org/jira/browse/MRESOLVER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRESOLVER-14: Affects Version/s: Maven Artifact Resolver 1.0.3 > Statistics should be calculated using System.nanoTime instead of > System.currentTimeMillis. > -- > > Key: MRESOLVER-14 > URL: https://issues.apache.org/jira/browse/MRESOLVER-14 > Project: Maven Resolver > Issue Type: Bug >Affects Versions: Maven Artifact Resolver 1.0.3 >Reporter: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (MRESOLVER-14) Statistics should be calculated using System.nanoTime instead of System.currentTimeMillis.
[ https://issues.apache.org/jira/browse/MRESOLVER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reopened MRESOLVER-14: - > Statistics should be calculated using System.nanoTime instead of > System.currentTimeMillis. > -- > > Key: MRESOLVER-14 > URL: https://issues.apache.org/jira/browse/MRESOLVER-14 > Project: Maven Resolver > Issue Type: Bug >Affects Versions: Maven Artifact Resolver 1.0.3 >Reporter: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MRESOLVER-11) Project dependency collection result should contain repositories.
[ https://issues.apache.org/jira/browse/MRESOLVER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MRESOLVER-11. --- Resolution: Fixed Assignee: Christian Schulte Issue has already been fixed by Christian. > Project dependency collection result should contain repositories. > - > > Key: MRESOLVER-11 > URL: https://issues.apache.org/jira/browse/MRESOLVER-11 > Project: Maven Resolver > Issue Type: Improvement >Affects Versions: Maven Artifact Resolver 1.0.3 >Reporter: Christian Schulte >Assignee: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > > The resolution result provided when performing project dependency collection > is lacking the repositories from the collection request. Components the > project root node is passed to (transformers, for example), expect this > information to be provided. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MRESOLVER-11) Project dependency collection result should contain repositories.
[ https://issues.apache.org/jira/browse/MRESOLVER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRESOLVER-11: Issue Type: Improvement (was: Bug) > Project dependency collection result should contain repositories. > - > > Key: MRESOLVER-11 > URL: https://issues.apache.org/jira/browse/MRESOLVER-11 > Project: Maven Resolver > Issue Type: Improvement >Affects Versions: Maven Artifact Resolver 1.0.3 >Reporter: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > > The resolution result provided when performing project dependency collection > is lacking the repositories from the collection request. Components the > project root node is passed to (transformers, for example), expect this > information to be provided. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MRESOLVER-11) Project dependency collection result should contain repositories.
[ https://issues.apache.org/jira/browse/MRESOLVER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MRESOLVER-11: Affects Version/s: Maven Artifact Resolver 1.0.3 > Project dependency collection result should contain repositories. > - > > Key: MRESOLVER-11 > URL: https://issues.apache.org/jira/browse/MRESOLVER-11 > Project: Maven Resolver > Issue Type: Bug >Affects Versions: Maven Artifact Resolver 1.0.3 >Reporter: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > > The resolution result provided when performing project dependency collection > is lacking the repositories from the collection request. Components the > project root node is passed to (transformers, for example), expect this > information to be provided. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (MRESOLVER-11) Project dependency collection result should contain repositories.
[ https://issues.apache.org/jira/browse/MRESOLVER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reopened MRESOLVER-11: - Reopening to change values. > Project dependency collection result should contain repositories. > - > > Key: MRESOLVER-11 > URL: https://issues.apache.org/jira/browse/MRESOLVER-11 > Project: Maven Resolver > Issue Type: Bug >Reporter: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > > The resolution result provided when performing project dependency collection > is lacking the repositories from the collection request. Components the > project root node is passed to (transformers, for example), expect this > information to be provided. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MDEP-566) Upgrade maven-common-artifact-filter to version 3.0.1
[ https://issues.apache.org/jira/browse/MDEP-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1510#comment-1510 ] Hudson commented on MDEP-566: - FAILURE: Integrated in Jenkins build maven-plugins #8954 (See [https://builds.apache.org/job/maven-plugins/8954/]) [MDEP-566] Upgrade maven-common-artifact-filter to version 3.0.1 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1794210]) * (edit) maven-dependency-plugin/pom.xml > Upgrade maven-common-artifact-filter to version 3.0.1 > - > > Key: MDEP-566 > URL: https://issues.apache.org/jira/browse/MDEP-566 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.1 > > > Upgrade to version 3.0.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MDEP-567) Upgrade to maven-dependency-tree to 3.0.1
Karl Heinz Marbaise created MDEP-567: Summary: Upgrade to maven-dependency-tree to 3.0.1 Key: MDEP-567 URL: https://issues.apache.org/jira/browse/MDEP-567 Project: Maven Dependency Plugin Issue Type: Improvement Affects Versions: 3.0.1 Reporter: Karl Heinz Marbaise Priority: Blocker Fix For: 3.0.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MDEP-566) Upgrade maven-common-artifact-filter to version 3.0.1
[ https://issues.apache.org/jira/browse/MDEP-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEP-566. Resolution: Fixed Done in [r1794210|https://svn.apache.org/r1794210] > Upgrade maven-common-artifact-filter to version 3.0.1 > - > > Key: MDEP-566 > URL: https://issues.apache.org/jira/browse/MDEP-566 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.1 > > > Upgrade to version 3.0.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MDEP-566) Upgrade maven-common-artifact-filter to version 3.0.1
Karl Heinz Marbaise created MDEP-566: Summary: Upgrade maven-common-artifact-filter to version 3.0.1 Key: MDEP-566 URL: https://issues.apache.org/jira/browse/MDEP-566 Project: Maven Dependency Plugin Issue Type: Improvement Affects Versions: 3.0.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Minor Fix For: 3.0.1 Upgrade to version 3.0.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6218) Jansi 1.13 does not recognize MinGW bash
[
https://issues.apache.org/jira/browse/MNG-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999884#comment-15999884
]
Michael Osipov commented on MNG-6218:
-
The {{xterm}} check is competely gone with 1.16. See:
https://github.com/fusesource/jansi/issues/83
> Jansi 1.13 does not recognize MinGW bash
>
>
> Key: MNG-6218
> URL: https://issues.apache.org/jira/browse/MNG-6218
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Windows Git Bash(MinGW)
>Reporter: Daniel Heinrich
>Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Jansi checks if the platform is Windows to decide if coloring needs to be
> handled differently. In the case that MinGW is detected it will handle
> coloring as if it was running on Unix.
> The test in Jansi 1.13 is if the enviroment variable TERM == "xterm", but
> MinGW returns "xterm-256color".
> Since Jansi 1.14 it checks if TERM starts with "xterm".
> see:
> https://github.com/fusesource/jansi/blob/jansi-project-1.14/jansi/src/main/java/org/fusesource/jansi/AnsiConsole.java#L123
> An upgrade to Jansi 1.14 or even 1.15 fixes this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MDEP-565) Upgrade maven-artifact-transfer to version 0.9.1
[ https://issues.apache.org/jira/browse/MDEP-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDEP-565: - Affects Version/s: (was: 3.0.0) 3.0.1 > Upgrade maven-artifact-transfer to version 0.9.1 > > > Key: MDEP-565 > URL: https://issues.apache.org/jira/browse/MDEP-565 > Project: Maven Dependency Plugin > Issue Type: Bug >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.1 > > > The version 0.9.1 of the maven-artifact-transfer contains a [fix for Maven > 3.0|MSHARED-602] which should be part of this release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Moved] (MDEP-565) Upgrade maven-artifact-transfer to version 0.9.1
[ https://issues.apache.org/jira/browse/MDEP-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise moved MDEPLOY-220 to MDEP-565: -- Fix Version/s: (was: 3.0.0) 3.0.0 Affects Version/s: (was: 3.0.0) 3.0.0 Key: MDEP-565 (was: MDEPLOY-220) Project: Maven Dependency Plugin (was: Maven Deploy Plugin) > Upgrade maven-artifact-transfer to version 0.9.1 > > > Key: MDEP-565 > URL: https://issues.apache.org/jira/browse/MDEP-565 > Project: Maven Dependency Plugin > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > > The version 0.9.1 of the maven-artifact-transfer contains a [fix for Maven > 3.0|MSHARED-602] which should be part of this release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MDEP-565) Upgrade maven-artifact-transfer to version 0.9.1
[ https://issues.apache.org/jira/browse/MDEP-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDEP-565: - Fix Version/s: (was: 3.0.0) 3.0.1 > Upgrade maven-artifact-transfer to version 0.9.1 > > > Key: MDEP-565 > URL: https://issues.apache.org/jira/browse/MDEP-565 > Project: Maven Dependency Plugin > Issue Type: Bug >Affects Versions: 3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.1 > > > The version 0.9.1 of the maven-artifact-transfer contains a [fix for Maven > 3.0|MSHARED-602] which should be part of this release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MDEPLOY-220) Upgrade maven-artifact-transfer to version 0.9.1
Karl Heinz Marbaise created MDEPLOY-220: --- Summary: Upgrade maven-artifact-transfer to version 0.9.1 Key: MDEPLOY-220 URL: https://issues.apache.org/jira/browse/MDEPLOY-220 Project: Maven Deploy Plugin Issue Type: Bug Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Blocker Fix For: 3.0.0 The version 0.9.1 of the maven-artifact-transfer contains a [fix for Maven 3.0|MSHARED-602] which should be part of this release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MSHARED-637) Remove IOException from ProjectDeployer cause it's not thrown by the code
[
https://issues.apache.org/jira/browse/MSHARED-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999842#comment-15999842
]
Hudson commented on MSHARED-637:
SUCCESS: Integrated in Jenkins build maven-shared #3729 (See
[https://builds.apache.org/job/maven-shared/3729/])
[MSHARED-637] Remove IOException from ProjectDeployer cause it's not thrown by
the code
o Fixed duplicated license header ProjectDeployer.
o Changed the deploy() method and removed IOException and added
IllegalArgumentException (khmarbaise:
[http://svn.apache.org/viewvc/?view=rev&rev=1794196])
* (edit)
maven-artifact-transfer/src/main/java/org/apache/maven/shared/project/deploy/ProjectDeployer.java
* (edit)
maven-artifact-transfer/src/main/java/org/apache/maven/shared/project/deploy/internal/DefaultProjectDeployer.java
> Remove IOException from ProjectDeployer cause it's not thrown by the code
> -
>
> Key: MSHARED-637
> URL: https://issues.apache.org/jira/browse/MSHARED-637
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: maven-artifact-transfer-0.9.1
>
>
> Remove the IOException from the ProjectDeploy.deploy() interface cause it is
> not thrown by the code.
> Need to add the {{IllegalArgumentException}} in cases where no main artifact
> is assigned to the interface.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MDEPLOY-219) Upgrade maven-artifact-transfer to version 0.9.1
Karl Heinz Marbaise created MDEPLOY-219: --- Summary: Upgrade maven-artifact-transfer to version 0.9.1 Key: MDEPLOY-219 URL: https://issues.apache.org/jira/browse/MDEPLOY-219 Project: Maven Deploy Plugin Issue Type: Bug Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Blocker Fix For: 3.0.0 The version 0.9.1 of the maven-artifact-transfer contains a [fix for Maven 3.0|MSHARED-602] which should be part of this release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MSHARED-637) Remove IOException from ProjectDeployer cause it's not thrown by the code
[
https://issues.apache.org/jira/browse/MSHARED-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MSHARED-637.
---
Resolution: Fixed
Fixed in [r1794196|https://svn.apache.org/r1794196]
> Remove IOException from ProjectDeployer cause it's not thrown by the code
> -
>
> Key: MSHARED-637
> URL: https://issues.apache.org/jira/browse/MSHARED-637
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: maven-artifact-transfer-0.9.1
>
>
> Remove the IOException from the ProjectDeploy.deploy() interface cause it is
> not thrown by the code.
> Need to add the {{IllegalArgumentException}} in cases where no main artifact
> is assigned to the interface.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MSHARED-637) Remove IOException from ProjectDeployer cause it's not thrown by the code
[
https://issues.apache.org/jira/browse/MSHARED-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MSHARED-637:
Description:
Remove the IOException from the ProjectDeploy.deploy() interface cause it is
not thrown by the code.
Need to add the {{IllegalArgumentException}} in cases where no main artifact is
assigned to the interface.
was:Remove the IOException from the ProjectDeploy.deploy() interface cause it
is not thrown by the code.
> Remove IOException from ProjectDeployer cause it's not thrown by the code
> -
>
> Key: MSHARED-637
> URL: https://issues.apache.org/jira/browse/MSHARED-637
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: maven-artifact-transfer-0.9.1
>
>
> Remove the IOException from the ProjectDeploy.deploy() interface cause it is
> not thrown by the code.
> Need to add the {{IllegalArgumentException}} in cases where no main artifact
> is assigned to the interface.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MSHARED-637) Remove IOException from ProjectDeployer cause it's not thrown by the code
Karl Heinz Marbaise created MSHARED-637: --- Summary: Remove IOException from ProjectDeployer cause it's not thrown by the code Key: MSHARED-637 URL: https://issues.apache.org/jira/browse/MSHARED-637 Project: Maven Shared Components Issue Type: Improvement Components: maven-artifact-transfer Affects Versions: maven-artifact-transfer-0.9.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Minor Fix For: maven-artifact-transfer-0.9.1 Remove the IOException from the ProjectDeploy.deploy() interface cause it is not thrown by the code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
