[jira] Created: (SUREFIRE-528) Splitting tests names in two categories : success and failure
Splitting tests names in two categories : success and failure - Key: SUREFIRE-528 URL: http://jira.codehaus.org/browse/SUREFIRE-528 Project: Maven Surefire Issue Type: Improvement Affects Versions: 2.0 (2.2 plugin) Reporter: Emmanuel Lécharny We have to check all the *.txt files to find the ones which contain some errors. The fact that failed tests are listed before does not help a lot when you have hundred of tests run with sometime lot of logs. I would rather propose that we either create two sub-directories (failure/success) or that we postfix tests. A good example : ... Tests run: 197, Failures: 1, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /home/elecharny/apacheds/mina/trunk/core/target/surefire-reports for the individual test results. ... Would be better to have : Please refer to /home/elecharny/apacheds/mina/trunk/core/target/surefire-reports/failure for the individual test failures. -- 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: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153195#action_153195
]
Kyle Lebel commented on SCM-406:
Actually just after posting my comment I noticed this was already fixed in
1.1.1 - I guess the next step then to make this official is updating
maven-release-plugin / manager? Anyone know the plans for this?
> scm tag does not work with Subversion 1.5.1
> ---
>
> Key: SCM-406
> URL: http://jira.codehaus.org/browse/SCM-406
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.0
>Reporter: James William Dumay
> Fix For: 1.1.1
>
>
> scm:checkin does not work with Subversion 1.5.1
> On release:perform (which I assume calls scm:checkin) the following error
> occurs:
> {code}
> svn: File
> '/svn/private/atlassian/confluence/tags/confluence-project-2.10-m1/conf-acceptance-test/pom.xml'
> already exists
> {code}
> Using subversion 1.4.x is a good enough workaround.
--
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: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153193#action_153193
]
Kyle Lebel commented on SCM-406:
Hey guys, I downloaded the source code for the multiple dependencies
(maven-release-plugin, maven-release-manager, maven-scm-providers-svn).
If the maven-release-plugin you have is configured to use the latest, it will
use 1.1 version of the maven-scm-providers. Simply changing the following line
162 in SvnTagCommand resolves this issue:
cl.createArgument().setValue( "." );
to
cl.createArgument().setValue( repository.getUrl() );
So not sure if someone would want to make an official revision for this. For
now I will deploy this to our local maven repository.
> scm tag does not work with Subversion 1.5.1
> ---
>
> Key: SCM-406
> URL: http://jira.codehaus.org/browse/SCM-406
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.0
>Reporter: James William Dumay
> Fix For: 1.1.1
>
>
> scm:checkin does not work with Subversion 1.5.1
> On release:perform (which I assume calls scm:checkin) the following error
> occurs:
> {code}
> svn: File
> '/svn/private/atlassian/confluence/tags/confluence-project-2.10-m1/conf-acceptance-test/pom.xml'
> already exists
> {code}
> Using subversion 1.4.x is a good enough workaround.
--
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: (MSHARED-80) NullPointer in DefaultDependencyTreeBuilder.java:93, no logger
[
http://jira.codehaus.org/browse/MSHARED-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153183#action_153183
]
Mark Hobson commented on MSHARED-80:
How are you using this cloned TreeMojo, as another maven plugin? If you attach
a simplified project that reproduces your problem then I can take a look.
> NullPointer in DefaultDependencyTreeBuilder.java:93, no logger
> ---
>
> Key: MSHARED-80
> URL: http://jira.codehaus.org/browse/MSHARED-80
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
>Affects Versions: maven-dependency-tree 1.2
> Environment: Windows XP 64 JDK 1.6
>Reporter: MTStorm
>Assignee: Mark Hobson
>Priority: Critical
>
> I have a report and a mojo that seeks transversal dependencies. It shows a
> nullpointer in the DefaultDependencyTreeBuilder.
> I can not figure it out what is wrong sice the implementation off
> DependencyTreeBuilder is assigned by Maven and I have no controll on the
> logger.
> Here is the code snippet
> //members
> /**
>* Used to look up Artifacts in the remote repository.
>*
>* @parameter expression=
>*
> "${component.org.apache.maven.artifact.factory.ArtifactFactory}"
>* @required
>* @readonly
>*/
> protected org.apache.maven.artifact.factory.ArtifactFactory
> artifactFactory;
> /**
>* Used to look up Artifacts in the remote repository.
>*
>* @parameter expression=
>*
> "${component.org.apache.maven.artifact.resolver.ArtifactResolver}"
>* @required
>* @readonly
>*/
> protected org.apache.maven.artifact.resolver.ArtifactResolver resolver;
> /**
>* Artifact collector, needed to resolve dependencies.
>*
>* @component
> role="org.apache.maven.artifact.resolver.ArtifactCollector"
>* @required
>* @readonly
>*/
> protected ArtifactCollector artifactCollector;
> /**
>* @component
>*
> role="org.apache.maven.artifact.metadata.ArtifactMetadataSource"
>*hint="maven"
>* @required
>* @readonly
>*/
> protected ArtifactMetadataSource artifactMetadataSource;
> /**
>* Dependency tree builder component.
>*
>* @component expression=
>*
> "org.apache.maven.shared.dependency.tree.DependencyTreeBuilder"
>* @required
>* @readonly
>*/
> private DependencyTreeBuilder dependencyTreeBuilder;
> //sample snippet to use in report and mojo
> ArtifactFilter artifactFilter = new ScopeArtifactFilter(
> Artifact.SCOPE_COMPILE);
> DependencyNode dn;
> getLog().info("Start");
> try {
> dn = dependencyTreeBuilder.buildDependencyTree(
> project, localRepository,
> artifactFactory, artifactMetadataSource,
> artifactFilter, artifactCollector);
>
> } catch (DependencyTreeBuilderException e) {
> e.printStackTrace();
> getLog().error("oeps",e);
> }
> getLog().info("Done");
--
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: (MSHARED-80) NullPointer in DefaultDependencyTreeBuilder.java:93, no logger
[
http://jira.codehaus.org/browse/MSHARED-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153181#action_153181
]
MTStorm commented on MSHARED-80:
Thanks, but the problem remains. Even when I copy the entire TreeMojo and
deploy it in an other groupId, the nullpointer remains... Here is how the
TreeMojo does it.
/**
* The dependency tree builder to use.
*
* @component
* @required
* @readonly
*/
private DependencyTreeBuilder dependencyTreeBuilder;
> NullPointer in DefaultDependencyTreeBuilder.java:93, no logger
> ---
>
> Key: MSHARED-80
> URL: http://jira.codehaus.org/browse/MSHARED-80
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
>Affects Versions: maven-dependency-tree 1.2
> Environment: Windows XP 64 JDK 1.6
>Reporter: MTStorm
>Assignee: Mark Hobson
>Priority: Critical
>
> I have a report and a mojo that seeks transversal dependencies. It shows a
> nullpointer in the DefaultDependencyTreeBuilder.
> I can not figure it out what is wrong sice the implementation off
> DependencyTreeBuilder is assigned by Maven and I have no controll on the
> logger.
> Here is the code snippet
> //members
> /**
>* Used to look up Artifacts in the remote repository.
>*
>* @parameter expression=
>*
> "${component.org.apache.maven.artifact.factory.ArtifactFactory}"
>* @required
>* @readonly
>*/
> protected org.apache.maven.artifact.factory.ArtifactFactory
> artifactFactory;
> /**
>* Used to look up Artifacts in the remote repository.
>*
>* @parameter expression=
>*
> "${component.org.apache.maven.artifact.resolver.ArtifactResolver}"
>* @required
>* @readonly
>*/
> protected org.apache.maven.artifact.resolver.ArtifactResolver resolver;
> /**
>* Artifact collector, needed to resolve dependencies.
>*
>* @component
> role="org.apache.maven.artifact.resolver.ArtifactCollector"
>* @required
>* @readonly
>*/
> protected ArtifactCollector artifactCollector;
> /**
>* @component
>*
> role="org.apache.maven.artifact.metadata.ArtifactMetadataSource"
>*hint="maven"
>* @required
>* @readonly
>*/
> protected ArtifactMetadataSource artifactMetadataSource;
> /**
>* Dependency tree builder component.
>*
>* @component expression=
>*
> "org.apache.maven.shared.dependency.tree.DependencyTreeBuilder"
>* @required
>* @readonly
>*/
> private DependencyTreeBuilder dependencyTreeBuilder;
> //sample snippet to use in report and mojo
> ArtifactFilter artifactFilter = new ScopeArtifactFilter(
> Artifact.SCOPE_COMPILE);
> DependencyNode dn;
> getLog().info("Start");
> try {
> dn = dependencyTreeBuilder.buildDependencyTree(
> project, localRepository,
> artifactFactory, artifactMetadataSource,
> artifactFilter, artifactCollector);
>
> } catch (DependencyTreeBuilderException e) {
> e.printStackTrace();
> getLog().error("oeps",e);
> }
> getLog().info("Done");
--
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: (MCHANGES-129) The version can't be set from the cli in announcement-mail
[ http://jira.codehaus.org/browse/MCHANGES-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MCHANGES-129. - Resolution: Fixed fixed in rev [711706|http://svn.apache.org/viewvc?rev=711706&view=rev] > The version can't be set from the cli in announcement-mail > -- > > Key: MCHANGES-129 > URL: http://jira.codehaus.org/browse/MCHANGES-129 > Project: Maven 2.x Changes Plugin > Issue Type: New Feature > Components: announcement >Affects Versions: 2.0-beta-2, 2.0-beta-3, 2.0 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.1 > > > Currently, it's possible to define the version in the cli : > -Dannounce.version. > This means we can send an announce mail only for the current version of the > pom. > My use case is : > * I release my project > * I send the announce email (at this stage the version is the next dev one) > * here I can send the email from the released version except if checkout the > tagged version or change manually the 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: (MCHANGES-128) unable to use "toAddresses" field for announces
[
http://jira.codehaus.org/browse/MCHANGES-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MCHANGES-128.
-
Resolution: Fixed
fix in rev [711701|http://svn.apache.org/viewvc?rev=711701&view=rev]
> unable to use "toAddresses" field for announces
> ---
>
> Key: MCHANGES-128
> URL: http://jira.codehaus.org/browse/MCHANGES-128
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: announcement
>Affects Versions: 2.0
>Reporter: Fabien Galampoix
>Assignee: Olivier Lamy
> Fix For: 2.1
>
>
> Unable to use "toAddresses" field for mail announces.
> Error raised :
> >>> [INFO] Failed to configure plugin parameters for:
> >>> org.apache.maven.plugins:maven-changes-plugin:2.1-SNAPSHOT
> >>> Cause: Class 'java.util.List' cannot be instantiated
> It seems that there was a similar error on changelog plugin before.
> This patch may help :
> >>> in ---
> >>> src/main/java/org/apache/maven/plugin/announcement/AnnouncementMailMojo.java
> >>> - * @parameter expression="${changes.toAddresses}"
> >>> + * @parameter
--
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: (MCHANGES-129) The version can't be set from the cli in announcement-mail
[ http://jira.codehaus.org/browse/MCHANGES-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MCHANGES-129: -- Summary: The version can't be set from the cli in announcement-mail (was: The version can be set from the cli in announcement-mail) > The version can't be set from the cli in announcement-mail > -- > > Key: MCHANGES-129 > URL: http://jira.codehaus.org/browse/MCHANGES-129 > Project: Maven 2.x Changes Plugin > Issue Type: New Feature > Components: announcement >Affects Versions: 2.0-beta-2, 2.0-beta-3, 2.0 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.1 > > > Currently, it's possible to define the version in the cli : > -Dannounce.version. > This means we can send an announce mail only for the current version of the > pom. > My use case is : > * I release my project > * I send the announce email (at this stage the version is the next dev one) > * here I can send the email from the released version except if checkout the > tagged version or change manually the 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: (MNG-3817) Property inheritance when filtering with multiple profiles is gone
[
http://jira.codehaus.org/browse/MNG-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Buechler closed MNG-3817.
Resolution: Not A Bug
Fix Version/s: 2.0.9
The problem exists only if empty values are inherited, which can be quite
always eliminated by avoiding to rely on empty values.
> Property inheritance when filtering with multiple profiles is gone
> ---
>
> Key: MNG-3817
> URL: http://jira.codehaus.org/browse/MNG-3817
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.0.9
>Reporter: Martin Buechler
>Priority: Blocker
> Fix For: 2.0.9
>
> Attachments: MNG-3817.zip
>
>
> pom.xml:
>
>
> default.properties
>
>
>
>
> first
>
>
> first.properties
>
>
>
>
> second
>
>
> second.properties
>
>
> ...
> default.properties:
> prop=
> first.properties:
> prop=first_value
> second.properties:
> other_prop=${prop}
> since 2.0.9 the value of
> other_prop
> is not replaced and is written as ${prop}, instead of inherit the value
> 'first_value', when executing
>mvn -Pfirst,second process-resources
> This breaks existing configurations badly and I do not see a workaround
> whithout losing the ability to configure in more than one dimension, which
> makes mvn 2.0.9 quite unsuable for project requirements in real life.
>
--
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-3668) maven-eclipse-plugin 2.5 is failing with java.lang.LinkageError
[
http://jira.codehaus.org/browse/MNG-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153162#action_153162
]
Yann Albou commented on MNG-3668:
-
Now it works with maven-eclipse-plugin 2.5.
But with a plugin that use JDK classes (for instance
com.sun.mirror.apt.AnnotationProcessorFactory) it fails :
{code}
org.test.simplePlugin.MyMojo#execute() caused a linkage error
(java.lang.NoClassDefFoundError). Check the realms:
java.lang.NoClassDefFoundError: com.sun.mirror.apt.AnnotationProcessorFactory
at org.test.simplePlugin.MyMojo.class$(MyMojo.java:33)
at org.test.simplePlugin.MyMojo.execute(MyMojo.java:33)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:623)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:521)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:288)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:214)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:172)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:208)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:854)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
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:585)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
{code}
of course the plugin use the dependency:
{code}
com.sun
tools
1.5
system
${java.home}/../lib/tools.jar
{code}
see MNGECLIPSE-745 for a test case.
> maven-eclipse-plugin 2.5 is failing with java.lang.LinkageError
> ---
>
> Key: MNG-3668
> URL: http://jira.codehaus.org/browse/MNG-3668
> Project: Maven 2
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.0-alpha-1
>Reporter: Eugene Kuleshov
> Fix For: 3.0-alpha-1
>
>
> eclipse:eclipse goal in maven-eclipse-plugin 2.5 is failing with the
> following exception. same thing is working with 2.4
> {code}
> Exception in thread "main" java.lang.LinkageError: loader constraint
> violation: when resolving method
>
> "org.codehaus.plexus.util.xml.Xpp3DomWriter.write(Lorg/codehaus/plexus/util/xml/XMLWriter;Lorg/codehaus/plexus/util/xml/Xpp3Dom;)V"
>
> the class loader (instance of
> org/codehaus/plexus/classworlds/realm/ClassRealm) of the current class,
> org/apache/maven/plugin/eclipse/writers/wtp/EclipseWtpApplicationXMLWriter,
> and the class loader (instance of
> org/codehaus/plexus/classworlds/realm/ClassRealm)
> for resolved class, org/codehaus/plexus/util/xml/Xpp3DomWriter, have
> different Class objects for the type
> org/codehaus/plexus/util/xml/XMLWriter used in the signature
> at
> org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpApplicationXMLWriter.writePrettyXmlFile(EclipseWtpApplicationXMLWriter.java:624)
> at
> org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpApplicationXMLWriter.write(EclipseWtpApplicationXMLWriter.java:157)
> at
> org.apache.maven.plugin.eclipse.EclipsePlugin.writeConfiguration(EclipsePlugin.java:957)
> at
> org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:494)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
> at
> org.apache.maven.DefaultMaven.execute_aroundBody0(De
[jira] Commented: (MAVENUPLOAD-2261) Automatic upload of mockito versions.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153144#action_153144 ] Szczepan Faber commented on MAVENUPLOAD-2261: - Erik Brakkee helps us getting mockito jars quickly to maven central - as written at the bottom of http://mockito.org. Thanks a lot! Szczepan Faber > Automatic upload of mockito versions. > - > > Key: MAVENUPLOAD-2261 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2261 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Erik Brakkee > > Authenticity > = > Please contact Szczepan Faber for information about the authenticity of this > request. He is the owner of the mockito.org domain. > Also, my name will appear shortly on the mockito wiki at > http://code.google.com/p/mockito/. -- 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: (MAVENUPLOAD-2261) Automatic upload of mockito versions.
Automatic upload of mockito versions. - Key: MAVENUPLOAD-2261 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2261 Project: Maven Upload Requests Issue Type: Wish Reporter: Erik Brakkee Authenticity = Please contact Szczepan Faber for information about the authenticity of this request. He is the owner of the mockito.org domain. Also, my name will appear shortly on the mockito wiki at http://code.google.com/p/mockito/. -- 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: (MAVENUPLOAD-2260) jetty-gwt upload request
jetty-gwt upload request Key: MAVENUPLOAD-2260 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2260 Project: Maven Upload Requests Issue Type: Wish Reporter: Merijn de Jonge http://www.extra.research.philips.com/hera/people/mdejonge/maven/jetty-gwt-6.1.12-bundle.jar I'm a user, not a developer of the above package. This is an update to the newest version of the jetty-gwt package that works with gwt-1.5.x. -- 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: (MAVENUPLOAD-2259) JasperReports 3.1.2 upload
JasperReports 3.1.2 upload -- Key: MAVENUPLOAD-2259 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2259 Project: Maven Upload Requests Issue Type: Task Reporter: Teodor Danciu http://jasperreports.sf.net/maven/jasperreports-3.1.2-bundle.jar http://sourceforge.net/projects/jasperreports http://sourceforge.net/project/memberlist.php?group_id=36382 Open Source Reporting Engine -- 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: (MCHANGES-128) unable to use "toAddresses" field for announces
[
http://jira.codehaus.org/browse/MCHANGES-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153118#action_153118
]
Fabien Galampoix commented on MCHANGES-128:
---
Good example from Olivier, with these informations :
JVM:
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)
... and maven 2.0.9
Issue is resolved when i remove "expression="${changes.toAddresses}" as shown
in the description.
> unable to use "toAddresses" field for announces
> ---
>
> Key: MCHANGES-128
> URL: http://jira.codehaus.org/browse/MCHANGES-128
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: announcement
>Affects Versions: 2.0
>Reporter: Fabien Galampoix
> Fix For: 2.1
>
>
> Unable to use "toAddresses" field for mail announces.
> Error raised :
> >>> [INFO] Failed to configure plugin parameters for:
> >>> org.apache.maven.plugins:maven-changes-plugin:2.1-SNAPSHOT
> >>> Cause: Class 'java.util.List' cannot be instantiated
> It seems that there was a similar error on changelog plugin before.
> This patch may help :
> >>> in ---
> >>> src/main/java/org/apache/maven/plugin/announcement/AnnouncementMailMojo.java
> >>> - * @parameter expression="${changes.toAddresses}"
> >>> + * @parameter
--
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: (MSHARED-80) NullPointer in DefaultDependencyTreeBuilder.java:93, no logger
[
http://jira.codehaus.org/browse/MSHARED-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153102#action_153102
]
Mark Hobson commented on MSHARED-80:
Firstly, it looks like your plexus annotations are wrong:
{noformat}/**
* Dependency tree builder component.
*
* @component
expression="org.apache.maven.shared.dependency.tree.DependencyTreeBuilder"
* @required
* @readonly
*/
private DependencyTreeBuilder dependencyTreeBuilder;{noformat}
@component takes a 'role' attribute, not an 'expression'. So it should be:
{noformat}/**
* Dependency tree builder component.
*
* @component
role="org.apache.maven.shared.dependency.tree.DependencyTreeBuilder"
* @required
* @readonly
*/
private DependencyTreeBuilder dependencyTreeBuilder;{noformat}
Of course, DependencyTreeBuilder will only be injected here if this class is
instantiated by plexus, which all maven plugins are.
Secondly, the NPE is due to DependencyTreeBuilder having no Logger injected
into it. Again, this would only happen if it were constructed outside of
maven/plexus, and not if you've got your plexus annotations set up as described
above.
Hope this helps.
> NullPointer in DefaultDependencyTreeBuilder.java:93, no logger
> ---
>
> Key: MSHARED-80
> URL: http://jira.codehaus.org/browse/MSHARED-80
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
>Affects Versions: maven-dependency-tree 1.2
> Environment: Windows XP 64 JDK 1.6
>Reporter: MTStorm
>Priority: Critical
>
> I have a report and a mojo that seeks transversal dependencies. It shows a
> nullpointer in the DefaultDependencyTreeBuilder.
> I can not figure it out what is wrong sice the implementation off
> DependencyTreeBuilder is assigned by Maven and I have no controll on the
> logger.
> Here is the code snippet
> //members
> /**
>* Used to look up Artifacts in the remote repository.
>*
>* @parameter expression=
>*
> "${component.org.apache.maven.artifact.factory.ArtifactFactory}"
>* @required
>* @readonly
>*/
> protected org.apache.maven.artifact.factory.ArtifactFactory
> artifactFactory;
> /**
>* Used to look up Artifacts in the remote repository.
>*
>* @parameter expression=
>*
> "${component.org.apache.maven.artifact.resolver.ArtifactResolver}"
>* @required
>* @readonly
>*/
> protected org.apache.maven.artifact.resolver.ArtifactResolver resolver;
> /**
>* Artifact collector, needed to resolve dependencies.
>*
>* @component
> role="org.apache.maven.artifact.resolver.ArtifactCollector"
>* @required
>* @readonly
>*/
> protected ArtifactCollector artifactCollector;
> /**
>* @component
>*
> role="org.apache.maven.artifact.metadata.ArtifactMetadataSource"
>*hint="maven"
>* @required
>* @readonly
>*/
> protected ArtifactMetadataSource artifactMetadataSource;
> /**
>* Dependency tree builder component.
>*
>* @component expression=
>*
> "org.apache.maven.shared.dependency.tree.DependencyTreeBuilder"
>* @required
>* @readonly
>*/
> private DependencyTreeBuilder dependencyTreeBuilder;
> //sample snippet to use in report and mojo
> ArtifactFilter artifactFilter = new ScopeArtifactFilter(
> Artifact.SCOPE_COMPILE);
> DependencyNode dn;
> getLog().info("Start");
> try {
> dn = dependencyTreeBuilder.buildDependencyTree(
> project, localRepository,
> artifactFactory, artifactMetadataSource,
> artifactFilter, artifactCollector);
>
> } catch (DependencyTreeBuilderException e) {
> e.printStackTrace();
> getLog().error("oeps",e);
> }
> getLog().info("Done");
--
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-186) Build classpath for dependency between modules in multiproject
Build classpath for dependency between modules in multiproject
--
Key: MDEP-186
URL: http://jira.codehaus.org/browse/MDEP-186
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: build-classpath
Affects Versions: 2.0
Environment: * Windows XP SP3
* JDK 1.5.0_16-b02
* Maven 2.0.9
Reporter: Petr Prochazka
Assignee: Brian Fox
Attachments: db-mapper-logs.zip, db-mapper.zip
I can create classpath to file in mutli project in this use case:
# Replace local repo path with prefix
## If artifacts is in my defined company group id, replace path with /KIV prefix
## Others artefacts, replace path with /EXT prefix
I using this settings of plugin:
{noformat}
maven-dependency-plugin
2.0
gk-depends
generate-sources
build-classpath
${project.build.directory}/classpath/classpath-zcu.txt
/KIV
cz.zcu.kiv
ext-depends
generate-sources
build-classpath
${project.build.directory}/classpath/classpath-ext.txt
/EXT
cz.zcu.kiv,junit
:
true
/
true
{noformat}
Problem is if i call goal {{package}} or {{install}}, then final path to
dependency artifact is not refer to my local repository (property M2_REPO), but
to artifact build localy in project directory.
For ex. have this dependency tree and module db-mapper has dependency to others
modules (db-mapper-core, webkiv-db, etc.), which is in same group ID:
{noformat}
[INFO]
[INFO] Building DB Mapper Distribution
[INFO]task-segment: [dependency:tree]
[INFO]
[INFO] [dependency:tree]
[INFO] cz.zcu.kiv:db-mapper:jar:0.7.3-SNAPSHOT
[INFO] +- cz.zcu.kiv:db-mapper-core:jar:0.7.3-SNAPSHOT:compile
[INFO] | +- commons-cli:commons-cli:jar:1.1:compile
[INFO] | +- org.springframework:spring-context:jar:2.5.5:compile
[INFO] | | +- aopalliance:aopalliance:jar:1.0:compile
[INFO] | | \- org.springframework:spring-core:jar:2.5.5:compile
[INFO] | +- org.springframework:spring-beans:jar:2.5.5:compile
[INFO] | +- javax.xml.bind:jaxb-api:jar:2.1:compile
[INFO] | | +- javax.xml.stream:stax-api:jar:1.0-2:compile
[INFO] | | \- javax.activation:activation:jar:1.1:compile
[INFO] | +- javax.xml:jsr173:jar:1.0:compile
[INFO] | +- javax.xml:jaxb-impl:jar:2.1:compile
[INFO] | \- commons-lang:commons-lang:jar:2.4:compile
[INFO] +- cz.zcu.kiv:web-kiv-old:jar:1.0-SNAPSHOT:compile
[INFO] | +- org.springframework:spring-jdbc:jar:2.5.5:compile
[INFO] | | \- org.springframework:spring-tx:jar:2.5.5:compile
[INFO] | \- mysql:mysql-connector-java:jar:5.1.6:compile
[INFO] +- cz.zcu.kiv:webkiv-db:jar:2.14-SNAPSHOT:compile
[INFO] +- cz.zcu.kiv:webkiv-db-processing:jar:0.7.3-SNAPSHOT:compile
[INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] \- log4j:log4j:jar:1.2.15:runtime
{noformat}
and fragment of result of classpath is following:
{noformat}
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo]
D:/Projects-test/db-mapper/db-mapper-core/target/db-mapper-core-0.7.3-SNAPSHOT.jar:
D:/Projects-test/db-mapper/web-kiv-old/target/web-kiv-old-1.0-SNAPSHOT.jar:
...
/EXT/aopalliance/aopalliance/1.0/aopalliance-1.0.jar:
/EXT/commons-cli/commons-cli/1.1/commons-cli-1.1.jar:
...
{noformat}
Classpath refer to project build directory, but not to local repository :-(
Have I settings anything wrong or is it bug?
I attach simple test case with multiproject and logs in different goals
(generate-sources, compile, package, generate)
Regards
Petr Prochazka
--
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
