[jira] Commented: (MAVENUPLOAD-470) Upload glazedlists On ibiblio / give URL if already there
[ http://jira.codehaus.org/browse/MAVENUPLOAD-470?page=comments#action_44224 ] Martin Skopp commented on MAVENUPLOAD-470: -- fixed Upload glazedlists On ibiblio / give URL if already there - Key: MAVENUPLOAD-470 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-470 Project: maven-upload-requests Type: Task Reporter: Martin Skopp http://trackdemo.riege.com/glazedlists-0.9.7-bundle.jar https://glazedlists.dev.java.net/ https://glazedlists.dev.java.net/ Hi Maven-Team, I haven't found glazedlists on ibiblio (btw: it would be superb if one could download/search a list of ALL jar file on ibiblio!) so I hope you guys put it on. It's a pretty cool project for dynamically filtered and sorted tables. Thanks Martin -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-718) dependency management validation requires a version, when you might just want to force a scope.
[ http://jira.codehaus.org/browse/MNG-718?page=comments#action_44225 ] Kenney Westerhof commented on MNG-718: -- I don't see why forcing a scope is useful. Specifying default versions is more useful. Each pom has to determine for itself what the scope of a dependency is; in a project tree, the same dependency can be used several times with different scopes (i've got an example of this). dependency management validation requires a version, when you might just want to force a scope. --- Key: MNG-718 URL: http://jira.codehaus.org/browse/MNG-718 Project: Maven 2 Type: Bug Reporter: Brett Porter Fix For: 2.0-beta-2 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-711) NPE when calling 'm2 surefire:test'
[ http://jira.codehaus.org/browse/MNG-711?page=all ] Kenney Westerhof closed MNG-711: NPE when calling 'm2 surefire:test' --- Key: MNG-711 URL: http://jira.codehaus.org/browse/MNG-711 Project: Maven 2 Type: Bug Versions: 2.0-beta-1 Reporter: Kenney Westerhof Assignee: Kenney Westerhof Fix For: 2.0-beta-1 MavenProject.getArtifacts() can return null when a single mojo is called (and @requiresDependencyResolution is not set). The code however expects it to be non-null (everywhere .size() etc. is called). -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-692) Project.getArtifacts() returns artifacts with getFile() pointing to target/classes when that project is in the reactor
[ http://jira.codehaus.org/browse/MNG-692?page=all ] Kenney Westerhof closed MNG-692: fixed the plugins to update the project's artifact Project.getArtifacts() returns artifacts with getFile() pointing to target/classes when that project is in the reactor -- Key: MNG-692 URL: http://jira.codehaus.org/browse/MNG-692 Project: Maven 2 Type: Bug Versions: 2.0-beta-1 Reporter: Kenney Westerhof Assignee: Kenney Westerhof Priority: Blocker Fix For: 2.0-beta-1 MNG-249 solves the reactor-awareness by setting the File of an Artifact to the Build.outputDirectory if the project is in the reactor (more or less). This leads to problems when plugins want to copy those artifacts: they're now pointing to directories (try the ear plugin for instance). -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-687) Crash: in source-plugin, using assembly:assembly goal, on non-SNAPSHOT project.
[ http://jira.codehaus.org/browse/MNG-687?page=all ] Kenney Westerhof closed MNG-687: modified the clone of a MavenProject to have a modifyable attachment list Crash: in source-plugin, using assembly:assembly goal, on non-SNAPSHOT project. --- Key: MNG-687 URL: http://jira.codehaus.org/browse/MNG-687 Project: Maven 2 Type: Bug Components: maven-plugins Versions: 2.0-beta-1 Environment: 2.0-beta-1-SNAPSHOT (from SVN: 20050801-1940) - linux and XP Reporter: Joakim Erdfelt Assignee: Kenney Westerhof Priority: Blocker Fix For: 2.0-beta-1 Attachments: assembly-unmodifiable-exception.tar.gz When using the assembly:assembly plugin, the following Exception occurs. java.lang.UnsupportedOperationException at java.util.Collections$UnmodifiableCollection.add(Collections.java:1004) at org.apache.maven.project.MavenProject.addAttachedArtifact(MavenProject.java:1016) at org.apache.maven.plugin.source.JarSourceMojo.execute(JarSourceMojo.java:106) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:361) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:378) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:351) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:437) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:373) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:359) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:341) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:229) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:123) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:209) at org.apache.maven.cli.MavenCli.main(MavenCli.java:267) 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:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Attached is an example project that shows this behaviour. I used the commands $ m2 clean:clean package $ m2 assembly:assembly -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-514) Provided dependencies not included in eclipse build path
[ http://jira.codehaus.org/browse/MNG-514?page=all ] Kenney Westerhof closed MNG-514: Provided dependencies not included in eclipse build path -- Key: MNG-514 URL: http://jira.codehaus.org/browse/MNG-514 Project: Maven 2 Type: Bug Components: maven-plugins Environment: Windows XP SP2, J2SE 5.0, running against main trunk in SVN. Reporter: Nathaniel Stoddard Assignee: Kenney Westerhof Fix For: 2.0-beta-1 When an eclipse project is generated for a project with a dependency whose scope is provided, the dependency is not included in the build path of the project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-508) mboot will not detect dependency versions injected via dependencyManagement
[ http://jira.codehaus.org/browse/MNG-508?page=all ] Kenney Westerhof closed MNG-508: mboot will not detect dependency versions injected via dependencyManagement --- Key: MNG-508 URL: http://jira.codehaus.org/browse/MNG-508 Project: Maven 2 Type: Bug Reporter: John Casey Assignee: Kenney Westerhof Fix For: 2.0-beta-1 the marmalade project makes use of dependencyManagement to help keep track of the common library versions used throughout the project. When these artifacts are subsequently released, their dependency versions are still a product of injecting that dependencyManagement info into the specific pom's dependency list. MBoot does not handle this correctly. instead, it blows off dependencyManagement sections. I'm correcting this for marmalade on the repository itself, but it will become a concern again as soon as the marmalade dependency is promoted to a new version. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r231199 - /maven/components/trunk/maven-plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java
Author: kenney Date: Wed Aug 10 02:16:23 2005 New Revision: 231199 URL: http://svn.apache.org/viewcvs?rev=231199view=rev Log: MNG-692, continued: also update project.artifact.file for War. I'm leaving it alone for non-war (i.e. exploded/inplace webapp) generation. Modified: maven/components/trunk/maven-plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java Modified: maven/components/trunk/maven-plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java?rev=231199r1=231198r2=231199view=diff == --- maven/components/trunk/maven-plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java (original) +++ maven/components/trunk/maven-plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java Wed Aug 10 02:16:23 2005 @@ -256,6 +256,8 @@ // create archive archiver.createArchive( project, archive ); + +project.getArtifact().setFile( warFile ); } } } - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Wed Aug 10 09:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050810.091500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050810.091500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPJBOSS-23) Deploy-ear fails with spaces in maven.build.dir
Deploy-ear fails with spaces in maven.build.dir
---
Key: MPJBOSS-23
URL: http://jira.codehaus.org/browse/MPJBOSS-23
Project: maven-jboss-plugin
Type: Bug
Versions: 1.5
Reporter: Geoffrey
Fix For: 1.6
Having spaces in maven.build.dir for example if the maven project is in Windows
Document and settings causes the jboss:deploy-ear goal to fail (and others
probably too).
.replaceAll(' ', '%20') works.
Actually all url-special characters should be encoded before handing it to the
jmx: space, , ... by doing something similar to a
HttpServletRequest.encodeUrl()
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Question About Reactor Operation
After doing some experimentation, I think I have a means to accomplish what I want without altering the way the reactor works. I think I can convince my coworkers that we should only document the production projects; this collapses the first two use cases into a single use case that I think can be handled using the module stanza in the POM. The third use case is a bit harder, but with the ability to build Java-based plugins I think I can build a plugin to do the aggregation as a separate process. The main things I need to figure out are: -- How do I define a new packaging value? Looking at the m2 code, it appears to involve something called an extension plugin but I could not find a description of what is required to make one. -- How do I link the items to be aggregated to the project? The likely answer here is configuration information provided to the plugin which does the aggregation. -- How do I ensure that the components to be aggregated are built by the reactor before the aggregation occurs? If I declare the components as dependencies, what scope can I use to ensure the correct build order without also causing the web application war files to be automatically added to the artifact being built? -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 09, 2005 07:58 To: Maven Developers List Subject: RE: Question About Reactor Operation -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, August 08, 2005 20:00 To: Maven Developers List Subject: Re: Question About Reactor Operation Allison, Bob wrote: Use Case 1: There are a number of project directories which do not produce artifacts (the top level and all mid-level directories, for example) as well as a few projects which are samples and should not be included in the production deliverables. Set these to packaging pom. If I set the packaging to pom on a sample project that is supposed to produce a deployable web application, won't that mess up the build process for that project? I want to be able to produce proper artifacts from the sample projects, just be able to automatically exclude them from production builds. Ok, I was confused because you said directories which do not produce artifacts, didn't catch the samples not included. Wouldn't you omit those from the modules list, and traverse them separately? IF they are not part of the product release, they probably aren't tagged and developed on the same timeline, so could even be in a separate tree? They could be in a separate tree, but that makes it hard to include them in the product documentation. Also, this case might include an obsolete deliverable that we don't want to remove from CVS quite yet (e.g., used in a version that is still being supported). I'm not talking about making site reactor-aware (something I am eagerly awaiting). I am referring to being able to automatically exclude some projects from the documentation. Ok, so if it is reactor aware, you want to exclude projects? Is this just the same use case as above applied to the site, or are there others that would be excluded? It is almost the same as the previous case, but the list of exclusions might be different so it would require a different property to filter on. This should be done by creating a web application subproject that depends on the portlet projects. The main problem with that, I think, is the portlet-specific deplyment descriptors. In the 1.0.2 build tree we are currently using I have done a bit of work to have these descriptors generated from project properties in such a way that the descriptor is correct whether I aggregated the portlets or not. I had a look at your example below and am still a little lost. I don't totally understand portlets so that may be the reason. If I'm off here I apologise, but here goes... One of the key things that makes Maven work is that a project always builds a single thing the same way. It appears from your example that a project builds a different descriptor depending on its usage. This is fine as long as it isn't included in the final artifact. Based on this paragraph, I guess I am back to either sticking with Maven 1.x or abandoning the idea of being able to keep the portlets in separate projects and aggregating them as necessary during the build process. It might be better to actually generate the aggregated descriptor inside the aggregated webapp with a different goal though, that is able to take the normal generated descriptors and put them together (if that's possible). The main reasons the descriptor is built inside of the individual component are: -- the content of the descriptor depends on a number of
[jira] Created: (MNG-720) short commandline options are not parsed
short commandline options are not parsed Key: MNG-720 URL: http://jira.codehaus.org/browse/MNG-720 Project: Maven 2 Type: Bug Components: maven-core Versions: 2.0-beta-1 Reporter: Kenney Westerhof Priority: Minor The short commandline options displayed in the usage of m2 --help don't get parsed: m2 -npl install Unable to parse command line options: Unrecognized option: -n usage: maven [options] [goal [goal2 [goal3] ...]] I've checked commons-cli and there's a fix for this in cvs/svn: http://cvs.apache.org/viewcvs.cgi/jakarta-commons/cli/src/java/org/apache/commons/cli/PosixParser.java see version 1.16 comments. I've tried bumping commons-cli to 1.0, but this fix apparently isn't in there. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-720) short commandline options are not parsed
[ http://jira.codehaus.org/browse/MNG-720?page=comments#action_44235 ] Trygve Laugstol commented on MNG-720: - There was another issue when upgrading to the 1.0 release so that's why we're still at rc2. short commandline options are not parsed Key: MNG-720 URL: http://jira.codehaus.org/browse/MNG-720 Project: Maven 2 Type: Bug Components: maven-core Versions: 2.0-beta-1 Reporter: Kenney Westerhof Priority: Minor The short commandline options displayed in the usage of m2 --help don't get parsed: m2 -npl install Unable to parse command line options: Unrecognized option: -n usage: maven [options] [goal [goal2 [goal3] ...]] I've checked commons-cli and there's a fix for this in cvs/svn: http://cvs.apache.org/viewcvs.cgi/jakarta-commons/cli/src/java/org/apache/commons/cli/PosixParser.java see version 1.16 comments. I've tried bumping commons-cli to 1.0, but this fix apparently isn't in there. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r231226 - in /maven/components/trunk/sandbox/csharp: ./ maven-csharp-plugin/ maven-csharp-plugin/src/ maven-csharp-plugin/src/main/ maven-csharp-plugin/src/main/java/ maven-csharp-plugin/src/main/java/org/ maven-csharp-plugin/src/main/java/...
Author: brett Date: Wed Aug 10 06:12:25 2005 New Revision: 231226 URL: http://svn.apache.org/viewcvs?rev=231226view=rev Log: add a basic C# plugin using the Ant tasks Added: maven/components/trunk/sandbox/csharp/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/pom.xml (with props) maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/java/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/java/org/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/java/org/apache/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/java/org/apache/plugins/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/java/org/apache/plugins/csharp/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/java/org/apache/plugins/csharp/compiler/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/java/org/apache/plugins/csharp/compiler/CSharpCompiler.java (with props) maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/java/org/apache/plugins/csharp/compiler/CSharpCompilerMojo.java (with props) maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/java/org/apache/plugins/csharp/helpers/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/java/org/apache/plugins/csharp/helpers/AntBuildListener.java (with props) maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/resources/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/resources/META-INF/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/resources/META-INF/plexus/ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/resources/META-INF/plexus/components.xml (with props) maven/components/trunk/sandbox/csharp/maven-csharp-test/ maven/components/trunk/sandbox/csharp/maven-csharp-test/pom.xml (with props) maven/components/trunk/sandbox/csharp/maven-csharp-test/src/ maven/components/trunk/sandbox/csharp/maven-csharp-test/src/main/ maven/components/trunk/sandbox/csharp/maven-csharp-test/src/main/csharp/ maven/components/trunk/sandbox/csharp/maven-csharp-test/src/main/csharp/Test.cs Added: maven/components/trunk/sandbox/csharp/maven-csharp-plugin/pom.xml URL: http://svn.apache.org/viewcvs/maven/components/trunk/sandbox/csharp/maven-csharp-plugin/pom.xml?rev=231226view=auto == --- maven/components/trunk/sandbox/csharp/maven-csharp-plugin/pom.xml (added) +++ maven/components/trunk/sandbox/csharp/maven-csharp-plugin/pom.xml Wed Aug 10 06:12:25 2005 @@ -0,0 +1,52 @@ +?xml version=1.0 encoding=UTF-8? +project + modelVersion4.0.0/modelVersion + parent +groupIdorg.apache.maven.plugins/groupId +artifactIdmaven-plugin-parent/artifactId +version2.0-beta-1-SNAPSHOT/version + /parent + artifactIdmaven-csharp-plugin/artifactId + packagingmaven-plugin/packaging + namecsharp-plugin/name + version1.0-SNAPSHOT/version + inceptionYear2005/inceptionYear + descriptionM2 csharp plugin/description + + contributors +contributor + nameGilles Dodinet/name + email[EMAIL PROTECTED]/email + organizationKarmic Software Research/organization +/contributor + /contributors + + dependencies +dependency + groupIdorg.apache.maven/groupId + artifactIdmaven-artifact/artifactId + version2.0-beta-1-SNAPSHOT/version +/dependency +dependency + groupIdorg.apache.maven/groupId + artifactIdmaven-project/artifactId + version2.0-beta-1-SNAPSHOT/version +/dependency +dependency + groupIdplexus/groupId + artifactIdplexus-compiler-api/artifactId + version1.2/version +/dependency +dependency + groupIdant/groupId + artifactIdant/artifactId + version1.6.5/version +/dependency +dependency + groupIdant/groupId + artifactIdant-nodeps/artifactId + version1.6.5/version +/dependency + /dependencies +/project + Propchange: maven/components/trunk/sandbox/csharp/maven-csharp-plugin/pom.xml -- svn:eol-style = native Propchange: maven/components/trunk/sandbox/csharp/maven-csharp-plugin/pom.xml -- svn:keywords = Author Date Id Revision Added: maven/components/trunk/sandbox/csharp/maven-csharp-plugin/src/main/java/org/apache/plugins/csharp/compiler/CSharpCompiler.java URL:
[maven2 build - SUCCESS - update] Wed Aug 10 13:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050810.131500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050810.131500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1659) Dependency jars are not downloading from remote repository placed in Subversion with http access
Dependency jars are not downloading from remote repository placed in Subversion with http access Key: MAVEN-1659 URL: http://jira.codehaus.org/browse/MAVEN-1659 Project: Maven Type: Bug Versions: 1.1-beta-1 Environment: Server: Apache 1.3.x with Subversion 1.1.1 Client: Linux 2.6/Windows 2000, J2SE 5.0 Reporter: Roman Krutyakov Dependencies are not downloading from remote repository if it's placed in Subversion with http access (with apache and mod_davsvn) In verbose mode maven logs (under linux): --- Getting failed dependencies: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Attempting to download slamd_client-1.8.1.jar. http://server.net:81/svn/v2/trunk/target/maven//slamd/jars/slamd_client-1.8.1.jar - Status code: 200 Local file is newer: not downloaded Attempting to download slamd_server-1.8.1.jar. http://server.net:81/svn/v2/trunk/target/maven//slamd/jars/slamd_server-1.8.1.jar - Status code: 200 Local file is newer: not downloaded Artifact '/opt/maven-repository/slamd/jars/slamd_client-1.8.1.jar' not found to add to classpath Artifact '/opt/maven-repository/slamd/jars/slamd_server-1.8.1.jar' not found to add to classpath --- in local repository appropriate paths are created, but jar files are missing this was checked against repository server with basic auth and without authentication - result is the same affected version 1.1-beta-1, 1.0.x works 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r231230 - in /maven/components/trunk/maven-plugins: ./ maven-antrun-plugin/ maven-antrun-plugin/src/ maven-antrun-plugin/src/main/ maven-antrun-plugin/src/main/java/ maven-antrun-plugin/src/main/java/org/ maven-antrun-plugin/src/main/java/o...
Author: kenney Date: Wed Aug 10 06:38:21 2005 New Revision: 231230 URL: http://svn.apache.org/viewcvs?rev=231230view=rev Log: Donating maven-antrun-plugin to the Maven2 project, as discussed with Brett. Enjoy! :-) TODO: o make echo.../echo output visible. o devise a way to pass on maven2 properties to ant/-called build.xml files. The ant code just copies all properties from the default PropertyHandler, however with m2 that's not possible since they are resolved/evaluated at runtime. Added: maven/components/trunk/maven-plugins/maven-antrun-plugin/ maven/components/trunk/maven-plugins/maven-antrun-plugin/pom.xml (with props) maven/components/trunk/maven-plugins/maven-antrun-plugin/src/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/java/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/java/org/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/java/org/apache/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/java/org/apache/maven/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/java/org/apache/maven/plugin/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/java/org/apache/maven/plugin/antrun/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/java/org/apache/maven/plugin/antrun/AntPropertyHelper.java (with props) maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/java/org/apache/maven/plugin/antrun/AntRunMojo.java (with props) maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/java/org/apache/maven/plugin/antrun/components/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/java/org/apache/maven/plugin/antrun/components/AntTargetConverter.java (with props) maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/resources/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/resources/META-INF/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/resources/META-INF/plexus/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/main/resources/META-INF/plexus/components.xml (with props) maven/components/trunk/maven-plugins/maven-antrun-plugin/src/site/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/site/site.xml (with props) maven/components/trunk/maven-plugins/maven-antrun-plugin/src/site/xdoc/ maven/components/trunk/maven-plugins/maven-antrun-plugin/src/site/xdoc/introduction.xml (with props) maven/components/trunk/maven-plugins/maven-antrun-plugin/src/site/xdoc/usage.xml (with props) Modified: maven/components/trunk/maven-plugins/pom.xml Added: maven/components/trunk/maven-plugins/maven-antrun-plugin/pom.xml URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-antrun-plugin/pom.xml?rev=231230view=auto == --- maven/components/trunk/maven-plugins/maven-antrun-plugin/pom.xml (added) +++ maven/components/trunk/maven-plugins/maven-antrun-plugin/pom.xml Wed Aug 10 06:38:21 2005 @@ -0,0 +1,54 @@ +model + xmlns=http://maven.apache.org/POM/4.0.0; + xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; + xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; + + modelVersion4.0.0/modelVersion + parent +artifactIdmaven-plugin-parent/artifactId +groupIdorg.apache.maven.plugins/groupId +version2.0-beta-1-SNAPSHOT/version + /parent + artifactIdmaven-antrun-plugin/artifactId + packagingmaven-plugin/packaging + version1.0-alpha-1-SNAPSHOT/version + + nameMaven AntRun Plugin/name + descriptionRuns ant scripts embedded in the POM/description + + developers +developer + idkenney/id + nameKenney Westerhof/name + email[EMAIL PROTECTED]/email +/developer + /developers + + dependencies +dependency + groupIdorg.apache.maven/groupId + artifactIdmaven-project/artifactId +/dependency + +dependency + groupIdplexus/groupId + artifactIdplexus-container-default/artifactId +/dependency + +dependency + groupIdant/groupId + artifactIdant/artifactId + version1.6.5/version +/dependency + +!-- needed for launching a build.xml file -- +dependency + groupIdant/groupId + artifactIdant-launcher/artifactId + version1.6.5/version + scoperuntime/scope +/dependency + + /dependencies + +/model Propchange: maven/components/trunk/maven-plugins/maven-antrun-plugin/pom.xml -- svn:eol-style = native Propchange: maven/components/trunk/maven-plugins/maven-antrun-plugin/pom.xml -- svn:keywords =
[jira] Created: (MNG-721) reactor summary should have time taken next to SUCCESS message for each subproject
reactor summary should have time taken next to SUCCESS message for each subproject -- Key: MNG-721 URL: http://jira.codehaus.org/browse/MNG-721 Project: Maven 2 Type: Improvement Components: maven-core Reporter: Brett Porter Priority: Trivial Fix For: 2.0-beta-2 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Aug 10 13:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050810.134500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Wed Aug 10 14:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050810.141500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050810.141500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPJIRA-13) Update plugin to fix outstanding issues and more
Update plugin to fix outstanding issues and more Key: MPJIRA-13 URL: http://jira.codehaus.org/browse/MPJIRA-13 Project: maven-jira-plugin Type: Improvement Versions: 1.2 Reporter: Michael Franken Assigned to: Emmanuel Venisse Fix For: 1.2 Attachments: maven-jira-plugin-patch.txt I've updated the maven-jira-plugin, and fixed issues MPJIRA-4, MPJIRA-5, MPJIRA-6, MPJIRA-8 and MPJIRA-11. Patch is attached. I've used parts of the patch that was supplied by Dr. Spock (MPJIRA-8). I hope this patch gets some serious attention. Documentation is complete. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPJIRA-7) maven-jira-plugin could not generate report
[ http://jira.codehaus.org/browse/MPJIRA-7?page=comments#action_44239 ] Michael Franken commented on MPJIRA-7: -- The problem withthis issue, is that the project id is incorrect. It should probably be a number, not 'PSH'. I guess it can be closed. maven-jira-plugin could not generate report --- Key: MPJIRA-7 URL: http://jira.codehaus.org/browse/MPJIRA-7 Project: maven-jira-plugin Type: Bug Versions: 1.2 Reporter: Charles Moulliard Assignee: Emmanuel Venisse The jira-report.xml generated is not well formed for the plugin Xdoc. E:\ING_dvlpt\pshmaven maven-jira-plugin:report __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.1 Downloading http://194.154.201.204/secure/IssueNavigator.jspa?view=rsspid=PSHsorter/field=issuekeysor ter/order=DESCsorter/field=statussorter/order=DESCtempMax=1000reset=truedecorator=none BUILD FAILED File.. V:\.maven\cache\maven-xdoc-plugin-1.8\plugin.jelly Element... x:parse Line.. 120 Column 48 Error on line 24 of document file:/E:/ING_dvlpt/psh/target/jira/jira-results.xml : Open quote is expected for attribute width. Nested exception: Open quote is expected for attribute width. Total time: 10 seconds Finished at: Mon Nov 29 13:51:07 CET 2004 Jira 3.0 is used. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - SUCCESS - update] Wed Aug 10 14:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20050810.143000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050810.143000.txt
svn commit: r231258 - in /maven/components/trunk/maven-site/src/site: apt/building.apt apt/developers/building.apt apt/developers/development-guide.apt fml/about.fml fml/general.fml site.xml xdoc/index.xml
Author: trygvis
Date: Wed Aug 10 08:06:03 2005
New Revision: 231258
URL: http://svn.apache.org/viewcvs?rev=231258view=rev
Log:
o Adding a part on how to get into development of m2 itself.
Added:
maven/components/trunk/maven-site/src/site/apt/developers/building.apt
- copied, changed from r231057,
maven/components/trunk/maven-site/src/site/apt/building.apt
Removed:
maven/components/trunk/maven-site/src/site/apt/building.apt
Modified:
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
maven/components/trunk/maven-site/src/site/fml/about.fml
maven/components/trunk/maven-site/src/site/fml/general.fml
maven/components/trunk/maven-site/src/site/site.xml
maven/components/trunk/maven-site/src/site/xdoc/index.xml
Copied: maven/components/trunk/maven-site/src/site/apt/developers/building.apt
(from r231057, maven/components/trunk/maven-site/src/site/apt/building.apt)
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/apt/developers/building.apt?p2=maven/components/trunk/maven-site/src/site/apt/developers/building.aptp1=maven/components/trunk/maven-site/src/site/apt/building.aptr1=231057r2=231258rev=231258view=diff
==
--- maven/components/trunk/maven-site/src/site/apt/building.apt (original)
+++ maven/components/trunk/maven-site/src/site/apt/developers/building.apt Wed
Aug 10 08:06:03 2005
@@ -53,7 +53,11 @@
export M2_HOME=/usr/local/maven-2.0-SNAPSHOT
PATH=$M2_HOME/bin:$PATH
+
+
or
+
+
set M2_HOME=c:\maven-2.0-SNAPSHOT
set PATH=%M2_HOME%\bin;%PATH%
@@ -62,7 +66,11 @@
sh m2-bootstrap-all.sh
+
+
or
+
+
m2-bootstrap-all.bat
@@ -77,7 +85,5 @@
* M2_HOME directory contains a valid installation of m2 (ie
$M2_HOME/bin/m2.conf or %M2_HOME%\bin\m2.conf exists).
- If you have any problems or get any failures during the run, please report
them to the
+ If you have any problems or get any failures during the run, please report
them to the
{{{/mail-lists.html} Maven Developers List}}.
-
-
Modified:
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt?rev=231258r1=231257r2=231258view=diff
==
---
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
(original)
+++
maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt
Wed Aug 10 08:06:03 2005
@@ -2,27 +2,135 @@
Development Guide
--
Emmanuel Venisse
+Trygve Laugstol
--
8 July 2005
--
-~~ Copyright 2001-2004 The Apache Software Foundation.
-~~
+~~ Copyright 2005 The Apache Software Foundation.
+~~
~~ Licensed under the Apache License, Version 2.0 (the License);
~~ you may not use this file except in compliance with the License.
~~ You may obtain a copy of the License at
-~~
+~~
~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
+~~
~~ Unless required by applicable law or agreed to in writing, software
~~ distributed under the License is distributed on an AS IS BASIS,
~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~~ See the License for the specific language governing permissions and
~~ limitations under the License.
-Subversion configuration
+Developing Maven 2
-Before committing files in subversion repository, you need to read the
-{{{http://www.apache.org/dev/version-control.html#https-svn}Committer
Subversion Access}}
-document and you must set your svn client
-with these properties file : {{svn-eol-style.txt}}
+ This document describes how to get started into developing Maven 2 itself.
There is a separate page describing how
+ to {{{building.html}building Maven 2}}.
+
+* Finding some work to do
+
+ First of all you need something to work on! Unless you have found a
particular issue you would like to work on
+ the Maven team has categorized a few issues that we could use your help to
solve them. The list is on our
+ {{{http://docs.codehaus.org/display/MAVEN/How+to+help}Conflucene wiki}} and
will be updated every 60 minutes.
+
+ JIRA also has RSS feeds available if you'd like to include those in your
favorite feed aggregator.
+
+ We categorize the issues in three different categories:
+
+ * Noice: No previous exposure to the code needed.
+
({{{http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rsspid=10500resolutionIds=-1customfield_10010=Novicesorter/field=prioritysorter/order=ASCsorter/field=issuekeysorter/order=ASCtempMax=25reset=truedecorator=none}rss
feed}})
+
+ * Intermediate: Exposure to Maven pluins and/or internals required.
+
[maven2 build - SUCCESS - update] Wed Aug 10 15:15:01 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050810.151501.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050810.151501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1659) Dependency jars are not downloading from remote repository placed in Subversion with http access
[ http://jira.codehaus.org/browse/MAVEN-1659?page=all ] Brett Porter updated MAVEN-1659: Fix Version: 1.1-beta-2 Dependency jars are not downloading from remote repository placed in Subversion with http access Key: MAVEN-1659 URL: http://jira.codehaus.org/browse/MAVEN-1659 Project: Maven Type: Bug Versions: 1.1-beta-1 Environment: Server: Apache 1.3.x with Subversion 1.1.1 Client: Linux 2.6/Windows 2000, J2SE 5.0 Reporter: Roman Krutyakov Fix For: 1.1-beta-2 Dependencies are not downloading from remote repository if it's placed in Subversion with http access (with apache and mod_davsvn) In verbose mode maven logs (under linux): --- Getting failed dependencies: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Attempting to download slamd_client-1.8.1.jar. http://server.net:81/svn/v2/trunk/target/maven//slamd/jars/slamd_client-1.8.1.jar - Status code: 200 Local file is newer: not downloaded Attempting to download slamd_server-1.8.1.jar. http://server.net:81/svn/v2/trunk/target/maven//slamd/jars/slamd_server-1.8.1.jar - Status code: 200 Local file is newer: not downloaded Artifact '/opt/maven-repository/slamd/jars/slamd_client-1.8.1.jar' not found to add to classpath Artifact '/opt/maven-repository/slamd/jars/slamd_server-1.8.1.jar' not found to add to classpath --- in local repository appropriate paths are created, but jar files are missing this was checked against repository server with basic auth and without authentication - result is the same affected version 1.1-beta-1, 1.0.x works 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] rearrange commits lists
Brett Porter wrote, On 8/8/2005 5:15 PM: Hi, Alan proposed we use the standard that is used when setting up Apache projects these days (we're still on our 2003 setup). Here it is in summary, elaborated into a bit more detail: 1) create [EMAIL PROTECTED], scm-commits, wagon-commits, continuum-commits 2) subscribe everyone on [EMAIL PROTECTED], [EMAIL PROTECTED], post to the list to let people know what they are in for and instructions to unsubscribe 3) stop *-dev forwarding from commits lists 4) reconfigure svn to put Maven commits to that list. I think Maven plugin developers should keep across what's happening in the core, so they can stay together, but the other subprojects remain separate. 5) keep JIRA and repository reports on [EMAIL PROTECTED] 6) send continuum/ci messages to the relevant commits list 7) disband the old cvs lists Please vote: [X] +1: in favour [ ] +0 x +1: in favour, but prefer a different setup [ ] 0: don't care either way [ ] -1: I don't like this for reason __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-478) Please upload extremecomponents to ibiblio
Please upload extremecomponents to ibiblio -- Key: MAVENUPLOAD-478 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-478 Project: maven-upload-requests Type: Improvement Reporter: Todd Huss I've created the project bundle for: http://extremecomponents.org/extremesite/welcome.jsp -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [me] Setting up the project in my IDE
On Wed, Aug 10, 2005 at 06:49:40PM +0200, Joerg Hohwiller wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I got a little lost in jakarta-commons since my getting involved? thread, but finally I checked out the complete m2 thing. You tailered your components quite small - which (usually) leads to a gread design. Anyways I am little frustrated setting all this up in my JAVA IDE (eclipse). I tried the according plugin to generate the IDE config but did not succeed since the toplevel POM seems to be broken. Broken how? Not all of the modules are in the default modules collection so you might have to go into some sub directories to be able to generate the project files for all Maven 2 artifacts. Do you have any suggestions (or maybe a developers manual :) ) to make my start a little easier? I added some how to develop Maven 2 earlier today, but as the site it not deployed yet you'll have to read it from the Subversion repository[1]. Not that that make it any harder to read, it's APT after all ;) As this is only a small start any contributions or just plain notes you're takin while getting into Maven 2 development would be appreciated. [1]: https://svn.apache.org/repos/asf/maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt -- Trygve signature.asc Description: Digital signature
Re: [me] Setting up the project in my IDE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Trygve Laugstøl wrote: On Wed, Aug 10, 2005 at 06:49:40PM +0200, Joerg Hohwiller wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I got a little lost in jakarta-commons since my getting involved? thread, but finally I checked out the complete m2 thing. You tailered your components quite small - which (usually) leads to a gread design. Anyways I am little frustrated setting all this up in my JAVA IDE (eclipse). I tried the according plugin to generate the IDE config but did not succeed since the toplevel POM seems to be broken. Broken how? Not all of the modules are in the default modules collection so you might have to go into some sub directories to be able to generate the project files for all Maven 2 artifacts. [EMAIL PROTECTED]:~/projects/maven2$ m2 eclipse:eclipse [INFO] - [INFO] BUILD FAILURE [INFO] - [INFO] Reason: Failed to parse model from file '/home/joerg/projects/maven2/pom.xml'. Error: 'TEXT must be immediately followed by END_TAG and not START_TAG (position: START_TAG seen ...snapshotRepository\n id... @121:11) ' [INFO] - [INFO] Total time: 1 second [INFO] Finished at: Wed Aug 10 19:16:09 CEST 2005 [INFO] Final Memory: 1M/2M [INFO] - [EMAIL PROTECTED]:~/projects/maven2$ cd maven-artifact [EMAIL PROTECTED]:~/projects/maven2/maven-artifact$ m2 eclipse:eclipse [INFO] maven: using locally installed snapshot [INFO] - [INFO] BUILD FAILURE [INFO] - [INFO] Reason: Failed to parse model from file '/home/joerg/.m2/repository/org/apache/maven/maven/2.0-beta-1-SNAPSHOT/maven-2.0-beta-1-SNAPSHOT.pom'. Error: 'TEXT must be immediately followed by END_TAG and not START_TAG (position: START_TAG seen ...snapshotRepository\n id... @121:11) ' [INFO] - [INFO] Total time: 1 second [INFO] Finished at: Wed Aug 10 19:16:34 CEST 2005 [INFO] Final Memory: 1M/2M [INFO] - So I need a toplevel POM that is NOT broken. Do you have any suggestions (or maybe a developers manual :) ) to make my start a little easier? I added some how to develop Maven 2 earlier today, but as the site it not deployed yet you'll have to read it from the Subversion repository[1]. Not that that make it any harder to read, it's APT after all ;) As this is only a small start any contributions or just plain notes you're takin while getting into Maven 2 development would be appreciated. [1]: https://svn.apache.org/repos/asf/maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt Thanks. But its more about general support and svn usage. I will contribute something if I am through with this (and its not the setup every single subproject in eclipse by hand solution). -- Trygve Thanks Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC+jd9mPuec2Dcv/8RAvvqAJ0SakMd63DkG4af2d3Fut2eY4oY7wCfT2r3 d2Pwke9cRcBmk17UIJRYEcE= =QDEX -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPCHANGELOG-70) The Subversion parser of the maven-changelog-plugin chokes on spaces in usernames.
The Subversion parser of the maven-changelog-plugin chokes on spaces in usernames. -- Key: MPCHANGELOG-70 URL: http://jira.codehaus.org/browse/MPCHANGELOG-70 Project: maven-changelog-plugin Type: Bug Versions: 1.8.2 Reporter: Henning Schmiedehausen Attachments: patch We use client certificates for authentication to the web server which holds our SVN repository. This results in the changelog messages containing the CN field of the certificate; in my case e.g. it is Henning Schmiedehausen. Subversion now produces log files like this: r237 | Henning Schmiedehausen | 2005-08-10 13:02:39 +0200 (Wed, 10 Aug 2005) | 3 lines and the changelog report is empty. The reason for this is a bad regular expression in the SvnLogParser which does not expect user names to contain blanks. The attached patch fixes this by using a greedy RE. Changelog now works for me again. Please consider this patch to be part of the (not yet released?!?) 1.8.2 or 1.8.3 release. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPCHANGELOG-70) The Subversion parser of the maven-changelog-plugin chokes on spaces in usernames.
[ http://jira.codehaus.org/browse/MPCHANGELOG-70?page=all ] Henning Schmiedehausen updated MPCHANGELOG-70: -- Attachment: patch patch vs. changelog-plugin 1.8.2 to fix the space in usernames issue. The Subversion parser of the maven-changelog-plugin chokes on spaces in usernames. -- Key: MPCHANGELOG-70 URL: http://jira.codehaus.org/browse/MPCHANGELOG-70 Project: maven-changelog-plugin Type: Bug Versions: 1.8.2 Reporter: Henning Schmiedehausen Attachments: patch We use client certificates for authentication to the web server which holds our SVN repository. This results in the changelog messages containing the CN field of the certificate; in my case e.g. it is Henning Schmiedehausen. Subversion now produces log files like this: r237 | Henning Schmiedehausen | 2005-08-10 13:02:39 +0200 (Wed, 10 Aug 2005) | 3 lines and the changelog report is empty. The reason for this is a bad regular expression in the SvnLogParser which does not expect user names to contain blanks. The attached patch fixes this by using a greedy RE. Changelog now works for me again. Please consider this patch to be part of the (not yet released?!?) 1.8.2 or 1.8.3 release. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [me] Setting up the project in my IDE
On Wed, Aug 10, 2005 at 07:21:01PM +0200, Joerg Hohwiller wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Trygve Laugstøl wrote: On Wed, Aug 10, 2005 at 06:49:40PM +0200, Joerg Hohwiller wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I got a little lost in jakarta-commons since my getting involved? thread, but finally I checked out the complete m2 thing. You tailered your components quite small - which (usually) leads to a gread design. Anyways I am little frustrated setting all this up in my JAVA IDE (eclipse). I tried the according plugin to generate the IDE config but did not succeed since the toplevel POM seems to be broken. Broken how? Not all of the modules are in the default modules collection so you might have to go into some sub directories to be able to generate the project files for all Maven 2 artifacts. [EMAIL PROTECTED]:~/projects/maven2$ m2 eclipse:eclipse [snip] So I need a toplevel POM that is NOT broken. You need to use the latest Maven 2 from trunk to be able to build Maven 2. Read up on how to build Maven 2 here[1]. [1]: http://maven.apache.org/maven2/building.html Do you have any suggestions (or maybe a developers manual :) ) to make my start a little easier? I added some how to develop Maven 2 earlier today, but as the site it not deployed yet you'll have to read it from the Subversion repository[1]. Not that that make it any harder to read, it's APT after all ;) As this is only a small start any contributions or just plain notes you're takin while getting into Maven 2 development would be appreciated. [1]: https://svn.apache.org/repos/asf/maven/components/trunk/maven-site/src/site/apt/developers/development-guide.apt Thanks. But its more about general support and svn usage. I will contribute something if I am through with this (and its not the setup every single subproject in eclipse by hand solution). Just give me some pointers to what you need more information on and I'll try to write up something. -- Trygve signature.asc Description: Digital signature
Re: [me] Setting up the project in my IDE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Trygve, So I need a toplevel POM that is NOT broken. You need to use the latest Maven 2 from trunk to be able to build Maven 2. Read up on how to build Maven 2 here[1]. [1]: http://maven.apache.org/maven2/building.html I DO use the latest! [EMAIL PROTECTED]:~/projects/maven2$ cat .svn/entries | grep url url=http://svn.apache.org/repos/asf/maven/components/trunk; [EMAIL PROTECTED]:~/projects/maven2$ svn update Revision 231289. [EMAIL PROTECTED]:~/projects/maven2$ m2 eclipse:eclipse [INFO] - [INFO] BUILD FAILURE [INFO] - [INFO] Reason: Failed to parse model from file '/home/joerg/projects/maven2/pom.xml'. Error: 'TEXT must be immediately followed by END_TAG and not START_TAG (position: START_TAG seen ...snapshotRepository\n id... @121:11) ' [INFO] - [INFO] Total time: 1 second [INFO] Finished at: Wed Aug 10 20:24:44 CEST 2005 [INFO] Final Memory: 1M/2M [INFO] - Regards Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC+kbImPuec2Dcv/8RAga6AJ9Oq8x6zdArrRDkihPBEZEJZauAUACfaxtO cRV2T5cCHaWugHIaGczZwp4= =EyQv -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [me] Setting up the project in my IDE
On Wed, Aug 10, 2005 at 08:26:16PM +0200, Joerg Hohwiller wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Trygve, So I need a toplevel POM that is NOT broken. You need to use the latest Maven 2 from trunk to be able to build Maven 2. Read up on how to build Maven 2 here[1]. [1]: http://maven.apache.org/maven2/building.html I DO use the latest! [snip] Pasting lots of output is not the most effective way of getting help. Make sure that the version you installed is the one that you are actually using, look in PATH and make sure that M2_HOME points to the right location. Verify that are running the correct version by running $ m2 -version Mine outputs Maven version: 2.0-beta-1-SNAPSHOT. -- Trygve signature.asc Description: Digital signature
[jira] Closed: (MNG-689) build fails on compiler warning
[ http://jira.codehaus.org/browse/MNG-689?page=all ] Carlos Sanchez closed MNG-689: -- Resolution: Fixed After bootstrapping it worked. Seems that I hadn't installed the plugin correctly build fails on compiler warning --- Key: MNG-689 URL: http://jira.codehaus.org/browse/MNG-689 Project: Maven 2 Type: Bug Components: maven-plugins Versions: 2.0-beta-1, 2.0-alpha-3 Environment: Linux u-235 2.6.10-gentoo-r4 #1 SMP Mon Jan 10 14:53:56 EST 2005 i686 AMD Athlon(tm) MP 2400+ AuthenticAMD GNU/Linux java version 1.4.2_08 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03) Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode) Reporter: Andrew Moore Assignee: Kenney Westerhof Fix For: 2.0-beta-1 Attachments: spring-support.zip I'm attempting to compile a class that contains the now reserved word 'assert' as a identifier. This compiles fine, with the requisite warnings, outside of m2. Under m2, the compiler:compile goal produces the warnings and actually compiles the class BUT the build fails [Listing 1]. I would expect the build to pass in this case. Previously on this list I have seen it suggested that setting the source compatibility to 1.4 may fix this. In my case, setting this [Listing 2] results in no warning, no class file and a failed build [Listing 3]. Any suggestions on how I can get around this? Even if I do away with the assert, will m2 fail the build on any compiler warning? Cheers, ...andrew Listing 1 $ m2 clean:clean compiler:compile [INFO] Using local copy of plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins' from: /home/amm/.m2/repository/org/apache/maven/plugins/plugins.xml [INFO] maven-clean-plugin: resolved to version 2.0-alpha-3 from local repository [INFO] maven-compiler-plugin: resolved to version 2.0-alpha-3 from local repository [INFO] [INFO] Building distra - numpty [INFO]task-segment: [clean:clean, compiler:compile] [INFO] [INFO] [clean:clean] [INFO] Deleting directory /secure/home/amm/prj/bt3/distra/numpty/numpty/target [INFO] [compiler:compile] Compiling 1 source file to /secure/home/amm/prj/bt3/distra/numpty/numpty/target/classes [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Reason: Compilation failure [INFO] [INFO] no more tokens - could not parse error message: /secure/home/amm/prj/bt3/distra/numpty/numpty/src/main/java/Numpty.java:4: warning: as of release 1.4, assert is a keyword, and may not be used as an identifier private static String assert = Hello assert!; // should trigger compiler warning ^ no more tokens - could not parse error message: /secure/home/amm/prj/bt3/distra/numpty/numpty/src/main/java/Numpty.java:6: warning: as of release 1.4, assert is a keyword, and may not be used as an identifier System.out.println(assert); // should trigger compiler warning ^ [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Aug 03 13:08:26 EST 2005 [INFO] Final Memory: 2M/5M [INFO] Listing 2 build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId version2.0-alpha-3/version goals goal idcompile/id configuration source1.4/source /configuration /goal /goals /plugin /plugins /build Listing 3 $ m2 clean:clean compiler:compile [INFO] Using local copy of plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins' from: /home/amm/.m2/repository/org/apache/maven/plugins/plugins.xml [INFO] maven-clean-plugin: resolved to version 2.0-alpha-3 from local repository [INFO] [INFO] Building distra - numpty [INFO]task-segment: [clean:clean, compiler:compile] [INFO] [INFO] [clean:clean] [INFO] Deleting directory /secure/home/amm/prj/bt3/distra/numpty/numpty/target [INFO] [compiler:compile] Compiling 1 source file to /secure/home/amm/prj/bt3/distra/numpty/numpty/target/classes [INFO] [INFO] BUILD
svn commit: r231294 - in /maven/components/trunk: maven-core-it/it0048/ maven-core-it/it0048/src/ maven-core-it/it0048/src/main/ maven-core-it/it0048/src/main/java/ maven-core-it/it0048/src/main/java/org/ maven-core-it/it0048/src/main/java/org/apache/ ...
Author: jdcasey Date: Wed Aug 10 12:21:34 2005 New Revision: 231294 URL: http://svn.apache.org/viewcvs?rev=231294view=rev Log: Resolving: MNG-684 o Split profile injection out into its own component away from the defaults assembler o Moved code common to the defaults assembler and the profile injector into ModelUtils o Removed the profile-related method from ModelIntheritanceAssembler o added it0048 to test that profile values will override POM values. Added: maven/components/trunk/maven-core-it/it0048/ maven/components/trunk/maven-core-it/it0048/expected-results.txt (with props) maven/components/trunk/maven-core-it/it0048/goals.txt (with props) maven/components/trunk/maven-core-it/it0048/pom.xml (with props) maven/components/trunk/maven-core-it/it0048/src/ maven/components/trunk/maven-core-it/it0048/src/main/ maven/components/trunk/maven-core-it/it0048/src/main/java/ maven/components/trunk/maven-core-it/it0048/src/main/java/org/ maven/components/trunk/maven-core-it/it0048/src/main/java/org/apache/ maven/components/trunk/maven-core-it/it0048/src/main/java/org/apache/maven/ maven/components/trunk/maven-core-it/it0048/src/main/java/org/apache/maven/it0023/ maven/components/trunk/maven-core-it/it0048/src/main/java/org/apache/maven/it0023/Person.java (with props) maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/injection/DefaultProfileInjector.java (with props) maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/injection/ProfileInjector.java (with props) Modified: maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/DefaultMavenProjectBuilder.java maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/ModelUtils.java maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/inheritance/DefaultModelInheritanceAssembler.java maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/inheritance/ModelInheritanceAssembler.java maven/components/trunk/maven-project/src/main/resources/META-INF/plexus/components.xml Added: maven/components/trunk/maven-core-it/it0048/expected-results.txt URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-core-it/it0048/expected-results.txt?rev=231294view=auto == --- maven/components/trunk/maven-core-it/it0048/expected-results.txt (added) +++ maven/components/trunk/maven-core-it/it0048/expected-results.txt Wed Aug 10 12:21:34 2005 @@ -0,0 +1 @@ +target/replacedPluginItem.txt Propchange: maven/components/trunk/maven-core-it/it0048/expected-results.txt -- svn:eol-style = native Propchange: maven/components/trunk/maven-core-it/it0048/expected-results.txt -- svn:keywords = Author Date Id Revision Added: maven/components/trunk/maven-core-it/it0048/goals.txt URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-core-it/it0048/goals.txt?rev=231294view=auto == --- maven/components/trunk/maven-core-it/it0048/goals.txt (added) +++ maven/components/trunk/maven-core-it/it0048/goals.txt Wed Aug 10 12:21:34 2005 @@ -0,0 +1 @@ +core-it:touch \ No newline at end of file Propchange: maven/components/trunk/maven-core-it/it0048/goals.txt -- svn:eol-style = native Propchange: maven/components/trunk/maven-core-it/it0048/goals.txt -- svn:keywords = Author Date Id Revision Added: maven/components/trunk/maven-core-it/it0048/pom.xml URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-core-it/it0048/pom.xml?rev=231294view=auto == --- maven/components/trunk/maven-core-it/it0048/pom.xml (added) +++ maven/components/trunk/maven-core-it/it0048/pom.xml Wed Aug 10 12:21:34 2005 @@ -0,0 +1,53 @@ +project + modelVersion4.0.0/modelVersion + groupIdorg.apache.maven/groupId + artifactIdmaven-it0023/artifactId + version1.0-SNAPSHOT/version + + build +plugins + plugin +groupIdorg.apache.maven.plugins/groupId +artifactIdmaven-core-it-plugin/artifactId +version1.0-SNAPSHOT/version +configuration + pluginItempluginItem.txt/pluginItem +/configuration + /plugin +/plugins + /build + pluginRepositories +pluginRepository + idsnapshots/id + nameMaven Central Plugins Development Repository/name + urlhttp://snapshots.maven.codehaus.org/maven2/plugins/url +/pluginRepository + /pluginRepositories + + profiles +
[jira] Closed: (MNG-684) profiles not correctly merged
[ http://jira.codehaus.org/browse/MNG-684?page=all ] John Casey closed MNG-684: -- Resolution: Fixed split profile injection into a separate component, and moved code common to this and the inheritance assembler into ModelUtils. profiles not correctly merged - Key: MNG-684 URL: http://jira.codehaus.org/browse/MNG-684 Project: Maven 2 Type: Bug Components: maven-project Reporter: Brett Porter Assignee: John Casey Fix For: 2.0-beta-1 the profiles in the model are not merged correctly. It uses the inheritence assembler, but uses the profile as the parent and the end model as the child. This means that anything in the profile that overrides something in the child does not get applied. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r231297 - /maven/maven-1/plugins/trunk/test/xdocs/properties.xml
Author: carlos Date: Wed Aug 10 12:34:15 2005 New Revision: 231297 URL: http://svn.apache.org/viewcvs?rev=231297view=rev Log: Added required maven version for maven.junit.forkmode Modified: maven/maven-1/plugins/trunk/test/xdocs/properties.xml Modified: maven/maven-1/plugins/trunk/test/xdocs/properties.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/test/xdocs/properties.xml?rev=231297r1=231296r2=231297view=diff == --- maven/maven-1/plugins/trunk/test/xdocs/properties.xml (original) +++ maven/maven-1/plugins/trunk/test/xdocs/properties.xml Wed Aug 10 12:34:15 2005 @@ -41,6 +41,7 @@ tdmaven.junit.forkmode/td tdYes/td td +NOTE: Ignored in maven lt; 1.1. Controls how many Java Virtual Machines get created if you want to fork some tests. Possible values are perTest (the default), and once. once creates only a single Java VM for - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-483) sort out artifact attachment
[ http://jira.codehaus.org/browse/MNG-483?page=comments#action_44258 ]
John Casey commented on MNG-483:
1. Okay, I get it now...that's easy enough to handle.
2. What about having something like:
project
...
build
...
attachments
sourcetrue/source
/attachments
/build
/project
in order to turn on/off source attachments? the values in the attachments
stanza could be a free-form DOM or somesuch, with the maven-source-plugin
checking for ${project.buildAttachments}.isEnabled( source ) or
somesuch...and the inheritance assembler could do a DOM merge with local-wins
for the child to override the value in the super-pom. WDYT?
3. I'd agree that maybe the super-pom should have a profile inline that
specifies the source plugin, and is activated by -DsourceArtifact=true or
somesuch. Then, we get away from checking for -SNAPSHOT, and only releases and
very explicit usages would activate that profile.
4. will do. Is someone already working on this part (or on the assembly mojo's
lack of execution in the package phase)?
sort out artifact attachment
Key: MNG-483
URL: http://jira.codehaus.org/browse/MNG-483
Project: Maven 2
Type: Bug
Reporter: Brett Porter
Assignee: John Casey
Priority: Blocker
Fix For: 2.0-beta-1
currently, there is an attachArtifact call inside the plugin building the
attachment. It imposes a m-a and m-p dependency, as well as an
artifactFactory requirement to be able to construct the artifact to attach.
sort out
- if there is an easier way to achieve this
- how to retain the default source binding, but also how to turn it off
- how to make the source binding happen only on release (bear in mind
people may not be using the release plugin... a profile was the original idea)
- how to bind assembly similarly
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Wed Aug 10 19:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050810.193000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050810.193000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-479) unable to override the default central repository
[ http://jira.codehaus.org/browse/MNG-479?page=comments#action_44260 ] John Casey commented on MNG-479: I've been rethinking this one a little bit, and I'm not sure we should allow redefinition of repositories. The problem is the intention of doing this: what you're really trying to achieve is isolation from the public repositories, right? Otherwise, why redefine the 'central' repository? So, if you're doing that, you really want your overridden repository to be used by everything in your transitive dependency graph. However, since POMs must have the ability to state their own build environment - including the repositories used to track down their dependencies - they must resolve using a repository list independent of the project being built...which means that the overridden 'central' repository is reverted to the one specified in the super-pom for transitive deps. This is what Kenney is describing above. I believe what a user would be actually trying to achieve is mirroring of the central repository in this case. Currently, this is possible using the settings.xml, which can also be configured at the global installation level. Not ideal if each developer workstation has a separate install of maven, but maybe ok as a first step... I think we should actively warn if a user tries to override pre-existing repositories, and drop the override. We can tell them to use the mirror functionality instead. unable to override the default central repository - Key: MNG-479 URL: http://jira.codehaus.org/browse/MNG-479 Project: Maven 2 Type: Bug Components: maven-core Versions: 2.0-alpha-2 Environment: WinXP Reporter: Edwin Punzalan Assignee: John Casey Priority: Blocker Fix For: 2.0-beta-1 Attachments: DefaultModelInheritanceAssembler-with-updated-JUnitTest.diff, DefaultModelInheritanceAssembler.diff, it0042.tgz Adding to my pom.xml: repositories repository idcentral/id namecustom repository/name urlhttp://maven.company.com/maven2/url /repository /repositories did not override the central repository but instead uses the above configured repository as backup/mirror. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r231304 - /maven/maven-1/plugins/trunk/test/project.xml
Author: carlos Date: Wed Aug 10 12:59:00 2005 New Revision: 231304 URL: http://svn.apache.org/viewcvs?rev=231304view=rev Log: Added myself as developer to be listed in Activity by Developer report Modified: maven/maven-1/plugins/trunk/test/project.xml Modified: maven/maven-1/plugins/trunk/test/project.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/test/project.xml?rev=231304r1=231303r2=231304view=diff == --- maven/maven-1/plugins/trunk/test/project.xml (original) +++ maven/maven-1/plugins/trunk/test/project.xml Wed Aug 10 12:59:00 2005 @@ -70,6 +70,14 @@ roleJava Developer/role /roles /developer +developer + nameCarlos Sanchez/name + idcarlos/id + email[EMAIL PROTECTED]/email + roles +roleJava Developer/role + /roles +/developer /developers dependencies dependency - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPCHECKSTYLE-38) RSS file has incorrect dir paths generated for use in Maven multiproject site.
RSS file has incorrect dir paths generated for use in Maven multiproject site. -- Key: MPCHECKSTYLE-38 URL: http://jira.codehaus.org/browse/MPCHECKSTYLE-38 Project: maven-checkstyle-plugin Type: Bug Versions: 2.5 Environment: Maven 1.1 Reporter: Jeff Jensen The checkstyle RSS file does not work in a multiproject site, as the links in it do not consider the actual multiproject dir structure. For example, this is the actual path generated for one entry: file:/D020-8m-1228157/sites/healthmatchbatch/index.html/checkstyle-report.html#us/state/vantage/hm/ar/entity/Account.java and it should be: file:/D020-8m-1228157/sites/healthmatchmultiproject/multiproject/healthmatchbatch/checkstyle-report.html#us_state_vantage_hm_ar_entity_Account_java -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-477) Please upload DWR 1.0-rc3 to the global Maven repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-477?page=all ] Carlos Sanchez closed MAVENUPLOAD-477: -- Assign To: Carlos Sanchez Resolution: Fixed Please upload DWR 1.0-rc3 to the global Maven repo -- Key: MAVENUPLOAD-477 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-477 Project: maven-upload-requests Type: Task Reporter: Julien Dubois Assignee: Carlos Sanchez DWR is already in the global Maven repository (see MAVENUPLOAD-433), this is a request for uploading a new version. I'm doing this, of course, with the agreement of Joe Walker, who is the author of DWR. Regards, Julien Dubois. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPPDF-43) sub-/superscripts do not work
[ http://jira.codehaus.org/browse/MPPDF-43?page=all ] Arnaud Heritier updated MPPDF-43: - Fix Version: 2.3.1 sub-/superscripts do not work - Key: MPPDF-43 URL: http://jira.codehaus.org/browse/MPPDF-43 Project: maven-pdf-plugin Type: Bug Versions: 2.3 Environment: any Reporter: Lukas Theussl Assignee: Arnaud Heritier Priority: Minor Fix For: 2.3.1 Attachments: fo-body.patch Original Estimate: 5 minutes Remaining: 5 minutes A patch for fo-body.xslt that makes sub-/superscripts (sub/sub, sup/sup) work: I just replaced the baseline-shift property by vertical-align. According to the fop implementations page ( http://xml.apache.org/fop/compliance.html ), the vertical-align property is just a shorthand for baseline-shift, however, vertical-align works while baseline-shift doesn't ... (I got that from a recent thread on the fop-users list: http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/200508.mbox/[EMAIL PROTECTED] ) The patch also reinserts some commented part that should work now after MPPDF-39 is fixed. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-470) Upload glazedlists On ibiblio / give URL if already there
[ http://jira.codehaus.org/browse/MAVENUPLOAD-470?page=all ] Carlos Sanchez closed MAVENUPLOAD-470: -- Assign To: Carlos Sanchez Resolution: Fixed Upload glazedlists On ibiblio / give URL if already there - Key: MAVENUPLOAD-470 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-470 Project: maven-upload-requests Type: Task Reporter: Martin Skopp Assignee: Carlos Sanchez http://trackdemo.riege.com/glazedlists-0.9.7-bundle.jar https://glazedlists.dev.java.net/ https://glazedlists.dev.java.net/ Hi Maven-Team, I haven't found glazedlists on ibiblio (btw: it would be superb if one could download/search a list of ALL jar file on ibiblio!) so I hope you guys put it on. It's a pretty cool project for dynamically filtered and sorted tables. Thanks Martin -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-478) Please upload extremecomponents to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-478?page=all ] Carlos Sanchez closed MAVENUPLOAD-478: -- Assign To: Carlos Sanchez Resolution: Fixed Please upload extremecomponents to ibiblio -- Key: MAVENUPLOAD-478 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-478 Project: maven-upload-requests Type: Improvement Reporter: Todd Huss Assignee: Carlos Sanchez I've created the project bundle for: http://extremecomponents.org/extremesite/welcome.jsp -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPCHECKSTYLE-35) Add option to break report into multiple files for large results
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-35?page=comments#action_44262 ] Carlos Sanchez commented on MPCHECKSTYLE-35: If you have such a huge report you shouldn't be using checkstyle or you should start with a smaller set of rules Add option to break report into multiple files for large results Key: MPCHECKSTYLE-35 URL: http://jira.codehaus.org/browse/MPCHECKSTYLE-35 Project: maven-checkstyle-plugin Type: Wish Reporter: Jeff Jensen For large projects, the load of the HTML report is unwieldy with the rule violations. This particularly occurs when setting up on existing codebases – many rule violations. Not only does it take a long time to load, it is overwhelming for team members to wade through this large page. This does not help the effort of adoption. Also, the current workaround is to greatly reduce the rule set to make smaller results. But that is not optimal and prolongs the problem. Even with a reduced ruleset, our checkstyle-report.html file is over 13M. Suggested organization: - The main page has the current “Summary” and “Files” sections. Each file link loads a separate page, vs linking to a ref on the same page. - Have an “All on one page” link that provides as is today (handy for printing smaller lists if needed, and also for audits). - If needed, have a config property that states which way to generate the report – all on one page or separate pages - that defaults to all on one page so it maintains backwards compatibility. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [me] Setting up the project in my IDE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Trygve Laugstøl wrote: On Wed, Aug 10, 2005 at 08:26:16PM +0200, Joerg Hohwiller wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Trygve, So I need a toplevel POM that is NOT broken. You need to use the latest Maven 2 from trunk to be able to build Maven 2. Read up on how to build Maven 2 here[1]. [1]: http://maven.apache.org/maven2/building.html I DO use the latest! [snip] Pasting lots of output is not the most effective way of getting help. I did not mean to spam you with my console output. I just thought the few lines would say very precises on which SVN_ROOT and revision I am working and that I still have the problem with the latest head revision. Make sure that the version you installed is the one that you are actually using, look in PATH and make sure that M2_HOME points to the right location. Verify that are running the correct version by running $ m2 -version Mine outputs Maven version: 2.0-beta-1-SNAPSHOT. Yep, you gessed it. The problem is that I did not read everything completely. Sorry for that. So since I have beta-1 instead of alpha-3 it works fine now. -- Trygve Thank you Jörg p.s.: In case anyone cares: There is a very clear suggestion for commandline arguments from GNU that is used by most linux and other programms. So for full word triggers it should be -- as prefix. This allows combining single letter options without clashing the full-wort options. So -h or --help. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC+miSmPuec2Dcv/8RApGHAKCJJDf5Che0hncv7XEP8GOvvrGFDgCfWAY0 lyHfdo47Yf/CJRGTgYmy9ZI= =p8Mm -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1660) DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.
DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal. --- Key: MAVEN-1660 URL: http://jira.codehaus.org/browse/MAVEN-1660 Project: Maven Type: Bug Components: core Versions: 1.1-beta-1 Reporter: Pascal Larin Priority: Minor Since revision 179556 of src/java/org/apache/maven/verifier/DependencyVerifier.java, the satisfyDependencies() method check if an artifact has already been resolved. It changes the behavior from version 1.0. For example, if you call maven with goals multiproject:clean and multiproject:deploy with artifact versions set to snaphot, maven doesn't resolve the dependencies for the multiproject:deploy because it has been already done for the multiproject:clean. I know that a multiproject:clean should not resolve the project dependencies but it can probably cause problems in other 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPDF-8) add support for external imaging libraries like jimi and jai
[ http://jira.codehaus.org/browse/MPPDF-8?page=comments#action_44263 ]
Arnaud Heritier commented on MPPDF-8:
-
I prefered something standard like Lukas proposed. But what about jar
releases ?
I'm not in favor to store in a repository a jar without a release number.
Another idea is to get Jimi or Jai in the project dependency. It's less
restricting in the plugin but it's more annoying for the project because in m1
we can't separate build and runtime dependencies.
Any thought ?
add support for external imaging libraries like jimi and jai
Key: MPPDF-8
URL: http://jira.codehaus.org/browse/MPPDF-8
Project: maven-pdf-plugin
Type: Improvement
Environment: maven-1.0rc2, maven-pdf-plugin 2.1
Reporter: Fábio Franco Uechi
Assignee: Arnaud Heritier
Priority: Minor
Problems with the insertion of PNG image files.
JIMI/JAI libraries needed for handling them.
How I've solved it:
I created 3 new properties in my project.properties. Each of
them just pointing to its respective library location.
maven.pdf.jimi.jar=${maven.repo.local}/jimi/jars/jimi-1.0.jar
maven.pdf.jaicore.jar=${maven.repo.local}/jai/jars/jai_core-1.1.2.jar
maven.pdf.jaicodec.jar=${maven.repo.local}/jai/jars/jai_codec-1.1.2.jar
After that I've inserted the following lines to the plugin.jelly
script file:
pathelement
location=${pom.getPluginContext('maven-pdf-plugin').getVariable('maven.pdf.jimi.jar')}/
pathelement
location=${pom.getPluginContext('maven-pdf-plugin').getVariable('maven.pdf.jaicore.jar')}/
pathelement
location=${pom.getPluginContext('maven-pdf-plugin').getVariable('maven.pdf.jaicodec.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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPPDF-31) Cannot insert logo image to PDF
[ http://jira.codehaus.org/browse/MPPDF-31?page=all ]
Arnaud Heritier updated MPPDF-31:
-
Description:
Fragment of text of project.xml:
?xml version=1.0 encoding=UTF-8?
project
...
organization
logo/images/XXX.gif/logo
/organization
logo/images/YYY.gif/logo
...
Fragment of text of maven.xml:
postGoal name=site
attainGoal name=pdf/
/postGoal
In compile time the error is generated.
...
[java] [ERROR] Error while creating area : Error while recovering Image
Informations (file:/images/YYY.gif) : /images/YYY.gif (No such file or
directory)
...
As I understand the problem is connected with following code:
j:if test=not ${maven.pdf.projectLogo.startsWith('http://')}
maven:makeAbsolutePath
var=maven.pdf.projectLogo
basedir=${maven.xdoc.src}
path=${maven.pdf.projectLogo}
trim=true/
/j:if
logo/images/YYY.gif/logo includes the path which is absolute. And so the
prefix ${maven.xdoc.src}is not concatenated to the path. And so the file
YYY.gif cannot be found.
I have simplified code and YYY.gif was found:
j:if test=${not maven.pdf.companyLogo.startsWith('http://')}
j:set
var=maven.pdf.companyLogo${maven.xdoc.src}${maven.pdf.companyLogo}/j:set
/j:if
I think this problem can be resolved by more general way.
was:
Fragment of text of project.xml:
?xml version=1.0 encoding=UTF-8?
project
...
organization
logo/images/XXX.gif/logo
/organization
logo/images/YYY.gif/logo
...
Fragment of text of maven.xml:
postGoal name=site
attainGoal name=pdf/
/postGoal
In compile time the error is generated.
...
[java] [ERROR] Error while creating area : Error while recovering Image
Informations (file:/images/YYY.gif) : /images/YYY.gif (No such file or
directory)
...
As I understand the problem is connected with following code:
j:if test=not ${maven.pdf.projectLogo.startsWith('http://')}
maven:makeAbsolutePath
var=maven.pdf.projectLogo
basedir=${maven.xdoc.src}
path=${maven.pdf.projectLogo}
trim=true/
/j:if
logo/images/YYY.gif/logo includes the path which is absolute. And so the
prefix ${maven.xdoc.src}is not concatenated to the path. And so the file
YYY.gif cannot be found.
I have simplified code and YYY.gif was found:
j:if test=${not maven.pdf.companyLogo.startsWith('http://')}
j:set
var=maven.pdf.companyLogo${maven.xdoc.src}${maven.pdf.companyLogo}/j:set
/j:if
I think this problem can be resolved by more general way.
Fix Version: 2.3.1
Environment:
Windows XP professional version 2002 and
Linux Red Hat / Maven 1.0.2 / maven-pdf-plugin-2.2.1
was:
Windows XP professional version 2002 and
Linux Red Hat / Maven 1.0.2 / maven-pdf-plugin-2.2.1
Cannot insert logo image to PDF
---
Key: MPPDF-31
URL: http://jira.codehaus.org/browse/MPPDF-31
Project: maven-pdf-plugin
Type: Bug
Versions: 2.2
Environment: Windows XP professional version 2002 and
Linux Red Hat / Maven 1.0.2 / maven-pdf-plugin-2.2.1
Reporter: Oleg F. Vlasenko
Assignee: Arnaud Heritier
Fix For: 2.3.1
Attachments: plugin.jelly-logos.patch, project.properties.patch
Fragment of text of project.xml:
?xml version=1.0 encoding=UTF-8?
project
...
organization
logo/images/XXX.gif/logo
/organization
logo/images/YYY.gif/logo
...
Fragment of text of maven.xml:
postGoal name=site
attainGoal name=pdf/
/postGoal
In compile time the error is generated.
...
[java] [ERROR] Error while creating area : Error while recovering Image
Informations (file:/images/YYY.gif) : /images/YYY.gif (No such file or
directory)
...
As I understand the problem is connected with following code:
j:if test=not ${maven.pdf.projectLogo.startsWith('http://')}
maven:makeAbsolutePath
var=maven.pdf.projectLogo
basedir=${maven.xdoc.src}
path=${maven.pdf.projectLogo}
trim=true/
/j:if
logo/images/YYY.gif/logo includes the path which is absolute. And so the
prefix ${maven.xdoc.src}is not concatenated to the path. And so the file
YYY.gif cannot be found.
I have simplified code and YYY.gif was found:
j:if test=${not maven.pdf.companyLogo.startsWith('http://')}
j:set
var=maven.pdf.companyLogo${maven.xdoc.src}${maven.pdf.companyLogo}/j:set
/j:if
I think this problem can be resolved by more general way.
--
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: (MPPDF-42) error when logo locations are not set
[ http://jira.codehaus.org/browse/MPPDF-42?page=all ] Arnaud Heritier updated MPPDF-42: - Fix Version: 2.3.1 error when logo locations are not set - Key: MPPDF-42 URL: http://jira.codehaus.org/browse/MPPDF-42 Project: maven-pdf-plugin Type: Bug Versions: 2.3 Environment: any Reporter: Lukas Theussl Assignee: Arnaud Heritier Priority: Minor Fix For: 2.3.1 Attachments: fo-cover.xslt.patch Original Estimate: 5 minutes Remaining: 5 minutes The pdf goal spits some unnecessary error messages when maven.pdf.projectLogo or maven.pdf.companyLogo are not set (or are set to an empty string). This patch only includes the logos on the pdf cover if their locations are actually set. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPPDF-22) Allow copy and paste from pdf to text editor
[ http://jira.codehaus.org/browse/MPPDF-22?page=all ] Arnaud Heritier updated MPPDF-22: - Description: Actually, we cant copy text from a PDF section and paste it in a text editor. But we can do it for title section or table of contents... Example: copy this title from the generated PDF: Table of Contents paste in a text editor: Table of Contents Correct copy this section from the generated PDF: No current items paste in a text editor: .. In hexa it should be: h: 2E 2E 2E 2E 20 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E ; ... 0010h: 2E 2E 2E 20 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E ; ... Thus incorrect Maybe a font problem... was: Actually, we cant copy text from a PDF section and paste it in a text editor. But we can do it for title section or table of contents... Example: copy this title from the generated PDF: Table of Contents paste in a text editor: Table of Contents Correct copy this section from the generated PDF: No current items paste in a text editor: .. In hexa it should be: h: 2E 2E 2E 2E 20 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E ; ... 0010h: 2E 2E 2E 20 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E ; ... Thus incorrect Maybe a font problem... Fix Version: 2.3.1 Allow copy and paste from pdf to text editor Key: MPPDF-22 URL: http://jira.codehaus.org/browse/MPPDF-22 Project: maven-pdf-plugin Type: Bug Versions: 2.3 Environment: Maven xdoc 1.9 Reporter: Vincent Siveton Assignee: Arnaud Heritier Fix For: 2.3.1 Attachments: ttf-gara.xml, ttf-garabd.xml, ttf-garait.xml Actually, we cant copy text from a PDF section and paste it in a text editor. But we can do it for title section or table of contents... Example: copy this title from the generated PDF: Table of Contents paste in a text editor: Table of Contents Correct copy this section from the generated PDF: No current items paste in a text editor: .. In hexa it should be: h: 2E 2E 2E 2E 20 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E ; ... 0010h: 2E 2E 2E 20 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E 2E ; ... Thus incorrect Maybe a font problem... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPPDF-41) suppress verbose output by default
[ http://jira.codehaus.org/browse/MPPDF-41?page=all ]
Arnaud Heritier updated MPPDF-41:
-
Fix Version: 2.3.1
suppress verbose output by default
--
Key: MPPDF-41
URL: http://jira.codehaus.org/browse/MPPDF-41
Project: maven-pdf-plugin
Type: Bug
Versions: 2.3
Environment: any
Reporter: Lukas Theussl
Assignee: Arnaud Heritier
Priority: Minor
Fix For: 2.3.1
Attachments: plugin.jelly.patch
Original Estimate: 5 minutes
Remaining: 5 minutes
The screen output of the current pdf goal is always verbose, regardless of
the ${maven.pdf.debug} variable because the default messagelevel for the fop
task is already 'debug'. The attached patch sets it to 'error' by default.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPDF-19) Cannot build the pdf documentation for maven 1.1
[ http://jira.codehaus.org/browse/MPPDF-19?page=comments#action_44264 ] Arnaud Heritier commented on MPPDF-19: -- No, I don't think this the same problem. The one I found is due to duplicated entries in navigation.xml. Your one is certainly due to the fact you use fig1 several times. It's certainly 2 problems with the same error. Cannot build the pdf documentation for maven 1.1 Key: MPPDF-19 URL: http://jira.codehaus.org/browse/MPPDF-19 Project: maven-pdf-plugin Type: Bug Versions: 2.3 Reporter: Arnaud Heritier Assignee: Arnaud Heritier Error : [java] [INFO] area contents overflows area in line [java] [INFO] area contents overflows area in line [java] [INFO] area contents overflows area in line [java] [INFO] area contents overflows area in line [java] [INFO] [115] [java] [INFO] [116] [java] [ERROR] file:/D:/Work/Dev/maven-1.1/target/pdf/project.fo:18645:87 The id #org.apache.maven.plugin.GoalToJellyScriptHousingMapper.methodsN27024C already exists in this document BUILD FAILED File.. D:\Work\Data\maven\cache\maven-pdf-plugin-2.3-SNAPSHOT\plugin.jelly Element... java Line.. 263 Column 94 Java returned: 2 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPPDF-33) contents overflows area message
[ http://jira.codehaus.org/browse/MPPDF-33?page=all ]
Arnaud Heritier updated MPPDF-33:
-
Description:
Hello
--
The problem:
--
When running pdf:pdf in debug mode, the informational message indicates that
area content overflows:
[java] [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2
Parser
[java] [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2
Parser
[java] [INFO] FOP 0.20.5
[java] [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2
Parser
[java] [INFO] building formatting object tree
[java] [INFO] setting up fonts
[java] [INFO] [1]
[java] [INFO] [2]
[java] [INFO] [1]
[java] [INFO] area contents overflows area in line
[java] [INFO] area contents overflows area in line
[java] [INFO] area contents overflows area in line
[java] [INFO] area contents overflows area in line
[java] [INFO] area contents overflows area in line
[java] [INFO] area contents overflows area in line
[java] [INFO] [2] (blank)
[java] [INFO] [1]
[java] [INFO] area contents overflows area in line
[java] [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2
Parser
[java] [INFO] [2]
[java] [INFO] area contents overflows area in line
[java] [INFO] [3]
[java] [INFO] [4]
[java] [INFO] area contents overflows area in line
[java] [INFO] [5]
[java] [INFO] [6]
[java] [INFO] area contents overflows area in line
[java] [INFO] [7]
[java] [INFO] area contents overflows area in line
[java] [INFO] [8]
[java] [INFO] area contents overflows area in line
[java] [INFO] [9]
[java] [INFO] area contents overflows area in line
[java] [INFO] [10]
[java] [INFO] area contents overflows area in line
[java] [INFO] [11]
[java] [INFO] area contents overflows area in line
[java] [INFO] [12]
[java] [INFO] area contents overflows area in line
[java] [INFO] [13]
[java] [INFO] area contents overflows area in line
[java] [INFO] [14]
[java] [INFO] [15]
[java] [INFO] area contents overflows area in line
[java] [INFO] Parsing of document complete, stopping renderer
[copy] Copying 1 file to
I:\MAVENLOCALREPO\maasintern\NYRETEST\target\docs
[copy] [VERBOSE] Copying
I:\MAVENLOCALREPO\maasintern\NYRETEST\target\pdf\nyretest.pdf to
I:\MAVENLOCALREPO\maasintern\NYRETEST\target\docs\nyretest.pdf
attaining goal build:end
--
Well, one way to to prevent these messages is ...
--
in fo-body.xslt
xsl:template name=body-chapter-heading
!-- NYRE - 20050228 --
!-- NYRE specified indents explicitly to avoid overflow messages --
!-- fo:list-block provisional-distance-between-starts={$leftMargin +
$gutter}in provisional-label-separation={$gutter}in --
fo:list-block
fo:list-item
fo:list-item-label start-indent={0 -$leftMargin}in
end-indent={$bodyWidth + $gutter}in
fo:block xsl:use-attribute-sets=outdented.number.style
xsl:value-of select=normalize-space($chapterNumber)/
/fo:block
/fo:list-item-label
fo:list-item-body start-indent=0in end-indent={$rightMargin}in
fo:block xsl:use-attribute-sets=chapter.title
xsl:value-of select=normalize-space($chapter)/
/fo:block
/fo:list-item-body
/fo:list-item
/fo:list-block
/fo:block
Or in the file fo-toc.xslt
in xsl:template name=fo-toc
...
fo:table table-layout=fixed
!-- NYRE - 20050228 adjustments for --
!-- NYRE increased size to avoid overflow messages --
fo:table-column column-width=0.45in/
fo:table-column column-width=0.4in/
fo:table-column column-width=0.4in/
fo:table-column column-width={$maxBodyWidth - 1.25}in/
fo:table-body
xsl:apply-templates mode=toc/
/fo:table-body
/fo:table
was:
Hello
--
The problem:
--
When running pdf:pdf in debug mode, the informational message indicates that
area content overflows:
[java] [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2
Parser
[java] [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2
Parser
[java] [INFO] FOP 0.20.5
[java] [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2
Parser
[java] [INFO] building formatting object tree
[java] [INFO] setting up fonts
[java] [INFO] [1]
[java] [INFO] [2]
[java] [INFO] [1]
[java] [INFO] area contents overflows area in line
[java] [INFO] area contents overflows area in line
[java] [INFO] area contents overflows area in line
[java] [INFO] area contents
[jira] Created: (MPSITE-35) ftpdeploy doesn't work properly
ftpdeploy doesn't work properly --- Key: MPSITE-35 URL: http://jira.codehaus.org/browse/MPSITE-35 Project: maven-site-plugin Type: Bug Components: plugin Versions: 1.6.1 Environment: maven-site-plugin-1.6.1, Maven 1.0.2, Windows XP, Java 5.0 Reporter: Steffen Krause 1. configured the remote siteAdress (project.xml) 2. configured the remote siteDirectory (project.xml) 3. configured deploy method (ftp), username and password (project.properties) 4. called goal site:deploy Result: BUILD FAILED File.. C:\Documents and Settings\kimba\.maven\cache\maven-site-plugin-1.6.1\plugin.jelly Element... taskdef Line.. 130 Column 6 taskdef class org.apache.tools.ant.taskdefs.optional.net.FTP cannot be found 5. tried calling goal site:ftpdeploy directly Result: BUILD FAILED File.. C:\Documents and Settings\kimba\.maven\cache\maven-site-plugin-1.6.1\plugin.jelly Element... taskdef Line.. 130 Column 6 taskdef class org.apache.tools.ant.taskdefs.optional.net.FTP cannot be found -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPPDF-26) document the need for different files for different items
[ http://jira.codehaus.org/browse/MPPDF-26?page=all ] Arnaud Heritier updated MPPDF-26: - Fix Version: 2.3.1 Environment: document the need for different files for different items - Key: MPPDF-26 URL: http://jira.codehaus.org/browse/MPPDF-26 Project: maven-pdf-plugin Type: Task Versions: 2.2 Reporter: Rick Wood Assignee: Arnaud Heritier Fix For: 2.3.1 Due to several problems, it is actually impossible to reference the same file in different items in navigation.xml. You must define another navigation file which you'll use only with the PDF plug-in. This navigation cannot define several items with the same href. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPPDF-35) Standardize copyright notices
[ http://jira.codehaus.org/browse/MPPDF-35?page=all ] Arnaud Heritier updated MPPDF-35: - Description: It should be nice to standardize the copyright between the different generated files (HTML/PDF) Actually, we have: * © 2001-2005, Apache Software Foundation (HTML - XDOC, lets see http://maven.apache.org) * © 2001 APACHE SOFTWARE FOUNDATION • ALL RIGHTS RESERVED (PDF, lets see http://maven.apache.org/maven.pdf, page 3) Personally, I vote for this following copyright: © 2001-2005, Apache Software Foundation • ALL RIGHTS RESERVED was: It should be nice to standardize the copyright between the different generated files (HTML/PDF) Actually, we have: * © 2001-2005, Apache Software Foundation (HTML - XDOC, lets see http://maven.apache.org) * © 2001 APACHE SOFTWARE FOUNDATION • ALL RIGHTS RESERVED (PDF, lets see http://maven.apache.org/maven.pdf, page 3) Personally, I vote for this following copyright: © 2001-2005, Apache Software Foundation • ALL RIGHTS RESERVED Environment: type: Bug (was: Improvement) Standardize copyright notices - Key: MPPDF-35 URL: http://jira.codehaus.org/browse/MPPDF-35 Project: maven-pdf-plugin Type: Bug Versions: 2.2 Reporter: Vincent Siveton Assignee: Arnaud Heritier Fix For: 2.3.1 Attachments: copyright.patch It should be nice to standardize the copyright between the different generated files (HTML/PDF) Actually, we have: * © 2001-2005, Apache Software Foundation (HTML - XDOC, lets see http://maven.apache.org) * © 2001 APACHE SOFTWARE FOUNDATION • ALL RIGHTS RESERVED (PDF, lets see http://maven.apache.org/maven.pdf, page 3) Personally, I vote for this following copyright: © 2001-2005, Apache Software Foundation • ALL RIGHTS RESERVED -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPPDF-39) missing patch for MPPDF-24
[ http://jira.codehaus.org/browse/MPPDF-39?page=all ] Arnaud Heritier closed MPPDF-39: Resolution: Fixed missing patch for MPPDF-24 -- Key: MPPDF-39 URL: http://jira.codehaus.org/browse/MPPDF-39 Project: maven-pdf-plugin Type: Bug Versions: 2.3 Environment: ? Reporter: Lukas Theussl Assignee: Arnaud Heritier Priority: Minor Fix For: 2.3.1 Attachments: fo-styles.patch Original Estimate: 5 minutes Remaining: 5 minutes In my recent submission for MPPDF-24 I missed one patch in the attachments. The patch for fo-styles.xslt is attached, it defines a missing attribute for code style=indent tags and cleans up some layout issues with definition lists. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPSITE-35) ftpdeploy doesn't work properly
[ http://jira.codehaus.org/browse/MPSITE-35?page=all ] Arnaud Heritier closed MPSITE-35: - Assign To: Arnaud Heritier Resolution: Won't Fix Sorry but it will never work with maven 1.0.X because the ftp ant task depends of jars not available on ibiblio. I don't know why but it was updated on the web site. I'm trying to republish the web site. I perhaps forgot to send it in the live site instead of the staging one : http://people.apache.org/~brett/maven-stage-site/reference/plugins/site/ ftpdeploy doesn't work properly --- Key: MPSITE-35 URL: http://jira.codehaus.org/browse/MPSITE-35 Project: maven-site-plugin Type: Bug Components: plugin Versions: 1.6.1 Environment: maven-site-plugin-1.6.1, Maven 1.0.2, Windows XP, Java 5.0 Reporter: Steffen Krause Assignee: Arnaud Heritier 1. configured the remote siteAdress (project.xml) 2. configured the remote siteDirectory (project.xml) 3. configured deploy method (ftp), username and password (project.properties) 4. called goal site:deploy Result: BUILD FAILED File.. C:\Documents and Settings\kimba\.maven\cache\maven-site-plugin-1.6.1\plugin.jelly Element... taskdef Line.. 130 Column 6 taskdef class org.apache.tools.ant.taskdefs.optional.net.FTP cannot be found 5. tried calling goal site:ftpdeploy directly Result: BUILD FAILED File.. C:\Documents and Settings\kimba\.maven\cache\maven-site-plugin-1.6.1\plugin.jelly Element... taskdef Line.. 130 Column 6 taskdef class org.apache.tools.ant.taskdefs.optional.net.FTP cannot be found -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPJXR-29) If a package.html exists, add it to the package page like Javadoc does.
If a package.html exists, add it to the package page like Javadoc does. --- Key: MPJXR-29 URL: http://jira.codehaus.org/browse/MPJXR-29 Project: maven-jxr-plugin Type: New Feature Reporter: Jeff Jensen Some code bases have a lot of documentation in package.html files. Reading that info while navigating source through JXR would be very helpful, preventing having switch to and hunt for it in Javadoc or reading the raw package.html 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPDF-8) add support for external imaging libraries like jimi and jai
[ http://jira.codehaus.org/browse/MPPDF-8?page=comments#action_44272 ]
Lukas Theussl commented on MPPDF-8:
---
Jimi and Jai are not free and cannot be distributed via Ibiblio. Therefore I
don't think it's a good idea to put them into the project dependencies - you
shouldn't be obliged to download these jars manually in order to run the pdf
goal.
For the jar release numbers, we'll either have to fall back to the first
suggestion (set the version via a property), or use a hardcoded string (telling
the user that he has to use a certain version of the jars).
Another possibility would be to loop over all .jar files found in the local
repository (don't know if that's possible).
add support for external imaging libraries like jimi and jai
Key: MPPDF-8
URL: http://jira.codehaus.org/browse/MPPDF-8
Project: maven-pdf-plugin
Type: Improvement
Environment: maven-1.0rc2, maven-pdf-plugin 2.1
Reporter: Fábio Franco Uechi
Assignee: Arnaud Heritier
Priority: Minor
Problems with the insertion of PNG image files.
JIMI/JAI libraries needed for handling them.
How I've solved it:
I created 3 new properties in my project.properties. Each of
them just pointing to its respective library location.
maven.pdf.jimi.jar=${maven.repo.local}/jimi/jars/jimi-1.0.jar
maven.pdf.jaicore.jar=${maven.repo.local}/jai/jars/jai_core-1.1.2.jar
maven.pdf.jaicodec.jar=${maven.repo.local}/jai/jars/jai_codec-1.1.2.jar
After that I've inserted the following lines to the plugin.jelly
script file:
pathelement
location=${pom.getPluginContext('maven-pdf-plugin').getVariable('maven.pdf.jimi.jar')}/
pathelement
location=${pom.getPluginContext('maven-pdf-plugin').getVariable('maven.pdf.jaicore.jar')}/
pathelement
location=${pom.getPluginContext('maven-pdf-plugin').getVariable('maven.pdf.jaicodec.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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPDF-19) Cannot build the pdf documentation for maven 1.1
[ http://jira.codehaus.org/browse/MPPDF-19?page=comments#action_44276 ] Lukas Theussl commented on MPPDF-19: I am not sure if your conclusion is correct. First, I only used fig1 once. Second, you reported the issue first for pdf-plugin-2.3-SNAPSHOT, this was before MPPDF-24 was fixed. The algorithm for id generation was changed by that fix, so it must be a different issue than MPPDF-40. I'll check that a bit more. Cannot build the pdf documentation for maven 1.1 Key: MPPDF-19 URL: http://jira.codehaus.org/browse/MPPDF-19 Project: maven-pdf-plugin Type: Bug Versions: 2.3 Reporter: Arnaud Heritier Assignee: Arnaud Heritier Error : [java] [INFO] area contents overflows area in line [java] [INFO] area contents overflows area in line [java] [INFO] area contents overflows area in line [java] [INFO] area contents overflows area in line [java] [INFO] [115] [java] [INFO] [116] [java] [ERROR] file:/D:/Work/Dev/maven-1.1/target/pdf/project.fo:18645:87 The id #org.apache.maven.plugin.GoalToJellyScriptHousingMapper.methodsN27024C already exists in this document BUILD FAILED File.. D:\Work\Data\maven\cache\maven-pdf-plugin-2.3-SNAPSHOT\plugin.jelly Element... java Line.. 263 Column 94 Java returned: 2 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r231353 - /maven/components/trunk/maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginManager.java
Author: kenney
Date: Wed Aug 10 16:31:40 2005
New Revision: 231353
URL: http://svn.apache.org/viewcvs?rev=231353view=rev
Log:
Sometimes plugins get added in an unofficial way - the pluginDiscovererManager
sees the plugin and marks it as 'installed' (it's in a hashtable somewhere).
The official way is to go through verifyPlugin. That gets called later on
for that plugin, which only calls addPlugin (that registers, resolves,
and, most importantly, creates a childContainer for that plugin!) IF
the plugin is NOT yet registered.
Since it is registered in the hashtable, but no childRealm was made there,
addPlugin doesn't get called. Added a simple check to ALSO call 'addPlugin'
if it was added to the hashtable. Side effect is that the version that
was normally going to be used is now used and overrides the other version.
This really needs a cleanup!
Committing anyway:
01:26trygvis right now I think we're allowed to push over old ladies and
steal candy from small children to get this to work
Modified:
maven/components/trunk/maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginManager.java
Modified:
maven/components/trunk/maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginManager.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginManager.java?rev=231353r1=231352r2=231353view=diff
==
---
maven/components/trunk/maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginManager.java
(original)
+++
maven/components/trunk/maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginManager.java
Wed Aug 10 16:31:40 2005
@@ -186,7 +186,10 @@
}
// TODO: this might result in an artifact RELEASE being resolved
continuously
-if ( !pluginCollector.isPluginInstalled( plugin ) )
+ // FIXME: need to find out how a plugin gets marked as
'installed'
+ // and no ChildContainer exists. The check for that below fixes
+ // the 'Can't find plexus container for plugin: xxx' error.
+if ( !pluginCollector.isPluginInstalled( plugin ) ||
container.getChildContainer( plugin.getKey() ) == null )
{
try
{
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-722) maven-site-plugin maven-site.vm contains wired encoding
maven-site-plugin maven-site.vm contains wired encoding --- Key: MNG-722 URL: http://jira.codehaus.org/browse/MNG-722 Project: Maven 2 Type: Bug Components: maven-plugins Versions: 2.0-beta-1 Environment: all Reporter: Incze Lajos maven-site-plugin maven-site.vm contains wired encoding: meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1 / It probably needs a conf. parameter and changed to meta http-equiv=Content-Type content=text/html; charset=$outputEncoding / -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-722) maven-site-plugin maven-site.vm contains wired encoding
[ http://jira.codehaus.org/browse/MNG-722?page=comments#action_44277 ] Incze Lajos commented on MNG-722: - The diagnosis OK, but the cure is bad. It basically depends on the velocity settings what the output encoding will be. So, the velocity properties should be adjusted to the required encoding, too. maven-site-plugin maven-site.vm contains wired encoding --- Key: MNG-722 URL: http://jira.codehaus.org/browse/MNG-722 Project: Maven 2 Type: Bug Components: maven-plugins Versions: 2.0-beta-1 Environment: all Reporter: Incze Lajos maven-site-plugin maven-site.vm contains wired encoding: meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1 / It probably needs a conf. parameter and changed to meta http-equiv=Content-Type content=text/html; charset=$outputEncoding / -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Thu Aug 11 00:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050811.00.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050811.00.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-479) This is the spellchecker component of Lucene as described in http://wiki.apache.org/jakarta-lucene/SpellChecker.
This is the spellchecker component of Lucene as described in http://wiki.apache.org/jakarta-lucene/SpellChecker. Key: MAVENUPLOAD-479 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-479 Project: maven-upload-requests Type: Wish Reporter: Chris Kimm The mis-spelling of spellcheker-1.1 is intentional. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - checkout] Thu Aug 11 00:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050811.001500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050811.001500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-710) Add ability to fork the maven-compiler-plugin
[ http://jira.codehaus.org/browse/MNG-710?page=all ] Rod Coffin updated MNG-710: --- Attachment: maven-compiler-plugin.diff3.txt plexus-compiler-javac.diff3.txt plexus-compiler-api.diff3.txt I've added unit tests for building an argument string for several versions of the javac compiler. I also enhanced the plexus compiler and the maven compiler plugin to correctly handle jdk 1.3 arguments by passing a compilerVersion parameter in the CompilerConfiguration object. I realized why my source weren't properly formatted last time. I have the Maven format installed instead of the plexus one. Where can I get the plexus format template for Eclipse? In the meantime I just tried to do the best job I could manually adhering to the code style I found in the rest of the file. Add ability to fork the maven-compiler-plugin - Key: MNG-710 URL: http://jira.codehaus.org/browse/MNG-710 Project: Maven 2 Type: Improvement Components: maven-plugins Reporter: Rod Coffin Assignee: Trygve Laugstol Fix For: 2.0-beta-1 Attachments: maven-compiler-plugin.diff.txt, maven-compiler-plugin.diff3.txt, plexus-compiler-api.diff.txt, plexus-compiler-api.diff3.txt, plexus-compiler-javac.diff.txt, plexus-compiler-javac.diff2.txt, plexus-compiler-javac.diff3.txt Add the ability to fork the maven-compiler-plugin. This would allow projects to be compiled with a JDK other than the one used to run Maven from. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-480) Upload Joda-Time 1.1
Upload Joda-Time 1.1 Key: MAVENUPLOAD-480 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-480 Project: maven-upload-requests Type: Task Reporter: Stephen Colebourne http://joda-time.sourceforge.net/release/joda-time-1.1-bundle.jar http://joda-time.sourceforge.net http://joda-time.sourceforge.net/team-list.html Joda-Time is a quality replacement for dates and times in Java -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-479) This is the spellchecker component of Lucene as described in http://wiki.apache.org/jakarta-lucene/SpellChecker.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-479?page=comments#action_44280 ] Carlos Sanchez commented on MAVENUPLOAD-479: If this is an apache project it has to be uploaded through the apache repo at http://www.apache.org/dist/java-repository/ Check apache policies This is the spellchecker component of Lucene as described in http://wiki.apache.org/jakarta-lucene/SpellChecker. Key: MAVENUPLOAD-479 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-479 Project: maven-upload-requests Type: Wish Reporter: Chris Kimm The mis-spelling of spellcheker-1.1 is intentional. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-480) Upload Joda-Time 1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-480?page=all ] Carlos Sanchez closed MAVENUPLOAD-480: -- Assign To: Carlos Sanchez Resolution: Fixed Upload Joda-Time 1.1 Key: MAVENUPLOAD-480 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-480 Project: maven-upload-requests Type: Task Reporter: Stephen Colebourne Assignee: Carlos Sanchez http://joda-time.sourceforge.net/release/joda-time-1.1-bundle.jar http://joda-time.sourceforge.net http://joda-time.sourceforge.net/team-list.html Joda-Time is a quality replacement for dates and times in Java -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r231371 - /maven/maven-1/plugins/trunk/multiproject/xdocs/properties.xml
Author: carlos Date: Wed Aug 10 18:57:16 2005 New Revision: 231371 URL: http://svn.apache.org/viewcvs?rev=231371view=rev Log: Fixed typo Modified: maven/maven-1/plugins/trunk/multiproject/xdocs/properties.xml Modified: maven/maven-1/plugins/trunk/multiproject/xdocs/properties.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/multiproject/xdocs/properties.xml?rev=231371r1=231370r2=231371view=diff == --- maven/maven-1/plugins/trunk/multiproject/xdocs/properties.xml (original) +++ maven/maven-1/plugins/trunk/multiproject/xdocs/properties.xml Wed Aug 10 18:57:16 2005 @@ -156,7 +156,7 @@ tdYes/td td Name of the .xml file to be created for the overview page. -Defaults to codeproject-overview/code. +Defaults to codeprojects-overview/code. /td /tr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Subscription: Outstanding Repository Maintenance: Evangelism
Issue Subscription Filter: Outstanding Repository Maintenance: Evangelism (30 issues) Subscriber: mavendevlist Project: Maven Evangelism Resolution: Unresolved Key Summary MEV-58 commons-el missing dependency scope http://jira.codehaus.org/browse/MEV-58 MEV-59 commons-upload missing dependency scope http://jira.codehaus.org/browse/MEV-59 MEV-28 bogus dependencies in commons-configuration http://jira.codehaus.org/browse/MEV-28 MEV-57 Invalid commons-beanutils:commons-beanutils versions http://jira.codehaus.org/browse/MEV-57 MEV-50 empty dependencies/ in batik v1.6 poms on maven1 repository on ibiblio http://jira.codehaus.org/browse/MEV-50 MEV-52 broken active MQ poms http://jira.codehaus.org/browse/MEV-52 MEV-51 broken geronimo POMS http://jira.codehaus.org/browse/MEV-51 MEV-48 openejb poms http://jira.codehaus.org/browse/MEV-48 MEV-46 Missing JDBC POM http://jira.codehaus.org/browse/MEV-46 MEV-45 Full list of poms that doesn't respect the m2 format http://jira.codehaus.org/browse/MEV-45 MEV-43 Hibernate 3.0 pom doesn't have any dependencies declared http://jira.codehaus.org/browse/MEV-43 MEV-40 URL tag invalids http://jira.codehaus.org/browse/MEV-40 MEV-39 Junit scope in commons-lang pom not in scope test. http://jira.codehaus.org/browse/MEV-39 MEV-38 POM for commons-jelly-tags-ant has incorrect artifact references bogus dependency http://jira.codehaus.org/browse/MEV-38 MEV-36 Exo POM(s) missing dependency versions http://jira.codehaus.org/browse/MEV-36 MEV-34 XOM POM references icu4j which is not in the repo http://jira.codehaus.org/browse/MEV-34 MEV-35 XOM POM references tagsoup which is not in the repo http://jira.codehaus.org/browse/MEV-35 MEV-33 XOM POM references xercesImpl v.2.2.1 which does not exist in repo http://jira.codehaus.org/browse/MEV-33 MEV-32 XOM POM references invalid servlet API location http://jira.codehaus.org/browse/MEV-32 MEV-31 XOM POM references xmlParserAPIs v2.6.1 which is not in the repo http://jira.codehaus.org/browse/MEV-31 MEV-20 clean up bad IDs in the repository http://jira.codehaus.org/browse/MEV-20 MEV-2 Broken dependency for groovy http://jira.codehaus.org/browse/MEV-2 MEV-4 Misnamed pom for Postgresql http://jira.codehaus.org/browse/MEV-4 MEV-9 jmock-cglib should depend on cglib http://jira.codehaus.org/browse/MEV-9 MEV-17 nanocontainer junit compile scope dependency http://jira.codehaus.org/browse/MEV-17 MEV-16 picocontainer junit compile scope dependency http://jira.codehaus.org/browse/MEV-16 MEV-15 commons-pool junit compile scope dependency http://jira.codehaus.org/browse/MEV-15 MEV-14 commons-loggin junit compile scope dependency http://jira.codehaus.org/browse/MEV-14 MEV-13 commons-cli junit compile scope dependency http://jira.codehaus.org/browse/MEV-13 MEV-3 Broken dependencies for nanocontainer http://jira.codehaus.org/browse/MEV-3 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Subscription: Outstanding Repository Maintenance: Uploads
Issue Subscription Filter: Outstanding Repository Maintenance: Uploads (7 issues) Subscriber: mavendevlist Project: maven-upload-requests Resolution: Unresolved Key Summary MAVENUPLOAD-479This is the spellchecker component of Lucene as described in http://wiki.apache.org/jakarta-lucene/SpellChecker. http://jira.codehaus.org/browse/MAVENUPLOAD-479 MAVENUPLOAD-465Please upload Hammurapi bundle http://jira.codehaus.org/browse/MAVENUPLOAD-465 MAVENUPLOAD-467please upload OrangeVolt ant tasks 1.3 http://jira.codehaus.org/browse/MAVENUPLOAD-467 MAVENUPLOAD-466please upload ROXES ant tasks 1.2 http://jira.codehaus.org/browse/MAVENUPLOAD-466 MAVENUPLOAD-450upload EMMA PLUGIN v0.6 http://jira.codehaus.org/browse/MAVENUPLOAD-450 MAVENUPLOAD-449Please upload JVending Registry Utility http://jira.codehaus.org/browse/MAVENUPLOAD-449 MAVENUPLOAD-452JOX 1.16 is an empty jar http://jira.codehaus.org/browse/MAVENUPLOAD-452 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEV-50) empty dependencies/ in batik v1.6 poms on maven1 repository on ibiblio
[ http://jira.codehaus.org/browse/MEV-50?page=all ] Brett Porter closed MEV-50: --- Resolution: Fixed empty dependencies/ in batik v1.6 poms on maven1 repository on ibiblio Key: MEV-50 URL: http://jira.codehaus.org/browse/MEV-50 Project: Maven Evangelism Type: Bug Reporter: Michael Heuer Attachments: batik.tar.gz Sorry to be venting a bit of frustration, but the POMs for batik in the maven1 ibiblio repository are quite useless without the dependencies tags filled in. Having to random-guess trial-and-error dependency relationships between 21 different jar files is a pain in the ass. e.g. http://www.ibiblio.org/maven/batik/poms/batik-parser-1.6.pom ?xml version=1.0 encoding=UTF-8? project nameBatik Parser/name groupIdbatik/groupId idbatik-parser/id currentVersion1.6/currentVersion inceptionYear2000/inceptionYear shortDescriptionBatik Parser/shortDescription descriptionBatik Parser/description dependencies/ /project -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-478) war:war warSourceExcludes parameter not used when set in the POM
[ http://jira.codehaus.org/browse/MNG-478?page=comments#action_44281 ] Greg Case commented on MNG-478: --- After using Maven2 for sometime (and loving it), I would like to help out by taking a crack at submitting a patch for this issue, but wanted to get some ideas of how to aproach it before I start hacking away...Currently the WarMojo is using FileUtils.copyDirectoryStructure from plexus, which of course doesn't support excludes/includes. I was thinking of modifying this to use an approach similar to how ResourcesMojo handles the copying, by using DirectoryScanner and setting the excludes/includs there. So my questions are: 1) Is this an appropriate approach? 2) Does it make sense to allow for multiple warSourceExcludes elements, rather than a single element with a comma-separated list? It would seem that multiple elements would be cleaner, and more consistent with the rest of the maven 2 project. war:war warSourceExcludes parameter not used when set in the POM Key: MNG-478 URL: http://jira.codehaus.org/browse/MNG-478 Project: Maven 2 Type: Bug Components: maven-plugins Versions: 2.0-alpha-2 Environment: Windows XP Reporter: Yann Le Du Fix For: 2.0-beta-1 I got the following in my POM for a WAR-packaged project : build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId configuration warSourceExcludes**/test.html/warSourceExcludes /configuration /plugin /plugins /build I run m2 install. The file src/main/webapp/test.html is included in the resulting WAR, but, unless I'm mistaken, it shouldn't. I've tried with the following patterns : test.html */test.html **/test.html *\test.html **\test.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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/11-Aug-2005_12.00.35/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-478) war:war warSourceExcludes parameter not used when set in the POM
[ http://jira.codehaus.org/browse/MNG-478?page=all ] Brett Porter updated MNG-478: - Description: I got the following in my POM for a WAR-packaged project : build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId configuration warSourceExcludes**/test.html/warSourceExcludes /configuration /plugin /plugins /build I run m2 install. The file src/main/webapp/test.html is included in the resulting WAR, but, unless I'm mistaken, it shouldn't. I've tried with the following patterns : test.html */test.html **/test.html *\test.html **\test.html was: I got the following in my POM for a WAR-packaged project : build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId configuration warSourceExcludes**/test.html/warSourceExcludes /configuration /plugin /plugins /build I run m2 install. The file src/main/webapp/test.html is included in the resulting WAR, but, unless I'm mistaken, it shouldn't. I've tried with the following patterns : test.html */test.html **/test.html *\test.html **\test.html Complexity: Novice both sound good to me. go for it, and thanks! war:war warSourceExcludes parameter not used when set in the POM Key: MNG-478 URL: http://jira.codehaus.org/browse/MNG-478 Project: Maven 2 Type: Bug Components: maven-plugins Versions: 2.0-alpha-2 Environment: Windows XP Reporter: Yann Le Du Fix For: 2.0-beta-1 I got the following in my POM for a WAR-packaged project : build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId configuration warSourceExcludes**/test.html/warSourceExcludes /configuration /plugin /plugins /build I run m2 install. The file src/main/webapp/test.html is included in the resulting WAR, but, unless I'm mistaken, it shouldn't. I've tried with the following patterns : test.html */test.html **/test.html *\test.html **\test.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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-723) [patch] assembly:unpack
[patch] assembly:unpack --- Key: MNG-723 URL: http://jira.codehaus.org/browse/MNG-723 Project: Maven 2 Type: New Feature Components: maven-plugins Versions: 2.0-beta-1 Reporter: Jason Grant Priority: Minor Fix For: 2.0-beta-1 Attachments: AbstractAssemblyMojo.java, AssemblyMojo.diff, UnpackMojo.java I've coded an assembly:unpack goal. It will unpack any dependencies in the project whose filenames indicate type jar or zip. These are unpacked into the workDirectory. I went about it by pulling common infrastructure out of AssemblyMojo and placing it in a new abstract superclass AbstractAssemblyMojo. Another new class, called UnpackMojo now also resides in maven-assembly-plugin. I was going to code an integration test for this, however I will instead do some work on http://jira.codehaus.org/browse/MNG-483 first, so that I can use the latter as the first step in the test. I'll write some supporting notes over on that jira issue. Note that this is the first code that I've contributed to Maven - I'm happy to take direction should I be breaking conventions. You'll see me from time to time on #maven as jasong. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MAVENUPLOAD-480) Upload Joda-Time 1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-480?page=all ] Brett Porter reopened MAVENUPLOAD-480: -- http://test.maven.codehaus.org/reports/repoclean/11-Aug-2005_12.00.35/repository.report.txt It appears the POM submitted does not parse. Upload Joda-Time 1.1 Key: MAVENUPLOAD-480 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-480 Project: maven-upload-requests Type: Task Reporter: Stephen Colebourne Assignee: Carlos Sanchez http://joda-time.sourceforge.net/release/joda-time-1.1-bundle.jar http://joda-time.sourceforge.net http://joda-time.sourceforge.net/team-list.html Joda-Time is a quality replacement for dates and times in Java -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r231393 - in /maven/components/trunk: maven-core-it-plugin/src/main/java/org/apache/maven/plugin/coreit/ maven-core-it/ maven-core-it/it0049/ maven-core/src/main/java/org/apache/maven/plugin/
Author: jdcasey Date: Wed Aug 10 21:38:46 2005 New Revision: 231393 URL: http://svn.apache.org/viewcvs?rev=231393view=rev Log: Resolving: MNG-674 o Added it0049 to prevent further regressions. ;) Added: maven/components/trunk/maven-core-it/it0049/ maven/components/trunk/maven-core-it/it0049/expected-results.txt (with props) maven/components/trunk/maven-core-it/it0049/goals.txt (with props) maven/components/trunk/maven-core-it/it0049/pom.xml (with props) Modified: maven/components/trunk/maven-core-it-plugin/src/main/java/org/apache/maven/plugin/coreit/CoreItMojo.java maven/components/trunk/maven-core-it/README.txt maven/components/trunk/maven-core-it/integration-tests.txt maven/components/trunk/maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginManager.java Modified: maven/components/trunk/maven-core-it-plugin/src/main/java/org/apache/maven/plugin/coreit/CoreItMojo.java URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-core-it-plugin/src/main/java/org/apache/maven/plugin/coreit/CoreItMojo.java?rev=231393r1=231392r2=231393view=diff == --- maven/components/trunk/maven-core-it-plugin/src/main/java/org/apache/maven/plugin/coreit/CoreItMojo.java (original) +++ maven/components/trunk/maven-core-it-plugin/src/main/java/org/apache/maven/plugin/coreit/CoreItMojo.java Wed Aug 10 21:38:46 2005 @@ -59,7 +59,7 @@ private File basedirAlignmentDirectory; /** - * @parameter + * @parameter alias=pluginFile */ private String pluginItem = foo; Modified: maven/components/trunk/maven-core-it/README.txt URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-core-it/README.txt?rev=231393r1=231392r2=231393view=diff == --- maven/components/trunk/maven-core-it/README.txt (original) +++ maven/components/trunk/maven-core-it/README.txt Wed Aug 10 21:38:46 2005 @@ -134,6 +134,10 @@ it0047: Test the use case for having a compile time dependency be transitive: when you extend a class you need its dependencies at compile time. +it0048: Test profile overrides of values specified in the pom. + +it0049: Test parameter alias usage. + --- - generated sources Modified: maven/components/trunk/maven-core-it/integration-tests.txt URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-core-it/integration-tests.txt?rev=231393r1=231392r2=231393view=diff == --- maven/components/trunk/maven-core-it/integration-tests.txt (original) +++ maven/components/trunk/maven-core-it/integration-tests.txt Wed Aug 10 21:38:46 2005 @@ -1,3 +1,5 @@ +it0049 +it0048 it0047 it0046 it0045 Added: maven/components/trunk/maven-core-it/it0049/expected-results.txt URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-core-it/it0049/expected-results.txt?rev=231393view=auto == --- maven/components/trunk/maven-core-it/it0049/expected-results.txt (added) +++ maven/components/trunk/maven-core-it/it0049/expected-results.txt Wed Aug 10 21:38:46 2005 @@ -0,0 +1 @@ +target/touchFile.txt Propchange: maven/components/trunk/maven-core-it/it0049/expected-results.txt -- svn:eol-style = native Propchange: maven/components/trunk/maven-core-it/it0049/expected-results.txt -- svn:keywords = Author Date Id Revision Added: maven/components/trunk/maven-core-it/it0049/goals.txt URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-core-it/it0049/goals.txt?rev=231393view=auto == --- maven/components/trunk/maven-core-it/it0049/goals.txt (added) +++ maven/components/trunk/maven-core-it/it0049/goals.txt Wed Aug 10 21:38:46 2005 @@ -0,0 +1 @@ +core-it:touch Propchange: maven/components/trunk/maven-core-it/it0049/goals.txt -- svn:eol-style = native Propchange: maven/components/trunk/maven-core-it/it0049/goals.txt -- svn:keywords = Author Date Id Revision Added: maven/components/trunk/maven-core-it/it0049/pom.xml URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-core-it/it0049/pom.xml?rev=231393view=auto == --- maven/components/trunk/maven-core-it/it0049/pom.xml (added) +++ maven/components/trunk/maven-core-it/it0049/pom.xml Wed Aug 10 21:38:46 2005 @@ -0,0 +1,28 @@ +project +
[jira] Closed: (MNG-674) Plugin @parameter alias does not seem to work
[ http://jira.codehaus.org/browse/MNG-674?page=all ] John Casey closed MNG-674: -- Resolution: Fixed it0049 should prevent further regressions on this issue. Plugin @parameter alias does not seem to work - Key: MNG-674 URL: http://jira.codehaus.org/browse/MNG-674 Project: Maven 2 Type: Bug Components: maven-plugin-api Versions: 2.0-beta-1 Reporter: Peter van de Hoef Assignee: John Casey Fix For: 2.0-beta-1 I'm trying to use the alias feature in plugin parameter definitions: The syntax I'm using is: /** * @parameter alias=bar */ private String foo; Then: configuration foomaven/foo /configuration does work, but: configuration barmaven/bar /configuration does not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-709) lifecycle can end up in an infinite loop
[ http://jira.codehaus.org/browse/MNG-709?page=comments#action_44287 ] John Casey commented on MNG-709: which one should win? the @execute phase=package or the phasepackage/phase? Since the assembly mojo declares that it needs to have the package phase completed before running, I think it would be safer to defer to the mojo developer and forget about binding it to the package phase...maybe handle it as an addendum after the package phase has been run or something... This is vague because I'm still wrapping my brain around the problem...am I missing something? lifecycle can end up in an infinite loop Key: MNG-709 URL: http://jira.codehaus.org/browse/MNG-709 Project: Maven 2 Type: Bug Components: maven-plugins Versions: 2.0-beta-1 Environment: linux fedora core 3 Reporter: Jason Grant Priority: Blocker Fix For: 2.0-beta-1 The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop. build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId configuration descriptorsrc/assemble/zip-source.xml/descriptor /configuration executions execution !-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -- !--phasepackage/phase-- goals goalassembly/goal /goals /execution /executions /plugin /plugins /build -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-483) sort out artifact attachment
[ http://jira.codehaus.org/browse/MNG-483?page=comments#action_44289 ] Jason Grant commented on MNG-483: - A bit of background with regard to Brett's mention of me looking at the attachment of artifacts, above. I've been using assembly to produce zip files, and asked questions on IRC about how best to get these across to the local repo so that other project could depend on them. If I understand correctly, Brett suggested an enhancement to AssemblyMojo that will attach all assemblies to the project as artifacts. Then, when the project is installed, these artifacts will wind up in the local repo. There was some talk of only doing this if the project packaging was of [new] type assembly, but I think we agreed to do it whatever the packaging is (see below). I'm happy to have a go at this - I'll build it on top of my contribution sent as a patch in http://jira.codehaus.org/browse/MNG-723 if other folk agree. So just to be clear, my contribution to this issue has quite limited scope. I'm too green to understand some of the content above. --- (15:58:29) jasong: [junk snipped] just thinking ahead though - I was going to modify AssemblyMojo to simply attach each archive to the project. Is that a reasonable start, or should I be considering what the project's packaging is? (16:05:05) brett: jasong: attach away! That's great, because then anyone generating an assembly (even for a jar) will be able to install/deploy it. Thanks! sort out artifact attachment Key: MNG-483 URL: http://jira.codehaus.org/browse/MNG-483 Project: Maven 2 Type: Bug Reporter: Brett Porter Assignee: John Casey Priority: Blocker Fix For: 2.0-beta-1 currently, there is an attachArtifact call inside the plugin building the attachment. It imposes a m-a and m-p dependency, as well as an artifactFactory requirement to be able to construct the artifact to attach. sort out - if there is an easier way to achieve this - how to retain the default source binding, but also how to turn it off - how to make the source binding happen only on release (bear in mind people may not be using the release plugin... a profile was the original idea) - how to bind assembly similarly -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-697) allow plugins to declare dependence on the project-classpath(s)
[ http://jira.codehaus.org/browse/MNG-697?page=comments#action_44290 ]
John Casey commented on MNG-697:
one use case that I can think of would be using a newly minted implementation
of, say, plexus-compiler, where you're doing a lookup by ROLE which is provided
in -compiler-api, and using the implementation you just put together.
I guess the bottom line for me is that this doesn't amount to too much in the
way of extra code to implement. I know the above use case could be implemented
in other ways, but this would be far less code in the plugin itself.
Personally, I'm +0 - sort of without strong opinion, but willing to implement -
but I do believe its plausible to say that this could save some time and
complexity in plugin development.
An alternative might be some maven-plugin-utils artifact which is on a separate
release schedule, and could provide utilities for constructing/managing
classloaders based on ${project.compileClasspathElements} and the like.
allow plugins to declare dependence on the project-classpath(s)
---
Key: MNG-697
URL: http://jira.codehaus.org/browse/MNG-697
Project: Maven 2
Type: New Feature
Components: maven-plugin-descriptor, maven-core
Versions: 2.0-alpha-3
Reporter: John Casey
Assignee: John Casey
Priority: Critical
Fix For: 2.0-beta-1
Currently the only way to provide access to the classpath which consists of
the project artifacts within some scope from a plugin is to manually create
your own classloader inside the plugin using project.getCompileClasspath() or
somesuch. In many plugins (thinking of integration-tests where the project is
NOT an appserver module), it would be most useful to have the plugin
container started with the appropriate project-classpath already added to the
container. This might even be nice for testing plexus projects, and would
allow the plugin to simply instantiate (somehow) and use compiled classes in
order to run tests.
Jesse even tells me this would be useful from a process-classes phase, in
order to gather info about the classes that were compiled.
I propose the following modifications:
1. Add addProjectClasspath=scope (where scope = {compile,test...})
configuration for the maven-plugin-plugin, alongside prefix or whatever else
we use to define the plugin-level metadata.
2. For plugins declaring addProjectClasspath, add the appropriate project
classpath to the plugin container before calling the mojo.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-591) Integration tests lifecycle
[ http://jira.codehaus.org/browse/MNG-591?page=comments#action_44291 ] John Casey commented on MNG-591: in the xdoclet example above, would it make more sense to emulate the build-extension pattern and allow plugin-extensions that are loaded into the plugin container? I know this is a repackaging of the plugin-dependency argument, but I believe calling them plugin-extensions would be more correct. Also, it would remain up to the plugin's underlying technology (xdoclet, f.e.) to actually discover the optional components contained in the extension artifacts...we'd just make them available. Integration tests lifecycle --- Key: MNG-591 URL: http://jira.codehaus.org/browse/MNG-591 Project: Maven 2 Type: Improvement Reporter: Kenney Westerhof Assignee: John Casey Priority: Blocker Fix For: 2.0-beta-1 I'm trying to do an integration test that depends on a war/ear to be deployed. What i'm missing is: - integration-test-compile stage and/or: - a way to specify an integrationTestSourceDirectory or multiple testSourceDirectories in the pom I can't put the test sources in src/test/java because then surefire will run them in the test stage, when there's no artifact to deploy yet. [Btw, I'm doing this while creating a cactus plugin, for the moment using cargo in the TestSuite itself to deploy.] The idea is that the integration test sources go in src/itest/*; that there be a integration-test-compile, integration-test-package and/or integration-test-appdeploy[or something] and that surefire is also bound to integration-test. Maybe something can be done using the src/test/project/some-project/ approach seen in maven-javadoc-plugin, maven-site-plugin and maven-eclipse-plugin (i'd like to see some of that standardized anyway to allow plugin testing generally - which can also be seen as integration testing). Thoughts, comments, approaches? -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-591) Integration tests lifecycle
[ http://jira.codehaus.org/browse/MNG-591?page=comments#action_44292 ] John Casey commented on MNG-591: the problem with adding integration-test dependency scope and srcdir is that this is a slippery slope. Can we really define all of the types of tests that are out there, and if we do, do we really want integrationTestSourceDirectory/ and functionalTestSourceDirectory/ and ...? I think it's reasonable to expect that integration- or functional- or ... tests will need their own set of dependencies, and that it's unreasonable to expect that these can be satisfied using scopetest/scope. The source dir is easier, although we'd still have to provide a utility to help these plugins compile it. This got shot down once before, but I'll toss it out there again, just to see if it'll help generate some discussion/thinking: what about allowing dependencies to be tied to a particular lifecycle phase? While this would help by allowing phaseintegration-test/phase in the dependency, it could conceivably muddy the waters of scope vs. bindings for dependencies. Calculating inheritedScope is easy on this...if it's not runtime || compile, it's not included transitively. I think it might not be such a great thing to ship maven 2.0 with the disclaimer We can't handle all of your testing needs yet. However, I'm not sure what the way forward is. I'd really like to get started on this issue, though, since it looks like the highest-risk issue left for -beta-1. Integration tests lifecycle --- Key: MNG-591 URL: http://jira.codehaus.org/browse/MNG-591 Project: Maven 2 Type: Improvement Reporter: Kenney Westerhof Assignee: John Casey Priority: Blocker Fix For: 2.0-beta-1 I'm trying to do an integration test that depends on a war/ear to be deployed. What i'm missing is: - integration-test-compile stage and/or: - a way to specify an integrationTestSourceDirectory or multiple testSourceDirectories in the pom I can't put the test sources in src/test/java because then surefire will run them in the test stage, when there's no artifact to deploy yet. [Btw, I'm doing this while creating a cactus plugin, for the moment using cargo in the TestSuite itself to deploy.] The idea is that the integration test sources go in src/itest/*; that there be a integration-test-compile, integration-test-package and/or integration-test-appdeploy[or something] and that surefire is also bound to integration-test. Maybe something can be done using the src/test/project/some-project/ approach seen in maven-javadoc-plugin, maven-site-plugin and maven-eclipse-plugin (i'd like to see some of that standardized anyway to allow plugin testing generally - which can also be seen as integration testing). Thoughts, comments, approaches? -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-709) lifecycle can end up in an infinite loop
[ http://jira.codehaus.org/browse/MNG-709?page=comments#action_44293 ] Jason Grant commented on MNG-709: - Would that approach allow me to specify, say, phasegenerate-sources/phase if I wanted to create some zips for inclusion into tests, etc.? WRT your question about anyone else working on this - I'm not game to fiddle about with classes like DefaultLifecycleExecutor just yet, so I'll work on the assembly stuff, as described in #MNG-483 and #MNG-723. lifecycle can end up in an infinite loop Key: MNG-709 URL: http://jira.codehaus.org/browse/MNG-709 Project: Maven 2 Type: Bug Components: maven-plugins Versions: 2.0-beta-1 Environment: linux fedora core 3 Reporter: Jason Grant Assignee: John Casey Priority: Blocker Fix For: 2.0-beta-1 The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop. build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId configuration descriptorsrc/assemble/zip-source.xml/descriptor /configuration executions execution !-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -- !--phasepackage/phase-- goals goalassembly/goal /goals /execution /executions /plugin /plugins /build -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven2 build - FAILED - update] Thu Aug 11 04:45:00 GMT 2005
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 FWIW, I redeployed the new copy of maven-core-it-plugin just now. I'm not sure how long it'll be before the copy on the zone gets updated, but I'll try to get that sorted before bed. - -john [EMAIL PROTECTED] wrote: | Log: | http://maven.zones.apache.org/~maven/logs/m2-build-log-20050811.044500.txt | | - | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFC+txwK3h2CZwO/4URAtw8AKCknfz9ubGRRgtd5v/2xyqX9f4WnACfWdvQ er+4FBI6Y8e3fmJn329lfYU= =JksE -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Thu Aug 11 05:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050811.05.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r231401 - /maven/components/trunk/maven-core-it/it0049/prebuild-hook.txt
Author: brett Date: Wed Aug 10 22:14:58 2005 New Revision: 231401 URL: http://svn.apache.org/viewcvs?rev=231401view=rev Log: add pre build hook to remove the core it plugin so it is always updated Added: maven/components/trunk/maven-core-it/it0049/prebuild-hook.txt - copied unchanged from r231400, maven/components/trunk/maven-core-it/it0009/prebuild-hook.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Thu Aug 11 05:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050811.053000.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050811.053000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
