[jira] [Created] (ARCHETYPE-528) Archetype:generate from repos besides central does not work
João Cabrita created ARCHETYPE-528:
--
Summary: Archetype:generate from repos besides central does not
work
Key: ARCHETYPE-528
URL: https://issues.apache.org/jira/browse/ARCHETYPE-528
Project: Maven Archetype
Issue Type: Bug
Affects Versions: 3.0.1
Reporter: João Cabrita
Priority: Critical
Attachments: settings.xml
{noformat}
mvn -X -P camunda -DarchetypeCatalog=remote
org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate
-Dfilter=org.camunda.bpm.archetype:
{noformat}
Results in the following:
{noformat}
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate' with basic
configurator -->
[DEBUG] (f) archetypeCatalog = remote
[DEBUG] (f) basedir = C:\Users\joao.cabrita\projects\bpm
[DEBUG] (f) filter = org.camunda.bpm.archetype:
[DEBUG] (f) interactiveMode = true
[DEBUG] (f) localRepository = id: local
url: file:///C:/Users/joao.cabrita/.m2/repository/
layout: default
snapshots: [enabled => true, update => always]
releases: [enabled => true, update => always]
[DEBUG] (f) remoteArtifactRepositories = [ id: central
url: https://repo.maven.apache.org/maven2
layout: default
proxy: proxy.brisa.pt:3128
snapshots: [enabled => false, update => daily]
releases: [enabled => true, update => daily]
]
[DEBUG] (f) session = org.apache.maven.execution.MavenSession@408613cc
[DEBUG] -- end configuration --
[INFO] Generating project in Interactive mode
[DEBUG] Searching for remote catalog:
https://repo.maven.apache.org/maven2/archetype-catalog.xml
[WARNING] No archetype found in remote catalog. Defaulting to internal catalog
[INFO] Your filter doesn't match any archetype, so try again with another value.
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
I've attached my settings.xml file.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ARCHETYPE-528) Archetype:generate from repos besides central does not work
[
https://issues.apache.org/jira/browse/ARCHETYPE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
João Cabrita updated ARCHETYPE-528:
---
Description:
{noformat}
mvn -X -P camunda -DarchetypeCatalog=remote
org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate
-Dfilter=org.camunda.bpm.archetype:
{noformat}
Results in the following:
{noformat}
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate' with basic
configurator -->
[DEBUG] (f) archetypeCatalog = remote
[DEBUG] (f) basedir = C:\Users\joao.cabrita\projects\bpm
[DEBUG] (f) filter = org.camunda.bpm.archetype:
[DEBUG] (f) interactiveMode = true
[DEBUG] (f) localRepository = id: local
url: file:///C:/Users/joao.cabrita/.m2/repository/
layout: default
snapshots: [enabled => true, update => always]
releases: [enabled => true, update => always]
[DEBUG] (f) remoteArtifactRepositories = [ id: central
url: https://app.camunda.com/nexus/content/repositories/camunda-bpm
layout: default
proxy: proxy.brisa.pt:3128
snapshots: [enabled => true, update => daily]
releases: [enabled => true, update => daily]
, id: archetype
url: https://app.camunda.com/nexus/content/repositories/camunda-bpm
layout: default
proxy: proxy.brisa.pt:3128
snapshots: [enabled => true, update => daily]
releases: [enabled => true, update => daily]
]
[DEBUG] (f) session = org.apache.maven.execution.MavenSession@325f7fa9
[DEBUG] -- end configuration --
[INFO] Generating project in Interactive mode
[DEBUG] Searching for remote catalog:
https://repo.maven.apache.org/maven2/archetype-catalog.xml
[WARNING] No archetype found in remote catalog. Defaulting to internal catalog
[INFO] Your filter doesn't match any archetype, so try again with another value.
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
I've attached my settings.xml file.
was:
{noformat}
mvn -X -P camunda -DarchetypeCatalog=remote
org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate
-Dfilter=org.camunda.bpm.archetype:
{noformat}
Results in the following:
{noformat}
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate' with basic
configurator -->
[DEBUG] (f) archetypeCatalog = remote
[DEBUG] (f) basedir = C:\Users\joao.cabrita\projects\bpm
[DEBUG] (f) filter = org.camunda.bpm.archetype:
[DEBUG] (f) interactiveMode = true
[DEBUG] (f) localRepository = id: local
url: file:///C:/Users/joao.cabrita/.m2/repository/
layout: default
snapshots: [enabled => true, update => always]
releases: [enabled => true, update => always]
[DEBUG] (f) remoteArtifactRepositories = [ id: central
url: https://repo.maven.apache.org/maven2
layout: default
proxy: proxy.brisa.pt:3128
snapshots: [enabled => false, update => daily]
releases: [enabled => true, update => daily]
]
[DEBUG] (f) session = org.apache.maven.execution.MavenSession@408613cc
[DEBUG] -- end configuration --
[INFO] Generating project in Interactive mode
[DEBUG] Searching for remote catalog:
https://repo.maven.apache.org/maven2/archetype-catalog.xml
[WARNING] No archetype found in remote catalog. Defaulting to internal catalog
[INFO] Your filter doesn't match any archetype, so try again with another value.
[INFO]
[INFO] BUILD SUCCESS
[INFO]
{noformat}
I've attached my settings.xml file.
> Archetype:generate from repos besides central does not work
> ---
>
> Key: ARCHETYPE-528
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-528
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: João Cabrita
>Priority: Critical
> Attachments: settings.xml
>
>
> {noformat}
> mvn -X -P camunda -DarchetypeCatalog=remote
> org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate
> -Dfilter=org.camunda.bpm.archetype:
> {noformat}
> Results in the following:
> {noformat}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate' with basic
> configurator -->
> [DEBUG] (f) archetypeCatalog = remote
> [DEBUG] (f) basedir = C:\Users\joao.cabrita\projects\bpm
> [DEBUG] (f) filter = org.camunda.bpm.archetype:
> [DEBUG] (f) interactiveMode = true
> [DEBUG] (f) localRepository = id: local
> url: file:///C:/Users/joao.cabrita/.m2/repository/
>layout: default
> snapshots: [enabled => true, update => always]
> releases: [enabled => true, update => always]
> [DEBUG] (f) remoteArtifactRepositories = [
[jira] [Commented] (ARCHETYPE-528) Archetype:generate from repos besides central does not work
[
https://issues.apache.org/jira/browse/ARCHETYPE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024453#comment-16024453
]
João Cabrita commented on ARCHETYPE-528:
Using the (undocumented)
-DarchetypeRepository=https://app.camunda.com/nexus/content/repositories/camunda-bpm/
works...
> Archetype:generate from repos besides central does not work
> ---
>
> Key: ARCHETYPE-528
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-528
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: João Cabrita
>Priority: Critical
> Attachments: settings.xml
>
>
> {noformat}
> mvn -X -P camunda -DarchetypeCatalog=remote
> org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate
> -Dfilter=org.camunda.bpm.archetype:
> {noformat}
> Results in the following:
> {noformat}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-archetype-plugin:3.0.1:generate' with basic
> configurator -->
> [DEBUG] (f) archetypeCatalog = remote
> [DEBUG] (f) basedir = C:\Users\joao.cabrita\projects\bpm
> [DEBUG] (f) filter = org.camunda.bpm.archetype:
> [DEBUG] (f) interactiveMode = true
> [DEBUG] (f) localRepository = id: local
> url: file:///C:/Users/joao.cabrita/.m2/repository/
>layout: default
> snapshots: [enabled => true, update => always]
> releases: [enabled => true, update => always]
> [DEBUG] (f) remoteArtifactRepositories = [ id: central
> url: https://app.camunda.com/nexus/content/repositories/camunda-bpm
>layout: default
> proxy: proxy.brisa.pt:3128
> snapshots: [enabled => true, update => daily]
> releases: [enabled => true, update => daily]
> , id: archetype
> url: https://app.camunda.com/nexus/content/repositories/camunda-bpm
>layout: default
> proxy: proxy.brisa.pt:3128
> snapshots: [enabled => true, update => daily]
> releases: [enabled => true, update => daily]
> ]
> [DEBUG] (f) session = org.apache.maven.execution.MavenSession@325f7fa9
> [DEBUG] -- end configuration --
> [INFO] Generating project in Interactive mode
> [DEBUG] Searching for remote catalog:
> https://repo.maven.apache.org/maven2/archetype-catalog.xml
> [WARNING] No archetype found in remote catalog. Defaulting to internal catalog
> [INFO] Your filter doesn't match any archetype, so try again with another
> value.
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {noformat}
> I've attached my settings.xml file.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MCHECKSTYLE-338) Add support for 'omitIgnoredModules'
richard created MCHECKSTYLE-338: --- Summary: Add support for 'omitIgnoredModules' Key: MCHECKSTYLE-338 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-338 Project: Maven Checkstyle Plugin Issue Type: Improvement Components: checkstyle:check Affects Versions: 2.17 Environment: Windows 7, 64 bit Reporter: richard Checkstyle has an option in it's ant process that allows users to avoid executing modules that have a severity set to ignore. It is called `omitIgnoredModules`. It has been in checkstyle already for atleast 2 years. See: https://github.com/checkstyle/checkstyle/blob/2f3f4b76f04f0b5071abcaed54648a49a0db3160/src/main/java/com/puppycrawl/tools/checkstyle/ant/CheckstyleAntTask.java#L118 https://github.com/checkstyle/checkstyle/blob/2f3f4b76f04f0b5071abcaed54648a49a0db3160/src/main/java/com/puppycrawl/tools/checkstyle/ant/CheckstyleAntTask.java#L424-L428 We are in the process of adding this option to our CLI (https://github.com/checkstyle/checkstyle/issues/3566) and would like to see maven-checkstyle-plugin support this feature so users can customize it. A simple tag for this option like: `false` would be enough. Thanks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6236) maven-metadata-local.xml polluted with whitespaces
[ https://issues.apache.org/jira/browse/MNG-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomer Cohen updated MNG-6236: - Attachment: (was: maven-metadata-local.xml) > maven-metadata-local.xml polluted with whitespaces > -- > > Key: MNG-6236 > URL: https://issues.apache.org/jira/browse/MNG-6236 > Project: Maven > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Tomer Cohen > Attachments: maven-metadata-local.xml, stacktrace.txt > > > After starting to use Maven 3.5.0 multiple instances of the attached > exceptions started occurring when multiple builds are using and installing > modules of the same reactor. I sanitized the module name. > Maven 3.3.9 did not have this issue -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6236) maven-metadata-local.xml polluted with whitespaces
[ https://issues.apache.org/jira/browse/MNG-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomer Cohen updated MNG-6236: - Attachment: maven-metadata-local.xml > maven-metadata-local.xml polluted with whitespaces > -- > > Key: MNG-6236 > URL: https://issues.apache.org/jira/browse/MNG-6236 > Project: Maven > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Tomer Cohen > Attachments: maven-metadata-local.xml, stacktrace.txt > > > After starting to use Maven 3.5.0 multiple instances of the attached > exceptions started occurring when multiple builds are using and installing > modules of the same reactor. I sanitized the module name. > Maven 3.3.9 did not have this issue -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6236) maven-metadata-local.xml polluted with whitespaces
[ https://issues.apache.org/jira/browse/MNG-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025080#comment-16025080 ] Tomer Cohen commented on MNG-6236: -- oye vey my bad! I corrected it with the proper corruct file. Throwing away does work, but since it happens spontaneously it can be quite annoying. > maven-metadata-local.xml polluted with whitespaces > -- > > Key: MNG-6236 > URL: https://issues.apache.org/jira/browse/MNG-6236 > Project: Maven > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Tomer Cohen > Attachments: maven-metadata-local.xml, stacktrace.txt > > > After starting to use Maven 3.5.0 multiple instances of the attached > exceptions started occurring when multiple builds are using and installing > modules of the same reactor. I sanitized the module name. > Maven 3.3.9 did not have this issue -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6236) maven-metadata-local.xml polluted with whitespaces
[
https://issues.apache.org/jira/browse/MNG-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025114#comment-16025114
]
Michael Osipov commented on MNG-6236:
-
Got it, this is one seriously broken. It is not polluted with whitespace but
really really broken:
{code:xml}
BLABLA
BLABLA
18.0-SNAPSHOT
true
20170525173245
jar
18.0-SNAPSHOT
20170525173245
pom
18.0-SNAPSHOT
20170525173245
/classifier>
jar
18.0-SNAPSHOT
20170525173240
{code}
Can you anyhow provide a way to reproduce it otherwise I won't be even able to
take a look at the cause.
> maven-metadata-local.xml polluted with whitespaces
> --
>
> Key: MNG-6236
> URL: https://issues.apache.org/jira/browse/MNG-6236
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Tomer Cohen
> Attachments: maven-metadata-local.xml, stacktrace.txt
>
>
> After starting to use Maven 3.5.0 multiple instances of the attached
> exceptions started occurring when multiple builds are using and installing
> modules of the same reactor. I sanitized the module name.
> Maven 3.3.9 did not have this issue
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (MNG-6236) maven-metadata-local.xml polluted with whitespaces
[
https://issues.apache.org/jira/browse/MNG-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025114#comment-16025114
]
Michael Osipov edited comment on MNG-6236 at 5/25/17 5:57 PM:
--
Got it, this is one seriously broken. It is not polluted with whitespace but
really really broken:
{code:xml}
BLABLA
BLABLA
18.0-SNAPSHOT
true
20170525173245
jar
18.0-SNAPSHOT
20170525173245
pom
18.0-SNAPSHOT
20170525173245
/classifier>
jar
18.0-SNAPSHOT
20170525173240
{code}
Can you anyhow provide a way to reproduce it otherwise I won't be even able to
take a look at the cause?! Please provide the full logfile with {{-X}},
sanitize private information.
was (Author: michael-o):
Got it, this is one seriously broken. It is not polluted with whitespace but
really really broken:
{code:xml}
BLABLA
BLABLA
18.0-SNAPSHOT
true
20170525173245
jar
18.0-SNAPSHOT
20170525173245
pom
18.0-SNAPSHOT
20170525173245
/classifier>
jar
18.0-SNAPSHOT
20170525173240
{code}
Can you anyhow provide a way to reproduce it otherwise I won't be even able to
take a look at the cause.
> maven-metadata-local.xml polluted with whitespaces
> --
>
> Key: MNG-6236
> URL: https://issues.apache.org/jira/browse/MNG-6236
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Tomer Cohen
> Attachments: maven-metadata-local.xml, stacktrace.txt
>
>
> After starting to use Maven 3.5.0 multiple instances of the attached
> exceptions started occurring when multiple builds are using and installing
> modules of the same reactor. I sanitized the module name.
> Maven 3.3.9 did not have this issue
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6084) Support JSR 250 annotations
[ https://issues.apache.org/jira/browse/MNG-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6084: Fix Version/s: (was: 3.5.1-candidate) 3.5.1 > Support JSR 250 annotations > --- > > Key: MNG-6084 > URL: https://issues.apache.org/jira/browse/MNG-6084 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.3.9 >Reporter: Dan Tran >Assignee: Dan Tran > Fix For: 3.5.1 > > > JSR330 ( @Named, @Singeton, etc) currently supported for plugin development. > Would like to see JSR250 as well(@PostConstruct, etc) > Detail discussion is at > http://maven.40175.n5.nabble.com/Maven-Plugin-and-JSR330-td5879508.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MNG-6084) Support JSR 250 annotations
[ https://issues.apache.org/jira/browse/MNG-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6084. --- Resolution: Fixed Fixed with [a7dddcb87626fec256f1b8ccbe957f94cdf401e4|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=a7dddcb87626fec256f1b8ccbe957f94cdf401e4]. > Support JSR 250 annotations > --- > > Key: MNG-6084 > URL: https://issues.apache.org/jira/browse/MNG-6084 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.3.9 >Reporter: Dan Tran >Assignee: Dan Tran > Fix For: 3.5.1 > > > JSR330 ( @Named, @Singeton, etc) currently supported for plugin development. > Would like to see JSR250 as well(@PostConstruct, etc) > Detail discussion is at > http://maven.40175.n5.nabble.com/Maven-Plugin-and-JSR330-td5879508.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (MNG-6164) Collections inconsistently immutable.
[
https://issues.apache.org/jira/browse/MNG-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MNG-6164:
---
Assignee: Michael Osipov
> Collections inconsistently immutable.
> -
>
> Key: MNG-6164
> URL: https://issues.apache.org/jira/browse/MNG-6164
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: 3.5.1-candidate
>
>
> There are plenty of places where empty collections are returned from public
> API methods like:
> {code}
> public List getExceptions()
> {
> return exceptions == null ? Collections. emptyList() :
> exceptions;
> }
> {code}
> The issue with this is that the empty list is immutable but the collection
> returned for the nun-null case is not immutable. All those methods should
> return an immutable collection consistently.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MNG-6164) Collections inconsistently immutable
[
https://issues.apache.org/jira/browse/MNG-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6164:
Summary: Collections inconsistently immutable (was: Collections
inconsistently immutable.)
> Collections inconsistently immutable
>
>
> Key: MNG-6164
> URL: https://issues.apache.org/jira/browse/MNG-6164
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: 3.5.1-candidate
>
>
> There are plenty of places where empty collections are returned from public
> API methods like:
> {code}
> public List getExceptions()
> {
> return exceptions == null ? Collections. emptyList() :
> exceptions;
> }
> {code}
> The issue with this is that the empty list is immutable but the collection
> returned for the nun-null case is not immutable. All those methods should
> return an immutable collection consistently.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MNG-6084) Support JSR 250 annotations
[ https://issues.apache.org/jira/browse/MNG-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025145#comment-16025145 ] Hudson commented on MNG-6084: - SUCCESS: Integrated in Jenkins build maven-3.x #1654 (See [https://builds.apache.org/job/maven-3.x/1654/]) [MNG-6084] Support JSR 250 annotations (michaelo: [http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=a7dddcb87626fec256f1b8ccbe957f94cdf401e4]) * (edit) maven-core/src/main/resources/META-INF/maven/extension.xml * (edit) maven-embedder/pom.xml * (edit) pom.xml * (edit) maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java > Support JSR 250 annotations > --- > > Key: MNG-6084 > URL: https://issues.apache.org/jira/browse/MNG-6084 > Project: Maven > Issue Type: New Feature > Components: core >Affects Versions: 3.3.9 >Reporter: Dan Tran >Assignee: Dan Tran > Fix For: 3.5.1 > > > JSR330 ( @Named, @Singeton, etc) currently supported for plugin development. > Would like to see JSR250 as well(@PostConstruct, etc) > Detail discussion is at > http://maven.40175.n5.nabble.com/Maven-Plugin-and-JSR330-td5879508.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6216) IndexArrayOutOfBounds when parsing POM
[ https://issues.apache.org/jira/browse/MNG-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025150#comment-16025150 ] Michael Osipov commented on MNG-6216: - [~rfscholte], is this one already addressed in master? > IndexArrayOutOfBounds when parsing POM > --- > > Key: MNG-6216 > URL: https://issues.apache.org/jira/browse/MNG-6216 > Project: Maven > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Marc Savy > Fix For: 3.5.1-candidate > > Attachments: log > > > When building apiman https://github.com/apiman/apiman.git on Maven 3.5.0 the > XML parser seems to have some issues parsing the apiman-test-common module. > If you want to reproduce, you can simply use mvn clean install, no profiles > needed. > Log: https://gist.github.com/msavy/a1b4307fb238a543dfd6af426b42d446 > Also attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6114) Elements from the global settings should be ordered before elements from the user settings.
[ https://issues.apache.org/jira/browse/MNG-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025198#comment-16025198 ] Michael Osipov commented on MNG-6114: - [~schulte77], do you have an IT at hand? Your fork does not contain any. > Elements from the global settings should be ordered before elements from the > user settings. > --- > > Key: MNG-6114 > URL: https://issues.apache.org/jira/browse/MNG-6114 > Project: Maven > Issue Type: Bug >Reporter: Christian Schulte > Fix For: 3.5.1-candidate > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MWAR-303) filtering of ${project.developers[0].id} does not work
[
https://issues.apache.org/jira/browse/MWAR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MWAR-303:
Description:
An expression like {{$\{project.developers\[0\].id}}} is not filtered in
version 2.4.
It works fine in maven war plugin version 2.3.
I attached a patch file with a modified integration test.
was:
An expression like ${project.developers[0].id} is not filtered in version 2.4.
It works fine in maven war plugin version 2.3.
I attached a patch file with a modified integration test.
Regards,
Gabriel
> filtering of ${project.developers[0].id} does not work
> --
>
> Key: MWAR-303
> URL: https://issues.apache.org/jira/browse/MWAR-303
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: filtering
>Affects Versions: 2.4, 2.5, 2.6
> Environment: tested with maven 3.0.5, 3.1.0, 3.2.1 Win XP and 7, Java
> 7.
>Reporter: Gabriel Belingueres
>Assignee: Michael Osipov
> Attachments: modified-integ-test.patch
>
>
> An expression like {{$\{project.developers\[0\].id}}} is not filtered
> in version 2.4.
> It works fine in maven war plugin version 2.3.
> I attached a patch file with a modified integration test.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MNG-6236) maven-metadata-local.xml polluted with whitespaces
[ https://issues.apache.org/jira/browse/MNG-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025220#comment-16025220 ] Tomer Cohen commented on MNG-6236: -- It happens randomly (mostly depends on the number if concurrent builds). I've set the log level as you asked, next time it happens I will attach the debug log. > maven-metadata-local.xml polluted with whitespaces > -- > > Key: MNG-6236 > URL: https://issues.apache.org/jira/browse/MNG-6236 > Project: Maven > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Tomer Cohen > Attachments: maven-metadata-local.xml, stacktrace.txt > > > After starting to use Maven 3.5.0 multiple instances of the attached > exceptions started occurring when multiple builds are using and installing > modules of the same reactor. I sanitized the module name. > Maven 3.3.9 did not have this issue -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MNG-6164) Collections inconsistently immutable
[
https://issues.apache.org/jira/browse/MNG-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6164:
Affects Version/s: 3.5.0
> Collections inconsistently immutable
>
>
> Key: MNG-6164
> URL: https://issues.apache.org/jira/browse/MNG-6164
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Christian Schulte
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: 3.5.1-candidate
>
>
> There are plenty of places where empty collections are returned from public
> API methods like:
> {code}
> public List getExceptions()
> {
> return exceptions == null ? Collections. emptyList() :
> exceptions;
> }
> {code}
> The issue with this is that the empty list is immutable but the collection
> returned for the nun-null case is not immutable. All those methods should
> return an immutable collection consistently.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MNG-6236) maven-metadata-local.xml polluted with whitespaces
[ https://issues.apache.org/jira/browse/MNG-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025240#comment-16025240 ] Michael Osipov commented on MNG-6236: - OK, I'll wait. Sporadic issues are hard to tackle. > maven-metadata-local.xml polluted with whitespaces > -- > > Key: MNG-6236 > URL: https://issues.apache.org/jira/browse/MNG-6236 > Project: Maven > Issue Type: Bug >Affects Versions: 3.5.0 >Reporter: Tomer Cohen > Attachments: maven-metadata-local.xml, stacktrace.txt > > > After starting to use Maven 3.5.0 multiple instances of the attached > exceptions started occurring when multiple builds are using and installing > modules of the same reactor. I sanitized the module name. > Maven 3.3.9 did not have this issue -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MRESOLVER-20) Create re-packaged uber JAR with basic dependencies to perform resolution against Maven central
[
https://issues.apache.org/jira/browse/MRESOLVER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025261#comment-16025261
]
Michael Osipov commented on MRESOLVER-20:
-
HI Graeme, even if we provide an Über JAR, Grape folks would still need to add
code to use Maven Resolver, won't they? How will they configure the Resolver
instance? Should they use {{URLConnection}} or {{HttpClient}}?
> Create re-packaged uber JAR with basic dependencies to perform resolution
> against Maven central
> ---
>
> Key: MRESOLVER-20
> URL: https://issues.apache.org/jira/browse/MRESOLVER-20
> Project: Maven Resolver
> Issue Type: Wish
>Reporter: Graeme Rocher
>
> Apache Groovy's @Grab annotation currently uses Ivy for resolution. It would
> be preferable if Ivy was removed and replaced by Apache Maven Resolver,
> however one challenge to that is Ivy is a single JAR whilst Apache Maven
> Resolver has a whole graph of dependencies requiring additional dependency
> management.
> See http://docs.groovy-lang.org/latest/html/documentation/grape.html
> Would it be a possible to release as part of the release process a single JAR
> designed to be embedded into systems like @Grab?
> We could also use this same JAR in the Grails project which has a CLI that
> uses Aether to resolve dependencies from central and a configured list HTTPS
> repositories.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
