[jira] Created: (ARCHETYPE-284) Cannot define sources elsewhere than in src/main/java
Cannot define sources elsewhere than in src/main/java - Key: ARCHETYPE-284 URL: http://jira.codehaus.org/browse/ARCHETYPE-284 Project: Maven Archetype Issue Type: Improvement Components: Generator Affects Versions: 2.0-alpha-4 Environment: Observed on Ubuntu (Affects all?) Reporter: Mike Andrzejewski I have additional sources & resources in src/setup/*, but project generation complains as this path is not recognized as a standard one... It is very fustrating to be limited to src/main, as the main reason for defining a custom archetype is to have custom layout. -- 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: (MINSTALL-54) [INFO] Error installing artifact's metadata
[
http://jira.codehaus.org/browse/MINSTALL-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209016#action_209016
]
Daniel Takai commented on MINSTALL-54:
--
We're experiencing the same problem. We run
* Archiva 1.2.1
* CentOS release 5 (Final)
* Java 1.6.0_02
* Maven 2.2.1
{code}
[INFO] Retrieving previous metadata from snapshots
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error installing artifact's metadata:
Error installing metadata:
Error updating group repository metadata in epilog
non whitespace content is not allowed but got n
(position: END_TAG seen ...\nn... @14:2)
[INFO]
{code}
This problem occurs on a regular basis (daily) and causes problems with our
builds since artifacts cannot be deployed and builds fail. The corrupt metadata
needs to be repaired manually which is quite a lot of work. Quite nerve
wrecking when you really need that build and Archiva goes bom.
An example for corrupt metadata look like this:
{code:xml}
com.some.group
html
0.1-SNAPSHOT
0.1-SNAPSHOT
20100202145220
>html
0.1-SNAPSHOT
0.1-SNAPSHOT
20100202163215
{code}
> [INFO] Error installing artifact's metadata
> ---
>
> Key: MINSTALL-54
> URL: http://jira.codehaus.org/browse/MINSTALL-54
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Components: install:install
>Affects Versions: 2.2
> Environment: Windows XP
>Reporter: geoff simpson
>
> [INFO] Error installing artifact's metadata: Error installing metadata: Error
> updating group repository metadata
> end tag not allowed in epilog but got / (position: END_TAG seen ...\n
> Looks like there might be an issue with updates to maven-metadata-local.xml
> during the mvn install task. we have a build server that is multi threaded.
> we often see this in the
>
>
>
> maven-metadata-local.xml.
> maybe a solution is to add maven-metadata-local.xml.lock to ensure two
> threads don't update the file at the same time
--
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: (MINSTALL-54) [INFO] Error installing artifact's metadata
[ http://jira.codehaus.org/browse/MINSTALL-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209017#action_209017 ] Daniel Takai commented on MINSTALL-54: -- I forgot to mention: Our environment is not multi threaded for artifact updates. > [INFO] Error installing artifact's metadata > --- > > Key: MINSTALL-54 > URL: http://jira.codehaus.org/browse/MINSTALL-54 > Project: Maven 2.x Install Plugin > Issue Type: Bug > Components: install:install >Affects Versions: 2.2 > Environment: Windows XP >Reporter: geoff simpson > > [INFO] Error installing artifact's metadata: Error installing metadata: Error > updating group repository metadata > end tag not allowed in epilog but got / (position: END_TAG seen ...\n > Looks like there might be an issue with updates to maven-metadata-local.xml > during the mvn install task. we have a build server that is multi threaded. > we often see this in the > > > > maven-metadata-local.xml. > maybe a solution is to add maven-metadata-local.xml.lock to ensure two > threads don't update the file at the same time -- 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: (MAVENUPLOAD-2734) upload JAXB 2.2 impl to maven central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209019#action_209019 ] Pavel Bucek commented on MAVENUPLOAD-2734: -- is there some specific important reason to move to sonatype repository? It would be good to have some info before I present this to my manager. But to be honest, I don't believe that we'll move to sonatype, JAXB is java.net hosted project, so we use java.net maven repository. Additionally, moving would require some work (we have automated tasks which deploy artifacts to java.net and changing them + testing would require some time) and I don't see any benefit granted by moving. Regards, Pavel > upload JAXB 2.2 impl to maven central > - > > Key: MAVENUPLOAD-2734 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2734 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Pavel Bucek >Assignee: Juven Xu > > Hello, > can you please upload following artifacts to maven central? > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-impl/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-osgi/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-xjc/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb1-impl/2.2/ > Thanks, > Pavel -- 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: (MAVENUPLOAD-2734) upload JAXB 2.2 impl to maven central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209022#action_209022 ] Juven Xu commented on MAVENUPLOAD-2734: --- the reason is described at http://maven.apache.org/guides/mini/guide-central-repository-upload.html the *Sync'ing your own repository to the central repository automatically* section > upload JAXB 2.2 impl to maven central > - > > Key: MAVENUPLOAD-2734 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2734 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Pavel Bucek >Assignee: Juven Xu > > Hello, > can you please upload following artifacts to maven central? > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-impl/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-osgi/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-xjc/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb1-impl/2.2/ > Thanks, > Pavel -- 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: (MAVENUPLOAD-2734) upload JAXB 2.2 impl to maven central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209023#action_209023 ] Pavel Bucek commented on MAVENUPLOAD-2734: -- So does that mean our artifacts won't be pushed into maven central when we won't move? We release max. four stable versions per year and we don't mind some delay after submitting upload request. Another option is sync java.net maven repository with maven central; I can suggest this to java.net maven repo maintainers but thats probably everything I can do about that.. > upload JAXB 2.2 impl to maven central > - > > Key: MAVENUPLOAD-2734 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2734 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Pavel Bucek >Assignee: Juven Xu > > Hello, > can you please upload following artifacts to maven central? > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-impl/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-osgi/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-xjc/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb1-impl/2.2/ > Thanks, > Pavel -- 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: (MSHADE-73) Documentation does not detail what goes into PackageRelocation
Documentation does not detail what goes into PackageRelocation -- Key: MSHADE-73 URL: http://jira.codehaus.org/browse/MSHADE-73 Project: Maven 2.x Shade Plugin Issue Type: Bug Affects Versions: 1.3.1 Reporter: Benson Margulies The automatically generated documentation does not seem to detail the properties of a In particular, by analogy, I expected to be able to say instead of , but it is rejected. if there is doc for the attributres of as PackageRelocation I'm failing to find it. -- 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: (MSHADE-73) Documentation does not detail what goes into PackageRelocation
[ http://jira.codehaus.org/browse/MSHADE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209049#action_209049 ] Benjamin Bentmann commented on MSHADE-73: - bq. if there is doc for the attributres of as PackageRelocation I'm failing to find it. http://maven.apache.org/plugins/maven-shade-plugin/examples/class-relocation.html http://maven.apache.org/plugins/maven-shade-plugin/apidocs/org/apache/maven/plugins/shade/mojo/PackageRelocation.html http://maven.apache.org/plugins/maven-shade-plugin/xref/org/apache/maven/plugins/shade/mojo/PackageRelocation.html > Documentation does not detail what goes into PackageRelocation > -- > > Key: MSHADE-73 > URL: http://jira.codehaus.org/browse/MSHADE-73 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.3.1 >Reporter: Benson Margulies > > The automatically generated documentation does not seem to detail the > properties of a > In particular, by analogy, I expected to be able to say instead of > , but it is rejected. if there is doc for the attributres of as > PackageRelocation I'm failing to find it. -- 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: (MSHADE-73) Documentation does not detail what goes into PackageRelocation
[ http://jira.codehaus.org/browse/MSHADE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209052#action_209052 ] Benson Margulies commented on MSHADE-73: thanks for the pointer. It would, in my opinion, be good if the goal documentation could somehow pull this in. > Documentation does not detail what goes into PackageRelocation > -- > > Key: MSHADE-73 > URL: http://jira.codehaus.org/browse/MSHADE-73 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.3.1 >Reporter: Benson Margulies > > The automatically generated documentation does not seem to detail the > properties of a > In particular, by analogy, I expected to be able to say instead of > , but it is rejected. if there is doc for the attributres of as > PackageRelocation I'm failing to find it. -- 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: (MSHADE-74) Includes as well as Excludes in PackageRelocation
Includes as well as Excludes in PackageRelocation - Key: MSHADE-74 URL: http://jira.codehaus.org/browse/MSHADE-74 Project: Maven 2.x Shade Plugin Issue Type: Wish Affects Versions: 1.3.1 Reporter: Benson Margulies Priority: Minor I've run into a case where it would be more concise, not to mention safer, to call out the relocations by include instead of by exclude. It would match the usual pattern if both were supported. -- 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: (MAVENUPLOAD-2734) upload JAXB 2.2 impl to maven central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209055#action_209055 ] Jason van Zyl commented on MAVENUPLOAD-2734: The reason we are trying to get people to use the infrastructure we've setup is outlined here: http://www.sonatype.com/people/2010/01/nexus-oss-ecosystem/ You and about a thousand other projects want to get their stuff into Maven Central and we want to make this easier as well as improving the quality of the content going into Maven Central. Case in point is that you have no PGP signatures. We don't know who you are to be honest. Additionally, you haven't formatted any of your submissions as we request so it just makes it harder for us. We have tools for automating the checking and publishing of the standard upload bundles. It's even easier if you use a Nexus instance in some way, shape, or form because we know the artifacts have good POMs and addition information which ultimately makes it easier for consumers of the artifacts. You also don't have any Javadoc JARs or Source JARs. While not completely mandatory a major release coming from Sun for such a widely used project makes it extremely painful for users trying to navigate in an IDE. We recently worked with the Glassfish folks to clean up and get some artifacts into Maven Central. We're happy to do the same with you. Doing a major release for something so widely used as JAXB without signatures, javadocs and sources is honestly kind of crappy. All that happens is people blame Maven and so we're trying to nip these problems in the bud. Please work us to try and make the releases going to Maven Central of higher quality. > upload JAXB 2.2 impl to maven central > - > > Key: MAVENUPLOAD-2734 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2734 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Pavel Bucek >Assignee: Juven Xu > > Hello, > can you please upload following artifacts to maven central? > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-impl/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-osgi/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-xjc/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb1-impl/2.2/ > Thanks, > Pavel -- 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: (MAVENUPLOAD-2734) upload JAXB 2.2 impl to maven central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209061#action_209061 ] Pavel Bucek commented on MAVENUPLOAD-2734: -- ad sources: that is our fault, issue with release script. Looks like publishing to java.net maven1 repository worked better (sources are included): http://download.java.net/maven/1/com.sun.xml.bind/ ad pom file: we definitely can improve that. Maven is not main distribution site for JAXB and JAXB itself is not mavenized so I guess pom files contain only mandatory information. ad my identity: you can check my email address and send me something for identification if you want (and we can discuss further steps there, I would like to CC some people and I can't do it here..) > upload JAXB 2.2 impl to maven central > - > > Key: MAVENUPLOAD-2734 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2734 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Pavel Bucek >Assignee: Juven Xu > > Hello, > can you please upload following artifacts to maven central? > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-impl/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-osgi/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-xjc/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb1-impl/2.2/ > Thanks, > Pavel -- 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: (MAVENUPLOAD-2734) upload JAXB 2.2 impl to maven central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209064#action_209064 ] Jason van Zyl commented on MAVENUPLOAD-2734: Make standard upload bundles and we'll be happy to process the request. We're not piecing it all together from your Maven 1 and Maven 2 repositories. The guide is located here: http://maven.apache.org/guides/mini/guide-central-repository-upload.html > upload JAXB 2.2 impl to maven central > - > > Key: MAVENUPLOAD-2734 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2734 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Pavel Bucek >Assignee: Juven Xu > > Hello, > can you please upload following artifacts to maven central? > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-impl/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-osgi/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-xjc/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb1-impl/2.2/ > Thanks, > Pavel -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2733) Maven plugin for hadoop
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Kay closed MAVENUPLOAD-2733. Resolution: Won't Fix https://issues.sonatype.org/browse/OSSRH-228 , logged instead. > Maven plugin for hadoop > > > Key: MAVENUPLOAD-2733 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2733 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Kay Kay >Assignee: Juven Xu > > Maven Plugin for Hadoop . > I am the original author of the project - available here at - > http://github.com/akkumar/maven-hadoop . > Contributor Name + URL found in: source files and README file -- 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: (MAVENUPLOAD-2493) JAI ImageIO 1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209079#action_209079 ] Adam Goode commented on MAVENUPLOAD-2493: - The jj2000 part of the sources is not BSD licensed, but under a restrictive license. It may not even be permissible to redistribute, I don't know. See: https://jai-imageio-core.dev.java.net/source/browse/jai-imageio-core/src/share/classes/jj2000/j2k/JJ2KInfo.java?rev=1.1&view=markup http://lists.fedoraproject.org/pipermail/legal/2008-December/000465.html > JAI ImageIO 1.1 > --- > > Key: MAVENUPLOAD-2493 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2493 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Joerg Schaible >Assignee: Carlos Sanchez > > New version 1.1 of JAI ImageIO, this time with source (all is BSD licensed > now). -- 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: (MSITE-440) Site document validation fails if unable to retrieve schema (in offline mode)
[
http://jira.codehaus.org/browse/MSITE-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209083#action_209083
]
Mike Hanafey commented on MSITE-440:
The problem exists even when not in offline mode if you require a proxy to
fetch external resources. The root cause in this case is
*java.net.UnknownHostException: maven.apache.org*.
I stored a local copy of the FML schema, but then the same error occurs on some
reference to www.w3.org. So the problem is the proxy configuration from
settings.xml is not being used.
{code}http://maven.apache.org/FML/1.0.1";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/FML/1.0.1
http://maven.apache.org/xsd/fml-1.0.1.xsd";
title="">
...
[DEBUG] Generating
/home/mkh/sd/svn/LeadTracker/trunk/DB/target/site/conventions.html
[DEBUG] Validating the content...
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error parsing
'/home/mkh/sd/svn/LeadTracker/trunk/DB/src/site/fml/conventions.fml': line [-1]
Error validating the model: maven.apache.org
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error during page
generation
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.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)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:110)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page
generation
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:114)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 22 more
Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error parsing
'/home/mkh/sd/svn/LeadTracker/trunk/DB/src/site/fml/conventions.fml': line [-1]
Error validating the model: maven.apache.org
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:412)
at
org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:328)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:132)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:142)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:109)
... 24 more
Caused by: org.apache.maven.doxia.parser.ParseException: Error validating the
model: maven.apache.org
at
org.apache.maven.doxia.parser.AbstractXmlParser.validate(AbstractXmlParser.java:640)
at
org.apache.maven.doxia.parser.Abstract
[jira] Updated: (MAVENUPLOAD-2242) Sync JGoodies from https://sourceforge.net/projects/mvnartifacts/
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated MAVENUPLOAD-2242: Assignee: (was: Carlos Sanchez) You were removed because the email you provided was bouncing > Sync JGoodies from https://sourceforge.net/projects/mvnartifacts/ > - > > Key: MAVENUPLOAD-2242 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2242 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Roland Klein > > "com.jgoodies","mavens...@shell.sourceforge.net:/home/groups/j/jg/jgoodies/htdocs/m2-repo","rsync_ssh","Roland > Klein","pereg...@sourceforge.net",, > In february 2006 I asked at the mailing list to upload binding and the other > JGoodies libs to the central repo, but the project leader didn't want to > change their build system (ant). > https://binding.dev.java.net/servlets/ReadMsg?listName=users&msgNo=767 > Now I registered a project at sourceforge.net to collect such libs, that are > not willing or unable to deploy to central repo. There I deployed the most > recent versions. The artifacts under the groupId "jgoodies" aren't actual and > this groupId isn't recommended, so I changed it to "com.jgoodies" because > under this domain http:/www.jgoodies.com You find the original maintainer. > hth > Roland -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2578) Sync with datanucleus M2 repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2578. --- Resolution: Fixed Everything seems to be in both repos > Sync with datanucleus M2 repo > - > > Key: MAVENUPLOAD-2578 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2578 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Data Nucleus >Assignee: Carlos Sanchez > > "org.datanucleus","j...@www.datanucleus.org:/home/jpox/htdocs/downloads/maven2","rsync_ssh","Andy > Jefferson","i...@datanucleus.org",, > The domain is obviously mine, registered under my name. > I put the Maven public key into the user "jpox" "$home/.ssh/authorized_keys" > Left as an exercise to see if that works -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2659) repository synchronization
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2659. --- Resolution: Fixed You were looking in the wrong place http://repo1.maven.org/maven2/com/sirika/ > repository synchronization > -- > > Key: MAVENUPLOAD-2659 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2659 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Sami Dalouche >Assignee: Carlos Sanchez > > Hi, > Is it possible to add the following files to the list of automatically > synchronized repositories ? > "com.sirika.httpclienthelpers","rsync://developers.sirika.com/maven2/releases","rsync","Sami > Dalouche","sami.dalou...@gmail.com",, > "com.sirika.pymager","rsync://developers.sirika.com/maven2/releases","rsync","Sami > Dalouche","sami.dalou...@gmail.com",, > URLs : > http://developers.sirika.com/httpclienthelpers/ > http://developers.sirika.com/pymager-java-client/ > thanks, > Sami Dalouche > PS: I am not sure whether the previous information is enough to allow me to > use the "com.sirika.*" namespaces. If you want a more solid proof of it, I > can always upload -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1538) xml-apis-1.2.01.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1538. --- Resolution: Fixed Added relocation pom > xml-apis-1.2.01.jar > --- > > Key: MAVENUPLOAD-1538 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1538 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Michael Böckling >Assignee: Carlos Sanchez > Attachments: pom.xml, xml-apis-1.2.01.jar > > > An older version of xml-apis. Needed by ICEFaces-1.5.3 which will follow > later on. POM is partially copied from > http://mirrors.ibiblio.org/pub/mirrors/maven2/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.pom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1774) Sync de.berlios.jsunit
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1774. --- Resolution: Incomplete > Sync de.berlios.jsunit > -- > > Key: MAVENUPLOAD-1774 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1774 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Joerg Schaible >Assignee: Carlos Sanchez > Attachments: screenshot.png > > > Please sync with de.berlios.jsunit, a JavaScript unit test library with Maven > 2 plugin and Ant task. Licensed with ASL 2.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2615) rsync_ssh request for svenson and jcouchdb
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2615. --- Resolution: Fixed Added port to ssh config > rsync_ssh request for svenson and jcouchdb > -- > > Key: MAVENUPLOAD-2615 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2615 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Sven Helmberger >Assignee: Carlos Sanchez > > "com.google.code.svenson","mvnrs...@fforw.de:/home/mvnrsync/m2repo/releases","rsync_ssh","Sven > Helmberger","i...@fforw.de" > "com.google.code.jcouchdb","mvnrs...@fforw.de:/home/mvnrsync/m2repo/releases","rsync_ssh","Sven > Helmberger","i...@fforw.de" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2658) Please upload MessAdmin 4.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2658. --- Resolution: Incomplete Assignee: Carlos Sanchez (was: Juven Xu) > Please upload MessAdmin 4.2 > --- > > Key: MAVENUPLOAD-2658 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2658 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: codehauser >Assignee: Carlos Sanchez > Attachments: MessAdmin-4.2-bundles.zip > > > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-Core-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-ClickStream-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-DiskBrowser-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-Ehcache-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-JMX-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-Log4J-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-ScriptExecutor-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-Serializable-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-ServletStats-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-SessionKiller-4.2-bundle.jar > http://messadmin.sourceforge.net/ > http://messadmin.sourceforge.net/#%5B%5BLicense%20%2F%20Contact%5D%5D > MessAdmin is a light-weigth and non-intrusive tool for monitoring Java > HttpSession and more. Please upload! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2642) Upload Hbase jars to a public maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2642. --- Resolution: Won't Fix Assignee: Carlos Sanchez (was: Juven Xu) you can help them to prepare their artifacts for the apache repo and get them uploaded through there, they dont need to use maven For any questions regarding the apache repo: repository at apache dot org > Upload Hbase jars to a public maven repository > -- > > Key: MAVENUPLOAD-2642 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2642 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Cyril Lakech >Assignee: Carlos Sanchez > > I just contact the hadoop hbase team by creating issues on the tracker, they > use ant to build there projects and they don't plan to use maven. (see > https://issues.apache.org/jira/browse/HBASE-1933) > I help them to upload the hadoop projects on the maven central repository. > I can be designated the "unofficial" mantainer of the repository section > associated with hadoop project. -- 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: (MPMD-114) Add a parameter to make the build fail if number of warnings is above a certain amount
Add a parameter to make the build fail if number of warnings is above a certain amount -- Key: MPMD-114 URL: http://jira.codehaus.org/browse/MPMD-114 Project: Maven 2.x PMD Plugin Issue Type: Improvement Reporter: Greg Snyder Priority: Minor Currently, PMD provides functionality to fail the build if there are any violations or if there is any violation above a certain priority. There is no way to say "fail the build if there are more than xxx violations". -- 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: (MCHANGES-196) statusIds are ignored for announcement-generate goal
statusIds are ignored for announcement-generate goal
Key: MCHANGES-196
URL: http://jira.codehaus.org/browse/MCHANGES-196
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: announcement
Affects Versions: 2.3
Environment: maven 2.2.1, windows XP, java 1.6.0_13, jira 3.13.5#360
Reporter: rob fellows
I am trying to configure the changes plugin to retrieve issues from our jira
system. the jira-report goal works as expected, generating the xml based on
the parameters, including statusIds. when i use announcement-generate, the
statusIds are ignored and only Closed issues are returned in the
jira-announcements.xml file.
here is my current configuration...
org.apache.maven.plugins
maven-changes-plugin
${maven.changes.plugin.version}
jira-report
true
Type,Key,Summary,Assignee,Status,Resolution,Fix
Version
Type,Key DESC
Fixed
Resolved,Closed
100
smtpserver
25
m...@email.com
true
true
executing"mvn clean changes:announcement-generate"
results in
[INFO]
[INFO] Building Capps
[INFO]task-segment: [clean, changes:announcement-generate]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory c:\workspace\Framework_CAPPS2_OD3\CAPPS2\target
[INFO] [changes:announcement-generate {execution: default-cli}]
Feb 3, 2010 5:27:29 PM org.apache.commons.httpclient.HttpMethodBase
getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using
getResponseBodyAsStream instead is recommended.
[ERROR] maven-changes-plugin: None of the configured sortColumnNames 'null' are
correct.
[INFO] Downloading from JIRA at:
http://xxx/secure/IssueNavigator.jspa?view=rss&pid=10944&statusIds=6&resolutionIds=1&tempMax=100&reset=true&decorator=none
Feb 3, 2010 5:27:30 PM org.apache.commons.httpclient.HttpMethodBase
getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using
getResponseBodyAsStream instead is recommended.
[INFO] Creating announcement file from JIRA releases...
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Couldn't find the release '2.0.7' among the supplied releases.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 3 seconds
[INFO] Finished at: Wed Feb 03 17:27:30 EST 2010
[INFO] Final Memory: 23M/254M
[INFO]
Even though there is an error, the jira-announcements.xml file gets generated.
xxx
http://xx/secure/IssueNavigator.jspa?reset=true&pid=10944&status=6&resolution=1&sorter/field=issuekey&sorter/order=DESC
An XML representation of a search request
en-us
3.13.5
360
07-07-2009
Enterprise
..[items]..
You can tell by the tag in the xml that the only status retrieved was
CLOSED (status=6).
I'm not sure why the build error is popping up & i still get the generated
file. I suppose there are 2 issues here.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MEV-651) Maven Junit's maven-metadata.xml is missing new versions
[ http://jira.codehaus.org/browse/MEV-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-651. -- Resolution: Fixed Assignee: Carlos Sanchez > Maven Junit's maven-metadata.xml is missing new versions > > > Key: MEV-651 > URL: http://jira.codehaus.org/browse/MEV-651 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid Metadata >Reporter: Jane Young >Assignee: Carlos Sanchez > > Not sure if this bug belongs here... > Take a look at http://repo1.maven.org/maven2/junit/junit/ and you'll see > versions 4.5, 4.6 and 4.7. > But if you look at > http://repo1.maven.org/maven2/junit/junit/maven-metadata.xml it stops at > version 4.4. > If I use version range (e.g. "[4.4,)") or the key word "RELEASE" in the pom > file, Maven downloads the highest version in maven-metadata.xml file and in > this case version 4.4 but the highest version in > http://repo1.maven.org/maven2/junit/junit is 4.7. > This is clearly an issue in maven-metadata.xml. However, is there a way for > Maven to find the latest version w/o relying on metadata.xml? > Also how can this be fixed in the Maven central 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] Closed: (MEV-644) xerces:xercesImpl is missing verisons greater than 2.8.0 in metadata
[ http://jira.codehaus.org/browse/MEV-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-644. -- Resolution: Fixed Assignee: Carlos Sanchez > xerces:xercesImpl is missing verisons greater than 2.8.0 in metadata > > > Key: MEV-644 > URL: http://jira.codehaus.org/browse/MEV-644 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid Metadata >Reporter: Karla Jacobsen >Assignee: Carlos Sanchez > > The maven-metadata.xml for xerces:xercesImpl is missing versions 2.8.1, > 2.9.0, and 2.9.1. > As a side note, this was a very difficult issue to decode for a newbie. It > would be very helpful to have more documentation, or better error messages to > indicate that bad metadata could be the cause of resolve problems. I was > seeing the problem when trying to use a range of versions, or when specifying > a constrained range (e.g. [2.8.1,) or [2.8.1]). My build succeeded when I > just used 2.8.1, so it took me quite a while to figure out why. > In case it is helpful...I was running a build using the Ant Maven task > 'dependencies' and the following pom.xml: > > 4.0.0 > com.mycompany > example > 1.1.1 > > > xerces > xercesImpl > [2.8.1,2.9.1] > > > xalan > xalan > [2.7.0,2.7.1] > > > > Here is the relevant Ant output (when running in verbose mode): > [artifact:pom] Loading Maven settings file: > C:\bin\apache-maven-2.0.9\conf\settings.xml > [available] Found: .pom.xml > -resolve-compile-dependencies: > [artifact:dependencies] Loading Maven settings file: > C:\bin\apache-maven-2.0.9\conf\settings.xml > [artifact:dependencies] Maven Ant Tasks version: 2.0.10 > [artifact:dependencies] Using local repository: C:\Documents and > Settings\kjacobse\.m2\repository > [artifact:dependencies] Resolving dependencies... > [artifact:dependencies] Using remote repositories: > - id=enterprise.mvn.repository, url=file:///V:/depot/maven, > releases=enabled, snapshots=enabled > - id=central, > url=http://localhost:8081/nexus/content/repositories/MavenProxy/, > releases=enabled, snapshots=disabled > com.mycompany:example:jar:1.1.1 (selected) > [artifact:dependencies] [INFO] artifact xerces:xercesImpl: checking for > updates from enterprise.mvn.repository > [artifact:dependencies] [INFO] artifact xerces:xercesImpl: checking for > updates from central > [artifact:dependencies] An error has occurred while processing the Maven > artifact tasks. > [artifact:dependencies] Diagnosis: > [artifact:dependencies] > [artifact:dependencies] Unable to resolve artifact: Couldn't find a version > in [2.0.0, 2.0.2, 2.2.1, 2.3.0, 2.4.0, 2.5.0, 2.6.0, 2.6.1, 2.6.2, 2.7.1, > 2.8.0] to match range [2.8.1,2.9.1] > [artifact:dependencies] xerces:xercesImpl:jar:null > [artifact:dependencies] > [artifact:dependencies] from the specified remote repositories: > [artifact:dependencies] enterprise.mvn.repository (file:///V:/depot/maven), > [artifact:dependencies] central > (http://localhost:8081/nexus/content/repositories/MavenProxy/) > [artifact:dependencies] > [artifact:dependencies] Path to dependency: > [artifact:dependencies] 1) com.mycompany:example:jar:1.1.1 > [artifact:dependencies] > [artifact:dependencies] > [artifact:dependencies] > BUILD FAILED > C:\eclipse\eclipse-workspaces\eclipse-jee-galileo\galileo\build\super-build.xml:406: > Unable to resolve artifact: Couldn't find a version in [2.0.0, 2.0.2, 2.2.1, > 2.3.0, 2.4.0, 2.5.0, 2.6.0, 2.6.1, 2.6.2, 2.7.1, 2.8.0] to match range > [2.8.1,2.9.1] > xerces:xercesImpl:jar:null > from the specified remote repositories: > enterprise.mvn.repository (file:///V:/depot/maven), > central (http://localhost:8081/nexus/content/repositories/MavenProxy/) > Path to dependency: > 1) com.mycompany:example:jar:1.1.1 > at > org.apache.maven.artifact.ant.DependenciesTask.doExecute(DependenciesTask.java:175) > at > org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractArtifactTask.java:678) > at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at > org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) > at org.apache.tools.ant.Task.perform(Task.java:348) > at org.apache.tools.ant.Target.execute(Target.java:357) > at org.apache.tools.ant.Target.performTasks(Target.java:385) > at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) > at org.apache.tools.ant.Project.executeTarget(Project.java:1306) > at > o
[jira] Closed: (MEV-639) log4j bad metadata
[ http://jira.codehaus.org/browse/MEV-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-639. -- Resolution: Fixed Assignee: Carlos Sanchez > log4j bad metadata > -- > > Key: MEV-639 > URL: http://jira.codehaus.org/browse/MEV-639 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid Metadata >Reporter: Borut Bolcina >Assignee: Carlos Sanchez > > why there are no 1.2.14 and 1.2.15 versions in at > http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml > > log4j > log4j > 1.1.3 > > > 1.1.3 > 1.2.4 > 1.2.5 > 1.2.6 > 1.2.7 > 1.2.8 > 1.2.11 > 1.2.9 > 1.2.12 > 1.2.13 > > > -- 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: (MRELEASE-520) A comma separated list of release goals causes the release:perform goal to fail
A comma separated list of release goals causes the release:perform goal to fail --- Key: MRELEASE-520 URL: http://jira.codehaus.org/browse/MRELEASE-520 Project: Maven 2.x Release Plugin Issue Type: Bug Components: documentation Affects Versions: 2.0-beta-9 Reporter: Kurt Zettel A space separated list of goals works fine but a comma separated list of goals is causing the build to fail. The documents should be updated if this is not supported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MEV-649) log4j 1.2.15 points to nonfuctional maven-repository.dev.java.net packages breaking whole build
[ http://jira.codehaus.org/browse/MEV-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-649. -- Resolution: Won't Fix Assignee: Carlos Sanchez Log4j team need to fix the pom for their next release, you need to talk to them. They probably want to make these dependencies optional and they must remove the repositories section 1) com.sun.jmx:jmxri:jar:1.2.1 2) com.sun.jdmk:jmxtools:jar:1.2.1 3) javax.jms:jms:jar:1.1 In the meantime you can exclude them > log4j 1.2.15 points to nonfuctional maven-repository.dev.java.net packages > breaking whole build > --- > > Key: MEV-649 > URL: http://jira.codehaus.org/browse/MEV-649 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Jan Uhlir >Assignee: Carlos Sanchez > > Log4j 2.1.15 dependency from central repository has dependencies linked to > https://maven-repository.dev.java.net/nonav/repository - jmxri, jmxtools and > java mail (and others?). These denpendencies are broken or the whole external > repository is unaccesible by now. > Is it even permitted to have "external" dependency for a package in central > repository? > I found it hard to find how to disable a repository (block a repository) so I > am using this opportunity for a micro how to for unlucky ones like me. > Troubled dependency definition: > > log4j > log4j > 1.2.15 > > Error log (shortened) -- > [INFO] Scanning for projects... > ... > [INFO] Copying 1 resource > Downloading: > https://maven-repository.dev.java.net/nonav/repository/com.sun.jmx/jars/jmxri-1.2.1.jar > Downloading: > https://maven-repository.dev.java.net/nonav/repository/com.sun.jdmk/jars/jmxtools-1.2.1.jar > 353/353b > 353b downloaded (jmxri-1.2.1.jar) > 357/357b > 357b downloaded (jmxtools-1.2.1.jar) > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > 'a55ce8e95c9bb027e78557acc9e2b973fe3c611e'; remote = ' Downloading: > https://maven-repository.dev.java.net/nonav/repository/com.sun.jmx/jars/jmxri-1.2.1.jar > 353/353b > 353b downloaded (jmxri-1.2.1.jar) > [WARNING] [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local > = 'a55ce8e95c9bb027e78557acc9e2b973fe3c611e'; remote = ' *** CHECKSUM FAILED - Checksum failed on download: local = > '9e1dae7682d2b60d5b17b7d47e20d99d70ba65cf'; remote = ' Downloading: > https://maven-repository.dev.java.net/nonav/repository/com.sun.jdmk/jars/jmxtools-1.2.1.jar > 357/357b > 357b downloaded (jmxtools-1.2.1.jar) > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '9e1dae7682d2b60d5b17b7d47e20d99d70ba65cf'; remote = ' ... > [INFO] Compilation failure > ... > error: error reading > /opt/javalibs/com/sun/jdmk/jmxtools/1.2.1/jmxtools-1.2.1.jar; error in > opening zip file > error: error reading /opt/javalibs/com/sun/jmx/jmxri/1.2.1/jmxri-1.2.1.jar; > error in opening zip file > Solution (1) - Disable repository (settings.xml). > Note, it is much more tricky that it seems to be! It gave me hard time before > I found out. Documentation should be improved here. > 1) Tricky, you have to do it for releases and snapshots. There is no > repository wide disabling option. > 2) You have to provide not just same (failing) repository URL but more > importantly the same repository ID as it is in ill referencig POM (log4j > 2.1.15 in our case) > 3) Blacklisting repository is something completely different then disabling. > Not usable in this case (?). It is not ad hoc settable by user anyway > OK, here is the code: > > default > ... > > > java.net > > > https://maven-repository.dev.java.net/nonav/repository > > false > > > false > > > > > Solution (2) - exclude the "external" sub-dependencies of log4j 2.1.15, like > jmxri, jmxtools and java mail. And perhaps others. It takes more time to > figure out what else "external". > Solution (3) - the best one. Use version log4j 2.1.14 instead. It seems to be > OK. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MEV-427) relocate ehcache:ehcache to net.sf.ehcache
[ http://jira.codehaus.org/browse/MEV-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-427. -- Resolution: Won't Fix Assignee: Carlos Sanchez we just do it for the last version to avoid changing previous poms > relocate ehcache:ehcache to net.sf.ehcache > -- > > Key: MEV-427 > URL: http://jira.codehaus.org/browse/MEV-427 > Project: Maven Evangelism > Issue Type: Bug > Components: Relocation >Reporter: fabrizio giustina >Assignee: Carlos Sanchez > > version 1.2 of ehcache has already been relocated to groupid net.sf.ehcache, > relocation should also be performed for all the previous versions (0.6, 0.7, > 0.9, 1.0, 1.1, 1.2beta4) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MEV-604) bump com.oracle/ojdbc14 to 10.2.0.4.0
[ http://jira.codehaus.org/browse/MEV-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-604. -- Resolution: Fixed Assignee: Carlos Sanchez > bump com.oracle/ojdbc14 to 10.2.0.4.0 > - > > Key: MEV-604 > URL: http://jira.codehaus.org/browse/MEV-604 > Project: Maven Evangelism > Issue Type: Improvement >Reporter: Craig >Assignee: Carlos Sanchez > > 10.2.0.4.0 has been released. It would be nice to have a pom in the > repository for it. Thanks! -- 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: (MSITE-443) add a reportingManagement section
[
http://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209104#action_209104
]
Sven Ludwig commented on MSITE-443:
---
I want to add an idea how to solve this issue. It could be done by offering a
new boolean property in the reporting section like "honorPluginManagement".
Default should be false, but if it is set to true, the plugins in the reporting
section would use the respective configurations in pluginManagement. It should
then also be possible to override pluginManagement settings in the reporting
section. Moreover, it should work no matter if the reporting section is in the
same pom as the pluginManagement section, or if it is further down the
inheritance tree. At least from my current personal perspective, this would be
a good solution. ;-)
I can see however that some people may want a separate pluginManagement-like
section within the reporting section.
> add a reportingManagement section
> -
>
> Key: MSITE-443
> URL: http://jira.codehaus.org/browse/MSITE-443
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
>Reporter: Indrajit Raychaudhuri
> Fix For: 3.0-alpha-1
>
>
> Consider the following POM:
> {code:xml}
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> false
>
>
>
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
>
>
>
> {code}
> {{mvn site:site}} doesn't honor the javadoc configuration specified in the
> {{}} section.
> However, {{mvn javadoc:javadoc}} honors them.
> This is true not just for javadoc but other plugins like checkstyle as well.
> I guess, the {{}} section doesn't use the {{}}
> section at all.
--
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
