[JBoss JIRA] (JBIDE-15919) The API for installed plugins list is slow
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15919?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-15919:
---------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Issue Type: Bug (was: Feature Request)
> The API for installed plugins list is slow
> ------------------------------------------
>
> Key: JBIDE-15919
> URL: https://issues.jboss.org/browse/JBIDE-15919
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Gorkem Ercan
> Priority: Minor
> Fix For: 4.2.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.getInstalledPlugins() and org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.isPluginInstalled(String) is slow. It can be improved by more agressive caching and/or different ways to track installed plugins.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-14855) p2.mirrorsURL are kept in site metadata after mirroring with format attribute
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14855?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-14855.
------------------------------
Closing.
> p2.mirrorsURL are kept in site metadata after mirroring with format attribute
> -----------------------------------------------------------------------------
>
> Key: JBIDE-14855
> URL: https://issues.jboss.org/browse/JBIDE-14855
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
>
> When we mirror sites using the "format" argument (to keep the original repository layout with .pack.gz as siblings) it also keep the p2.mirrorsURL attribute. This is not bad per se, but since the mirrors are often not correctly sync'd with the Eclipse repositories/our mirrors, it leads to build failure.
> Current workaround is to remove them by end in content.jar and artifact.jar.
> We should think about removing this, for example as part of the remove-references script.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBDS-2393) remove all references to JBDS Extras site from within JBDS 7
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2393?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-2393.
----------------------------
Fix Version/s: 7.1.0.CR1
(was: 7.1.x)
Resolution: Out of Date
None of the files listed in the issue description are still relevant for JBDS 7.
> remove all references to JBDS Extras site from within JBDS 7
> ------------------------------------------------------------
>
> Key: JBDS-2393
> URL: https://issues.jboss.org/browse/JBDS-2393
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, updatesite
> Affects Versions: 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 7.1.0.CR1
>
>
> The following files in devstudio svn trunk need to be revised to no longer reference an extras/ site, if in fact we're going to obsolete it in favour of the Central composite site.
> {quote}
> ./documentation/Release_Guide/2012_Release_JBDS_Staging_For_QE.txt
> ./devstudio.jboss.com/updates/6.0/central/core/compositeArtifacts.xml
> ./devstudio.jboss.com/updates/6.0/central/core/compositeContent.xml
> ./devstudio.jboss.com/updates/6.0-staging/central/core/compositeArtifacts.xml
> ./devstudio.jboss.com/updates/6.0-staging/central/core/compositeContent.xml
> ./devstudio.jboss.com/updates/6.0-staging/updatesites.xml
> ./devstudio.jboss.com/updates/6.0-staging/index.html
> ./devstudio.jboss.com/updates/6.0/index.html
> ./devstudio.jboss.com/updates/6.0/updatesites.xml
> ./product/features/com.jboss.jbds.product.feature.source/feature.xml
> ./product/site/associate.properties
> ./extras/site/associate.properties
> ./techpreview/features/com.jboss.jbds.byoe.feature/feature.xml
> ./techpreview/site/associate.properties
> ./product-soa/site/associate.properties
> ./qa/install-extras/jbds.properties
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15892) Weird code in JBT installation script: install.sh
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15892?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-15892.
------------------------------
Resolution: Duplicate Issue
Links updated.
https://www.jboss.org/tools/download/installation/update_4_1#fromscript
Closing as dupe of JBIDE-15891
> Weird code in JBT installation script: install.sh
> --------------------------------------------------
>
> Key: JBIDE-15892
> URL: https://issues.jboss.org/browse/JBIDE-15892
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.1.1.Beta1
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.1.1.CR1
>
> Attachments: JBIDE15892.png
>
>
> install.sh contains some weird hardcoded stuff. you can download the script from offcial pages: http://www.jboss.org/tools/download/installation/update_4_1.html#fromscript
> [~nickboldt] can you explain how is it meant to be used?
> I don't think it is very straight forward for the user.
> {code}
> #!/bin/bash
> # install all of JBT into Eclipse Standard bundle
> target=${HOME}/eclipse/eclipse43; cd ${target}; rm -fr ${target}/eclipse
> tar xzf /tmp/eclipse-standard-kepler-R-linux-gtk-x86_64.tar.gz
> ${target}/eclipse/eclipse -consolelog -nosplash -data /tmp -application org.eclipse.ant.core.antRunner -f \
> install.xml \
> -DsourceZip=/tmp/jbosstools-Update-4.1.0.Final_2013-07-19_19-47-52-B380.zip \
> -DotherRepos=http://download.jboss.org/jbosstools/updates/stable/kepler/central/core/ \
> -DtargetDir=${target}/eclipse/
> # [p2.dir] Installing org.hibernate.eclipse.feature.source.feature.group 3.7.0.Final-v20130717-0715-B84.
> # ...
> # [p2.dir] Installing org.mozilla.xulrunner.feature.feature.group 1.9.218.Final-v20121126-2356-B155.
> # [p2.dir] Operation completed in 212518 ms.
> # install JBT Central, including Subclipse w/ SVNKit into Eclipse JEE bundle
> target=${HOME}/eclipse/eclipse43; cd ${target}; rm -fr ${target}/eclipse
> tar xzf /tmp/eclipse-jee-kepler-R-linux-gtk-x86_64.tar.gz
> ${target}/eclipse/eclipse -consolelog -nosplash -data /tmp -application org.eclipse.ant.core.antRunner -f \
> install.xml \
> -DsourceZip=/tmp/jbosstools-Update-4.1.0.Final_2013-07-19_19-47-52-B380.zip \
> -DotherRepos=http://download.jboss.org/jbosstools/updates/stable/kepler/central/core/ \
> -DtargetDir=${target}/eclipse/
> -Dinstall="org.jboss.tools.community.central.feature.feature.group,\
> org.tigris.subversion.subclipse.feature.group,\
> org.tigris.subversion.clientadapter.svnkit.feature.feature.group,\
> com.collabnet.subversion.merge.feature.feature.group,\
> net.java.dev.jna.feature.group,\
> org.tigris.subversion.clientadapter.feature.feature.group,\
> org.tigris.subversion.subclipse.graph.feature.feature.group,\
> org.tmatesoft.svnkit.feature.group"
> # [p2.dir] Installing org.jboss.tools.community.central.feature.feature.group 1.2.0.Final-v20130719-2050-B70.
> # [p2.dir] Installing org.tigris.subversion.subclipse.feature.group 1.8.20.
> # [p2.dir] Installing org.tigris.subversion.clientadapter.svnkit.feature.feature.group 1.7.9.1.
> # ...
> # [p2.dir] Operation completed in 55635 ms.
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15919) The API for installed plugins list is slow
by Gorkem Ercan (JIRA)
Gorkem Ercan created JBIDE-15919:
------------------------------------
Summary: The API for installed plugins list is slow
Key: JBIDE-15919
URL: https://issues.jboss.org/browse/JBIDE-15919
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: aerogear-hybrid
Affects Versions: 4.1.1.Beta1
Reporter: Gorkem Ercan
Priority: Minor
Fix For: 4.2.x
org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.getInstalledPlugins() and org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.isPluginInstalled(String) is slow. It can be improved by more agressive caching and/or different ways to track installed plugins.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15918) Could Jenkins perform tagging of its own repo?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15918?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15918:
-------------------------------
Description:
[~maxandersen] said:
{quote}
Project leads, please tag your projects!
{code}
co jbosstools-4.1.1.Beta1x
git tag jbosstools-4.1.1.Beta1
git push origin jbosstools-4.1.1.Beta1
{code}
{quote}
Then asked:
{quote}
Really would be nice if jenkins could just make such tags in its own repository and we could move the exact commit over from the "build" repository to the master repository.
{quote}
was:
[~maxandersen] asked:
{quote}
{quote}
Project leads, please tag your projects!
{code}
co jbosstools-4.1.1.Beta1x
git tag jbosstools-4.1.1.Beta1
git push origin jbosstools-4.1.1.Beta1
{code}
{quote}
Really would be nice if jenkins could just make such tags in its own repository and we could move the exact commit over from the "build" repository to the master repository.
{quote}
> Could Jenkins perform tagging of its own repo?
> ----------------------------------------------
>
> Key: JBIDE-15918
> URL: https://issues.jboss.org/browse/JBIDE-15918
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Priority: Minor
>
> [~maxandersen] said:
> {quote}
> Project leads, please tag your projects!
> {code}
> co jbosstools-4.1.1.Beta1x
> git tag jbosstools-4.1.1.Beta1
> git push origin jbosstools-4.1.1.Beta1
> {code}
> {quote}
> Then asked:
> {quote}
> Really would be nice if jenkins could just make such tags in its own repository and we could move the exact commit over from the "build" repository to the master repository.
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15918) Could Jenkins perform tagging of its own repo?
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15918:
----------------------------------
Summary: Could Jenkins perform tagging of its own repo?
Key: JBIDE-15918
URL: https://issues.jboss.org/browse/JBIDE-15918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.1.1.Beta1
Reporter: Nick Boldt
Priority: Minor
[~maxandersen] asked:
{quote}
{quote}
Project leads, please tag your projects!
{code}
co jbosstools-4.1.1.Beta1x
git tag jbosstools-4.1.1.Beta1
git push origin jbosstools-4.1.1.Beta1
{code}
{quote}
Really would be nice if jenkins could just make such tags in its own repository and we could move the exact commit over from the "build" repository to the master repository.
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months