You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2007/11/29 18:19:27 UTC
[jira] Created: (SM-1157) maven-jbi-plugin creates wrong classpath
entries in jbi.xml for SE
maven-jbi-plugin creates wrong classpath entries in jbi.xml for SE
------------------------------------------------------------------
Key: SM-1157
URL: https://issues.apache.org/activemq/browse/SM-1157
Project: ServiceMix
Issue Type: Bug
Components: tooling
Reporter: Tammo van Lessen
When the m2 build is customized and a <finalname> is set (i.e. is different to ${artifactname}-${version}), the generated jbi.xml is wrong.
I guess the problem is located in Line 207in GenerateComponentDescriptorMojo.java
Should be something like project.getBuild().getFinalName()
http://maven.apache.org/ref/current/maven-model/apidocs/org/apache/maven/model/BuildBase.html#getFinalName()
http://maven.apache.org/ref/2.0.4/maven-project/apidocs/org/apache/maven/project/MavenProject.html#getBuild()
Cheers,
Tammo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1157) maven-jbi-plugin creates wrong classpath
entries in jbi.xml for SE
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated SM-1157:
--------------------------------
Patch Info: [Patch Available]
> maven-jbi-plugin creates wrong classpath entries in jbi.xml for SE
> ------------------------------------------------------------------
>
> Key: SM-1157
> URL: https://issues.apache.org/activemq/browse/SM-1157
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
> Reporter: Tammo van Lessen
> Fix For: 3.2.2, 3.3
>
> Attachments: jbi-maven-patch.txt
>
>
> When the m2 build is customized and a <finalname> is set (i.e. is different to ${artifactname}-${version}), the generated jbi.xml is wrong.
> I guess the problem is located in Line 207in GenerateComponentDescriptorMojo.java
> Should be something like project.getBuild().getFinalName()
> http://maven.apache.org/ref/current/maven-model/apidocs/org/apache/maven/model/BuildBase.html#getFinalName()
> http://maven.apache.org/ref/2.0.4/maven-project/apidocs/org/apache/maven/project/MavenProject.html#getBuild()
> Cheers,
> Tammo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1157) maven-jbi-plugin creates wrong classpath
entries in jbi.xml for SE
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated SM-1157:
--------------------------------
Fix Version/s: 3.3
3.2.2
> maven-jbi-plugin creates wrong classpath entries in jbi.xml for SE
> ------------------------------------------------------------------
>
> Key: SM-1157
> URL: https://issues.apache.org/activemq/browse/SM-1157
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
> Reporter: Tammo van Lessen
> Fix For: 3.2.2, 3.3
>
> Attachments: jbi-maven-patch.txt
>
>
> When the m2 build is customized and a <finalname> is set (i.e. is different to ${artifactname}-${version}), the generated jbi.xml is wrong.
> I guess the problem is located in Line 207in GenerateComponentDescriptorMojo.java
> Should be something like project.getBuild().getFinalName()
> http://maven.apache.org/ref/current/maven-model/apidocs/org/apache/maven/model/BuildBase.html#getFinalName()
> http://maven.apache.org/ref/2.0.4/maven-project/apidocs/org/apache/maven/project/MavenProject.html#getBuild()
> Cheers,
> Tammo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1157) maven-jbi-plugin creates wrong
classpath entries in jbi.xml for SE
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40796 ]
Tammo van Lessen commented on SM-1157:
--------------------------------------
In the meantime I've tested the patch, it works like a charm.
> maven-jbi-plugin creates wrong classpath entries in jbi.xml for SE
> ------------------------------------------------------------------
>
> Key: SM-1157
> URL: https://issues.apache.org/activemq/browse/SM-1157
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
> Reporter: Tammo van Lessen
> Attachments: jbi-maven-patch.txt
>
>
> When the m2 build is customized and a <finalname> is set (i.e. is different to ${artifactname}-${version}), the generated jbi.xml is wrong.
> I guess the problem is located in Line 207in GenerateComponentDescriptorMojo.java
> Should be something like project.getBuild().getFinalName()
> http://maven.apache.org/ref/current/maven-model/apidocs/org/apache/maven/model/BuildBase.html#getFinalName()
> http://maven.apache.org/ref/2.0.4/maven-project/apidocs/org/apache/maven/project/MavenProject.html#getBuild()
> Cheers,
> Tammo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1157) maven-jbi-plugin creates wrong classpath
entries in jbi.xml for SE
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen updated SM-1157:
---------------------------------
Attachment: jbi-maven-patch.txt
untested patch
> maven-jbi-plugin creates wrong classpath entries in jbi.xml for SE
> ------------------------------------------------------------------
>
> Key: SM-1157
> URL: https://issues.apache.org/activemq/browse/SM-1157
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
> Reporter: Tammo van Lessen
> Attachments: jbi-maven-patch.txt
>
>
> When the m2 build is customized and a <finalname> is set (i.e. is different to ${artifactname}-${version}), the generated jbi.xml is wrong.
> I guess the problem is located in Line 207in GenerateComponentDescriptorMojo.java
> Should be something like project.getBuild().getFinalName()
> http://maven.apache.org/ref/current/maven-model/apidocs/org/apache/maven/model/BuildBase.html#getFinalName()
> http://maven.apache.org/ref/2.0.4/maven-project/apidocs/org/apache/maven/project/MavenProject.html#getBuild()
> Cheers,
> Tammo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1157) maven-jbi-plugin creates wrong classpath
entries in jbi.xml for SE
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Snyder resolved SM-1157.
------------------------------
Resolution: Fixed
Committed to the 3.2 branch via [revision |http://svn.apache.org/viewvc?rev=614094&view=rev].
Committed to the trunk (3.3) via [via revision 614095|http://svn.apache.org/viewvc?rev=614095&view=rev].
> maven-jbi-plugin creates wrong classpath entries in jbi.xml for SE
> ------------------------------------------------------------------
>
> Key: SM-1157
> URL: https://issues.apache.org/activemq/browse/SM-1157
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
> Reporter: Tammo van Lessen
> Fix For: 3.2.2, 3.3
>
> Attachments: jbi-maven-patch.txt
>
>
> When the m2 build is customized and a <finalname> is set (i.e. is different to ${artifactname}-${version}), the generated jbi.xml is wrong.
> I guess the problem is located in Line 207in GenerateComponentDescriptorMojo.java
> Should be something like project.getBuild().getFinalName()
> http://maven.apache.org/ref/current/maven-model/apidocs/org/apache/maven/model/BuildBase.html#getFinalName()
> http://maven.apache.org/ref/2.0.4/maven-project/apidocs/org/apache/maven/project/MavenProject.html#getBuild()
> Cheers,
> Tammo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.