[jira] Commented: (MRELEASE-588) Improve snapshot dependency handling of parent artifacts
[
http://jira.codehaus.org/browse/MRELEASE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235569#action_235569
]
Marcus Linke commented on MRELEASE-588:
---
I think a should give it a try... ;) For what version is your patch for? I
suggest to merge the patches from MRELEASE-583, MRELEASE-588 and MRELEASE-350
into one. After that the discussed changes from MRELEASE-588 (improved version
prompting) could be implemented. But i dont know if this is desired by the core
developer. Any comments?
> Improve snapshot dependency handling of parent artifacts
>
>
> Key: MRELEASE-588
> URL: http://jira.codehaus.org/browse/MRELEASE-588
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
>Affects Versions: 2.0
>Reporter: Elliot Metsger
> Fix For: 2.1
>
> Attachments: Dependency_handling_of_parent_artifacts.patch
>
>
> This builds on the patch in MRELEASE-583, where the user is prompted for the
> release version of snapshot dependencies.
> However, when the snapshot dependency to be resolved is the parent artifact
> of the project being released, the version supplied by the user is not used
> in the transformed release version of the pom.
> For example, I want to release the following:
> {code}
>
> org.dataconservancy
> project-pom
> 1.0.0-SNAPSHOT
>
> org.dataconservancy
> parent-pom
> 1.0.0-SNAPSHOT
>
> ...
>
> {code}
> If I have MRELEASE-583 applied, I go through the snapshot resolution dialog:
> {code}
> There are still some remaining snapshot dependencies.: Do you want to resolve
> them now? (yes/no) no: : yes
> Dependency type to resolve,: specify the selection number ( 0:All 1:Project
> Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
> Resolve Project Dependency Snapshots.: 'org.dataconservancy:parent-pom' set
> to release? (yes/no) yes: : yes
> What is the release version? 1.0.0: : 1.0.0-test
> {code}
> The resulting release pom doesn't use 1.0.0-test as the parent version. It
> uses 1.0.0:
> {code}
>
> org.dataconservancy
> project-pom
> 1.0.0-test
>
> org.dataconservancy
> parent-pom
> 1.0.0
>
> ...
>
> {code}
--
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] Issue Comment Edited: (MRELEASE-588) Improve snapshot dependency handling of parent artifacts
[
http://jira.codehaus.org/browse/MRELEASE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235569#action_235569
]
Marcus Linke edited comment on MRELEASE-588 at 9/17/10 2:47 AM:
I think a should give it a try... ;) For what version is your patch for? I
suggest to merge the patches from MRELEASE-583, MRELEASE-588 and MRELEASE-350
into one. After that the discussed changes from MRELEASE-583 (improved version
prompting) could be implemented. But i dont know if this is desired by the core
developer. Any comments?
was (Author: mlinke):
I think a should give it a try... ;) For what version is your patch for? I
suggest to merge the patches from MRELEASE-583, MRELEASE-588 and MRELEASE-350
into one. After that the discussed changes from MRELEASE-588 (improved version
prompting) could be implemented. But i dont know if this is desired by the core
developer. Any comments?
> Improve snapshot dependency handling of parent artifacts
>
>
> Key: MRELEASE-588
> URL: http://jira.codehaus.org/browse/MRELEASE-588
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
>Affects Versions: 2.0
>Reporter: Elliot Metsger
> Fix For: 2.1
>
> Attachments: Dependency_handling_of_parent_artifacts.patch
>
>
> This builds on the patch in MRELEASE-583, where the user is prompted for the
> release version of snapshot dependencies.
> However, when the snapshot dependency to be resolved is the parent artifact
> of the project being released, the version supplied by the user is not used
> in the transformed release version of the pom.
> For example, I want to release the following:
> {code}
>
> org.dataconservancy
> project-pom
> 1.0.0-SNAPSHOT
>
> org.dataconservancy
> parent-pom
> 1.0.0-SNAPSHOT
>
> ...
>
> {code}
> If I have MRELEASE-583 applied, I go through the snapshot resolution dialog:
> {code}
> There are still some remaining snapshot dependencies.: Do you want to resolve
> them now? (yes/no) no: : yes
> Dependency type to resolve,: specify the selection number ( 0:All 1:Project
> Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
> Resolve Project Dependency Snapshots.: 'org.dataconservancy:parent-pom' set
> to release? (yes/no) yes: : yes
> What is the release version? 1.0.0: : 1.0.0-test
> {code}
> The resulting release pom doesn't use 1.0.0-test as the parent version. It
> uses 1.0.0:
> {code}
>
> org.dataconservancy
> project-pom
> 1.0.0-test
>
> org.dataconservancy
> parent-pom
> 1.0.0
>
> ...
>
> {code}
--
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: (MRELEASE-350) Option '0' for "specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ):" is broken
[ http://jira.codehaus.org/browse/MRELEASE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235573#action_235573 ] Marcus Linke commented on MRELEASE-350: --- The default for the following prompt while release:prepare is '1': 'Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1:' If handle only project dependencies per default than at least parent artifact snapshots remain in the pom which should be avoided. In my opinion the default should be changed to '0' to prevent all snapshot versions in the pom. > Option '0' for "specify the selection number ( 0:All 1:Project Dependencies > 2:Plugins 3:Reports 4:Extensions ):" is broken > -- > > Key: MRELEASE-350 > URL: http://jira.codehaus.org/browse/MRELEASE-350 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0-beta-8 >Reporter: Craig >Priority: Minor > Fix For: 2.1 > > Attachments: MRELEASE-350.patch > > > CheckDependencySnapshotsPhase.java has a bug when processing this prompt with > the 0 option selected: > specify the selection number ( 0:All 1:Project Dependencies 2:Plugins > 3:Reports 4:Extensions ): 0 > When choosing 0: All, the plugin goes through the motions of asking to > resolve snapshot dependencies, but after resolving them, fails saying there > are still snapshot dependencies. > This bug lies with the function resolveSnapshots relying on the function > processSnapshot to remove resolved dependencies from the set. This works for > all cases except 0, which creates a new dependency set -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-4804) EJB dependencies are included when using the ejb-client packaging/type
[ http://jira.codehaus.org/browse/MNG-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Ruijgers updated MNG-4804: - Attachment: maven-artifact-components.xml.patch just noticed i used the wrong boolean value. the value should be true > EJB dependencies are included when using the ejb-client packaging/type > -- > > Key: MNG-4804 > URL: http://jira.codehaus.org/browse/MNG-4804 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Dependencies >Affects Versions: 2.0.11, 2.2.1 >Reporter: Jeroen Ruijgers > Attachments: maven-artifact-components.xml.patch, > maven-artifact-components.xml.patch > > > When generating an EJB-client module and including it in your project, the > EJB dependencies are included in your project. This is unnecessary behaviour, > because the EJB with it's dependencies will be deployed separately and the > only files needed are in de EJB-client library. These dependencies are easely > excluded in the compontens.xml by setting the includesDependencies property > from DefaultArtifactHandler. > Patch attachted -- 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: (MDOAP-27) Generated files aren't useable with Jena
Generated files aren't useable with Jena Key: MDOAP-27 URL: http://jira.codehaus.org/browse/MDOAP-27 Project: Maven 2.x DOAP Plugin Issue Type: Bug Reporter: Christian Mahnke I'm generating a DOAP file for deployment, the resulting file isn't parseable by Jena, here the exception: Caused by: com.hp.hpl.jena.rdf.model.LiteralRequiredException: Apache UGH metadata library at com.hp.hpl.jena.rdf.model.impl.StatementImpl.getLiteral(StatementImpl.java:101) at com.hp.hpl.jena.rdf.model.impl.StatementBase.getString(StatementBase.java:127) at uk.ac.osswatch.simal.model.jena.Resource.getLiteralValue(Resource.java:198) at uk.ac.osswatch.simal.model.jena.DoapResource.getName(DoapResource.java:77) at uk.ac.osswatch.simal.wicket.panel.ProjectSummaryPanel.populatePage(ProjectSummaryPanel.java:83) at uk.ac.osswatch.simal.wicket.panel.ProjectSummaryPanel.(ProjectSummaryPanel.java:65) at uk.ac.osswatch.simal.wicket.UserHomePage.(UserHomePage.java:32) ... 32 more The offending fragment of the DOAP file: Note the spaces in the rdf:resource attribute. The Plugin should probably do a sanity check. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-4815) (3.0-RC1) Maven Java API does not give nice error messages when improperly configured
[
http://jira.codehaus.org/browse/MNG-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4815:
---
Description:
I get nullpointers all over the place if I do not set up the configuration
options exactly as maven requires them. This is fine, but not a very friendly
experience for developers trying to figure out how to use the API.
This is a correct/simple bootstrap (see below,) but if any or many of the
methods are not called "just so" a nullpointer will result. Better error
messages should be provided, such as:
"No LocalRepositoryManager was configured in the RespositorySession - this may
not be null."
Etc...
{noformat}
/*
* JBoss, Home of Professional Open Source
* Copyright 2010, Red Hat, Inc., and individual contributors
* by the @authors tag. See the copyright.txt in the distribution for a
* full listing of individual contributors.
*
* This is free software; you can redistribute it and/or modify it
* under the terms of the GNU Lesser General Public License as
* published by the Free Software Foundation; either version 2.1 of
* the License, or (at your option) any later version.
*
* This software is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this software; if not, write to the Free
* Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
* 02110-1301 USA, or see the FSF site: http://www.fsf.org.
*/
package org.jboss.arqmvn;
import java.io.File;
import java.util.ArrayList;
import org.apache.maven.artifact.repository.ArtifactRepository;
import org.apache.maven.artifact.repository.ArtifactRepositoryPolicy;
import org.apache.maven.artifact.repository.MavenArtifactRepository;
import org.apache.maven.artifact.repository.layout.ArtifactRepositoryLayout;
import org.apache.maven.project.DefaultProjectBuildingRequest;
import org.apache.maven.project.ProjectBuilder;
import org.apache.maven.project.ProjectBuildingException;
import org.apache.maven.project.ProjectBuildingRequest;
import org.apache.maven.project.ProjectBuildingResult;
import org.codehaus.plexus.DefaultPlexusContainer;
import org.codehaus.plexus.logging.console.ConsoleLoggerManager;
import org.sonatype.aether.impl.internal.SimpleLocalRepositoryManager;
import org.sonatype.aether.util.DefaultRepositorySystemSession;
/**
* @author mailto:lincolnbax...@gmail.com";>Lincoln Baxter, III
*/
public class MavenFacet
{
private final ProjectBuildingRequest request = new
DefaultProjectBuildingRequest();
private DefaultPlexusContainer container = null;
private ProjectBuilder builder = null;
private void bootstrapMaven()
{
if (!initialized())
{
try
{
container = new DefaultPlexusContainer();
ConsoleLoggerManager loggerManager = new ConsoleLoggerManager();
loggerManager.setThreshold("ERROR");
container.setLoggerManager(loggerManager);
builder = container.lookup(ProjectBuilder.class);
// TODO this needs to be configurable via the project/.sidekick
file.
String localRepository = getUserHomeDir().getAbsolutePath() +
"/.m2/repository";
request.setLocalRepository(new MavenArtifactRepository(
"local", new
File(localRepository).toURI().toURL().toString(),
container.lookup(ArtifactRepositoryLayout.class),
new ArtifactRepositoryPolicy(true,
ArtifactRepositoryPolicy.UPDATE_POLICY_NEVER,
ArtifactRepositoryPolicy.CHECKSUM_POLICY_WARN),
new ArtifactRepositoryPolicy(true,
ArtifactRepositoryPolicy.UPDATE_POLICY_NEVER,
ArtifactRepositoryPolicy.CHECKSUM_POLICY_WARN)));
request.setRemoteRepositories(new ArrayList());
DefaultRepositorySystemSession repositorySession = new
DefaultRepositorySystemSession();
repositorySession.setLocalRepositoryManager(new
SimpleLocalRepositoryManager(localRepository));
repositorySession.setOffline(true);
request.setRepositorySession(repositorySession);
request.setProcessPlugins(true);
request.setResolveDependencies(true);
// request.setOffline(true);
}
catch (Exception e)
{
throw new RuntimeException(e);
}
}
}
private boolean initialized()
{
return request == null;
}
/*
* POM manipulation methods
*/
public ProjectBuildingResult getProjectBuildingResult()
{
bootstrapMaven();
try
{
ProjectBuildingResult buildingResult = builder.build(getP
[jira] Closed: (MNG-4813) org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate fails with Maven 3.0-RC1
[
http://jira.codehaus.org/browse/MNG-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4813.
--
Resolution: Not A Bug
Assignee: Benjamin Bentmann
Turns out to be a bug in {{org.jboss.jdocbook.xslt.resolve.ClasspathResolver}}
which passes invalid resource names into {{ClassLoader.getResource()}}:
{noformat}
public Source resolve(String href, String base) throws TransformerException {
// href would need to start with classpath:
if ( !href.startsWith( "classpath:" ) ) {
return null;
}
try {
URL url = classLoader.getResource( href.substring(10) );
return new StreamSource( url.openStream(), url.toExternalForm() );
}
catch ( Throwable t ) {
return null;
}
}
{noformat}
e.g. for "classpath:/xslt/org/jboss/xhtml-single.xsl", the class loader is
asked for "/xslt/org/jboss/xhtml-single.xsl" (note the leading slash) instead
of "xslt/org/jboss/xhtml-single.xsl".
> org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate fails with Maven
> 3.0-RC1
> -
>
> Key: MNG-4813
> URL: http://jira.codehaus.org/browse/MNG-4813
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0-alpha-6, 3.0-alpha-7, 3.0-beta-1, 3.0-beta-2,
> 3.0-beta-3
>Reporter: Arnaud Heritier
>Assignee: Benjamin Bentmann
>
> Module to reproduce :
> https://anonsvn.jboss.org/repos/exo-jcr/jcr/trunk/docs/reference/en
> You'll probably need this repo to build :
> http://repository.exoplatform.org/public
> The error :
> {code}
> [INFO] --- maven-jdocbook-plugin:2.1.1:generate (default-generate) @
> reference-docs-en ---
> Error at xsl:import on line 12 of
> jar:file:/Users/arnaud/.m2/repository/org/exoplatform/doc/exo-docbook-xslt/1/exo-docbook-xslt-1.jar!/xslt/org/exojcr/xhtml.xsl:
> Malformed URL classpath:/xslt/org/jboss/xhtml.xsl(base
> jar:file:/Users/arnaud/.m2/repository/org/exoplatform/doc/exo-docbook-xslt/1/exo-docbook-xslt-1.jar!/xslt/org/exojcr/xhtml.xsl):
> unknown protocol: classpath
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.898s
> [INFO] Finished at: Thu Sep 16 22:13:39 CEST 2010
> [INFO] Final Memory: 7M/125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate
> (default-generate) on project reference-docs-en: XSLT problem: unable to
> build transformer [null] : Failed to compile stylesheet. 1 error detected. ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate
> (default-generate) on project reference-docs-en: XSLT problem
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: XSLT problem
> at
> org.jboss.maven.pl
[jira] Created: (MEAR-131) Default value for earSourceDirectory param missing
Default value for earSourceDirectory param missing
--
Key: MEAR-131
URL: http://jira.codehaus.org/browse/MEAR-131
Project: Maven 2.x Ear Plugin
Issue Type: Bug
Affects Versions: 2.4.2
Environment: n/a
Reporter: Anders Hammar
In the docs for the earSourceDirectory param is states:
earSourceDirectory:
Single directory for extra files to include in the EAR.
* Type: java.io.File
* Required: Yes
* Expression: ${basedir}/src/main/application
The expression value is weird and should, I think, rather be the default value
(which it is). As it is now, the default value is not clearly stated in the
docs nor when using the help goal.
--
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: (MEAR-132) State default value for generateApplicationXml
[ http://jira.codehaus.org/browse/MEAR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235594#action_235594 ] Anders Hammar commented on MEAR-132: Affected version is 2.4.2. > State default value for generateApplicationXml > -- > > Key: MEAR-132 > URL: http://jira.codehaus.org/browse/MEAR-132 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement > Environment: n/a >Reporter: Anders Hammar > > The default value for the generateApplicationXml param is 'true'. But this is > not stated in the docs or when using the help goal. I believe what's missing > is this in the org.apache.maven.plugin.ear.GenerateApplicationXmlMojo class: > /** > * Whether the application.xml should be generated or not. > * > * @parameter default-value="true" > */ > private Boolean generateApplicationXml = Boolean.TRUE; -- 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: (MEAR-132) State default value for generateApplicationXml
State default value for generateApplicationXml -- Key: MEAR-132 URL: http://jira.codehaus.org/browse/MEAR-132 Project: Maven 2.x Ear Plugin Issue Type: Improvement Environment: n/a Reporter: Anders Hammar The default value for the generateApplicationXml param is 'true'. But this is not stated in the docs or when using the help goal. I believe what's missing is this in the org.apache.maven.plugin.ear.GenerateApplicationXmlMojo class: /** * Whether the application.xml should be generated or not. * * @parameter default-value="true" */ private Boolean generateApplicationXml = Boolean.TRUE; -- 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: (DOXIA-408) Test failures on Windows
[
http://jira.codehaus.org/browse/DOXIA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235595#action_235595
]
Lukas Theussl commented on DOXIA-408:
-
I have no windows box to reproduce but this sounds weird: there should be no
new-lines at all, neither in the actual nor especially in the expected result
(see e.g. XdocSinkTest, line 129). And why does it only fail for lists and
tables, I see no special treatment for those tags?
> Test failures on Windows
>
>
> Key: DOXIA-408
> URL: http://jira.codehaus.org/browse/DOXIA-408
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Xdoc
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.5.0_22
> Java home: C:\Program\Java\jdk1.5.0_22\jre
> Default locale: sv_SE, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Dennis Lundberg
> Attachments:
> org.apache.maven.doxia.module.xdoc.XmlWriterXdocSinkTest.txt
>
>
> mvn test in the xdoc module of the current trunk produces this output
> {noformat}
> ...
> Failed tests:
> testList(org.apache.maven.doxia.module.xdoc.XmlWriterXdocSinkTest)
> testNumberedList(org.apache.maven.doxia.module.xdoc.XmlWriterXdocSinkTest)
> testDefinitionList(org.apache.maven.doxia.module.xdoc.XmlWriterXdocSinkTest)
> testTable(org.apache.maven.doxia.module.xdoc.XmlWriterXdocSinkTest)
> Tests run: 117, Failures: 4, Errors: 0, Skipped: 0
> ...
> {noformat}
> The failures has to do with differences in line breaks for list, ordered
> list, definition list and table. See attached Surefire report.
> The actual results have one line break *less* than expected, which is odd
> considering that Windows usually get *more* line breaks. The errors might be
> due to differences between org.codehaus.plexus.util.xml.PrettyPrintXMLWriter
> and org.codehaus.plexus.util.xml.XmlUtil.prettyFormat().
--
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: (MASSEMBLY-327) Using filtered within dependencySet unpackOptions
[
http://jira.codehaus.org/browse/MASSEMBLY-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235598#action_235598
]
Luca commented on MASSEMBLY-327:
no news on this issue?
I suppose plexus-archiver must be enhanced for use interpolation or return the
list of extracted files.
A workaround could be:
false
my.group:myartifact
${project.build.directory}/assembly-tmp
true
true
${project.build.directory}/assembly-tmp
.
true
**
the problem is that the plugin reorder the sets and moves fileSets before
dependencySets.
> Using filtered within dependencySet unpackOptions
> -
>
> Key: MASSEMBLY-327
> URL: http://jira.codehaus.org/browse/MASSEMBLY-327
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-2
>Reporter: Andy Yeung
>
> The files within the unpacked jar did not apply the filters defined.
> pom configuration includes
>
>
>
> src/assemble/filter.properties
>
>
> which contains
>storage.id=abcde
> assembly.xml defines dependency set
>
> /snp-agent1
> true
>
> true
>
> runtime
>
>
> XXX.agent:agent-ear-config
>
>
>
> However, the files within are not filtered.
--
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: (MEAR-131) Default value for earSourceDirectory param missing
[
http://jira.codehaus.org/browse/MEAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235604#action_235604
]
Stephane Nicoll commented on MEAR-131:
--
What is weird about the expression? you mean it's missing the default-value
annotation?
> Default value for earSourceDirectory param missing
> --
>
> Key: MEAR-131
> URL: http://jira.codehaus.org/browse/MEAR-131
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: n/a
>Reporter: Anders Hammar
>
> In the docs for the earSourceDirectory param is states:
> earSourceDirectory:
> Single directory for extra files to include in the EAR.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${basedir}/src/main/application
> The expression value is weird and should, I think, rather be the default
> value (which it is). As it is now, the default value is not clearly stated in
> the docs nor when using the help goal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MEAR-132) State default value for generateApplicationXml
[ http://jira.codehaus.org/browse/MEAR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEAR-132: - Affects Version/s: 2.4.2 > State default value for generateApplicationXml > -- > > Key: MEAR-132 > URL: http://jira.codehaus.org/browse/MEAR-132 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.4.2 > Environment: n/a >Reporter: Anders Hammar > > The default value for the generateApplicationXml param is 'true'. But this is > not stated in the docs or when using the help goal. I believe what's missing > is this in the org.apache.maven.plugin.ear.GenerateApplicationXmlMojo class: > /** > * Whether the application.xml should be generated or not. > * > * @parameter default-value="true" > */ > private Boolean generateApplicationXml = Boolean.TRUE; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-286) Typo in documentation
Typo in documentation - Key: MDEP-286 URL: http://jira.codehaus.org/browse/MDEP-286 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: copy-dependencies Affects Versions: 2.1 Environment: Documentation Reporter: Gerard Weatherby Assignee: Brian Fox Typo on http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html, excludeArtifactIds, change "too exclude" to "to exclude" -- 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: (MPH-79) help:active-profiles does not list active inherited profiles
help:active-profiles does not list active inherited profiles Key: MPH-79 URL: http://jira.codehaus.org/browse/MPH-79 Project: Maven 2.x Help Plugin Issue Type: Bug Affects Versions: 2.2 Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100) Windows (XP,2003,2008), Java 1.6 Reporter: Xavier D. Priority: Minor The code fix for http://jira.codehaus.org/browse/MPH-16 appears to have been removed and the test now breaks. Refer to http://jira.codehaus.org/browse/MPH-16 for the Testcase zip 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: (MEAR-131) Default value for earSourceDirectory param missing
[
http://jira.codehaus.org/browse/MEAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235608#action_235608
]
Anders Hammar commented on MEAR-131:
Yes, it is missing the default-value annotation. Regarding the expression, I
though that was for the possibility to specify the value from CLI. Thus, I find
the current one very weird. But, I'm no maven plugin implementation expert.
> Default value for earSourceDirectory param missing
> --
>
> Key: MEAR-131
> URL: http://jira.codehaus.org/browse/MEAR-131
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Stephane Nicoll
>
> In the docs for the earSourceDirectory param is states:
> earSourceDirectory:
> Single directory for extra files to include in the EAR.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${basedir}/src/main/application
> The expression value is weird and should, I think, rather be the default
> value (which it is). As it is now, the default value is not clearly stated in
> the docs nor when using the help goal.
--
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: (MEAR-131) Default value for earSourceDirectory param missing
[
http://jira.codehaus.org/browse/MEAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235609#action_235609
]
Anders Hammar commented on MEAR-131:
According to
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html:
"The expression parameter can be used to allow configuration of the mojo
parameter from the command line by referencing a system property that the user
sets via the -D option."
How would that be possible with the current expression?
> Default value for earSourceDirectory param missing
> --
>
> Key: MEAR-131
> URL: http://jira.codehaus.org/browse/MEAR-131
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Stephane Nicoll
>
> In the docs for the earSourceDirectory param is states:
> earSourceDirectory:
> Single directory for extra files to include in the EAR.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${basedir}/src/main/application
> The expression value is weird and should, I think, rather be the default
> value (which it is). As it is now, the default value is not clearly stated in
> the docs nor when using the help goal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4817) Unable to use gwt-maven-plugin 1.3-SNAPSHOT
Unable to use gwt-maven-plugin 1.3-SNAPSHOT
---
Key: MNG-4817
URL: http://jira.codehaus.org/browse/MNG-4817
Project: Maven 2 & 3
Issue Type: Bug
Components: POM
Affects Versions: 3.0
Environment: Ubuntu 10.10
Reporter: Jacek Furmankiewicz
Tried to create a project using the gwt-maven plugin. After generating the
archetype using the current 1.2 version I attempted to update it to 1.3-SNAPSHOT
{code:xml}
org.codehaus.mojo
gwt-maven-plugin
1.3-SNAPSHOT
compile
generateAsync
test
com.rp.portal.campaign.Application/Application.html
{code}
Added the repo for the plugin:
{code:xml}
Codehaus
Codehaus Maven Plugin Repository
http://repository.codehaus.org/org/codehaus/mojo
true
[code}
Got this repeatedly:
{code}
jac...@jacekf:~/src/tmp/portal-campaign$ mvn eclipse:eclipse
[INFO] Scanning for projects...
[WARNING] Failed to retrieve plugin descriptor for
org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT: Failed to parse plugin
descriptor for org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT
(/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar):
error in opening zip file
[WARNING] Error reading plugin group metadata: end tag name must match
start tag name from line 7 (position: TEXT seen ...\n...
@9:8)
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
Downloaded:
http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
(437 B at 1.6 KB/sec)
[WARNING] Failed to read metadata
/home/jacekf/.m2/repository/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata-Codehaus.xml:
end tag name must match start tag name from line 7 (position:
TEXT seen ...\n... @9:8)
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4817) Unable to use gwt-maven-plugin 1.3-SNAPSHOT
[
http://jira.codehaus.org/browse/MNG-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235610#action_235610
]
Jacek Furmankiewicz commented on MNG-4817:
--
The error above is on the mvn eclipse:eclipse plugin, but same thing happens on
mvn gwt:run
{code}
jac...@jacekf:~/src/tmp/portal-campaign$ mvn gwt:run
[INFO] Scanning for projects...
[WARNING] Failed to retrieve plugin descriptor for
org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT: Failed to parse plugin
descriptor for org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT
(/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar):
error in opening zip file
[WARNING] Error reading plugin group metadata: end tag name must match
start tag name from line 7 (position: TEXT seen ...\n...
@9:8)
[WARNING] Error reading plugin group metadata: end tag name must match
start tag name from line 7 (position: TEXT seen ...\n...
@9:8)
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 0.458s
[INFO] Finished at: Fri Sep 17 09:36:43 EDT 2010
[INFO] Final Memory: 3M/73M
[INFO]
[ERROR] Failed to parse plugin descriptor for
org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT
(/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar):
error in opening zip file -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginDescriptorParsingException
jac...@jacekf:~/src/tmp/portal-campaign$
{code}
> Unable to use gwt-maven-plugin 1.3-SNAPSHOT
> ---
>
> Key: MNG-4817
> URL: http://jira.codehaus.org/browse/MNG-4817
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0
> Environment: Ubuntu 10.10
>Reporter: Jacek Furmankiewicz
>
> Tried to create a project using the gwt-maven plugin. After generating the
> archetype using the current 1.2 version I attempted to update it to
> 1.3-SNAPSHOT
> {code:xml}
>
> org.codehaus.mojo
> gwt-maven-plugin
> 1.3-SNAPSHOT
>
>
>
> compile
>
> generateAsync
> test
>
>
>
>
>
> com.rp.portal.campaign.Application/Application.html
>
>
> {code}
> Added the repo for the plugin:
> {code:xml}
>
>
> Codehaus
> Codehaus Maven Plugin Repository
>
> http://repository.codehaus.org/org/codehaus/mojo
>
> true
>
>
>
> [code}
> Got this repeatedly:
> {code}
> jac...@jacekf:~/src/tmp/portal-campaign$ mvn eclipse:eclipse
> [INFO] Scanning for projects...
> [WARNING] Failed to retrieve plugin descriptor for
> org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT: Failed to parse plugin
> descriptor for org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT
> (/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar):
> error in opening zip file
> [WARNING] Error reading plugin group metadata: end tag name must
> match start tag name from line 7 (position: TEXT seen
> ...\n... @9:8)
> Downloading:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> Downloaded:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> (437 B at 1.6 KB/sec)
> [WARNING] Failed to read metadata
> /home/jacekf/.m2/repository/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata-Codehaus.xml:
> end tag name must match start tag name from line 7 (position:
> TEXT seen ...\n... @9:8)
> {code}
--
This message is automatically generated by JIRA.
[jira] Commented: (MEAR-131) Default value for earSourceDirectory param missing
[
http://jira.codehaus.org/browse/MEAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235613#action_235613
]
Stephane Nicoll commented on MEAR-131:
--
you're right. this should be the default-value and not the expression.
> Default value for earSourceDirectory param missing
> --
>
> Key: MEAR-131
> URL: http://jira.codehaus.org/browse/MEAR-131
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Stephane Nicoll
>
> In the docs for the earSourceDirectory param is states:
> earSourceDirectory:
> Single directory for extra files to include in the EAR.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${basedir}/src/main/application
> The expression value is weird and should, I think, rather be the default
> value (which it is). As it is now, the default value is not clearly stated in
> the docs nor when using the help goal.
--
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: (MEAR-131) Default value for earSourceDirectory param missing
[
http://jira.codehaus.org/browse/MEAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235611#action_235611
]
Anders Hammar commented on MEAR-131:
I see no use case for specifying the earSourceDirectory from command line, I
might add.
> Default value for earSourceDirectory param missing
> --
>
> Key: MEAR-131
> URL: http://jira.codehaus.org/browse/MEAR-131
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Stephane Nicoll
>
> In the docs for the earSourceDirectory param is states:
> earSourceDirectory:
> Single directory for extra files to include in the EAR.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${basedir}/src/main/application
> The expression value is weird and should, I think, rather be the default
> value (which it is). As it is now, the default value is not clearly stated in
> the docs nor when using the help goal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4817) Unable to use gwt-maven-plugin 1.3-SNAPSHOT
[
http://jira.codehaus.org/browse/MNG-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235612#action_235612
]
Jacek Furmankiewicz commented on MNG-4817:
--
Full debug
{code}
jac...@jacekf:~/src/tmp/portal-campaign$ mvn gwt:run -X
Apache Maven 3.0-RC1 (r997478; 2010-09-15 15:57:55-0400)
Java version: 1.6.0_20
Java home: /home/jacekf/Dev/Java/JDK/jdk1.6.0_20/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.32-24-generic-pae" arch: "i386" Family: "unix"
[INFO] Error stacktraces are turned on.
[DEBUG] Reading user settings from /home/jacekf/.m2/settings.xml
[DEBUG] Reading global settings from /home/jacekf/bin/maven3/conf/settings.xml
[DEBUG] Using local repository at /home/jacekf/.m2/repository
[INFO] Scanning for projects...
[DEBUG] Extension realms for project com.rp:portal-campaign:war:1.0-SNAPSHOT:
(none)
[DEBUG] Looking up lifecyle mappings for packaging war from
ClassRealm[plexus.core, parent: null]
[DEBUG] Resolving plugin prefix gwt from [org.apache.maven.plugins,
org.codehaus.mojo]
[DEBUG] Calculating update check for
org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT/maven-metadata.xml using policy
daily
[WARNING] Failed to retrieve plugin descriptor for
org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT: Failed to parse plugin
descriptor for org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT
(/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar):
error in opening zip file
org.apache.maven.plugin.PluginDescriptorParsingException: Failed to parse
plugin descriptor for org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT
(/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar):
error in opening zip file
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.extractPluginDescriptor(DefaultMavenPluginManager.java:202)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:139)
at
org.apache.maven.plugin.DefaultBuildPluginManager.loadPlugin(DefaultBuildPluginManager.java:63)
at
org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolveFromProject(DefaultPluginPrefixResolver.java:135)
at
org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolveFromProject(DefaultPluginPrefixResolver.java:118)
at
org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:82)
at
org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:248)
at
org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:208)
at
org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106)
at
org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:86)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:98)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:114)
at java.util.jar.JarFile.(JarFile.java:135)
at java.util.jar.JarFile.(JarFile.java:114)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.extractPluginDescriptor(DefaultMavenPluginManager.java:160)
... 23 more
[DEBUG] Calculating update check for
org.apache.maven.plugins/maven-metadata.xml using policy warn
[DEBUG] Calculating update check for
org.apache.maven.plugins/maven-metadata.xml using policy never
[DEBUG] Calculating update check for org.codehaus
[jira] Commented: (MEAR-131) Default value for earSourceDirectory param missing
[
http://jira.codehaus.org/browse/MEAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235614#action_235614
]
Anders Hammar commented on MEAR-131:
The weird thing is that this value seems to be injected as the default value
somehow anyways, I think. I didn't check the code very thoroughly though.
> Default value for earSourceDirectory param missing
> --
>
> Key: MEAR-131
> URL: http://jira.codehaus.org/browse/MEAR-131
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Stephane Nicoll
>
> In the docs for the earSourceDirectory param is states:
> earSourceDirectory:
> Single directory for extra files to include in the EAR.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${basedir}/src/main/application
> The expression value is weird and should, I think, rather be the default
> value (which it is). As it is now, the default value is not clearly stated in
> the docs nor when using the help goal.
--
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: (MNG-4817) Unable to use gwt-maven-plugin 1.3-SNAPSHOT
[
http://jira.codehaus.org/browse/MNG-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4817.
--
Resolution: Duplicate
Assignee: Benjamin Bentmann
Consequence of inability to follow HTTP->HTTPS redirects (MNG-4428), use
{{https://}} for the plugin repository instead to workaround that.
> Unable to use gwt-maven-plugin 1.3-SNAPSHOT
> ---
>
> Key: MNG-4817
> URL: http://jira.codehaus.org/browse/MNG-4817
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0
> Environment: Ubuntu 10.10
>Reporter: Jacek Furmankiewicz
>Assignee: Benjamin Bentmann
>
> Tried to create a project using the gwt-maven plugin. After generating the
> archetype using the current 1.2 version I attempted to update it to
> 1.3-SNAPSHOT
> {code:xml}
>
> org.codehaus.mojo
> gwt-maven-plugin
> 1.3-SNAPSHOT
>
>
>
> compile
>
> generateAsync
> test
>
>
>
>
>
> com.rp.portal.campaign.Application/Application.html
>
>
> {code}
> Added the repo for the plugin:
> {code:xml}
>
>
> Codehaus
> Codehaus Maven Plugin Repository
>
> http://repository.codehaus.org/org/codehaus/mojo
>
> true
>
>
>
> [code}
> Got this repeatedly:
> {code}
> jac...@jacekf:~/src/tmp/portal-campaign$ mvn eclipse:eclipse
> [INFO] Scanning for projects...
> [WARNING] Failed to retrieve plugin descriptor for
> org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT: Failed to parse plugin
> descriptor for org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT
> (/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar):
> error in opening zip file
> [WARNING] Error reading plugin group metadata: end tag name must
> match start tag name from line 7 (position: TEXT seen
> ...\n... @9:8)
> Downloading:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> Downloaded:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> (437 B at 1.6 KB/sec)
> [WARNING] Failed to read metadata
> /home/jacekf/.m2/repository/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata-Codehaus.xml:
> end tag name must match start tag name from line 7 (position:
> TEXT seen ...\n... @9:8)
> {code}
--
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: (MEAR-131) Default value for earSourceDirectory param missing
[
http://jira.codehaus.org/browse/MEAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235616#action_235616
]
Anders Hammar commented on MEAR-131:
I also see that it's similar case with "generatedDescriptorLocation". Not sure
if we could expand this jira to handle all of these cases?
> Default value for earSourceDirectory param missing
> --
>
> Key: MEAR-131
> URL: http://jira.codehaus.org/browse/MEAR-131
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Stephane Nicoll
>
> In the docs for the earSourceDirectory param is states:
> earSourceDirectory:
> Single directory for extra files to include in the EAR.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${basedir}/src/main/application
> The expression value is weird and should, I think, rather be the default
> value (which it is). As it is now, the default value is not clearly stated in
> the docs nor when using the help goal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4817) Unable to use gwt-maven-plugin 1.3-SNAPSHOT
[
http://jira.codehaus.org/browse/MNG-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235617#action_235617
]
Benjamin Bentmann commented on MNG-4817:
Forgot to mention, your local repository contains garbage by now (HTML files)
which will continue to cause build failures unless manually removed.
> Unable to use gwt-maven-plugin 1.3-SNAPSHOT
> ---
>
> Key: MNG-4817
> URL: http://jira.codehaus.org/browse/MNG-4817
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0
> Environment: Ubuntu 10.10
>Reporter: Jacek Furmankiewicz
>Assignee: Benjamin Bentmann
>
> Tried to create a project using the gwt-maven plugin. After generating the
> archetype using the current 1.2 version I attempted to update it to
> 1.3-SNAPSHOT
> {code:xml}
>
> org.codehaus.mojo
> gwt-maven-plugin
> 1.3-SNAPSHOT
>
>
>
> compile
>
> generateAsync
> test
>
>
>
>
>
> com.rp.portal.campaign.Application/Application.html
>
>
> {code}
> Added the repo for the plugin:
> {code:xml}
>
>
> Codehaus
> Codehaus Maven Plugin Repository
>
> http://repository.codehaus.org/org/codehaus/mojo
>
> true
>
>
>
> [code}
> Got this repeatedly:
> {code}
> jac...@jacekf:~/src/tmp/portal-campaign$ mvn eclipse:eclipse
> [INFO] Scanning for projects...
> [WARNING] Failed to retrieve plugin descriptor for
> org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT: Failed to parse plugin
> descriptor for org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT
> (/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar):
> error in opening zip file
> [WARNING] Error reading plugin group metadata: end tag name must
> match start tag name from line 7 (position: TEXT seen
> ...\n... @9:8)
> Downloading:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> Downloaded:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> (437 B at 1.6 KB/sec)
> [WARNING] Failed to read metadata
> /home/jacekf/.m2/repository/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata-Codehaus.xml:
> end tag name must match start tag name from line 7 (position:
> TEXT seen ...\n... @9:8)
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4817) Unable to use gwt-maven-plugin 1.3-SNAPSHOT
[
http://jira.codehaus.org/browse/MNG-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235618#action_235618
]
Jacek Furmankiewicz commented on MNG-4817:
--
Hm still no luck. I deleted the /org/codehaus/mojo folder from .m2/repository
and updated the plugin repos to uses https and 1.3-SNAPSHOT, different error:
{code}
jac...@jacekf:~/src/tmp/portal-campaign$ mvn gwt:run -X
Apache Maven 3.0-RC1 (r997478; 2010-09-15 15:57:55-0400)
Java version: 1.6.0_20
Java home: /home/jacekf/Dev/Java/JDK/jdk1.6.0_20/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.32-24-generic-pae" arch: "i386" Family: "unix"
[INFO] Error stacktraces are turned on.
[DEBUG] Reading user settings from /home/jacekf/.m2/settings.xml
[DEBUG] Reading global settings from /home/jacekf/bin/maven3/conf/settings.xml
[DEBUG] Using local repository at /home/jacekf/.m2/repository
[INFO] Scanning for projects...
[DEBUG] Extension realms for project com.rp:portal-campaign:war:1.0-SNAPSHOT:
(none)
[DEBUG] Looking up lifecyle mappings for packaging war from
ClassRealm[plexus.core, parent: null]
[DEBUG] Resolving plugin prefix gwt from [org.apache.maven.plugins,
org.codehaus.mojo]
[DEBUG] Calculating update check for
org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT/maven-metadata.xml using policy
daily
Downloading:
https://repository.codehaus.org/org/codehaus/mojo/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/maven-metadata.xml
[DEBUG] Reading resolution tracking file
/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/resolver-status.properties
[DEBUG] Writing resolution tracking file
/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/resolver-status.properties
[DEBUG] Calculating update check for
org.codehaus.mojo:gwt-maven-plugin:jar:1.3-SNAPSHOT using policy daily
Downloading:
https://repository.codehaus.org/org/codehaus/mojo/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar
[DEBUG] Reading resolution tracking file
/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar.lastUpdated
[DEBUG] Writing resolution tracking file
/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar.lastUpdated
[WARNING] Failed to retrieve plugin descriptor for
org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT: Plugin
org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT or one of its dependencies
could not be resolved: The following artifacts could not be resolved:
org.codehaus.mojo:gwt-maven-plugin:jar:1.3-SNAPSHOT: Could not transfer
artifact org.codehaus.mojo:gwt-maven-plugin:jar:1.3-SNAPSHOT from Codehaus
(https://repository.codehaus.org/org/codehaus/mojo, releases=true,
snapshots=true, managed=false): Error transferring file:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
org.apache.maven.plugin.PluginResolutionException: Plugin
org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT or one of its dependencies
could not be resolved: The following artifacts could not be resolved:
org.codehaus.mojo:gwt-maven-plugin:jar:1.3-SNAPSHOT: Could not transfer
artifact org.codehaus.mojo:gwt-maven-plugin:jar:1.3-SNAPSHOT from Codehaus
(https://repository.codehaus.org/org/codehaus/mojo, releases=true,
snapshots=true, managed=false): Error transferring file:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at
org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:96)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:136)
at
org.apache.maven.plugin.DefaultBuildPluginManager.loadPlugin(DefaultBuildPluginManager.java:63)
at
org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolveFromProject(DefaultPluginPrefixResolver.java:135)
at
org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolveFromProject(DefaultPluginPrefixResolver.java:118)
at
org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:82)
at
org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:248)
at
org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:208)
at
org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106)
at
org.apache.maven.li
[jira] Commented: (MNG-4813) org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate fails with Maven 3.0-RC1
[
http://jira.codehaus.org/browse/MNG-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235620#action_235620
]
Arnaud Heritier commented on MNG-4813:
--
But the question is why does it work with Maven 2.x ??
I didn't have the time to test more recent versions of this plugin to see if
the code was improved.
> org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate fails with Maven
> 3.0-RC1
> -
>
> Key: MNG-4813
> URL: http://jira.codehaus.org/browse/MNG-4813
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0-alpha-6, 3.0-alpha-7, 3.0-beta-1, 3.0-beta-2,
> 3.0-beta-3
>Reporter: Arnaud Heritier
>Assignee: Benjamin Bentmann
>
> Module to reproduce :
> https://anonsvn.jboss.org/repos/exo-jcr/jcr/trunk/docs/reference/en
> You'll probably need this repo to build :
> http://repository.exoplatform.org/public
> The error :
> {code}
> [INFO] --- maven-jdocbook-plugin:2.1.1:generate (default-generate) @
> reference-docs-en ---
> Error at xsl:import on line 12 of
> jar:file:/Users/arnaud/.m2/repository/org/exoplatform/doc/exo-docbook-xslt/1/exo-docbook-xslt-1.jar!/xslt/org/exojcr/xhtml.xsl:
> Malformed URL classpath:/xslt/org/jboss/xhtml.xsl(base
> jar:file:/Users/arnaud/.m2/repository/org/exoplatform/doc/exo-docbook-xslt/1/exo-docbook-xslt-1.jar!/xslt/org/exojcr/xhtml.xsl):
> unknown protocol: classpath
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.898s
> [INFO] Finished at: Thu Sep 16 22:13:39 CEST 2010
> [INFO] Final Memory: 7M/125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate
> (default-generate) on project reference-docs-en: XSLT problem: unable to
> build transformer [null] : Failed to compile stylesheet. 1 error detected. ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate
> (default-generate) on project reference-docs-en: XSLT problem
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: XSLT problem
> at
> org.jboss.maven.plugins.jdocbook.AbstractDocBookMojo.execute(AbstractDocBookMojo.java:285)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
> ... 19 more
> Caused by: org.jboss.jdocbook.xslt.XSLTException: unable to build transformer
> [null] : Failed to compile stylesheet. 1 error detected.
> at
> org.jboss.jdocbook.xslt.TransformerBuilder.buildTransformer(TransformerBuilder.java:94)
> at
> org.jboss.jdocbook.xslt.TransformerBuilder.buildTran
[jira] Commented: (MNG-4817) Unable to use gwt-maven-plugin 1.3-SNAPSHOT
[
http://jira.codehaus.org/browse/MNG-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235621#action_235621
]
Brian Fox commented on MNG-4817:
use http://nexus.codehaus.org/snapshots as the repo and you'll avoid all the
redirects
> Unable to use gwt-maven-plugin 1.3-SNAPSHOT
> ---
>
> Key: MNG-4817
> URL: http://jira.codehaus.org/browse/MNG-4817
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0
> Environment: Ubuntu 10.10
>Reporter: Jacek Furmankiewicz
>Assignee: Benjamin Bentmann
>
> Tried to create a project using the gwt-maven plugin. After generating the
> archetype using the current 1.2 version I attempted to update it to
> 1.3-SNAPSHOT
> {code:xml}
>
> org.codehaus.mojo
> gwt-maven-plugin
> 1.3-SNAPSHOT
>
>
>
> compile
>
> generateAsync
> test
>
>
>
>
>
> com.rp.portal.campaign.Application/Application.html
>
>
> {code}
> Added the repo for the plugin:
> {code:xml}
>
>
> Codehaus
> Codehaus Maven Plugin Repository
>
> http://repository.codehaus.org/org/codehaus/mojo
>
> true
>
>
>
> [code}
> Got this repeatedly:
> {code}
> jac...@jacekf:~/src/tmp/portal-campaign$ mvn eclipse:eclipse
> [INFO] Scanning for projects...
> [WARNING] Failed to retrieve plugin descriptor for
> org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT: Failed to parse plugin
> descriptor for org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT
> (/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar):
> error in opening zip file
> [WARNING] Error reading plugin group metadata: end tag name must
> match start tag name from line 7 (position: TEXT seen
> ...\n... @9:8)
> Downloading:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> Downloaded:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> (437 B at 1.6 KB/sec)
> [WARNING] Failed to read metadata
> /home/jacekf/.m2/repository/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata-Codehaus.xml:
> end tag name must match start tag name from line 7 (position:
> TEXT seen ...\n... @9:8)
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4813) org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate fails with Maven 3.0-RC1
[
http://jira.codehaus.org/browse/MNG-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235622#action_235622
]
Benjamin Bentmann commented on MNG-4813:
Because Maven 2.x employs unusual class loaders.
> org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate fails with Maven
> 3.0-RC1
> -
>
> Key: MNG-4813
> URL: http://jira.codehaus.org/browse/MNG-4813
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0-alpha-6, 3.0-alpha-7, 3.0-beta-1, 3.0-beta-2,
> 3.0-beta-3
>Reporter: Arnaud Heritier
>Assignee: Benjamin Bentmann
>
> Module to reproduce :
> https://anonsvn.jboss.org/repos/exo-jcr/jcr/trunk/docs/reference/en
> You'll probably need this repo to build :
> http://repository.exoplatform.org/public
> The error :
> {code}
> [INFO] --- maven-jdocbook-plugin:2.1.1:generate (default-generate) @
> reference-docs-en ---
> Error at xsl:import on line 12 of
> jar:file:/Users/arnaud/.m2/repository/org/exoplatform/doc/exo-docbook-xslt/1/exo-docbook-xslt-1.jar!/xslt/org/exojcr/xhtml.xsl:
> Malformed URL classpath:/xslt/org/jboss/xhtml.xsl(base
> jar:file:/Users/arnaud/.m2/repository/org/exoplatform/doc/exo-docbook-xslt/1/exo-docbook-xslt-1.jar!/xslt/org/exojcr/xhtml.xsl):
> unknown protocol: classpath
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.898s
> [INFO] Finished at: Thu Sep 16 22:13:39 CEST 2010
> [INFO] Final Memory: 7M/125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate
> (default-generate) on project reference-docs-en: XSLT problem: unable to
> build transformer [null] : Failed to compile stylesheet. 1 error detected. ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate
> (default-generate) on project reference-docs-en: XSLT problem
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: XSLT problem
> at
> org.jboss.maven.plugins.jdocbook.AbstractDocBookMojo.execute(AbstractDocBookMojo.java:285)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
> ... 19 more
> Caused by: org.jboss.jdocbook.xslt.XSLTException: unable to build transformer
> [null] : Failed to compile stylesheet. 1 error detected.
> at
> org.jboss.jdocbook.xslt.TransformerBuilder.buildTransformer(TransformerBuilder.java:94)
> at
> org.jboss.jdocbook.xslt.TransformerBuilder.buildTransformer(TransformerBuilder.java:78)
> at
> org.jboss.jdocbook.render.impl.BasicRenderer.buildTra
[jira] Commented: (MNG-4816) Maven 3 fails to follow 301 redirects
[
http://jira.codehaus.org/browse/MNG-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235623#action_235623
]
Jesse Glick commented on MNG-4816:
--
Actually a bit more complicated than I thought. The artifact is also apparently
available in Central (i.e. the command would have worked in any Maven version
if no alternate repository were specified). M3 tries to get it from Codehaus
first (as requested), and misinterprets the 301 as the actual file, as
described in MNG-4428:
{code}
...
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/archetypes/webapp-javaee6/1.1/webapp-javaee6-1.1.jar
Downloaded:
http://repository.codehaus.org/org/codehaus/mojo/archetypes/webapp-javaee6/1.1/webapp-javaee6-1.1.jar
(425 B at 0.9 KB/sec)
...
[DEBUG] Found archetype org.codehaus.mojo.archetypes:webapp-javaee6:1.1 in
cache:
~/.m2/repository/org/codehaus/mojo/archetypes/webapp-javaee6/1.1/webapp-javaee6-1.1.jar
[ERROR] Failed to close zipFile
{code}
M2 (both 2.2.0 and 2.2.1, contrary to MNG-4428 which claims a regression in
2.2.1!) fails to get the artifact from Codehaus at all, but falls back
correctly to Central:
{code}
...
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/archetypes/webapp-javaee6/1.1/webapp-javaee6-1.1.jar
[DEBUG]
http://repository.codehaus.org/org/codehaus/mojo/archetypes/webapp-javaee6/1.1/webapp-javaee6-1.1.jar
- Status code: 404
[DEBUG] File:
http://repository.codehaus.org/org/codehaus/mojo/archetypes/webapp-javaee6/1.1/webapp-javaee6-1.1.jar
does not exist
org.apache.maven.wagon.ResourceDoesNotExistException: File:
http://repository.codehaus.org/org/codehaus/mojo/archetypes/webapp-javaee6/1.1/webapp-javaee6-1.1.jar
does not exist
at
org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:603)
at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:491)
...
[INFO] Unable to find resource
'org.codehaus.mojo.archetypes:webapp-javaee6:jar:1.1' in repository
webapp-javaee6-repo (http://repository.codehaus.org)
[DEBUG] Trying repository central
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] Connecting to repository: 'central' with url:
'http://repo1.maven.org/maven2'.
Downloading:
http://repo1.maven.org/maven2/org/codehaus/mojo/archetypes/webapp-javaee6/1.1/webapp-javaee6-1.1.jar
[DEBUG]
http://repo1.maven.org/maven2/org/codehaus/mojo/archetypes/webapp-javaee6/1.1/webapp-javaee6-1.1.jar
- Status code: 200
...
{code}
This is odd, as curl confirms that the Codehaus server sends a 301 redirect,
not a 404. So in addition to known redirect handling bug in M3, there appears
to also be some transport bug in M2.
> Maven 3 fails to follow 301 redirects
> -
>
> Key: MNG-4816
> URL: http://jira.codehaus.org/browse/MNG-4816
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0-beta-3
> Environment: JDK 6u21, Ubuntu.
>Reporter: Jesse Glick
>
> See https://netbeans.org/bugzilla/show_bug.cgi?id=190033 for steps to
> reproduce, and in particular delete
> ~/.m2/repository/org/codehaus/mojo/archetypes/webapp-javaee6/1.1/webapp-javaee6-1.1.jar
> first. Maven 2.2.1 works; 3.0-beta-3 fails. The difference is that M3 tries
> to download this JAR but the HTTP transport does not handle redirects, so the
> JAR file in the local repo is actually a text file:
> {code}
>
>
> 301 Moved Permanently
>
> Moved Permanently
> The document has moved href="https://nexus.codehaus.org/content/repositories/releases/org/codehaus/mojo/archetypes/webapp-javaee6/1.1/webapp-javaee6-1.1.jar";>here.
>
> Apache/2.0.52 (Red Hat) Server at repository.codehaus.org Port
> 80
>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4817) Unable to use gwt-maven-plugin 1.3-SNAPSHOT
[
http://jira.codehaus.org/browse/MNG-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235624#action_235624
]
Jacek Furmankiewicz commented on MNG-4817:
--
Tested and verified, able to use 1.3-SNAPSHOT now. Good to close as a dup of
MNG-4428, thanks for your help
> Unable to use gwt-maven-plugin 1.3-SNAPSHOT
> ---
>
> Key: MNG-4817
> URL: http://jira.codehaus.org/browse/MNG-4817
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM
>Affects Versions: 3.0
> Environment: Ubuntu 10.10
>Reporter: Jacek Furmankiewicz
>Assignee: Benjamin Bentmann
>
> Tried to create a project using the gwt-maven plugin. After generating the
> archetype using the current 1.2 version I attempted to update it to
> 1.3-SNAPSHOT
> {code:xml}
>
> org.codehaus.mojo
> gwt-maven-plugin
> 1.3-SNAPSHOT
>
>
>
> compile
>
> generateAsync
> test
>
>
>
>
>
> com.rp.portal.campaign.Application/Application.html
>
>
> {code}
> Added the repo for the plugin:
> {code:xml}
>
>
> Codehaus
> Codehaus Maven Plugin Repository
>
> http://repository.codehaus.org/org/codehaus/mojo
>
> true
>
>
>
> [code}
> Got this repeatedly:
> {code}
> jac...@jacekf:~/src/tmp/portal-campaign$ mvn eclipse:eclipse
> [INFO] Scanning for projects...
> [WARNING] Failed to retrieve plugin descriptor for
> org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT: Failed to parse plugin
> descriptor for org.codehaus.mojo:gwt-maven-plugin:1.3-SNAPSHOT
> (/home/jacekf/.m2/repository/org/codehaus/mojo/gwt-maven-plugin/1.3-SNAPSHOT/gwt-maven-plugin-1.3-SNAPSHOT.jar):
> error in opening zip file
> [WARNING] Error reading plugin group metadata: end tag name must
> match start tag name from line 7 (position: TEXT seen
> ...\n... @9:8)
> Downloading:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> Downloaded:
> http://repository.codehaus.org/org/codehaus/mojo/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
> (437 B at 1.6 KB/sec)
> [WARNING] Failed to read metadata
> /home/jacekf/.m2/repository/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata-Codehaus.xml:
> end tag name must match start tag name from line 7 (position:
> TEXT seen ...\n... @9:8)
> {code}
--
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: (MEAR-131) Default value for earSourceDirectory param missing
[
http://jira.codehaus.org/browse/MEAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235625#action_235625
]
Stephane Nicoll commented on MEAR-131:
--
I need to revisit all this. Thanks for the report anyway!
> Default value for earSourceDirectory param missing
> --
>
> Key: MEAR-131
> URL: http://jira.codehaus.org/browse/MEAR-131
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: n/a
>Reporter: Anders Hammar
>Assignee: Stephane Nicoll
>
> In the docs for the earSourceDirectory param is states:
> earSourceDirectory:
> Single directory for extra files to include in the EAR.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${basedir}/src/main/application
> The expression value is weird and should, I think, rather be the default
> value (which it is). As it is now, the default value is not clearly stated in
> the docs nor when using the help goal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4818) NPE in legacy.DefaultWagonManager.getArtifact
NPE in legacy.DefaultWagonManager.getArtifact - Key: MNG-4818 URL: http://jira.codehaus.org/browse/MNG-4818 Project: Maven 2 & 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0 Environment: At revision 998131; 1.6.0_21 (32-bit); win7ent-x64 Reporter: Matthew Daniel Attachments: bug.log 1. mvn archetype:create (with your favorite -DgroupId etc) 2. add some non-local dependency to the pom (I used commons-jexl:2.0.1) 3. mvn idea:idea 4. kaboom The problem is that the Logger is declared as @Requirement but it is evidently not being provided (any path leading to a logging statement yields the NPE) I regret that I don't know enough plexus-voodoo to even create a TestCase for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4816) Maven 3 fails to follow 301 redirects
[
http://jira.codehaus.org/browse/MNG-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235626#action_235626
]
Jesse Glick commented on MNG-4816:
--
Complete test case, for reference (works in M2 and fails in M3):
{noformat}
rm -rf ~/.m2/repository/org/codehaus/mojo/archetypes test-MNG-4816
mvn -DarchetypeVersion=1.1 -Darchetype.interactive=false -DgroupId=test
-DarchetypeArtifactId=webapp-javaee6
-DarchetypeRepository=http://repository.codehaus.org -Dversion=1.0-SNAPSHOT
-DarchetypeGroupId=org.codehaus.mojo.archetypes -Dpackage=test
-DartifactId=test-MNG-4816 --batch-mode --debug
org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-5:generate
{noformat}
> Maven 3 fails to follow 301 redirects
> -
>
> Key: MNG-4816
> URL: http://jira.codehaus.org/browse/MNG-4816
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0-beta-3
> Environment: JDK 6u21, Ubuntu.
>Reporter: Jesse Glick
>
> See https://netbeans.org/bugzilla/show_bug.cgi?id=190033 for steps to
> reproduce, and in particular delete
> ~/.m2/repository/org/codehaus/mojo/archetypes/webapp-javaee6/1.1/webapp-javaee6-1.1.jar
> first. Maven 2.2.1 works; 3.0-beta-3 fails. The difference is that M3 tries
> to download this JAR but the HTTP transport does not handle redirects, so the
> JAR file in the local repo is actually a text file:
> {code}
>
>
> 301 Moved Permanently
>
> Moved Permanently
> The document has moved href="https://nexus.codehaus.org/content/repositories/releases/org/codehaus/mojo/archetypes/webapp-javaee6/1.1/webapp-javaee6-1.1.jar";>here.
>
> Apache/2.0.52 (Red Hat) Server at repository.codehaus.org Port
> 80
>
> {code}
--
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-2798) Please sync biz.aQute bnd 0.0.384
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235627#action_235627 ] Juven Xu commented on MAVENUPLOAD-2798: --- see https://issues.sonatype.org/browse/OSSRH-786 > Please sync biz.aQute bnd 0.0.384 > - > > Key: MAVENUPLOAD-2798 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2798 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Max Bowsher >Assignee: Juven Xu > > Please sync groupId=biz.aQute artifactId=bnd version=0.0.384 from the bnd > repository: http://www.aqute.biz/repo/biz/aQute/bnd/0.0.384/ > (There are higher version numbers present in that repository, but the one I > am asking for is the one that the project's web page states is current, and > is in use in the project - Guice - I want to write a better pom for) -- 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: (MRELEASE-588) Improve snapshot dependency handling of parent artifacts
[
http://jira.codehaus.org/browse/MRELEASE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235628#action_235628
]
Elliot Metsger commented on MRELEASE-588:
-
bq. For what version is your patch for?
2.0
bq. After that the discussed changes from MRELEASE-583 (improved version
prompting) could be implemented. But i dont know if this is desired by the core
developer. Any comments?
I'd suggest that discussion happen on MRELEASE-583 instead of here.
> Improve snapshot dependency handling of parent artifacts
>
>
> Key: MRELEASE-588
> URL: http://jira.codehaus.org/browse/MRELEASE-588
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
>Affects Versions: 2.0
>Reporter: Elliot Metsger
> Fix For: 2.1
>
> Attachments: Dependency_handling_of_parent_artifacts.patch
>
>
> This builds on the patch in MRELEASE-583, where the user is prompted for the
> release version of snapshot dependencies.
> However, when the snapshot dependency to be resolved is the parent artifact
> of the project being released, the version supplied by the user is not used
> in the transformed release version of the pom.
> For example, I want to release the following:
> {code}
>
> org.dataconservancy
> project-pom
> 1.0.0-SNAPSHOT
>
> org.dataconservancy
> parent-pom
> 1.0.0-SNAPSHOT
>
> ...
>
> {code}
> If I have MRELEASE-583 applied, I go through the snapshot resolution dialog:
> {code}
> There are still some remaining snapshot dependencies.: Do you want to resolve
> them now? (yes/no) no: : yes
> Dependency type to resolve,: specify the selection number ( 0:All 1:Project
> Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
> Resolve Project Dependency Snapshots.: 'org.dataconservancy:parent-pom' set
> to release? (yes/no) yes: : yes
> What is the release version? 1.0.0: : 1.0.0-test
> {code}
> The resulting release pom doesn't use 1.0.0-test as the parent version. It
> uses 1.0.0:
> {code}
>
> org.dataconservancy
> project-pom
> 1.0.0-test
>
> org.dataconservancy
> parent-pom
> 1.0.0
>
> ...
>
> {code}
--
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] Work started: (MAVENUPLOAD-2798) Please sync biz.aQute bnd 0.0.384
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MAVENUPLOAD-2798 started by Juven Xu. > Please sync biz.aQute bnd 0.0.384 > - > > Key: MAVENUPLOAD-2798 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2798 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Max Bowsher >Assignee: Juven Xu > > Please sync groupId=biz.aQute artifactId=bnd version=0.0.384 from the bnd > repository: http://www.aqute.biz/repo/biz/aQute/bnd/0.0.384/ > (There are higher version numbers present in that repository, but the one I > am asking for is the one that the project's web page states is current, and > is in use in the project - Guice - I want to write a better pom for) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4819) Inheritance Error in Object List Configuration for Custom Plugin
Inheritance Error in Object List Configuration for Custom Plugin Key: MNG-4819 URL: http://jira.codehaus.org/browse/MNG-4819 Project: Maven 2 & 3 Issue Type: Bug Components: Inheritance and Interpolation Affects Versions: 2.2.1 Environment: Windows XP SP3, running under Cygwin bash shell Reporter: Jonathan Pearson Attachments: bugdemo.tgz When a parent defines an object list in a plugin configuration, and then a child of that parent also defines an object list for the same plugin leaving some values undefined (so as to use defaults), the object list is loaded into the plugin in an unpredictable manner, sometimes using parent-defined properties instead of defaults, and sometimes not. The attached plugin/parent/child projects produce this incorrect output: $ mvn inherit_bug_demo:bugdemo ... [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: prop1='Parent Object 1 Property 1', prop2='Child Object 2 Property 2']]'] The expected output would either be: [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: prop1='Child Object 1 Property 1', prop2='Parent Object 1 Property 2'], [DemoObject: prop1='Parent Object 1 Property 1', prop2='Child Object 2 Property 2'], [DemoObject: prop1='Parent Object 3 Property 1', prop2='Parent Object 3 Property 2]]'] Or: [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: prop1='Property 1', prop2='Child Object 2 Property 2']]'] See attached build log, demonstration plugin, and parent/child project for details. Usage: $ cd inherit_bug_demo $ mvn deploy $ cd ../child $ mvn inherit_bug_demo:bugdemo -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4819) Inheritance Error in Object List Configuration for Custom Plugin
[ http://jira.codehaus.org/browse/MNG-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235632#action_235632 ] Jonathan Pearson commented on MNG-4819: --- I'm sorry, I made a mistake in my expected output: The expected output would either be: [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: prop1='Child Object 1 Property 1', prop2='Parent Object 1 Property 2'], [DemoObject: prop1='Parent Object 2 Property 1', prop2='Child Object 2 Property 2'], [DemoObject: prop1='Parent Object 3 Property 1', prop2='Parent Object 3 Property 2]]'] The second DemoObject, first property was listed with incorrect "Parent Object 1...", should have been "Parent Object 2..." > Inheritance Error in Object List Configuration for Custom Plugin > > > Key: MNG-4819 > URL: http://jira.codehaus.org/browse/MNG-4819 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 2.2.1 > Environment: Windows XP SP3, running under Cygwin bash shell >Reporter: Jonathan Pearson > Attachments: bugdemo.tgz > > > When a parent defines an object list in a plugin configuration, and then a > child of that parent also defines an object list for the same plugin leaving > some values undefined (so as to use defaults), the object list is loaded into > the plugin in an unpredictable manner, sometimes using parent-defined > properties instead of defaults, and sometimes not. > The attached plugin/parent/child projects produce this incorrect output: > $ mvn inherit_bug_demo:bugdemo > ... > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Parent Object 1 Property 1', prop2='Child Object 2 Property 2']]'] > The expected output would either be: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Parent Object 1 Property 2'], > [DemoObject: prop1='Parent Object 1 Property 1', prop2='Child Object 2 > Property 2'], [DemoObject: prop1='Parent Object 3 Property 1', prop2='Parent > Object 3 Property 2]]'] > Or: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Property 1', prop2='Child Object 2 Property 2']]'] > See attached build log, demonstration plugin, and parent/child project for > details. > Usage: > $ cd inherit_bug_demo > $ mvn deploy > $ cd ../child > $ mvn inherit_bug_demo:bugdemo -- 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] Issue Comment Edited: (MNG-4819) Inheritance Error in Object List Configuration for Custom Plugin
[ http://jira.codehaus.org/browse/MNG-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235632#action_235632 ] Jonathan Pearson edited comment on MNG-4819 at 9/17/10 9:33 AM: I'm sorry, I made a mistake in my expected output; the first block should be: [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: prop1='Child Object 1 Property 1', prop2='Parent Object 1 Property 2'], [DemoObject: prop1='Parent Object 2 Property 1', prop2='Child Object 2 Property 2'], [DemoObject: prop1='Parent Object 3 Property 1', prop2='Parent Object 3 Property 2]]'] The second DemoObject, first property was listed with incorrect "Parent Object 1...", should have been "Parent Object 2..." was (Author: celloman): I'm sorry, I made a mistake in my expected output: The expected output would either be: [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: prop1='Child Object 1 Property 1', prop2='Parent Object 1 Property 2'], [DemoObject: prop1='Parent Object 2 Property 1', prop2='Child Object 2 Property 2'], [DemoObject: prop1='Parent Object 3 Property 1', prop2='Parent Object 3 Property 2]]'] The second DemoObject, first property was listed with incorrect "Parent Object 1...", should have been "Parent Object 2..." > Inheritance Error in Object List Configuration for Custom Plugin > > > Key: MNG-4819 > URL: http://jira.codehaus.org/browse/MNG-4819 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 2.2.1 > Environment: Windows XP SP3, running under Cygwin bash shell >Reporter: Jonathan Pearson > Attachments: bugdemo.tgz > > > When a parent defines an object list in a plugin configuration, and then a > child of that parent also defines an object list for the same plugin leaving > some values undefined (so as to use defaults), the object list is loaded into > the plugin in an unpredictable manner, sometimes using parent-defined > properties instead of defaults, and sometimes not. > The attached plugin/parent/child projects produce this incorrect output: > $ mvn inherit_bug_demo:bugdemo > ... > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Parent Object 1 Property 1', prop2='Child Object 2 Property 2']]'] > The expected output would either be: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Parent Object 1 Property 2'], > [DemoObject: prop1='Parent Object 1 Property 1', prop2='Child Object 2 > Property 2'], [DemoObject: prop1='Parent Object 3 Property 1', prop2='Parent > Object 3 Property 2]]'] > Or: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Property 1', prop2='Child Object 2 Property 2']]'] > See attached build log, demonstration plugin, and parent/child project for > details. > Usage: > $ cd inherit_bug_demo > $ mvn deploy > $ cd ../child > $ mvn inherit_bug_demo:bugdemo -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-4819) Inheritance Error in Object List Configuration for Custom Plugin
[ http://jira.codehaus.org/browse/MNG-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Pearson updated MNG-4819: -- Attachment: build.log Also included in bugdemo.tgz, but this may be more convenient. > Inheritance Error in Object List Configuration for Custom Plugin > > > Key: MNG-4819 > URL: http://jira.codehaus.org/browse/MNG-4819 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 2.2.1 > Environment: Windows XP SP3, running under Cygwin bash shell >Reporter: Jonathan Pearson > Attachments: bugdemo.tgz, build.log > > > When a parent defines an object list in a plugin configuration, and then a > child of that parent also defines an object list for the same plugin leaving > some values undefined (so as to use defaults), the object list is loaded into > the plugin in an unpredictable manner, sometimes using parent-defined > properties instead of defaults, and sometimes not. > The attached plugin/parent/child projects produce this incorrect output: > $ mvn inherit_bug_demo:bugdemo > ... > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Parent Object 1 Property 1', prop2='Child Object 2 Property 2']]'] > The expected output would either be: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Parent Object 1 Property 2'], > [DemoObject: prop1='Parent Object 1 Property 1', prop2='Child Object 2 > Property 2'], [DemoObject: prop1='Parent Object 3 Property 1', prop2='Parent > Object 3 Property 2]]'] > Or: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Property 1', prop2='Child Object 2 Property 2']]'] > See attached build log, demonstration plugin, and parent/child project for > details. > Usage: > $ cd inherit_bug_demo > $ mvn deploy > $ cd ../child > $ mvn inherit_bug_demo:bugdemo -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4819) Inheritance Error in Object List Configuration for Custom Plugin
[ http://jira.codehaus.org/browse/MNG-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235638#action_235638 ] Jonathan Pearson commented on MNG-4819: --- I recommend going with the second of the two output choices (if the child supplies settings for the list, they override the entire parent list and not just those properties that are specified explicitly by the child). > Inheritance Error in Object List Configuration for Custom Plugin > > > Key: MNG-4819 > URL: http://jira.codehaus.org/browse/MNG-4819 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 2.2.1 > Environment: Windows XP SP3, running under Cygwin bash shell >Reporter: Jonathan Pearson > Attachments: bugdemo.tgz, build.log > > > When a parent defines an object list in a plugin configuration, and then a > child of that parent also defines an object list for the same plugin leaving > some values undefined (so as to use defaults), the object list is loaded into > the plugin in an unpredictable manner, sometimes using parent-defined > properties instead of defaults, and sometimes not. > The attached plugin/parent/child projects produce this incorrect output: > $ mvn inherit_bug_demo:bugdemo > ... > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Parent Object 1 Property 1', prop2='Child Object 2 Property 2']]'] > The expected output would either be: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Parent Object 1 Property 2'], > [DemoObject: prop1='Parent Object 1 Property 1', prop2='Child Object 2 > Property 2'], [DemoObject: prop1='Parent Object 3 Property 1', prop2='Parent > Object 3 Property 2]]'] > Or: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Property 1', prop2='Child Object 2 Property 2']]'] > See attached build log, demonstration plugin, and parent/child project for > details. > Usage: > $ cd inherit_bug_demo > $ mvn deploy > $ cd ../child > $ mvn inherit_bug_demo:bugdemo -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4820) Releasing a renamed pom file using the -f option does release to wrong pom file
Releasing a renamed pom file using the -f option does release to wrong pom file Key: MNG-4820 URL: http://jira.codehaus.org/browse/MNG-4820 Project: Maven 2 & 3 Issue Type: Bug Affects Versions: 3.0-beta-3 Environment: Release is 3.0-RC1, Linux Ubuntu 32 Reporter: Ulli Hafner Attachments: bundle-pom.xml, maven.log, pom.xml I have a directory containing 2 pom files that are used as our parent pom's: de.faktorlogik.pom/ - pom.xml - bundle-pom.xml When I go into this folder and release the 'pom.xml' file using 'mvn release:prepare', and 'mvn release:perform' then everything is ok. However, when I try to release the 'bundle-pom.xml' then the 'mvn -f bundle-pom.xml release:prepare' process works, but the 'mvn f bundle-pom.xml release:perform' process releases the snapshot version of 'pom.xml' rather than the new version of the bundle-pom.xml file. Seems that the -f parameter is ignored in the latter case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIA-397) Cannot link to javadoc methods
[
http://jira.codehaus.org/browse/DOXIA-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thom Nichols updated DOXIA-397:
---
Attachment: apt-link-fix.diff
I've fixed this myself, the patch is trivial and I don't believe it breaks
backwards compatibility. Please try it out and let me know if it causes any
problems with existing apt sources.
> Cannot link to javadoc methods
> --
>
> Key: DOXIA-397
> URL: http://jira.codehaus.org/browse/DOXIA-397
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core, Module - Apt, Module - Xdoc
>Affects Versions: 1.1.3
>Reporter: Lukas Theussl
> Attachments: apt-link-fix.diff
>
>
> Using a link to a javadoc method like
> {noformat}
> {{{../apidocs/groovyx/net/http/ParserRegistry.html#parseText(org.apache.http.HttpResponse)}ParserRegistry}}
> {noformat}
> the apt parser removes the brackets of the anchor. The same thing happens
> with xdocs and probably other formats. Note that non-ascii characters are not
> legal in anchor names, but they should be replaced by their hex values, see
> http://www.w3.org/TR/html401/appendix/notes.html#non-ascii-chars.
--
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: (MSITE-504) Maven site fails to run due to non-report goals
Maven site fails to run due to non-report goals
---
Key: MSITE-504
URL: http://jira.codehaus.org/browse/MSITE-504
Project: Maven 2.x Site Plugin
Issue Type: Bug
Affects Versions: 3.0-beta-2
Reporter: Marvin Froeder
An user just reported me a curious bug when using flexmojos and maven 3
{quote}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-cli) on
project calculator-api: failed to get Reports: The parameters 'filesToTrust'
for goal org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-SNAPSHOT:trust are
missing or invalid -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-cli) on
project calculator-api: failed to get Reports
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:88)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:80)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:87)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: failed to get
Reports
at
org.apache.maven.plugins.site.DefaultMavenReportExecutor.buildMavenReports(DefaultMavenReportExecutor.java:264)
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getReports(AbstractSiteRenderingMojo.java:208)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:105)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
... 19 more
Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
'filesToTrust' for goal
org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-SNAPSHOT:trust are missing or
invalid
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:514)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:467)
at
org.apache.maven.plugins.site.DefaultMavenReportExecutor.getConfiguredMavenReport(DefaultMavenReportExecutor.java:294)
at
org.apache.maven.plugins.site.DefaultMavenReportExecutor.buildMavenReports(DefaultMavenReportExecutor.java:234)
... 23 more
{quote}
This goal 'trust' is NOT a Maven report and this user never invokes it, but
seems maven-site creeps out with this goal, seems maven is trying to configure
it and fail because 'filesToTrust' is required but not configured.
Since the goal is neither used nor a maven-report it shouldn't affect
maven-site at all.
I will create an IT for this in a few minutes
--
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: (MRELEASE-597) Releasing a renamed pom file using the -f option does release to wrong pom file
[ http://jira.codehaus.org/browse/MRELEASE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MRELEASE-597. -- Resolution: Duplicate Assignee: Benjamin Bentmann > Releasing a renamed pom file using the -f option does release to wrong pom > file > > > Key: MRELEASE-597 > URL: http://jira.codehaus.org/browse/MRELEASE-597 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: Release is 3.0-RC1, Linux Ubuntu 32 >Reporter: Ulli Hafner >Assignee: Benjamin Bentmann > Attachments: bundle-pom.xml, maven.log, pom.xml > > > I have a directory containing 2 pom files that are used as our parent pom's: > de.faktorlogik.pom/ > - pom.xml > - bundle-pom.xml > When I go into this folder and release the 'pom.xml' file using 'mvn > release:prepare', and 'mvn release:perform' then everything is ok. However, > when I try to release the 'bundle-pom.xml' then the 'mvn -f bundle-pom.xml > release:prepare' process works, but the 'mvn f bundle-pom.xml > release:perform' process releases the snapshot version of 'pom.xml' rather > than the new version of the bundle-pom.xml file. Seems that the -f parameter > is ignored in the latter case. -- 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] Moved: (MRELEASE-597) Releasing a renamed pom file using the -f option does release to wrong pom file
[ http://jira.codehaus.org/browse/MRELEASE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-4820 to MRELEASE-597: - Complexity: (was: Intermediate) Affects Version/s: (was: 3.0-beta-3) 2.0 Key: MRELEASE-597 (was: MNG-4820) Project: Maven 2.x Release Plugin (was: Maven 2 & 3) > Releasing a renamed pom file using the -f option does release to wrong pom > file > > > Key: MRELEASE-597 > URL: http://jira.codehaus.org/browse/MRELEASE-597 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: Release is 3.0-RC1, Linux Ubuntu 32 >Reporter: Ulli Hafner > Attachments: bundle-pom.xml, maven.log, pom.xml > > > I have a directory containing 2 pom files that are used as our parent pom's: > de.faktorlogik.pom/ > - pom.xml > - bundle-pom.xml > When I go into this folder and release the 'pom.xml' file using 'mvn > release:prepare', and 'mvn release:perform' then everything is ok. However, > when I try to release the 'bundle-pom.xml' then the 'mvn -f bundle-pom.xml > release:prepare' process works, but the 'mvn f bundle-pom.xml > release:perform' process releases the snapshot version of 'pom.xml' rather > than the new version of the bundle-pom.xml file. Seems that the -f parameter > is ignored in the latter case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-568) Release plugin (in perform phase) ignore -f directive (non-default pom.xml file)
[ http://jira.codehaus.org/browse/MRELEASE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MRELEASE-568: --- Affects Version/s: 2.0 > Release plugin (in perform phase) ignore -f directive (non-default pom.xml > file) > > > Key: MRELEASE-568 > URL: http://jira.codehaus.org/browse/MRELEASE-568 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Paul Hammant > > mvn -f alternate-pom.xml release:perform > [ time passes ] > [INFO] Working directory: /scm/oss/atinject/target > [INFO] Executing goals 'deploy'... > [INFO] Executing: /bin/sh -c cd /scm/oss/atinject/target/checkout && > /Installed/apache-maven-2.2.1/bin/mvn deploy --no-plugin-updates > -DperformRelease=true -f pom.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4798) NullPointerException at NearestVersionConflictResolver.selectVersion()
[
http://jira.codehaus.org/browse/MNG-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235643#action_235643
]
Igor Fedorenko commented on MNG-4798:
-
Couple more stack traces from IBM JDK
i...@desktop:/code/sonatype-aether$ $JAVA_HOME/bin/java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pxa6460sr8fp1-20100624_01(SR8 FP1))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64
jvmxa6460sr8ifx-20100609_59383 (JIT enabled, AOT enabled)
J9VM - 20100609_059383
JIT - r9_20100401_15339ifx2
GC - 20100308_AA)
JCL - 20100624_01
Building current maven 3.0 trunk with 3.0-RC1
{noformat}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1.436s
[INFO] Finished at: Fri Sep 17 11:18:49 EDT 2010
[INFO] Final Memory: 7M/20M
[INFO]
[ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
java.lang.NullPointerException
at
org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.NullPointerException
at
org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.resolve(JavaEffectiveScopeCalculator.java:134)
at
org.sonatype.aether.util.graph.transformer.JavaEffectiveScopeCalculator.transformGraph(JavaEffectiveScopeCalculator.java:80)
at
org.sonatype.aether.util.graph.transformer.ChainedDependencyGraphTransformer.transformGraph(ChainedDependencyGraphTransformer.java:76)
at
org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:246)
at
org.sonatype.aether.impl.internal.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:265)
at
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:165)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:104)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:244)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:187)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
... 16 more
{noformat}
building aether with 3.0-RC1
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-install-plugin:2.2:install (default-install) on
project aether-parent: Execution default-install of goal
org.apache.maven.plugins:maven-install-plugin:2.2:install failed: Unable to
load the mojo 'install' in the plugin
'org.apache.maven.plugins:maven-install-plugin:2.2'. A required class is
missing: org.codehaus.plexus.digest.Digester
-
realm =plugin>org.apache.maven.plugins:mav
[jira] Commented: (MCHECKSTYLE-135) Can't use a configFile with an URL
[
http://jira.codehaus.org/browse/MCHECKSTYLE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235647#action_235647
]
Rick Mangi commented on MCHECKSTYLE-135:
Thanks! Look forward to 2.6
> Can't use a configFile with an URL
> --
>
> Key: MCHECKSTYLE-135
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-135
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Dominique Jean-Prost
>Assignee: Olivier Lamy
> Fix For: 2.6
>
> Attachments: log.txt
>
>
> If I specify a config file with an url, this file can't be downloaded anymore.
> I double checked that this file is reachable by http.
> After searching a bit, I guess the problem comes from
> org.codehaus.plexus.resource.loader.URLResourceLoader.getResource(String) in
> the following lines :
> for ( Iterator i = paths.iterator(); i.hasNext(); ) { <-- paths is empty there
> }
--
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-504) Maven site fails to run due to non-report goals
[
http://jira.codehaus.org/browse/MSITE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235649#action_235649
]
Marvin Froeder commented on MSITE-504:
--
Test case for the problem:
{code}
Index: pom.xml
===
--- pom.xml (revision 998149)
+++ pom.xml (working copy)
@@ -145,6 +145,13 @@
Lithuanian translator
+
+ Marvin Froeder
+ velo...@gmail.com
+
+msite-504
+
+
Index: src/it/MSITE-504/maven-plugin/pom.xml
===
--- src/it/MSITE-504/maven-plugin/pom.xml (revision 0)
+++ src/it/MSITE-504/maven-plugin/pom.xml (revision 0)
@@ -0,0 +1,23 @@
+
+http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
+ 4.0.0
+
+
+msite-504
+parent
+1.0
+../pom.xml
+
+
+ maven-plugin
+
+ maven-plugin
+
+
+
+ org.apache.maven
+ maven-plugin-api
+ 3.0-beta-3
+
+
+
\ No newline at end of file
Property changes on: src\it\MSITE-504\maven-plugin\pom.xml
___
Added: svn:mime-type
+ text/plain
Index:
src/it/MSITE-504/maven-plugin/src/main/java/msite504/mavenplugin/MyMojo.java
===
---
src/it/MSITE-504/maven-plugin/src/main/java/msite504/mavenplugin/MyMojo.java
(revision 0)
+++
src/it/MSITE-504/maven-plugin/src/main/java/msite504/mavenplugin/MyMojo.java
(revision 0)
@@ -0,0 +1,48 @@
+package msite504.mavenplugin;
+
+/*
+ * Copyright 2001-2005 The Apache Software Foundation.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+import org.apache.maven.plugin.AbstractMojo;
+import org.apache.maven.plugin.MojoExecutionException;
+
+import java.io.File;
+import java.io.FileWriter;
+import java.io.IOException;
+
+/**
+ * Goal which touches a timestamp file.
+ *
+ * @goal touch
+ * @phase process-sources
+ */
+public class MyMojo
+extends AbstractMojo
+{
+/**
+ * Location of the file.
+ *
+ * @parameter
+ * @required
+ */
+private File outputDirectory;
+
+public void execute()
+throws MojoExecutionException
+{
+// do nothing
+}
+}
Property changes on:
src\it\MSITE-504\maven-plugin\src\main\java\msite504\mavenplugin\MyMojo.java
___
Added: svn:mime-type
+ text/plain
Index: src/it/MSITE-504/pom.xml
===
--- src/it/MSITE-504/pom.xml(revision 0)
+++ src/it/MSITE-504/pom.xml(revision 0)
@@ -0,0 +1,35 @@
+
+http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
+ 4.0.0
+ msite-504
+ parent
+ 1.0
+ pom
+
+
+maven-plugin
+maven-plugin-consumer
+
+
+
+3.0
+
+
+
+
+
+
+ org.apache.maven.plugins
+ maven-site-plugin
+ @project.version@
+
+
+ org.apache.maven.plugins
+ maven-project-info-reports-plugin
+ @projectInfoReportsPluginVersion@
+
+
+
+
+
+
\ No newline at end of file
Property changes on: src\it\MSITE-504\pom.xml
___
Added: svn:mime-type
+ text/plain
Index: src/it/MSITE-504/maven-plugin-consumer/pom.xml
===
--- src/it/MSITE-504/maven-plugin-consumer/pom.xml (revision 0)
+++ src/it/MSITE-504/maven-plugin-consumer/pom.xml (revision 0)
@@ -0,0 +1,24 @@
+
+http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
+ 4.0.0
+
+
+msite-504
+parent
+1.0
+../pom.xml
+
+
+ maven-plugin-consumer
+
+
+
+
+msite-504
+maven-plugin
+1.0
+
+
+
+
+
\ No newline at end of file
Property changes on: src\it\MSITE-504\maven
[jira] Commented: (ARCHETYPE-326) fail on mvn install with a archetype created from create-from-project command
[
http://jira.codehaus.org/browse/ARCHETYPE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235651#action_235651
]
Kyle Kirkland commented on ARCHETYPE-326:
-
Just to provide additional confirmation of this issue, I'm experiencing the
exact same thing with 2.0-alpha-6-SNAPSHOT.
> fail on mvn install with a archetype created from create-from-project command
> -
>
> Key: ARCHETYPE-326
> URL: http://jira.codehaus.org/browse/ARCHETYPE-326
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
>Affects Versions: 2.0-alpha-5
> Environment: Archetype plugin 2.0-alpha-6,
> OS name: "windows 2003" version: "5.2" arch: "x86" Family: "windows" , maven
> 2.2.1 (r801777; 2009-08-06 21:16:01+0200) , jdk 1.6.0_20
>Reporter: eric worth
> Fix For: 2.0
>
>
> Creatin archetype form my projects was working 2 days ago, now it is broken ^^
> Try to create a project "foo" with "mvn archetype:generate",
> choose 16 for exemple, and follow documentation steps :
> - "mvn archetype:create-from-project"
> - cd target/generated-sources/archetype/
> - mvn install
> stack trace :
> {noformat}
> [INFO] [archetype:integration-test {execution: default-integration-test}]
> F:\dev\tmp\test\foo\target\generated-sources\archetype\target\test-classes\projects\basic\archetype.properties
> [ERROR] Archetype fr.mycompany.foo:foo-archetype:1.0-SNAPSHOT is not
> configured
> Property archetype.goals is missing.
> org.apache.maven.archetype.exception.ArchetypeNotConfigured: Archetype
> fr.mycompany.foo:foo-archetype:1.0-SNAPSHOT is not configured
> Property archetype.goals is missing.
> at
> org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:127)
> at
> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:136)
> at
> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:106)
> at
> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149)
> at
> org.apache.maven.archetype.mojos.IntegrationTestMojo.processIntegrationTest(IntegrationTestMojo.java:215)
> at
> org.apache.maven.archetype.mojos.IntegrationTestMojo.execute(IntegrationTestMojo.java:92)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> 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)
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Test basic failed
> [Ljava.lang.StackTraceElement;@864e43
> org.apache.maven.archetype.exception.ArchetypeNotConfigured: Archetype
> fr.mycompany.foo:foo-archetype:1.0-SNAPSHOT is not configured
> Property archetype.goals is missing.{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the admini
[jira] Commented: (MSITE-504) Maven site fails to run due to non-report goals
[
http://jira.codehaus.org/browse/MSITE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235656#action_235656
]
Marvin Froeder commented on MSITE-504:
--
I came up with a quick dirty patch, not sure if that is the best way to deal
with the problem but it did solve my problems here.
{code}
Index:
src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java
===
--- src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java
(revision 998149)
+++ src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java
(working copy)
@@ -48,8 +48,10 @@
import org.apache.maven.project.MavenProject;
import org.apache.maven.reporting.MavenReport;
import org.codehaus.classworlds.ClassRealm;
+import org.codehaus.plexus.PlexusContainer;
import org.codehaus.plexus.component.annotations.Component;
import org.codehaus.plexus.component.annotations.Requirement;
+import
org.codehaus.plexus.component.repository.exception.ComponentLookupException;
import org.codehaus.plexus.configuration.PlexusConfiguration;
import org.codehaus.plexus.logging.Logger;
import org.codehaus.plexus.util.StringUtils;
@@ -103,6 +105,9 @@
implements MavenReportExecutor
{
@Requirement
+private PlexusContainer container;
+
+@Requirement
private Logger logger;
@Requirement
@@ -291,6 +296,37 @@
{
try
{
+Mojo unconfiguredMojo;
+
+org.codehaus.plexus.classworlds.realm.ClassRealm pluginRealm =
pluginDescriptor.getClassRealm();
+org.codehaus.plexus.classworlds.realm.ClassRealm oldLookupRealm =
container.setLookupRealm( pluginRealm );
+
+ClassLoader oldClassLoader =
Thread.currentThread().getContextClassLoader();
+
+try
+{
+container.setLookupRealm( pluginRealm );
+Thread.currentThread().setContextClassLoader( pluginRealm );
+unconfiguredMojo = container.lookup( Mojo.class,
mojoExecution.getMojoDescriptor().getRoleHint() );
+}
+catch ( ComponentLookupException e )
+{
+throw new PluginContainerException(
mojoExecution.getMojoDescriptor(), pluginRealm,
+"Unable to load the mojo '"
++
mojoExecution.getMojoDescriptor().getGoal()
++ "' (or one of its
required components) from the plugin '"
++
pluginDescriptor.getId() + "'", e );
+}
+finally
+{
+container.setLookupRealm( oldLookupRealm );
+Thread.currentThread().setContextClassLoader( oldClassLoader );
+}
+
+if(!MavenReport.class.isAssignableFrom(
unconfiguredMojo.getClass() )) {
+return null;
+}
+
Mojo mojo = mavenPluginManager.getConfiguredMojo( Mojo.class,
mavenReportExecutorRequest.getMavenSession(),
mojoExecution );
{code}
> Maven site fails to run due to non-report goals
> ---
>
> Key: MSITE-504
> URL: http://jira.codehaus.org/browse/MSITE-504
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 3.0-beta-2
>Reporter: Marvin Froeder
>Assignee: Olivier Lamy
>
> An user just reported me a curious bug when using flexmojos and maven 3
> {quote}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-cli) on
> project calculator-api: failed to get Reports: The parameters 'filesToTrust'
> for goal org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-SNAPSHOT:trust are
> missing or invalid -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-cli)
> on project calculator-api: failed to get Reports
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:88)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:80)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:87)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThr
[jira] Created: (MNG-4821) Wrong spring-context version resolved when depending on artifact with dependency management and jersey-spring dependency
Wrong spring-context version resolved when depending on artifact with dependency management and jersey-spring dependency Key: MNG-4821 URL: http://jira.codehaus.org/browse/MNG-4821 Project: Maven 2 & 3 Issue Type: Bug Components: Dependencies Affects Versions: 2.2.1 Environment: Ubuntu 10.04 64-bit, jdk6 Windows 7 64-bit, Cygwin, jdk6 Windows XP SP3 32-bit, Cygwin, jdk5 Reporter: Ryan Stewart Attachments: dependency-versions.zip Given two artifacts, A and B: - A depends on B and on org.springframework:spring-context:3.0.1.RELEASE - B depends on com.sun.jersey.contribs:jersey-spring:1.2 and has a dependency management entry that sets the version for org.springframework:spring-context to 3.0.2.RELEASE - com.sun.jersey.contribs:jersey-spring:1.2 depends on org.springframework:spring-context:[2.5.2,3) When B is built, maven uses org.springframework:spring-context:jar:3.0.2.RELEASE, as expected. When A is built, maven 2 uses org.springframework:spring-context:jar:2.5.6, and maven 3 uses version 2.5.6.SEC02. I'm attaching a sample project that demonstrates the bug. There are two poms: dependent and dependee. These correspond to A and B above, respectively. The top-level pom just includes the other two for ease of building. In the real-life situation where I found the problem, the two artifacts are from separate projects. There is no unit test, since I don't even know how I'd write a test for this, but there is a bash script called test.sh that checks for the problem. -- 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: (MEV-671) ftpserver-parent 1.0.4 has an 'r' character after closing groupId and before opening artifactId tag
ftpserver-parent 1.0.4 has an 'r' character after closing groupId and before opening artifactId tag --- Key: MEV-671 URL: http://jira.codehaus.org/browse/MEV-671 Project: Maven Evangelism Issue Type: Bug Components: Invalid POM Reporter: Stevo Slavic See related issues [FTPSERVER-388|https://issues.apache.org/jira/browse/FTPSERVER-388] and [FTPSERVER-356|https://issues.apache.org/jira/browse/FTPSERVER-356], where latter has fixed pom file attached. -- 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: (MNG-4819) Inheritance Error in Object List Configuration for Custom Plugin
[
http://jira.codehaus.org/browse/MNG-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4819.
--
Resolution: Duplicate
Assignee: Benjamin Bentmann
Thanks for the example project!
The default behavior is merging at any depth such that the effective plugin
configuration in the child now looks like:
{code:xml}
Child Object 1 Property 1
Parent Object 1 Property 2
Child Object 2 Property 2
Parent Object 2 Property 1
{code}
i.e. the parent objects get merged to the proper locations in the child list.
To achieve the result that you mention in your last comment, the child POM
needs to be changed like this:
{code:xml}
Child Object 1 Property 1
Child Object 2 Property 2
{code}
i.e. the attribute {{combine.self="override"}} disables merging of parent
values for that node.
> Inheritance Error in Object List Configuration for Custom Plugin
>
>
> Key: MNG-4819
> URL: http://jira.codehaus.org/browse/MNG-4819
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 2.2.1
> Environment: Windows XP SP3, running under Cygwin bash shell
>Reporter: Jonathan Pearson
>Assignee: Benjamin Bentmann
> Attachments: bugdemo.tgz, build.log
>
>
> When a parent defines an object list in a plugin configuration, and then a
> child of that parent also defines an object list for the same plugin leaving
> some values undefined (so as to use defaults), the object list is loaded into
> the plugin in an unpredictable manner, sometimes using parent-defined
> properties instead of defaults, and sometimes not.
> The attached plugin/parent/child projects produce this incorrect output:
> $ mvn inherit_bug_demo:bugdemo
> ...
> [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject:
> prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject:
> prop1='Parent Object 1 Property 1', prop2='Child Object 2 Property 2']]']
> The expected output would either be:
> [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject:
> prop1='Child Object 1 Property 1', prop2='Parent Object 1 Property 2'],
> [DemoObject: prop1='Parent Object 1 Property 1', prop2='Child Object 2
> Property 2'], [DemoObject: prop1='Parent Object 3 Property 1', prop2='Parent
> Object 3 Property 2]]']
> Or:
> [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject:
> prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject:
> prop1='Property 1', prop2='Child Object 2 Property 2']]']
> See attached build log, demonstration plugin, and parent/child project for
> details.
> Usage:
> $ cd inherit_bug_demo
> $ mvn deploy
> $ cd ../child
> $ mvn inherit_bug_demo:bugdemo
--
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-504) Maven site fails to run due to non-report goals
[
http://jira.codehaus.org/browse/MSITE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235664#action_235664
]
Dennis Lundberg commented on MSITE-504:
---
If your custom plugin is not a report, why do you configure it in the
section of the POM? That section is for reporting plugins.
> Maven site fails to run due to non-report goals
> ---
>
> Key: MSITE-504
> URL: http://jira.codehaus.org/browse/MSITE-504
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 3.0-beta-2
>Reporter: Marvin Froeder
>Assignee: Olivier Lamy
>
> An user just reported me a curious bug when using flexmojos and maven 3
> {quote}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-cli) on
> project calculator-api: failed to get Reports: The parameters 'filesToTrust'
> for goal org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-SNAPSHOT:trust are
> missing or invalid -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-cli)
> on project calculator-api: failed to get Reports
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:88)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:80)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:87)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: failed to get
> Reports
> at
> org.apache.maven.plugins.site.DefaultMavenReportExecutor.buildMavenReports(DefaultMavenReportExecutor.java:264)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getReports(AbstractSiteRenderingMojo.java:208)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:105)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> ... 19 more
> Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
> 'filesToTrust' for goal
> org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-SNAPSHOT:trust are missing
> or invalid
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:514)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:467)
> at
> org.apache.maven.plugins.site.DefaultMavenReportExecutor.getConfiguredMavenReport(DefaultMavenReportExecutor.java:294)
> at
> org.apache.maven.plugins.site.DefaultMavenReportExecutor.buildMavenReports(DefaultMavenReportExecutor.java:234)
> ... 23 more
> {quote}
> This goal 'trust' is NOT a Maven report and this user never invokes it, but
> seems maven-site creeps out with this goal, seems maven is trying to
> configure it and fail because 'filesToTrust' is required but not configured.
> Since the goal is neither used nor a maven-report it shouldn't affect
> maven-site at all.
> I will create an IT for this in a few minutes
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4819) Inheritance Error in Object List Configuration for Custom Plugin
[ http://jira.codehaus.org/browse/MNG-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235665#action_235665 ] Jonathan Pearson commented on MNG-4819: --- Can that combine.self="override" attribute be used further up the tree? In that example, could it be used on the "objects" element instead of on each individual "demoObject"? > Inheritance Error in Object List Configuration for Custom Plugin > > > Key: MNG-4819 > URL: http://jira.codehaus.org/browse/MNG-4819 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 2.2.1 > Environment: Windows XP SP3, running under Cygwin bash shell >Reporter: Jonathan Pearson >Assignee: Benjamin Bentmann > Attachments: bugdemo.tgz, build.log > > > When a parent defines an object list in a plugin configuration, and then a > child of that parent also defines an object list for the same plugin leaving > some values undefined (so as to use defaults), the object list is loaded into > the plugin in an unpredictable manner, sometimes using parent-defined > properties instead of defaults, and sometimes not. > The attached plugin/parent/child projects produce this incorrect output: > $ mvn inherit_bug_demo:bugdemo > ... > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Parent Object 1 Property 1', prop2='Child Object 2 Property 2']]'] > The expected output would either be: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Parent Object 1 Property 2'], > [DemoObject: prop1='Parent Object 1 Property 1', prop2='Child Object 2 > Property 2'], [DemoObject: prop1='Parent Object 3 Property 1', prop2='Parent > Object 3 Property 2]]'] > Or: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Property 1', prop2='Child Object 2 Property 2']]'] > See attached build log, demonstration plugin, and parent/child project for > details. > Usage: > $ cd inherit_bug_demo > $ mvn deploy > $ cd ../child > $ mvn inherit_bug_demo:bugdemo -- 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] Issue Comment Edited: (MSITE-504) Maven site fails to run due to non-report goals
[
http://jira.codehaus.org/browse/MSITE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235656#action_235656
]
Marvin Froeder edited comment on MSITE-504 at 9/17/10 3:03 PM:
---
I came up with a quick dirty patch, not sure if that is the best way to deal
with the problem but it did solve my problems here.
{code}
Index:
src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java
===
--- src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java
(revision 998149)
+++ src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java
(working copy)
@@ -291,15 +291,15 @@
{
try
{
-Mojo mojo = mavenPluginManager.getConfiguredMojo( Mojo.class,
-
mavenReportExecutorRequest.getMavenSession(),
- mojoExecution );
-
-if ( !isMavenReport( mojoExecution, pluginDescriptor, mojo ) )
+if ( !isMavenReport( mojoExecution, pluginDescriptor ) )
{
return null;
}
+Mojo mojo = mavenPluginManager.getConfiguredMojo( Mojo.class,
+
mavenReportExecutorRequest.getMavenSession(),
+ mojoExecution );
+
return (MavenReport) mojo;
}
catch ( ClassCastException e )
@@ -328,15 +328,25 @@
}
}
-private boolean isMavenReport( MojoExecution mojoExecution,
PluginDescriptor pluginDescriptor, Mojo mojo )
+private boolean isMavenReport( MojoExecution mojoExecution,
PluginDescriptor pluginDescriptor )
{
-ClassLoader originalClassLoader =
Thread.currentThread().getContextClassLoader();
+Class mojoClass;
+try
+{
+mojoClass =
+pluginDescriptor.getClassRealm().loadClass(
mojoExecution.getMojoDescriptor().getImplementation() );
+}
+catch ( ClassNotFoundException e )
+{
+// TODO needs to decide what to do here, throws another error?
silent ignore?
+mojoClass = null;
+}
+
try
{
MojoDescriptor mojoDescriptor = pluginDescriptor.getMojo(
mojoExecution.getGoal() );
-Thread.currentThread().setContextClassLoader(
mojoDescriptor.getRealm() );
-boolean isMavenReport = MavenReport.class.isAssignableFrom(
mojo.getClass() );
+boolean isMavenReport = MavenReport.class.isAssignableFrom(
mojoClass );
if ( getLog().isDebugEnabled() )
{
@@ -360,10 +370,6 @@
e );
return false;
}
-finally
-{
-Thread.currentThread().setContextClassLoader( originalClassLoader
);
-}
}
private Xpp3Dom convert( MojoDescriptor mojoDescriptor )
{code}
was (Author: velo):
I came up with a quick dirty patch, not sure if that is the best way to
deal with the problem but it did solve my problems here.
{code}
Index:
src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java
===
--- src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java
(revision 998149)
+++ src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java
(working copy)
@@ -48,8 +48,10 @@
import org.apache.maven.project.MavenProject;
import org.apache.maven.reporting.MavenReport;
import org.codehaus.classworlds.ClassRealm;
+import org.codehaus.plexus.PlexusContainer;
import org.codehaus.plexus.component.annotations.Component;
import org.codehaus.plexus.component.annotations.Requirement;
+import
org.codehaus.plexus.component.repository.exception.ComponentLookupException;
import org.codehaus.plexus.configuration.PlexusConfiguration;
import org.codehaus.plexus.logging.Logger;
import org.codehaus.plexus.util.StringUtils;
@@ -103,6 +105,9 @@
implements MavenReportExecutor
{
@Requirement
+private PlexusContainer container;
+
+@Requirement
private Logger logger;
@Requirement
@@ -291,6 +296,37 @@
{
try
{
+Mojo unconfiguredMojo;
+
+org.codehaus.plexus.classworlds.realm.ClassRealm pluginRealm =
pluginDescriptor.getClassRealm();
+org.codehaus.plexus.classworlds.realm.ClassRealm oldLookupRealm =
container.setLookupRealm( pluginRealm );
+
+ClassLoader oldClassLoader =
Thread.currentThread().getContextClassLoader();
+
+try
+{
+container.setLookupRealm( pluginRealm );
+Thread.currentThre
[jira] Commented: (MNG-4819) Inheritance Error in Object List Configuration for Custom Plugin
[ http://jira.codehaus.org/browse/MNG-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235666#action_235666 ] Benjamin Bentmann commented on MNG-4819: Yes, that attribute can in general be applied on any element within a plugin configuration block. > Inheritance Error in Object List Configuration for Custom Plugin > > > Key: MNG-4819 > URL: http://jira.codehaus.org/browse/MNG-4819 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 2.2.1 > Environment: Windows XP SP3, running under Cygwin bash shell >Reporter: Jonathan Pearson >Assignee: Benjamin Bentmann > Attachments: bugdemo.tgz, build.log > > > When a parent defines an object list in a plugin configuration, and then a > child of that parent also defines an object list for the same plugin leaving > some values undefined (so as to use defaults), the object list is loaded into > the plugin in an unpredictable manner, sometimes using parent-defined > properties instead of defaults, and sometimes not. > The attached plugin/parent/child projects produce this incorrect output: > $ mvn inherit_bug_demo:bugdemo > ... > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Parent Object 1 Property 1', prop2='Child Object 2 Property 2']]'] > The expected output would either be: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Parent Object 1 Property 2'], > [DemoObject: prop1='Parent Object 1 Property 1', prop2='Child Object 2 > Property 2'], [DemoObject: prop1='Parent Object 3 Property 1', prop2='Parent > Object 3 Property 2]]'] > Or: > [INFO] Configuration: [InheritanceBugDemoMojo: objects='[[DemoObject: > prop1='Child Object 1 Property 1', prop2='Property 2'], [DemoObject: > prop1='Property 1', prop2='Child Object 2 Property 2']]'] > See attached build log, demonstration plugin, and parent/child project for > details. > Usage: > $ cd inherit_bug_demo > $ mvn deploy > $ cd ../child > $ mvn inherit_bug_demo:bugdemo -- 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-504) Maven site fails to run due to non-report goals
[
http://jira.codehaus.org/browse/MSITE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235671#action_235671
]
Marvin Froeder commented on MSITE-504:
--
Hi Dennis,
Although my IT doesn't do that, the original plugin where the problem popup has
both report and non-report goals. And splitting they into 2 different plugins
is not an option since the report need to use the same configuration as other
goals use... and flexmojos has a LOT of configurations, so wouldn't be a nice
idea to duplicate it.
The IT I posted is just a oversimplified version of the problem I found.
> Maven site fails to run due to non-report goals
> ---
>
> Key: MSITE-504
> URL: http://jira.codehaus.org/browse/MSITE-504
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 3.0-beta-2
>Reporter: Marvin Froeder
>Assignee: Olivier Lamy
>
> An user just reported me a curious bug when using flexmojos and maven 3
> {quote}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-cli) on
> project calculator-api: failed to get Reports: The parameters 'filesToTrust'
> for goal org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-SNAPSHOT:trust are
> missing or invalid -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-cli)
> on project calculator-api: failed to get Reports
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:88)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:80)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:87)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: failed to get
> Reports
> at
> org.apache.maven.plugins.site.DefaultMavenReportExecutor.buildMavenReports(DefaultMavenReportExecutor.java:264)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getReports(AbstractSiteRenderingMojo.java:208)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:105)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> ... 19 more
> Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
> 'filesToTrust' for goal
> org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-SNAPSHOT:trust are missing
> or invalid
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:514)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:467)
> at
> org.apache.maven.plugins.site.DefaultMavenReportExecutor.getConfiguredMavenReport(DefaultMavenReportExecutor.java:294)
> at
> org.apache.maven.plugins.site.DefaultMavenReportExecutor.buildMavenReports(DefaultMavenReportExecutor.java:234)
> ... 23 more
> {quote}
> This goal 'trust' is NOT a Maven report and this user never invokes it, but
> seems maven-site creeps out with this goal, seems maven is trying to
> configure it and fail because 'filesToTrust' is required but not configured.
> Since the goal is neither used nor a maven-report it shouldn't affect
> maven-site at all.
> I will create an IT for this in a few minutes
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://j
[jira] Commented: (DOXIA-408) Test failures on Windows
[
http://jira.codehaus.org/browse/DOXIA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235673#action_235673
]
Dennis Lundberg commented on DOXIA-408:
---
The failures are in XmlWriterXdocSinkTest, not XdocSinkTest. See the attached
Surefire report.
The methods getListBlock(), getNumberedListBlock(), getDefinitionListBlock()
and getTableBlock() all have XmlUtil.DEFAULT_LINE_SEPARATOR in them, which is
what I think is the source of problem. These methods represent the expected
results and the actual results come from the sink that is created in
{code:java}
protected Sink createSink( Writer writer )
{
return new XmlWriterXdocSink( new PrettyPrintXMLWriter( writer ) );
}
{code}
The sink uses a pretty printer so I guess that it differs in that is deemed
pretty compared to the LINE_SEPARATORs used in the methods above.
It'd probably be best if we could stop pretty printing in the tests.
> Test failures on Windows
>
>
> Key: DOXIA-408
> URL: http://jira.codehaus.org/browse/DOXIA-408
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Xdoc
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.5.0_22
> Java home: C:\Program\Java\jdk1.5.0_22\jre
> Default locale: sv_SE, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Dennis Lundberg
> Attachments:
> org.apache.maven.doxia.module.xdoc.XmlWriterXdocSinkTest.txt
>
>
> mvn test in the xdoc module of the current trunk produces this output
> {noformat}
> ...
> Failed tests:
> testList(org.apache.maven.doxia.module.xdoc.XmlWriterXdocSinkTest)
> testNumberedList(org.apache.maven.doxia.module.xdoc.XmlWriterXdocSinkTest)
> testDefinitionList(org.apache.maven.doxia.module.xdoc.XmlWriterXdocSinkTest)
> testTable(org.apache.maven.doxia.module.xdoc.XmlWriterXdocSinkTest)
> Tests run: 117, Failures: 4, Errors: 0, Skipped: 0
> ...
> {noformat}
> The failures has to do with differences in line breaks for list, ordered
> list, definition list and table. See attached Surefire report.
> The actual results have one line break *less* than expected, which is odd
> considering that Windows usually get *more* line breaks. The errors might be
> due to differences between org.codehaus.plexus.util.xml.PrettyPrintXMLWriter
> and org.codehaus.plexus.util.xml.XmlUtil.prettyFormat().
--
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: (MSITE-504) Maven site fails to run due to non-report goals
[
http://jira.codehaus.org/browse/MSITE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MSITE-504.
--
Resolution: Fixed
Fix Version/s: 3.0-beta-3
fixed rev 998334
Thanks !
> Maven site fails to run due to non-report goals
> ---
>
> Key: MSITE-504
> URL: http://jira.codehaus.org/browse/MSITE-504
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 3.0-beta-2
>Reporter: Marvin Froeder
>Assignee: Olivier Lamy
> Fix For: 3.0-beta-3
>
>
> An user just reported me a curious bug when using flexmojos and maven 3
> {quote}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-cli) on
> project calculator-api: failed to get Reports: The parameters 'filesToTrust'
> for goal org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-SNAPSHOT:trust are
> missing or invalid -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-2:site (default-cli)
> on project calculator-api: failed to get Reports
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:88)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:80)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:87)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: failed to get
> Reports
> at
> org.apache.maven.plugins.site.DefaultMavenReportExecutor.buildMavenReports(DefaultMavenReportExecutor.java:264)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getReports(AbstractSiteRenderingMojo.java:208)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:105)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> ... 19 more
> Caused by: org.apache.maven.plugin.PluginParameterException: The parameters
> 'filesToTrust' for goal
> org.sonatype.flexmojos:flexmojos-maven-plugin:4.0-SNAPSHOT:trust are missing
> or invalid
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:514)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:467)
> at
> org.apache.maven.plugins.site.DefaultMavenReportExecutor.getConfiguredMavenReport(DefaultMavenReportExecutor.java:294)
> at
> org.apache.maven.plugins.site.DefaultMavenReportExecutor.buildMavenReports(DefaultMavenReportExecutor.java:234)
> ... 23 more
> {quote}
> This goal 'trust' is NOT a Maven report and this user never invokes it, but
> seems maven-site creeps out with this goal, seems maven is trying to
> configure it and fail because 'filesToTrust' is required but not configured.
> Since the goal is neither used nor a maven-report it shouldn't affect
> maven-site at all.
> I will create an IT for this in a few minutes
--
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: (MASSEMBLY-157) maven assembly plugin, includes/excludes in moduleSet
[
http://jira.codehaus.org/browse/MASSEMBLY-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MASSEMBLY-157.
Resolution: Fixed
Assignee: John Casey
I've verified that putting includes/excludes in the moduleSet section, rather
than in the embedded binaries section, works. See
src/it/projects/multimodule/multimodule-binariesNotSource for an example.
> maven assembly plugin, includes/excludes in moduleSet
> --
>
> Key: MASSEMBLY-157
> URL: http://jira.codehaus.org/browse/MASSEMBLY-157
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: Maven 2.0.4, JDK 6.0, assembly plugin
>Reporter: Lukasz Dywicki
>Assignee: John Casey
>Priority: Minor
> Fix For: 2.2-beta-6
>
>
> Hello everyone, I've some assembly descriptor with operations in modulesSet,
> but maven ignore my excludes/includes.
> I've got all modules in bin directory, all modules in modules ditectory and
> all modules in libs.
>
>
> package
> false
>
> zip
>
>
>
>
>
> modules/
> false
> false
>
>
> autoguard:autocontrol-core
>
>
>
>
>
>
> bin/
> false
> false
>
>
> autoguard:autocontrol-core
>
>
>
>
>
>
> libs/
> true
> false
>
>
> ${project.groupId}
>
>
>
>
>
>
>
> libs/
> false
> runtime
>
>
>
--
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: (MNG-4490) Inconsistent handling of POMs
[
http://jira.codehaus.org/browse/MNG-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4490.
--
Resolution: Fixed
Fix Version/s: 3.0-beta-3
Assignee: Benjamin Bentmann
Fixed by [r988749|http://svn.apache.org/viewvc?view=revision&revision=988749],
POMs are consequently treated as artifacts.
> Inconsistent handling of POMs
> -
>
> Key: MNG-4490
> URL: http://jira.codehaus.org/browse/MNG-4490
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.0-alpha-5
>Reporter: Tamás Cservenák
>Assignee: Benjamin Bentmann
> Fix For: 3.0-beta-3
>
>
> As we learned from discussion happened in issue MNG-4368, Maven3 -- depending
> on packaging ("pom" vs anything else) -- handles the POM installation in
> different ways.
> When packaging is "pom", the POM is _handled as artifact_, and MNG-4368 (and
> any other future "optimization") interferes with it's installation. When
> packaging is not "pom", the POM is _handled as repository metadata in Maven3
> internals.
> IMHO, the latter should be _always_ the case, regardless of the packaging
> type.
--
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: (MNG-4491) Maven3 reports warnings about POM problems in very spurious way
[
http://jira.codehaus.org/browse/MNG-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4491.
--
Resolution: Won't Fix
Assignee: Benjamin Bentmann
Invalid = existent but unusuable, for any more details the debug log can be
consulted.
> Maven3 reports warnings about POM problems in very spurious way
> ---
>
> Key: MNG-4491
> URL: http://jira.codehaus.org/browse/MNG-4491
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Errors
>Affects Versions: 3.0-alpha-5
>Reporter: Tamás Cservenák
>Assignee: Benjamin Bentmann
>
> In relation to issue MNG-4490, Maven3 reported the following on CLI:
> {noformat}
> [WARNING] Invalid artifact metadata for
> org.sonatype.nexus:nexus-proxy:jar:1.4.1-SNAPSHOT, transitive dependencies
> (if any) will not be available, enable debug logging for more details
> {noformat}
> This is due to the issue above (the branch i worked on completely revamped
> the dependencies in aggregator poms, hence the module pom became "invalid",
> since it contained dependencies that would be "filled in" from dependency
> management section, but they were not, hence by Maven3 they were considered
> "invalid").
> What I was thinking, that maybe we should distinguish between "corrupt" POMs
> in way like:
> * syntactical broken, which is like unparseable POM (usually corrupted during
> transport or proxy issues)
> * semantically broken -- this is what Maven3 tried to tell me -- a POM that
> was not "correct" in validation sense (in this case, depepndency had no
> "version" declared)
--
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: (MRELEASE-406) release:perform ignores environment variables
[
http://jira.codehaus.org/browse/MRELEASE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MRELEASE-406.
-
Resolution: Won't Fix
Assignee: Brett Porter
as you've identified, this was related to the documented Maven change.
You should use ${env.*} if you require an environment variable. However, you
might better consider using it as a property, in which case you'd set it with
MAVEN_OPTS="-DsomeProperty=someValue" instead of using an env. variable.
> release:perform ignores environment variables
> -
>
> Key: MRELEASE-406
> URL: http://jira.codehaus.org/browse/MRELEASE-406
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.0-beta-8
> Environment: WinXP Maven 2.0.9
>Reporter: James Nord
>Assignee: Brett Porter
>Priority: Blocker
> Attachments: mvn2.0.10.log, mvn2.0.10_debug.log, mvn2.1.0-RC3.log,
> pom.xml, settings.xml
>
>
> Our settings.xml is shared across many sites and we use reository mirrors at
> each of our sites.
> The mirrors are setup in the settings.xml as ${proxyURL}/repopath
> the users set an environment variable to point to the nexus cache at their
> paticular site -
> eg http://maven-proxy-east.mycorp.com/nexus/content/repositories
> This woks fine for normal working (compile, site deploy etc..) but
> release:perform fails as it tries to download from
> ${proxyURL}/central/org/apache/mave
> It would appear that environment variables are not passed to the forked
> process doing the release.
> -- settings.xml snippet --
>
> central-mirror
> Maven Central [nexus mirror]
> ${proxyURL}/central
> central
>
> -- end settings.xml snippet --
> output from release:perfrom
> D:\workspaces\TestProject>set | grep proxyURL
> proxyURL=http://maven-proxy-east.mycorp.com/nexus/content/repositories
> D:\workspaces\TestProject>mvn release:perform
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'release'.
> [INFO]
>
> [INFO] Building Test Project
> [INFO]task-segment: [release:perform] (aggregator-style)
> [INFO]
>
> [INFO] [release:perform]
> [INFO] Checking out the project to perform the release ...
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive checkout
> https://svnserver.mycorp.com/repos/scratch/tags/testproj-0.0.1
> checkout"
> [INFO] Working directory: D:\workspaces\TestProject\target
> [INFO] Executing goals 'deploy site-deploy'...
> [WARNING] Maven will be executed in interactive mode, but no input stream has
> been configured for this MavenInvoker inst
> ance.
> [INFO] [INFO] Scanning for projects...
> [INFO] [INFO]
>
> [INFO] [INFO] Building Test Project
> [INFO] [INFO]task-segment: [deploy, site-deploy]
> [INFO] [INFO]
>
> [INFO] Downloading:
> ${proxyURL}/releases/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading:
> ${proxyURL}/central/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading:
> ${proxyURL}/releases/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading:
> ${proxyURL}/thirdparty/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading:
> ${proxyURL}/central/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading:
> ${proxyURL}/codehaus/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading:
> ${proxyURL}/java.net/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading:
> ${proxyURL}/jboss/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] [INFO]
>
> [INFO] [ERROR] BUILD ERROR
> [INFO] [INFO]
>
> [INFO] [INFO] Error building POM (may not be this project's 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: (MRELEASE-135) Reelase plugin updates other plugins during release
[
http://jira.codehaus.org/browse/MRELEASE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MRELEASE-135.
-
Resolution: Won't Fix
Assignee: Brett Porter
This appears to be a property of Maven. It is better to lock down the versions
and utilise the tools available such as the enforcer to ensure this doesn't
happen.
> Reelase plugin updates other plugins during release
> ---
>
> Key: MRELEASE-135
> URL: http://jira.codehaus.org/browse/MRELEASE-135
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.0-beta-4
>Reporter: Joerg Schaible
>Assignee: Brett Porter
>Priority: Critical
>
> Couldn't happen at the worst moment:
> {noformat}
> ...
> [INFO] Executing preparation goals 'clean integration-test'...
> [INFO] Executing: mvn clean integration-test --no-plugin-updates -P
> elsag,elsag
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] project, Master Project of XZ0
> [INFO] project Web-Client
> [INFO] project EAR
> [INFO]
>
> [INFO] Building project, Master Project of XZ0
> [INFO]task-segment: [clean, integration-test]
> [INFO]
>
> [INFO] [clean:clean]
> [INFO] Deleting directory C:\Work\Projects\XZ0\target
> [INFO] Deleting directory C:\Work\Projects\XZ0\target\classes
> [INFO] Deleting directory C:\Work\Projects\XZ0\target\test-classes
> [INFO] [site:attach-descriptor]
> [INFO]
>
> [INFO] Building project Web-Client
> [INFO]task-segment: [clean, integration-test]
> [INFO]
>
> [INFO] [clean:clean]
> [INFO] Deleting directory C:\Work\Projects\XZ0\project-war\target
> [INFO] Deleting directory C:\Work\Projects\XZ0\project-war\target\classes
> [INFO] Deleting directory
> C:\Work\Projects\XZ0\project-war\target\test-classes
> [INFO] artifact org.apache.maven.plugins:maven-war-plugin: checking for
> updates from central
> [INFO] artifact org.apache.maven.plugins:maven-war-plugin: checking for
> updates from elsag-plugin-release
> Downloading:
> http://es3.elsag.de:8234/org/apache/maven/plugins/maven-war-plugin/2.0.1/maven-war-plugin-2.0.1.pom
> 1/1K
> 1K downloaded
> Downloading:
> http://es3.elsag.de:8234/org/apache/maven/plugins/maven-war-plugin/2.0.1/maven-war-plugin-2.0.1.jar
> 4/22K
> 8/22K
> 12/22K
> 16/22K
> 20/22K
> 22/22K
> 22K downloaded
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> Compiling 35 source files to
> C:\Work\Projects\XZ0\project-war\target\classes
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [surefire:test]
> [INFO] No tests to run.
> Downloading:
> http://es3.elsag.de:8234/org/apache/maven/maven-archiver/2.1/maven-archiver-2.1.pom
> 1/1K
> 1K downloaded
> Downloading:
> http://es3.elsag.de:8234/org/apache/maven/shared/maven-shared-components/2/maven-shared-components-2.pom
> 1/1K
> 1K downloaded
> Downloading:
> http://es3.elsag.de:8234/org/apache/maven/maven-archiver/2.1/maven-archiver-2.1.jar
> 4/9K
> 8/9K
> 9/9K
> 9K downloaded
> [INFO] [war:war]
> ...
> {noformat}
> http://es3.elsag.de:8234 is the address of our maven-proxy. Nevertheless the
> embedded Maven was started with "--no-plugin-updates" and this was happily
> ignored!
--
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: (MRELEASE-411) Release plugin disregards SCM configured element within the pom
[
http://jira.codehaus.org/browse/MRELEASE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MRELEASE-411.
-
Resolution: Won't Fix
Assignee: Brett Porter
This is not how the SCM element is designed to work in Maven, so the release
plugin can't support it.
You could make a feature request to support shallow checkouts by the release
plugin, however I'd encourage you to structure the project so that release
units are self contained.
> Release plugin disregards SCM configured element within the pom
> ---
>
> Key: MRELEASE-411
> URL: http://jira.codehaus.org/browse/MRELEASE-411
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.0-beta-7
> Environment: Maven 2.0.9 using maven-release-plugin version 2.0-beta-7
>Reporter: Robert Bracewell
>Assignee: Brett Porter
>
> I have a scenario where the SCM tag is configured with the following:
> {code:xml}
>
>
> scm:perforce:p4server:1666://components/projectA/pom.xml
>
> scm:perforce:p4server:1666://components/projectA/pom.xml
>
> {code}
> The location in Perforce //components/projectA contains the pom.xml in
> question and then a bunch of sub-directories located at the same level as the
> pom.
> When the release plugin runs a perform it churns out the following:
> [INFO] [release:perform]
> [INFO] Checking out the project to perform the release ...
> [INFO] The SCM location in your pom.xml (//components/projectA/pom.xml) is
> not equal to the depot location (//components/projectA). This happens
> frequently with branches. Ignoring the SCM location.
> For my situation the above is incorrect as I am only releasing a pom not
> several modules. The release:perform then continues to sync every file
> located under //components/projectA which in my case is several thousand and
> as such takes several minutes to complete.
> The release plugin should be able to handle such SCM elements and understand
> that only a single file is being released when such is explicitly defined
--
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: (MRELEASE-262) Release pom dependencies are incorrectly rewritten for internal snapshot ranges
[ http://jira.codehaus.org/browse/MRELEASE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRELEASE-262. - Resolution: Cannot Reproduce Assignee: Brett Porter not seeing test failures - Mark, can you reopen if this is still an issue? > Release pom dependencies are incorrectly rewritten for internal snapshot > ranges > --- > > Key: MRELEASE-262 > URL: http://jira.codehaus.org/browse/MRELEASE-262 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0-beta-6 >Reporter: Mark Hobson >Assignee: Brett Porter > > GenerateReleasePomsPhaseTest.testRewriteInternalRangeDependency fails. -- 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: (MRELEASE-312) CVS examples in guide to using release plugin
[ http://jira.codehaus.org/browse/MRELEASE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRELEASE-312. - Resolution: Won't Fix Assignee: Brett Porter This is a very old issue. I'd expect a request to show examples for Git or another SCM would be more relevant now. > CVS examples in guide to using release plugin > - > > Key: MRELEASE-312 > URL: http://jira.codehaus.org/browse/MRELEASE-312 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: scm >Reporter: Miguel Griffa >Assignee: Brett Porter > > Guide to using release plugin should include examples for CVS as well as SVN -- 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: (MRELEASE-113) prepare dryRun should also run site:site
[ http://jira.codehaus.org/browse/MRELEASE-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRELEASE-113. - Resolution: Won't Fix Assignee: Brett Porter Please use the preparationGoals configuration > prepare dryRun should also run site:site > > > Key: MRELEASE-113 > URL: http://jira.codehaus.org/browse/MRELEASE-113 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: perform >Affects Versions: 2.0-beta-4 >Reporter: Mike Perham >Assignee: Brett Porter > > Currently just runs 'clean integration-test'. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-203) support more than one release pattern via new goal release:branch
[ http://jira.codehaus.org/browse/MRELEASE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRELEASE-203: -- Affects Version/s: (was: 2.1) > support more than one release pattern via new goal release:branch > - > > Key: MRELEASE-203 > URL: http://jira.codehaus.org/browse/MRELEASE-203 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: scm >Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 > Environment: irrelevant >Reporter: Joerg Buchberger > > - CURRENT BEHAVIOUR: > maven currently seems to support only this one release pattern well: > *_feature branches_* > develop towards release in trunk; prepare it by tagging, then release from > that tag; continue for next iteration in trunk (+pom version tags are nicely > updated+), while some or most features are done in branches > - DESIRABLE IMPROVEMENT: > alternative patterns or customizations such as *_release branches_* should be > available: > develop features in trunk and rarely use feature branches; begin release > phase by branching, then work towards release in branch, while continuing for > next iteration in trunk (+currently pom version tag hell, when doing this > manually+); prepare by tagging from branch, then release from tag > this could be achieved by offering a new goal release:branch, that creates a > branch from trunk, updates *the trunk* poms for next iteration and stores > some properties in the branch, so that upon release:prepare from *the > branch*, the user can opt out preparations for next iteration on the branch > - loosely related to following issues: > -- branch instead of tag (MRELEASE-179) > -- branch during prepare (MRELEASE-170) -- 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: (MRELEASE-402) The release plugin will not check for local modifications after the first initial check
[ http://jira.codehaus.org/browse/MRELEASE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRELEASE-402. - Resolution: Duplicate Assignee: Brett Porter (was: Jason van Zyl) > The release plugin will not check for local modifications after the first > initial check > --- > > Key: MRELEASE-402 > URL: http://jira.codehaus.org/browse/MRELEASE-402 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-8 >Reporter: Jason van Zyl >Assignee: Brett Porter > > You can start the release process, have a failure, make local modifications, > and still have the release plugin allow you to create a tag. -- 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: (MRELEASE-509) Release dependencies before releasing the projects
[ http://jira.codehaus.org/browse/MRELEASE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRELEASE-509. - Resolution: Won't Fix Assignee: Brett Porter I think this over-reaches the scope of the release plugin. It might be best to consider a separate plugin to do this. > Release dependencies before releasing the projects > --- > > Key: MRELEASE-509 > URL: http://jira.codehaus.org/browse/MRELEASE-509 > Project: Maven 2.x Release Plugin > Issue Type: Wish >Reporter: Mohammad Norouzi >Assignee: Brett Porter > > Consider we have project A which is dependent to B and C with SNAPSHOT > version. then what if the project version manager was able to run the command > with an option and the plugin first checks out all the snapshot versions and > creates a release version for each and then create a release version for > project which this plugin is fired and update all the pom files. -- 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: (MRELEASE-413) Branch goal should not insert version information for child modules which do not already have it
[ http://jira.codehaus.org/browse/MRELEASE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRELEASE-413. - Resolution: Won't Fix Assignee: Brett Porter correct behaviour, and you can use autoVersionSubModules to not worry about typos > Branch goal should not insert version information for child modules which do > not already have it > > > Key: MRELEASE-413 > URL: http://jira.codehaus.org/browse/MRELEASE-413 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: branch >Affects Versions: 2.0-beta-8 > Environment: windows >Reporter: Andrius Kurtinaitis >Assignee: Brett Porter > Attachments: pavyzdys.zip > > > When performing a release:branch on a project which have several child > modules, the branch plugin updates versions in the parent and also all child > pom.xml files. > Even in those files having no information, i.e. those inheriting > the version from the parent. > IMO branch plugin should leave those pom.xml files versionless and only > change those pom.xml files that have their own version. > I attach one such multimodule project. You will have to edit the scm and > deployment info to try it. > What is the preferred form of test cases for plugin issues? -- 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: (MRELEASE-504) Check if working copy is up-to-date
[ http://jira.codehaus.org/browse/MRELEASE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRELEASE-504. - Resolution: Duplicate Assignee: Brett Porter > Check if working copy is up-to-date > --- > > Key: MRELEASE-504 > URL: http://jira.codehaus.org/browse/MRELEASE-504 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: prepare >Affects Versions: 2.0-beta-9 >Reporter: Stefan Seelmann >Assignee: Brett Porter > > It would be nice if the release:prepare goal could check if the working copy > is up-to-date. > For svn the local and the remote revision number could be compared. > For git the it should also be possible to compare commit IDs. > My current problem that release:prepare fails if there is a newer revision in > the SVN repository: > --- > [INFO] Unable to commit files > Provider message: > The svn command failed. > Command output: > svn: Commit failed (details follow): > svn: File '/firstmodule/trunk/pom.xml' is out of date > --- -- 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: (MRELEASE-301) generateReleasePoms doesn't seem to default to false, and setting the property explicitly doesn't work either
[ http://jira.codehaus.org/browse/MRELEASE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRELEASE-301. - Resolution: Cannot Reproduce Assignee: Brett Porter I believe this is no longer an issue due to the change in goals in 2.0. > generateReleasePoms doesn't seem to default to false, and setting the > property explicitly doesn't work either > - > > Key: MRELEASE-301 > URL: http://jira.codehaus.org/browse/MRELEASE-301 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0-beta-6, 2.0-beta-7 >Reporter: Samuel Le Berrigaud >Assignee: Brett Porter > > Without any specific configuration, running mvn release:prepare generates the > release POMs even though the documentation states that this shouldn't be. > Setting the generateReleasePoms property explicitly on the command line ( > -DgenerateReleasePoms=false ) does not prevent POMs from being generated > either! -- 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] Moved: (SCM-577) SvnCheckInConsumer is "English locale" dependent
[ http://jira.codehaus.org/browse/SCM-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MRELEASE-537 to SCM-577: --- Complexity: Intermediate Component/s: (was: scm) Affects Version/s: (was: 2.0) (was: 2.0-beta-9) Key: SCM-577 (was: MRELEASE-537) Project: Maven SCM (was: Maven 2.x Release Plugin) > SvnCheckInConsumer is "English locale" dependent > > > Key: SCM-577 > URL: http://jira.codehaus.org/browse/SCM-577 > Project: Maven SCM > Issue Type: Bug > Environment: Debian > Locale fr_FR >Reporter: Frédéric Camblor >Priority: Critical > > Looking at the SvnCheckInConsumer class (here : > http://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.3/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/checkin/SvnCheckInConsumer.java) > we can say that if message displayed while commiting file is not "Committed > revision XXX", revision parsing will fail ! > Maybe the implementation should look at the current Locale ? > Or (maybe simplier) some regex such as [^0-9]*([0-9]+)[^0-9]* should be used > to match/retrieve current revision number after commit ? > When using French locale, revision 0 is returned to the SVN commit result ... > so, later, tagging fails with some spacy message "revision 0 doesn't exist". -- 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
