[jira] Created: (MPLUGIN-27) CLONE -Generated Goal documentation displays incorrect type for arrays
CLONE -Generated Goal documentation displays incorrect type for arrays
--
Key: MPLUGIN-27
URL: http://jira.codehaus.org/browse/MPLUGIN-27
Project: Maven 2.x Plugin Plugin
Issue Type: Bug
Reporter: Marcus Schulte
Assigned To: Brett Porter
Priority: Minor
The site document generated to display specific goal information (site\Project
Reports\Plugin documentation\Individual Site) does not correctly display the
type for a parameter which is an array.
An example of this would be if a goal has a parameter defined like the example
below:
/**
* @parameter expression=${vmArgs}
*/
private String[] vmArgs;
the generated site displays the parameter as only having a type of String.
This is misleading since it should be type String[].
--
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: (MPLUGIN-27) CLONE -Generated Goal documentation displays incorrect type for arrays
[ http://jira.codehaus.org/browse/MPLUGIN-27?page=comments#action_84458 ]
Marcus Schulte commented on MPLUGIN-27:
---
For another example see the docs of the assembly-Plugin:
http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html#descriptors
or
http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html#descriptorRefs
while the source is
/**
109 * A list of descriptor files to generate from.
110 *
111 * @parameter
112 */
113 private File[] descriptors;
114
115 /**
116 * A list of built-in descriptor references to generate from. You can
select from codebin/code,
117 * codejar-with-dependencies/code, or codesrc/code.
118 *
119 * @parameter
120 */
121 private String[] descriptorRefs;
CLONE -Generated Goal documentation displays incorrect type for arrays
--
Key: MPLUGIN-27
URL: http://jira.codehaus.org/browse/MPLUGIN-27
Project: Maven 2.x Plugin Plugin
Issue Type: Bug
Reporter: Marcus Schulte
Assigned To: Brett Porter
Priority: Minor
The site document generated to display specific goal information
(site\Project Reports\Plugin documentation\Individual Site) does not
correctly display the type for a parameter which is an array.
An example of this would be if a goal has a parameter defined like the
example below:
/**
* @parameter expression=${vmArgs}
*/
private String[] vmArgs;
the generated site displays the parameter as only having a type of String.
This is misleading since it should be type String[].
--
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: (CONTINUUM-1126) All groups are listed in main page regardless of permissions
All groups are listed in main page regardless of permissions Key: CONTINUUM-1126 URL: http://jira.codehaus.org/browse/CONTINUUM-1126 Project: Continuum Issue Type: Bug Components: Web - Security Reporter: Lester Ecarma -- 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: (CONTINUUM-1126) All groups are listed in main page regardless of permissions
[ http://jira.codehaus.org/browse/CONTINUUM-1126?page=all ] Lester Ecarma updated CONTINUUM-1126: - Attachment: CONTINUUM-1126.patch Attached patch should fix this. All groups are listed in main page regardless of permissions Key: CONTINUUM-1126 URL: http://jira.codehaus.org/browse/CONTINUUM-1126 Project: Continuum Issue Type: Bug Components: Web - Security Reporter: Lester Ecarma Assigned To: Lester Ecarma Attachments: CONTINUUM-1126.patch -- 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: (MPLUGIN-27) CLONE -Generated Goal documentation displays incorrect type for arrays
[ http://jira.codehaus.org/browse/MPLUGIN-27?page=comments#action_84462 ]
Brett Porter commented on MPLUGIN-27:
-
it's fine with plugin-plugin 2.2.
CLONE -Generated Goal documentation displays incorrect type for arrays
--
Key: MPLUGIN-27
URL: http://jira.codehaus.org/browse/MPLUGIN-27
Project: Maven 2.x Plugin Plugin
Issue Type: Bug
Reporter: Marcus Schulte
Assigned To: Brett Porter
Priority: Minor
The site document generated to display specific goal information
(site\Project Reports\Plugin documentation\Individual Site) does not
correctly display the type for a parameter which is an array.
An example of this would be if a goal has a parameter defined like the
example below:
/**
* @parameter expression=${vmArgs}
*/
private String[] vmArgs;
the generated site displays the parameter as only having a type of String.
This is misleading since it should be type String[].
--
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] Deleted: (MPLUGIN-27) CLONE -Generated Goal documentation displays incorrect type for arrays
[ http://jira.codehaus.org/browse/MPLUGIN-27?page=all ]
Brett Porter deleted MPLUGIN-27:
CLONE -Generated Goal documentation displays incorrect type for arrays
--
Key: MPLUGIN-27
URL: http://jira.codehaus.org/browse/MPLUGIN-27
Project: Maven 2.x Plugin Plugin
Issue Type: Bug
Reporter: Marcus Schulte
Assigned To: Brett Porter
Priority: Minor
The site document generated to display specific goal information
(site\Project Reports\Plugin documentation\Individual Site) does not
correctly display the type for a parameter which is an array.
An example of this would be if a goal has a parameter defined like the
example below:
/**
* @parameter expression=${vmArgs}
*/
private String[] vmArgs;
the generated site displays the parameter as only having a type of String.
This is misleading since it should be type String[].
--
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] Closed: (CONTINUUM-1116) m2 build of project with missing parent pom results in error with no reason or logs
[ http://jira.codehaus.org/browse/CONTINUUM-1116?page=all ] Emmanuel Venisse closed CONTINUUM-1116. --- Assignee: Emmanuel Venisse (was: Lester Ecarma) Resolution: Fixed Fix Version/s: 1.1 Applied. Thanks. m2 build of project with missing parent pom results in error with no reason or logs --- Key: CONTINUUM-1116 URL: http://jira.codehaus.org/browse/CONTINUUM-1116 Project: Continuum Issue Type: Bug Components: Core system Reporter: Lester Ecarma Assigned To: Emmanuel Venisse Fix For: 1.1 Attachments: CONTINUUM-1116.patch Steps to reproduce. 1. Add an m2 project to continuum 2. modify the project's pom so that it references a parent pom that does not exist 2. Build this recently added m2 project 3. See failure and lack of message indicating the reason. -- 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] Closed: (CONTINUUM-1126) All groups are listed in main page regardless of permissions
[ http://jira.codehaus.org/browse/CONTINUUM-1126?page=all ] Emmanuel Venisse closed CONTINUUM-1126. --- Assignee: Emmanuel Venisse (was: Lester Ecarma) Resolution: Fixed Fix Version/s: 1.1 Applied. Thanks. All groups are listed in main page regardless of permissions Key: CONTINUUM-1126 URL: http://jira.codehaus.org/browse/CONTINUUM-1126 Project: Continuum Issue Type: Bug Components: Web - Security Reporter: Lester Ecarma Assigned To: Emmanuel Venisse Fix For: 1.1 Attachments: CONTINUUM-1126.patch -- 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: (ARCHETYPE-63) Provide more properties (like current date) that are provided automatically
Provide more properties (like current date) that are provided automatically --- Key: ARCHETYPE-63 URL: http://jira.codehaus.org/browse/ARCHETYPE-63 Project: Maven Archetype Issue Type: New Feature Affects Versions: 1.0-alpha-3 Reporter: Martin Ahrer I'm trying to create archetypes that create project templates that need to refer to properties other than groupId artifactId version packageName archetypeGroupId ... to allow more flexible customization of the templates using velocity. for example I'm providing a changes.xml with a pre-set release element. this here refers to a variable $currentDate (like the site plugin provides one) through a VTL expression. release version=1.0 date=$currentDate description=First release action dev=xxx type=add$currentDate: initial project setup/action /release But there might be more auto-properties that one could think of! * date * time * current user * ... -- 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: (MECLIPSE-134) target/classes not acceptable for eclipse
[ http://jira.codehaus.org/browse/MECLIPSE-134?page=comments#action_84475 ]
Aaron Digulla commented on MECLIPSE-134:
you can already use the outputDir parameter
I tried that and it didn't work. Can you please post an example?
Also, in the code, you write:
212 /**
213 * The default output directory
214 *
215 * @parameter expression=${outputDirectory} alias=outputDirectory
default-value=${project.build.outputDirectory}
216 * @required
217 */
218 private File buildOutputDirectory;
That means I have to define a property outputDirectory instead of
buildOutputDirectory, right?
I'd suggest to use eclipse.outputDirectory instead because outputDirectory is
easily confused with the Maven config element.
target/classes not acceptable for eclipse
-
Key: MECLIPSE-134
URL: http://jira.codehaus.org/browse/MECLIPSE-134
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Affects Versions: 2.0, 2.1, 2.2
Reporter: Jörg Hohwiller
Assigned To: fabrizio giustina
Priority: Minor
mvn eclipse:eclipse causes an eclipse configuration where the classfiles
generated by eclipse go to the same directory as the classes generated by
maven. This is extremly evil! Eclipse and maven are independent tools and
should therefore not compile to the same target folder causing side effects.
Especially when mvn clean is called and you re-run an existing application
inside eclipse, and get a NoClassDefFoundError you can get slightly confused.
Please use anything else than target/ My suggestion would be
.eclipse-build.
--
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-55) Adding ejb-client dependencies as modulejarModule gives error
[ http://jira.codehaus.org/browse/MEAR-55?page=comments#action_84477 ]
Stephane Nicoll commented on MEAR-55:
-
UH?
What workaround are you talking about
{code:xml}
configuration
modules
ejbClientModule
groupIdde.xpm/groupId
artifactIdlucenesearch-ejb/artifactId
includeInApplicationXmltrue/includeInApplicationXml
/ejbClientModule
/modules
/configuration
{code}
???
Adding ejb-client dependencies as modulejarModule gives error
-
Key: MEAR-55
URL: http://jira.codehaus.org/browse/MEAR-55
Project: Maven 2.x Ear Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: Stefan Seidel
Priority: Minor
The plugin complains that the artifacts which are of type ejb-client are no
dependencies of this project.
{code}[INFO] Artifact[jar:de.xpm:lucenesearch-ejb] is not a dependency of the
project.{code}
The dependency looks like
{code}
dependency
groupIdde.xpm/groupId
artifactIdlucenesearch-ejb/artifactId
version[1.2.1,2.0)/version
typeejb-client/type
/dependency
{code}
The plugin configuration looks like
{code}
configuration
modules
jarModule
groupIdde.xpm/groupId
artifactIdlucenesearch-ejb/artifactId
includeInApplicationXmltrue/includeInApplicationXml
/jarModule
/modules
/configuration
{code}
The workaround is to include
{code}
artifactTypeMappings
artifactTypeMapping type=ejb-client mapping=jar /
/artifactTypeMappings
{code}
in the plugin configuration.
--
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: (MSOURCES-6) Sources plugin ignores resource includes/excludes
[ http://jira.codehaus.org/browse/MSOURCES-6?page=all ] Richard van der Hoff updated MSOURCES-6: Attachment: maven-source-plugin-2.0.2-patches-take2.zip My previous patch had a problem which meant that an exception was thrown if src/main/resources directory didn't exist; I've updated the patch to correct this. I've also split the patch into tests and source. Sources plugin ignores resource includes/excludes - Key: MSOURCES-6 URL: http://jira.codehaus.org/browse/MSOURCES-6 Project: Maven 2.x Sources Plugin Issue Type: Bug Affects Versions: 2.0.1 Reporter: Matthew Beermann Priority: Critical Fix For: 2.0.2 Attachments: maven-source-plugin-2.0.2-patches-take2.zip, maven-source-plugin-2.0.2.patch, maven-sources-plugin-patches.zip, maven-sources-plugin-patches_v1.1.zip, patch.txt The sources plugin appears to ignore the includes and excludes filters on resource items. I discovered this because I have a project that needs to package certain files that appear in the project root; e.g. directory./directory, and then I include certain files. Trouble is, when the source plugin runs, it packages up EVERYTHING - including the stuff in the target (output) directory! This leads to a source attachment that's much too large. Worse, if you forget to clean between builds, the size of the source jar will increase exponentially with each build. Checking out the source code at http://svn.apache.org/viewvc/maven/plugins/trunk/maven-source-plugin/src/main/java/org/apache/maven/plugin/source/AbstractJarSourceMojo.java?view=markup, I think the problem is in the addDirectories() method, which is simply adding resource.getDirectory() and dropping the other information on the floor. -- 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-55) Adding ejb-client dependencies as modulejarModule gives error
[ http://jira.codehaus.org/browse/MEAR-55?page=comments#action_84479 ]
Stephane Nicoll commented on MEAR-55:
-
http://maven.apache.org/plugins/maven-ear-plugin/modules.html
Adding ejb-client dependencies as modulejarModule gives error
-
Key: MEAR-55
URL: http://jira.codehaus.org/browse/MEAR-55
Project: Maven 2.x Ear Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: Stefan Seidel
Assigned To: Stephane Nicoll
Priority: Minor
The plugin complains that the artifacts which are of type ejb-client are no
dependencies of this project.
{code}[INFO] Artifact[jar:de.xpm:lucenesearch-ejb] is not a dependency of the
project.{code}
The dependency looks like
{code}
dependency
groupIdde.xpm/groupId
artifactIdlucenesearch-ejb/artifactId
version[1.2.1,2.0)/version
typeejb-client/type
/dependency
{code}
The plugin configuration looks like
{code}
configuration
modules
jarModule
groupIdde.xpm/groupId
artifactIdlucenesearch-ejb/artifactId
includeInApplicationXmltrue/includeInApplicationXml
/jarModule
/modules
/configuration
{code}
The workaround is to include
{code}
artifactTypeMappings
artifactTypeMapping type=ejb-client mapping=jar /
/artifactTypeMappings
{code}
in the plugin configuration.
--
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: (MPNATIVE-19) MSVC link.exe won't run smoothly as restricted user
MSVC link.exe won't run smoothly as restricted user --- Key: MPNATIVE-19 URL: http://jira.codehaus.org/browse/MPNATIVE-19 Project: maven-native-plugin Issue Type: Bug Environment: win32 (WinXP), Maven 2.0.4, JDK 1.4.2, JDK 1.5, JDK 1.6, VS.NET 2003 Reporter: Hans-Gunnar Vold Running Maven as a restricted user causes link.exe to fail since it wants to write temporary files to C:\WINDOWS. TEMP and TMP variables are evidently unset/ not set. Possible solution: Set TMP and TEMP variables in environment factory to point to the user's temp directory (i.e. C:\DOCUME~1\username\LOCALS~1\Temp). Shouldn't be hardcoded to C:\ obviously. I monitored file access using Sysinternals Filemon, here's a snippet: 198 09:03:25link.exe:3812 QUERY INFORMATION C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\LIB\MSVCRTD.lib SUCCESS Length: 442910 199 09:03:25link.exe:3812 QUERY INFORMATION C:\WINDOWS SUCCESS Attributes: D 200 09:03:25link.exe:3812 CREATE C:\WINDOWS\lnkED0.tmp ACCESS DENIED username 201 09:03:25link.exe:3812 CLOSE C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\LIB\MSVCRTD.lib SUCCESS 202 09:03:25link.exe:3812 SET INFORMATION D:\Eclipse\VersionTesting\jni-example\native\win32\target\hello.dll SUCCESS Length: 0 Build output snippet: [INFO] [native:link] [INFO] link.exe /DEBUG /INCREMENTAL:NO /DLL oldnames.lib kernel32.lib /out:D:\... target\HelloWorld.obj Microsoft (R) Incremental Linker Version 7.10.6030 Copyright (C) Microsoft Corporation. All rights reserved. LINK : warning LNK4068: /MACHINE not specified; defaulting to X86 LINK : fatal error LNK1104: cannot open file 'TEMPFILE' [INFO] --- [ERROR] BUILD ERROR [INFO] --- [INFO] Error executing command line. Exit code:1104 -- 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: (CONTINUUM-1113) Continuum doesn't work with MySQL
[ http://jira.codehaus.org/browse/CONTINUUM-1113?page=comments#action_84487 ] Carlos Sanchez commented on CONTINUUM-1113: --- Last comment in mysql bug says it's verified. Seems it depends on the character set of your DB What's your output of show variables like %char%; Continuum doesn't work with MySQL - Key: CONTINUUM-1113 URL: http://jira.codehaus.org/browse/CONTINUUM-1113 Project: Continuum Issue Type: Improvement Components: Database Affects Versions: 1.1 Reporter: Carlos Sanchez Assigned To: Carlos Sanchez 2006-10-20 19:23:14,288 [WrapperSimpleAppMain] ERROR RDBMS - Error thrown executing CREATE TABLE `PROJECTNOTIFIER_CONFIGURATION` [SNIP] 2006/10/20 19:23:14 | java.sql.SQLException: BLOB/TEXT column 'STRING_KEY' used in key specification without a key length -- 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: (MNG-2748) jackrabit pom fix suggestions
jackrabit pom fix suggestions - Key: MNG-2748 URL: http://jira.codehaus.org/browse/MNG-2748 Project: Maven 2 Issue Type: Bug Components: Artifacts Reporter: Laszlo Hornyak Kocka Attachments: jackrabbit-poms.tar.gz mandatory 'groupId' and 'version' tags missing, some dependency has strange version (and it looks trivial which version it should use) attached poms fix the issues -- 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-56) test-jar
test-jar Key: MDEP-56 URL: http://jira.codehaus.org/browse/MDEP-56 Project: Maven 2.x Dependency Plugin Issue Type: Bug Affects Versions: 2.0-alpha-1 Reporter: Yuri Schimke Assigned To: Brian Fox For the following dependency dependency groupIdXXX/groupId artifactIdmodel/artifactId version1.2.1-SNAPSHOT/version typetest-jar/type /dependency dependency:copy-dependencies creates the wrong JAR file when run with stripVersion = true The created jar file is called model-tests.test-jar It should be called model-tests.jar -- 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: (CONTINUUM-1127) logic for whether to build is confusing
logic for whether to build is confusing --- Key: CONTINUUM-1127 URL: http://jira.codehaus.org/browse/CONTINUUM-1127 Project: Continuum Issue Type: Bug Components: Core system Affects Versions: 1.1 Reporter: Brett Porter Looking at the logic in DefaultBuildcontroller's shouldBuild( BuildContext context ), I see some potential problems: - the second else clause is redundant - shouldBuild is always true at this point - the code is confusing - better to default to false, then set to true if state/oldstate is new or checkedout, or if the build was forced - move the dependency checking outside the other if. It doesn't need to be conditional on whether there were changes or not. -- 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] Closed: (MNG-2117) Update doap file descriptor
[ http://jira.codehaus.org/browse/MNG-2117?page=all ] Jason van Zyl closed MNG-2117. -- Resolution: Fixed Use the DOAP plugin, it's been released. Update doap file descriptor --- Key: MNG-2117 URL: http://jira.codehaus.org/browse/MNG-2117 Project: Maven 2 Issue Type: Task Components: Sites Reporting Affects Versions: 2.0.3 Reporter: Emmanuel Venisse Assigned To: Dennis Lundberg Fix For: 2.0.5 -- 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: (DOXIA-92) cannot load images in APT files
cannot load images in APT files --- Key: DOXIA-92 URL: http://jira.codehaus.org/browse/DOXIA-92 Project: doxia Issue Type: Bug Reporter: Martin Goldhahn Priority: Critical I want to render an APT file that I use in my site as a PDF file. Maven's site plugin finds the image because it is located in src/site/resources. It seams that this path is not added to doxia's classpath. Thus it cannot find the image. How do I tell the doxia-maven-plugin that it should search the resources folder as well? -- 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-55) Adding ejb-client dependencies as modulejarModule gives error
[ http://jira.codehaus.org/browse/MEAR-55?page=comments#action_84504 ]
Stefan Seidel commented on MEAR-55:
---
Ok, I didn't know about the ejbClientModule tag ... when I looked at the
documentation back when I included the module, I didn't find it. Thx closing.
Adding ejb-client dependencies as modulejarModule gives error
-
Key: MEAR-55
URL: http://jira.codehaus.org/browse/MEAR-55
Project: Maven 2.x Ear Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: Stefan Seidel
Assigned To: Stephane Nicoll
Priority: Minor
The plugin complains that the artifacts which are of type ejb-client are no
dependencies of this project.
{code}[INFO] Artifact[jar:de.xpm:lucenesearch-ejb] is not a dependency of the
project.{code}
The dependency looks like
{code}
dependency
groupIdde.xpm/groupId
artifactIdlucenesearch-ejb/artifactId
version[1.2.1,2.0)/version
typeejb-client/type
/dependency
{code}
The plugin configuration looks like
{code}
configuration
modules
jarModule
groupIdde.xpm/groupId
artifactIdlucenesearch-ejb/artifactId
includeInApplicationXmltrue/includeInApplicationXml
/jarModule
/modules
/configuration
{code}
The workaround is to include
{code}
artifactTypeMappings
artifactTypeMapping type=ejb-client mapping=jar /
/artifactTypeMappings
{code}
in the plugin configuration.
--
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] Closed: (MEAR-55) Adding ejb-client dependencies as modulejarModule gives error
[ http://jira.codehaus.org/browse/MEAR-55?page=all ]
Stefan Seidel closed MEAR-55.
-
Resolution: Won't Fix
Is not a bug - it's a feature ;)
Adding ejb-client dependencies as modulejarModule gives error
-
Key: MEAR-55
URL: http://jira.codehaus.org/browse/MEAR-55
Project: Maven 2.x Ear Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: Stefan Seidel
Assigned To: Stephane Nicoll
Priority: Minor
The plugin complains that the artifacts which are of type ejb-client are no
dependencies of this project.
{code}[INFO] Artifact[jar:de.xpm:lucenesearch-ejb] is not a dependency of the
project.{code}
The dependency looks like
{code}
dependency
groupIdde.xpm/groupId
artifactIdlucenesearch-ejb/artifactId
version[1.2.1,2.0)/version
typeejb-client/type
/dependency
{code}
The plugin configuration looks like
{code}
configuration
modules
jarModule
groupIdde.xpm/groupId
artifactIdlucenesearch-ejb/artifactId
includeInApplicationXmltrue/includeInApplicationXml
/jarModule
/modules
/configuration
{code}
The workaround is to include
{code}
artifactTypeMappings
artifactTypeMapping type=ejb-client mapping=jar /
/artifactTypeMappings
{code}
in the plugin configuration.
--
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: (DOXIA-92) cannot load images in APT files
[ http://jira.codehaus.org/browse/DOXIA-92?page=comments#action_84507 ] Martin Goldhahn commented on DOXIA-92: -- I figured out two solutions to the problem: 1. Use the ITextSink.setClassLoader(ClassLoader) function 2. set a new Thread.contextClassLoader in the DoxiaRenderBooksMojo and allow the Thread.contextClassLoader to load the image, a new config parameter is added to the Mojo The first alternative requires more knowledge of the inner working of maven than I have. For the second solution I add two patches: ITextSink.patch from the doxia-module-itext project and DoxiaRendererBooksMojo from the doxia-maven-plugin project cannot load images in APT files --- Key: DOXIA-92 URL: http://jira.codehaus.org/browse/DOXIA-92 Project: doxia Issue Type: Bug Reporter: Martin Goldhahn Priority: Critical I want to render an APT file that I use in my site as a PDF file. Maven's site plugin finds the image because it is located in src/site/resources. It seams that this path is not added to doxia's classpath. Thus it cannot find the image. How do I tell the doxia-maven-plugin that it should search the resources folder as well? -- 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: (CONTINUUM-1128) continuum doesn't correctly handle SVN property changes as an update
continuum doesn't correctly handle SVN property changes as an update Key: CONTINUUM-1128 URL: http://jira.codehaus.org/browse/CONTINUUM-1128 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.1 Reporter: Brett Porter 2007-01-09 15:22:28,137 [Thread-2094] INFO ScmManager - Unknown file status: ' ' in line U src/test/resources/ projects/restore-backup-poms/basic-pom/pom.xml.releaseBackup. 2007-01-09 15:22:28,138 [Thread-2094] INFO ScmManager - Unknown file status: ' ' in line U src/test/resources/ projects/restore-backup-poms/pom-with-modules/pom.xml.releaseBackup. 2007-01-09 15:22:28,138 [Thread-2094] INFO ScmManager - Unknown file status: ' ' in line U src/test/resources/ projects/restore-backup-poms/pom-with-modules/subproject1/pom.xml.releaseBackup. 2007-01-09 15:22:28,138 [Thread-2094] INFO ScmManager - Unknown file status: ' ' in line U src/test/resources/ projects/restore-backup-poms/pom-with-modules/subproject2/pom.xml.releaseBackup. I assume that this update was actually ' U src/...', ie a property update, not a file update -- 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: (DOXIA-92) cannot load images in APT files
[ http://jira.codehaus.org/browse/DOXIA-92?page=all ] Martin Goldhahn updated DOXIA-92: - Attachment: ITextSink.patch DoxiaRenderBooksMojo.patch See my previous comment cannot load images in APT files --- Key: DOXIA-92 URL: http://jira.codehaus.org/browse/DOXIA-92 Project: doxia Issue Type: Bug Reporter: Martin Goldhahn Priority: Critical Attachments: DoxiaRenderBooksMojo.patch, ITextSink.patch I want to render an APT file that I use in my site as a PDF file. Maven's site plugin finds the image because it is located in src/site/resources. It seams that this path is not added to doxia's classpath. Thus it cannot find the image. How do I tell the doxia-maven-plugin that it should search the resources folder as well? -- 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: (CONTINUUM-1129) projects can be built out of order if some are already scheduled when a new batch get scheduled
projects can be built out of order if some are already scheduled when a new batch get scheduled --- Key: CONTINUUM-1129 URL: http://jira.codehaus.org/browse/CONTINUUM-1129 Project: Continuum Issue Type: Bug Components: Core system Affects Versions: 1.1 Reporter: Brett Porter -- 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: (CONTINUUM-1130) can't delete default project group
can't delete default project group -- Key: CONTINUUM-1130 URL: http://jira.codehaus.org/browse/CONTINUUM-1130 Project: Continuum Issue Type: Bug Components: Core system, Database Affects Versions: 1.1 Reporter: Brett Porter I don't really want/need this - but after deleting it, it keeps coming back -- 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: (MPPMD-29) Upgrade to PMD 3.9
[ http://jira.codehaus.org/browse/MPPMD-29?page=comments#action_84514 ] Francois Le Droff commented on MPPMD-29: For those like me who can't wait, I'll attach an official maven-pmd-plugin-1.10 plugin that bundles pmd 3.9 you'll need to have asm 3.0 in your local maven1 repository though ! Cheers and thanks for PMD ! Upgrade to PMD 3.9 -- Key: MPPMD-29 URL: http://jira.codehaus.org/browse/MPPMD-29 Project: maven-pmd-plugin Issue Type: Task Affects Versions: 1.9 Reporter: Anthony Whitford Assigned To: Jeff Jensen Fix For: 1.10 PMD 3.8 was released October 4, 2006. The Maven plugin should be updated too. http://sourceforge.net/project/shownotes.php?release_id=452776group_id=56262 -- 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: (MAVENUPLOAD-1282) PMD 3.9 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1282?page=comments#action_84515 ] Xavier Chatelain commented on MAVENUPLOAD-1282: --- There is still a reference to pmd version 3.7 in the pom.xml (http://svn.apache.org/viewvc/maven/plugins/trunk/maven-pmd-plugin/pom.xml?revision=494359view=markup) : dependency groupIdpmd/groupId artifactIdpmd/artifactId version3.7/version /dependency PMD 3.9 bundle -- Key: MAVENUPLOAD-1282 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1282 Project: maven-upload-requests Issue Type: Task Reporter: Tom Copeland Assigned To: Carlos Sanchez PMD is a Java source code analyzer. It finds unused variables, empty catch blocks, unnecessary object creation, and so forth. -- 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: (MPPMD-29) Upgrade to PMD 3.9
[ http://jira.codehaus.org/browse/MPPMD-29?page=comments#action_84516 ] Francois Le Droff commented on MPPMD-29: I meant unofficial maven-pmd-plugin-1.10 plugin Upgrade to PMD 3.9 -- Key: MPPMD-29 URL: http://jira.codehaus.org/browse/MPPMD-29 Project: maven-pmd-plugin Issue Type: Task Affects Versions: 1.9 Reporter: Anthony Whitford Assigned To: Jeff Jensen Fix For: 1.10 PMD 3.8 was released October 4, 2006. The Maven plugin should be updated too. http://sourceforge.net/project/shownotes.php?release_id=452776group_id=56262 -- 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: (MPPMD-29) Upgrade to PMD 3.9
[ http://jira.codehaus.org/browse/MPPMD-29?page=all ] Francois Le Droff updated MPPMD-29: --- Attachment: maven-pmd-plugin-1.10.jar For those like me who can't wait, I'll attach my unofficial maven-pmd-plugin-1.10 plugin that bundles pmd 3.9 you'll need to have asm 3.0 in your local maven1 repository though ! Upgrade to PMD 3.9 -- Key: MPPMD-29 URL: http://jira.codehaus.org/browse/MPPMD-29 Project: maven-pmd-plugin Issue Type: Task Affects Versions: 1.9 Reporter: Anthony Whitford Assigned To: Jeff Jensen Fix For: 1.10 Attachments: maven-pmd-plugin-1.10.jar PMD 3.8 was released October 4, 2006. The Maven plugin should be updated too. http://sourceforge.net/project/shownotes.php?release_id=452776group_id=56262 -- 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: (MAVENUPLOAD-1310) NanoXML Lite
NanoXML Lite Key: MAVENUPLOAD-1310 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1310 Project: maven-upload-requests Issue Type: Task Reporter: Tassilo Schweyer NanoXML Lite is an extremely small (6KB) XML parser -- 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: (CONTINUUM-1030) Build for official release leaves a dirty working copy if it fails
[ http://jira.codehaus.org/browse/CONTINUUM-1030?page=all ] Edwin Punzalan updated CONTINUUM-1030: -- Attachment: CONTINUUM-1030-continuum.patch Attached a patch to allow a rollback after a release. Build for official release leaves a dirty working copy if it fails -- Key: CONTINUUM-1030 URL: http://jira.codehaus.org/browse/CONTINUUM-1030 Project: Continuum Issue Type: Bug Components: Core system Affects Versions: 1.1 Reporter: Carlos Sanchez Assigned To: Edwin Punzalan Priority: Critical Fix For: 1.1 Attachments: CONTINUUM-1030-continuum.patch if release breaks after modyfing the pom the working copy is left dirty, with a modified pom and you can't release again, it complains with pom is not snapshot -- 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] Work stopped: (CONTINUUM-1030) Build for official release leaves a dirty working copy if it fails
[ http://jira.codehaus.org/browse/CONTINUUM-1030?page=all ] Work on CONTINUUM-1030 stopped by Edwin Punzalan. Build for official release leaves a dirty working copy if it fails -- Key: CONTINUUM-1030 URL: http://jira.codehaus.org/browse/CONTINUUM-1030 Project: Continuum Issue Type: Bug Components: Core system Affects Versions: 1.1 Reporter: Carlos Sanchez Assigned To: Edwin Punzalan Priority: Critical Fix For: 1.1 Attachments: CONTINUUM-1030-continuum.patch if release breaks after modyfing the pom the working copy is left dirty, with a modified pom and you can't release again, it complains with pom is not snapshot -- 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: (SCM-269) Perforce support doesn't work when there's a space in the local path
Perforce support doesn't work when there's a space in the local path Key: SCM-269 URL: http://jira.codehaus.org/browse/SCM-269 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-perforce Affects Versions: 1.0-beta-4 Reporter: David Jackman Create a view of a Maven project in Perforce in a local directory whose path contains a space. Perform some SCM goal (I was trying to scm:update). It won't work. The error message is very cryptic (Unable to sync. Are you logged in?). From the looks of it, the client command (which is run just before the sync command) has problems, but these problems aren't reported. I think the main problem is the fact that the local path is used in the client name, and client names can't contain spaces. Other elements of the client (root and view) also will contain spaces, but I don't know if Perforce has a problem with these. -- 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: (MRELEASE-190) scmTagPhase scm comment when creating the branch/tag directory uses the prefix [maven-scm]
scmTagPhase scm comment when creating the branch/tag directory uses the prefix [maven-scm] -- Key: MRELEASE-190 URL: http://jira.codehaus.org/browse/MRELEASE-190 Project: Maven 2.x Release Plugin Issue Type: Bug Reporter: Edwin Punzalan -- 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: (MNG-2318) When a project has modules and its parent is not preinstalled the build fails
[ http://jira.codehaus.org/browse/MNG-2318?page=all ] Jason van Zyl updated MNG-2318: --- Fix Version/s: (was: 2.0.5) 2.0.6 When a project has modules and its parent is not preinstalled the build fails - Key: MNG-2318 URL: http://jira.codehaus.org/browse/MNG-2318 Project: Maven 2 Issue Type: Bug Components: Inheritance and Interpolation Affects Versions: 2.0.4 Reporter: Carlos Sanchez Priority: Critical Fix For: 2.0.6 . |-- A | `-- pom.xml (A) |-- C | `-- pom.xml (C) - module of B `-- pom.xml (B) C parent is B and B parent is A, trying to build B it fails -- 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: (MNG-2206) bad properties interpolation with profiles
[ http://jira.codehaus.org/browse/MNG-2206?page=all ] Jason van Zyl updated MNG-2206: --- Fix Version/s: (was: 2.0.5) 2.0.6 bad properties interpolation with profiles --- Key: MNG-2206 URL: http://jira.codehaus.org/browse/MNG-2206 Project: Maven 2 Issue Type: Bug Components: Inheritance and Interpolation Affects Versions: 2.0.3 Environment: cygwin Reporter: Olivier Lamy Assigned To: Edwin Punzalan Priority: Blocker Fix For: 2.0.6 Attachments: MNG-2206-maven-project.patch, pom.xml Original Estimate: 2 hours Remaining Estimate: 2 hours create two profiles in your settings.xml - id test with a property testdev/test - id snapshots with a property testsnapshots/test activeProfiles activeProfiledev/activeProfile activeProfilesnapshots/activeProfile /activeProfiles With the attached pom run : mvn validate : [echo] dev mvn -P snapshots validate : [echo] dev Olivier -- 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: (MNG-2000) Create comprehensive profiles documentation
[ http://jira.codehaus.org/browse/MNG-2000?page=all ] Jason van Zyl updated MNG-2000: --- Fix Version/s: (was: 2.0.5) 2.0.6 Create comprehensive profiles documentation --- Key: MNG-2000 URL: http://jira.codehaus.org/browse/MNG-2000 Project: Maven 2 Issue Type: Task Components: Documentation: Guides Reporter: John Casey Assigned To: John Casey Priority: Critical Fix For: 2.0.6 Original Estimate: 16 hours Time Spent: 1 day Remaining Estimate: 0 minutes This document should draw from the mailing list, FAQ wiki, MNGFAQ jira project (on codehaus), existing site documentation, project source code, and any IRC conversations necessary. It should include: * How can I tell which profiles are in effect during a build? * What are the different types of profile? Where is each defined? * Which areas of a POM can be customized by each type of profile? Why? - settings-defined and profiles.xml-defined only modify properties, repositories, and pluginRepositories. This is necessary to preserve the portability of the pom as much as possible, since these two locations are not installed/deployed to the repository system. * How can a profile be triggered? How does this vary according to the type of profile being used? * Profiles are not inherited, but their effects are, because they are applied to the POM before it's used for inheritance. This means a parent POM will have its profiles triggered and applied before it is used to calculate the inherited values for the current POM. Please include this in the documentation as well. There's probably more, but I can't think of it off the top of my head. We need to make this another one of those definitive documents for POM configuration. -- 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] Closed: (MNG-2252) Upgrade to plexus-utils 1.3
[ http://jira.codehaus.org/browse/MNG-2252?page=all ] Jason van Zyl closed MNG-2252. -- Resolution: Fixed We are already at 1.4-alpha-1 Upgrade to plexus-utils 1.3 --- Key: MNG-2252 URL: http://jira.codehaus.org/browse/MNG-2252 Project: Maven 2 Issue Type: Improvement Components: Dependencies Affects Versions: 2.0.4 Reporter: Carlos Sanchez Fix For: 2.0.5 When ready, upgrade to plexus-utils 1.3 This issue is just a placeholder for other ones to depend on -- 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] Closed: (CONTINUUM-1030) Build for official release leaves a dirty working copy if it fails
[ http://jira.codehaus.org/browse/CONTINUUM-1030?page=all ] Emmanuel Venisse closed CONTINUUM-1030. --- Assignee: Emmanuel Venisse (was: Edwin Punzalan) Resolution: Fixed Applied. Thanks Build for official release leaves a dirty working copy if it fails -- Key: CONTINUUM-1030 URL: http://jira.codehaus.org/browse/CONTINUUM-1030 Project: Continuum Issue Type: Bug Components: Core system Affects Versions: 1.1 Reporter: Carlos Sanchez Assigned To: Emmanuel Venisse Priority: Critical Fix For: 1.1 Attachments: CONTINUUM-1030-continuum.patch if release breaks after modyfing the pom the working copy is left dirty, with a modified pom and you can't release again, it complains with pom is not snapshot -- 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: (MNG-1994) Execution order of child plugins is arbitrary if inheritance is involved
[ http://jira.codehaus.org/browse/MNG-1994?page=all ] Jason van Zyl updated MNG-1994: --- Fix Version/s: (was: 2.0.5) 2.1 Execution order of child plugins is arbitrary if inheritance is involved Key: MNG-1994 URL: http://jira.codehaus.org/browse/MNG-1994 Project: Maven 2 Issue Type: Bug Components: Inheritance and Interpolation Affects Versions: 2.0.1 Reporter: John Didion Priority: Critical Fix For: 2.1 Attachments: mergePluginLists.txt This is related to MNG-1499, but different, and, in my opinion, equally important. It makes sense that the order of plugin execution should be the same as it appears in the POM. For example, I have two plugins: one that generates a batch file and one that executes it. These plugins must run in order or the build will fail. However, the current implementation of ModelUtils.mergePluginLists does not respect the order of child plugins. There is also a seperate bug in that the assembledPlugins map is being checked for the presence of child plugins before adding them to the mergedPlugins list, but nothing is ever added to assembledPlugins. So if a plugin exists in a parent and a child, it will end up appearing twice in the child's plugin list. I have re-written this method to fix both these problems. See attached. -- 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: (MNG-2201) Interpolation problem when using surefire
[ http://jira.codehaus.org/browse/MNG-2201?page=all ]
Jason van Zyl updated MNG-2201:
---
Fix Version/s: (was: 2.0.5)
2.0.6
Interpolation problem when using surefire
-
Key: MNG-2201
URL: http://jira.codehaus.org/browse/MNG-2201
Project: Maven 2
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 2.0, 2.0.1, 2.0.3, 2.0.2, 2.0.4
Reporter: Vincent Massol
Assigned To: John Casey
Priority: Critical
Fix For: 2.0.6
Original Estimate: 4 hours
Remaining Estimate: 4 hours
I've just tried the cargo build with the latest trunk versions of
2.0.4-SNAPSHOT and surefire plugin, and it seems there's some interpolation
issue (I don't know if the problem is with the surefire plugin or with maven
core).
Here's what I have:
{code:xml}
build
pluginManagement
plugins
plugin
artifactIdmaven-surefire-plugin/artifactId
configuration
forkModepertest/forkMode
systemProperties
[...]
property
namecargo.target.dir/name
value${project.build.directory}/value
/property
[...]
{code}
It seems the ${project.build.directory} property is no longer getting
resolved as I got a directory named ${project.build.directory} created.
It used to work fine before.
--
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: (MNG-2664) Add native support for webdav
[ http://jira.codehaus.org/browse/MNG-2664?page=all ] Jason van Zyl updated MNG-2664: --- Fix Version/s: (was: 2.0.5) 2.1 This is really going to required more heavy duty changes. Like running extensions like we do plugins. Add native support for webdav - Key: MNG-2664 URL: http://jira.codehaus.org/browse/MNG-2664 Project: Maven 2 Issue Type: New Feature Components: Artifacts and Repositories Affects Versions: 2.0.4 Reporter: Arnaud Heritier Fix For: 2.1 Attachments: MNG-2664.patch Actually with maven 2.0.4 we can't use the deploy:deploy-file goal to add an artifact on a remote repository with webdav. This is really annoying for archiva which supports webdav for uploads. -- 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: (MNG-2713) Maven debug output should show the lifecycle mapping
[ http://jira.codehaus.org/browse/MNG-2713?page=all ] Jason van Zyl updated MNG-2713: --- Fix Version/s: (was: 2.0.5) 2.1 Maven debug output should show the lifecycle mapping Key: MNG-2713 URL: http://jira.codehaus.org/browse/MNG-2713 Project: Maven 2 Issue Type: Improvement Components: Plugins and Lifecycle Affects Versions: 2.0.4 Reporter: Brett Porter Assigned To: Jason van Zyl Fix For: 2.1 debugging errors in this is not fun. The lifecyle mapping should be displayed in debug mode before starting build for a project -- 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: (MNG-2201) Interpolation problem when using surefire
[ http://jira.codehaus.org/browse/MNG-2201?page=all ]
Jason van Zyl updated MNG-2201:
---
Fix Version/s: (was: 2.0.6)
2.0.5
Word is this works in 2.0.4 and now doesn't so that's bad. Checking now,
putting back in 2.0.5 so I don't forget.
Interpolation problem when using surefire
-
Key: MNG-2201
URL: http://jira.codehaus.org/browse/MNG-2201
Project: Maven 2
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 2.0, 2.0.1, 2.0.3, 2.0.2, 2.0.4
Reporter: Vincent Massol
Assigned To: John Casey
Priority: Critical
Fix For: 2.0.5
Original Estimate: 4 hours
Remaining Estimate: 4 hours
I've just tried the cargo build with the latest trunk versions of
2.0.4-SNAPSHOT and surefire plugin, and it seems there's some interpolation
issue (I don't know if the problem is with the surefire plugin or with maven
core).
Here's what I have:
{code:xml}
build
pluginManagement
plugins
plugin
artifactIdmaven-surefire-plugin/artifactId
configuration
forkModepertest/forkMode
systemProperties
[...]
property
namecargo.target.dir/name
value${project.build.directory}/value
/property
[...]
{code}
It seems the ${project.build.directory} property is no longer getting
resolved as I got a directory named ${project.build.directory} created.
It used to work fine before.
--
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: (MNG-2646) [PATCH] MavenProjectBuilder.buildFromRepository(...) does not support profiles
[ http://jira.codehaus.org/browse/MNG-2646?page=all ] Jason van Zyl updated MNG-2646: --- Fix Version/s: (was: 2.0.5) 2.1 Too much surgery required to do this cleanly in 2.0.x. [PATCH] MavenProjectBuilder.buildFromRepository(...) does not support profiles -- Key: MNG-2646 URL: http://jira.codehaus.org/browse/MNG-2646 Project: Maven 2 Issue Type: Bug Components: Profiles Affects Versions: 2.0.4 Reporter: Christian Schulte Fix For: 2.1 Attachments: profile.patch Currently profiles are not injected into models retrieved from a repository. The attached patch was written against /tags/maven-2.0.4 and should apply cleanly. It adds a ProfileManager parameter to the corresponding MavenProjectBuilder.buildFromRepository(...) methods so that profiles are also injected into models build from a repository. -- 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: (MNG-1928) ignores pluginRepository in settings.xml, honors in POM
[ http://jira.codehaus.org/browse/MNG-1928?page=all ] Jason van Zyl updated MNG-1928: --- Fix Version/s: (was: 2.0.5) 2.1 ignores pluginRepository in settings.xml, honors in POM --- Key: MNG-1928 URL: http://jira.codehaus.org/browse/MNG-1928 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0.1 Environment: mvn 2.0.1, jvm 1.5.0_05, OSX 10.4.3 Reporter: Ryan Marsh Fix For: 2.1 if specified in the POM as a plugin repo, maven can use the team.andromda.org/maven2 repo for finding, downloading, and installing plugins. however, settings.xml ignores plugin repos and only checks central if the plugin has never been downloaded before. for instance. if settings.xml has a pluginRepository entry for team.andromda.org/maven2 then: mvn andromdapp:generate should download the andromdapp plugin from our repo. but it doesn't. only central is checked and it fails to find the plugin. -- 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: (MNG-1577) dependencyManagement does not work for transitive dependencies
[ http://jira.codehaus.org/browse/MNG-1577?page=all ] Jason van Zyl updated MNG-1577: --- Fix Version/s: (was: 2.1) 2.0.5 dependencyManagement does not work for transitive dependencies -- Key: MNG-1577 URL: http://jira.codehaus.org/browse/MNG-1577 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0 Reporter: Joerg Schaible Assigned To: Jason van Zyl Fix For: 2.0.5 Attachments: mng1577.patch, mng1577a.patch, mng1577b.patch, mng1577c.patch, mng1577d.patch, mng1577e-trunk.patch, mng1577e.patch, mng1577f.patch, mng1577trunk.patch The dependencyManagement does not work for transient dependencies. The specified version is ignored. Use case: Main POM defines commons-digester-1.6 and commons-beanutils-1.7.0, A-SNAPSHOT and B-SNAPSHOT Project A is child of Main and depends directly on commons-beanutils (version inherited from Main) Project B is child of Main and depends directly on commons-digester (version inherited from Main) Project C is child of Main and depends directly on A B (versions inherited from Main) A is compiled and tests are run using commons-beanutils-1.7.0 B is compiled and tests are run using commons-digester-1.6 and commons-beanutils-1.6, since digester is dependend on this C is compiled and tests are run using commons-beanutils-1.7.0 Integration tests of B did not verify, that B is behaving as expected in this scenario. B might fail with 1.7.0 and it is not even recognized. If I add beanutils also as direct dependency to B, it works fine, but then are transitive dependency useless. It should be possible to define at least in the dependencyManagement, that the versions of transient dependencies also defined in the dependencyManagement have priority. - Jörg -- 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: (MNG-2749) extensions stopped working in 2.0.5-SNAPSHOT
extensions stopped working in 2.0.5-SNAPSHOT Key: MNG-2749 URL: http://jira.codehaus.org/browse/MNG-2749 Project: Maven 2 Issue Type: Bug Components: Artifacts Affects Versions: 2.0.5 Reporter: Brian Fox Priority: Blocker We're testing our build with the latest 2.0.5-SNAPSHOT. We use the checkstyle config described here http://people.apache.org/%7Eoching/maven-checkstyle-plugin/examples/multi-module-config.html and it works perfectly in 2.0.4. Switching to 2.0.5 causes this to not be available on the classpath anymore. -- 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: (CONTINUUM-1113) Continuum doesn't work with MySQL
[ http://jira.codehaus.org/browse/CONTINUUM-1113?page=comments#action_84529 ] Rahul Thakur commented on CONTINUUM-1113: - Here: mysql mysql show variables like %char%; +--+--+ | Variable_name| Value| +--+--+ | character_set_client | latin1 | | character_set_connection | latin1 | | character_set_database | latin1 | | character_set_filesystem | binary | | character_set_results| latin1 | | character_set_server | latin1 | | character_set_system | utf8 | | character_sets_dir | c:\mysql\share\charsets\ | +--+--+ 8 rows in set (0.81 sec) Continuum doesn't work with MySQL - Key: CONTINUUM-1113 URL: http://jira.codehaus.org/browse/CONTINUUM-1113 Project: Continuum Issue Type: Improvement Components: Database Affects Versions: 1.1 Reporter: Carlos Sanchez Assigned To: Carlos Sanchez 2006-10-20 19:23:14,288 [WrapperSimpleAppMain] ERROR RDBMS - Error thrown executing CREATE TABLE `PROJECTNOTIFIER_CONFIGURATION` [SNIP] 2006/10/20 19:23:14 | java.sql.SQLException: BLOB/TEXT column 'STRING_KEY' used in key specification without a key length -- 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: (CONTINUUM-1113) Continuum doesn't work with MySQL
[ http://jira.codehaus.org/browse/CONTINUUM-1113?page=comments#action_84531 ] Carlos Sanchez commented on CONTINUUM-1113: --- The problem is when the database is in utf8 charset Continuum doesn't work with MySQL - Key: CONTINUUM-1113 URL: http://jira.codehaus.org/browse/CONTINUUM-1113 Project: Continuum Issue Type: Improvement Components: Database Affects Versions: 1.1 Reporter: Carlos Sanchez Assigned To: Carlos Sanchez 2006-10-20 19:23:14,288 [WrapperSimpleAppMain] ERROR RDBMS - Error thrown executing CREATE TABLE `PROJECTNOTIFIER_CONFIGURATION` [SNIP] 2006/10/20 19:23:14 | java.sql.SQLException: BLOB/TEXT column 'STRING_KEY' used in key specification without a key length -- 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-2551) pom metadata file gets truncated during install into local repository
[ http://jira.codehaus.org/browse/MNG-2551?page=comments#action_84532 ] Franck HUGOT commented on MNG-2551: --- I get the same problem with maven-metatdata-inhouse.xml and I use scp to deploy artefact on a remote repository. The end of the file is truncated (/metadata) I use proximity as maven proxy. It's a very important problem because with this problem we can't deploy and share projects. Is there a workaround? pom metadata file gets truncated during install into local repository - Key: MNG-2551 URL: http://jira.codehaus.org/browse/MNG-2551 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories, Artifacts Affects Versions: 2.0.4 Environment: Win XP, JDK 1.4 Reporter: Sharmarke Aden Attachments: pom.xml, shared-1.9.0.pom When I attempt to install my project artifact to my local repository it seems that sometimes an incomplete/truncated .pom is deployed to my local repository. It's kind of weird because sometimes it happens and sometimes it doesn't. Any thoughts as to what could cause this? Attached is my pom.xml and the truncated pom meta data artifact deployed to my local repository. One thing I found that's odd is that the size of the truncated pom generated is consistently 4096 bytes. p.s. my pom.xml is UTF-8 encoded and uses Unix style line delimiters. -- 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: (MAVENUPLOAD-1282) PMD 3.9 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1282?page=comments#action_84533 ] Carlos Sanchez commented on MAVENUPLOAD-1282: - current sync info is in http://svn.apache.org/viewvc/maven/archiva/trunk/maven-meeper/src/bin/synchronize/syncopate/conf/m1/objectweb.conf?view=markup PMD 3.9 bundle -- Key: MAVENUPLOAD-1282 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1282 Project: maven-upload-requests Issue Type: Task Reporter: Tom Copeland Assigned To: Carlos Sanchez PMD is a Java source code analyzer. It finds unused variables, empty catch blocks, unnecessary object creation, and so forth. -- 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: (MAVENUPLOAD-1309) iBatis 2.2.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1309?page=comments#action_84534 ] Carlos Sanchez commented on MAVENUPLOAD-1309: - you'd need to ask them to upload it through apache repo, please copy repository at apache dot org iBatis 2.2.0 Key: MAVENUPLOAD-1309 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1309 Project: maven-upload-requests Issue Type: Bug Reporter: Trygve Laugstol http://codehaus.org/~trygvis/ibatis-common-2.2.0.jar http://codehaus.org/~trygvis/ibatis-sqlmap-2.2.0.jar http://codehaus.org/~trygvis/ibatis-dao-2.2.0.jar Note that these jars use a different group id compared to the old ones. This one uses (the correct IMO) org.apache.ibatis, while the old ones used com.ibatis. -- 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: (MAVENUPLOAD-1310) NanoXML Lite
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1310?page=comments#action_84535 ] Carlos Sanchez commented on MAVENUPLOAD-1310: - Check http://maven.apache.org/guides/mini/guide-central-repository-upload.html for minimal pom info NanoXML Lite Key: MAVENUPLOAD-1310 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1310 Project: maven-upload-requests Issue Type: Task Reporter: Tassilo Schweyer NanoXML Lite is an extremely small (6KB) XML parser -- 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] Closed: (MAVENUPLOAD-1280) jMimeMagic 0.1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1280?page=all ] Carlos Sanchez closed MAVENUPLOAD-1280. --- Resolution: Fixed jMimeMagic 0.1.1 -- Key: MAVENUPLOAD-1280 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1280 Project: maven-upload-requests Issue Type: Task Reporter: David Castro Assigned To: Carlos Sanchez Attachments: jmimemagic-0.1.1-bundle.jar jMimeMagic is a Java library for determining the content type of files or streams. -- 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: (MAVENUPLOAD-1304) org.springframework:beandoc:0.7.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1304?page=comments#action_84536 ] Carlos Sanchez commented on MAVENUPLOAD-1304: - If it's not from Spring project it can't be in org.springframework group org.springframework:beandoc:0.7.1 - Key: MAVENUPLOAD-1304 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1304 Project: maven-upload-requests Issue Type: Task Reporter: fabrizio giustina -- 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] Closed: (MNG-2539) Transitive dependencies referenced by a plugin are searched only in the plugin-repositories
[ http://jira.codehaus.org/browse/MNG-2539?page=all ] Jason van Zyl closed MNG-2539. -- Resolution: Fixed This is the intended behaviour, but normally people just set their plugin repos and standard repos to the same url. Transitive dependencies referenced by a plugin are searched only in the plugin-repositories --- Key: MNG-2539 URL: http://jira.codehaus.org/browse/MNG-2539 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle, Dependencies Affects Versions: 2.0.4 Environment: WinXP, JDK 1.5_08 Reporter: Thomas Minor Assigned To: Jason van Zyl Fix For: 2.0.5 Attachments: mng-2539.zip Transitive dependencies referenced by a plugin are searched only in the plugin-repositories In my case, the axis plugin references th javax.activation artifact. this artifact is keep at our site in a 3rd-party repo. If this repo is only addressed in the Repositories, the build fails.If it is also refereced in the pluginRepositories everything works fine. Is this the intended practice? -- 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: (MNG-2750) Remove the notion of pluginRepositories
Remove the notion of pluginRepositories --- Key: MNG-2750 URL: http://jira.codehaus.org/browse/MNG-2750 Project: Maven 2 Issue Type: New Feature Components: Artifacts and Repositories Affects Versions: 2.0.4 Reporter: Jason van Zyl Fix For: 2.1 I really don't think we need separate repositories for plugins. With the current behavior where dependencies are specified in plugins, they can only come from a plugin repository which is sort of useless. I think most people in practice just point their repository and pluginRepository settings at the same URL. -- 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: (MNG-2750) Remove the notion of pluginRepositories
[ http://jira.codehaus.org/browse/MNG-2750?page=all ] Jason van Zyl updated MNG-2750: --- Fix Version/s: 2.1 Remove the notion of pluginRepositories --- Key: MNG-2750 URL: http://jira.codehaus.org/browse/MNG-2750 Project: Maven 2 Issue Type: New Feature Components: Artifacts and Repositories Affects Versions: 2.0.4 Reporter: Jason van Zyl Assigned To: Jason van Zyl Fix For: 2.1 I really don't think we need separate repositories for plugins. With the current behavior where dependencies are specified in plugins, they can only come from a plugin repository which is sort of useless. I think most people in practice just point their repository and pluginRepository settings at the same URL. -- 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] Closed: (MNG-1379) Wrong path for artifacts with system scope
[ http://jira.codehaus.org/browse/MNG-1379?page=all ] Jason van Zyl closed MNG-1379. -- Resolution: Fixed Several ITs for system scoped dependencies. it0063, it0085 Wrong path for artifacts with system scope -- Key: MNG-1379 URL: http://jira.codehaus.org/browse/MNG-1379 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0 Reporter: fabrizio giustina Assigned To: Jason van Zyl Fix For: 2.0.5 Attachments: MNG-1379-maven-project.patch For system dependencies artifact.getFile() returns a wrong file. While dependency.getSystemPath() correctly returns the user-set path, artifact.getPath always returns the path in the local repository. For example a dependency with system path = /test.jar will result in: dependency.getSystemPath() = /test.jar artifact.getFile().getAbsolutePath()= M2_REPO/groupid/artifactid/version/artifactid-1.0.jar -- 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: (MAVENUPLOAD-1304) org.springframework:beandoc:0.7.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1304?page=comments#action_84545 ] fabrizio giustina commented on MAVENUPLOAD-1304: It's already in the repo under that groupId, I just kept the existing one: http://repo1.maven.org/maven2/org/springframework/beandoc/ org.springframework:beandoc:0.7.1 - Key: MAVENUPLOAD-1304 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1304 Project: maven-upload-requests Issue Type: Task Reporter: fabrizio giustina -- 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: (MDEP-56) test-jar
[ http://jira.codehaus.org/browse/MDEP-56?page=all ] Brian Fox updated MDEP-56: -- Fix Version/s: 2.0-alpha-2 test-jar Key: MDEP-56 URL: http://jira.codehaus.org/browse/MDEP-56 Project: Maven 2.x Dependency Plugin Issue Type: Bug Affects Versions: 2.0-alpha-1 Reporter: Yuri Schimke Assigned To: Brian Fox Fix For: 2.0-alpha-2 For the following dependency dependency groupIdXXX/groupId artifactIdmodel/artifactId version1.2.1-SNAPSHOT/version typetest-jar/type /dependency dependency:copy-dependencies creates the wrong JAR file when run with stripVersion = true The created jar file is called model-tests.test-jar It should be called model-tests.jar -- 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: (MDEP-50) dependency:unpack doesn't seem to handle version ranges
[ http://jira.codehaus.org/browse/MDEP-50?page=all ]
Brian Fox updated MDEP-50:
--
Fix Version/s: 2.0-alpha-2
dependency:unpack doesn't seem to handle version ranges
---
Key: MDEP-50
URL: http://jira.codehaus.org/browse/MDEP-50
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Affects Versions: 1.0
Environment: Java 1.5
Reporter: Martin Goldhahn
Assigned To: Brian Fox
Fix For: 2.0-alpha-2
When I use the dependency unpack goal and a version range as shown below,
Maven cannot download the artifact from the repository. There is a version
1.4.1 in the repository. If I use the specific version number 1.4.1. It works.
build
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddependency-maven-plugin/artifactId
executions
execution
idunpack/id
phasecompile/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdmy.package/groupId
artifactIdconcept/artifactId
version[1.4,1.5)/version
classifierres/classifier
outputDirectory${project.build.sourceDirectory}/../webapp/res/outputDirectory
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
--
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: (MDEP-44) unpacking/copying of attached artifacts from reactor projects doesn't work
[ http://jira.codehaus.org/browse/MDEP-44?page=all ] Brian Fox updated MDEP-44: -- Fix Version/s: 2.0-alpha-2 unpacking/copying of attached artifacts from reactor projects doesn't work -- Key: MDEP-44 URL: http://jira.codehaus.org/browse/MDEP-44 Project: Maven 2.x Dependency Plugin Issue Type: Bug Affects Versions: 2.0-alpha-1 Reporter: Richard van der Hoff Fix For: 2.0-alpha-2 Attachments: dependency-issue.zip, diff.txt I have a parent project, which has two modules - one and two. one uses assembly:single to attach an assembly to its build. two depends upon that assembly, and uses dependency:unpack-dependencies to unpack it. This works fine if the projects are built separately - and the assembly is installed in the local repository. However, when using the reactor to build both projects at once, the dependency plugin still looks in the local repository for the assembly, rather than using the artifact which was just built. This either fails, or produces the wrong version of the assembly. I suspect this may be a bug with the reactor mechanism - but I don't really understand how all that works... The attachment demonstrates the problem. -- 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: (MDEP-27) Plugin configuration error message - caused by certain liefecycle bindings
[ http://jira.codehaus.org/browse/MDEP-27?page=all ]
Brian Fox updated MDEP-27:
--
Fix Version/s: 2.0-alpha-2
Plugin configuration error message - caused by certain liefecycle bindings
--
Key: MDEP-27
URL: http://jira.codehaus.org/browse/MDEP-27
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Affects Versions: 1.0
Environment: Maven 2.0.4, MS-XP Pro V 2002
Reporter: Markus Wilke
Priority: Critical
Fix For: 2.0-alpha-2
If a project`s POM contains a configuration, which binds the
dependency:unpack-goal to a certain liefecylce phase,
the execution of other plugins or lifecycle phases on the command line causes
the following error message:
...
[ERROR] BUILD ERROR
[INFO]
[INFO] One or more required plugin parameters are invalid/missing for
'dependency:unpack'
[0] inside the definition for plugin: 'dependency-maven-plugin'specify the
following:
configuration
...
artifactItemsVALUE/artifactItems
/configuration.
...
The direct execution of the configured lifecyclephase on the command line
does not produce any errors.
Here are 2 examples, which reproduce the error message.
Example 1:
---
Plugin configuration in POM:
...
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddependency-maven-plugin/artifactId
inheritedfalse/inherited
executions
execution
phaseinitialize/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdaGroupId/groupId
artifactIdanArtifactId/artifactId
versionaVersion/version
typezip/type
classifiermd/classifier
outputDirectory${project.build.directory}\dependencies/outputDirectory
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
...
Command line execution: mvn eclipse:eclipse
Example 2:
---
Plugin configuration in POM:
...
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddependency-maven-plugin/artifactId
inheritedfalse/inherited
executions
execution
phaseprocess-resources/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
artifactItem
groupIdaGroupId/groupId
artifactIdanArtifactId/artifactId
versionaVersion/version
typezip/type
classifiermd/classifier
outputDirectory${project.build.directory}\dependencies/outputDirectory
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
...
Command line execution: mvn package
In this example, the project also contained Unit Tests which where executed
by the surefire-plugin.
--
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: (MDEP-54) Exclude and Include specific dependencies based on Artifact id or group name
[ http://jira.codehaus.org/browse/MDEP-54?page=all ] Brian Fox updated MDEP-54: -- Fix Version/s: 2.0-alpha-2 Exclude and Include specific dependencies based on Artifact id or group name Key: MDEP-54 URL: http://jira.codehaus.org/browse/MDEP-54 Project: Maven 2.x Dependency Plugin Issue Type: New Feature Affects Versions: 2.0-alpha-1 Reporter: Chris Love Assigned To: Brian Fox Fix For: 2.0-alpha-2 Attachments: newFilters.patch new plugin parameters excludeArtifactId, includeArtifactId, excludeGroupId, includeGroupId comma seperated lists first will implement exact matching laterz will implement regex matching I want too be able too include or exclude specific jars. Sometimes the dependent poms do not setup the scope well. For example I do not want too deploy maven jars! I recommend adding two different filters to match these dependencies. -- 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: (MDEP-26) New goal to write classpath string with all dependencies from local repo
[ http://jira.codehaus.org/browse/MDEP-26?page=all ]
Brian Fox updated MDEP-26:
--
Fix Version/s: 2.0-alpha-2
New goal to write classpath string with all dependencies from local repo
Key: MDEP-26
URL: http://jira.codehaus.org/browse/MDEP-26
Project: Maven 2.x Dependency Plugin
Issue Type: New Feature
Affects Versions: 1.0
Reporter: Anagnostopoulos Kostis
Assigned To: Brian Fox
Priority: Minor
Fix For: 2.0-alpha-2
Attachments: MDEP-26_BuildClasspathMojo.java
Hi to all,
'm wondering whether it would be usefull to make a new mojo that when
executed it will output a text file containing the required classpath string
to run a project directly from the local repository.
For instance, the file would contain a classpath string like that :
{noformat}
/home/foo/.m2/repository/org/java/utils/util/util-1.0.jar:/home/foo/.m2/
{noformat}
The result file could then be used like that:
{noformat}
java -cp `cat resultFile` MyClass
{noformat}
The new goal should maybe a sub-class of AbstractFromDependenciesMojo.
In that case, the useSubDirectoryPerType and useSubDirectoryPerArtifact
params should move to (copy/unpack)-dependencies mojo classes. Anyway, these
params are only used by sub-classes, so, their definition should be propably
inside of those.
Next are the parameters of the mojo i propose:
goal name: dependency:printClasspath
params:
|| Param Name || Type || Description
| outputFile| File | The file to write the classpath string into.
|
| overwrite | boolean| If true, re-write file even when nothing has
changed. |
| includeTypes | String | Comma Separated list of Types to include. |
| excludeTypes | String | Comma Separated list of Types to exclude |
| includeProjectArtifact| boolean | see [this
issue|http://jira.codehaus.org/browse/MDEP-25]. |
--
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: (MDEP-47) Ability to have an includes/excludes feature on the dependency:unpack goal.
[ http://jira.codehaus.org/browse/MDEP-47?page=all ] Brian Fox updated MDEP-47: -- Fix Version/s: 2.0-alpha-2 Ability to have an includes/excludes feature on the dependency:unpack goal. --- Key: MDEP-47 URL: http://jira.codehaus.org/browse/MDEP-47 Project: Maven 2.x Dependency Plugin Issue Type: New Feature Reporter: Paul Shemansky Assigned To: Brian Fox Priority: Minor Fix For: 2.0-alpha-2 Perhaps there is another solution that I'm overlooking, and if so... I apologize, but in the dependency-maven-plugin's dependency:unpack goal, it would be quite convenient to have an option to have an includes/excludes capability which did pattern matched unpack resolutions. I.E. : !-- files I'd like to unpack -- includes include*.class/include /includes excludes exclude*.html/exclude /excludes -- 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: (MDEP-55) generate javadocs and jar src files with releae
[ http://jira.codehaus.org/browse/MDEP-55?page=all ] Brian Fox updated MDEP-55: -- Fix Version/s: 2.0-alpha-2 generate javadocs and jar src files with releae --- Key: MDEP-55 URL: http://jira.codehaus.org/browse/MDEP-55 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Affects Versions: 2.0 Reporter: Chris Love Assigned To: Brian Fox Priority: Minor Fix For: 2.0-alpha-2 Attachments: pompatch.patch see attached pom patch -- 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-1486) Can't use pom properties inside resource directory tag
[ http://jira.codehaus.org/browse/MNG-1486?page=comments#action_84547 ]
Jason Melnick commented on MNG-1486:
This issue needs to be resolved to really get the most out of the inheritance
model. If I've declared the sourceDirectory in a parent pom, the child should
be able to use ${project.build.sourceDirectory} throughout.
Can't use pom properties inside resource directory tag
---
Key: MNG-1486
URL: http://jira.codehaus.org/browse/MNG-1486
Project: Maven 2
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 2.0
Reporter: Filip Vuksanovic
Priority: Minor
Fix For: 2.0.6
I have pom.xml with following snippet:
build
sourceDirectorysrc\JavaSource/sourceDirectory
resources
resource
directorysrc\JavaSource/directory
and it works.
If I use property like this
build
sourceDirectorysrc\JavaSource/sourceDirectory
resources
resource
directory${project.build.sourceDirectory}/directory
it doesn't work.
--
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: (MNG-2751) Resource inheritance isn't additive
Resource inheritance isn't additive --- Key: MNG-2751 URL: http://jira.codehaus.org/browse/MNG-2751 Project: Maven 2 Issue Type: Bug Components: Inheritance and Interpolation Affects Versions: 2.0.4 Environment: All Reporter: Jason Melnick I have an inheritance model as such: Parent_POM (General dependencyManagement, pluginManagement, etc) |--Base_POM (global dependency inclusion, default goal, default plugins, etc) |--Artifact_POM (declares specific artifact type functionality, resources, profiles, etc) |--Project_POM (project specific dependencies, resources, etc) I am attempting to create an hierarchy that will enable a new project to get up and running with very little modification. The issue I am having is if build.resources are declared in the Project_POM they are wiping the Artifact_POM's declarations. I think that resources should always be additive. If nothing else add an inherited tag a la the plugin element's inherited tag. In lieu of that perhaps a resourceManagement section that exposes resource id's that could be selectively added by the child... -- 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: (DOXIA-84) Update of Maven Generated Sites to use 'Built by Maven' logo
[ http://jira.codehaus.org/browse/DOXIA-84?page=comments#action_84550 ] Vincent Siveton commented on DOXIA-84: -- I resized mavenlogo_builtby_w.gif to 90*30 and it appears that built by is too small and unreadable. IMHO we need to have the same font size that [1]. Could you provide new readable images, directly in png format and in the correct size? Tx. [1] https://svn.apache.org/repos/asf/maven/doxia/trunk/doxia-site-renderer/src/main/resources/org/apache/maven/doxia/siterenderer/resources/images/logos/maven-feather.png Update of Maven Generated Sites to use 'Built by Maven' logo Key: DOXIA-84 URL: http://jira.codehaus.org/browse/DOXIA-84 Project: doxia Issue Type: Task Reporter: Natalie Burdick Attachments: mavenlogo_builtby_b.gif, mavenlogo_builtby_w.gif Attached are some sample images, they would need to be resized to 90 by 30 pixels to work. -- 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: (MAVENUPLOAD-1310) NanoXML Lite
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1310?page=comments#action_84551 ] Tassilo Schweyer commented on MAVENUPLOAD-1310: --- already read that, and used that to generate the package NanoXML Lite Key: MAVENUPLOAD-1310 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1310 Project: maven-upload-requests Issue Type: Task Reporter: Tassilo Schweyer NanoXML Lite is an extremely small (6KB) XML parser -- 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: (MECLIPSE-155) Stop assuming J2EE 1.3
[ http://jira.codehaus.org/browse/MECLIPSE-155?page=comments#action_84555 ] Shelley L commented on MECLIPSE-155: This fix is working in 2.3, but assumes that the j2ee dependency is defined. This dependency is not always needed in the EAR, but is now required in order to configure the WTP ear facet correctly. Can the version be detected by the maven-ear-plugin version configuration or can the eclipse plugin define an additional parameter for this configuration? Stop assuming J2EE 1.3 -- Key: MECLIPSE-155 URL: http://jira.codehaus.org/browse/MECLIPSE-155 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: WTP support Affects Versions: 2.2 Reporter: Matthew Beermann Assigned To: fabrizio giustina Fix For: 2.3 Attachments: maven-eclipse-plugin.patch Currently, when writing out the WTP facet settings for an EAR, the eclipse goal is assuming J2EE version 1.3. This is a problem, as certain functionality could be disabled or broken in the IDE if we're actually working on a 1.4 project. The source code contains a comment saying as much. I'm attaching a patch that does the TODO, and lets the goal sense if we're running on J2EE 1.4. -- 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: (MNG-2749) extensions stopped working in 2.0.5-SNAPSHOT
[ http://jira.codehaus.org/browse/MNG-2749?page=all ] Brian Fox updated MNG-2749: --- Attachment: checkstyle-demo.zip The attached builds successfully when run with maven 2.0.4 but fails when run with 2.0.5-SNAPSHOT [ERROR] BUILD ERROR [INFO] --- [INFO] An error has occurred in Checkstyle report generation. Embedded error: Unable to find configuration file location. Unable to find location 'stc_checks.xml' as URL, File or Resource. extensions stopped working in 2.0.5-SNAPSHOT Key: MNG-2749 URL: http://jira.codehaus.org/browse/MNG-2749 Project: Maven 2 Issue Type: Bug Components: Artifacts Affects Versions: 2.0.5 Reporter: Brian Fox Priority: Blocker Attachments: checkstyle-demo.zip We're testing our build with the latest 2.0.5-SNAPSHOT. We use the checkstyle config described here http://people.apache.org/%7Eoching/maven-checkstyle-plugin/examples/multi-module-config.html and it works perfectly in 2.0.4. Switching to 2.0.5 causes this to not be available on the classpath anymore. -- 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-1592) Top level element in POM is not correctly validated
[ http://jira.codehaus.org/browse/MNG-1592?page=comments#action_84561 ] Brett Porter commented on MNG-1592: --- this should not be changed in 2.0.5 - it breaks backwards compat for no good reason. The model POMs are left overs from the early days of Maven. However, I think we'd find there are still some floating around in repositories as you've said, and builds would just break. That's no fun. Top level element in POM is not correctly validated --- Key: MNG-1592 URL: http://jira.codehaus.org/browse/MNG-1592 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0 Reporter: Carlos Sanchez Fix For: 2.0.5 Attachments: it1019.patch this pom doesn't make the build break modelzz modelVersion4.0.0/modelVersion groupIdtest/groupId artifactIdtest/artifactId version1.0/version /modelzz and I'm starting to see wrong poms with a top level model instead of project -- 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: (MNG-2749) extensions stopped working in 2.0.5-SNAPSHOT
[ http://jira.codehaus.org/browse/MNG-2749?page=all ] Brett Porter updated MNG-2749: -- Fix Version/s: 2.0.5 extensions stopped working in 2.0.5-SNAPSHOT Key: MNG-2749 URL: http://jira.codehaus.org/browse/MNG-2749 Project: Maven 2 Issue Type: Bug Components: Artifacts Affects Versions: 2.0.5 Reporter: Brian Fox Assigned To: Brett Porter Priority: Blocker Fix For: 2.0.5 Attachments: checkstyle-demo.zip We're testing our build with the latest 2.0.5-SNAPSHOT. We use the checkstyle config described here http://people.apache.org/%7Eoching/maven-checkstyle-plugin/examples/multi-module-config.html and it works perfectly in 2.0.4. Switching to 2.0.5 causes this to not be available on the classpath anymore. -- 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: (MECLIPSE-212) Add POM Schema to pom.xml
Add POM Schema to pom.xml - Key: MECLIPSE-212 URL: http://jira.codehaus.org/browse/MECLIPSE-212 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Reporter: Ben Tatham Priority: Minor The POM Editor does not include the XML Schema for POMs in the pom.xml. In fact, if I add it manually, and then use the Add Dependency feature, it takes it away. Having the Schema available make it really nice to use the build in XML Editor features of Eclipse when manually modifying the POM. This should be an extremely trivial thing to... project xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; instead of just project -- 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-2731) Regression: new container handling cannot locate resources properly
[ http://jira.codehaus.org/browse/MNG-2731?page=comments#action_84567 ]
Vincent Siveton commented on MNG-2731:
--
I tried {{mvn site}} with 2.0.x and 2.1-SNAPSHOT and I got the NPE.
The pb seems to come in plexus (maybe plexus-container-default) when we
upgraded plexus-i18n from 1.0.6 to 1.0-beta-7-SNAPSHOT in doxia-site-renderer
It is the same, if we used in doxia-site-renderer:
plexus-i18n:1.0.6
plexus-velocity:1.1.4
Regression: new container handling cannot locate resources properly
---
Key: MNG-2731
URL: http://jira.codehaus.org/browse/MNG-2731
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.1
Reporter: Brett Porter
Priority: Blocker
Run: mvn project-info-reports:scm on any Maven project.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Can't find bundle for base name project-info-report, locale en_AU
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: Can't find bundle for base name
project-info-report, locale en_AU
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:141)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:550)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:346)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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:408)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
Caused by: java.util.MissingResourceException: Can't find bundle for base
name project-info-report, locale en_AU
at
org.codehaus.plexus.i18n.DefaultI18N.cacheBundle(DefaultI18N.java:394)
at
org.codehaus.plexus.i18n.DefaultI18N.getBundle(DefaultI18N.java:157)
at
org.codehaus.plexus.i18n.DefaultI18N.getString(DefaultI18N.java:206)
at
org.apache.maven.report.projectinfo.ScmReport.getName(ScmReport.java:68)
at
org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute(AbstractProjectInfoReport.java:158)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:435)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:311)
... 11 more
This works in Maven 2.0.4/2.0.5-SNAPSHOT, but not on trunk.
--
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-2731) Regression: new container handling cannot locate resources properly
[ http://jira.codehaus.org/browse/MNG-2731?page=comments#action_84570 ] Brett Porter commented on MNG-2731: --- Vincent - I get this too, but it's a bug in the MPIR plugin so should be filed there. Thanks. Regression: new container handling cannot locate resources properly --- Key: MNG-2731 URL: http://jira.codehaus.org/browse/MNG-2731 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.1 Reporter: Brett Porter Priority: Blocker Run: mvn project-info-reports:scm on any Maven project. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Can't find bundle for base name project-info-report, locale en_AU [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Can't find bundle for base name project-info-report, locale en_AU at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:141) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:550) at org.apache.maven.cli.MavenCli.main(MavenCli.java:346) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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:408) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) Caused by: java.util.MissingResourceException: Can't find bundle for base name project-info-report, locale en_AU at org.codehaus.plexus.i18n.DefaultI18N.cacheBundle(DefaultI18N.java:394) at org.codehaus.plexus.i18n.DefaultI18N.getBundle(DefaultI18N.java:157) at org.codehaus.plexus.i18n.DefaultI18N.getString(DefaultI18N.java:206) at org.apache.maven.report.projectinfo.ScmReport.getName(ScmReport.java:68) at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute(AbstractProjectInfoReport.java:158) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:435) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:311) ... 11 more This works in Maven 2.0.4/2.0.5-SNAPSHOT, but not on trunk. -- 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] Closed: (CONTINUUM-1113) Continuum doesn't work with MySQL
[ http://jira.codehaus.org/browse/CONTINUUM-1113?page=all ] Carlos Sanchez closed CONTINUUM-1113. - Resolution: Won't Fix Use MySQL 5.0.3 with a non UTF8 database until their bug is fixed, or apply changes to the application.xml as detailed in previous comment Continuum doesn't work with MySQL - Key: CONTINUUM-1113 URL: http://jira.codehaus.org/browse/CONTINUUM-1113 Project: Continuum Issue Type: Improvement Components: Database Affects Versions: 1.1 Reporter: Carlos Sanchez Assigned To: Carlos Sanchez Attachments: mysql-CONTINUUM-1113.patch 2006-10-20 19:23:14,288 [WrapperSimpleAppMain] ERROR RDBMS - Error thrown executing CREATE TABLE `PROJECTNOTIFIER_CONFIGURATION` [SNIP] 2006/10/20 19:23:14 | java.sql.SQLException: BLOB/TEXT column 'STRING_KEY' used in key specification without a key length -- 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] Closed: (MRM-227) Archiva doesn't suppost UTF-8 databases in Mysql
[ http://jira.codehaus.org/browse/MRM-227?page=all ]
Carlos Sanchez closed MRM-227.
--
Assignee: Carlos Sanchez
Resolution: Won't Fix
Fix Version/s: (was: 1.0)
Use MySQL 5.0.3 with a non UTF8 database until MySQL bug
http://bugs.mysql.com/bug.php?id=25480 is fixed, or change the application.xml
as follows:
Add inside component org.codehaus.plexus.jdo.JdoFactory, configuration,
otherProperties:
!-- this is required for some MySQL versions and configurations, see
CONTINUUM-1113 --
property
nameorg.jpox.rdbms.stringDefaultLength/name
value255/value
/property
Archiva doesn't suppost UTF-8 databases in Mysql
Key: MRM-227
URL: http://jira.codehaus.org/browse/MRM-227
Project: Archiva
Issue Type: Bug
Components: Users/Security
Affects Versions: 1.0
Environment: Linux jtbox01 2.4.21-37.0.1.ELsmp #1 SMP Wed Jan 11
18:35:45 EST 2006 i686 athlon i386 GNU/Linux
jdk1.5.0_07 + apache-tomcat-5.5.17 + mysql-5.0.22
Reporter: Arnaud Heritier
Assigned To: Carlos Sanchez
If the mysql database is created with Collation utf8_unicode_ci I receive
this error when tables are created :
{code}
2006-11-17 14:29:13,782 [http-8080-Processor25] ERROR RDBMS
- Error thrown executing CREATE TABLE `OPERATIONS`
(
`NAME` VARCHAR(256) BINARY NOT NULL,
`DESCRIPTION` VARCHAR(256) BINARY NULL,
`PERMANENT` BIT NOT NULL,
`RESOURCE_REQUIRED` BIT NOT NULL,
PRIMARY KEY (`NAME`)
) ENGINE=INNODB : Specified key was too long; max key length is 765 bytes
java.sql.SQLException: Specified key was too long; max key length is 765 bytes
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2975)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1600)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1695)
at com.mysql.jdbc.Connection.execSQL(Connection.java:2998)
at com.mysql.jdbc.Connection.execSQL(Connection.java:2927)
at com.mysql.jdbc.Statement.execute(Statement.java:535)
at
org.apache.tomcat.dbcp.dbcp.DelegatingStatement.execute(DelegatingStatement.java:261)
at
org.jpox.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:561)
at
org.jpox.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:516)
at
org.jpox.store.rdbms.table.AbstractTable.create(AbstractTable.java:244)
at
org.jpox.store.rdbms.table.AbstractTable.exists(AbstractTable.java:287)
at
org.jpox.store.rdbms.RDBMSManager$ClassAdder.addClassTablesAndValidate(RDBMSManager.java:3006)
at
org.jpox.store.rdbms.RDBMSManager$ClassAdder.run(RDBMSManager.java:2540)
at
org.jpox.store.rdbms.RDBMSManager$MgmtTransaction.execute(RDBMSManager.java:2397)
at org.jpox.store.rdbms.RDBMSManager.addClasses(RDBMSManager.java:603)
at org.jpox.store.rdbms.RDBMSManager.addClass(RDBMSManager.java:617)
at org.jpox.store.StoreManager.getDatastoreClass(StoreManager.java:1016)
at org.jpox.store.rdbms.RDBMSManager.getExtent(RDBMSManager.java:1134)
at
org.jpox.AbstractPersistenceManager.getExtent(AbstractPersistenceManager.java:2216)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.getAllObjects(JdoTool.java:199)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.getAllObjects(JdoTool.java:182)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.triggerInit(JdoTool.java:131)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.getPersistenceManager(JdoTool.java:118)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.getObjectById(JdoTool.java:236)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.objectExistsById(JdoTool.java:283)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoRbacManager.roleExists(JdoRbacManager.java:124)
at
org.codehaus.plexus.rbac.profile.AbstractRoleProfile.getRole(AbstractRoleProfile.java:236)
at
org.codehaus.plexus.rbac.profile.DefaultRoleProfileManager.getRole(DefaultRoleProfileManager.java:72)
at
org.codehaus.plexus.security.ui.web.checks.security.RequiredRolesEnvironmentCheck.validateEnvironment(RequiredRolesEnvironmentCheck.java:64)
at
org.codehaus.plexus.security.ui.web.interceptor.EnvironmentCheckInterceptor.init(EnvironmentCheckInterceptor.java:78)
at
org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(PlexusObjectFactory.java:101)
at
com.opensymphony.xwork.config.providers.InterceptorBuilder.constructInterceptorReference(InterceptorBuilder.java:48)
at
[jira] Updated: (CONTINUUM-1103) Build Fresh checkbox doesn't stay checked
[ http://jira.codehaus.org/browse/CONTINUUM-1103?page=all ] Marcelo Takeshi Fukushima updated CONTINUUM-1103: - Attachment: buildFresh.patch A patch to ContinuumStoreTest and AbstractContinuumStoreTestCase to check if the buildFresh attribute is being correctly persisted Build Fresh checkbox doesn't stay checked - Key: CONTINUUM-1103 URL: http://jira.codehaus.org/browse/CONTINUUM-1103 Project: Continuum Issue Type: Bug Components: Web - UI Affects Versions: 1.1 Reporter: Wendy Smoak Attachments: buildFresh.patch To reproduce: Project Groups - [any group] - Build Definitions tab 1. Edit a build definition 2. check the 'Build Fresh' checkbox 3. Save 4. Edit the same build definition The checkbox should remain checked, but it does not. -- 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] Work started: (CONTINUUM-1105) Duplicate email notifications with notifier in pom.xml
[ http://jira.codehaus.org/browse/CONTINUUM-1105?page=all ] Work on CONTINUUM-1105 started by Maria Odea Ching. Duplicate email notifications with notifier in pom.xml -- Key: CONTINUUM-1105 URL: http://jira.codehaus.org/browse/CONTINUUM-1105 Project: Continuum Issue Type: Bug Components: Notifier - Mail Affects Versions: 1.1 Reporter: Wendy Smoak Assigned To: Maria Odea Ching When there is a notifier in the pom, and a group of projects (such as maven/plugins/trunk/pom.xml) is added under the groupId in the pom, every notification email is duplicated. In the UI for each project, the notifier correctly shows From Project. It doesn't look like two notifiers have been added. 20070102 IRC conversation about adding maven/plugins/trunk/pom.xml under various groupIds: wsmoak what could make continuum send duplicate emails? wsmoak I've added and deleted all of maven/plugins/trunk/pom.xml a few times under different project groups. wsmoak When I add it under the pom default org.apache.maven.plugins group, I get duplicate emails for every build. joakim wsmoak, have you verified that there are not duplicate entries for emails in the build defs? joakim I used to get duplicates when I belonged to an distribution-list and a direct email address. wsmoak joakim: there is only the default build definition, and admin is the only member of the group evenisse wsmoak: I think we look at project group notifiers too when we look at project notifier, so we get the project group notifier twice when we send the mail wsmoak it only happens when I add the projects under the pom default group id. If I delete and re-add it to some other group, I only get one email. evenisse yes, because, when you use the default project group, project notifiers are moved to the project group but I think they aren't removed in the project wsmoak okay. and it's only happening with maven/plugins because struts, etc. doesn't have notifiers in the pom. From the log file (email addresses changed...): INFO | jvm 1| 2007/01/02 20:16:39 | 2007-01-02 20:16:39,831 [pool-1-thread-1] INFO ShellCommandHelper:default - Executing: mvn --batch-mode --non-recursive clean install INFO | jvm 1| 2007/01/02 20:16:39 | 2007-01-02 20:16:39,831 [pool-1-thread-1] INFO ShellCommandHelper:default - Working directory: /opt/continuum-1.1-r490629-SNAPSHOT/apps/continuum/webapp/WEB-INF/working-directory/7 INFO | jvm 1| 2007/01/02 20:16:41 | 2007-01-02 20:16:41,660 [pool-1-thread-1] INFO ContinuumBuildExecutor:maven2 - Exit code: 1 INFO | jvm 1| 2007/01/02 20:16:41 | 2007-01-02 20:16:41,944 [pool-1-thread-1] INFO BuildController:default- Performing action deploy-artifact INFO | jvm 1| 2007/01/02 20:16:42 | 2007-01-02 20:16:42,072 [pool-1-thread-1] INFO Notifier:mail - Sending message: From '[EMAIL PROTECTED] [EMAIL PROTECTED]'. INFO | jvm 1| 2007/01/02 20:16:42 | 2007-01-02 20:16:42,072 [pool-1-thread-1] INFO Notifier:mail - Recipient: To '[EMAIL PROTECTED]'. INFO | jvm 1| 2007/01/02 20:16:42 | 2007-01-02 20:16:42,337 [pool-1-thread-1] INFO Notifier:mail - Sending message: From '[EMAIL PROTECTED] [EMAIL PROTECTED]'. INFO | jvm 1| 2007/01/02 20:16:42 | 2007-01-02 20:16:42,337 [pool-1-thread-1] INFO Notifier:mail - Recipient: To '[EMAIL PROTECTED]'. -- 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: (MCHECKSTYLE-65) regression in checkstyle 2.2: config locations seen as null
regression in checkstyle 2.2: config locations seen as null --- Key: MCHECKSTYLE-65 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-65 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Brett Porter Fix For: 2.2 I was just looking at the test Jason added from Brian about the extensions (utilising checkstyle), and I've found an additional problem occurs under Checkstyle 2.2 that works with 2.1. With Maven 2.0.4, change it0111 to use checkstyle 2.2-SNAPSHOT and run mvn -Dtest=MavenIT0111PluginsThatRequireAResourceFromAnExtensionTest test Caused by: org.apache.maven.reporting.MavenReportException: Unable to process null config location. at org.apache.maven.plugin.checkstyle.CheckstyleReport.getConfigFile(CheckstyleReport.java:969) at org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:504) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98) at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:73) ... 18 more -- 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-2749) extensions stopped working in 2.0.5-SNAPSHOT
[ http://jira.codehaus.org/browse/MNG-2749?page=comments#action_84584 ] Brett Porter commented on MNG-2749: --- this works if you use a plugin dependency instead, however I will try and provide a workaround for the old behaviour extensions stopped working in 2.0.5-SNAPSHOT Key: MNG-2749 URL: http://jira.codehaus.org/browse/MNG-2749 Project: Maven 2 Issue Type: Bug Components: Artifacts Affects Versions: 2.0.5 Reporter: Brian Fox Assigned To: Brett Porter Priority: Blocker Fix For: 2.0.5 Attachments: checkstyle-demo.zip We're testing our build with the latest 2.0.5-SNAPSHOT. We use the checkstyle config described here http://people.apache.org/%7Eoching/maven-checkstyle-plugin/examples/multi-module-config.html and it works perfectly in 2.0.4. Switching to 2.0.5 causes this to not be available on the classpath anymore. -- 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-2749) extensions stopped working in 2.0.5-SNAPSHOT
[ http://jira.codehaus.org/browse/MNG-2749?page=comments#action_84585 ] Brian Fox commented on MNG-2749: The extension was chosen because the dependency won't be found if the plugin repo is separate from the regular artifact repo. extensions stopped working in 2.0.5-SNAPSHOT Key: MNG-2749 URL: http://jira.codehaus.org/browse/MNG-2749 Project: Maven 2 Issue Type: Bug Components: Artifacts Affects Versions: 2.0.5 Reporter: Brian Fox Assigned To: Brett Porter Priority: Blocker Fix For: 2.0.5 Attachments: checkstyle-demo.zip We're testing our build with the latest 2.0.5-SNAPSHOT. We use the checkstyle config described here http://people.apache.org/%7Eoching/maven-checkstyle-plugin/examples/multi-module-config.html and it works perfectly in 2.0.4. Switching to 2.0.5 causes this to not be available on the classpath anymore. -- 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: (MNG-2752) Ant tasks does not support updatePolicy correctly
Ant tasks does not support updatePolicy correctly - Key: MNG-2752 URL: http://jira.codehaus.org/browse/MNG-2752 Project: Maven 2 Issue Type: Bug Components: Ant tasks Affects Versions: 2.0.4 Reporter: Chris Hilton Attachments: build.xml Attached is an example build.xml file. The relevant line is: snapshots enabled=true updatePolicy=never/ I completely remove the com.alterpoint.thirdPart:example directory from my local repository and, in a separate project, I build a com.alterpoint.thirdParty:example:6.0-SNAPSHOT artifact and install it back into the local repository so it's the only version there. With regular Maven, because I have a locally installed snapshot and updatePolicy=never, nothing is downloaded and it references that snapshot directly. When I run the attached build file, though, I get the following output: F:\Temp\scratchant Buildfile: build.xml [INFO] snapshot com.alterpoint.thirdParty:example:6.0-SNAPSHOT: checking for updates from central Downloading: com/alterpoint/thirdParty/example/6.0-SNAPSHOT/example-6.0-20070110.005843-3.pom Transferring 2K Downloading: com/alterpoint/thirdParty/example/6.0-SNAPSHOT/example-6.0-20070110.005843-3.jar Transferring 17K dist: [copy] Copying 1 file to F:\Temp\scratch BUILD SUCCESSFUL Total time: 1 second F:\Temp\scratch The Maven Ant tasks for some reason decide to download and update over my local SNAPSHOT even though updatePolicy=never is specified. Subsequent build deployments of that artifact remotely do not get downloaded, even if I rebuild a local SNAPSHOT. Only the first local SNAPSHOT, when it's the only SNAPSHOT, seems to cause this behavior. Unfortunately, that's a pretty common occurrence with our build system. -- 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: (CONTINUUM-1103) Build Fresh checkbox doesn't stay checked
[ http://jira.codehaus.org/browse/CONTINUUM-1103?page=all ] Marcelo Takeshi Fukushima updated CONTINUUM-1103: - Attachment: jpox1.1.3.patch it turns out that to use jpox-1.1.3, this class also needs a change Build Fresh checkbox doesn't stay checked - Key: CONTINUUM-1103 URL: http://jira.codehaus.org/browse/CONTINUUM-1103 Project: Continuum Issue Type: Bug Components: Web - UI Affects Versions: 1.1 Reporter: Wendy Smoak Attachments: buildFresh.patch, jpox1.1.3.patch To reproduce: Project Groups - [any group] - Build Definitions tab 1. Edit a build definition 2. check the 'Build Fresh' checkbox 3. Save 4. Edit the same build definition The checkbox should remain checked, but it does not. -- 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] Closed: (MNG-2749) extensions stopped working in 2.0.5-SNAPSHOT
[ http://jira.codehaus.org/browse/MNG-2749?page=all ] Brett Porter closed MNG-2749. - Resolution: Fixed extensions stopped working in 2.0.5-SNAPSHOT Key: MNG-2749 URL: http://jira.codehaus.org/browse/MNG-2749 Project: Maven 2 Issue Type: Bug Components: Artifacts Affects Versions: 2.0.5 Reporter: Brian Fox Assigned To: Brett Porter Priority: Blocker Fix For: 2.0.5 Attachments: checkstyle-demo.zip We're testing our build with the latest 2.0.5-SNAPSHOT. We use the checkstyle config described here http://people.apache.org/%7Eoching/maven-checkstyle-plugin/examples/multi-module-config.html and it works perfectly in 2.0.4. Switching to 2.0.5 causes this to not be available on the classpath anymore. -- 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: (MCOMPILER-21) compiler smarts
[ http://jira.codehaus.org/browse/MCOMPILER-21?page=comments#action_84589 ] Christian Goetze commented on MCOMPILER-21: --- 3) Track inventory. If files are removed, remove associated class files and force jar repacking/ 4) Track timestamps. If file timestamp changes (e.g. to an -older- version), rebuild. 5) Track hash signatures for source files. Recompute signature if file timestamp changes, rebuild only if signature changes. 6) Track hash signatures for class files. Repack jars only if hash signatures change. compiler smarts --- Key: MCOMPILER-21 URL: http://jira.codehaus.org/browse/MCOMPILER-21 Project: Maven 2.x Compiler Plugin Issue Type: Bug Reporter: Brett Porter Priority: Minor Fix For: 2.1 there are probably other ways we can make the compiler stale check smarter. List them out here if you think of them. 1) if a snapshot was resolved to a newer version, rebuild everything. -- 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-1) Prompt for pass phrase if it is not supplied
Prompt for pass phrase if it is not supplied Key: MGPG-1 URL: http://jira.codehaus.org/browse/MGPG-1 Project: Maven 2.x GPG Plugin Issue Type: Improvement Reporter: Wendy Smoak The plugin should prompt for a pass phrase if one is not supplied, and should mask the input. (The pass phrase should not be visible or stored in plain text.) Brian Fox suggested the plugin should detect that Maven is running in batch mode, and not prompt in that case. -- 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: (MNG-2753) trunk needs to support passing system properties and environment variables through the CLI into the embedder
trunk needs to support passing system properties and environment variables through the CLI into the embedder Key: MNG-2753 URL: http://jira.codehaus.org/browse/MNG-2753 Project: Maven 2 Issue Type: Bug Components: Command Line Affects Versions: 2.1 Reporter: Brett Porter Priority: Blocker handling was wisely removed from maven-project itself, but for backwards compatibility we need to still support the population of properties from system properties and environment variables at the CLI level. These variables should be passed in to the embedder. -- 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: (MNG-2754) System Properties profile activation should move to Execution Properties activation
System Properties profile activation should move to Execution Properties activation --- Key: MNG-2754 URL: http://jira.codehaus.org/browse/MNG-2754 Project: Maven 2 Issue Type: Task Components: Profiles Affects Versions: 2.1 Reporter: Jason van Zyl Fix For: 2.1 Any -D options from the CLI should be turned into execution properties and the activator which relies on system properties should use activation properties. -- 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: (MNG-2754) System Properties profile activation should move to Execution Properties activation
[ http://jira.codehaus.org/browse/MNG-2754?page=all ] Jason van Zyl updated MNG-2754: --- Fix Version/s: 2.1 System Properties profile activation should move to Execution Properties activation --- Key: MNG-2754 URL: http://jira.codehaus.org/browse/MNG-2754 Project: Maven 2 Issue Type: Task Components: Profiles Affects Versions: 2.1 Reporter: Jason van Zyl Assigned To: Jason van Zyl Fix For: 2.1 Any -D options from the CLI should be turned into execution properties and the activator which relies on system properties should use activation properties. -- 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: (MNG-1577) dependencyManagement does not work for transitive dependencies
[ http://jira.codehaus.org/browse/MNG-1577?page=all ] Jason van Zyl updated MNG-1577: --- Fix Version/s: (was: 2.0.5) 2.0.6 dependencyManagement does not work for transitive dependencies -- Key: MNG-1577 URL: http://jira.codehaus.org/browse/MNG-1577 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0 Reporter: Joerg Schaible Assigned To: Jason van Zyl Fix For: 2.0.6 Attachments: mng1577.patch, mng1577a.patch, mng1577b.patch, mng1577c.patch, mng1577d.patch, mng1577e-trunk.patch, mng1577e.patch, mng1577f.patch, mng1577trunk.patch The dependencyManagement does not work for transient dependencies. The specified version is ignored. Use case: Main POM defines commons-digester-1.6 and commons-beanutils-1.7.0, A-SNAPSHOT and B-SNAPSHOT Project A is child of Main and depends directly on commons-beanutils (version inherited from Main) Project B is child of Main and depends directly on commons-digester (version inherited from Main) Project C is child of Main and depends directly on A B (versions inherited from Main) A is compiled and tests are run using commons-beanutils-1.7.0 B is compiled and tests are run using commons-digester-1.6 and commons-beanutils-1.6, since digester is dependend on this C is compiled and tests are run using commons-beanutils-1.7.0 Integration tests of B did not verify, that B is behaving as expected in this scenario. B might fail with 1.7.0 and it is not even recognized. If I add beanutils also as direct dependency to B, it works fine, but then are transitive dependency useless. It should be possible to define at least in the dependencyManagement, that the versions of transient dependencies also defined in the dependencyManagement have priority. - Jörg -- 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-2684) local repository can only be specified per user, not per build, which impacts scalability
[ http://jira.codehaus.org/browse/MNG-2684?page=comments#action_84591 ] Marilyn E. Sander commented on MNG-2684: While working up a test case, I discovered antlib.xml, which has taskdefs for remoteRepository and localRepository. How do I find documentation for those? Do I have to download the sources and read them? Thanks. local repository can only be specified per user, not per build, which impacts scalability - Key: MNG-2684 URL: http://jira.codehaus.org/browse/MNG-2684 Project: Maven 2 Issue Type: Improvement Components: Ant tasks Affects Versions: 2.0.4 Environment: Linux Reporter: Marilyn E. Sander Because the local repository can only be specified in the ~/.m2/settings.xml or ~/.m2/ant/settings.xml file, there can be only one local repository per user per executing build. Worst case, the repository is on a mounted filesystem and thus the user can run only one build at a time. Best case, the repository is on the local machine, and the user can run one build per machine. This does not scale to an installation with large-capacity build servers, where one user might run several builds of different products or releases simultaneously, with each build using its own local repository. This can be done with Maven alone, but not with Maven ant tasks. I would like a mechanism for the ant tasks to pick up the local repository from a property, an environment variable, or a file in the base directory for the build. Even $M2_HOME/conf/settings.xml would be acceptable, as we could jigger $M2_HOME so as to have a unique one for each build. Any mechanism would be suitable, as long as it would allow a unique local repostory for each build. Feel free to lower this from major to minor if you do not agree with the impact. For our shop it is a major inconvenience, and we are considering a major rewrite to our build in order to avoid the ant tasks. We really need to make good use of our build servers. -- 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: (MRM-266) Changed the location of the Run Now link in the Configuration page.
Changed the location of the Run Now link in the Configuration page. - Key: MRM-266 URL: http://jira.codehaus.org/browse/MRM-266 Project: Archiva Issue Type: Improvement Components: web application Affects Versions: 1.0 Reporter: Dawn Angelito Priority: Minor If your window is not wide, you have to scroll right and may not even notice that Run Now is there. Link is now under Last Indexing Time. -- 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
