servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mateusz Prokopowicz (JIRA)" <>
Subject [jira] [Updated] (SM-2145) jbi-maven-plugin: Artifact unexpectedly filtered
Date Wed, 06 Mar 2013 15:10:13 GMT


Mateusz Prokopowicz updated SM-2145:

    Attachment: artifact_filtering_fixed1.patch

The same problem occurs in _GenerateComponentMojo_ (line: 186) - there are references compared
instead of objects. I've attached a patch with the fix
> jbi-maven-plugin: Artifact unexpectedly filtered
> ------------------------------------------------
>                 Key: SM-2145
>                 URL:
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: jbi-maven-plugin-4.3, jbi-maven-plugin-4.4, jbi-maven-plugin-4.5
>            Reporter: Julien Blass
>            Assignee: Jean-Baptiste Onofré
>             Fix For: jbi-maven-plugin-4.6
>         Attachments: artifact_filtering_fixed1.patch
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
> Some of the artifacts defined in my project's pom.xml in scope 'compile' are unexpectedly
filtered during the generation of a component.
> By debugging the generation process, I have found that this is due to the use of '=='
to compare the strings defining two artifact's scopes (,
line 225). For a reason that I could not establish yet, my artifact as a scope value of 'compile'
but the string object is not equal to Artifact.SCOPE_COMPILE. 
> I think that one solution for this bug is either to change "artifact.getScope() == Artifact.SCOPE_COMPILE"
by "artifact.getScope().equals(Artifact.SCOPE_COMPILE)" or to find the places where the scope
of the artifact is set to a value that is not a constant of the class org.apache.maven.artifact.Artifact.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message