You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Cedric Bompart (JIRA)" <ji...@apache.org> on 2007/02/08 14:41:02 UTC
[jira] Created: (SM-835) archtype
servicemix-lwcontainer-service-unit - invalid classpath section in
servicemix.xml
archtype servicemix-lwcontainer-service-unit - invalid classpath section in servicemix.xml
------------------------------------------------------------------------------------------
Key: SM-835
URL: https://issues.apache.org/activemq/browse/SM-835
Project: ServiceMix
Issue Type: Bug
Components: tooling
Affects Versions: 3.1
Reporter: Cedric Bompart
The Maven2 archtype "servicemix-lwcontainer-service-unit" is producing an invalid servicemix.xml file which can be resolved by removing the classpath section:
<classpath>
<location>.</location>
</classpath>
The problem was; that Servicemix 3.1 didn't find the provided libraries from the SU project.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-835) achetypes should not contain the
tag inside the spring files
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved SM-835.
--------------------------------
Resolution: Fixed
URL: http://svn.apache.org/viewvc?view=rev&rev=507664
URL: http://svn.apache.org/viewvc?view=rev&rev=507665
Modified:
incubator/servicemix/branches/servicemix-3.1/archetypes/servicemix-jms-provider-service-unit/src/main/resources/archetype-resources/src/main/resources/xbean.xml
incubator/servicemix/branches/servicemix-3.1/archetypes/servicemix-jsr181-annotated-service-unit/src/main/resources/archetype-resources/src/main/resources/xbean.xml
incubator/servicemix/branches/servicemix-3.1/archetypes/servicemix-jsr181-wsdl-first-service-unit/src/main/resources/archetype-resources/src/main/resources/xbean.xml
incubator/servicemix/branches/servicemix-3.1/archetypes/servicemix-lwcontainer-service-unit/src/main/resources/archetype-resources/src/main/resources/servicemix.xml
> achetypes should not contain the <classpath/> tag inside the spring files
> -------------------------------------------------------------------------
>
> Key: SM-835
> URL: https://issues.apache.org/activemq/browse/SM-835
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
> Affects Versions: 3.1
> Reporter: Cedric Bompart
> Assigned To: Guillaume Nodet
> Fix For: 3.1.1, 3.2
>
>
> The Maven2 archtype "servicemix-lwcontainer-service-unit" is producing an invalid servicemix.xml file which can be resolved by removing the classpath section:
> <classpath>
> <location>.</location>
> </classpath>
> The problem was; that Servicemix 3.1 didn't find the provided libraries from the SU project.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-835) achetypes should not contain the
tag inside the spring files
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated SM-835:
-------------------------------
Fix Version/s: 3.2
3.1.1
Assignee: Guillaume Nodet
Summary: achetypes should not contain the <classpath/> tag inside the spring files (was: archtype servicemix-lwcontainer-service-unit - invalid classpath section in servicemix.xml)
> achetypes should not contain the <classpath/> tag inside the spring files
> -------------------------------------------------------------------------
>
> Key: SM-835
> URL: https://issues.apache.org/activemq/browse/SM-835
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
> Affects Versions: 3.1
> Reporter: Cedric Bompart
> Assigned To: Guillaume Nodet
> Fix For: 3.1.1, 3.2
>
>
> The Maven2 archtype "servicemix-lwcontainer-service-unit" is producing an invalid servicemix.xml file which can be resolved by removing the classpath section:
> <classpath>
> <location>.</location>
> </classpath>
> The problem was; that Servicemix 3.1 didn't find the provided libraries from the SU project.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.