[JBoss JIRA] (JBIDE-17527) revise Early Access disclaimer copy
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17527?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-17527:
------------------------------------
Two issues w/ the above:
a) "Early Access" not "early access"
b) "update (a space) site" not "updatesite"
Just because a new site is added to the list of Available Software Sites does not guarantee it'll be used when "updating plug-ins manually". Assuming you mean via Help > Install new software, a user might have disabled the flag for "check all available sites" and therefore the new EA site will be ignored for such an operation.
Therefore, how about this:
"An Early Access update site will be added to the list of >Available Software Sites<, and may then be used to resolve dependencies or provide newer versions of software when performing an update, install, or when launching examples from JBoss Central."
I would also link >Available Software Sites< to the preferences page, if possible.
> revise Early Access disclaimer copy
> -----------------------------------
>
> Key: JBIDE-17527
> URL: https://issues.jboss.org/browse/JBIDE-17527
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, discovery
> Affects Versions: 4.2.0.Beta2
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Labels: early-access
> Fix For: 4.2.0.Beta3
>
>
> Copy needs a bit of a rewrite.
> Old:
> {quote}
> *Early Access Features*
> Early Access features contains new functionality and fixes that are under development. You are encouraged to use these and give feedback but be aware: They are NOT officially supported, and NOT guaranteed to work correctly in your installation nor is it guaranteed it will end up in the final version. Use them at your own risk!
> [ ] I understand those conditions, and I still want to access Early Access features.
> {quote}
> Proposed:
> {quote}
> *Early Access features*
> Early Access features contain new functionality and/or fixes that are under development. You are encouraged to use these features and to give feedback but be aware that these features are NOT officially supported, NOT guaranteed to work correctly, and subject to removal from JBoss Central at any time, for any reason. Use them at your own risk!
> [ ] I understand these conditions, and still want to enable Early Access features.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-15609) versionwatch should ignore when there's a folder & jar which are identical
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15609?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15609:
-------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> versionwatch should ignore when there's a folder & jar which are identical
> --------------------------------------------------------------------------
>
> Key: JBIDE-15609
> URL: https://issues.jboss.org/browse/JBIDE-15609
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa
> Affects Versions: 4.1.1.Alpha2
> Reporter: Nick Boldt
> Assignee: Jiri Peterka
> Fix For: 4.2.0.CR1
>
>
> A while ago I added a facility to jar up feature and plugin folders so they could have their md5 sums compared.
> Now, the vwatch tool complains when there's a folder and a jar present.
> Two possible solutions to this come to mind:
> a) ignore this - do not report as *{color:red}a problem{color}*
> b) whenever a folder is jarred up, delete the source folder, so the above condition cannot occur
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-2949) Require Java 7 for the IDE
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2949?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2949:
----------------------------------
{quote}"I have changed the ACKs. Pray I don't change them further." - Darth JIRA{quote}
[~burrsutter] thanks for your considerACKtion.
[~mmurray] I wasn't blaming, was simply pointing out that this JIRA needed some ACKing changes. Not sure why doc ACK is new, or needed, since there's a Docs QE Status field too.
[~ldimaggio] As you're on vacation, I've ACKed this for you, as I believe everything you need to do is already covered in the test plan doc in mojo. Hope you don't consider that a SYN or worse, that "it's a trap!" You can of course ACKbar me from changing the qa_ack field in future. :)
/me drops the mic and walks off.
> Require Java 7 for the IDE
> --------------------------
>
> Key: JBDS-2949
> URL: https://issues.jboss.org/browse/JBDS-2949
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: integration
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Fix For: 8.0.0.Beta3
>
>
> Run the IDE with Java 7 (Java 6 no longer supported) (Users applications and servers can still use older and newer JDK’s like Java 1.4,5,6, 8 etc.) P1
> Java 6 is no longer supported by Oracle and by requiring Java 7 we can use better native IO and JavaFX (only on oracle)
> Forge already requires Java 7.
> Concerns: If we do not run with Java 6 we cannot support Xulrunner based VPE on OSX.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-2949) Require Java 7 for the IDE
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2949?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2949:
-----------------------------
CDW docs_ack: + (was: ?)
> Require Java 7 for the IDE
> --------------------------
>
> Key: JBDS-2949
> URL: https://issues.jboss.org/browse/JBDS-2949
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: integration
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Fix For: 8.0.0.Beta3
>
>
> Run the IDE with Java 7 (Java 6 no longer supported) (Users applications and servers can still use older and newer JDK’s like Java 1.4,5,6, 8 etc.) P1
> Java 6 is no longer supported by Oracle and by requiring Java 7 we can use better native IO and JavaFX (only on oracle)
> Forge already requires Java 7.
> Concerns: If we do not run with Java 6 we cannot support Xulrunner based VPE on OSX.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-2949) Require Java 7 for the IDE
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2949?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2949:
-----------------------------
CDW release: + (was: ?)
> Require Java 7 for the IDE
> --------------------------
>
> Key: JBDS-2949
> URL: https://issues.jboss.org/browse/JBDS-2949
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: integration
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Fix For: 8.0.0.Beta3
>
>
> Run the IDE with Java 7 (Java 6 no longer supported) (Users applications and servers can still use older and newer JDK’s like Java 1.4,5,6, 8 etc.) P1
> Java 6 is no longer supported by Oracle and by requiring Java 7 we can use better native IO and JavaFX (only on oracle)
> Forge already requires Java 7.
> Concerns: If we do not run with Java 6 we cannot support Xulrunner based VPE on OSX.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-2949) Require Java 7 for the IDE
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2949?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2949:
-----------------------------
CDW qa_ack: + (was: ?)
> Require Java 7 for the IDE
> --------------------------
>
> Key: JBDS-2949
> URL: https://issues.jboss.org/browse/JBDS-2949
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: integration
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Fix For: 8.0.0.Beta3
>
>
> Run the IDE with Java 7 (Java 6 no longer supported) (Users applications and servers can still use older and newer JDK’s like Java 1.4,5,6, 8 etc.) P1
> Java 6 is no longer supported by Oracle and by requiring Java 7 we can use better native IO and JavaFX (only on oracle)
> Forge already requires Java 7.
> Concerns: If we do not run with Java 6 we cannot support Xulrunner based VPE on OSX.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17766) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17766?page=com.atlassian.jira.plugi... ]
Snjezana Peco closed JBIDE-17766.
---------------------------------
Resolution: Done
> For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Arquillian]
> --------------------------------------------------------
>
> Key: JBIDE-17766
> URL: https://issues.jboss.org/browse/JBIDE-17766
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Beta3
>
>
> For JBIDE 4.2.0.Beta3 [Arquillian]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3
> [Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Beta3-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Beta3x
> git push origin jbosstools-4.2.0.Beta3x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Beta3-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and
> * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-16991) arquillian editor - quailfiier list is very slow to load and does not seem to be cached
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16991?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-16991:
----------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> arquillian editor - quailfiier list is very slow to load and does not seem to be cached
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-16991
> URL: https://issues.jboss.org/browse/JBIDE-16991
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Fix For: 4.2.0.CR1
>
>
> clicking and opening qualifier list the first time freezes the UI (it shouldn't).
> Then an empty dialog shows up.
> A few seconds later the content starts "dripping in'
> Second time there is no freeze - but the content still takes a bit to load and no info about it loading.
> Can't this be cached ?
> Can't we show "Loading..." while it is running and secondly - how will this work when not connected to the network (I assume it is loading something remotely which is great, but we need to work while offline too)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months