[jira] Commented: (MRELEASE-322) Unable to set the working directory for projects where the master pom isn't at the root of the project
[
http://jira.codehaus.org/browse/MRELEASE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125568
]
Pavel Muller commented on MRELEASE-322:
---
I've got the same problem. Real blocker for our project.
> Unable to set the working directory for projects where the master pom isn't
> at the root of the project
> --
>
> Key: MRELEASE-322
> URL: http://jira.codehaus.org/browse/MRELEASE-322
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
>Affects Versions: 2.0-beta-7
>Reporter: Christian Nelson
>Priority: Blocker
>
> Branches and Tags are created from the current working directory, which isn't
> always correct and there isn't a way to override the working directory.
> For example, we have the following directory structure:
> ${root}/master/pom.xml - The modules section include relative paths to
> modules a, b, and c.
> ${root}/module-a/pom.xml
> ${root}/module-b/pom.xml
> ${root}/module-c/pom.xml
> All subversion copies (via branch or prepare) originate from ${root}/master.
> As a result, they are incomplete; we really want to create copies from
> ${root} not ${root}/master. Here's the subversion command that I think is
> the problem:
> {noformat}
> [INFO] Working directory: C:\devsys\repos\trunk\master
> [INFO] Branching release with the label release-1.0...
> [INFO] Executing: svn --non-interactive copy --file
> C:\Users\cnelson\AppData\Local\Temp\maven-scm-1179760787.commit .
> http://hostname/svn/dev/branches/release-1.0
> {noformat}
> The period after the filename is what's indicating to subversion to create
> the copy from master instead of ${root}. Note: the working directory is
> derived from the basedir and I couldn't find a way to override the basedir.
> While not having the master pom at the root of the project may be a little
> uncommon, it doesn't seem unreasonable. Can we add a configuration option to
> handle these cases?
--
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-143) Add the possibility to generate files at project's root
Add the possibility to generate files at project's root --- Key: ARCHETYPE-143 URL: http://jira.codehaus.org/browse/ARCHETYPE-143 Project: Maven Archetype Issue Type: Improvement Affects Versions: 2.0-alpha-2 Reporter: Dominique Jean-Prost Priority: Minor Actually, I can't specify with fileset to generate files next to pom.xml, I mean, not in src dir. I tried the following, but it doesn't work / ChangeMyName.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-688) Replace plexus-runtime with standalone jetty bundle
[ http://jira.codehaus.org/browse/MRM-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125569 ] Maria Odea Ching commented on MRM-688: -- Okey dokey, thanks Brett! :-) > Replace plexus-runtime with standalone jetty bundle > --- > > Key: MRM-688 > URL: http://jira.codehaus.org/browse/MRM-688 > Project: Archiva > Issue Type: Task > Components: build >Affects Versions: 1.0, 1.0.1 >Reporter: Maria Odea Ching >Assignee: Maria Odea Ching > Fix For: 1.1 > > > http://www.nabble.com/Re%3A-Archiva-1.1-Roadmap-p15331690.html -- 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-326) Doens't resolve multiproject dependencies properly
Doens't resolve multiproject dependencies properly --- Key: MRELEASE-326 URL: http://jira.codehaus.org/browse/MRELEASE-326 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-7 Environment: Windows, JDK 1.6, Maven 2.08 Reporter: Kuno Baeriswyl Attachments: Stacktrace_release-plugin.txt I'd try to make a release:prepare from a multiproject: A (Multiproject POM) B (Core Interfaces) C (Component) D (Core Impl) E (Standalone Client) F (EJB) G (Client) A is the parent project and contains the other project from B to G. Following dependencies are defined : G -> F -> D -> B -> A However, when it comes to build the Artifact G, the release plugin aborts, because of missing Artifact F. But it's part of the Multiproject and was just build before. The release plugin checks the remote repository for an existing version. Which is non-sense, since I'm actually try to buld it right now... Since the release plugin has already changed the pom from Snapshot to stable version labels. I can now do "mvn install" and the missing Artefact will be installed. And the second run of mvn release:prepare will succeed! Though, I don't like this workaround and hope this can be fixed. Thanks Kuno -- 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: (ARCHETYPE-143) Add the possibility to generate files at project's root
[ http://jira.codehaus.org/browse/ARCHETYPE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125572 ] Dominique Jean-Prost commented on ARCHETYPE-143: Well, I tried what you said. The correct syntax is . I got my solution Maybe you can add this in documentation, so that dummies like me could find it ;-) Thank you. > Add the possibility to generate files at project's root > --- > > Key: ARCHETYPE-143 > URL: http://jira.codehaus.org/browse/ARCHETYPE-143 > Project: Maven Archetype > Issue Type: Improvement >Affects Versions: 2.0-alpha-2 >Reporter: Dominique Jean-Prost >Priority: Minor > > Actually, I can't specify with fileset to generate files next to pom.xml, I > mean, not in src dir. I tried the following, but it doesn't work > > / > > ChangeMyName.xml > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MARTIFACT-4) allow wildcards and versions in In/ExcludesArtifactFilter
[ http://jira.codehaus.org/browse/MARTIFACT-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125576 ] Mark Hobson commented on MARTIFACT-4: - Note that StrictPatternIncludesArtifactFilter and StrictPatternExcludesArtifactFilter in maven-common-artifact-filters supports wildcards and versions. > allow wildcards and versions in In/ExcludesArtifactFilter > - > > Key: MARTIFACT-4 > URL: http://jira.codehaus.org/browse/MARTIFACT-4 > Project: Maven Artifact > Issue Type: Improvement >Reporter: Brett Porter > Fix For: 3.0-alpha-1 > > -- 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-37) 'noSnapshots' rule do not check version of parent
'noSnapshots' rule do not check version of parent - Key: MENFORCER-37 URL: http://jira.codehaus.org/browse/MENFORCER-37 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Components: Standard Rules Affects Versions: 1.0-alpha-3 Reporter: Tomasz Pik Assignee: Brian Fox 'noSnapshots' is passing when parent is defined to be SNAPSHOT, IMHO parent is also a dependency so it should be checked and rule should throw an error if parent is a 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-2123) NullPointerException when a dependency uses version range and another uses an actual version incompatible with that range
[ http://jira.codehaus.org/browse/MNG-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Goldhahn updated MNG-2123: - Attachment: mng2123_versionRangeDependency.tar.bz2 Integration test. The test create two artifacts with a dependency to commons-collection. artifact-fix requires version 3.2 artifact-range requires version (2.0,3.1.99] artifact-combined has a dependency on the artifacts above. In version 2.0.8 the test fails with a NPE > NullPointerException when a dependency uses version range and another uses an > actual version incompatible with that range > - > > Key: MNG-2123 > URL: http://jira.codehaus.org/browse/MNG-2123 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.2, 2.0.3, 2.0.4 >Reporter: Carlos Sanchez >Assignee: Brian Fox > Fix For: 2.0.9 > > Attachments: MNG-2123-maven-artifact.patch, > mng2123_versionRangeDependency.tar.bz2, pom.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Struts 1.2.7 depends on commons-digester 1.6 and jasperreports 1.1.1 in [1.7,) > Build fails with a null pointer exception that is not very explanatory > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Unnamed - test:test:jar:1.0-SNAPSHOT > [INFO]task-segment: [test] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:361) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:222) > at > org.apache.maven.artifact.resolver.ResolutionNode.getDependencyTrail(ResolutionNode.java:115) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:88) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:223) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:211) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:182) > at > org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1117) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:366) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > 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:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > 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.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > > [INFO] Total
[jira] Commented: (DOXIA-217) Make default impl classes
[
http://jira.codehaus.org/browse/DOXIA-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125597
]
Vincent Siveton commented on DOXIA-217:
---
To be more clear, a lot of internal classes are publics and should be change to
default, i.e.
public class BulletedListBlock{}
class BulletedListBlock{}
> Make default impl classes
> -
>
> Key: DOXIA-217
> URL: http://jira.codehaus.org/browse/DOXIA-217
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Module - Confluence, Module - Rtf, Module - Twiki
>Affects Versions: 1.0-alpha-10
>Reporter: Vincent Siveton
> Fix For: 1.0-beta-1
>
>
> doxia-module-rtf
> doxia-module-confluence
> doxia-module-twiki
--
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: (MNG-2123) NullPointerException when a dependency uses version range and another uses an actual version incompatible with that range
[ http://jira.codehaus.org/browse/MNG-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125590 ] mgoldhahn edited comment on MNG-2123 at 2/29/08 7:20 AM: --- Integration test. The test creates two artifacts with a dependency to commons-collection. artifact-fix requires version 3.2 artifact-range requires version (2.0,3.1.99] artifact-combined has a dependency on the artifacts above. In version 2.0.8 the test fails with a NPE was (Author: mgoldhahn): Integration test. The test create two artifacts with a dependency to commons-collection. artifact-fix requires version 3.2 artifact-range requires version (2.0,3.1.99] artifact-combined has a dependency on the artifacts above. In version 2.0.8 the test fails with a NPE > NullPointerException when a dependency uses version range and another uses an > actual version incompatible with that range > - > > Key: MNG-2123 > URL: http://jira.codehaus.org/browse/MNG-2123 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.2, 2.0.3, 2.0.4 >Reporter: Carlos Sanchez >Assignee: Brian Fox > Fix For: 2.0.9 > > Attachments: MNG-2123-maven-artifact.patch, > mng2123_versionRangeDependency.tar.bz2, pom.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Struts 1.2.7 depends on commons-digester 1.6 and jasperreports 1.1.1 in [1.7,) > Build fails with a null pointer exception that is not very explanatory > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Unnamed - test:test:jar:1.0-SNAPSHOT > [INFO]task-segment: [test] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:361) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:222) > at > org.apache.maven.artifact.resolver.ResolutionNode.getDependencyTrail(ResolutionNode.java:115) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:88) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:223) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:211) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:182) > at > org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1117) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:366) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > 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:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > 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.classworlds.Launcher.launchEnhanced(Launcher.java:315) >
[jira] Created: (MDEP-148) Use Set.contains() rather than manual iteration to check for containment of class in artifact
Use Set.contains() rather than manual iteration to check for containment of
class in artifact
-
Key: MDEP-148
URL: http://jira.codehaus.org/browse/MDEP-148
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Components: analyze
Affects Versions: 2.0
Reporter: Benjamin Bentmann
Assignee: Brian Fox
Priority: Trivial
Attachments: set-containment-check.patch
The usual {{java.util.Set}} implementations use data structures that are
optimized for containment checks.
--
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-149) Field accesses and method invocations cause bogus dependencies
Field accesses and method invocations cause bogus dependencies
--
Key: MDEP-149
URL: http://jira.codehaus.org/browse/MDEP-149
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: analyze
Affects Versions: 2.0
Reporter: Benjamin Bentmann
Assignee: Brian Fox
Priority: Trivial
Attachments: bogus-dependencies.patch
When hunting down some "Used undeclared dependencies" warnings, I found the
plugin lying. For example, the line
{code:java}
java.lang.Object var = bean.field;
{code}
does not impose a direct dependency on the field's type, whatever it may be.
Likewise, the line
{code:java}
bean.method(null);
{code}
does not directly depend on the method's return type nor parameter types.
Unless I explicitly code a reference to a type by means of variable
declarations, type checks/casts etc., there is no need to declare dependencies
that are already brought in via transitivity, that's what Maven was invented
for, isn't is ;-)
--
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: (MSITE-306) [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
[ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. Key: MSITE-306 URL: http://jira.codehaus.org/browse/MSITE-306 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-6 Reporter: Alexandre Navarro Priority: Minor I always get the error below: [INFO] Velocimacro : initialization starting. [INFO] Velocimacro : adding VMs from VM library template : VM_global_library.vm [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. [INFO] Velocimacro : error using VM library template VM_global_library.vm : org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource 'VM_global_library.vm' [INFO] Velocimacro : VM library template macro registration complete. this does not seem to affect my site generation. I get rid of this because my build server (Luntbuild/Quickbuild) thinks there is an error. thanks, Alexandre PS : The same bug was reported before http://jira.codehaus.org/browse/MSITE-286 normally it mght be fixed in 2.0-beta-6 but it not true (not for me). -- 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-3282) maven only tries the first repo that contains an artifact
[ http://jira.codehaus.org/browse/MNG-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125615 ] Ken in nashua commented on MNG-3282: Happening again out of the blue... was building fine yesterday. No changes to this machine or source tree or repo. [INFO] snapshot com.javaforge.tapestry:tapestry-javaforge:1.0.0-SNAPSHOT: checking for updates from apache.snapshots [INFO] snapshot com.javaforge.tapestry:tapestry-javaforge:1.0.0-SNAPSHOT: checking for updates from howardlewisship.com [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: com.javaforge.tapestry:tapestry-spring:jar:1.0.0 Reason: Cannot find parent: com.javaforge.tapestry:tapestry-javaforge for project: com.javafor ge.tapestry:tapestry-spring:jar:1.0.0 for project com.javaforge.tapestry:tapestry-spring:jar:1 .0.0 [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 2 minutes 9 seconds [INFO] Finished at: Fri Feb 29 09:35:15 EST 2008 [INFO] Final Memory: 16M/49M [INFO] C:\Prototype\Mavenized\Product\trails\trunk\trails>mvn clean install > maven only tries the first repo that contains an artifact > - > > Key: MNG-3282 > URL: http://jira.codehaus.org/browse/MNG-3282 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.7 >Reporter: Brian Fox >Assignee: Brian Fox > > If there are multiple repos that contain an artifact, the metadata in the > local repo for all of them will contain this fact. Maven only tries the first > one to get the artifact and doesn't try the others. It should try any other > repos known to contain the artifact if the previous ones fail (if they are > down for example). -- 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-149) Field accesses and method invocations cause bogus dependencies
[
http://jira.codehaus.org/browse/MDEP-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MDEP-149:
---
Attachment: MDEP-149.zip
Here are some (pathological) demo projects if you want to try this out. Run
"mvn install" on api and impl, then "mvn dependency:analyze" on impl-client.
Without the patch, the plugin warns that impl-client uses api although there is
not a single souce code line directly referencing any type from api.
> Field accesses and method invocations cause bogus dependencies
> --
>
> Key: MDEP-149
> URL: http://jira.codehaus.org/browse/MDEP-149
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 2.0
>Reporter: Benjamin Bentmann
>Assignee: Brian Fox
>Priority: Trivial
> Attachments: bogus-dependencies.patch, MDEP-149.zip
>
>
> When hunting down some "Used undeclared dependencies" warnings, I found the
> plugin lying. For example, the line
> {code:java}
> java.lang.Object var = bean.field;
> {code}
> does not impose a direct dependency on the field's type, whatever it may be.
> Likewise, the line
> {code:java}
> bean.method(null);
> {code}
> does not directly depend on the method's return type nor parameter types.
> Unless I explicitly code a reference to a type by means of variable
> declarations, type checks/casts etc., there is no need to declare
> dependencies that are already brought in via transitivity, that's what Maven
> was invented for, isn't is ;-)
--
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-38) Enforcer rules for AlwaysPass and AlwaysFail
Enforcer rules for AlwaysPass and AlwaysFail Key: MENFORCER-38 URL: http://jira.codehaus.org/browse/MENFORCER-38 Project: Maven 2.x Enforcer Plugin Issue Type: Improvement Components: Standard Rules Reporter: Ben Lidgey Assignee: Brian Fox Attachments: MavenEnforcerAlwaysRules.zip As discussed on email, here is my first attempt at submitting some code! It implements two rules: one always passes and the other always fails. They are useful for checking the Enforcer rules config and possible failing the build if a certain profile is used by setting the AlwaysFail rule in that profile. -- 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: (WAGON-96) WebDAV deploy fails with - Failed to create destination WebDAV collection
[ http://jira.codehaus.org/browse/WAGON-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125639 ] Richard Taylor commented on WAGON-96: - We are getting this same error randomly while trying to deploy to Artifactory 1.2.5u1. Our environment is Windows XP, Maven 2.0.7, JDK 1.5.0 [artifact:install-provider] Installing provider: org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-2:runtime [artifact:install-provider] WAGON_VERSION: 1.0-beta-2 [artifact:deploy] Deploying to dav:http://dev-maven1.foo.com:8081/artifactory/[EMAIL PROTECTED] [artifact:deploy] [INFO] Retrieving previous build number from com.foo.snapshots [artifact:deploy] Feb 28, 2008 8:51:08 PM org.apache.commons.httpclient.HttpMethodBase processRequest [artifact:deploy] INFO: Recoverable exception caught when processing request [artifact:deploy] Feb 28, 2008 8:51:08 PM org.apache.commons.httpclient.HttpMethodBase processRequest [artifact:deploy] WARNING: Recoverable exception caught but MethodRetryHandler.retryMethod() returned false, rethrowing exception [artifact:deploy] An error has occurred while processing the Maven artifact tasks. [artifact:deploy] Diagnosis: [artifact:deploy] [artifact:deploy] Error deploying artifact 'com.foo.vhi:wcp:jar': Error deploying artifact: Failed to create destination WebDAV collection (directory): /artifactory/[EMAIL PROTECTED]/com/foo/vhi/wcp/6.6.0-SNAPSHOT [artifact:deploy] org.apache.commons.httpclient.HttpRecoverableException: Error in parsing the status line from the response: unable to find line starting with "HTTP" [artifact:deploy] BUILD FAILED d:\vhi\6.6\dev\java\build.xml:77: Error deploying artifact 'com.foo.vhi:wcp:jar': Error deploying artifact: Failed to create destination WebDAV collection (directory): /artifactory/[EMAIL PROTECTED]/com/foo/vhi/wcp/6.6.0-SNAPSHOT > WebDAV deploy fails with - Failed to create destination WebDAV collection > - > > Key: WAGON-96 > URL: http://jira.codehaus.org/browse/WAGON-96 > Project: wagon > Issue Type: Bug > Components: wagon-ssh-external >Affects Versions: 1.0-beta-2 > Environment: Linux > Maven 2.0.8 >Reporter: Erik R. Jensen > Attachments: output.txt > > > I'm trying to deploy projects over WebDAV and receive an error when I try to > deploy. The error is random and doesn't happen in the same place every time. > I don't believe the remote WebDav server is causing the issue as I see no > errors on the remote end and occasionally the wagon-webdav plugin works > without errors. > The output is attached to this bug. -- 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: (MJAVADOC-180) aggregation doesn't work for test-javadoc goal
aggregation doesn't work for test-javadoc goal -- Key: MJAVADOC-180 URL: http://jira.codehaus.org/browse/MJAVADOC-180 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.3, 2.4 Environment: maven-javadoc-plugin 2.3 final maven-javadoc-plugin 2.4-SNAPSHOT r632385 Maven version: 2.0.8 Java version: 1.5.0_13 OS name: "mac os x" version: "10.5.2" arch: "i386" Family: "unix" Reporter: Elliot Metsger When executing 'javadoc:test-javadoc' from a parent project in a multi-module build, it fails complaining of missing dependencies: mvn clean -X -e javadoc:test-javadoc [DEBUG] embargo-api: using locally installed snapshot [DEBUG] dspace-api: resolved to version 1.4.2e-20080118.034638-23 from repository msel.maven.snapshots [DEBUG] Compiled artifacts for edu.jhu.library.embargo:embargo-dspace:1.0.0-SNAPSHOT /Users/esm/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar /Users/esm/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar /Users/esm/.m2/repository/xerces/xercesImpl/2.0.2/xercesImpl-2.0.2.jar /Users/esm/.m2/repository/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.jar /Users/esm/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar /Users/esm/.m2/repository/commons-pool/commons-pool/1.2/commons-pool-1.2.jar /Users/esm/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar /Users/esm/.m2/repository/edu/jhu/library/embargo/embargo-api/1.0.0-SNAPSHOT/embargo-api-1.0.0-SNAPSHOT.jar /Users/esm/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar /Users/esm/.m2/repository/org/dspace/dspace-api/1.4.2e-SNAPSHOT/dspace-api-1.4.2e-SNAPSHOT.jar /Users/esm/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar [DEBUG] "cd /Users/esm/idea/workspace/embargo/target/site/testapidocs && /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc" @options @packages [search path for source files: [/Users/esm/idea/workspace/embargo/embargo-api/src/test/java, /Users/esm/idea/workspace/embargo/embargo-dspace/src/test/java]] [search path for class files: [/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/classes.jar, /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/ui.jar, /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/laf.jar, /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jsse.jar, /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jce.jar, /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/charsets.jar, /System/Library/Java/Extensions/CoreAudio.jar, /System/Library/Java/Extensions/dns_sd.jar, /System/Library/Java/Extensions/j3daudio.jar, /System/Library/Java/Extensions/j3dcore.jar, /System/Library/Java/Extensions/j3dutils.jar, /System/Library/Java/Extensions/jai_codec.jar, /System/Library/Java/Extensions/jai_core.jar, /System/Library/Java/Extensions/mlibwrapper_jai.jar, /System/Library/Java/Extensions/MRJToolkit.jar, /System/Library/Java/Extensions/QTJava.zip, /System/Library/Java/Extensions/vecmath.jar, /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/apple_provider.jar, /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/dnsns.jar, /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/localedata.jar, /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunjce_provider.jar, /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunpkcs11.jar, /Users/esm/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar, /Users/esm/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar, /Users/esm/.m2/repository/xerces/xercesImpl/2.0.2/xercesImpl-2.0.2.jar, /Users/esm/.m2/repository/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.jar, /Users/esm/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar, /Users/esm/.m2/repository/commons-pool/commons-pool/1.2/commons-pool-1.2.jar, /Users/esm/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar, /Users/esm/.m2/repository/edu/jhu/library/embargo/embargo-api/1.0.0-SNAPSHOT/embargo-api-1.0.0-SNAPSHOT.jar, /Users/esm/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar, /Users/esm/.m2/repository/org/dspace/dspace-api/1.4.2e-SNAPSHOT/dspace-api-1.4.2e-SNAPSHOT.jar, /Users/esm/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar]] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error has occurred in Test JavaDocs report generation:Exit code: 1 - /Users/esm/idea/workspace/embargo/embargo-dspace/src/test/java/org/dspace/embargo/AbstractServiceT
[jira] Commented: (MNG-3419) Build continues despite OutOfMemoryError
[ http://jira.codehaus.org/browse/MNG-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125645 ] Kohsuke Kawaguchi commented on MNG-3419: This is actually a bug in javac/apt. They are the ones who are masking an exception in annotation processors, and it won't even return a failure error code. > Build continues despite OutOfMemoryError > > > Key: MNG-3419 > URL: http://jira.codehaus.org/browse/MNG-3419 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0.7 >Reporter: Sanjeeb Sahoo > Fix For: 2.0.9 > > > [I have already sent this question to users forum twice, but no response, so > I am filing this issue] > I am seeing something very strange. We have our own plugin(it's basically an > annotation processor) that gets invoked as part of compile phase. It appears > that the JVM gets OutOfMemoryError when this plugin is executed, yet the > build continues to the next phase instead of aborting. I ran with -X option > and it shows that the plugin is invoked in process. I have looked at our > plugin code and we do not catch Throwable or Error in our code. So, it > appears to be a bug in Maven. Given below is some selected output that I > think should give an idea of what's going on... > [INFO] > > [INFO] Building Web Container for GlassFish > [INFO]task-segment: [install] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > ... > [DEBUG] Configuring mojo > 'com.sun.enterprise:hk2-maven-plugin:0.2-SNAPSHOT:hk2-compile' --> > ... > [DEBUG] (f) fork = false > ... > [INFO] [hk2:hk2-compile] > [DEBUG] Using compiler 'hk2-apt'. > [DEBUG] Source directories: > [/space/ss141213/WS/gf/v3/web/webtier/src/main/java] > [DEBUG] Classpath: [/space/ss141213/WS/gf/v3/web/webtier/target/classes... > [INFO] Compiling 660 source files to > /space/ss141213/WS/gf/v3/web/webtier/target/classes > The system is out of resources. > Consult the following stack trace for details. > java.lang.OutOfMemoryError: Java heap space >at > java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:99) >at > java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:393) >at java.lang.StringBuilder.append(StringBuilder.java:120) >at com.sun.tools.javac.jvm.ClassReader.list(ClassReader.java:1756) >at com.sun.tools.javac.jvm.ClassReader.listAll(ClassReader.java:1882) >at com.sun.tools.javac.jvm.ClassReader.fillIn(ClassReader.java:1901) >at com.sun.tools.javac.jvm.ClassReader.complete(ClassReader.java:1538) >at com.sun.tools.javac.code.Symbol.complete(Symbol.java:355) >at > com.sun.tools.javac.jvm.ClassReader.completeOwners(ClassReader.java:1547) >at com.sun.tools.javac.jvm.ClassReader.complete(ClassReader.java:1534) >at com.sun.tools.javac.code.Symbol.complete(Symbol.java:355) >at > com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:612) >at com.sun.tools.javac.code.Symbol$ClassSymbol.flags(Symbol.java:550) >at > com.sun.tools.javac.code.Types$AsSuperFcn.visitClassType(Types.java:1440) >at com.sun.tools.javac.code.Type$ClassType.accept(Type.java:482) >at com.sun.tools.javac.code.Types$AsSuperFcn.asSuper(Types.java:1417) >at > com.sun.tools.javac.code.Types$AsSuperFcn.visitClassType(Types.java:1434) >at com.sun.tools.javac.code.Type$ClassType.accept(Type.java:482) >at com.sun.tools.javac.code.Types$AsSuperFcn.asSuper(Types.java:1417) >at com.sun.tools.javac.code.Types.asSuper(Types.java:1407) >at > com.sun.tools.javac.code.Types$IsSubTypeFcn.visitClassType(Types.java:429) >at com.sun.tools.javac.code.Type$ClassType.accept(Type.java:482) >at > com.sun.tools.javac.code.Types$IsSubTypeFcn.isSubType(Types.java:353) >at com.sun.tools.javac.code.Types.isSubType(Types.java:331) >at com.sun.tools.javac.code.Types.isSubTypeUnchecked(Types.java:311) >at com.sun.tools.javac.code.Types.isConvertible(Types.java:278) >at com.sun.tools.javac.code.Types.isAssignable(Types.java:1630) >at com.sun.tools.javac.comp.Check.checkType(Check.java:325) >at com.sun.tools.javac.comp.Annotate.enterAnnotation(Annotate.java:122) >at > com.sun.tools.javac.comp.MemberEnter.enterAnnotations(MemberEnter.java:705) > Note: Some input files use or override a deprecated API. > Note: Recompile with -Xlint:deprecation for details. > Note: Some input files use unchecked or unsafe operations. > Note: Recompile with -Xlint:unchecked for detai
[jira] Commented: (MJAVADOC-180) aggregation doesn't work for test-javadoc goal
[ http://jira.codehaus.org/browse/MJAVADOC-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125649 ] Elliot Metsger commented on MJAVADOC-180: - The solution for the 'javadoc' goal seems to have been added via MJAVADOC-72 in r434560. AbstractJavadocMojo's getClasspath() was modified to obtain the classpaths for aggregated projects. I'd be happy to work on a patch but need a little direction: should getClasspath() be made protected and allow TestJavadocReport to override it and add the test classpaths? > aggregation doesn't work for test-javadoc goal > -- > > Key: MJAVADOC-180 > URL: http://jira.codehaus.org/browse/MJAVADOC-180 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.3, 2.4 > Environment: maven-javadoc-plugin 2.3 final > maven-javadoc-plugin 2.4-SNAPSHOT r632385 > Maven version: 2.0.8 > Java version: 1.5.0_13 > OS name: "mac os x" version: "10.5.2" arch: "i386" Family: "unix" >Reporter: Elliot Metsger > > When executing 'javadoc:test-javadoc' from a parent project in a multi-module > build, it fails complaining of missing dependencies: > mvn clean -X -e javadoc:test-javadoc > > [DEBUG] embargo-api: using locally installed snapshot > [DEBUG] dspace-api: resolved to version 1.4.2e-20080118.034638-23 from > repository msel.maven.snapshots > [DEBUG] Compiled artifacts for > edu.jhu.library.embargo:embargo-dspace:1.0.0-SNAPSHOT > /Users/esm/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar > /Users/esm/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar > /Users/esm/.m2/repository/xerces/xercesImpl/2.0.2/xercesImpl-2.0.2.jar > /Users/esm/.m2/repository/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.jar > /Users/esm/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar > /Users/esm/.m2/repository/commons-pool/commons-pool/1.2/commons-pool-1.2.jar > /Users/esm/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar > /Users/esm/.m2/repository/edu/jhu/library/embargo/embargo-api/1.0.0-SNAPSHOT/embargo-api-1.0.0-SNAPSHOT.jar > /Users/esm/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar > /Users/esm/.m2/repository/org/dspace/dspace-api/1.4.2e-SNAPSHOT/dspace-api-1.4.2e-SNAPSHOT.jar > /Users/esm/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar > > [DEBUG] "cd /Users/esm/idea/workspace/embargo/target/site/testapidocs && > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc" > @options @packages > [search path for source files: > [/Users/esm/idea/workspace/embargo/embargo-api/src/test/java, > /Users/esm/idea/workspace/embargo/embargo-dspace/src/test/java]] > [search path for class files: > [/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/classes.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/ui.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/laf.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jsse.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jce.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/charsets.jar, > /System/Library/Java/Extensions/CoreAudio.jar, > /System/Library/Java/Extensions/dns_sd.jar, > /System/Library/Java/Extensions/j3daudio.jar, > /System/Library/Java/Extensions/j3dcore.jar, > /System/Library/Java/Extensions/j3dutils.jar, > /System/Library/Java/Extensions/jai_codec.jar, > /System/Library/Java/Extensions/jai_core.jar, > /System/Library/Java/Extensions/mlibwrapper_jai.jar, > /System/Library/Java/Extensions/MRJToolkit.jar, > /System/Library/Java/Extensions/QTJava.zip, > /System/Library/Java/Extensions/vecmath.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/apple_provider.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/dnsns.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/localedata.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunjce_provider.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunpkcs11.jar, > /Users/esm/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar, > /Users/esm/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar, > /Users/esm/.m2/repository/xerces/xercesImpl/2.0.2/xercesImpl-2.0.2.jar, > /Users/esm/.m2/repository/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.jar, > /Users/esm/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar, > /Users/esm/.m2/repository/commons-pool/commons-pool/1.2/commons-pool-1.2.jar, > /Users/esm/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar, > /Users/esm/.m2/reposi
[jira] Commented: (MJAVADOC-180) aggregation doesn't work for test-javadoc goal
[ http://jira.codehaus.org/browse/MJAVADOC-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125648 ] Elliot Metsger commented on MJAVADOC-180: - * The compiled artifacts list doesn't include any of the test dependencies * DB Unit is a test dependency. If I make it a compile-time dep, the DB Unit errors go away (but other test deps cannot be found) * I can execute the test-javadoc goal successfully if I run it inside the child module instead of the parent. > aggregation doesn't work for test-javadoc goal > -- > > Key: MJAVADOC-180 > URL: http://jira.codehaus.org/browse/MJAVADOC-180 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.3, 2.4 > Environment: maven-javadoc-plugin 2.3 final > maven-javadoc-plugin 2.4-SNAPSHOT r632385 > Maven version: 2.0.8 > Java version: 1.5.0_13 > OS name: "mac os x" version: "10.5.2" arch: "i386" Family: "unix" >Reporter: Elliot Metsger > > When executing 'javadoc:test-javadoc' from a parent project in a multi-module > build, it fails complaining of missing dependencies: > mvn clean -X -e javadoc:test-javadoc > > [DEBUG] embargo-api: using locally installed snapshot > [DEBUG] dspace-api: resolved to version 1.4.2e-20080118.034638-23 from > repository msel.maven.snapshots > [DEBUG] Compiled artifacts for > edu.jhu.library.embargo:embargo-dspace:1.0.0-SNAPSHOT > /Users/esm/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar > /Users/esm/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar > /Users/esm/.m2/repository/xerces/xercesImpl/2.0.2/xercesImpl-2.0.2.jar > /Users/esm/.m2/repository/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.jar > /Users/esm/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar > /Users/esm/.m2/repository/commons-pool/commons-pool/1.2/commons-pool-1.2.jar > /Users/esm/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar > /Users/esm/.m2/repository/edu/jhu/library/embargo/embargo-api/1.0.0-SNAPSHOT/embargo-api-1.0.0-SNAPSHOT.jar > /Users/esm/.m2/repository/commons-logging/commons-logging/1.1/commons-logging-1.1.jar > /Users/esm/.m2/repository/org/dspace/dspace-api/1.4.2e-SNAPSHOT/dspace-api-1.4.2e-SNAPSHOT.jar > /Users/esm/.m2/repository/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar > > [DEBUG] "cd /Users/esm/idea/workspace/embargo/target/site/testapidocs && > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/javadoc" > @options @packages > [search path for source files: > [/Users/esm/idea/workspace/embargo/embargo-api/src/test/java, > /Users/esm/idea/workspace/embargo/embargo-dspace/src/test/java]] > [search path for class files: > [/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/classes.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/ui.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/laf.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jsse.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jce.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/charsets.jar, > /System/Library/Java/Extensions/CoreAudio.jar, > /System/Library/Java/Extensions/dns_sd.jar, > /System/Library/Java/Extensions/j3daudio.jar, > /System/Library/Java/Extensions/j3dcore.jar, > /System/Library/Java/Extensions/j3dutils.jar, > /System/Library/Java/Extensions/jai_codec.jar, > /System/Library/Java/Extensions/jai_core.jar, > /System/Library/Java/Extensions/mlibwrapper_jai.jar, > /System/Library/Java/Extensions/MRJToolkit.jar, > /System/Library/Java/Extensions/QTJava.zip, > /System/Library/Java/Extensions/vecmath.jar, > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/apple_provider.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/dnsns.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/localedata.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunjce_provider.jar, > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunpkcs11.jar, > /Users/esm/.m2/repository/javax/servlet/servlet-api/2.3/servlet-api-2.3.jar, > /Users/esm/.m2/repository/commons-collections/commons-collections/2.1/commons-collections-2.1.jar, > /Users/esm/.m2/repository/xerces/xercesImpl/2.0.2/xercesImpl-2.0.2.jar, > /Users/esm/.m2/repository/commons-dbcp/commons-dbcp/1.2.1/commons-dbcp-1.2.1.jar, > /Users/esm/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar, > /Users/esm/.m2/repository/commons-pool/commons-pool/1.2/commons-pool-1.2.jar, > /Users/esm/.m2/repository/logkit/logkit/1.0.1/logkit-1.0.1.jar, > /Users/esm/.m2/repository/edu/jhu/library/embargo/embargo-api/1.0.0-S
[jira] Created: (MARTIFACT-9) Prefer LinkedHashMap over HashMap
Prefer LinkedHashMap over HashMap - Key: MARTIFACT-9 URL: http://jira.codehaus.org/browse/MARTIFACT-9 Project: Maven Artifact Issue Type: Improvement Reporter: Benjamin Bentmann Priority: Trivial Attachments: deterministic-map-ordering.patch Sometimes order is important, Maven is learning that the hard way (MNG-1412, MNG-3118, SUREFIRE-61, ...). Methods that don't know for sure that ordering is irrelevant should follow "better safe than sorry" and keep the ordering of input collections. -- 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-151) Use File(URI) for converting from URI to File
Use File(URI) for converting from URI to File
-
Key: MDEP-151
URL: http://jira.codehaus.org/browse/MDEP-151
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Components: analyze
Affects Versions: 2.0
Reporter: Benjamin Bentmann
Assignee: Brian Fox
Priority: Trivial
Attachments: uri-to-file.patch
There is a dedicated constructor to create a {{java.io.File}} from
{{java.net.URI}} which does more than {{File(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: (MRELEASE-156) Prompt for customizing commit comment during release preparation
[ http://jira.codehaus.org/browse/MRELEASE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125685 ] Dennis Lundberg commented on MRELEASE-156: -- Perhaps you can use the configuration parameter scmCommentPrefix as a work around? See http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#scmCommentPrefix > Prompt for customizing commit comment during release preparation > > > Key: MRELEASE-156 > URL: http://jira.codehaus.org/browse/MRELEASE-156 > Project: Maven 2.x Release Plugin > Issue Type: Improvement >Affects Versions: 2.0-beta-4 >Reporter: Dário Oliveros > > Hi there, > I've been trying to use maven-release-plugin to prepare a release, but > whenever I do that, it fails since I have a SVN precommit hook that > integrates with an issue tracking system which in turn waits for a comment > containing an issue number. Since release plugin adds its own comment, such > as "[maven-release-plugin] prepare release ...", this integration fails. So > I was wondering if this could be prompted in the same way for the release and > next development iteration versions. > Thanks, > Dário -- 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: (MSITE-306) [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
[ http://jira.codehaus.org/browse/MSITE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125687 ] Dennis Lundberg commented on MSITE-306: --- I don't think that this particular output comes from the site plugin itself. That has been fixed. It probably comes from a reporting plugin that is executed during the site phase. Can you please attach the full output from a 'mvn site' execution? > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > > > Key: MSITE-306 > URL: http://jira.codehaus.org/browse/MSITE-306 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: Alexandre Navarro >Priority: Minor > > I always get the error below: > [INFO] Velocimacro : initialization starting. > [INFO] Velocimacro : adding VMs from VM library template : > VM_global_library.vm > [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in > any resource loader. > [INFO] Velocimacro : error using VM library template VM_global_library.vm : > org.apache.velocity.exception.ResourceNotFoundException: Unable to find > resource 'VM_global_library.vm' > [INFO] Velocimacro : VM library template macro registration complete. > this does not seem to affect my site generation. > I get rid of this because my build server (Luntbuild/Quickbuild) thinks there > is an error. > thanks, > Alexandre > PS : The same bug was reported before > http://jira.codehaus.org/browse/MSITE-286 > normally it mght be fixed in 2.0-beta-6 but it not true (not for me). -- 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-150) Indeterministic artifact ordering can cause bogus warnings
Indeterministic artifact ordering can cause bogus warnings
--
Key: MDEP-150
URL: http://jira.codehaus.org/browse/MDEP-150
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: analyze
Affects Versions: 2.0
Reporter: Benjamin Bentmann
Assignee: Brian Fox
Priority: Trivial
Attachments: deterministic-artifact-ordering.patch
Once MNG-1412 gets released, it will be nice to have the dependency analyzer
respect ordering, too.
As some motivation, consider a project P with the following dependency tree:
{noformat}
Project P
+- Dep A
+- Dep B
{noformat}
Further assume that both dependencies a and B contain the same class X (for
whatever reason, say backward-compat). Project P directly uses this class X
(hence Dep A being a dependency of P).
Currenlty, the ordering of artifacts is ignored by the analyzer such that the
{{artifactClassMap}} might list Dep B before Dep A. This in turn will make
{{findArtifactForClassName()}} return Dep B as the source artifact for class X
which results in the bogus warning "Used undeclared dependency Dep B" because
Dep A should have been considered instead as it is first on the class path.
--
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-3424) Respect ordering of elements as given in POM
Respect ordering of elements as given in POM
Key: MNG-3424
URL: http://jira.codehaus.org/browse/MNG-3424
Project: Maven 2
Issue Type: Improvement
Affects Versions: 2.0.8
Reporter: Benjamin Bentmann
Priority: Trivial
Attachments: retain-collection-order.patch
"Better safe than sorry" suggests to keep the ordering of collections when
converting them into maps. It's hard to know when ordering is really irrelevant
and the penalty of using {{java.util.Linked*}} is usually neglectable.
--
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: (SUREFIRE-462) Running Surefire with TestNG fails
[ http://jira.codehaus.org/browse/SUREFIRE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-462. - Resolution: Won't Fix This is a known issue with Surefire 2.3, fixed in 2.4. I recommend the latest version, 2.4.2. > Running Surefire with TestNG fails > -- > > Key: SUREFIRE-462 > URL: http://jira.codehaus.org/browse/SUREFIRE-462 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.3 > Environment: maven-2.0.8, surefire-testng 2.3 >Reporter: Markus Wolf > > After updating to surefire-testng 2.3 the following exception is thrown. > --- > T E S T S > --- > org.apache.maven.surefire.booter.SurefireExecutionException: > org.testng.xml.XmlSuite.setParallel(Z)V; nested exception is > java.lang.NoSuchMethodError: org.testng.xml.XmlSuite.setParallel(Z)V > java.lang.NoSuchMethodError: org.testng.xml.XmlSuite.setParallel(Z)V > at > org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:123) > at org.apache.maven.surefire.Surefire.run(Surefire.java:132) > 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:597) > at > org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290) > at > org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818) > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > -- 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125702 ] Hadrian Zbarcea commented on MNG-2551: -- I fought with the same unexplainable issue (on osx 10.5.2) until dkulp gave me a valuable pointer. It only happened during deploy. What made things worse is that an xml parsing error would pop up only later, while using the truncated pom. The problem in my case was that I was deploying back into the local maven2 repo so pom files were written back to the same location they were read from (doh). Deploying to a different location made the problem go away. So I suspect this is not a problem after all. I guess an enhancement would be to verify that the read and write locations are not the same (even that may not be totally possible if soft links are used, but hey, it's more than nothing). > 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 >Affects Versions: 2.0.4 > Environment: Win XP, JDK 1.4 >Reporter: Sharmarke Aden > Fix For: Reviewed Pending Version Assignment > > 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: (MNG-2551) pom metadata file gets truncated during install into local repository
[ http://jira.codehaus.org/browse/MNG-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125705 ] Todd Flora commented on MNG-2551: - We have tried both setting our local repo to the same repo as our deployment repo and setting our local repo to a different location from our deployment repo and this issue still exists. Am I missing something here we have our settings.xml setup to use a local user directory on the box and the distribution section of our pom to point at our webapps/deployment folder. > 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 >Affects Versions: 2.0.4 > Environment: Win XP, JDK 1.4 >Reporter: Sharmarke Aden > Fix For: Reviewed Pending Version Assignment > > 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] Updated: (MRESOURCES-42) Filtering properties that contain ${basedir} for property files doesn't escape backslashes
[
http://jira.codehaus.org/browse/MRESOURCES-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MRESOURCES-42:
---
Fix Version/s: 2.3
> Filtering properties that contain ${basedir} for property files doesn't
> escape backslashes
> ---
>
> Key: MRESOURCES-42
> URL: http://jira.codehaus.org/browse/MRESOURCES-42
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
>Affects Versions: 2.2, 2.3
> Environment: OS: Windows XP; Maven: 2.0.5, 2.0.6;
>Reporter: Jérémy Soula
> Fix For: 2.3
>
> Attachments: MRESOURCES-42-maven-resources-plugin-2.3-SNAPSHOT.patch
>
>
> For exemple consider this in a filtered property files
> application.propertyOne=${pom.build.directory}
> application.propertyTwo=${basedir}
> which generates after filtering:
> application.propertyOne=D\:\\ProjectsDirectory\\project\\target
> application.propertyTwo=D:\ProjectsDirectory\project\
> Behavior are different and causes a second property bad value when reading
> the properties file.
--
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: (MRESOURCES-8) maven-resources-plugin ignores configuration/resources property
[
http://jira.codehaus.org/browse/MRESOURCES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125710
]
Olivier Lamy commented on MRESOURCES-8:
---
IMHO adding a mojo called copy-resources is the best option here.
> maven-resources-plugin ignores configuration/resources property
> ---
>
> Key: MRESOURCES-8
> URL: http://jira.codehaus.org/browse/MRESOURCES-8
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
>Reporter: Leszek Gawron
>Assignee: Brett Porter
> Attachments: example.zip, MRESOURCES-8-workaround.patch, pom.xml
>
>
> I am evaluating maven + eclipse combo. In a trivial POM filtered resources
> exist only in target/classes. If one executes Project -> Clean under eclipse
> this information is lost. If filtered resources would appear as source folder
> they would survive cleaning and not got overriden by unfiltered ones.
> I have been trying to implement a scenario which would allow filtered
> resources to appear as "static" source folder under eclipse.
> The POM explains it best:
> 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
> com.mobilebox.squash.client
> squash-client
> jar
> 1.0-SNAPSHOT
> Maven Quick Start Archetype
> http://maven.apache.org
>
>
>
> maven-resources-plugin
>
>
> prefilter-resources
> generate-resources
>
> resources
>
>
>
> target/generated-resources
>
>
>
> src/main/resource-templates
> true
>
>
>
>
>
>
>
>
> ${ffile}
>
>
>
> src/main/resources
>
>
> target/generated-resources
>
>
>
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
> filter.properties
>
>
> thing is this part:
>
>
> src/main/properties
> true
>
>
> is completely ignored. Instead for both maven-resource-plugin executions (the
> one in generate-resources phase and the default one) this config is used:
>
>
> src/main/resources
>
>
> target/generated-resources
>
>
> which of course breaks the whole idea.
> Is this a bug or a design decision. In latter case is there any equivalent
> approach I might take?
--
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: (MRESOURCES-49) Maven 2 resources:resources causes NPE
[ http://jira.codehaus.org/browse/MRESOURCES-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRESOURCES-49. -- Resolution: Cannot Reproduce I cannot reproduce. If you can, please reopen the issue with a simple project which reproduce the issue. Thanks. > Maven 2 resources:resources causes NPE > -- > > Key: MRESOURCES-49 > URL: http://jira.codehaus.org/browse/MRESOURCES-49 > Project: Maven 2.x Resources Plugin > Issue Type: Bug > Environment: Maven 2.0.2 > java version "1.5.0_02" > 4GB RAM (plenty) > Diskspace app 1 tera (plenty) > 2.2Mhz Wintel >Reporter: Martin Gainty > Original Estimate: 1 minute > Remaining Estimate: 1 minute > > Download Jetty 6.1.0 > cd /Jetty/jetty-6.1.0 > mvn > everything is fine until the resources plugin is called and then NPE > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [GC [DefNew: 3962K->0K(4032K), 0.0059200 secs] 47622K->44219K(262080K), > 0.006027 > 0 secs] > [INFO] > - > --- > [ERROR] FATAL ERROR > [INFO] > - > --- > [INFO] null > [INFO] > - > --- > [INFO] Trace > java.lang.NullPointerException > at org.apache.maven.wagon.PathUtils.protocol(PathUtils.java:206) > at > org.apache.maven.wagon.repository.Repository.setUrl(Repository.java:1 > 19) > at > org.apache.maven.wagon.repository.Repository.(Repository.java:7 > 2) > at > org.apache.maven.artifact.repository.DefaultArtifactRepository. > (DefaultArtifactRepository.java:67) > at > org.apache.maven.artifact.repository.DefaultArtifactRepositoryFactory > .createDeploymentArtifactRepository(DefaultArtifactRepositoryFactory.java:41) > at > org.apache.maven.project.ProjectUtils.buildDeploymentArtifactReposito > ry(ProjectUtils.java:77) > at > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLog > ic(DefaultMavenProjectBuilder.java:751) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave > nProjectBuilder.java:631) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromReposito > ry(DefaultMavenProjectBuilder.java:353) > at > org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenM > etadataSource.java:102) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(D > efaultArtifactCollector.java:282) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(D > efaultArtifactCollector.java:67) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTra > nsitively(DefaultArtifactResolver.java:223) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTra > nsitively(DefaultArtifactResolver.java:211) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTra > nsitively(DefaultArtifactResolver.java:182) > at > org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsC > omplete(DefaultPluginManager.java:611) > at > org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Defaul > tPluginManager.java:522) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:393) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:531) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:472) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:270) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:139) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher
[jira] Updated: (DOXIA-217) Make default internal classes
[ http://jira.codehaus.org/browse/DOXIA-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated DOXIA-217: -- Summary: Make default internal classes (was: Make default impl classes) > Make default internal classes > - > > Key: DOXIA-217 > URL: http://jira.codehaus.org/browse/DOXIA-217 > Project: Maven Doxia > Issue Type: Improvement > Components: Module - Confluence, Module - Rtf, Module - Twiki >Affects Versions: 1.0-alpha-10 >Reporter: Vincent Siveton > Fix For: 1.0-beta-1 > > > doxia-module-rtf > doxia-module-confluence > doxia-module-twiki -- 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: (DOXIA-217) Make default internal classes
[ http://jira.codehaus.org/browse/DOXIA-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed DOXIA-217. - Assignee: Vincent Siveton Resolution: Fixed Fixed > Make default internal classes > - > > Key: DOXIA-217 > URL: http://jira.codehaus.org/browse/DOXIA-217 > Project: Maven Doxia > Issue Type: Improvement > Components: Module - Confluence, Module - Rtf, Module - Twiki >Affects Versions: 1.0-alpha-10 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 1.0-beta-1 > > > doxia-module-rtf > doxia-module-confluence > doxia-module-twiki -- 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: (SUREFIRE-463) ClassCastException when using testng suiteXmlFile
ClassCastException when using testng suiteXmlFile - Key: SUREFIRE-463 URL: http://jira.codehaus.org/browse/SUREFIRE-463 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.4.2 Environment: linux 2.6.22-1-mepis-smp Reporter: Andreas Andreou The related pom part is: browser org.apache.maven.plugins maven-surefire-plugin src/test/resources/testng-browser.xml Issuing mvn -Pbrowser test results in the exception: java.lang.ClassCastException: java.io.File cannot be cast to java.lang.String at org.apache.maven.surefire.booter.SurefireBooter.runSuitesForkPerTestSet(SurefireBooter.java:403) at org.apache.maven.surefire.booter.SurefireBooter.run(SurefireBooter.java:249) at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:492) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) 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:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Any workarounds for this? -- 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
