[jira] [Created] (MASFRES-8) Include assembly descriptor in the produced jar file
Maysam Yabandeh created MASFRES-8: - Summary: Include assembly descriptor in the produced jar file Key: MASFRES-8 URL: https://issues.apache.org/jira/browse/MASFRES-8 Project: Apache Maven Resource Bundles Issue Type: Wish Reporter: Maysam Yabandeh Priority: Minor Many assembly descriptors conservatively include many jar dependencies in the final jar file, resulting into fat jar problem. If the assembly descriptor file was included by default, each framework could disassemble the fat jar on demand and reassemble it having the known, available jar files excluded. Issues like hadoop-9639 can benefit from this feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRRESOURCES-70) SVN settings: eol-style and keywords
[ https://jira.codehaus.org/browse/MRRESOURCES-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330750#comment-330750 ] SebbASF commented on MRRESOURCES-70: Trunk looks good now > SVN settings: eol-style and keywords > > > Key: MRRESOURCES-70 > URL: https://jira.codehaus.org/browse/MRRESOURCES-70 > Project: Maven Remote Resources Plugin > Issue Type: Bug >Reporter: SebbASF >Assignee: Dennis Lundberg >Priority: Minor > Fix For: 1.6 > > > The following files don't have the standard SVN settings: > svn ps svn:eol-style native > src/it/resources/generate-from-bundle-with-type-and-classifier/src/main/java/org/apache/maven/plugin/rresource/it/App.java > svn ps svn:eol-style native > src/test/java/org/apache/maven/plugin/resources/remote/it/IT_GenerateFromBundleWithTypeAndClassifier.java > svn ps svn:eol-style native > src/it/resources/bad-dependency-poms/repo/test/invalid/0.1/invalid-0.1.pom > svn ps svn:eol-style native > src/it/resources/bad-dependency-poms/repo/test/pom/0.2/pom-0.2.pom > svn ps svn:eol-style native > src/it/resources/bootstrap/resource-bundle-with-type-and-classifier/pom.xml > svn ps svn:eol-style native > src/it/resources/bootstrap/resource-bundle-with-type-and-classifier/src/main/resources/DEPENDENCIES.vm > svn ps svn:eol-style native > src/it/resources/generate-from-bundle-with-type-and-classifier/pom.xml > svn ps svn:eol-style native src/it/settings.xml > The following files have invalid SVN keyword settings: > pom.xml > src/it/maven-remote-resources-test/pom.xml > src/site/apt/index.apt.vm > src/site/apt/usage.apt.vm > src/site/fml/faq.fml > src/site/site.xml > For example, pom.xml has > keywords="Author Date Id Revision" > whereas it should be > keywords=Author Date Id Revision > Looks like spurious quotes have been added. > But ideally, Date should not be enabled (it's locale-dependent) and Author is > unlikely to be useful. Id and Revision may be useful at times. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRRESOURCES-70) SVN settings: eol-style and keywords
[ https://jira.codehaus.org/browse/MRRESOURCES-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MRRESOURCES-70. -- Resolution: Fixed Fix Version/s: 1.6 Assignee: Dennis Lundberg Fixed in [r1514463|http://svn.apache.org/viewvc?view=revision&revision=1514463] and [r1514467|http://svn.apache.org/viewvc?view=revision&revision=1514467]. > SVN settings: eol-style and keywords > > > Key: MRRESOURCES-70 > URL: https://jira.codehaus.org/browse/MRRESOURCES-70 > Project: Maven Remote Resources Plugin > Issue Type: Bug >Reporter: SebbASF >Assignee: Dennis Lundberg >Priority: Minor > Fix For: 1.6 > > > The following files don't have the standard SVN settings: > svn ps svn:eol-style native > src/it/resources/generate-from-bundle-with-type-and-classifier/src/main/java/org/apache/maven/plugin/rresource/it/App.java > svn ps svn:eol-style native > src/test/java/org/apache/maven/plugin/resources/remote/it/IT_GenerateFromBundleWithTypeAndClassifier.java > svn ps svn:eol-style native > src/it/resources/bad-dependency-poms/repo/test/invalid/0.1/invalid-0.1.pom > svn ps svn:eol-style native > src/it/resources/bad-dependency-poms/repo/test/pom/0.2/pom-0.2.pom > svn ps svn:eol-style native > src/it/resources/bootstrap/resource-bundle-with-type-and-classifier/pom.xml > svn ps svn:eol-style native > src/it/resources/bootstrap/resource-bundle-with-type-and-classifier/src/main/resources/DEPENDENCIES.vm > svn ps svn:eol-style native > src/it/resources/generate-from-bundle-with-type-and-classifier/pom.xml > svn ps svn:eol-style native src/it/settings.xml > The following files have invalid SVN keyword settings: > pom.xml > src/it/maven-remote-resources-test/pom.xml > src/site/apt/index.apt.vm > src/site/apt/usage.apt.vm > src/site/fml/faq.fml > src/site/site.xml > For example, pom.xml has > keywords="Author Date Id Revision" > whereas it should be > keywords=Author Date Id Revision > Looks like spurious quotes have been added. > But ideally, Date should not be enabled (it's locale-dependent) and Author is > unlikely to be useful. Id and Revision may be useful at times. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MAVENUPLOAD-2825) Upload version 1.2 of JarAnalyzer
[ https://jira.codehaus.org/browse/MAVENUPLOAD-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MAVENUPLOAD-2825. Resolution: Won't Fix Please read the instructions at https://jira.codehaus.org/browse/MAVENUPLOAD > Upload version 1.2 of JarAnalyzer > - > > Key: MAVENUPLOAD-2825 > URL: https://jira.codehaus.org/browse/MAVENUPLOAD-2825 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Steinar Bang > Attachments: jaranalyzer-1.2-bundle.jar > > > "JarAnalyzer is a dependency management utility for jar files. It's primary > purpose is to traverse through a directory, parse each of the jar files in > that directory, and identify the dependencies between the jar files. The > output is an xml file representing the PhysicalDependencies between the jar > files." > Version 0.9.3 was uploaded with MAVENUPLOAD-753. > The source or binary bundles can be downloaded from the Project URL below. > The JAR is built by ant and not by maven. > I have attached a bundle containing the JAR, the source JAR, the license and > a pom.xml file (the same type of contents as the 0.9.3 bundle attached to > MAVENUPLOAD-753. The pom.xml file was grabbed from that bundle and the > ArtifactId and the version number was adjusted). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEPLOY-163) Maven Deploy Plugin Deploys Attached Sources A Second Time
[
https://jira.codehaus.org/browse/MDEPLOY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330737#comment-330737
]
Jonathon Golden commented on MDEPLOY-163:
-
I just ran into the same problem when using deploy-file in a pom that was using
the maven-assembly-plugin. I set the attach to false and the problem went away
(I don't need the assembly deployed to my repository in this case) But i would
say this reveals that the problem is that the deploy-file goal should not
attempt to deploy attached artifacts since it is supposed to be used for
explicitly specified artifacts.
> Maven Deploy Plugin Deploys Attached Sources A Second Time
> --
>
> Key: MDEPLOY-163
> URL: https://jira.codehaus.org/browse/MDEPLOY-163
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy-file
>Affects Versions: 2.7
> Environment: 64 Bit Linux
>Reporter: Jonathon Golden
>
> This happens in a jar pom where I have attached sources to the jar thus:
> {code:xml}
>
> org.apache.maven.plugins
> maven-source-plugin
>
>
> attach-sources-
> compile
>
> jar-no-fork
>
>
>
>
> {code}
> When running the deploy phase this will result in the source jar being
> deployed to the repository (nexus in my case) in the normal fashion.
> I also had in the same pom (I've since moved it to another module to
> workaround this bug) deployment of additional configuration artifacts thus:
> {code:xml}
>
> org.apache.maven.plugins
> maven-deploy-plugin
>
>
> deploy-REDACTED
> deploy
>
> REDACTED
> REDACTED
> ${project.version}
> REDACTED
> xml
> true
> nexus
>
> http://nexus:8081/content/repositories/${deployment.repository.suffix}
>
>
> deploy-file
>
>
>
>
> {code}
> When the deploy-file goal executes it will succeed to deploy the xml file but
> for some reason it is also attempting to upload the jar sources a second time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEPLOY-163) Maven Deploy Plugin Deploys Attached Sources A Second Time
[
https://jira.codehaus.org/browse/MDEPLOY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathon Golden updated MDEPLOY-163:
Description:
This happens in a jar pom where I have attached sources to the jar thus:
{code:xml}
org.apache.maven.plugins
maven-source-plugin
attach-sources-
compile
jar-no-fork
{code}
When running the deploy phase this will result in the source jar being deployed
to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to workaround
this bug) deployment of additional configuration artifacts thus:
{code:xml}
org.apache.maven.plugins
maven-deploy-plugin
deploy-REDACTED
deploy
REDACTED
REDACTED
${project.version}
REDACTED
xml
true
nexus
http://nexus:8081/content/repositories/${deployment.repository.suffix}
deploy-file
{code}
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
was:
This happens in a jar pom where I have attached sources to the jar thus:
{code:xml}
org.apache.maven.plugins
maven-source-plugin
attach-sources-
compile
jar-no-fork
{code}
When running the deploy phase this will result in the source jar being deployed
to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to workaround
this bug) deployment of additional configuration artifacts thus:
org.apache.maven.plugins
maven-deploy-plugin
deploy-REDACTED
deploy
REDACTED
REDACTED
${project.version}
REDACTED
xml
true
nexus
http://nexus:8081/content/repositories/${deployment.repository.suffix}
deploy-file
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
> Maven Deploy Plugin Deploys Attached Sources A Second Time
> --
>
> Key: MDEPLOY-163
> URL: https://jira.codehaus.org/browse/MDEPLOY-163
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy-file
>Affects Versions: 2.7
> Environment: 64 Bit Linux
>Reporter: Jonathon Golden
>
> This happens in a jar pom where I have attached sources to the jar thus:
> {code:xml}
>
> org.apache.maven.plugins
> maven-source-plugin
>
>
> attach-sources-
> compile
>
> jar-no-fork
>
>
>
>
> {code}
> When running the deploy phase this will result in the source jar being
> deployed to the repository (nexus in my case) in the normal fashion.
> I also had in the same pom (I've since moved it to another module to
> workaround this bug) deployment of additional configuration artifacts thus:
> {code:xml}
>
> org.apache.maven.plugins
> maven-deploy-plugin
>
>
> deploy-REDACTED
> deploy
>
> REDACTED
> REDACTED
> ${project.version}
> REDACTED
> xml
> true
> nexus
>
> http://nexus:8081/content/re
[jira] (MDEPLOY-163) Maven Deploy Plugin Deploys Attached Sources A Second Time
[
https://jira.codehaus.org/browse/MDEPLOY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathon Golden updated MDEPLOY-163:
Description:
This happens in a jar pom where I have attached sources to the jar thus:
{code:xml}
org.apache.maven.plugins
maven-source-plugin
attach-sources-
compile
jar-no-fork
{code}
When running the deploy phase this will result in the source jar being deployed
to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to workaround
this bug) deployment of additional configuration artifacts thus:
org.apache.maven.plugins
maven-deploy-plugin
deploy-REDACTED
deploy
REDACTED
REDACTED
${project.version}
REDACTED
xml
true
nexus
http://nexus:8081/content/repositories/${deployment.repository.suffix}
deploy-file
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
was:
This happens in a jar pom where I have attached sources to the jar thus:
org.apache.maven.plugins
maven-source-plugin
attach-sources-
compile
jar-no-fork
When running the deploy phase this will result in the source jar being deployed
to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to workaround
this bug) deployment of additional configuration artifacts thus:
org.apache.maven.plugins
maven-deploy-plugin
deploy-REDACTED
deploy
REDACTED
REDACTED
${project.version}
REDACTED
xml
true
nexus
http://nexus:8081/content/repositories/${deployment.repository.suffix}
deploy-file
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
> Maven Deploy Plugin Deploys Attached Sources A Second Time
> --
>
> Key: MDEPLOY-163
> URL: https://jira.codehaus.org/browse/MDEPLOY-163
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy-file
>Affects Versions: 2.7
> Environment: 64 Bit Linux
>Reporter: Jonathon Golden
>
> This happens in a jar pom where I have attached sources to the jar thus:
> {code:xml}
>
> org.apache.maven.plugins
> maven-source-plugin
>
>
> attach-sources-
> compile
>
> jar-no-fork
>
>
>
>
> {code}
> When running the deploy phase this will result in the source jar being
> deployed to the repository (nexus in my case) in the normal fashion.
> I also had in the same pom (I've since moved it to another module to
> workaround this bug) deployment of additional configuration artifacts thus:
>
> org.apache.maven.plugins
> maven-deploy-plugin
>
>
> deploy-REDACTED
> deploy
>
> REDACTED
> REDACTED
> ${project.version}
> REDACTED
> xml
> true
> nexus
>
> http://nexus:8081/content/repositories/${deployment.repository.suffix}
>
[jira] (MDEPLOY-163) Maven Deploy Plugin Deploys Attached Sources A Second Time
Jonathon Golden created MDEPLOY-163:
---
Summary: Maven Deploy Plugin Deploys Attached Sources A Second Time
Key: MDEPLOY-163
URL: https://jira.codehaus.org/browse/MDEPLOY-163
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy-file
Affects Versions: 2.7
Environment: 64 Bit Linux
Reporter: Jonathon Golden
This happens in a jar pom where I have attached sources to the jar thus:
org.apache.maven.plugins
maven-source-plugin
attach-sources-
compile
jar-no-fork
When running the deploy phase this will result in the source jar being deployed
to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to workaround
this bug) deployment of additional configuration artifacts thus:
org.apache.maven.plugins
maven-deploy-plugin
deploy-REDACTED
deploy
REDACTED
REDACTED
${project.version}
REDACTED
xml
true
nexus
http://nexus:8081/content/repositories/${deployment.repository.suffix}
deploy-file
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-1020) Incorrect XML escape in and content of junit xml report
[ https://jira.codehaus.org/browse/SUREFIRE-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330706#comment-330706 ] Todor Todorov commented on SUREFIRE-1020: - Great! I'm looking forward to see 2.16 released:-) > Incorrect XML escape in and content of junit xml > report > - > > Key: SUREFIRE-1020 > URL: https://jira.codehaus.org/browse/SUREFIRE-1020 > Project: Maven Surefire > Issue Type: Bug > Components: xml generation >Affects Versions: 2.15, 2.16 >Reporter: Todor Todorov >Assignee: Andreas Gudian >Priority: Critical > Fix For: 2.16 > > Attachments: fixed-illegal-escape.patch > > > JUnit XML report contains invalid XML characters in and > content. The illegal characters handling defined in SUREFIRE-456 > doesn't work since version 2.15. The problem is that *EncodingOutputStream* > in *StatelessXmlReporter* does not convert the illegal XML characters to > their string representation (e.g. 0 -> "0"). > Please find attached a possible fix for this issue as well as extended test > case that includes illegal XML characters in system-out and system-err > content. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
