cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Heinemann (JIRA)" <>
Subject [jira] [Commented] (CXF-4375) Archetypes are broken
Date Wed, 13 Jun 2012 17:01:44 GMT


Lars Heinemann commented on CXF-4375:

Hi Glen,

the ## lines do mostly contain license stuff. I only wrote "this is a sample comment line"
as symbol here.
Currently trying to fix that issue so I can deliver a patch to you. The comments are easily
removed but the other
issue with the property placeholders is more complicated as you use resource filtering for
having always the current
cxf release version in one dependency (${project.version}).
If you for example try to generate a module out of one of the two archetypes from the shell
specifying the artifactId, groupId and version
of the new module then you will recognize that those values don't get included in the generated
pom. It will still say $artifactId etc.
You also can't correct the notation to ${artifactId} for example as it will otherwise replace
those in the archetype resources pom and so you 
have again the wrong data in the pom.

I am currently trying to create a patch for that. Will attach it here when finished.

> Archetypes are broken
> ---------------------
>                 Key: CXF-4375
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.6.1
>            Reporter: Lars Heinemann
>            Assignee: Glen Mazza
>              Labels: archetype, cxf
> The archetypes for cxf-jaxrs-service and cxf-jaxws-javafirst are broken. Some of the
contained xml files (not only the pom.xml) are invalid as they contain comment lines like

> {noformat}
> ## this is a sample comment line
> {noformat}
> which are not surrounded by a xml comment tag and also the notation of property placeholders
in the pom files are sometimes written in a wrong way. ( for example: $version instead of
${version} )

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


View raw message