[jira] Commented: (MJAR-106) Excludes do not work as described on the Usage page
[
http://jira.codehaus.org/browse/MJAR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131857#action_131857
]
Michael Mattox commented on MJAR-106:
-
You say it works for you, have you tried excluding resources or just classes?
Maybe it works for classes but not for resources??
If you confirm it works for resources I will make a test project and submit it.
Thanks.
> Excludes do not work as described on the Usage page
> ---
>
> Key: MJAR-106
> URL: http://jira.codehaus.org/browse/MJAR-106
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Michael Mattox
>
> The jar plugin usage page gives an example:
> {code:xml}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
> **/service/*
>
>
>
> {code}
> If I use excludes, such as this:
> {code:xml}
>
>
>
> **/*.properties
>
>
> {code}
> It doesn't work. I get the properties in both my jar and my -tests.jar.
> However, if I add executions to the plugin configuration, like this:
> {code:xml}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
>
> jar
>
>
>
>
> **/*.properties
>
>
>
>
>
> {code}
> Then the properties are excluded form my test jar but NOT from my regular
> jar. Here is some debug output:
> {noformat}
> [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-jar-plugin:2.2:jar'
> -->
> [DEBUG] (f) classesDirectory =
> C:\projects\company\projects\pam\workspace\mm-config\target\classes
> [DEBUG] (f) defaultManifestFile =
> C:\projects\company\projects\pam\workspace\mm-config\target\classes\META-INF\MANIFEST.MF
> [DEBUG] (f) finalName = mm-config-1.0-SNAPSHOT
> [DEBUG] (f) forceCreation = false
> [DEBUG] (f) outputDirectory =
> C:\projects\company\projects\pam\workspace\mm-config\target
> [DEBUG] (f) project = MavenProject: company:mm-config:1.0-SNAPSHOT @
> C:\projects\company\projects\pam\workspace\mm-config\pom.xml
> [DEBUG] (f) useDefaultManifestFile = false
> [DEBUG] -- end configuration --
> [INFO] [jar:jar]
> [DEBUG] isUp2date: false (Destination
> C:\projects\company\projects\pam\workspace\mm-config\target\mm-config-1.0-SNAPSHOT.jar
> not found.)
> [INFO] Building jar:
> C:\projects\company\projects\pam\workspace\mm-config\target\mm-config-1.0-SNAPSHOT.jar
> [DEBUG] adding directory META-INF/
> [DEBUG] adding entry META-INF/MANIFEST.MF
> [DEBUG] adding directory commons/
> [DEBUG] adding entry commons/applicationContext.xml
> [DEBUG] adding entry database.properties
> [DEBUG] adding entry log4j.xml
> [DEBUG] adding entry messages-exceptions-commons.properties
> [DEBUG] adding entry messages-warnings-commons.properties
> [DEBUG] adding entry mm2-rmi.properties
> [DEBUG] adding directory META-INF/maven/
> [DEBUG] adding directory META-INF/maven/company/
> [DEBUG] adding directory META-INF/maven/company/mm-config/
> [DEBUG] adding entry META-INF/maven/company/mm-config/pom.xml
> [DEBUG] adding entry META-INF/maven/company/mm-config/pom.properties
> [DEBUG] company:mm-config:jar:1.0-SNAPSHOT (selected for null)
> [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-jar-plugin:2.2:jar'
> -->
> [DEBUG] (f) classesDirectory =
> C:\projects\company\projects\pam\workspace\mm-config\target\classes
> [DEBUG] (f) defaultManifestFile =
> C:\projects\company\projects\pam\workspace\mm-config\target\classes\META-INF\MANIFEST.MF
> [DEBUG] (f) excludes = [Ljava.lang.String;@24dd07a
> [DEBUG] (f) finalName = mm-config-1.0-SNAPSHOT
> [DEBUG] (f) forceCreation = false
> [DEBUG] (f) outputDirectory =
> C:\projects\company\projects\pam\workspace\mm-config\target
> [DEBUG] (f) project = MavenProject: company:mm-config:1.0-SNAPSHOT @
> C:\projects\company\projects\pam\workspace\mm-config\pom.xml
> [DEBUG] (f) useDefaultManifestFile = false
> [DEBUG] -- end configuration --
> [INFO] [jar:
[jira] Closed: (MJAR-101) excluding files from jar doesn't work completely well
[
http://jira.codehaus.org/browse/MJAR-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrizio Munzi closed MJAR-101.
---
Resolution: Won't Fix
Fix Version/s: 2.2
It was not a real issue
> excluding files from jar doesn't work completely well
> -
>
> Key: MJAR-101
> URL: http://jira.codehaus.org/browse/MJAR-101
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: Windows XP, JDK 1.5
>Reporter: Patrizio Munzi
> Fix For: 2.2
>
> Attachments: mavenjarplugin.bug.tar.gz
>
>
> Maven Jar Plugin exclude feature seems not to work completely well.
> It actually excludes the specified files from the built jar but creates
> however the folders path into it.
> Here's my configuration:
> {code:xml}
>
>**/*.properties
>**/*.xml
>**/*.xsd
>
> {code}
> Although all the specified files are actually excluded from the deployed
> jar, the directory paths of the excluded files are still created into
> the jar.
> I mean, if I have the following files under the resources directory:
> resources/log4j.properties
> resources/xml/file.xml
> resources/xml/schema/schema.xsd
> These files won't be included in the built jar, but I'll still have the
> following path into it:
> /xml/schema/
> Find attached a simple project test case to reproduce the problem.
> - Extract it
> - Change to the main dir
> - run: mvn compile
> - run: mvn jar: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: (MJAR-101) excluding files from jar doesn't work completely well
[
http://jira.codehaus.org/browse/MJAR-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131859#action_131859
]
Patrizio Munzi commented on MJAR-101:
-
{quote}
If you want to exclude entire directories, simply tell the plugin:
{code:xml}
**/*.properties
xml/**
{code}
will exclude the directory "xml" and all files underneath it.
{quote}
It works for me.
Issue closed
> excluding files from jar doesn't work completely well
> -
>
> Key: MJAR-101
> URL: http://jira.codehaus.org/browse/MJAR-101
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: Windows XP, JDK 1.5
>Reporter: Patrizio Munzi
> Fix For: 2.2
>
> Attachments: mavenjarplugin.bug.tar.gz
>
>
> Maven Jar Plugin exclude feature seems not to work completely well.
> It actually excludes the specified files from the built jar but creates
> however the folders path into it.
> Here's my configuration:
> {code:xml}
>
>**/*.properties
>**/*.xml
>**/*.xsd
>
> {code}
> Although all the specified files are actually excluded from the deployed
> jar, the directory paths of the excluded files are still created into
> the jar.
> I mean, if I have the following files under the resources directory:
> resources/log4j.properties
> resources/xml/file.xml
> resources/xml/schema/schema.xsd
> These files won't be included in the built jar, but I'll still have the
> following path into it:
> /xml/schema/
> Find attached a simple project test case to reproduce the problem.
> - Extract it
> - Change to the main dir
> - run: mvn compile
> - run: mvn jar: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: (MAVENUPLOAD-2031) rsync-ssh request for naked objects
rsync-ssh request for naked objects --- Key: MAVENUPLOAD-2031 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2031 Project: maven-upload-requests Issue Type: Task Reporter: Robert Matthews "org.nakedobjects","[EMAIL PROTECTED]:/home/groups/n/na/nakedobjects/htdocs/m2-repo/release","rsync_ssh","Robert Matthews","[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] Commented: (MJAR-106) Excludes do not work as described on the Usage page
[
http://jira.codehaus.org/browse/MJAR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131858#action_131858
]
Benjamin Bentmann commented on MJAR-106:
I exluded a log4j.properties from src/main/resources.
> Excludes do not work as described on the Usage page
> ---
>
> Key: MJAR-106
> URL: http://jira.codehaus.org/browse/MJAR-106
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Michael Mattox
>
> The jar plugin usage page gives an example:
> {code:xml}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
> **/service/*
>
>
>
> {code}
> If I use excludes, such as this:
> {code:xml}
>
>
>
> **/*.properties
>
>
> {code}
> It doesn't work. I get the properties in both my jar and my -tests.jar.
> However, if I add executions to the plugin configuration, like this:
> {code:xml}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
>
> jar
>
>
>
>
> **/*.properties
>
>
>
>
>
> {code}
> Then the properties are excluded form my test jar but NOT from my regular
> jar. Here is some debug output:
> {noformat}
> [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-jar-plugin:2.2:jar'
> -->
> [DEBUG] (f) classesDirectory =
> C:\projects\company\projects\pam\workspace\mm-config\target\classes
> [DEBUG] (f) defaultManifestFile =
> C:\projects\company\projects\pam\workspace\mm-config\target\classes\META-INF\MANIFEST.MF
> [DEBUG] (f) finalName = mm-config-1.0-SNAPSHOT
> [DEBUG] (f) forceCreation = false
> [DEBUG] (f) outputDirectory =
> C:\projects\company\projects\pam\workspace\mm-config\target
> [DEBUG] (f) project = MavenProject: company:mm-config:1.0-SNAPSHOT @
> C:\projects\company\projects\pam\workspace\mm-config\pom.xml
> [DEBUG] (f) useDefaultManifestFile = false
> [DEBUG] -- end configuration --
> [INFO] [jar:jar]
> [DEBUG] isUp2date: false (Destination
> C:\projects\company\projects\pam\workspace\mm-config\target\mm-config-1.0-SNAPSHOT.jar
> not found.)
> [INFO] Building jar:
> C:\projects\company\projects\pam\workspace\mm-config\target\mm-config-1.0-SNAPSHOT.jar
> [DEBUG] adding directory META-INF/
> [DEBUG] adding entry META-INF/MANIFEST.MF
> [DEBUG] adding directory commons/
> [DEBUG] adding entry commons/applicationContext.xml
> [DEBUG] adding entry database.properties
> [DEBUG] adding entry log4j.xml
> [DEBUG] adding entry messages-exceptions-commons.properties
> [DEBUG] adding entry messages-warnings-commons.properties
> [DEBUG] adding entry mm2-rmi.properties
> [DEBUG] adding directory META-INF/maven/
> [DEBUG] adding directory META-INF/maven/company/
> [DEBUG] adding directory META-INF/maven/company/mm-config/
> [DEBUG] adding entry META-INF/maven/company/mm-config/pom.xml
> [DEBUG] adding entry META-INF/maven/company/mm-config/pom.properties
> [DEBUG] company:mm-config:jar:1.0-SNAPSHOT (selected for null)
> [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-jar-plugin:2.2:jar'
> -->
> [DEBUG] (f) classesDirectory =
> C:\projects\company\projects\pam\workspace\mm-config\target\classes
> [DEBUG] (f) defaultManifestFile =
> C:\projects\company\projects\pam\workspace\mm-config\target\classes\META-INF\MANIFEST.MF
> [DEBUG] (f) excludes = [Ljava.lang.String;@24dd07a
> [DEBUG] (f) finalName = mm-config-1.0-SNAPSHOT
> [DEBUG] (f) forceCreation = false
> [DEBUG] (f) outputDirectory =
> C:\projects\company\projects\pam\workspace\mm-config\target
> [DEBUG] (f) project = MavenProject: company:mm-config:1.0-SNAPSHOT @
> C:\projects\company\projects\pam\workspace\mm-config\pom.xml
> [DEBUG] (f) useDefaultManifestFile = false
> [DEBUG] -- end configuration --
> [INFO] [jar:jar {execution: default}]
> [DEBUG] isUp2date: true
> [DEBUG] Archive
> C:\projects\company\projects\pam\workspace\mm-config\target\mm-config-1.0-SNAPSHOT.jar
> i
[jira] Created: (MENFORCER-44) the banSnapshot option in requirePluginVersions should distinguish "SNAPSHOT" and timestamps
the banSnapshot option in requirePluginVersions should distinguish "SNAPSHOT" and timestamps Key: MENFORCER-44 URL: http://jira.codehaus.org/browse/MENFORCER-44 Project: Maven 2.x Enforcer Plugin Issue Type: Improvement Components: Standard Rules Affects Versions: 1.0 Reporter: nicolas de loof Assignee: Brian Fox The release plugin now allows to use timestamp dependencies. the requirePluginVersions rule cannot be used with such configuration as it considers a timestamp as a SNAPSHOT. Maybe the SNAPSHOT detection code could be shared ? -- 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: (MASSEMBLY-317) useStrictFiltering requires dependency in all included modules
useStrictFiltering requires dependency in all included modules
--
Key: MASSEMBLY-317
URL: http://jira.codehaus.org/browse/MASSEMBLY-317
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-2
Reporter: Thomas Diesler
With this moduleSet all dependency artifacts must be defined in all included
modules
org.jboss.ws:jbossws-cxf-server
org.jboss.ws:jbossws-cxf-client
server/default/deploy/jbossws.sar
${module.artifactId}.${module.extension}
false
${module.artifactId}.${module.extension}
true
*:cxf-*
*:geronimo-javamail*
*:geronimo-ws-metadata*
*:jaxrpc-api*
*:jaxws-api*
*:neethi*
*:saaj-api*
*:saaj-impl*
*:spring-beans*
*:spring-context*
*:spring-core*
*:wsdl4j*
*:xml-resolver*
*:XmlSchema*
I believe this should be changed such that the dependency is satisfied by at
least one module.
--
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: (MENFORCER-45) does not detect version for plugin configured in profiles
does not detect version for plugin configured in profiles - Key: MENFORCER-45 URL: http://jira.codehaus.org/browse/MENFORCER-45 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Components: Standard Rules Affects Versions: 1.0 Reporter: nicolas de loof Assignee: Brian Fox Here is my POM.xml : ... cxf true org.apache.cxf cxf-codegen-plugin 2.05.-incubator ... [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequirePluginVersions failed with message: Some plugins are missing valid versions:(LATEST RELEASE are not allowed ) org.apache.cxf:cxf-codegen-plugin. The version currently in use is 2.0.5-incubator -- 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: (MENFORCER-45) does not detect version for plugin configured in profiles
[ http://jira.codehaus.org/browse/MENFORCER-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MENFORCER-45. Resolution: Fixed Fix Version/s: 1.0 Add all plugins in profiles as candidates for version check > does not detect version for plugin configured in profiles > - > > Key: MENFORCER-45 > URL: http://jira.codehaus.org/browse/MENFORCER-45 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Standard Rules >Affects Versions: 1.0 >Reporter: nicolas de loof >Assignee: nicolas de loof > Fix For: 1.0 > > > Here is my POM.xml : > ... > > > cxf > > true > > > > > org.apache.cxf > cxf-codegen-plugin > 2.05.-incubator > ... > [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequirePluginVersions > failed with message: > Some plugins are missing valid versions:(LATEST RELEASE are not allowed ) > org.apache.cxf:cxf-codegen-plugin. The version currently in use is > 2.0.5-incubator -- 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: (MENFORCER-44) the banSnapshot option in requirePluginVersions should distinguish "SNAPSHOT" and timestamps
[ http://jira.codehaus.org/browse/MENFORCER-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MENFORCER-44. Assignee: nicolas de loof (was: Brian Fox) Resolution: Fixed Fix Version/s: 1.0 banTimestamps = false allow to user timestamp SNAPSHOTS (as release plugin does) > the banSnapshot option in requirePluginVersions should distinguish "SNAPSHOT" > and timestamps > > > Key: MENFORCER-44 > URL: http://jira.codehaus.org/browse/MENFORCER-44 > Project: Maven 2.x Enforcer Plugin > Issue Type: Improvement > Components: Standard Rules >Affects Versions: 1.0 >Reporter: nicolas de loof >Assignee: nicolas de loof > Fix For: 1.0 > > > The release plugin now allows to use timestamp dependencies. > the requirePluginVersions rule cannot be used with such configuration as it > considers a timestamp as a SNAPSHOT. > Maybe the SNAPSHOT detection code could be shared ? -- 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-3542) Filtering test resources replaces the wrong value
Filtering test resources replaces the wrong value
-
Key: MNG-3542
URL: http://jira.codehaus.org/browse/MNG-3542
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
Environment: Windows XP and Linux
Tried with Maven 2.0.7 upwards
Java 1.5
Reporter: Robert Bracewell
Noticed an oddity with filtering in that it is replacing the wrong properties
under certain conditions. The key thing to note in below mockup is the url
property in pom.xml
Contents of pom.xml:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
http://THIS_IS_A_URL_TO_HIGHLIGHT_THE_BUG
com.maven.bugs
bug1
1
jar
Maven Bug 1
src/test/resources
true
In the src/test/resources directory is a file that contains:
${test.url}
When running mvn clean process-test-resources the file generated in
target/test-classes now contains:
http://THIS_IS_A_URL_TO_HIGHLIGHT_THE_BUG
This is not what I expect as I don't have a property for test.url defined
--
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-441) Packaging type "maven-plugin" causes unresolved dependencies in multi-module build
Packaging type "maven-plugin" causes unresolved dependencies in multi-module build -- Key: MECLIPSE-441 URL: http://jira.codehaus.org/browse/MECLIPSE-441 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Dependencies resolution and build path, Core : Multi-projects Affects Versions: 2.5.1 Environment: Linux 2.6 (Xubuntu 8.0) Reporter: Alex Rau Attachments: maven_bug.tar.bz2 Attached a sample project setup. How to reproduce: - untar attachment - cd into reactor folder - call mvn eclipse:eclipse Artifact x:project_plugin cannot be resolved, however the dependency and the modules set is correct. As soon as the packaging type of the maven-plugin is changed to "jar" it works as expected. Installing the maven-plugin project first is perhaps a workaround (a bad one, not tried yet). Makes however a clean/from scratch multi-module build in eclipse very ugly. -- 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: (MCHANGELOG-84) wrong SVN directory path created when using cascaded pom modules(?)
wrong SVN directory path created when using cascaded pom modules(?)
---
Key: MCHANGELOG-84
URL: http://jira.codehaus.org/browse/MCHANGELOG-84
Project: Maven 2.x Changelog Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: java 1.5.0_13 / mac os x / maven 2.0.7
Reporter: jens breitenstein
When executing "site" the plugin accesses a wrong svn path (see log below).
the pom look similar to this (well, I simplified it a bit :-)
root.pom
...
...
configuration
...
pom (in directory configuration)
--
... root.pom ...
4.0.0
my.group.configuration
PREFIX-configuration
jar
directory layout:
` root-pom
`
` sub-module-pom this file defines the artifact
"PREFIX-configuration.jar"
[INFO] Generating "Change Log" report.
[INFO] Generating changed sets xml to:
/**/trunk/configuration/target/changelog.xml
[INFO] Executing: svn --username --password * --non-interactive log -v
-r "{2008-03-24 13:32:56 +}:{2008-04-24 13:32:56 +}"
https://***/svn/***/trunk/PREFIX-configuration
[INFO] Working directory: //trunk/configuration
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: REPORT request failed on
'/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
svn: '/svn/!svn/bc/461//trunk/PREFIX-configuration' path not found
"PREFIX-configuration" is the artifact name in the "sub-module" pom not a
directory. The root pom access this child pom via the module element
"configuration" which is identical to the directory in the file system and the
svn repository. So correctly the svn command should look like
"https://***/svn/***/trunk/configuration"; and not
"https://***/svn/***/trunk/PREFIX-configuration";.
In case I understand the error message correctly the plugin tries to read a
directory which is named like the artifact-id which is wrong here?
--
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-441) Packaging type "maven-plugin" causes unresolved dependencies in multi-module build
[ http://jira.codehaus.org/browse/MECLIPSE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131886#action_131886 ] Alex Rau commented on MECLIPSE-441: --- Earlier maven-eclipse-plugin versions down to version 2.2 (tried 2.3, 2.4, 2.5 as well) did not resolve the problem. However downgrading to version 2.0.5 for Maven resolved the issue. The problem was introduced with either Maven 2.0.6 (either Maven itself or one of it's plugins) > Packaging type "maven-plugin" causes unresolved dependencies in multi-module > build > -- > > Key: MECLIPSE-441 > URL: http://jira.codehaus.org/browse/MECLIPSE-441 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path, Core : > Multi-projects >Affects Versions: 2.5.1 > Environment: Linux 2.6 (Xubuntu 8.0) >Reporter: Alex Rau > Attachments: maven_bug.tar.bz2 > > > Attached a sample project setup. > How to reproduce: > - untar attachment > - cd into reactor folder > - call mvn eclipse:eclipse > Artifact x:project_plugin cannot be resolved, however the dependency and the > modules set is correct. > As soon as the packaging type of the maven-plugin is changed to "jar" it > works as expected. > Installing the maven-plugin project first is perhaps a workaround (a bad one, > not tried yet). Makes however a clean/from scratch multi-module build in > eclipse very ugly. -- 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: (MCHANGELOG-84) wrong SVN directory path created when using cascaded pom modules(?)
[
http://jira.codehaus.org/browse/MCHANGELOG-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131887#action_131887
]
jens breitenstein commented on MCHANGELOG-84:
-
sorry I forgot that leading spaces are lost the "sub-module-pom" in my
sketched "directory layout" is not indented correctly (imagine 4-6 spaces on
the left, than the layout is fine ;-) "sub-module-pom" is contained within the
sub-directory "configuration".
> wrong SVN directory path created when using cascaded pom modules(?)
> ---
>
> Key: MCHANGELOG-84
> URL: http://jira.codehaus.org/browse/MCHANGELOG-84
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: java 1.5.0_13 / mac os x / maven 2.0.7
>Reporter: jens breitenstein
>
> When executing "site" the plugin accesses a wrong svn path (see log below).
> the pom look similar to this (well, I simplified it a bit :-)
> root.pom
>
>
>...
>
> ...
> configuration
> ...
>
>
>
> pom (in directory configuration)
> --
>
> ... root.pom ...
>
> 4.0.0
> my.group.configuration
> PREFIX-configuration
> jar
>
>
> directory layout:
>
> ` root-pom
> `
> ` sub-module-pom this file defines the artifact
> "PREFIX-configuration.jar"
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to:
> /**/trunk/configuration/target/changelog.xml
> [INFO] Executing: svn --username --password * --non-interactive log
> -v -r "{2008-03-24 13:32:56 +}:{2008-04-24 13:32:56 +}"
> https://***/svn/***/trunk/PREFIX-configuration
> [INFO] Working directory: //trunk/configuration
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on
> '/svn/!svn/bc/461/***/trunk/PREFIX-configuration'
> svn: '/svn/!svn/bc/461//trunk/PREFIX-configuration' path not found
> "PREFIX-configuration" is the artifact name in the "sub-module" pom not a
> directory. The root pom access this child pom via the module element
> "configuration" which is identical to the directory in the file system and
> the svn repository. So correctly the svn command should look like
> "https://***/svn/***/trunk/configuration"; and not
> "https://***/svn/***/trunk/PREFIX-configuration";.
> In case I understand the error message correctly the plugin tries to read a
> directory which is named like the artifact-id which is wrong here?
--
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] Issue Comment Edited: (MECLIPSE-441) Packaging type "maven-plugin" causes unresolved dependencies in multi-module build
[ http://jira.codehaus.org/browse/MECLIPSE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131886#action_131886 ] rauar edited comment on MECLIPSE-441 at 4/23/08 9:21 AM: Earlier maven-eclipse-plugin versions down to version 2.2 (tried 2.3, 2.4, 2.5 as well) did not resolve the problem. However downgrading to version 2.0.5 for Maven resolved the issue. The problem was introduced with Maven 2.0.6 (either Maven itself or one of it's plugins) was (Author: rauar): Earlier maven-eclipse-plugin versions down to version 2.2 (tried 2.3, 2.4, 2.5 as well) did not resolve the problem. However downgrading to version 2.0.5 for Maven resolved the issue. The problem was introduced with either Maven 2.0.6 (either Maven itself or one of it's plugins) > Packaging type "maven-plugin" causes unresolved dependencies in multi-module > build > -- > > Key: MECLIPSE-441 > URL: http://jira.codehaus.org/browse/MECLIPSE-441 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path, Core : > Multi-projects >Affects Versions: 2.5.1 > Environment: Linux 2.6 (Xubuntu 8.0) >Reporter: Alex Rau > Attachments: maven_bug.tar.bz2 > > > Attached a sample project setup. > How to reproduce: > - untar attachment > - cd into reactor folder > - call mvn eclipse:eclipse > Artifact x:project_plugin cannot be resolved, however the dependency and the > modules set is correct. > As soon as the packaging type of the maven-plugin is changed to "jar" it > works as expected. > Installing the maven-plugin project first is perhaps a workaround (a bad one, > not tried yet). Makes however a clean/from scratch multi-module build in > eclipse very ugly. -- 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: (MEAR-86) Add a property to automatically add jars dependencies into application.xml (TEST AND PATCH ATTACHED).
[ http://jira.codehaus.org/browse/MEAR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Recloux updated MEAR-86: --- Attachment: MEAR-86-maven-ear-plugin-with_tests.patch The complete patch including tests. Replaces the previous one > Add a property to automatically add jars dependencies into application.xml > (TEST AND PATCH ATTACHED). > - > > Key: MEAR-86 > URL: http://jira.codehaus.org/browse/MEAR-86 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.3.1 >Reporter: Thomas Recloux >Assignee: Stephane Nicoll > Fix For: 2.3.2 > > Attachments: MEAR-86-maven-ear-plugin-with_tests.patch, > MEAR-86-maven-ear-plugin.patch > > > Before this issue resolution http://jira.codehaus.org/browse/MNG-826 , all > jar dependencies were added into the application.xml. After the resolution, > it was not added and a property was added on the javaModule element in order > to add it into the application.xml. > With a big ear project with a lot of direct or transitive dependencies, it is > becoming really long and a source of errors when a transitive dependency is > changing. > My application server (JBoss 4.0.5GA) needs to add the jar modules in the > application.xml. > The default behaviour should not be changed, I added a property which > includes all jar dependencies in the application.xml. If the property is not > set, nothing changes. > The patch was built against the ear plugin's trunk, it includes a test > (project 43). -- 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: (MEAR-86) Add a property to automatically add jars dependencies into application.xml (TEST AND PATCH ATTACHED).
[ http://jira.codehaus.org/browse/MEAR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Recloux updated MEAR-86: --- Attachment: jar-sample-three-with-deps-1.0.jar A Jar added to the test repo and userd by the new test. Path : src/test/resources/m2repo/eartest/jar-sample-three-with-deps/1.0/jar-sample-three-with-deps-1.0.jar > Add a property to automatically add jars dependencies into application.xml > (TEST AND PATCH ATTACHED). > - > > Key: MEAR-86 > URL: http://jira.codehaus.org/browse/MEAR-86 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.3.1 >Reporter: Thomas Recloux >Assignee: Stephane Nicoll > Fix For: 2.3.2 > > Attachments: jar-sample-three-with-deps-1.0.jar, > MEAR-86-maven-ear-plugin-with_tests.patch, MEAR-86-maven-ear-plugin.patch > > > Before this issue resolution http://jira.codehaus.org/browse/MNG-826 , all > jar dependencies were added into the application.xml. After the resolution, > it was not added and a property was added on the javaModule element in order > to add it into the application.xml. > With a big ear project with a lot of direct or transitive dependencies, it is > becoming really long and a source of errors when a transitive dependency is > changing. > My application server (JBoss 4.0.5GA) needs to add the jar modules in the > application.xml. > The default behaviour should not be changed, I added a property which > includes all jar dependencies in the application.xml. If the property is not > set, nothing changes. > The patch was built against the ear plugin's trunk, it includes a test > (project 43). -- 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: (MASSEMBLY-318) Example to attach assembly to package incorrect
Example to attach assembly to package incorrect
---
Key: MASSEMBLY-318
URL: http://jira.codehaus.org/browse/MASSEMBLY-318
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-2
Reporter: Michael Mattox
The website page:
http://maven.apache.org/plugins/maven-assembly-plugin/usage.html#Resources
lists the way to attach assembly to the package phase:
{code:xml}
[...]
[...]
maven-assembly-plugin
jar-with-dependencies
make-assembly
package
attached
[...]
{code}
This doesn't work for me and I believe it may be incorrect. What I have to do
is put the configuration INSIDE the execution:
{code:xml}
maven-assembly-plugin
make-assembly
package
attached
src/main/assembly/bin.xml
creation.CreationGeneriqueMain
true
{code}
--
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-37) eclipse:eclipse should execute in a later phase than "generate-sources"
[
http://jira.codehaus.org/browse/MECLIPSE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132054#action_132054
]
Benjamin Bentmann commented on MECLIPSE-37:
---
bq. Currently I think only a new mojo can do the trick since the @execute phase
is not runtime configurable.
+1, there should be a simple mojo ({{eclipse:eclipse}}) that is always capable
of generating the project metadata regardless or compilation errors.
> eclipse:eclipse should execute in a later phase than "generate-sources"
> ---
>
> Key: MECLIPSE-37
> URL: http://jira.codehaus.org/browse/MECLIPSE-37
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
>Affects Versions: 2.0
>Reporter: Mark Donszelmann
>Assignee: fabrizio giustina
>
> the eclipse:eclipse goal should run in a later phase than it currently does
> (generate-sources)
> as user defined plugins may add to the compileSourceRoots and
> testCompileSourceRoots.
> If it runs later, added paths will be written correctly to the .classpath.
> Suggested phase is "test"
--
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-409) Build path omits generated test resources
[ http://jira.codehaus.org/browse/MECLIPSE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132055#action_132055 ] Benjamin Bentmann commented on MECLIPSE-409: -1 on the proposed change due to the [reasons described by Kenney|http://jira.codehaus.org/browse/MECLIPSE-37?focusedCommentId=58060#action_58060]. > Build path omits generated test resources > - > > Key: MECLIPSE-409 > URL: http://jira.codehaus.org/browse/MECLIPSE-409 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path >Affects Versions: 2.5 >Reporter: Mark Hobson > Attachments: MECLIPSE-409.patch > > > eclipse:eclipse only executes up to the generate-resources phase, hence any > generated test resources are not included in the build path. This means that > tests that rely on these generated test resources will fail in the IDE. -- 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-37) eclipse:eclipse should execute in a later phase than "generate-sources"
[
http://jira.codehaus.org/browse/MECLIPSE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132056#action_132056
]
Arnaud Heritier commented on MECLIPSE-37:
-
I think we'll create a custom lifecycle for the eclipse plugin with following
phases :
{code:xml}
validate
initialize
generate-sources
process-sources
generate-resources
process-resources
generate-test-sources
process-test-sources
generate-test-resources
process-test-resources
pre-integration-test
post-integration-test
{code}
WDYT ?
> eclipse:eclipse should execute in a later phase than "generate-sources"
> ---
>
> Key: MECLIPSE-37
> URL: http://jira.codehaus.org/browse/MECLIPSE-37
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
>Affects Versions: 2.0
>Reporter: Mark Donszelmann
>Assignee: fabrizio giustina
>
> the eclipse:eclipse goal should run in a later phase than it currently does
> (generate-sources)
> as user defined plugins may add to the compileSourceRoots and
> testCompileSourceRoots.
> If it runs later, added paths will be written correctly to the .classpath.
> Suggested phase is "test"
--
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: (MCHANGES-108) Allow to configure changes-report mojo from properties
Allow to configure changes-report mojo from properties
--
Key: MCHANGES-108
URL: http://jira.codehaus.org/browse/MCHANGES-108
Project: Maven 2.x Changes Plugin
Issue Type: Improvement
Components: changes-report
Affects Versions: 2.0
Reporter: Benjamin Bentmann
Priority: Minor
In lack of a {{/}} section in the POM, one cannot
configure things like {{issueLinkTemplate}} in a central place but has to do it
over and over again in each project. If the plugin would support properties,
one could simply put
{code:xml}
yadayada
{code}
into the corporate parent POM and is done.
--
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: (MCHANGES-108) Allow to configure changes-report mojo from properties
[
http://jira.codehaus.org/browse/MCHANGES-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MCHANGES-108.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.1
Done in [r650917|http://svn.apache.org/viewvc?view=rev&revision=650917].
> Allow to configure changes-report mojo from properties
> --
>
> Key: MCHANGES-108
> URL: http://jira.codehaus.org/browse/MCHANGES-108
> Project: Maven 2.x Changes Plugin
> Issue Type: Improvement
> Components: changes-report
>Affects Versions: 2.0
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 2.1
>
>
> In lack of a {{/}} section in the POM, one
> cannot configure things like {{issueLinkTemplate}} in a central place but has
> to do it over and over again in each project. If the plugin would support
> properties, one could simply put
> {code:xml}
>
> yadayada
>
> {code}
> into the corporate parent POM and is done.
--
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-37) eclipse:eclipse should execute in a later phase than "generate-sources"
[
http://jira.codehaus.org/browse/MECLIPSE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132060#action_132060
]
Benjamin Bentmann commented on MECLIPSE-37:
---
bq. I think we'll create a custom lifecycle for the eclipse plugin with
following phases :
Hm, never thought about this, looks like a great idea! Just two questions:
Do we really need the {{process-*}} phases? For instance, {{process-resources}}
is usually used to copy the files over to "target/classes", it doesn't create
new source folders, does it? Especially if one has many resources (think about
the core-it's to name just one example) excluding this phase would safe further
time.
Likewise, is including {{*-integration-test}} sensible? For instance, many of
the Maven plugins use {{pre-integration-test}} to install the JAR to a test
repo or - even more time consuming - to create a staging repo.
Hence, maybe just:
{code:xml}
validate
initialize
generate-sources
generate-resources
generate-test-sources
generate-test-resources
{code}
> eclipse:eclipse should execute in a later phase than "generate-sources"
> ---
>
> Key: MECLIPSE-37
> URL: http://jira.codehaus.org/browse/MECLIPSE-37
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
>Affects Versions: 2.0
>Reporter: Mark Donszelmann
>Assignee: fabrizio giustina
>
> the eclipse:eclipse goal should run in a later phase than it currently does
> (generate-sources)
> as user defined plugins may add to the compileSourceRoots and
> testCompileSourceRoots.
> If it runs later, added paths will be written correctly to the .classpath.
> Suggested phase is "test"
--
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: (MCHANGES-109) Fix output directory for images of changes-report
Fix output directory for images of changes-report
-
Key: MCHANGES-109
URL: http://jira.codehaus.org/browse/MCHANGES-109
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: changes-report
Affects Versions: 2.0
Reporter: Benjamin Bentmann
Priority: Minor
The {{changes-report}} mojo suffers from [Common Bug
#4|http://www.nabble.com/Re%3A-Common-Bugs-p15246107s177.html]. More precisly,
the images are not exported to the right directory if a multilingual site is
generated.
--
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: (MCHANGES-109) Fix output directory for images of changes-report
[
http://jira.codehaus.org/browse/MCHANGES-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MCHANGES-109.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.1
Fixed in [r650936|http://svn.apache.org/viewvc?view=rev&revision=650936].
> Fix output directory for images of changes-report
> -
>
> Key: MCHANGES-109
> URL: http://jira.codehaus.org/browse/MCHANGES-109
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: changes-report
>Affects Versions: 2.0
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 2.1
>
>
> The {{changes-report}} mojo suffers from [Common Bug
> #4|http://www.nabble.com/Re%3A-Common-Bugs-p15246107s177.html]. More
> precisly, the images are not exported to the right directory if a
> multilingual site is generated.
--
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: (MCHANGES-71) need add template encoding to announcement-generate
[ http://jira.codehaus.org/browse/MCHANGES-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132062#action_132062 ] Benjamin Bentmann commented on MCHANGES-71: --- The default values for these new parameters should follow our proposal about [Source File Encoding|http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding]. > need add template encoding to announcement-generate > --- > > Key: MCHANGES-71 > URL: http://jira.codehaus.org/browse/MCHANGES-71 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Reporter: Yao Yong > > I need to generate a Chinese announcement, would you please add the following > velocity property into parameters > input.encoding > output.encoding -- 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: (MCHANGES-110) No issue links generated if ${project.issueManagement.url} empty but issueLinkTemplate provided
No issue links generated if ${project.issueManagement.url} empty but
issueLinkTemplate provided
---
Key: MCHANGES-110
URL: http://jira.codehaus.org/browse/MCHANGES-110
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: changes-report
Affects Versions: 2.0
Reporter: Benjamin Bentmann
Priority: Minor
The following configuration
{code:xml}
org.apache.maven.plugins
maven-changes-plugin
2.0
http://mycompany.org/mantis//view.php?id=%ISSUE%
{code}
will needlessly cause
{noformat}
[WARNING] No Issue Management/URL defined in pom.xml. Links to your issues
will not work correctly.
{noformat}
in case the POM does not define {{}}.
--
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-37) eclipse:eclipse should execute in a later phase than "generate-sources"
[ http://jira.codehaus.org/browse/MECLIPSE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132063#action_132063 ] Arnaud Heritier commented on MECLIPSE-37: - I agree. I proposed this quickly. I don't think we need process-* and *-integration-test phases. > eclipse:eclipse should execute in a later phase than "generate-sources" > --- > > Key: MECLIPSE-37 > URL: http://jira.codehaus.org/browse/MECLIPSE-37 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path >Affects Versions: 2.0 >Reporter: Mark Donszelmann >Assignee: fabrizio giustina > > the eclipse:eclipse goal should run in a later phase than it currently does > (generate-sources) > as user defined plugins may add to the compileSourceRoots and > testCompileSourceRoots. > If it runs later, added paths will be written correctly to the .classpath. > Suggested phase is "test" -- 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: (MASSEMBLY-319) Cannot bind to lifecycle with multiple modules
Cannot bind to lifecycle with multiple modules
--
Key: MASSEMBLY-319
URL: http://jira.codehaus.org/browse/MASSEMBLY-319
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-2
Reporter: Thomas Diesler
Executing
> mvn package
using this plugin config
maven-assembly-plugin
deploy-artifacts
true
false
src/main/scripts/assembly-deploy-artifacts.xml
build-deploy-artifacts
package
directory-inline
with a descriptor using module sets
org.jboss.ws:jbossws-cxf-client
org.jboss.ws:jbossws-cxf-server
lib
${module.artifactId}.${module.extension}
false
${module.artifactId}.${module.extension}
true
*:cxf-*
*:geronimo-javamail*
*:geronimo-ws-metadata*
*:jaxb-api:jar
*:jaxb-impl:jar
*:jaxb-xjc:jar
*:jaxrpc-api:jar
*:jaxws-api:jar
*:jbossws-common:jar
*:jbossws-framework:jar
*:jbossws-spi:jar
*:jbossws-jboss42:jar
*:neethi:jar
*:saaj-api:jar
*:saaj-impl:jar
*:spring-beans:jar
*:spring-context:jar
*:spring-core:jar
*:stax-api:jar
*:wsdl4j:jar
*:xml-resolver:jar
*:XmlSchema:jar
wstx.jar
true
*:wstx-asl:jar
org.jboss.ws:jbossws-cxf-management
lib
${module.artifactId}.${module.extension}
false
false
I get
[INFO] Executed tasks
[INFO] [source:jar {execution: attach-sources}]
[INFO] [assembly:directory-inline {execution: build-deploy-artifacts}]
[INFO] Reading assembly descriptor:
src/main/scripts/assembly-deploy-artifacts.xml
[INFO] Processing DependencySet (output=bin)
[WARNING] Cannot include project artifact:
org.jboss.ws:jbossws-cxf:pom:3.0.2-SNAPSHOT; it doesn't have an associated file
or directory.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error creating assembly: Artifact:
org.jboss.ws:jbossws-cxf-server:jar:3.0.2-SNAPSHOT (included by module) does
not have an artifact with a file. Please ensure the package phase is run before
the assembly is generated.
It seems that package was not executed in module
'org.jboss.ws:jbossws-cxf-server'
--
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-3543) readProjectWithDependencies take very long time for some projects
readProjectWithDependencies take very long time for some projects - Key: MNG-3543 URL: http://jira.codehaus.org/browse/MNG-3543 Project: Maven 2 Issue Type: Bug Components: Performance Affects Versions: 2.1 Reporter: Igor Fedorenko Invoking readProjectWithDependencies for all modules takes very long time for some projects. For example, for servicemix-3.2.1 it takes about ~300 seconds in online mode and ~90 seconds. I ran the code under profiler, and it seems that in online mode this project is hit by MNG-3531. Both in online and offline mode, however, significant time is spent in DefaultBuildExtensionScanner.scanInternal(File, MavenExecutionRequest, List, List, boolean), so I wonder if there is a way to cache extensions somehow. -- 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: (MCHANGES-110) No issue links generated if ${project.issueManagement.url} empty but issueLinkTemplate provided
[
http://jira.codehaus.org/browse/MCHANGES-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MCHANGES-110.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.1
Fixed in [r650961|http://svn.apache.org/viewvc?view=rev&revision=650961].
> No issue links generated if ${project.issueManagement.url} empty but
> issueLinkTemplate provided
> ---
>
> Key: MCHANGES-110
> URL: http://jira.codehaus.org/browse/MCHANGES-110
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: changes-report
>Affects Versions: 2.0
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 2.1
>
>
> The following configuration
> {code:xml}
>
> org.apache.maven.plugins
> maven-changes-plugin
> 2.0
>
>
> http://mycompany.org/mantis//view.php?id=%ISSUE%
>
>
> {code}
> will needlessly cause
> {noformat}
> [WARNING] No Issue Management/URL defined in pom.xml. Links to your issues
> will not work correctly.
> {noformat}
> in case the POM does not define {{}}.
--
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-2032) Upload new version of LogFacade to m2 repo
Upload new version of LogFacade to m2 repo -- Key: MAVENUPLOAD-2032 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2032 Project: maven-upload-requests Issue Type: Wish Reporter: Tony Dalbrekt New version of LogFacade released. PLZ upload. WHOIS to prove my domain ownership. You will see the email address here is the same as the owner of the google code project logfacade. http://www.whois.org/whois_new.cgi?d=jworx&tld=com -- 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-2033) Upload new version of LogFacade jar to m2 repo
Upload new version of LogFacade jar to m2 repo -- Key: MAVENUPLOAD-2033 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2033 Project: maven-upload-requests Issue Type: Wish Reporter: Tony Dalbrekt New version of LogFacade released. PLZ upload. WHOIS to prove my domain ownership. You will see the email address here is the same as the owner of the google code project logfacade. http://www.whois.org/whois_new.cgi?d=jworx&tld=com -- 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-3544) Beautify debug output for mojo parameters of type array
Beautify debug output for mojo parameters of type array
---
Key: MNG-3544
URL: http://jira.codehaus.org/browse/MNG-3544
Project: Maven 2
Issue Type: Improvement
Components: Logging
Affects Versions: 2.0.9
Reporter: Benjamin Bentmann
Priority: Trivial
Attachments: debug-mojo-array-params.patch
Currently:
{noformat}
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-jar-plugin:2.2:jar' -->
[DEBUG] (f) excludes = [Ljava.lang.String;@c3c315
[DEBUG] -- end configuration --
{noformat}
i.e. arrays won't show up nicely.
The attached patch returns a string similar to the result of
{code:java}
Arrays.asList( (Object[]) value ).toString()
{code}
but uses reflection to handle arrays of primitives 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: (MPA-112) Removed MAVENREPOMAINT
Removed MAVENREPOMAINT -- Key: MPA-112 URL: http://jira.codehaus.org/browse/MPA-112 Project: Maven Project Administration Issue Type: Bug Affects Versions: 2007-q4 Reporter: Vincent Siveton Priority: Minor Seems that http://jira.codehaus.org/browse/MAVENREPOMAINT is unused -- 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-3541) Better JIRA organization
[ http://jira.codehaus.org/browse/MNG-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MNG-3541. Assignee: Vincent Siveton Resolution: Won't Fix IMHO [1] is enough clear for an user point of view. MAVENREPOMAINT needs maybe to be removed [1] http://maven.apache.org/issue-tracking.html > Better JIRA organization > > > Key: MNG-3541 > URL: http://jira.codehaus.org/browse/MNG-3541 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories, Errors, Sites & Reporting >Reporter: Diego Plentz >Assignee: Vincent Siveton >Priority: Critical > > Looking at codehaus jira, its a pain to find where you must open an issue. > Look. > If its a problem in repository, I must open where? > - http://jira.codehaus.org/browse/MNG > Artifacts and Repositories > - http://jira.codehaus.org/browse/MAVENREPOMAINT > - http://jira.codehaus.org/browse/MEV > - http://jira.codehaus.org/browse/MPA > repository management > Or, if its a problem with the site? > - http://jira.codehaus.org/browse/MNG > Sites & Reporting > - http://jira.codehaus.org/browse/MNGSITE > - http://jira.codehaus.org/browse/MPA > sites > Cutting off some projects is a good start. -- 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
