[jira] (MNG-1977) Global dependency exclusions
[ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351264#comment-351264 ] Daniel Wu commented on MNG-1977: It has been always a problem for anyone who hates common loggings :-) Really, this is a MUST-HAVE. Global dependency exclusions Key: MNG-1977 URL: https://jira.codehaus.org/browse/MNG-1977 Project: Maven Issue Type: New Feature Components: FDPFC, POM Reporter: Kees de Kooter Fix For: Issues to be reviewed for 4.x Attachments: global_excls_it-test_v2.patch, global_excls_it-test_v3.patch, global_excls_maven3_v2.patch, global_excls_maven3_v3.patch I depend on some libraries, which in turn depend on something (which in turn depend on something) that I don't want, because I declare some other artifact in my pom.xml. A concrete example: I don't want that the artifact xerces is imported in my project because I declare to depend on xercesImpl which ships newer libraries but with the same namespaces. I guess I would need an exclude transitive dependency at all, either globally or from this and that artifact. I saw the exclusions tag, but it forces me to be very verbose and have exact control on what is required by a dependency. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5672) Switch access to Maven Central to HTTPS
[ https://jira.codehaus.org/browse/MNG-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-5672. --- Resolution: Fixed Fix Version/s: 3.2.3 Assignee: brianfox brianfox Fixed in [92161918698c55f4c108acb8c6042ad86e705b15|http://git-wip-us.apache.org/repos/asf/maven/commit/92161918] Switch access to Maven Central to HTTPS --- Key: MNG-5672 URL: https://jira.codehaus.org/browse/MNG-5672 Project: Maven Issue Type: Improvement Reporter: Andreas Schildbach Assignee: brianfox brianfox Fix For: 3.2.3 Maven Central can now be accessed via HTTPS. I think the default configuration should be switched to use that, rather than the current unsecured HTTP transport. http://central.sonatype.org/articles/2014/Aug/03/https-support-launching-now/ https://repo1.maven.org/maven2 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-424) Conditionally include or exclude a fileSet from an archetype when project is generated
[
https://jira.codehaus.org/browse/ARCHETYPE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351301#comment-351301
]
Martin Grigorov commented on ARCHETYPE-424:
---
This is a duplicate of ARCHETYPE-274.
Conditionally include or exclude a fileSet from an archetype when project is
generated
--
Key: ARCHETYPE-424
URL: https://jira.codehaus.org/browse/ARCHETYPE-424
Project: Maven Archetype
Issue Type: New Feature
Reporter: Adrian
I'm creating a project generating code samples for accessing Oracle and
Mainframe.
I want to conditionnaly generate the samples based on user input
Define value for groupId: : com.example
Define value for artifactId: : myproject
Define value for package: com.example: :
Define value for SGBD Sample : : Y
Define value for Mainframe Sample : : N
Could it be possible to add this functionnality ?
i.e. This could be done by adding an attribute into fileSet element which
would indicate if the fileSet directive needs to be taken into account :
{code:xml}
fileSet filtered=true encoding=UTF-8 enable=${mainframeSample}
directorysrc/main/java/directory
includes
includemainframe/*.java/include
/includes
/fileSet
{code}
Some links :
*
[http://stackoverflow.com/questions/1919704/how-do-i-conditionally-include-or-exclude-a-file-from-an-archetype-when-project]
* [ARCHETYPE-58|http://jira.codehaus.org/browse/ARCHETYPE-58] (this one
didn't adressed this issue)
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-1204) don't show disabled repositories in artifact exceptions
[ https://jira.codehaus.org/browse/MNG-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Benedict updated MNG-1204: --- Fix Version/s: (was: Issues to be reviewed for 3.x) don't show disabled repositories in artifact exceptions --- Key: MNG-1204 URL: https://jira.codehaus.org/browse/MNG-1204 Project: Maven Issue Type: Bug Components: Artifacts and Repositories Reporter: Brett Porter Assignee: Edwin Punzalan Priority: Minor Attachments: MNG-1204-maven-artifact.patch -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSITE-604) Properties from settings.xml are not recognized in site distribution management
[
https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351303#comment-351303
]
Jörg Schaible commented on MSITE-604:
-
@Herve: The code that you are using for the IT in Subversion is not the one
provided in the attachment. As long as you distribution site url starts with
file:// your test will not fail. See the real IT to reproduce the problem.
We're now in the situation that we cannot release anymore at all.
Properties from settings.xml are not recognized in site distribution
management
Key: MSITE-604
URL: https://jira.codehaus.org/browse/MSITE-604
Project: Maven Site Plugin
Issue Type: Bug
Components: site:deploy
Affects Versions: 3.0
Environment: Apache Maven 2.2.1 and 3.0.3
Reporter: Marcin Kuthan
Fix For: backlog
Attachments: MSITE-604-it.patch, MSITE-604-maven3-2.patch,
MSITE-604-maven3.patch, MSITE-604.tgz
My distribution management section looks like:
{code}
distributionManagement
site
id${acme-corporate-pom.siteRepositoryId}/id
url${acme-corporate-pom.siteRepositoryUrl}/url
/site
/distributionManagement
{code}
Where the default property values are defined in the pom:
{code}
properties
acme-corporate-pom.siteRepositoryIdacme-site/acme-corporate-pom.siteRepositoryId
acme-corporate-pom.siteRepositoryUrlscp://sites.intranet.acme.com/var/www/acme-corporate-pom.siteRepositoryUrl
/properties
{code}
I'm able redefine properties from command line, the provided repository is
used instead default one:
{code}
mvn site:site site:deploy
-Dacme-corporate-pom.siteRepositoryUrl=scp://somehost/var/www/sites
-Dacme-corporate-pom.siteRepositoryId=somehost
{code}
But when I redefine properties in the profile in {{settings.xml}}, they are
ignored. The profile is activated in {{activeProfiles}} element.
It looks, than only m-site-p ignores properties defined in the
{{settings.xml}} file. m-deploy-p recognizes properties as I expected
(distribution management section for articats deployment is configured in
similar way to site deployment).
--
Marcin Kuthan
Maven For Enterprise - http://code.google.com/p/m4enterprise/
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEP-451) Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project
[ https://jira.codehaus.org/browse/MDEP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351306#comment-351306 ] Lenny Primak commented on MDEP-451: --- Any updates on this issue? Thanks Regression: mvn dependency:copy doesn't run under maven 3.x multi-module project Key: MDEP-451 URL: https://jira.codehaus.org/browse/MDEP-451 Project: Maven Dependency Plugin Issue Type: Bug Components: copy Affects Versions: 2.8 Environment: All Reporter: Lenny Primak Priority: Critical Attachments: deptest.tar I have a muldi-module project, running mvn dependency:copy on root project just runs on root project without recursing into the modules. This works under maven 3.0.3 but doesn't run at all in the current 3.2.2 version of maven -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-274) Conditionally include or exclude a file from archetype during generation
[ https://jira.codehaus.org/browse/ARCHETYPE-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351307#comment-351307 ] Martin Grigorov commented on ARCHETYPE-274: --- Here is how I solved/workarounded similar issue: https://git-wip-us.apache.org/repos/asf?p=wicket.git;a=commitdiff;h=1c2661a6;hp=520aea93bd8bf87886bf307ac2f052d06a1a1d71 Our issue is explained here: https://issues.apache.org/jira/browse/WICKET-5671. Our archetype by default has 'src/main/resources/log4j.properties'. We needed to remove it when deploying in Wild Fly (JBoss 8.x) because otherwise it refuses to log any application specific logs. So with the above change if -Dlog4j.properties is specified then we use the value as the new name of the file. If this system property is skipped then the default is taken into account. So the file is neither added nor removed dynamically - it just has custom name depending on the property. Conditionally include or exclude a file from archetype during generation Key: ARCHETYPE-274 URL: https://jira.codehaus.org/browse/ARCHETYPE-274 Project: Maven Archetype Issue Type: Improvement Components: Generator Affects Versions: 2.0-alpha-4 Reporter: Dan Allen I would like to be able to control which files are placed into the generated project based on the value of a property that is defined during archetype:generate. For instance, I forsee the following prompt: Define value for groupId: : com.example Define value for artifactId: : myproject Define value for package: com.example: : Define value for extraSupport: : y Based on the value of extraSupport, I want to include (or not include) a file in the generated project. If the user does not want the extra support, I don't want to clutter up the generated project with unnecessary files. It's all about customization of the project based on what the developer intends to use. While I could create a whole other archetype, sometimes the changes are so slight that it would be easier to include/exclude a file. Is there a way to control this behavior using the archetype-metadata.xml descriptor? -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5663) [regression] resolution of import-scoped transitive dependencies ignores additional repositories
[
https://jira.codehaus.org/browse/MNG-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351308#comment-351308
]
Jason van Zyl commented on MNG-5663:
Maven 3.2.3 has now been staged.
[regression] resolution of import-scoped transitive dependencies ignores
additional repositories
Key: MNG-5663
URL: https://jira.codehaus.org/browse/MNG-5663
Project: Maven
Issue Type: Bug
Components: Artifacts and Repositories, Dependencies
Affects Versions: 3.2.2
Reporter: Fred Bricon
Assignee: Jason van Zyl
Fix For: 3.2.3
We (JBoss) use BOM poms extensively, notably in a number of project
archetypes or project examples available via JBoss Tools and Red Hat
Developer Studio . Some of these BOM poms (and their dependencies) are
available from a dedicated Maven repository
(http://maven.repository.redhat.com/techpreview/all/).
Maven 3.2.2 introduced a regression that breaks resolution of these BOM
dependencies, by ignoring additional repositories during artifact resolution.
{code:xml}project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
groupIdfoo/groupId
artifactIdbar/artifactId
version0.0.1-SNAPSHOT/version
dependencyManagement
dependencies
dependency
groupIdorg.jboss.bom.wfk/groupId
artifactIdjboss-javaee-6.0-with-tools/artifactId
version2.4.0-redhat-2/version
typepom/type
scopeimport/scope
/dependency
/dependencies
/dependencyManagement
repositories
repository
idredhat-techpreview-all-repository/id
urlhttp://maven.repository.redhat.com/techpreview/all//url
/repository
/repositories
/project{code}
yields :
{noformat}
âÃ
¾Ã
â bar mvn compile
[INFO] Scanning for projects...
Downloading:
http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom
Downloaded:
http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom
(8 KB at 5.1 KB/sec)
Downloading:
http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-wfk-bom-parent/2.4.0-redhat-2/jboss-wfk-bom-parent-2.4.0-redhat-2.pom
Downloaded:
http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-wfk-bom-parent/2.4.0-redhat-2/jboss-wfk-bom-parent-2.4.0-redhat-2.pom
(7 KB at 6.8 KB/sec)
Downloading:
http://repo.maven.apache.org/maven2/org/jboss/spec/jboss-javaee-6.0/3.0.2.Final-redhat-4/jboss-javaee-6.0-3.0.2.Final-redhat-4.pom
[ERROR] The build could not read 1 project - [Help 1]
[ERROR]
[ERROR] The project foo:bar:0.0.1-SNAPSHOT
(/Users/fbricon/Dev/workspaces/runtime-hosted/bar/pom.xml) has 2 errors
[ERROR] Non-resolvable import POM: Could not find artifact
org.jboss.spec:jboss-javaee-6.0:pom:3.0.2.Final-redhat-4 in central
(http://repo.maven.apache.org/maven2) @
org.jboss.bom.wfk:jboss-javaee-6.0-with-tools:[unknown-version],
/Users/fbricon/Dev/maven/repository/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom,
line 42, column 25 - [Help 2]
[ERROR] 'dependencies.dependency.version' for
javax.enterprise:cdi-api:jar is missing. @ line 27, column 15
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
âÃ
¾Ã
â bar
{noformat}
This kind of resolution used to work in maven 3.2.1 and before. The missing
pom is available at
http://maven.repository.redhat.com/techpreview/all/org/jboss/spec/jboss-javaee-6.0/3.0.2.Final-redhat-4/jboss-javaee-6.0-3.0.2.Final-redhat-4.pom
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5674) Connection - Time out
[ https://jira.codehaus.org/browse/MNG-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-5674. -- Resolution: Cannot Reproduce Connection - Time out - Key: MNG-5674 URL: https://jira.codehaus.org/browse/MNG-5674 Project: Maven Issue Type: Bug Components: Command Line Affects Versions: 3.2.1, 3.2.2 Environment: Ubuntu 12.04 Reporter: Heinz Wittig Priority: Blocker By run an mvn clean install or mvn compile on a project with dependencies defined on a local server, the connection hangs up and and don't gives feedback. If I try to put some error on the setting.xml (by setting username and password) and I will become back the correct error (auth failure). I tried with -X to have more information but nothing. Then I installed an older version (3.0.4) without changing anything and the download of the dependencies worked. I have the same behaviour in the current version 3.2.2 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5673) Profile activation does not work if more than 1 type of activation is present
[
https://jira.codehaus.org/browse/MNG-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MNG-5673.
--
Resolution: Won't Fix
Profile activation does not work if more than 1 type of activation is present
-
Key: MNG-5673
URL: https://jira.codehaus.org/browse/MNG-5673
Project: Maven
Issue Type: Bug
Components: Documentation: Guides, Profiles
Affects Versions: 3.2.2
Reporter: Jeroen Ruijgers
Priority: Blocker
When a profile has more than 1 activation, according to the
[documentation|http://maven.apache.org/pom.html#Activation] 1 match is enough
to activate a profile:
{quote}Activation occurs when one or more of the specified criteria have been
met. When the first positive result is encountered, processing stops and the
profile is marked as active.{quote}
Since Maven 3.2.2 this does not work. For instance with the following
activation code:
{code}
activation
file
exists${env.JBOSS_HOME}/server/development/exists
/file
property
nameassembly/name
/property
/activation
{code}
The profile only gets activated if both the directory is present and the
propery is specified. If we remove the property from the configuration, the
profile is activated based on the directory
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5673) Profile activation does not work if more than 1 type of activation is present
[
https://jira.codehaus.org/browse/MNG-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351309#comment-351309
]
Jason van Zyl commented on MNG-5673:
This change will not be reverted. There was conflicting documentation but I
believe this is the right behaviour. Occassionally we make changes that break
some things. There is only one way to specify profiles right now and it's not
possible currently to implement custom activators. As such this mode where it
is possible to AND and OR is preferred only only being able to to OR. When
custom profile activators can be added I will make an implementation using MVEL
which will be more flexible.
Profile activation does not work if more than 1 type of activation is present
-
Key: MNG-5673
URL: https://jira.codehaus.org/browse/MNG-5673
Project: Maven
Issue Type: Bug
Components: Documentation: Guides, Profiles
Affects Versions: 3.2.2
Reporter: Jeroen Ruijgers
Priority: Blocker
When a profile has more than 1 activation, according to the
[documentation|http://maven.apache.org/pom.html#Activation] 1 match is enough
to activate a profile:
{quote}Activation occurs when one or more of the specified criteria have been
met. When the first positive result is encountered, processing stops and the
profile is marked as active.{quote}
Since Maven 3.2.2 this does not work. For instance with the following
activation code:
{code}
activation
file
exists${env.JBOSS_HOME}/server/development/exists
/file
property
nameassembly/name
/property
/activation
{code}
The profile only gets activated if both the directory is present and the
propery is specified. If we remove the property from the configuration, the
profile is activated based on the directory
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351310#comment-351310 ] Jason van Zyl commented on MNG-5676: Which version of Java are you running on? mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351312#comment-351312 ] Dan Tran commented on MNG-5676: --- I am using java version 1.7.0 Java(TM) SE Runtime Environment (build pxa6470sr6fp1-20140108_01(SR6 FP1)) IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20140106_181350 (JIT enabled, AOT enabled) J9VM - R26_Java726_SR6_20140106_1601_B181350 JIT - r11.b05_20131003_47443.02 GC - R26_Java726_SR6_20140106_1601_B181350_CMPRSS J9CL - 20140106_181350) JCL - 20140103_01 based on Oracle 7u51-b11 mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
