[jira] Created: (MNGSITE-67) Dead link in the getting started guide (Intro to dependency management)
Dead link in the getting started guide (Intro to dependency management) --- Key: MNGSITE-67 URL: http://jira.codehaus.org/browse/MNGSITE-67 Project: Maven 2 Project Web Site Issue Type: Bug Reporter: Gareth Thomas Priority: Minor The link found in the first paragraph under [this section|http://maven.apache.org/guides/getting-started/index.html#How_do_I_use_external_dependencies] in the getting started guide has a dead link. The link has label text of 'Introduction the to Dependency Management' that leads to [this page|http://maven.apache.org/guides/introduction/introduction-to-dependency-management.html] and a 404 error. Sorry, but I'm not familiar with the site enouh to find a suitable replacement link. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSHARED-67) Add an parameter to force overwrite existing files even if the destination files are newer
Add an parameter to force overwrite existing files even if the destination files are newer -- Key: MSHARED-67 URL: http://jira.codehaus.org/browse/MSHARED-67 Project: Maven Shared Components Issue Type: Improvement Components: maven-filtering Affects Versions: maven-filtering-1.0-beta-1 Reporter: Olivier Lamy During resources processing it's not possible to overwrite existing files when the destination file is newer. -- 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: (MSHARED-67) Add a parameter to force overwrite existing files even if the destination files are newer
[ http://jira.codehaus.org/browse/MSHARED-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MSHARED-67: Assignee: Olivier Lamy Fix Version/s: maven-filtering-1.0-beta-2 Summary: Add a parameter to force overwrite existing files even if the destination files are newer (was: Add an parameter to force overwrite existing files even if the destination files are newer) > Add a parameter to force overwrite existing files even if the destination > files are newer > - > > Key: MSHARED-67 > URL: http://jira.codehaus.org/browse/MSHARED-67 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-filtering >Affects Versions: maven-filtering-1.0-beta-1 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: maven-filtering-1.0-beta-2 > > > During resources processing it's not possible to overwrite existing files > when the destination file is newer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3712) java.lang.NoClassDefFoundError in maven-jaxb-schemagen-plugin
[
http://jira.codehaus.org/browse/MNG-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147868#action_147868
]
Yann Albou commented on MNG-3712:
-
I did the test with maven 2.1.0-M1-RC17 and I haven't anymore the issue.
So could you use this release of Maven in m2Eclipse ?
> java.lang.NoClassDefFoundError in maven-jaxb-schemagen-plugin
> -
>
> Key: MNG-3712
> URL: http://jira.codehaus.org/browse/MNG-3712
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.1.x, 3.x
>Reporter: Eugene Kuleshov
>Priority: Blocker
> Attachments: build.log, generate-schema.zip
>
>
> When running maven-jaxb-schemagen-plugin with Maven 2.1-SNAPSHOT and latest
> 3.0-SNAPSHOT from trunk it fails with java.lang.NoClassDefFoundError. See
> attached test project and debug log from the build.
> {noformat}
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/sun/mirror/apt/AnnotationProcessorFactory
> at
> com.sun.tools.jxc.maven2.SchemaGenMojo.execute(SchemaGenMojo.java:143)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:638)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:521)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:288)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:214)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:172)
> at
> org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
> at
> org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:303)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
> at
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
> at
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:303)
> at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-3712) java.lang.NoClassDefFoundError in maven-jaxb-schemagen-plugin
[
http://jira.codehaus.org/browse/MNG-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147868#action_147868
]
yann edited comment on MNG-3712 at 9/13/08 6:34 AM:
--
I did the test with maven 2.1.0-M1-RC17 and I haven't anymore the issue.
was (Author: yann):
I did the test with maven 2.1.0-M1-RC17 and I haven't anymore the issue.
So could you use this release of Maven in m2Eclipse ?
> java.lang.NoClassDefFoundError in maven-jaxb-schemagen-plugin
> -
>
> Key: MNG-3712
> URL: http://jira.codehaus.org/browse/MNG-3712
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.1.x, 3.x
>Reporter: Eugene Kuleshov
>Priority: Blocker
> Attachments: build.log, generate-schema.zip
>
>
> When running maven-jaxb-schemagen-plugin with Maven 2.1-SNAPSHOT and latest
> 3.0-SNAPSHOT from trunk it fails with java.lang.NoClassDefFoundError. See
> attached test project and debug log from the build.
> {noformat}
> Exception in thread "main" java.lang.NoClassDefFoundError:
> com/sun/mirror/apt/AnnotationProcessorFactory
> at
> com.sun.tools.jxc.maven2.SchemaGenMojo.execute(SchemaGenMojo.java:143)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:638)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:521)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:288)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:214)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:172)
> at
> org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
> at
> org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:303)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
> at
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
> at
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:303)
> at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3715) Maven 2.1plugin cannot use classes form tools.jar
[
http://jira.codehaus.org/browse/MNG-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147867#action_147867
]
Yann Albou commented on MNG-3715:
-
I did the test with maven 2.1.0-M1-RC17 and I don't have anymore the issue
> Maven 2.1plugin cannot use classes form tools.jar
> -
>
> Key: MNG-3715
> URL: http://jira.codehaus.org/browse/MNG-3715
> Project: Maven 2
> Issue Type: Bug
> Components: General
>Affects Versions: 2.1.0-M1, 2.1.x
> Environment: Maven 2.1 Snapshot
>Reporter: Yann Albou
> Attachments: caseMaven.zip
>
>
> If a Maven plugin uses classes from ${java.home}/lib/tools.jar
> for instance : com.sun.mirror.apt.AnnotationProcessorFactory
> and if a Maven 2.1 project use this plugin then the following error appends:
> {code}
> java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory
> at org.test.simplePlugin.MyMojo.execute(MyMojo.java:33)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:638)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:521)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:288)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:214)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:172)
> at
> org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
> at
> org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:303)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
> at
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
> at
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:303)
> at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
> {code}
> I typically get this error with the maven-jaxb-schemagen-plugin but I created
> also a simple test case.
> Of course the tools.jar dependency is used:
> {code:xml}
>
> com.sun
> tools
> 1.5
> system
> ${java.home}/../lib/tools.jar
>
> {code}
> I tested with the last Maven 2.1 SNAPSHOT distribution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-601) hibernate4gwt version 1.1b deployed into wrong directory on repo1.maven.org/maven2
hibernate4gwt version 1.1b deployed into wrong directory on repo1.maven.org/maven2 -- Key: MEV-601 URL: http://jira.codehaus.org/browse/MEV-601 Project: Maven Evangelism Issue Type: Bug Components: Invalid Metadata Reporter: Holger Brands version 1.1b is deployed to http://repo1.maven.org/maven2/net/sf/hibernate4gwt/hibernate4gwt/1.1/ instead of http://repo1.maven.org/maven2/net/sf/hibernate4gwt/hibernate4gwt/1.1b/ which leads to download failure. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNGSITE-67) Dead link in the getting started guide (Intro to dependency management)
[ http://jira.codehaus.org/browse/MNGSITE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MNGSITE-67. -- Assignee: Dennis Lundberg Resolution: Fixed Thanks for pointing out this error. Fixed in r694953. > Dead link in the getting started guide (Intro to dependency management) > --- > > Key: MNGSITE-67 > URL: http://jira.codehaus.org/browse/MNGSITE-67 > Project: Maven 2 Project Web Site > Issue Type: Bug >Reporter: Gareth Thomas >Assignee: Dennis Lundberg >Priority: Minor > > The link found in the first paragraph under [this > section|http://maven.apache.org/guides/getting-started/index.html#How_do_I_use_external_dependencies] > in the getting started guide has a dead link. The link has label text of > 'Introduction the to Dependency Management' that leads to [this > page|http://maven.apache.org/guides/introduction/introduction-to-dependency-management.html] > and a 404 error. Sorry, but I'm not familiar with the site enouh to find a > suitable replacement link. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRESOURCES-8) maven-resources-plugin ignores configuration/resources property (add a new mojo to copy resources)
[
http://jira.codehaus.org/browse/MRESOURCES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147878#action_147878
]
Olivier Lamy commented on MRESOURCES-8:
---
Do we have to attach this mojo to phase ?
IHMO no.
But comments are welcome :-)
Thanks!
> maven-resources-plugin ignores configuration/resources property (add a new
> mojo to copy resources)
> --
>
> Key: MRESOURCES-8
> URL: http://jira.codehaus.org/browse/MRESOURCES-8
> Project: Maven 2.x Resources Plugin
> Issue Type: New Feature
>Affects Versions: 2.1, 2.2
>Reporter: Leszek Gawron
>Assignee: Olivier Lamy
> Fix For: 2.3
>
> Attachments: example.zip, MRESOURCES-8-workaround.patch, pom.xml
>
>
> I am evaluating maven + eclipse combo. In a trivial POM filtered resources
> exist only in target/classes. If one executes Project -> Clean under eclipse
> this information is lost. If filtered resources would appear as source folder
> they would survive cleaning and not got overriden by unfiltered ones.
> I have been trying to implement a scenario which would allow filtered
> resources to appear as "static" source folder under eclipse.
> The POM explains it best:
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.mobilebox.squash.client
> squash-client
> jar
> 1.0-SNAPSHOT
> Maven Quick Start Archetype
> http://maven.apache.org
>
>
>
> maven-resources-plugin
>
>
> prefilter-resources
> generate-resources
>
> resources
>
>
> target/generated-resources
>
>
> src/main/resource-templates
> true
>
>
>
>
>
>
>
>
> ${ffile}
>
>
>
> src/main/resources
>
>
> target/generated-resources
>
>
>
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
> filter.properties
>
>
> {code}
> thing is this part:
> {code:xml}
>
>
> src/main/properties
> true
>
>
> {code}
> is completely ignored. Instead for both maven-resource-plugin executions (the
> one in generate-resources phase and the default one) this config is used:
> {code:xml}
>
>
> src/main/resources
>
>
> target/generated-resources
>
>
> {code}
> which of course breaks the whole idea.
> Is this a bug or a design decision. In latter case is there any equivalent
> approach I might take?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-602) Upload bundle org.umlgraph.doclet 5.1
Upload bundle org.umlgraph.doclet 5.1 - Key: MEV-602 URL: http://jira.codehaus.org/browse/MEV-602 Project: Maven Evangelism Issue Type: Task Reporter: David J. M. Karlsen Upload bundle for umlgraph 5.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MEV-602) Upload bundle org.umlgraph.doclet 5.1
[ http://jira.codehaus.org/browse/MEV-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen updated MEV-602: Attachment: org.umlgraph.doclet-5.1.zip Ready upload bundle > Upload bundle org.umlgraph.doclet 5.1 > - > > Key: MEV-602 > URL: http://jira.codehaus.org/browse/MEV-602 > Project: Maven Evangelism > Issue Type: Task >Reporter: David J. M. Karlsen > Attachments: org.umlgraph.doclet-5.1.zip > > > Upload bundle for umlgraph 5.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHARED-63) Filtering Resources does not match patterns strictly
[
http://jira.codehaus.org/browse/MSHARED-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147883#action_147883
]
Walter White commented on MSHARED-63:
-
Yes, I tested this and it appears to work great now. Thanks much!
-Walter
> Filtering Resources does not match patterns strictly
>
>
> Key: MSHARED-63
> URL: http://jira.codehaus.org/browse/MSHARED-63
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
>Affects Versions: maven-filtering-1.0-beta-1
>Reporter: Walter White
>Assignee: Olivier Lamy
>
> When using Maven Filtering, maven-war-plugin, variables within the JSP that
> do not correspond to configured properties are updated as well ie.
> [code]
> ${users.id}
> ${user.id}
> ${adfadfadf.id}
> [/code]
> All of those patterns are matched to the project id which causes the JSP
> throw an exception. Having these properties set at build time lets me
> configure the context.path and links dynamically depending on the
> environment. The problem appears to be associated with the plexus pattern
> matching plugin as it is what decides to match any variable ending in .id
> I suggest that an option is added to configure which patterns are matched and
> if the pattern matching is strict. For example, in my JSPs, it would be
> ideal to only allow @context.path@ and not ${users.id} so the variables
> within the JSP remain just that and configured properties are updated
> accordingly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2202) XML Tool 1.0
XML Tool 1.0 Key: MAVENUPLOAD-2202 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2202 Project: Maven Upload Requests Issue Type: Wish Reporter: Mathieu Carbou Attachments: xmltool-1.0-bundle.jar XML Tool is a library to build and manage XML and XPath through a Fluent Interface I am the project owner of XML Tool. Thank you, Mathieu Carbou. -- 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] Moved: (MAVENUPLOAD-2203) Upload bundle org.umlgraph.doclet 5.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MEV-602 to MAVENUPLOAD-2203: Bundle URL: http://www.umlgraph.org/download.html Project URL: http://www.umlgraph.org/ Workflow: Maven New (was: jira) Key: MAVENUPLOAD-2203 (was: MEV-602) Project: Maven Upload Requests (was: Maven Evangelism) > Upload bundle org.umlgraph.doclet 5.1 > - > > Key: MAVENUPLOAD-2203 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2203 > Project: Maven Upload Requests > Issue Type: Task >Reporter: David J. M. Karlsen > Attachments: org.umlgraph.doclet-5.1.zip > > > Upload bundle for umlgraph 5.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSHARED-67) Add a parameter to force overwrite existing files even if the destination files are newer
[ http://jira.codehaus.org/browse/MSHARED-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MSHARED-67. --- Resolution: Fixed fixed in rev 695031 > Add a parameter to force overwrite existing files even if the destination > files are newer > - > > Key: MSHARED-67 > URL: http://jira.codehaus.org/browse/MSHARED-67 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-filtering >Affects Versions: maven-filtering-1.0-beta-1 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: maven-filtering-1.0-beta-2 > > > During resources processing it's not possible to overwrite existing files > when the destination file is newer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRESOURCES-8) maven-resources-plugin ignores configuration/resources property (add a new mojo to copy resources)
[
http://jira.codehaus.org/browse/MRESOURCES-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MRESOURCES-8.
-
Resolution: Fixed
junits, its and example in site are ok.
> maven-resources-plugin ignores configuration/resources property (add a new
> mojo to copy resources)
> --
>
> Key: MRESOURCES-8
> URL: http://jira.codehaus.org/browse/MRESOURCES-8
> Project: Maven 2.x Resources Plugin
> Issue Type: New Feature
>Affects Versions: 2.1, 2.2
>Reporter: Leszek Gawron
>Assignee: Olivier Lamy
> Fix For: 2.3
>
> Attachments: example.zip, MRESOURCES-8-workaround.patch, pom.xml
>
>
> I am evaluating maven + eclipse combo. In a trivial POM filtered resources
> exist only in target/classes. If one executes Project -> Clean under eclipse
> this information is lost. If filtered resources would appear as source folder
> they would survive cleaning and not got overriden by unfiltered ones.
> I have been trying to implement a scenario which would allow filtered
> resources to appear as "static" source folder under eclipse.
> The POM explains it best:
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.mobilebox.squash.client
> squash-client
> jar
> 1.0-SNAPSHOT
> Maven Quick Start Archetype
> http://maven.apache.org
>
>
>
> maven-resources-plugin
>
>
> prefilter-resources
> generate-resources
>
> resources
>
>
> target/generated-resources
>
>
> src/main/resource-templates
> true
>
>
>
>
>
>
>
>
> ${ffile}
>
>
>
> src/main/resources
>
>
> target/generated-resources
>
>
>
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
> filter.properties
>
>
> {code}
> thing is this part:
> {code:xml}
>
>
> src/main/properties
> true
>
>
> {code}
> is completely ignored. Instead for both maven-resource-plugin executions (the
> one in generate-resources phase and the default one) this config is used:
> {code:xml}
>
>
> src/main/resources
>
>
> target/generated-resources
>
>
> {code}
> which of course breaks the whole idea.
> Is this a bug or a design decision. In latter case is there any equivalent
> approach I might take?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRESOURCES-21) when pom specifies multiple resource directories, the directories should be copied in the order they are in the pom
[ http://jira.codehaus.org/browse/MRESOURCES-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRESOURCES-21. -- Resolution: Fixed fixed in rev 695036. There is now a flag called overwrite in the mojo and is false by default (you have to change it manually to true) IMHO this flag can be added in the Resource class but it's an other story :-) > when pom specifies multiple resource directories, the directories should be > copied in the order they are in the pom > --- > > Key: MRESOURCES-21 > URL: http://jira.codehaus.org/browse/MRESOURCES-21 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Ian Springer >Assignee: Olivier Lamy > Fix For: 2.3 > > > It should be possible to control the order in which resource directories are > copied to target/classes, since multiple resource dirs could potentially > contain files with the same names. The intutive thing would be to copy the > resource directories in the order they are specified in the POM (i.e. last > one wins). However, it appears the resources are currently copied in reverse > order (i.e. first one wins). -- 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
