[JBoss JIRA] (JBIDE-14367) Add helloworls-rs quickstart to central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14367?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-14367.
---------------------------------
Fix Version/s: 4.1.0.Beta1
Resolution: Done
Fixed. Refresh Central to see the changes.
> Add helloworls-rs quickstart to central
> ---------------------------------------
>
> Key: JBIDE-14367
> URL: https://issues.jboss.org/browse/JBIDE-14367
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, project-examples
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Fix For: 4.1.0.Beta1
>
>
> jax-rs-client quickstart has helloworld-rs as prerequisite, but helloworld-rs is not present in project examples in JBT.
> I think it would make sense to add this quickstart to central, OR at least mention in jax-rs-client readme where could be helloworld-rs obtained from.
> WDYT?
--
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, 10 months
[JBoss JIRA] (JBIDE-14122) Add VJET to Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14122?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-14122.
-----------------------------------------
Resolution: Done
done for beta1 - new issues can be opened for Beta2.
> Add VJET to Central
> -------------------
>
> Key: JBIDE-14122
> URL: https://issues.jboss.org/browse/JBIDE-14122
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, target-platform
> Affects Versions: 4.1.0.Beta1
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Beta1
>
> Attachments: installing-vjet-from-jbt-mirrors.png, installing-vjet-from-jbt-mirrors2.png, installing-vjet-from-jbt-mirrors3-problem-with-junit4.png, installing-vjet-from-jbt-mirrors4-success.png, installing-vjet-from-jbt-mirrors5-problem-with-junit4-SOLVED.png, JBIDE14122-central-with-vjet.png
>
>
> We should provide an ability to install VJET v.0.10 through Central
> The latest stable VJET Update Site: [http://download.eclipse.org/vjet/updates-0.10] - v.0.10.0, Released
> The following dependencies (in addition to what we already have in TP) are to be satisfied in order to run VJet:
> {code:title=Orbit bundles for VJET}
> <unit id="org.apache.xml.serializer" version="2.7.1.v201005080400"/>
> <unit id="org.apache.xml.resolver" version="1.2.0.v201005080400"/>
> <unit id="org.apache.batik.css" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.css.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.xerces" version="2.9.0.v201101211617"/>
> <unit id="org.ccil.cowan.tagsoup" version="1.2.0.v201202211000"/>
> <unit id="org.w3c.css.sac" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.css.sac.source" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.dom.svg" version="1.1.0.v201011041433"/>
> <unit id="org.w3c.dom.svg.source" version="1.1.0.v201011041433"/>
> <unit id="javax.xml" version="1.3.4.v201005080400"/>
> <unit id="org.apache.commons.collections" version="3.2.0.v2013030210310"/>
> <unit id="org.apache.commons.io" version="2.0.1.v201105210651"/>
> {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, 10 months
[JBoss JIRA] (JBIDE-13840) Progress bar is running weird when downloading runtime
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13840?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13840:
----------------------------------------
Fix Version/s: 4.1.0.Beta2
(was: 4.1.0.Beta1)
> Progress bar is running weird when downloading runtime
> ------------------------------------------------------
>
> Key: JBIDE-13840
> URL: https://issues.jboss.org/browse/JBIDE-13840
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Petr Suchý
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.1.0.Beta2
>
>
> When I am downloading runtime, the progress is running to the ~half of the bar (in progress view) and then starts again from the beginning.
> [EDIT] This happened only when you run downloading in the background!
> Runtime is always successfully downloaded, the problem is only with the bar.
> Tried on MS Windows and Linux.
--
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, 10 months
[JBoss JIRA] (JBIDE-14122) Add VJET to Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14122?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-14122:
---------------------------------------------
we delivered Vjet in central for Beta1 - can we resolve this and then report remaining issues separate from this ?
> Add VJET to Central
> -------------------
>
> Key: JBIDE-14122
> URL: https://issues.jboss.org/browse/JBIDE-14122
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, target-platform
> Affects Versions: 4.1.0.Beta1
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Beta1
>
> Attachments: installing-vjet-from-jbt-mirrors.png, installing-vjet-from-jbt-mirrors2.png, installing-vjet-from-jbt-mirrors3-problem-with-junit4.png, installing-vjet-from-jbt-mirrors4-success.png, installing-vjet-from-jbt-mirrors5-problem-with-junit4-SOLVED.png, JBIDE14122-central-with-vjet.png
>
>
> We should provide an ability to install VJET v.0.10 through Central
> The latest stable VJET Update Site: [http://download.eclipse.org/vjet/updates-0.10] - v.0.10.0, Released
> The following dependencies (in addition to what we already have in TP) are to be satisfied in order to run VJet:
> {code:title=Orbit bundles for VJET}
> <unit id="org.apache.xml.serializer" version="2.7.1.v201005080400"/>
> <unit id="org.apache.xml.resolver" version="1.2.0.v201005080400"/>
> <unit id="org.apache.batik.css" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.css.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.xerces" version="2.9.0.v201101211617"/>
> <unit id="org.ccil.cowan.tagsoup" version="1.2.0.v201202211000"/>
> <unit id="org.w3c.css.sac" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.css.sac.source" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.dom.svg" version="1.1.0.v201011041433"/>
> <unit id="org.w3c.dom.svg.source" version="1.1.0.v201011041433"/>
> <unit id="javax.xml" version="1.3.4.v201005080400"/>
> <unit id="org.apache.commons.collections" version="3.2.0.v2013030210310"/>
> <unit id="org.apache.commons.io" version="2.0.1.v201105210651"/>
> {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, 10 months
[JBoss JIRA] (JBIDE-14122) Add VJET to Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14122?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14122:
----------------------------------------
Fix Version/s: 4.1.0.Beta1
(was: 4.1.0.Beta2)
> Add VJET to Central
> -------------------
>
> Key: JBIDE-14122
> URL: https://issues.jboss.org/browse/JBIDE-14122
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, target-platform
> Affects Versions: 4.1.0.Beta1
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Beta1
>
> Attachments: installing-vjet-from-jbt-mirrors.png, installing-vjet-from-jbt-mirrors2.png, installing-vjet-from-jbt-mirrors3-problem-with-junit4.png, installing-vjet-from-jbt-mirrors4-success.png, installing-vjet-from-jbt-mirrors5-problem-with-junit4-SOLVED.png, JBIDE14122-central-with-vjet.png
>
>
> We should provide an ability to install VJET v.0.10 through Central
> The latest stable VJET Update Site: [http://download.eclipse.org/vjet/updates-0.10] - v.0.10.0, Released
> The following dependencies (in addition to what we already have in TP) are to be satisfied in order to run VJet:
> {code:title=Orbit bundles for VJET}
> <unit id="org.apache.xml.serializer" version="2.7.1.v201005080400"/>
> <unit id="org.apache.xml.resolver" version="1.2.0.v201005080400"/>
> <unit id="org.apache.batik.css" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.css.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.xerces" version="2.9.0.v201101211617"/>
> <unit id="org.ccil.cowan.tagsoup" version="1.2.0.v201202211000"/>
> <unit id="org.w3c.css.sac" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.css.sac.source" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.dom.svg" version="1.1.0.v201011041433"/>
> <unit id="org.w3c.dom.svg.source" version="1.1.0.v201011041433"/>
> <unit id="javax.xml" version="1.3.4.v201005080400"/>
> <unit id="org.apache.commons.collections" version="3.2.0.v2013030210310"/>
> <unit id="org.apache.commons.io" version="2.0.1.v201105210651"/>
> {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, 10 months
[JBoss JIRA] (JBIDE-14122) Add VJET to Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14122?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-14122:
-------------------------------
Fix Version/s: 4.1.0.Beta2
(was: 4.1.0.Beta1)
> Add VJET to Central
> -------------------
>
> Key: JBIDE-14122
> URL: https://issues.jboss.org/browse/JBIDE-14122
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, target-platform
> Affects Versions: 4.1.0.Beta1
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Beta2
>
> Attachments: installing-vjet-from-jbt-mirrors.png, installing-vjet-from-jbt-mirrors2.png, installing-vjet-from-jbt-mirrors3-problem-with-junit4.png, installing-vjet-from-jbt-mirrors4-success.png, installing-vjet-from-jbt-mirrors5-problem-with-junit4-SOLVED.png, JBIDE14122-central-with-vjet.png
>
>
> We should provide an ability to install VJET v.0.10 through Central
> The latest stable VJET Update Site: [http://download.eclipse.org/vjet/updates-0.10] - v.0.10.0, Released
> The following dependencies (in addition to what we already have in TP) are to be satisfied in order to run VJet:
> {code:title=Orbit bundles for VJET}
> <unit id="org.apache.xml.serializer" version="2.7.1.v201005080400"/>
> <unit id="org.apache.xml.resolver" version="1.2.0.v201005080400"/>
> <unit id="org.apache.batik.css" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.css.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.dom.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util" version="1.7.0.v201011041433"/>
> <unit id="org.apache.batik.util.source" version="1.7.0.v201011041433"/>
> <unit id="org.apache.xerces" version="2.9.0.v201101211617"/>
> <unit id="org.ccil.cowan.tagsoup" version="1.2.0.v201202211000"/>
> <unit id="org.w3c.css.sac" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.css.sac.source" version="1.3.1.v200903091627"/>
> <unit id="org.w3c.dom.svg" version="1.1.0.v201011041433"/>
> <unit id="org.w3c.dom.svg.source" version="1.1.0.v201011041433"/>
> <unit id="javax.xml" version="1.3.4.v201005080400"/>
> <unit id="org.apache.commons.collections" version="3.2.0.v2013030210310"/>
> <unit id="org.apache.commons.io" version="2.0.1.v201105210651"/>
> {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, 10 months
[JBoss JIRA] (JBIDE-14653) Feature and plugins info is incorrect for Aerogear plugins
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14653?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14653:
----------------------------------------
Fix Version/s: 4.1.0.Beta2
(was: 4.1.0.Beta1)
> Feature and plugins info is incorrect for Aerogear plugins
> ----------------------------------------------------------
>
> Key: JBIDE-14653
> URL: https://issues.jboss.org/browse/JBIDE-14653
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: JBT 4.1.0.Beta1-v20130526-0812-B258
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Critical
> Labels: respin-b
> Fix For: 4.1.0.Beta2
>
> Attachments: aerogearfeature.png, aerogearplugins.png
>
>
> 1. Open Help > About Eclipse > Installation Details
> 2. Select Installed Software tab
> 3. Select either org.jboss.tools.aerogear.hybrid.feature.feature.group or org.jboss.tools.aerogear.hybrid.feature.source.feature.group
> ERROR: Feature description should contain "based mobile" instead "basedmobile"
> !aerogearfeature.png!
> 4. Select Plug-ins tab
> 5. Type aerogear ni filter
> ERROR: Aerogear plugins has neither provider or Plug-in name. Version of org.jboss.tools.aerogear.hybrid.cordova is 2.7.0 all the others plug-ins has version 1.0.0.Beta1... I don't know if this is correct
> !aerogearplugins.png!
--
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, 10 months
[JBoss JIRA] (JBIDE-14653) Feature and plugins info is incorrect for Aerogear plugins
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14653?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14653:
----------------------------------------
Labels: (was: respin-b)
> Feature and plugins info is incorrect for Aerogear plugins
> ----------------------------------------------------------
>
> Key: JBIDE-14653
> URL: https://issues.jboss.org/browse/JBIDE-14653
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: JBT 4.1.0.Beta1-v20130526-0812-B258
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
> Attachments: aerogearfeature.png, aerogearplugins.png
>
>
> 1. Open Help > About Eclipse > Installation Details
> 2. Select Installed Software tab
> 3. Select either org.jboss.tools.aerogear.hybrid.feature.feature.group or org.jboss.tools.aerogear.hybrid.feature.source.feature.group
> ERROR: Feature description should contain "based mobile" instead "basedmobile"
> !aerogearfeature.png!
> 4. Select Plug-ins tab
> 5. Type aerogear ni filter
> ERROR: Aerogear plugins has neither provider or Plug-in name. Version of org.jboss.tools.aerogear.hybrid.cordova is 2.7.0 all the others plug-ins has version 1.0.0.Beta1... I don't know if this is correct
> !aerogearplugins.png!
--
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, 10 months
[JBoss JIRA] (JBIDE-14555) Wrong warning "Could not initialize class my.pkg.ArchiveBuilder" by Arquillian
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14555?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14555:
----------------------------------------
Fix Version/s: (was: 4.1.0.Beta1)
> Wrong warning "Could not initialize class my.pkg.ArchiveBuilder" by Arquillian
> ------------------------------------------------------------------------------
>
> Key: JBIDE-14555
> URL: https://issues.jboss.org/browse/JBIDE-14555
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.0.Beta1
> Reporter: Juergen Zimmermann
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> I'm using JBoss Tools 41-Update-2013-05-19_01-13-51-B207 having the new Arquillian component.
> I'm getting a warning "Could not initialize class my.pkg.ArchiveBuilder" in all Arquillian-based test classes.
> In fact my ArchiveBuilder isn't a regular class, but it's an enum:
> public enum ArchiveBuilder {
> INSTANCE;
> private final WebArchive archive = ShrinkWrap.create(WebArchive.class, "shop.war");
> private ArchiveBuilder() {...}
> public static ArchiveBuilder getInstance() { return INSTANCE; }
> public Archive<? extends Archive<?>> getArchive() { return archive; }
--
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, 10 months