[JBoss JIRA] (TOOLSDOC-340) Review: All to review Beta1 Release Notes
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-340?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-340:
-------------------------------------
Attachment: Red_Hat_JBoss_Developer_Studio-7.0-Release_Notes_7.0.0-en-US.pdf
> Review: All to review Beta1 Release Notes
> -----------------------------------------
>
> Key: TOOLSDOC-340
> URL: https://issues.jboss.org/browse/TOOLSDOC-340
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Components: Release Notes
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
> Attachments: Red_Hat_JBoss_Developer_Studio-7.0-Release_Notes_7.0.0-en-US.pdf
>
>
> *Please review* the Beta1 Release Notes document:
> 1) Are new features correctly documented?
> 2) Are there any new features that are missing?
> 3) Are there any JIRAs for resolved and unresolved bugs missing? Queries used were: Resolved = https://issues.jboss.org/issues/?filter=12319302 and Unresolved = https://issues.jboss.org/issues/?filter=12319301
> *Please give feedback* as comments in this JIRA, to assist tracking. The doc is available here as a pdf. Alternatively, the doc is also available on other formats at http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos...
> *To make this document better*, we could do with culling the list of JIRAs down to those that need to be included in release notes. This requires someone to go through the JIRA list manually and set the 'Affects' field to 'Release Notes'. This task will have to be done for GA release notes anyway.
> Just for info:
> *Note sure if the JIRA needs a release note?*
> A JIRA needs a release note if:
> a) the JIRA was reported by GSS
> b) the JIRA was reported or commented on by a potential user (so someone outside of Red Hat)
> d) the JIRA fixes a bug that users would have encountered or been aware of
> c) the JIRA fix may surprise users (in a good or bad way)
> e) the JIRA documents a bug in a third-party product that impacts the ability to fix JBDS (e.g. pushed patch to Eclipse & waiting on Eclipse release)
> A JIRA does not need a release note if:
> a) the JIRA fixes a bug that occurred from an internal build
> b) the JIRA fixes a bug that users would not have been aware of
> c) the JIRA was just part of a developer's to-do-list
--
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, 11 months
[JBoss JIRA] (TOOLSDOC-340) Review: All to review Beta1 Release Notes
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-340:
----------------------------------------
Summary: Review: All to review Beta1 Release Notes
Key: TOOLSDOC-340
URL: https://issues.jboss.org/browse/TOOLSDOC-340
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Task
Components: Release Notes
Affects Versions: 4.1.0
Reporter: Michelle Murray
Assignee: Michelle Murray
Fix For: 4.1.0
*Please review* the Beta1 Release Notes document:
1) Are new features correctly documented?
2) Are there any new features that are missing?
3) Are there any JIRAs for resolved and unresolved bugs missing? Queries used were: Resolved = https://issues.jboss.org/issues/?filter=12319302 and Unresolved = https://issues.jboss.org/issues/?filter=12319301
*Please give feedback* as comments in this JIRA, to assist tracking.
The doc is available here as a pdf. Alternatively, the doc is also available on other formats at http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos...
*To make this document better*, we could do with culling the list of JIRAs down to those that need to be included in release notes. This requires someone to go through the JIRA list manually and set the 'Affects' field to 'Release Notes'. This task will have to be done for GA release notes anyway.
Just for info:
*Note sure if the JIRA needs a release note?*
A JIRA needs a release note if:
a) the JIRA was reported by GSS
b) the JIRA was reported or commented on by a potential user (so someone outside of Red Hat)
d) the JIRA fixes a bug that users would have encountered or been aware of
c) the JIRA fix may surprise users (in a good or bad way)
e) the JIRA documents a bug in a third-party product that impacts the ability to fix JBDS (e.g. pushed patch to Eclipse & waiting on Eclipse release)
A JIRA does not need a release note if:
a) the JIRA fixes a bug that occurred from an internal build
b) the JIRA fixes a bug that users would not have been aware of
c) the JIRA was just part of a developer's to-do-list
--
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, 11 months
[JBoss JIRA] (TOOLSDOC-340) Review: All to review Beta1 Release Notes
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-340?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-340:
-------------------------------------
Description:
*Please review* the Beta1 Release Notes document:
1) Are new features correctly documented?
2) Are there any new features that are missing?
3) Are there any JIRAs for resolved and unresolved bugs missing? Queries used were: Resolved = https://issues.jboss.org/issues/?filter=12319302 and Unresolved = https://issues.jboss.org/issues/?filter=12319301
*Please give feedback* as comments in this JIRA, to assist tracking. The doc is available here as a pdf. Alternatively, the doc is also available on other formats at http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos...
*To make this document better*, we could do with culling the list of JIRAs down to those that need to be included in release notes. This requires someone to go through the JIRA list manually and set the 'Affects' field to 'Release Notes'. This task will have to be done for GA release notes anyway.
Just for info:
*Note sure if the JIRA needs a release note?*
A JIRA needs a release note if:
a) the JIRA was reported by GSS
b) the JIRA was reported or commented on by a potential user (so someone outside of Red Hat)
d) the JIRA fixes a bug that users would have encountered or been aware of
c) the JIRA fix may surprise users (in a good or bad way)
e) the JIRA documents a bug in a third-party product that impacts the ability to fix JBDS (e.g. pushed patch to Eclipse & waiting on Eclipse release)
A JIRA does not need a release note if:
a) the JIRA fixes a bug that occurred from an internal build
b) the JIRA fixes a bug that users would not have been aware of
c) the JIRA was just part of a developer's to-do-list
was:
*Please review* the Beta1 Release Notes document:
1) Are new features correctly documented?
2) Are there any new features that are missing?
3) Are there any JIRAs for resolved and unresolved bugs missing? Queries used were: Resolved = https://issues.jboss.org/issues/?filter=12319302 and Unresolved = https://issues.jboss.org/issues/?filter=12319301
*Please give feedback* as comments in this JIRA, to assist tracking.
The doc is available here as a pdf. Alternatively, the doc is also available on other formats at http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos...
*To make this document better*, we could do with culling the list of JIRAs down to those that need to be included in release notes. This requires someone to go through the JIRA list manually and set the 'Affects' field to 'Release Notes'. This task will have to be done for GA release notes anyway.
Just for info:
*Note sure if the JIRA needs a release note?*
A JIRA needs a release note if:
a) the JIRA was reported by GSS
b) the JIRA was reported or commented on by a potential user (so someone outside of Red Hat)
d) the JIRA fixes a bug that users would have encountered or been aware of
c) the JIRA fix may surprise users (in a good or bad way)
e) the JIRA documents a bug in a third-party product that impacts the ability to fix JBDS (e.g. pushed patch to Eclipse & waiting on Eclipse release)
A JIRA does not need a release note if:
a) the JIRA fixes a bug that occurred from an internal build
b) the JIRA fixes a bug that users would not have been aware of
c) the JIRA was just part of a developer's to-do-list
> Review: All to review Beta1 Release Notes
> -----------------------------------------
>
> Key: TOOLSDOC-340
> URL: https://issues.jboss.org/browse/TOOLSDOC-340
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Components: Release Notes
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
>
> *Please review* the Beta1 Release Notes document:
> 1) Are new features correctly documented?
> 2) Are there any new features that are missing?
> 3) Are there any JIRAs for resolved and unresolved bugs missing? Queries used were: Resolved = https://issues.jboss.org/issues/?filter=12319302 and Unresolved = https://issues.jboss.org/issues/?filter=12319301
> *Please give feedback* as comments in this JIRA, to assist tracking. The doc is available here as a pdf. Alternatively, the doc is also available on other formats at http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos...
> *To make this document better*, we could do with culling the list of JIRAs down to those that need to be included in release notes. This requires someone to go through the JIRA list manually and set the 'Affects' field to 'Release Notes'. This task will have to be done for GA release notes anyway.
> Just for info:
> *Note sure if the JIRA needs a release note?*
> A JIRA needs a release note if:
> a) the JIRA was reported by GSS
> b) the JIRA was reported or commented on by a potential user (so someone outside of Red Hat)
> d) the JIRA fixes a bug that users would have encountered or been aware of
> c) the JIRA fix may surprise users (in a good or bad way)
> e) the JIRA documents a bug in a third-party product that impacts the ability to fix JBDS (e.g. pushed patch to Eclipse & waiting on Eclipse release)
> A JIRA does not need a release note if:
> a) the JIRA fixes a bug that occurred from an internal build
> b) the JIRA fixes a bug that users would not have been aware of
> c) the JIRA was just part of a developer's to-do-list
--
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, 11 months
[JBoss JIRA] (JBDS-2456) JBDS should be buildable from source zip
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2456?page=com.atlassian.jira.plugin.... ]
Michelle Murray edited comment on JBDS-2456 at 5/27/13 8:18 PM:
----------------------------------------------------------------
[~nickboldt], downloaded the 7.0.0.Beta1-v20130526-0839-B241 source zip. I unzipped it and ran mvn install, with outcome:
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 40:35.326s
[INFO] Finished at: Tue May 28 09:48:10 EST 2013
[INFO] Final Memory: 133M/805M
[INFO] ------------------------------------------------------------------------
Woohoo! :D
But, now what do I need to do to actually install JBDS? How do I get the installer running?
Under devstudio/product/installer/target I found jbdevstudio-product-universal-7.0.0.Beta1-v20130527-2336.jar. So do I just run that as usual, with java -jar ...?
was (Author: mmurray):
[~nickboldt], downloaded the 7.0.0.Beta1-v20130526-0839-B241 source zip. I unzipped it and ran mvn install, with outcome:
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 40:35.326s
[INFO] Finished at: Tue May 28 09:48:10 EST 2013
[INFO] Final Memory: 133M/805M
[INFO] ------------------------------------------------------------------------
Woohoo! :D
But, now what do I need to do to actually install JBDS? How do I get the installer running?
> JBDS should be buildable from source zip
> ----------------------------------------
>
> Key: JBDS-2456
> URL: https://issues.jboss.org/browse/JBDS-2456
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.0.GA, 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta1
>
> Attachments: log.eap-hudson.txt, log.eap.txt, log.hudson.txt, log.txt
>
>
> As reported here: http://stackoverflow.com/questions/12807472/how-build-jboss-developer-stu... it would be nice if one could build JBDS from the sources zip. [~mmurray] reports that it sort of works but izPack is missing:
> {quote}it failed to find the devstudio/product/installer/IzPack-4.3.4.zip{quote}
> It should be noted that JBT can be built from github sources (but I don't think we've ever tried to build it from the source zip either).
> Ref: https://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3
--
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, 11 months
[JBoss JIRA] (JBDS-2456) JBDS should be buildable from source zip
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2456?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2456:
---------------------------------------
[~nickboldt], downloaded the 7.0.0.Beta1-v20130526-0839-B241 source zip. I unzipped it and ran mvn install, with outcome:
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 40:35.326s
[INFO] Finished at: Tue May 28 09:48:10 EST 2013
[INFO] Final Memory: 133M/805M
[INFO] ------------------------------------------------------------------------
Woohoo! :D
But, now what do I need to do to actually install JBDS? How do I get the installer running?
> JBDS should be buildable from source zip
> ----------------------------------------
>
> Key: JBDS-2456
> URL: https://issues.jboss.org/browse/JBDS-2456
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.0.GA, 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta1
>
> Attachments: log.eap-hudson.txt, log.eap.txt, log.hudson.txt, log.txt
>
>
> As reported here: http://stackoverflow.com/questions/12807472/how-build-jboss-developer-stu... it would be nice if one could build JBDS from the sources zip. [~mmurray] reports that it sort of works but izPack is missing:
> {quote}it failed to find the devstudio/product/installer/IzPack-4.3.4.zip{quote}
> It should be noted that JBT can be built from github sources (but I don't think we've ever tried to build it from the source zip either).
> Ref: https://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3
--
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, 11 months
[JBoss JIRA] (JBIDE-14523) Arquillian Cruiser View slows down Eclipse
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14523?page=com.atlassian.jira.plugi... ]
Aslak Knutsen commented on JBIDE-14523:
---------------------------------------
> Yes, it is. I have been trying to fix that issue.
> What 62 projects are you using? JBoss AS?
> I would like to test with a similar environment if possible.
I just have a bunch of Arquillian projects/extensions imported in the workspace.
https://github.com/arquillian
> Arquillian Cruiser View slows down Eclipse
> ------------------------------------------
>
> Key: JBIDE-14523
> URL: https://issues.jboss.org/browse/JBIDE-14523
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta2
>
>
> Not 100% sure what is going on here, but when I have the Cruiser View open, Eclipse slow's to a holdt for about 10s on save. Freezing the main thread, which makes the hole thing useless.
> In the Arquillian Cruiser view there are 62 projects shown(+ sub Test classes etc). It takes about 10s to start/open the view as well.
> Is it checking 'all' projects when a single file is saved?
> How is the content of the Archive calculated?
> Could the calculation be processed in a separate thread to avoid freezing the main GUI?
--
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, 11 months