Welcome!

Welcome to the Official BlackBerry Support Community Forums. This is your resource to discuss support topics with your peers, and learn from each other. New to the forum? Please visit the ‘Getting Started’ link below.
inside custom component

Java Development

Reply
New Developer
myquestion
Posts: 187
Registered: ‎11-12-2008

BlackBerry Java Plug-in for Eclipse error while building the BlackBerry_App_Descriptor.xml

Hi ,

 

I am getting the following error in BlackBerry Java Plug-in for Eclipse while building a project , in BlackBerry_App_Descriptor.xml  ,please anyone provide me the solution.

 

Description    Resource    Path    Location    Type
InvalidRegex: Pattern value '([a-zA-Z_]{1,63}[\s-a-zA-Z_0-9.]{0,63}[;]?)*' is not a valid regular expression. The reported error was: ''-' is an invalid character range. Write '\-'.' at column '{2}'.    BlackBerry_App_Descriptor.xml    /umesh    Unknown    XML Problem 


Thanks

Please use plain text.
Developer
eicheled
Posts: 77
Registered: ‎04-01-2011
My Carrier: Rogers

Re: BlackBerry Java Plug-in for Eclipse error while building the BlackBerry_App_Descriptor.xml

I think it's caused by running Java 1.7 (I can't find a link for you right now, sorry). I had the same issue and resolved it by uninstalling the 1.7 Java JDK and going back to 1.6

 

 

Please use plain text.
Developer
eicheled
Posts: 77
Registered: ‎04-01-2011
My Carrier: Rogers

Re: BlackBerry Java Plug-in for Eclipse error while building the BlackBerry_App_Descriptor.xml

Please use plain text.
New Developer
ebaskoro
Posts: 27
Registered: ‎11-03-2009
My Carrier: XL

Re: BlackBerry Java Plug-in for Eclipse error while building the BlackBerry_App_Descriptor.xml

Please use plain text.
New Member
mbcrowder
Posts: 1
Registered: ‎09-20-2011
My Carrier: NA

Re: BlackBerry Java Plug-in for Eclipse error while building the BlackBerry_App_Descriptor.xml

So ... am I reading this right?  V1.7 was released, and there's a bug which prevents even the simplest Hello World app from loading.  The solution is to revert to 1.6?  How in the world did this simple of a bug make it to production?  This has (so far) been the buggiest device I've ever worked with.  Nothing but issues.

Please use plain text.