[jira] Created: (SCM-463) Allow builds with Modello 1.0
Allow builds with Modello 1.0 - Key: SCM-463 URL: http://jira.codehaus.org/browse/SCM-463 Project: Maven SCM Issue Type: Improvement Components: Technical tasks Affects Versions: 1.2 Environment: Debian Reporter: Ludovic Claude Priority: Trivial Attachments: modello-xsd.diff The Debian project packages a minimal set of Java software and tries to keep only one version of each library in its repository. The latest version of Modello packaged for Debian is 1.0, and when building Maven SCM against this version, the build fails when generating the XSD files from Modello. I have made a patch which fixes this issue, it tries to follow the conventions used in Doxia, but you'd better have a look at my choice of namespaces. Ludovic -- 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-4071) Support additional read-only local repositories
[ http://jira.codehaus.org/browse/MNG-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168267#action_168267 ] Ludovic Claude commented on MNG-4071: - When building a Debian package with Maven, the Debian policies prevent from downloading anything from the Internet. So you need to run Maven with the --offline option, which disables all remote repositories, regardless of their actual location. > Support additional read-only local repositories > --- > > Key: MNG-4071 > URL: http://jira.codehaus.org/browse/MNG-4071 > Project: Maven 2 > Issue Type: Wish > Components: Artifacts and Repositories >Affects Versions: 3.0-alpha-3 > Environment: Debian Linux in particular, any other environment >Reporter: Ludovic Claude >Priority: Minor > > Work is under way at Debian to support Maven as a tool for building packaged > software. > Debian uses a local Maven repository (in /usr/share/maven-repo/) which is > updated by the Debian tools (dpkg, apt-get). This repository is read-only for > the normal user. > It would be great if users could use this repository in addition to their > local repository in ~/.m2/repo, and it would simplify the Debian tooling. > In Debian, when building a package you cannot download anything from the > Internet (to allow repeatable builds), so when packaging a Maven project, the > --offline option is always used. That means that if you try to trick Maven > and use file:///usr/share/maven-repo as a new repository, then it won't work > as Maven believes that it is a remote repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4071) Support additional read-only local repositories
Support additional read-only local repositories --- Key: MNG-4071 URL: http://jira.codehaus.org/browse/MNG-4071 Project: Maven 2 Issue Type: Wish Components: Artifacts and Repositories Affects Versions: 3.0-alpha-3 Environment: Debian Linux in particular, any other environment Reporter: Ludovic Claude Priority: Minor Work is under way at Debian to support Maven as a tool for building packaged software. Debian uses a local Maven repository (in /usr/share/maven-repo/) which is updated by the Debian tools (dpkg, apt-get). This repository is read-only for the normal user. It would be great if users could use this repository in addition to their local repository in ~/.m2/repo, and it would simplify the Debian tooling. In Debian, when building a package you cannot download anything from the Internet (to allow repeatable builds), so when packaging a Maven project, the --offline option is always used. That means that if you try to trick Maven and use file:///usr/share/maven-repo as a new repository, then it won't work as Maven believes that it is a remote repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEJB-27) duplicated ejb-jar.xml
[ http://jira.codehaus.org/browse/MEJB-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149391#action_149391 ] Ludovic Claude commented on MEJB-27: Why is there no fast-fail in the Ejb plugin when you try to add a lowercase meta-inf/ folder from the resources? This would avoid this type of issues completely. > duplicated ejb-jar.xml > -- > > Key: MEJB-27 > URL: http://jira.codehaus.org/browse/MEJB-27 > Project: Maven 2.x Ejb Plugin > Issue Type: Bug >Affects Versions: 2.0, 2.1 > Environment: Windows XP, jdk 1.4.2, maven 2.0.7 >Reporter: Stefan Chis > Attachments: trainingwall_mdb-1.0.0.jar > > > The ejb-jar.xml descriptor is duplicated in the generated jar file (the ejb > archive). The project is a J2EE multi-module project. The weird thing, is > this project is the only one affected, other J2EE multi-module project are > built just fine. > Anyway, I am attaching the generated artifact, as evidence of the problem. > Also, here is the relevant snippet from the child pom: > > > src/main/resources/meta-inf > meta-inf > > > > > org.apache.maven.plugins > maven-ejb-plugin > > > >true > > > > > > Problem affects the versions 2.0, 2.1of the ejb plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPLUGIN-106) remove no mojo deprecation warning and throw an exception
[ http://jira.codehaus.org/browse/MPLUGIN-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129551#action_129551 ] Ludovic Claude commented on MPLUGIN-106: I've got some reservation on throwing an exception, see MPLUGIN-109. Basically, which packaging should I use for a Maven plugin which doesn't define any Mojo but define a custom packaging with Plexus? > remove no mojo deprecation warning and throw an exception > - > > Key: MPLUGIN-106 > URL: http://jira.codehaus.org/browse/MPLUGIN-106 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Components: Plugin Plugin >Affects Versions: 2.4.1 >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 2.5 > > > MPLUGIN-103 (was MNG-1889) suddenly changed functionality that broke existing > builds resulting in MPLUGIN-102. We restored the old functionality with a > deprecation warning and commented out the test. Remove this in the next > release and make it fail the build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPLUGIN-109) Misleading warning when creating a Maven plugin defining a custom packaging
Misleading warning when creating a Maven plugin defining a custom packaging --- Key: MPLUGIN-109 URL: http://jira.codehaus.org/browse/MPLUGIN-109 Project: Maven 2.x Plugin Tools Issue Type: Bug Components: Plugin Plugin Affects Versions: 2.4.1 Reporter: Ludovic Claude Priority: Minor Attachments: console.log, test-custom-packaging.zip When creating a custom packaging using the 2.4.1 version of the maven-plugin-plugin, I'm getting the following warning message: [INFO] Building foobar-maven-plugin [INFO]task-segment: [install] [INFO] [INFO] [plugin:descriptor] [INFO] Using 2 extractors. [INFO] Applying extractor for language: java [INFO] Extractor for language: java found 0 mojo descriptors. [INFO] Applying extractor for language: bsh [INFO] Extractor for language: bsh found 0 mojo descriptors. [WARNING] [WARNING] [WARNING] *** [WARNING] Deprecation Alert: [WARNING] No mojo descriptors were found in this project which has a packaging type of maven-plugin. [WARNING] In future versions of the plugin tools, this will fail the build. [WARNING] If this project is an archetype, change the packaging type from maven-plugin to maven-archetype. [WARNING] Indeed, my project contains no Mojos, only a plexus components.xml file. Now if you try to enforce a rule that says that a maven-plugin must contain at least one Mojo (see MPLUGIN-106), that's fine, but which packaging am I supposed to use to create a plugin that defines a new packaging (here, the foobar packaging) -- 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: (MPLUGIN-37) parent with multi-type mojo children does not build ant mojo
[ http://jira.codehaus.org/browse/MPLUGIN-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ludovic Claude updated MPLUGIN-37: -- Attachment: antmojofix.zip Fix for the MPLUGIN-37 bug, you need to specify explicitly the right mix of versions for plugins and dependencies > parent with multi-type mojo children does not build ant mojo > > > Key: MPLUGIN-37 > URL: http://jira.codehaus.org/browse/MPLUGIN-37 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Environment: linux >Reporter: M. van der Plas > Attachments: antmojobug.tgz, antmojofix.zip > > > I've a parent with two childeren. Both are mojos. One is a java mojo, the > other is an ant mojo. > When I run mvn clean install in the parent, the ant mojo is not build > correctly. > To reproduce use the project in the attached tgz file: > tar -zxvf antmojobug.tgz > cd antmojobug > mvn clean install. > Observe that ant-child/target/classes only contains a META-INF directory. The > file test.build.xml is missing. > I notice that the mvn output gives: > ... > [INFO] [plugin:descriptor] > [INFO] Using 2 extractors. > [INFO] Applying extractor for language: java > [INFO] Extractor for language: java found 0 mojo descriptors. > [INFO] Applying extractor for language: bsh > [INFO] Extractor for language: bsh found 0 mojo descriptors. > ... > When I run mvn clean install in the ant-mojo directory I get a proper mojo > and the output is : > ... > [INFO] [plugin:descriptor] > [INFO] Using 3 extractors. > [INFO] Applying extractor for language: java > [INFO] Extractor for language: java found 0 mojo descriptors. > [INFO] Applying extractor for language: bsh > [INFO] Extractor for language: bsh found 0 mojo descriptors. > [INFO] Applying extractor for language: ant > [INFO] Extractor for language: ant found 1 mojo descriptors. > ... > When the order of modules in the parent pom is reversed, the ant mojo is > correctly build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPLUGIN-37) parent with multi-type mojo children does not build ant mojo
[ http://jira.codehaus.org/browse/MPLUGIN-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129283#action_129283 ] Ludovic Claude commented on MPLUGIN-37: --- I had the same issue when I want to build a collection of plugins containing a mix of Ant and Java mojos. I found that the issue comes actually from the version of the dependencies and plugins used. When you specify the right mix of versions, it works properly. See attached file for the fix. Ludovic > parent with multi-type mojo children does not build ant mojo > > > Key: MPLUGIN-37 > URL: http://jira.codehaus.org/browse/MPLUGIN-37 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Environment: linux >Reporter: M. van der Plas > Attachments: antmojobug.tgz > > > I've a parent with two childeren. Both are mojos. One is a java mojo, the > other is an ant mojo. > When I run mvn clean install in the parent, the ant mojo is not build > correctly. > To reproduce use the project in the attached tgz file: > tar -zxvf antmojobug.tgz > cd antmojobug > mvn clean install. > Observe that ant-child/target/classes only contains a META-INF directory. The > file test.build.xml is missing. > I notice that the mvn output gives: > ... > [INFO] [plugin:descriptor] > [INFO] Using 2 extractors. > [INFO] Applying extractor for language: java > [INFO] Extractor for language: java found 0 mojo descriptors. > [INFO] Applying extractor for language: bsh > [INFO] Extractor for language: bsh found 0 mojo descriptors. > ... > When I run mvn clean install in the ant-mojo directory I get a proper mojo > and the output is : > ... > [INFO] [plugin:descriptor] > [INFO] Using 3 extractors. > [INFO] Applying extractor for language: java > [INFO] Extractor for language: java found 0 mojo descriptors. > [INFO] Applying extractor for language: bsh > [INFO] Extractor for language: bsh found 0 mojo descriptors. > [INFO] Applying extractor for language: ant > [INFO] Extractor for language: ant found 1 mojo descriptors. > ... > When the order of modules in the parent pom is reversed, the ant mojo is > correctly build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-125) Build-classpath should store the classpath in a Filter
Build-classpath should store the classpath in a Filter
--
Key: MDEP-125
URL: http://jira.codehaus.org/browse/MDEP-125
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Components: build-classpath
Affects Versions: 2.0-alpha-4
Reporter: Ludovic Claude
Assignee: Brian Fox
I have some web.xml files which contain in their environment parameters a list
of jars to be downloaded by the client applets, for example:
Shared jars parameter
applet/shared_jars
ejb.jar, axis.jar, axis-ant.jar, jaxrpc.jar,
saaj.jar, wsdl4j.jar, commons-discovery.jar, commons-logging.jar,
[...]
java.lang.String
(don't ask me why it's done like that, it's legacy software...)
It would be great to be able to isolate this list of jars in a project, and
then create from that project the classpath, store it in a filter which can
then be applied on the web.xml file.
Then I could rewrite my web.xml like this:
Shared jars parameter
applet/shared_jars
${shared.jars}
java.lang.String
The list of shared jars would be defined in a new shared-jars project, which
would list the shared jars in its dependencies section, in pure Maven style ;-)
Thanks,
Ludovic
--
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: (MWAR-134) ClasscastException when turning filtering on the web resources
[ http://jira.codehaus.org/browse/MWAR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116128 ] Ludovic Claude commented on MWAR-134: - Update: I had this filtering issue because some developer put png images in the src/main/webapp folder. Once they are removed, then the filtering kind of works, if it were not for the issue mentioned above. Ludovic. > ClasscastException when turning filtering on the web resources > -- > > Key: MWAR-134 > URL: http://jira.codehaus.org/browse/MWAR-134 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: Maven 2.0.8, Win XP >Reporter: Ludovic Claude > > Hello, > I have configured the maven-war-plugin to filter my files in src/main/webapp, > in particular web.xml. > > org.apache.maven.plugins > maven-war-plugin > > > > false > > > > > true > > src/main/webapp > > > **/* > > > > > > But when I run Maven, I get the following error: > [INFO] Copy webapp webResources to [...]\client-framework-webapp-0.2-SNAPSHOT > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] org.apache.maven.project.MavenProject > [INFO] > > [INFO] Trace > java.lang.ClassCastException: org.apache.maven.project.MavenProject > at > org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:269) > at > org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:162) > at java.io.Reader.read(Reader.java:100) > at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:212) > at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:200) > at > org.apache.maven.plugin.war.AbstractWarMojo.copyFilteredFile(AbstractWarMojo.java:921) > at > org.apache.maven.plugin.war.AbstractWarMojo.copyResources(AbstractWarMojo.java:415) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:518) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:347) > at > org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:164) > at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:130) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > > Any idea? > Thanks, > Ludov
[jira] Commented: (MWAR-134) ClasscastException when turning filtering on the web resources
[
http://jira.codehaus.org/browse/MWAR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116123
]
Ludovic Claude commented on MWAR-134:
-
Hello Olivier,
I'm using version 2.0.2 of the war plugin. If I upgrade to 2.1-alpha-1, then
the build doesn't fail any more, but it still doesn't do what I want:
I have the following line in my web.xml file:
Myapp version ${app.version} - Login module
In a paren POM, app.version is set to 7, while the current project version is
0.2-snapshot. Now the filter replaces ${app.version} with the value of
${version} or ${project.version}...
Myapp version 0.2-SNAPSHOT - Login module
So it looks like I'm hitting now the MWAR-133 issue...
Thanks for your help,
Ludovic
> ClasscastException when turning filtering on the web resources
> --
>
> Key: MWAR-134
> URL: http://jira.codehaus.org/browse/MWAR-134
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.0.2
> Environment: Maven 2.0.8, Win XP
>Reporter: Ludovic Claude
>
> Hello,
> I have configured the maven-war-plugin to filter my files in src/main/webapp,
> in particular web.xml.
>
> org.apache.maven.plugins
> maven-war-plugin
>
>
>
> false
>
>
>
>
> true
>
> src/main/webapp
>
>
> **/*
>
>
>
>
>
> But when I run Maven, I get the following error:
> [INFO] Copy webapp webResources to [...]\client-framework-webapp-0.2-SNAPSHOT
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] org.apache.maven.project.MavenProject
> [INFO]
>
> [INFO] Trace
> java.lang.ClassCastException: org.apache.maven.project.MavenProject
> at
> org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:269)
> at
> org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:162)
> at java.io.Reader.read(Reader.java:100)
> at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:212)
> at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:200)
> at
> org.apache.maven.plugin.war.AbstractWarMojo.copyFilteredFile(AbstractWarMojo.java:921)
> at
> org.apache.maven.plugin.war.AbstractWarMojo.copyResources(AbstractWarMojo.java:415)
> at
> org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:518)
> at
> org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:347)
> at
> org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:164)
> at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:130)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.codehaus.classworlds.Launcher.launchEnhanced(La
[jira] Commented: (MWAR-134) ClasscastException when turning filtering on the web resources
[
http://jira.codehaus.org/browse/MWAR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116066
]
Ludovic Claude commented on MWAR-134:
-
I did a bit of debugging, so here are my results:
* the filter scans all files in src/main/webapp, and this includes JSP pages
with tags like <%@ taglib ... />
* in InterpolationFilterReader.read(), the key value is "@", and the
variableKey is ""
* for some reason, variables.get("") returns a MavenProject instance
In fact, the problem comes from the fact that plexus.utils 1.0.2 is used by the
war plugin, while a more recent version of plexus.utils such as 1.2 doesn't try
to cast directly the value returned by variables.get() to a String.
So the fix is quite simple here: use plexus 1.2 or better!
> ClasscastException when turning filtering on the web resources
> --
>
> Key: MWAR-134
> URL: http://jira.codehaus.org/browse/MWAR-134
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.0.2
> Environment: Maven 2.0.8, Win XP
>Reporter: Ludovic Claude
>
> Hello,
> I have configured the maven-war-plugin to filter my files in src/main/webapp,
> in particular web.xml.
>
> org.apache.maven.plugins
> maven-war-plugin
>
>
>
> false
>
>
>
>
> true
>
> src/main/webapp
>
>
> **/*
>
>
>
>
>
> But when I run Maven, I get the following error:
> [INFO] Copy webapp webResources to [...]\client-framework-webapp-0.2-SNAPSHOT
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] org.apache.maven.project.MavenProject
> [INFO]
>
> [INFO] Trace
> java.lang.ClassCastException: org.apache.maven.project.MavenProject
> at
> org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:269)
> at
> org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:162)
> at java.io.Reader.read(Reader.java:100)
> at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:212)
> at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:200)
> at
> org.apache.maven.plugin.war.AbstractWarMojo.copyFilteredFile(AbstractWarMojo.java:921)
> at
> org.apache.maven.plugin.war.AbstractWarMojo.copyResources(AbstractWarMojo.java:415)
> at
> org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:518)
> at
> org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:347)
> at
> org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:164)
> at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:130)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.codehaus.classwor
[jira] Created: (MWAR-134) ClasscastException when turning filtering on the web resources
ClasscastException when turning filtering on the web resources -- Key: MWAR-134 URL: http://jira.codehaus.org/browse/MWAR-134 Project: Maven 2.x War Plugin Issue Type: Bug Affects Versions: 2.0.2 Environment: Maven 2.0.8, Win XP Reporter: Ludovic Claude Hello, I have configured the maven-war-plugin to filter my files in src/main/webapp, in particular web.xml. org.apache.maven.plugins maven-war-plugin false true src/main/webapp **/* But when I run Maven, I get the following error: [INFO] Copy webapp webResources to [...]\client-framework-webapp-0.2-SNAPSHOT [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.project.MavenProject [INFO] [INFO] Trace java.lang.ClassCastException: org.apache.maven.project.MavenProject at org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:269) at org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:162) at java.io.Reader.read(Reader.java:100) at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:212) at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:200) at org.apache.maven.plugin.war.AbstractWarMojo.copyFilteredFile(AbstractWarMojo.java:921) at org.apache.maven.plugin.war.AbstractWarMojo.copyResources(AbstractWarMojo.java:415) at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:518) at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:347) at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:164) at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:130) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] Any idea? Thanks, Ludovic -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-85) Generated POM.xml should keep comments
Generated POM.xml should keep comments -- Key: ARCHETYPE-85 URL: http://jira.codehaus.org/browse/ARCHETYPE-85 Project: Maven Archetype Issue Type: Improvement Affects Versions: 1.0-alpha-4 Environment: Win XP, Maven 2.0.7 Reporter: Ludovic Claude Priority: Minor I'm writting some custom archetype for my projects. In the POM.xml template file, I want to put some comments that would be useful for those developers who don't know Maven and to guide them. Something like: [...] Unfortunately, the whole tag is removed from the generated pom.xml file. It would be nice to have a templating mechanism that's able to keep those comments. Thanks, Ludovic -- 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: (SCM-278) NPE when running changelog
[
http://jira.codehaus.org/browse/SCM-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86992
]
Ludovic Claude commented on SCM-278:
Adding the following lines to VssHistoryCommand.java takes care of this issue.
It works well for me, builds are now executed when there are modifications in
the VSS repository.
//Display only versions that fall within specified data range.
if ( startDate != null )
{
+ if (endDate == null)
+ {
+ endDate = new Date(); // = now
+ }
SimpleDateFormat sdf = new SimpleDateFormat( "dd/MM/",
Locale.ENGLISH );
String dateRange = sdf.format( endDate ) + "~" + sdf.format(
startDate );
command.createArgument().setValue( VssConstants.FLAG_VERSION_DATE +
dateRange );
}
return command;
> NPE when running changelog
> --
>
> Key: SCM-278
> URL: http://jira.codehaus.org/browse/SCM-278
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-vss
> Environment: SourceSafe 6.0d, Win XP
>Reporter: Ludovic Claude
>
> Hello,
> I have the following error when I try to update an existing project with
> Continuum. The first checkout of the project works fine, but when I modify
> some sources in VSS, I get this error. Forcing the build a second time works
> fine, so it's not a showstopper bug.
> org.apache.maven.continuum.scm.ContinuumScmException: Error while update
> sources.
> at
> org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:272)
> at
> org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:58)
> at
> org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:166)
> at
> org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47)
> at
> org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103)
> at java.lang.Thread.run(Thread.java:534)
> Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM
> command.
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
> at
> org.apache.maven.scm.provider.vss.VssScmProvider.update(VssScmProvider.java:209)
> at
> org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:386)
> at
> org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:363)
> at
> org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:242)
> ... 5 more
> Caused by: java.lang.NullPointerException
> at java.util.Calendar.setTime(Calendar.java:902)
> at java.text.SimpleDateFormat.format(SimpleDateFormat.java:782)
> at java.text.SimpleDateFormat.format(SimpleDateFormat.java:775)
> at java.text.DateFormat.format(DateFormat.java:314)
> at
> org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.buildCmdLine(VssHistoryCommand.java:114)
> at
> org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.executeChangeLogCommand(VssHistoryCommand.java:52)
> at
> org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand(AbstractChangeLogCommand.java:91)
> at
> org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:63)
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:55)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-278) NPE when running changelog
NPE when running changelog -- Key: SCM-278 URL: http://jira.codehaus.org/browse/SCM-278 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-vss Environment: SourceSafe 6.0d, Win XP Reporter: Ludovic Claude Hello, I have the following error when I try to update an existing project with Continuum. The first checkout of the project works fine, but when I modify some sources in VSS, I get this error. Forcing the build a second time works fine, so it's not a showstopper bug. org.apache.maven.continuum.scm.ContinuumScmException: Error while update sources. at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:272) at org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:58) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:166) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:534) Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) at org.apache.maven.scm.provider.vss.VssScmProvider.update(VssScmProvider.java:209) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:386) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:363) at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:242) ... 5 more Caused by: java.lang.NullPointerException at java.util.Calendar.setTime(Calendar.java:902) at java.text.SimpleDateFormat.format(SimpleDateFormat.java:782) at java.text.SimpleDateFormat.format(SimpleDateFormat.java:775) at java.text.DateFormat.format(DateFormat.java:314) at org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.buildCmdLine(VssHistoryCommand.java:114) at org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.executeChangeLogCommand(VssHistoryCommand.java:52) at org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand(AbstractChangeLogCommand.java:91) at org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:63) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:55) -- 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
