[jira] [Created] (MSITE-774) Usage of validate=true lead to "SAX2 driver class org.apache.xerces.parsers.SAXParser not found" exception
Roman Ivanov created MSITE-774:
--
Summary: Usage of validate=true lead to "SAX2 driver class
org.apache.xerces.parsers.SAXParser not found" exception
Key: MSITE-774
URL: https://issues.apache.org/jira/browse/MSITE-774
Project: Maven Site Plugin
Issue Type: Bug
Affects Versions: 3.5.1
Reporter: Roman Ivanov
project: https://github.com/checkstyle/checkstyle
usage of validate=true:
{code}
...
org.apache.maven.plugins
maven-site-plugin
${maven.site.plugin.version}
${basedir}/src/xdocs
true
...
{code}
lead to
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.5.1:site (default-site) on project
checkstyle: Error parsing '~/checkstyle/checkstyle/src/xdocs/anttask.xml.vm':
line [-1] Error validating the model: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.5.1:site (default-site) on project
checkstyle: Error parsing '~/checkstyle/checkstyle/src/xdocs/anttask.xml.vm':
line [-1] Error validating the model: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
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:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error parsing
'~/checkstyle/checkstyle/src/xdocs/anttask.xml.vm': line [-1] Error validating
the model: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
at
org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:140)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error parsing
'~/checkstyle/checkstyle/src/xdocs/anttask.xml.vm': line [-1] Error validating
the model: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:449)
at
org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:329)
at
org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:264)
at
org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:171)
at
org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
... 21 more
Caused by: org.apache.maven.doxia.parser.ParseException: Error validating the
model: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
at
org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:116)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.validate(DefaultSiteRenderer.java:1084)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:414)
... 26
[jira] [Commented] (MINVOKER-150) Results from prior execution are included unless clean build
[ https://issues.apache.org/jira/browse/MINVOKER-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15265558#comment-15265558 ] Hudson commented on MINVOKER-150: - SUCCESS: Integrated in maven-plugins #5831 (See [https://builds.apache.org/job/maven-plugins/5831/]) [MINVOKER-150] Results from prior execution are included unless clean build o Removing of the reportsDirectory is needed cause the results read back from the xml files in reportsDirectory. (khmarbaise: [http://svn.apache.org/viewvc/?view=rev=1741828]) * maven-invoker-plugin/src/main/java/org/apache/maven/plugin/invoker/AbstractInvokerMojo.java > Results from prior execution are included unless clean build > > > Key: MINVOKER-150 > URL: https://issues.apache.org/jira/browse/MINVOKER-150 > Project: Maven Invoker Plugin > Issue Type: Bug >Affects Versions: 1.6, 1.8 > Environment: Maven 3.0.5, Mac OS 10.8.2, Apple JDK 1.6.0 >Reporter: Anders Hammar >Assignee: Karl Heinz Marbaise > Fix For: 3.0.0 > > > When execution a subset of modules/projects without performing a clean build, > build result from prior executions is included in the result which is > confusing. I think that only the executed projects should be included in the > reported result. > To reproduce (on the m-invoker-p source e.g.): > 1. mvn clean install -Prun-its > 2. mvn install -Prun-its -Dinvoker.test=clone-clean -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MINVOKER-150) Results from prior execution are included unless clean build
[ https://issues.apache.org/jira/browse/MINVOKER-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MINVOKER-150: - Fix Version/s: 3.0.0 > Results from prior execution are included unless clean build > > > Key: MINVOKER-150 > URL: https://issues.apache.org/jira/browse/MINVOKER-150 > Project: Maven Invoker Plugin > Issue Type: Bug >Affects Versions: 1.6, 1.8 > Environment: Maven 3.0.5, Mac OS 10.8.2, Apple JDK 1.6.0 >Reporter: Anders Hammar > Fix For: 3.0.0 > > > When execution a subset of modules/projects without performing a clean build, > build result from prior executions is included in the result which is > confusing. I think that only the executed projects should be included in the > reported result. > To reproduce (on the m-invoker-p source e.g.): > 1. mvn clean install -Prun-its > 2. mvn install -Prun-its -Dinvoker.test=clone-clean -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MINVOKER-150) Results from prior execution are included unless clean build
[ https://issues.apache.org/jira/browse/MINVOKER-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MINVOKER-150. Resolution: Fixed Assignee: Karl Heinz Marbaise Fixed in [r1741828|http://svn.apache.org/r1741828] > Results from prior execution are included unless clean build > > > Key: MINVOKER-150 > URL: https://issues.apache.org/jira/browse/MINVOKER-150 > Project: Maven Invoker Plugin > Issue Type: Bug >Affects Versions: 1.6, 1.8 > Environment: Maven 3.0.5, Mac OS 10.8.2, Apple JDK 1.6.0 >Reporter: Anders Hammar >Assignee: Karl Heinz Marbaise > Fix For: 3.0.0 > > > When execution a subset of modules/projects without performing a clean build, > build result from prior executions is included in the result which is > confusing. I think that only the executed projects should be included in the > reported result. > To reproduce (on the m-invoker-p source e.g.): > 1. mvn clean install -Prun-its > 2. mvn install -Prun-its -Dinvoker.test=clone-clean -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MJAVADOC-428) problem with generation link to DefaultHandler
[
https://issues.apache.org/jira/browse/MJAVADOC-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Ivanov resolved MJAVADOC-428.
---
Resolution: Duplicate
duplicate of MJAVADOC-423
> problem with generation link to DefaultHandler
> --
>
> Key: MJAVADOC-428
> URL: https://issues.apache.org/jira/browse/MJAVADOC-428
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10.3
>Reporter: Roman Ivanov
>
> problem is described at https://jira.codehaus.org/browse/MJAVADOC-425
> update for new doxia works well the only issue left is :
> {quote}
> One more case:
> http://docs.oracle.com/javase/7/docs/api/org/xml/sax
> /helpers.DefaultHandler.html?is-external=true: 404 Not Found
> This link is broken because DefaultHandler is preceded by dot instead of '/'.
> {quote}
> Looks like it is not related to doxia version problem, but still a problem.
> You can find that error there -
> http://checkstyle.sourceforge.net/linkcheck.html
> to reproduce that problem please comment out line
> https://github.com/checkstyle/checkstyle/blob/master/pom.xml#L1100
> and run "mvn clean site"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-6008) Aether code import to git
[ https://issues.apache.org/jira/browse/MNG-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6008: --- Description: Need a temporary maven-aether.git repository to start working on license headers etc... while defining if we can continue to use the Aether name If not, in the future, we'll need to rename the repo was: Need a temporary maven-aether.git repository to start working on license headers etc... while defining if we can continue to use the Aether name I not, in the future, we'll need to rename the repo > Aether code import to git > - > > Key: MNG-6008 > URL: https://issues.apache.org/jira/browse/MNG-6008 > Project: Maven > Issue Type: Sub-task >Reporter: Hervé Boutemy > > Need a temporary maven-aether.git repository to start working on license > headers etc... while defining if we can continue to use the Aether name > If not, in the future, we'll need to rename the repo -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6008) Aether code import to git
[ https://issues.apache.org/jira/browse/MNG-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15265494#comment-15265494 ] Hervé Boutemy commented on MNG-6008: https://git-wip-us.apache.org/repos/asf?p=maven-aether.git created > Aether code import to git > - > > Key: MNG-6008 > URL: https://issues.apache.org/jira/browse/MNG-6008 > Project: Maven > Issue Type: Sub-task >Reporter: Hervé Boutemy > > Need a temporary maven-aether.git repository to start working on license > headers etc... while defining if we can continue to use the Aether name > If not, in the future, we'll need to rename the repo -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MJAR-193) Allow other mojos to contribute to the manifest
[ https://issues.apache.org/jira/browse/MJAR-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15265459#comment-15265459 ] Carsten Ziegeler commented on MJAR-193: --- The code example is below, but I agree that this is not the nicest way of doing it. Writing an additional merge mf file sounds fine for me. The code for the plugins I mentioned is at https://github.com/apache/felix/blob/trunk/tools/maven-scr-plugin/src/main/java/org/apache/felix/scrplugin/mojo/SCRDescriptorMojo.java#L462 which sets the property in the project and the following code iterates over all properties and picks the one with the special prefix: https://github.com/apache/felix/blob/trunk/tools/maven-bundle-plugin/src/main/java/org/apache/felix/bundleplugin/BundlePlugin.java#L563 > Allow other mojos to contribute to the manifest > --- > > Key: MJAR-193 > URL: https://issues.apache.org/jira/browse/MJAR-193 > Project: Maven JAR Plugin > Issue Type: Improvement >Reporter: Carsten Ziegeler > Fix For: waiting-for-feedback > > > It would be great to have a programmatic way to add entries to the manifest > from other mojos. The most important client of such a way would be the maven > bundle plugin (from the Apache Felix project) that calculates additional > headers for OSGi bundles. Right now, that bundle does not only do the > calculation but generates the jar file as well. > While a workaround would be to let the bundle plugin generate the full > manifest and configure the jar plugin to use it, this is not very elegant. > Passing down a map of manifest entries from one mojo to the jar plugin would > solve this in a much better way. > And I could imagine that other mojos/plugins might benefit for this as well. > This would be a simple but very convenient enhancement to the plugin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MACR-30) Add LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin
[
https://issues.apache.org/jira/browse/MACR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15265315#comment-15265315
]
Hudson commented on MACR-30:
SUCCESS: Integrated in maven-plugins #5814 (See
[https://builds.apache.org/job/maven-plugins/5814/])
[MACR-30] Add LifecycleMapping and ArtifactHandler from maven-core to target
packaging plugin
o The maven-acr-plugin already had the mapping for a long time
only improved it a little bit.
o Changed the location from src/main/resources to src/main/filtered-resources
instead to make it more clear and using the project.version to always use
the current version of the plugin.
o Added some comments in the components.xml
o Upgraded plugins
o maven-compiler-plugin from 3.3 to 3.5.1
o Using ${project.version} for the acr plugin.
o No need to add a supplemental IT cause they are using already
extensions=true. (khmarbaise:
[http://svn.apache.org/viewvc/?view=rev=1741760])
* maven-acr-plugin/pom.xml
* maven-acr-plugin/src/main/filtered-resources
* maven-acr-plugin/src/main/filtered-resources/META-INF/plexus/components.xml
* maven-acr-plugin/src/main/resources
> Add LifecycleMapping and ArtifactHandler from maven-core to target packaging
> plugin
> ---
>
> Key: MACR-30
> URL: https://issues.apache.org/jira/browse/MACR-30
> Project: Maven ACR Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.1
>
>
> Maven Core shouldn't be aware of this kind of information, instead the
> maven-acr-plugin should specify and maintain the {{LifecycleMapping}} and
> {{ArtifactHandler}} by itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MWAR-326) Add LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin
[
https://issues.apache.org/jira/browse/MWAR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15265305#comment-15265305
]
Hudson commented on MWAR-326:
-
SUCCESS: Integrated in maven-plugins #5813 (See
[https://builds.apache.org/job/maven-plugins/5813/])
[MWAR-326] Add LifecycleMapping and ArtifactHandler from maven-core to target
packaging plugin
o Added components.xml which contains
ArtifactHandler mapping and life cycle mapping and
the appropriate plugin versions.
o Added basic integration tests which checks if
by using the maven-war-plugin with extensions=true
the build will successfully end. (khmarbaise:
[http://svn.apache.org/viewvc/?view=rev=1741757])
* maven-war-plugin/pom.xml
* maven-war-plugin/src/it/MWAR-326
* maven-war-plugin/src/it/MWAR-326/invoker.properties
* maven-war-plugin/src/it/MWAR-326/pom.xml
* maven-war-plugin/src/it/MWAR-326/src
* maven-war-plugin/src/it/MWAR-326/src/main
* maven-war-plugin/src/it/MWAR-326/src/main/java
* maven-war-plugin/src/it/MWAR-326/src/main/java/A.java
* maven-war-plugin/src/it/MWAR-326/verify.bsh
* maven-war-plugin/src/main/filtered-resources
* maven-war-plugin/src/main/filtered-resources/META-INF
* maven-war-plugin/src/main/filtered-resources/META-INF/plexus
* maven-war-plugin/src/main/filtered-resources/META-INF/plexus/components.xml
> Add LifecycleMapping and ArtifactHandler from maven-core to target packaging
> plugin
> ---
>
> Key: MWAR-326
> URL: https://issues.apache.org/jira/browse/MWAR-326
> Project: Maven WAR Plugin
> Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Robert Scholte
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> Maven Core shouldn't be aware of this kind of information, instead the
> maven-war-plugin should specify and maintain the {{LifecycleMapping}} and
> {{ArtifactHandler}} by itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MRAR-55) Add LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin
[
https://issues.apache.org/jira/browse/MRAR-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15265304#comment-15265304
]
Hudson commented on MRAR-55:
SUCCESS: Integrated in maven-plugins #5813 (See
[https://builds.apache.org/job/maven-plugins/5813/])
[MRAR-55] Add LifecycleMapping and ArtifactHandler from maven-core to target
packaging plugin
o Added components.xml which contains
ArtifactHandler mapping and life cycle mapping and
the appropriate plugin versions.
o Added basic integration tests which checks if
by using the maven-rar-plugin with extensions=true
the build will successfully end. (khmarbaise:
[http://svn.apache.org/viewvc/?view=rev=1741754])
* maven-rar-plugin/filtered-resources
* maven-rar-plugin/filtered-resources/META-INF
* maven-rar-plugin/filtered-resources/META-INF/plexus
* maven-rar-plugin/filtered-resources/META-INF/plexus/components.xml
* maven-rar-plugin/pom.xml
> Add LifecycleMapping and ArtifactHandler from maven-core to target packaging
> plugin
> ---
>
> Key: MRAR-55
> URL: https://issues.apache.org/jira/browse/MRAR-55
> Project: Maven Rar Plugin
> Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> Maven Core shouldn't be aware of this kind of information, instead the
> maven-rar-plugin should specify and maintain the {{LifecycleMapping}} and
> {{ArtifactHandler}} by itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MACR-30) Add LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin
[
https://issues.apache.org/jira/browse/MACR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MACR-30.
---
Resolution: Fixed
Assignee: Karl Heinz Marbaise
Upgraded [r1741760|http://svn.apache.org/r1741760]
> Add LifecycleMapping and ArtifactHandler from maven-core to target packaging
> plugin
> ---
>
> Key: MACR-30
> URL: https://issues.apache.org/jira/browse/MACR-30
> Project: Maven ACR Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.1
>
>
> Maven Core shouldn't be aware of this kind of information, instead the
> maven-acr-plugin should specify and maintain the {{LifecycleMapping}} and
> {{ArtifactHandler}} by itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MWAR-326) Add LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin
[
https://issues.apache.org/jira/browse/MWAR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MWAR-326.
Resolution: Fixed
Done in [r1741757|http://svn.apache.org/r1741757]
> Add LifecycleMapping and ArtifactHandler from maven-core to target packaging
> plugin
> ---
>
> Key: MWAR-326
> URL: https://issues.apache.org/jira/browse/MWAR-326
> Project: Maven WAR Plugin
> Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Robert Scholte
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> Maven Core shouldn't be aware of this kind of information, instead the
> maven-war-plugin should specify and maintain the {{LifecycleMapping}} and
> {{ArtifactHandler}} by itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MWAR-326) Add LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin
[
https://issues.apache.org/jira/browse/MWAR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MWAR-326:
Assignee: Karl Heinz Marbaise
> Add LifecycleMapping and ArtifactHandler from maven-core to target packaging
> plugin
> ---
>
> Key: MWAR-326
> URL: https://issues.apache.org/jira/browse/MWAR-326
> Project: Maven WAR Plugin
> Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Robert Scholte
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> Maven Core shouldn't be aware of this kind of information, instead the
> maven-war-plugin should specify and maintain the {{LifecycleMapping}} and
> {{ArtifactHandler}} by itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MWAR-326) Add LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin
[
https://issues.apache.org/jira/browse/MWAR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MWAR-326:
-
Fix Version/s: 3.0.0
> Add LifecycleMapping and ArtifactHandler from maven-core to target packaging
> plugin
> ---
>
> Key: MWAR-326
> URL: https://issues.apache.org/jira/browse/MWAR-326
> Project: Maven WAR Plugin
> Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Robert Scholte
> Fix For: 3.0.0
>
>
> Maven Core shouldn't be aware of this kind of information, instead the
> maven-war-plugin should specify and maintain the {{LifecycleMapping}} and
> {{ArtifactHandler}} by itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MRAR-57) Upgrade maven-archiver to 3.0.2
Karl Heinz Marbaise created MRAR-57: --- Summary: Upgrade maven-archiver to 3.0.2 Key: MRAR-57 URL: https://issues.apache.org/jira/browse/MRAR-57 Project: Maven Rar Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Priority: Minor Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MRAR-42) Upgrade maven-filtering to 1.3
[ https://issues.apache.org/jira/browse/MRAR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MRAR-42: Affects Version/s: (was: next-release) 3.0.0 > Upgrade maven-filtering to 1.3 > -- > > Key: MRAR-42 > URL: https://issues.apache.org/jira/browse/MRAR-42 > Project: Maven Rar Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > > Upgrade maven-filtering to 1.3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MRAR-43) Upgrade maven-archiver to 2.6
[ https://issues.apache.org/jira/browse/MRAR-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MRAR-43: Affects Version/s: (was: next-release) 3.0.0 > Upgrade maven-archiver to 2.6 > - > > Key: MRAR-43 > URL: https://issues.apache.org/jira/browse/MRAR-43 > Project: Maven Rar Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > > Upgrade maven-archiver to 2.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MRAR-40) Update version of plexus-archiver to 2.9
[ https://issues.apache.org/jira/browse/MRAR-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MRAR-40: Affects Version/s: (was: next-release) 3.0.0 > Update version of plexus-archiver to 2.9 > > > Key: MRAR-40 > URL: https://issues.apache.org/jira/browse/MRAR-40 > Project: Maven Rar Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > > https://github.com/sonatype/plexus-archiver/blob/master/ReleaseNotes.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MRAR-44) Upgrade maven-plugin-testing-harness to 1.3
[ https://issues.apache.org/jira/browse/MRAR-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MRAR-44: Affects Version/s: (was: next-release) 3.0.0 > Upgrade maven-plugin-testing-harness to 1.3 > --- > > Key: MRAR-44 > URL: https://issues.apache.org/jira/browse/MRAR-44 > Project: Maven Rar Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > > Upgrade maven-plugin-testing-harness to 1.3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MRAR-55) Add LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin
[
https://issues.apache.org/jira/browse/MRAR-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MRAR-55.
---
Resolution: Fixed
Assignee: Karl Heinz Marbaise
Done in [r1741754|http://svn.apache.org/r1741754]
> Add LifecycleMapping and ArtifactHandler from maven-core to target packaging
> plugin
> ---
>
> Key: MRAR-55
> URL: https://issues.apache.org/jira/browse/MRAR-55
> Project: Maven Rar Plugin
> Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> Maven Core shouldn't be aware of this kind of information, instead the
> maven-rar-plugin should specify and maintain the {{LifecycleMapping}} and
> {{ArtifactHandler}} by itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MRAR-55) Add LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin
[
https://issues.apache.org/jira/browse/MRAR-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MRAR-55:
Fix Version/s: 3.0.0
> Add LifecycleMapping and ArtifactHandler from maven-core to target packaging
> plugin
> ---
>
> Key: MRAR-55
> URL: https://issues.apache.org/jira/browse/MRAR-55
> Project: Maven Rar Plugin
> Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> Maven Core shouldn't be aware of this kind of information, instead the
> maven-rar-plugin should specify and maintain the {{LifecycleMapping}} and
> {{ArtifactHandler}} by itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MJAR-193) Allow other mojos to contribute to the manifest
[
https://issues.apache.org/jira/browse/MJAR-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15265235#comment-15265235
]
Karl Heinz Marbaise commented on MJAR-193:
--
First it is important to say that with version 3.0.0 of maven-jar-plugin the
option via {{useDefaultManifestFile}} will not exist anymore. The second
options via manifestFile will work of course. Using the project context might
influence other parts of the build which should be prevented. May be you can
show an example of the code you use ? What i can think of is having an external
manifest-merge.mf file which might be merged with the current existing one...?
But i need think hard about that...
> Allow other mojos to contribute to the manifest
> ---
>
> Key: MJAR-193
> URL: https://issues.apache.org/jira/browse/MJAR-193
> Project: Maven JAR Plugin
> Issue Type: Improvement
>Reporter: Carsten Ziegeler
> Fix For: waiting-for-feedback
>
>
> It would be great to have a programmatic way to add entries to the manifest
> from other mojos. The most important client of such a way would be the maven
> bundle plugin (from the Apache Felix project) that calculates additional
> headers for OSGi bundles. Right now, that bundle does not only do the
> calculation but generates the jar file as well.
> While a workaround would be to let the bundle plugin generate the full
> manifest and configure the jar plugin to use it, this is not very elegant.
> Passing down a map of manifest entries from one mojo to the jar plugin would
> solve this in a much better way.
> And I could imagine that other mojos/plugins might benefit for this as well.
> This would be a simple but very convenient enhancement to the plugin
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
