[JBoss JIRA] (JBIDE-15768) Can't add Blackberry plug-ins listed in Cordova Discovery Wizard
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15768?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-15768:
---------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Fix Version/s: 4.2.0.Beta2
(was: LATER)
Assignee: Gorkem Ercan
> Can't add Blackberry plug-ins listed in Cordova Discovery Wizard
> ----------------------------------------------------------------
>
> Key: JBIDE-15768
> URL: https://issues.jboss.org/browse/JBIDE-15768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Michelle Murray
> Assignee: Gorkem Ercan
> Fix For: 4.2.0.Beta2
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Errors or no action when try to add blackberry items in Cordova Plugin Discovery wizard.
> In Cordova Configuration Editor, Platform Properties mode:
> 1. Click Add for first features table (opens Cordova Plugin Discovery window)
> 2. Select check box for blackberry item (e.g., com.blackberry.pim.contacts)
> 3. Click Next
> 4. Click Finish
> > Nothing happens
> Command line shows:
> {noformat}
> [Fatal Error] plugin.xml:46:25: The prefix "rim" for element "rim:permit" is not bound.
> java.lang.reflect.InvocationTargetException
> at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:121)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Caused by: org.eclipse.core.runtime.CoreException: Parsing error /home/mmurray/.plugman/cache/com.blackberry.pim.contacts/1.0.0/package/plugin.xml
> at org.jboss.tools.aerogear.hybrid.core.util.XMLUtil.loadXML(XMLUtil.java:63)
> at org.jboss.tools.aerogear.hybrid.core.util.XMLUtil.loadXML(XMLUtil.java:48)
> at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.installPlugin(CordovaPluginManager.java:108)
> at org.jboss.tools.aerogear.hybrid.ui.plugins.internal.CordovaPluginWizard$PluginInstallOperation.execute(CordovaPluginWizard.java:124)
> at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
> ... 1 more
> Caused by: org.xml.sax.SAXParseException; systemId: file:/home/mmurray/.plugman/cache/com.blackberry.pim.contacts/1.0.0/package/plugin.xml; lineNumber: 46; columnNumber: 25; The prefix "rim" for element "rim:permit" is not bound.
> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
> at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:205)
> at org.jboss.tools.aerogear.hybrid.core.util.XMLUtil.loadXML(XMLUtil.java:58)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-15768) Can't add Blackberry plug-ins listed in Cordova Discovery Wizard
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15768?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15768:
--------------------------------------
Most plugins do not add the necessary information that would enable us to detect supported platforms and cordova registry does not force plugins in that direction. Hence, I have implemented an informative message that explains the possible failure reasons.
The new message box is on the master to be released to Beta2
> Can't add Blackberry plug-ins listed in Cordova Discovery Wizard
> ----------------------------------------------------------------
>
> Key: JBIDE-15768
> URL: https://issues.jboss.org/browse/JBIDE-15768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Michelle Murray
> Assignee: Gorkem Ercan
> Fix For: 4.2.0.Beta2
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Errors or no action when try to add blackberry items in Cordova Plugin Discovery wizard.
> In Cordova Configuration Editor, Platform Properties mode:
> 1. Click Add for first features table (opens Cordova Plugin Discovery window)
> 2. Select check box for blackberry item (e.g., com.blackberry.pim.contacts)
> 3. Click Next
> 4. Click Finish
> > Nothing happens
> Command line shows:
> {noformat}
> [Fatal Error] plugin.xml:46:25: The prefix "rim" for element "rim:permit" is not bound.
> java.lang.reflect.InvocationTargetException
> at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:121)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Caused by: org.eclipse.core.runtime.CoreException: Parsing error /home/mmurray/.plugman/cache/com.blackberry.pim.contacts/1.0.0/package/plugin.xml
> at org.jboss.tools.aerogear.hybrid.core.util.XMLUtil.loadXML(XMLUtil.java:63)
> at org.jboss.tools.aerogear.hybrid.core.util.XMLUtil.loadXML(XMLUtil.java:48)
> at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.installPlugin(CordovaPluginManager.java:108)
> at org.jboss.tools.aerogear.hybrid.ui.plugins.internal.CordovaPluginWizard$PluginInstallOperation.execute(CordovaPluginWizard.java:124)
> at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
> ... 1 more
> Caused by: org.xml.sax.SAXParseException; systemId: file:/home/mmurray/.plugman/cache/com.blackberry.pim.contacts/1.0.0/package/plugin.xml; lineNumber: 46; columnNumber: 25; The prefix "rim" for element "rim:permit" is not bound.
> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
> at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:205)
> at org.jboss.tools.aerogear.hybrid.core.util.XMLUtil.loadXML(XMLUtil.java:58)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17117) Simplify publish process
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17117?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-17117:
------------------------------------
See also JBIDE-13835
> Simplify publish process
> ------------------------
>
> Key: JBIDE-17117
> URL: https://issues.jboss.org/browse/JBIDE-17117
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> We could work on improving the publishing process. Some ideas:
> * Why do we rename the files we pull on sf.net. Also, renaming files could happen on sf.net.
> * Files from sf.net could be fetch after (for example in parallel with creating marketplace entry)
> * webtools should be published in a similar way as other parts (moved to tools/static/releases and then referenced in the composite file)
> * Replace the .core, .webtools, .hibernatetools, .coretests suffix by actual URL segments, so one would only have to move a single folder instead of 4 ones.
> * Identify things that can be done in parallel.
> * ...
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17117) Simplify publish process
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17117?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-17117:
------------------------------------
I wish sf.net was secondary, but we have a lot of zip downloads. I've tried to convince Max to drop the need for the Hibernate Tools zip, but it continues to be a popular download so we continue to provide it.
THAT SAID... now that we have Akamai caching, we could look at caching files in /static instead of pushing files to SF.net at all.
Might be worth doing some perf tests as both places provide geo-located mirroring to improve dl speeds. If we didn't need to bother pushing bits to sf.net, then ALL our bits would live on download.jboss.org (or access.redhat.com, for JBDS) and that would certainly make the publishing process simpler.
----
Re: renaming for sf.net: That's so that the files are consistently named with the same qualifiers
Re: doing something at the same time as the marketplace entry: yes, I usually kick off the various scp/sftp/rsync processes in the background, then do the more manual steps in the foreground. The older versions of the release guides even stated "while the above is running..." to further drive home the difference between long-running background tasks and hands-on foreground tasks. Wherever possible I've tried to document that in the guide but there are other things we can do/simplify to allow even more parallel steps.
Re: JBossTools-version.suffix/ folders vs. jbosstools-version/suffix/ folders, yes, we could switch to that model (note the change to lowercase too, to make [~maxandersen] happy re: JBIDE-16871).
---
Re: webtools site:
As I keep saying in other places, webtools CANNOT BE REFERENCED as a composite. It doesn't work because the server adapter wizard uses Eclipse Update, not p2. So... composite sites don't work. Or they didn't the last time I tried to change over to a composite. Maybe that's fixed now in Luna. Feel free to open a JIRA on that, and if it's NOT fixed in upstream, open a bugzilla to get it fixed there (most likely won't be seen until Eclipse 4.5 ( Mars ) development starts in summer 2014.
Past JIRAs:
https://issues.jboss.org/browse/JBIDE-8460 - WTP 3.2 Helios
https://issues.jboss.org/browse/JBIDE-9851 - WTP 3.3 Indigo
https://issues.jboss.org/browse/JBIDE-10469 - WTP 3.4 Juno - https://bugs.eclipse.org/bugs/show_bug.cgi?id=373319 - Proof a composite didn't work: https://issues.jboss.org/browse/JBIDE-10469?focusedCommentId=12672513&pag...
?? - WTP 3.5 Kepler *can't find the JIRA*
https://issues.jboss.org/browse/JBIDE-16311 - WTP 3.6 Luna
> Simplify publish process
> ------------------------
>
> Key: JBIDE-17117
> URL: https://issues.jboss.org/browse/JBIDE-17117
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> We could work on improving the publishing process. Some ideas:
> * Why do we rename the files we pull on sf.net. Also, renaming files could happen on sf.net.
> * Files from sf.net could be fetch after (for example in parallel with creating marketplace entry)
> * webtools should be published in a similar way as other parts (moved to tools/static/releases and then referenced in the composite file)
> * Replace the .core, .webtools, .hibernatetools, .coretests suffix by actual URL segments, so one would only have to move a single folder instead of 4 ones.
> * Identify things that can be done in parallel.
> * ...
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17002) Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17002?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-17002 at 5/1/14 9:21 PM:
------------------------------------------------------------
Because it was determined that having to rebuild the whole Central target platform for this tiny add-on was a bit of overhead we didn't want to incur. Also, it would have potentially exposed these features to JBDS users, and this patch was deemed to be required for JBT users ONLY.
So the options at the time were:
a) spawn a different Central TP for JBT vs. for JBDS (today they're the same)
b) keep the new connector's update site separate from the JBT/JBDS Central TP site
Option b was considerably less effort to do while I was on PTO, so we went with that. :)
Functionally speaking, the effect for end-users is identical, but it was way less maintenance & build-churn & commits to do it the simpler way.
was (Author: nickboldt):
Because it was determined that having to rebuild the whole Central target platform for this tiny add-on was a bit of overhead we didn't want to incur. Also, it would have potentially exposed these features to JBDS users, and this patch was deemed to be required for JBT users ONLY.
So the options at the time were:
a) spawn a different Central TP for JBT vs. for JBDS (today they're the same)
b) keep the new connector's update site separate from the JBT/JBDS Central TP site
> Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2
> -----------------------------------------------------------
>
> Key: JBIDE-17002
> URL: https://issues.jboss.org/browse/JBIDE-17002
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.1.2.Final
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Fix For: 4.1.2.Final
>
> Attachments: java-8-in-kepler-central-site.png, java-8-in-kepler-central-site2.png, jbide17002-3-4-features.png, jbide17002-6-7-features.png, jbide17002-patch-catg.png
>
>
> We decided to provide an easy way for JBT users to install Java 8 support in Eclipse Kepler SR2 in 1 click, instead of have to chase the update sites for JDT, M2e and WTP.
> * JDT Feature patch : http://download.eclipse.org/eclipse/updates/4.3-P-builds/
> * M2E 1.4.1 (org.eclipse.m2e.feature) http://download.eclipse.org/technology/m2e/releases/1.4/1.4.1.20140328-1905
> * WTP Feature Patch : http://download.eclipse.org/webtools/patches/drops/R3.5.2/P-3.5.2-2014032...
> All 3 features should be available via a unique connector in JBoss Central > Software Updates
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-16220) create an all-in-one build for JBT projects, using submodules
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16220?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16220:
------------------------------------
Last time I played with this approach to building everything in one place was December, apparently.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-submodule...
> create an all-in-one build for JBT projects, using submodules
> -------------------------------------------------------------
>
> Key: JBIDE-16220
> URL: https://issues.jboss.org/browse/JBIDE-16220
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 4.2.x
>
> Attachments: buildlog_maven311.txt
>
>
> Git 1.8.2 includes an option to have submodules track a branch tip, rather than specific commit IDs.
> {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188}
> "git submodule" started learning a new mode to integrate with the
> tip of the remote branch (as opposed to integrating with the commit
> recorded in the superproject's gitlink).
> {code}
> Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current.
> If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months