[jira] Commented: (MEAR-128) Support for Java EE 6 application.xml
[ http://jira.codehaus.org/browse/MEAR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=225865#action_225865 ] Stephane Nicoll commented on MEAR-128: -- You might want to check the doc. Java EE6 is supported. Support for Java EE 6 application.xml - Key: MEAR-128 URL: http://jira.codehaus.org/browse/MEAR-128 Project: Maven 2.x Ear Plugin Issue Type: Improvement Reporter: Peter Major Assignee: Stephane Nicoll Currently the Java EE 6 is not supported, and the generated XML's are using Java EE 5 namespaces and elements. For example the EE 6 has a new element: application-name, which could be useful for Global JNDI naming. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-128) Support for Java EE 6 application.xml
[ http://jira.codehaus.org/browse/MEAR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=225868#action_225868 ] Peter Major commented on MEAR-128: -- Doh, I was assuming that when you don't supply plugin version, then Maven always will use the latest, well apperently not... (2.3.1 != 2.4.2 ...) But I rechecked the doc, and the only thing about Java EE 6 support I saw was this: version String - The version of the application.xml to generate. Valid values are 1.3, 1.4, 5 and 6. So I still can't find a way to add the 'application-name' tag to my application.xml. Support for Java EE 6 application.xml - Key: MEAR-128 URL: http://jira.codehaus.org/browse/MEAR-128 Project: Maven 2.x Ear Plugin Issue Type: Improvement Reporter: Peter Major Assignee: Stephane Nicoll Currently the Java EE 6 is not supported, and the generated XML's are using Java EE 5 namespaces and elements. For example the EE 6 has a new element: application-name, which could be useful for Global JNDI naming. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2553) Maven Local Settings Model should allow configuration of distributions (distributionManagement)
[
http://jira.codehaus.org/browse/MNG-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=225871#action_225871
]
Brian Fox commented on MNG-2553:
This is simply not how it was designed to work, and there is a perfectly valid
use case for this already, that's why it's marked won't fix. If you want to see
an example, take a look at the Maven and Apache parent poms:
http://svn.apache.org/repos/asf/maven/pom/trunk/
{code}
distributionManagement
!-- Site omitted - each project must provide their own --
repository
idapache.releases.https/id
nameApache Release Distribution Repository/name
urlhttps://repository.apache.org/service/local/staging/deploy/maven2/url
/repository
snapshotRepository
idapache.snapshots.https/id
name${distMgmtSnapshotsName}/name
url${distMgmtSnapshotsUrl}/url
/snapshotRepository
/distributionManagement
properties
distMgmtSnapshotsNameApache Development Snapshot
Repository/distMgmtSnapshotsName
distMgmtSnapshotsUrlhttps://repository.apache.org/content/repositories/snapshots/distMgmtSnapshotsUrl
/properties
{code}
Here we use a property in the distributionManagement section, and define a
default value for the property in the same pom so that it's always complete.
However for CI systems, we define a new value for the property in the settings
that that overrides the pom. We have done this intentionally only for snapshots
in our case as we don't want people to accidentally release somewhere else.
This is what you want to do and it can already be done in the current design.
Maven Local Settings Model should allow configuration of distributions
(distributionManagement)
---
Key: MNG-2553
URL: http://jira.codehaus.org/browse/MNG-2553
Project: Maven 2 3
Issue Type: Improvement
Components: Settings
Affects Versions: 2.0.4
Reporter: Jimisola Laursen
There is a good use case where this would be very useful.
E.g. I develop a plugin in mojo-sandbox and want to test it in an environment
other than the one that I developed it on (e.g. a computer at work). I check
out the plugin to this, build and then want to deploy to another repository
(e..g a company's internal repository). I don't want to fiddle with the
pom.xml of the plugin, just refer to a profile in settings.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-270) mvn dependency:sources fails to download sources for dependencies with classifier
mvn dependency:sources fails to download sources for dependencies with
classifier
---
Key: MDEP-270
URL: http://jira.codehaus.org/browse/MDEP-270
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: sources
Affects Versions: 2.1
Environment: Mac OS 10.6
Reporter: Peter Niederwieser
Assignee: Brian Fox
Priority: Critical
Given the following dependency:
{noformat}
dependency
groupIdnet.sf.json-lib/groupId
artifactIdjson-lib/artifactId
version2.3/version
classifierjdk15/classifier
optionaltrue/optional
/dependency
{noformat}
mvn dependency:sources fails to download the sources although they are
clearly in Maven Central (see
http://repo2.maven.org/maven2/net/sf/json-lib/json-lib/2.3/). My guess is that
the jdk15 classifier is overridden with sources.
Workaround is to use mvn dependency:resolve -Dclassifier=jdk15-sources, which
seems to work. Of course, you'd have to do this for every dependency that has a
classifier. Also, most people won't even get that far. They will simply think
that the sources are not available.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MGPG-29) Allow options to be passed to gpg
Allow options to be passed to gpg - Key: MGPG-29 URL: http://jira.codehaus.org/browse/MGPG-29 Project: Maven 2.x GPG Plugin Issue Type: Improvement Affects Versions: 1.1 Reporter: SebbASF It would sometimes be useful to be able to pass additional command-line options to the gpg executable. For example, if the secret key is stored on a removable medium the --secret-key option is needed. Changing the home directory to the removable medium can cause problems with the gpg2 agent. There may be other options that are needed on occasion. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-456) [regression] Site navigation not generated
[ http://jira.codehaus.org/browse/MSITE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] André Fügenschuh updated MSITE-456: --- Attachment: site-test.zip I can confirm Grzegorz Slowikowski's comment that the regression isn't fixed for multi-module projects *if* a site.xml on the parent module is used. 1) Run the attached sample *as is* with mvn site:stage -DstagingDirectory=[someLocation] and the left navigation bar for the sub-modules is *not* created. 2) Remove/Rename the site.xml and it works. 3) Alternatively re-configure the parent's POM to use v. 2.0.1 and it works fine *including* the site.xml. How to proceed? Re-open this issue or create a new one? [regression] Site navigation not generated -- Key: MSITE-456 URL: http://jira.codehaus.org/browse/MSITE-456 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.1 Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) Java version: 1.6.0_16 Java home: d:\jdk1.6.0_16\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Reporter: Paul Benedict Assignee: Dennis Lundberg Priority: Critical Fix For: 2.1.1, 3.0-alpha-1 Attachments: MSITE-456.zip, site-test.zip My corporate POM locks down the maven-site-plugin to version 2.1. The site of the corporate POM generates just fine. However, when a child project inherits from it, that project's site contains no left-hand navigation. Reverting to 2.0.1 is my workaround. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-558) Add support for 'mkdir' command
[ http://jira.codehaus.org/browse/SCM-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=225895#action_225895 ] Grant Gardner commented on SCM-558: --- The implementation of this looks very SVN specific. eg MkdirSCMResult.revision is an int, rather than an SCMRevision. My other question would be whether the Add command should cover mkdir. Some providers care about adding directories separately to adding files, some don't. Add support for 'mkdir' command --- Key: SCM-558 URL: http://jira.codehaus.org/browse/SCM-558 Project: Maven SCM Issue Type: New Feature Components: maven-scm-api Reporter: Maria Odea Ching Assignee: Maria Odea Ching -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-558) Add support for 'mkdir' command
[ http://jira.codehaus.org/browse/SCM-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=225898#action_225898 ] Maria Odea Ching commented on SCM-558: -- Yes, I have yet to implement the command for the other SCM providers. Thanks for pointing out the revision, I'll change it to a SCMRevision instead. Add support for 'mkdir' command --- Key: SCM-558 URL: http://jira.codehaus.org/browse/SCM-558 Project: Maven SCM Issue Type: New Feature Components: maven-scm-api Reporter: Maria Odea Ching Assignee: Maria Odea Ching -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
