[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19911:
----------------------------------------
Removing it from my bucket as it's not top-priority for 4.3.0.CR1. Maybe [~nickboldt] has time to give it a try? If not, we'll postpone it.
> Create a (manual) job to update a given 3rd-party project on TP
> ---------------------------------------------------------------
>
> Key: JBIDE-19911
> URL: https://issues.jboss.org/browse/JBIDE-19911
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.3.0.CR1
>
>
> For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request.
> * Input: sourceSite, initialMirror (as found in .target), targetMirror
> * Then
> ** job mirros the sourceSite
> ** job publishes (scp) it to targetMirror
> ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target
> ** job runs "mvn fix-version ..." on multiple/*.target
> ** "mvn clean verify -Pmultiple2repo" on multiple/*.target
> ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER
> ** p2diff
> ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-19911:
--------------------------------------
Assignee: (was: Mickael Istria)
> Create a (manual) job to update a given 3rd-party project on TP
> ---------------------------------------------------------------
>
> Key: JBIDE-19911
> URL: https://issues.jboss.org/browse/JBIDE-19911
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Mickael Istria
> Fix For: 4.3.0.CR1
>
>
> For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request.
> * Input: sourceSite, initialMirror (as found in .target), targetMirror
> * Then
> ** job mirros the sourceSite
> ** job publishes (scp) it to targetMirror
> ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target
> ** job runs "mvn fix-version ..." on multiple/*.target
> ** "mvn clean verify -Pmultiple2repo" on multiple/*.target
> ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER
> ** p2diff
> ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-19335) org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19335?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-19335 at 8/31/15 2:48 AM:
--------------------------------------------------------------
To me code looks correct. SWTError is catched -> logBrowserLoadingProblem is called -> FoundationUIPlugin.pluginLog().logError(message, e) is called -> error message is displayed
{code:title=BrowserUtility.java|borderStyle=solid}
try {
return new Browser(parent, style | preferredBrowser);
} catch (SWTError e) {
if(!(e instanceof SWTError) && !browserLoadingErrorLoged) {
logBrowserLoadingProblem(e, browserNames.get(preferredBrowser), true);
}
Control[] children = parent.getChildren();
for (Control child : children) {
child.dispose();
}
{code}
was (Author: vpakan):
To me code looks correct. SWTError is catched -> logBrowserLoadingProblem is called -> FoundationUIPlugin.pluginLog().logError(message, e) is called -> error message is displayed
{code:title=BrowserUtility.java.java|borderStyle=solid}
try {
return new Browser(parent, style | preferredBrowser);
} catch (SWTError e) {
if(!(e instanceof SWTError) && !browserLoadingErrorLoged) {
logBrowserLoadingProblem(e, browserNames.get(preferredBrowser), true);
}
Control[] children = parent.getChildren();
for (Control child : children) {
child.dispose();
}
{code}
> org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19335
> URL: https://issues.jboss.org/browse/JBIDE-19335
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core, runtime-detection
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Environment: Linux
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.CR1
>
>
> DownloadRuntimeLicenseFragment should work even without browser widget available and show html or text without html tags with <p> and <br> elements replaced with '\n'.
> Steps to tests the issue:
> 1. Linux disto without webkit or xulrunner (I was using xubuntu to verify)
> 2. Run JBT and try to download WildFly using Runtime Download dialog;
> 3. It should show not fail with SWTError when presenting license step, but show the link to the license, so you can click on it to open system browser or copy/past it into your favorite one
> 4. Close eclipse
> 5. Install libwebkit
> 6. Start eclipse, do WildFly downloading steps again and you should see license text inside dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-19335) org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19335?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-19335:
-------------------------------------
To me code looks correct. SWTError is catched -> logBrowserLoadingProblem is called -> FoundationUIPlugin.pluginLog().logError(message, e) is called -> error message is displayed
{code:title=BrowserUtility.java.java|borderStyle=solid}
try {
return new Browser(parent, style | preferredBrowser);
} catch (SWTError e) {
if(!(e instanceof SWTError) && !browserLoadingErrorLoged) {
logBrowserLoadingProblem(e, browserNames.get(preferredBrowser), true);
}
Control[] children = parent.getChildren();
for (Control child : children) {
child.dispose();
}
{code}
> org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19335
> URL: https://issues.jboss.org/browse/JBIDE-19335
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core, runtime-detection
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Environment: Linux
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.CR1
>
>
> DownloadRuntimeLicenseFragment should work even without browser widget available and show html or text without html tags with <p> and <br> elements replaced with '\n'.
> Steps to tests the issue:
> 1. Linux disto without webkit or xulrunner (I was using xubuntu to verify)
> 2. Run JBT and try to download WildFly using Runtime Download dialog;
> 3. It should show not fail with SWTError when presenting license step, but show the link to the license, so you can click on it to open system browser or copy/past it into your favorite one
> 4. Close eclipse
> 5. Install libwebkit
> 6. Start eclipse, do WildFly downloading steps again and you should see license text inside dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-19948) Reimplement Eclipse Download plugin to allow dynamic work flow
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19948?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19948:
-------------------------------------
Let's find a time to talk early this week. Please let me know when you're free.
> Reimplement Eclipse Download plugin to allow dynamic work flow
> --------------------------------------------------------------
>
> Key: JBIDE-19948
> URL: https://issues.jboss.org/browse/JBIDE-19948
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.3.0.Alpha2
> Reporter: David Hladky
> Assignee: Rob Stryker
> Fix For: 4.3.0.CR1
>
>
> We need to reimplement the plugin to accept new terms and conditions models as well as follow the workflow changes in case of changes to the current ones.
> Under this issue I will create the tasks we need to achieve this goal.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-19335) org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19335?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19335:
-------------------------------------
This seems very strange and (honestly) not possible? We specifically catch the SWTError, and the closest we come to rethrowing it (which we don't do) is logging it.
https://github.com/jbosstools/jbosstools-base/blob/9a66aca46b54e5ad86a41a...
I'm baffled.
> org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19335
> URL: https://issues.jboss.org/browse/JBIDE-19335
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core, runtime-detection
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Environment: Linux
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.CR1
>
>
> DownloadRuntimeLicenseFragment should work even without browser widget available and show html or text without html tags with <p> and <br> elements replaced with '\n'.
> Steps to tests the issue:
> 1. Linux disto without webkit or xulrunner (I was using xubuntu to verify)
> 2. Run JBT and try to download WildFly using Runtime Download dialog;
> 3. It should show not fail with SWTError when presenting license step, but show the link to the license, so you can click on it to open system browser or copy/past it into your favorite one
> 4. Close eclipse
> 5. Install libwebkit
> 6. Start eclipse, do WildFly downloading steps again and you should see license text inside dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?
by Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ]
Lars Heinemann commented on JBIDE-20100:
----------------------------------------
I like the early access checkbox more than the button in the bottom. (see Fred's screenshot)
> how to make users aware of fuse and other tooling only being available from earlyaccess?
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20100
> URL: https://issues.jboss.org/browse/JBIDE-20100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.0.CR1
>
> Attachments: JBIDE-20100-2.png
>
>
> [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page.
> Some comments:
> "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list."
> "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something."
> Suggestion:
> "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature."
> I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ?
> and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ?
> But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9)
> [~crobson], [~aileenc] and [~lhein] got any suggestions ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TOOLSDOC-635) Documentation deficient for Red_Hat_JBoss_Developer_Studio-8.1-Start_Developing-en-US.pdf tutorial expects that jboss-devstudio-8.1.0.GA-installer-eap.jar will install mavern and create directories conforming to the document,
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-635?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-635:
-------------------------------
Sprint: 03-Aug >> 16-Aug 2015-JBDS/J 2, 14-Sep >> 27-Sep 2015-JBDS/JBT (was: 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT)
> Documentation deficient for Red_Hat_JBoss_Developer_Studio-8.1-Start_Developing-en-US.pdf tutorial expects that jboss-devstudio-8.1.0.GA-installer-eap.jar will install mavern and create directories conforming to the document,
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-635
> URL: https://issues.jboss.org/browse/TOOLSDOC-635
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: Getting Started Guide
> Affects Versions: 4.2.3.Final
> Environment: Build Name: 23019, Start Developing-8.1
> Build Date: 23-03-2015 13:37:18
> Topic ID: 13798-718036 [Latest]
> Reporter: bob anderson
> Assignee: Misha Ali
> Priority: Blocker
> Fix For: 4.2.3.Final
>
>
> Title: Configure Maven to use the JBoss EAP Maven Repository
> Describe the issue:
> I am following the Red_Hat_JBoss_Developer_Studio-8.1-Start_Developing-en-US.pdf tutorial.
> I have followed the previous Red_Hat_JBoss_Developer_Studio-8.1-Install_Red_Hat_JBoss_Developer_Studio-en-US.pdf instructions to install the studio using the jboss-devstudio-8.1.0.GA-installer-eap.jar installer - which is supposed to install mavern too.
> I have reached
> 2.2. Configure Maven to use the JBoss EAP Maven Repository
>
> The issue I am having in Windows 8.1 and in Fedora 21, is where is Mavern?. I can't find the directories that are supposed to be there. I can't find Mavern.
> In windows I have searched for .m2 directories and in Fedora I have gone back and forth as both the administrator and root looking for this hidden directory.
> A search for setting.xml provides no results
> The tutorial says :
> "5. Navigate to path/to /jboss-eap-6 . x. y-maven-repository and click OK. JBoss Maven Tools recursively scans the path searching for the Maven repository."
> I don't actually know if mavern is installed or not, nor what to do to fix the situation.
> Suggestions for improvement:
> 1) Provide information on how to check for Mavern and where it is located
> 2) An actual example of the repository directory might be useful. I am assuming using the conventions etc the path should be something like
> C:\Users\smith\jbdevstudio\runtimes\jboss-eap-6.3.0-mavern-repository
> BUT it doesn't exist, it wasn't created on the install. The closest I can find is
> C:\Users\smith\jbdevstudio\runtimes\jboss-eap which doesn't have anything that looks like a repository
> 3)The tutorial needs to provide a link where we can resolve the issue, or alternatively explain what has happened.
> Additional information:
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months