[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636776#action_12636776
 ] 

Ted Kirby commented on GERONIMODEVTOOLS-522:
--------------------------------------------

Thanks for bug report.  I fixed it in trunk with rev 701571.  We would like to 
work better in p2, and have had some issues with it.

I don't know if we will do a 2.1.4.  Currently trunk is targeted to 2.2.

I wonder if we could or should fix this in 2.1.3 and put new artifacts on our 
eclipse plugin update site?

> Feature.properties has a trailing backslash in it
> -------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-522
>                 URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-522
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 2.1.3
>            Reporter: Charles Overbeck
>            Assignee: Tim McConnell
>
> The feature.properties on the update site bundled with 
> org.apache.geronimo.v21.feature_2.1.3.jar has a trailing backslash in it. The 
> last two lines of the file are this:
> trial in any resulting litigation. \n\
> \n\ 
> Note the trailing slash at the end of the second line; no characters follow 
> it. This may not sound like a terrible bug on its own, but because that 
> content ends up getting expanded inside the feature.xml, I think it escapes 
> the next character in the feature.xml, which in this case is the "<" which 
> closes a tag. This leads to an incorrectly generated content.xml file if you 
> are generating an update site using Eclipse's P2 metadata generator, and you 
> have the Geronimo feature present when you are doing the metadata generation. 
> I don't know if it has any other side-effects.
> In any case, that's why I'm proposing a priority of Major for this seeming 
> trivial bug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to