[jira] (ARCHETYPE-412) Cannot create project archétype with parent directory structure
Lefebvre JF created ARCHETYPE-412: - Summary: Cannot create project archétype with parent directory structure Key: ARCHETYPE-412 URL: https://jira.codehaus.org/browse/ARCHETYPE-412 Project: Maven Archetype Issue Type: Bug Affects Versions: 2.2 Reporter: Lefebvre JF Error when archetype:generate for project with structure like this |-parent |--- pom.xml |-child |---pom.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSOURCES-59) Bas génération of jar if filter ressources actvated
Lefebvre JF created MSOURCES-59: --- Summary: Bas génération of jar if filter ressources actvated Key: MSOURCES-59 URL: https://jira.codehaus.org/browse/MSOURCES-59 Project: Maven 2.x Source Plugin Issue Type: Bug Affects Versions: 2.1.2 Reporter: Lefebvre JF Priority: Critical If filter ressources is activated the jar content is ni bad format (jar and test-jar): JarFile |-.. <- due to filter ressource |-com -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-189) add java 5 annotations support to mark Mojo sources
[ https://jira.codehaus.org/browse/MPLUGIN-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MPLUGIN-189: - Fix Version/s: 3.0 Assignee: Olivier Lamy > add java 5 annotations support to mark Mojo sources > --- > > Key: MPLUGIN-189 > URL: https://jira.codehaus.org/browse/MPLUGIN-189 > Project: Maven 2.x Plugin Tools > Issue Type: New Feature > Components: Java Plugins >Affects Versions: 2.9 >Reporter: Herve Boutemy >Assignee: Olivier Lamy > Fix For: 3.0 > > > replacing javadoc annotations with Java 5 annotations will improve the build > process, like it has been done for [Plexus > annotations|http://plexus.codehaus.org/plexus-containers/plexus-component-annotations/] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-189) add java 5 annotations support to mark Mojo sources
[ https://jira.codehaus.org/browse/MPLUGIN-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MPLUGIN-189. Resolution: Fixed done > add java 5 annotations support to mark Mojo sources > --- > > Key: MPLUGIN-189 > URL: https://jira.codehaus.org/browse/MPLUGIN-189 > Project: Maven 2.x Plugin Tools > Issue Type: New Feature > Components: Java Plugins >Affects Versions: 2.9 >Reporter: Herve Boutemy >Assignee: Olivier Lamy > Fix For: 3.0 > > > replacing javadoc annotations with Java 5 annotations will improve the build > process, like it has been done for [Plexus > annotations|http://plexus.codehaus.org/plexus-containers/plexus-component-annotations/] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-187) plugin:report fails with maven-plugin-plugin 2.9
[
https://jira.codehaus.org/browse/MPLUGIN-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MPLUGIN-187:
-
Fix Version/s: 3.0
> plugin:report fails with maven-plugin-plugin 2.9
>
>
> Key: MPLUGIN-187
> URL: https://jira.codehaus.org/browse/MPLUGIN-187
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 2.9
> Environment: $ mvn -version
> Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: /opt/apache-maven
> Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.0.0-11-generic-pae", arch: "i386", family:
> "unix"
>Reporter: Hugo Josefson
>Assignee: Robert Scholte
> Fix For: 2.10, 3.0
>
>
> When I use maven-plugin-plugin 2.9, I can't run {{mvn plugin:report}}. It
> complains it can't find
> {{org.apache.maven.doxia.module.xhtml.decoration.render.RenderingContext}}
> even though Doxia 1.2 seems to be on the classpath.
> Steps to reproduce:
> {code}
> git clone git://gist.github.com/1247569.git MPLUGIN-187
> cd MPLUGIN-187
> mvn plugin:report
> {code}
> My complete ERROR_LOG.txt is included in the gist.
> (You may also browse the gist and ERROR_LOG.txt at
> https://gist.github.com/1247569 )
> WORKAROUND: maven-plugin-plugin 2.8 still works.
> Am I doing anything wrong, or should this work?
> (FYI, the project we are experiencing this in, is maven-android-plugin, which
> is currently downgraded to maven-plugin-plugin 2.8. Source at
> https://github.com/jayway/maven-android-plugin )
> Thanks,
> Hugo
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-190) @executionStrategy javadoc annotation is not recognized, but @attainAlways is (which is not documented)
[
https://jira.codehaus.org/browse/MPLUGIN-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MPLUGIN-190:
-
Fix Version/s: 3.0
> @executionStrategy javadoc annotation is not recognized, but @attainAlways is
> (which is not documented)
> ---
>
> Key: MPLUGIN-190
> URL: https://jira.codehaus.org/browse/MPLUGIN-190
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Java Plugins
>Affects Versions: 2.9
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
> Fix For: 2.10, 3.0
>
>
> {code:java}/**
> * @goal test
> * @executionStrategy always
> */{code}
> generates
> {code:xml}
>
> test
> once-per-session
>
> {code}
> but {code:java}/**
> * @goal test
> * @attainAlways
> */{code}
> does generate
> {code:xml}
>
> test
> always
>
> {code}
> either both forms should be supported and documented, or only
> @executionStrategy since it is documented in
> http://maven.apache.org/developers/mojo-api-specification.html for a long time
> (notice: I suppose nobody tried to use it...)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSOURCES-59) Bas génération of jar if filter ressources actvated
[
https://jira.codehaus.org/browse/MSOURCES-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MSOURCES-59:
Description:
If filter ressources is activated the jar content is ni bad format (jar and
test-jar):
JarFile
{noformat}
|-.. <- due to filter ressource
|-com
{noformat}
was:
If filter ressources is activated the jar content is ni bad format (jar and
test-jar):
JarFile
|-.. <- due to filter ressource
|-com
> Bas génération of jar if filter ressources actvated
> ---
>
> Key: MSOURCES-59
> URL: https://jira.codehaus.org/browse/MSOURCES-59
> Project: Maven 2.x Source Plugin
> Issue Type: Bug
>Affects Versions: 2.1.2
>Reporter: Lefebvre JF
>Priority: Critical
>
> If filter ressources is activated the jar content is ni bad format (jar and
> test-jar):
> JarFile
> {noformat}
> |-.. <- due to filter ressource
> |-com
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSOURCES-59) Bas génération of jar if filter ressources actvated
[ https://jira.codehaus.org/browse/MSOURCES-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298512#comment-298512 ] Dennis Lundberg commented on MSOURCES-59: - Please supply us with a runnable project that shows your problem. > Bas génération of jar if filter ressources actvated > --- > > Key: MSOURCES-59 > URL: https://jira.codehaus.org/browse/MSOURCES-59 > Project: Maven 2.x Source Plugin > Issue Type: Bug >Affects Versions: 2.1.2 >Reporter: Lefebvre JF >Priority: Critical > > If filter ressources is activated the jar content is ni bad format (jar and > test-jar): > JarFile > |-.. <- due to filter ressource > |-com -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-191) plugin-info.html is not created
[
https://jira.codehaus.org/browse/MPLUGIN-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPLUGIN-191:
--
Description:
During running maven-plugin-plugin:report the following exception occurs:
{noformat}Caused by: java.lang.NoClassDefFoundError:
org/apache/maven/doxia/module/xhtml/decoration/render/RenderingContext
at
org.apache.maven.reporting.sink.SinkFactory.createSink(SinkFactory.java:59)
at
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:85)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
Caused by: java.lang.ClassNotFoundException:
org.apache.maven.doxia.module.xhtml.decoration.render.RenderingContext
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
... 23 more{noformat}
After some debugging it seams to me that the cause is the version of
maven-reporting-impl dependency which is now 2.0.5. I made it work with the
following snippet in my pom.xml:
{code:xml}
org.apache.maven.plugins
maven-plugin-plugin
2.9
report
pre-site
report
org.apache.maven.reporting
maven-reporting-impl
2.2
{code}
After this setting the plugin-info.html file is generated at
target/generated-site/xdoc directory. However nothing is copied to target/site
as the output file should be moved to target/generated-site/xhtml and it should
have the extension .xhtml.vm.
I made the workaround that I copy and rename the html file to
src/site/xhtml/plugin-info.xhtml.vm.
was:
During running maven-plugin-plugin:report the following exception occurs:
Caused by: java.lang.NoClassDefFoundError:
org/apache/maven/doxia/module/xhtml/decoration/render/RenderingContext
at
org.apache.maven.reporting.sink.SinkFactory.createSink(SinkFactory.java:59)
at
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:85)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
Caused by: java.lang.ClassNotFoundException:
org.apache.maven.doxia.module.xhtml.decoration.render.RenderingContext
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
... 23 more
After some debugging it seams to me that the cause is the version of
maven-reporting-impl dependency which is now 2.0.5. I made it work with the
following snippet in my pom.xml:
org.apache.maven.plugins
maven-plugin-plugin
2.9
report
pre-site
report
org.apache.maven.reporting
maven-reporting-impl
2.2
After this setting the plugin-info.html file is generated at
target/generated-site/xdoc directory. However nothing is copied to target/site
as the output file should be moved to target/generated-site/xhtml and it should
have the ex
[jira] (MSKINS-51) Github ribbon image broken
Julien Nicoulaud created MSKINS-51: -- Summary: Github ribbon image broken Key: MSKINS-51 URL: https://jira.codehaus.org/browse/MSKINS-51 Project: Maven Skins Issue Type: Bug Components: Fluido Skin Affects Versions: fluido-1.2.1 Reporter: Julien Nicoulaud The Github ribbon image has changed address (example here: http://nicoulaj.github.com/checksum-maven-plugin) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-187) plugin:report fails with maven-plugin-plugin 2.9
[
https://jira.codehaus.org/browse/MPLUGIN-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298522#comment-298522
]
Herve Boutemy commented on MPLUGIN-187:
---
yes, maven-reporting-impl was upgraded in
[r1164679|http://svn.apache.org/viewvc?rev=1164679] following MPLUGIN-120 Doxia
upgrade
> plugin:report fails with maven-plugin-plugin 2.9
>
>
> Key: MPLUGIN-187
> URL: https://jira.codehaus.org/browse/MPLUGIN-187
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 2.9
> Environment: $ mvn -version
> Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: /opt/apache-maven
> Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.0.0-11-generic-pae", arch: "i386", family:
> "unix"
>Reporter: Hugo Josefson
>Assignee: Robert Scholte
> Fix For: 2.10, 3.0
>
>
> When I use maven-plugin-plugin 2.9, I can't run {{mvn plugin:report}}. It
> complains it can't find
> {{org.apache.maven.doxia.module.xhtml.decoration.render.RenderingContext}}
> even though Doxia 1.2 seems to be on the classpath.
> Steps to reproduce:
> {code}
> git clone git://gist.github.com/1247569.git MPLUGIN-187
> cd MPLUGIN-187
> mvn plugin:report
> {code}
> My complete ERROR_LOG.txt is included in the gist.
> (You may also browse the gist and ERROR_LOG.txt at
> https://gist.github.com/1247569 )
> WORKAROUND: maven-plugin-plugin 2.8 still works.
> Am I doing anything wrong, or should this work?
> (FYI, the project we are experiencing this in, is maven-android-plugin, which
> is currently downgraded to maven-plugin-plugin 2.8. Source at
> https://github.com/jayway/maven-android-plugin )
> Thanks,
> Hugo
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-194) support expression="a property" in addition to expression="${a property}"
Herve Boutemy created MPLUGIN-194:
-
Summary: support expression="a property" in addition to
expression="${a property}"
Key: MPLUGIN-194
URL: https://jira.codehaus.org/browse/MPLUGIN-194
Project: Maven 2.x Plugin Tools
Issue Type: Improvement
Components: maven-plugin-tools-annotations, maven-plugin-tools-java
Affects Versions: 2.9
Reporter: Herve Boutemy
since the value doesn't have any meaning without ${ }, removing them from the
annotation would make things more clear for users
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5162) Maven stuck on downloading dependencies when using java 7.
[
https://jira.codehaus.org/browse/MNG-5162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298549#comment-298549
]
Damien Coraboeuf commented on MNG-5162:
---
{quote}
Setting {{MAVEN_OPTS}} to {{-Djava.net.preferIPv4Stack=true}}
{quote}
It seems to do the trick as well :) I'm back to JDK7.
Thanks,
Damien.
> Maven stuck on downloading dependencies when using java 7.
> --
>
> Key: MNG-5162
> URL: https://jira.codehaus.org/browse/MNG-5162
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.0.1, 3.0.3
> Environment: Windows 7 Professional x64
>Reporter: Lukas Stampf
> Attachments: dump.tdump, edb.zip, java6.jpg, java7.jpg
>
>
> When JAVA_HOME is set to the Java 7 JDK and I run "mvn clean install" on my
> project the following happens:
> Maven downloads the dependencies to my local repository, as usual, but on
> some dependencies he stops while downloading and never continues. He is just
> stuck. I then must use CTRL+C and start from the beginning with my build, but
> it doesnt help because he gets stuck at the same dependencies again. In my
> local repository, where the failed dependency belongs is just a tmp file
> like: org.apache.servicemix.bundles.serp-1.13.1_4.jar.tmp90088a9d7e9e4642
> When I set JAVA_HOME to java 6 Update 27 everything works fine.
> The problem does not seem to be related to JAR size because, I saw it fail on
> 19kb dependencies as well.
> I have the impression it happens mostly to JARs with "long" names.
> Attached you will find a subproject of the project I am working on. it
> contains the org.apache.servicemix.bundles.serp-1.13.1_4 dependency, which is
> one of almost all servicemix bundles that is failing for me, when i use java7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
