[JBoss JIRA] (JBDS-3996) No installer jar as a result of jbdevstudio-product repo build
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3996?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-3996:
--------------------------------
Priority: Minor (was: Major)
> No installer jar as a result of jbdevstudio-product repo build
> --------------------------------------------------------------
>
> Key: JBDS-3996
> URL: https://issues.jboss.org/browse/JBDS-3996
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 10.1.0.AM3
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Minor
>
> When I build the jbdevstudio-product git repo using {code}mvn clean verify -DskipTests{code}, I was expecting to have the installer jar created in installer/target/, but all I see is a installer-10.1.0-SNAPSHOT.zip , not the installer jar (which should be called devstudio*.jar).
> This was on mac and I did it because I wanted to verify this JIRA:
> JBDS-3986 support building devstudio on windows
> So I wanted to try this on another platform first.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22819) wrap staging build process with a jenkins job
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22819?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22819 at 8/12/16 5:24 PM:
-------------------------------------------------------------
0. Overall buildflow job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow...
1. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-01-check-versions-branches-root-poms_master/}
// Verify correct version set in org.jboss.tools.foundation.core and devstudio.core.central
// Verify all branches have been created & all root poms point to the correct parent pom version.
{code}
1a. By hand:
* Disable jobs [so far has to be done by script locally because of permissions]
{code}
# kerberos login for the Jenkins server
userpass=nboldt:PASSWORD
stream_jbt=master # or 4.4.neon
stream_ds=master # or 10.0.neon
for j in jbosstools-build.parent_${stream_jbt} jbosstoolstargetplatforms-matrix jbosstools-buildflow_${stream_jbt} jbosstools-composite-install_${stream_jbt} jbosstools-browsersim-standalone_${stream_jbt} jbosstools-build-sites.aggregate.site_${stream_jbt} jbosstools-build-sites.aggregate.coretests-site_${stream_jbt} jbosstools-centraltarget_${stream_jbt} jbosstools-build-sites.aggregate.child-sites_${stream_jbt} devstudio.product_${stream_ds} devstudio.versionwatch_${stream_ds} jbosstools-install-p2director.install-tests.matrix_${stream_jbt} jbosstools-install-grinder.install-tests.matrix_${stream_jbt}; do
curl -k -X POST -u ${userpass} https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/${j}/disable && echo -n ".D"
curl -k -X POST -u ${userpass} https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/${j}/lastBuild/toggl... && echo -n ".K"
done
echo ""
{code}
1b. Using the buildflow, Jenkins job or by hand:
* Build Discovery Sites
{code}
# kerberos login for the Jenkins server
userpass=nboldt:PASSWORD
versionWithRespin_jbt=4.4.1.AM3 # a, b, c... (not SNAPSHOT!)
stream_jbt=master # or 4.4.neon
stream_ds=master # or 10.0.neon
TARGET_PLATFORM_VERSION_MAX=4.60.1.AM3-SNAPSHOT
TARGET_PLATFORM_CENTRAL_MAX=4.60.1.AM3-SNAPSHOT
for j in jbosstools-discovery_${stream_jbt}; do
curl -k -X POST -u ${userpass} https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/${j}/enable && echo -n ".E"
curl -k -u ${userpass} --data "VERSION=${versionWithRespin_jbt##*.}&TARGET_PLATFORM_VERSION_MAXIMUM=${TARGET_PLATFORM_VERSION_MAX}&JBTCENTRALTARGET_VERSION=${TARGET_PLATFORM_CENTRAL_MAX}" https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/${j}/buildWithParame... && echo -n ".B"
sleep 15s
# then disable the job
curl -k -X POST -u ${userpass} https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/${j}/disable && echo -n ".D"
curl -k -X POST -u ${userpass} https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/${j}/lastBuild/toggl... && echo -n ".K"
done
{code}
2. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-02-copy-builds-and-update-sites_master/}
// Copy & rename builds & update sites from "snapshots" to "staging"
{code}
Still To do:
{code}
// 3. Verify sites are correctly populated using curl | grep to check for contents / 404s; fail if anything missing
// 4. TODO: generate PR for Update http://download.jboss.org/jbosstools/neon/staging/updates/
// 5. merge in IS content
// 6. TODO: generate PR for Release the latest staging site to ide-config.properties
// 7. generate notification emails
{code}
8. By hand:
* re-enable jobs [may have to be done by hand because of permissions]
* disable the buildflow and push-to-staging jobs [may have to be done by hand because of permissions]
was (Author: nickboldt):
0. Overall buildflow job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow...
1. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-01-check-versions-branches-root-poms_master/}
// Verify correct version set in org.jboss.tools.foundation.core and devstudio.core.central
// Verify all branches have been created & all root poms point to the correct parent pom version.
{code}
1a. By hand:
* Disable jobs [so far has to be done by hand because of permissions]
1b. Using the buildflow or by hand:
* Build Discovery Sites
2. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-02-copy-builds-and-update-sites_master/}
// Copy & rename builds & update sites from "snapshots" to "staging"
{code}
Still To do:
{code}
// 3. Verify sites are correctly populated using curl | grep to check for contents / 404s; fail if anything missing
// 4. TODO: generate PR for Update http://download.jboss.org/jbosstools/neon/staging/updates/
// 5. merge in IS content
// 6. TODO: generate PR for Release the latest staging site to ide-config.properties
// 7. generate notification emails
{code}
8. By hand:
* re-enable jobs [may have to be done by hand because of permissions]
* disable the buildflow and push-to-staging jobs [may have to be done by hand because of permissions]
> wrap staging build process with a jenkins job
> ---------------------------------------------
>
> Key: JBIDE-22819
> URL: https://issues.jboss.org/browse/JBIDE-22819
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.AM3
>
>
> Job requires about 13 params:
> {code}
> version (JBT and JBDS)
> versionWithRespin (JBT and JBDS)
> versionWithRespin_PREV (JBT and JBDS)
> target platforms (min, max, central)
> respin # (- or a, b, c)
> devsuite installerExe url
> stream_JBT=master # or 4.4.neon
> stream_DS=master # or 10.0.neon
> {code}
> See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... for the steps to convert into a job
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-21059) Server Adapter does not connect in debug mode on WF in a Docker container
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21059:
--------------------------------
Fix Version/s: 4.4.x
(was: 4.4.1.AM1)
> Server Adapter does not connect in debug mode on WF in a Docker container
> --------------------------------------------------------------------------
>
> Key: JBIDE-21059
> URL: https://issues.jboss.org/browse/JBIDE-21059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.4.x
>
>
> I have a WF 9.0.2.Final in a Docker container, started with the debug flag in the command line :
> {code}
> CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone.xml", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0" , "--debug"]
> {code}
> I can connect to this server from the server adapter in Run mode but not in debug mode: the Debug view remains empty and the breakpoints are not hit.
> On the other side, I can connect using the plain Java remote debugger (in the launchers) and the same breakpoints are hit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-17615) When runtime download asks to reenter credentials, it will not accept them even if valid
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17615?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-17615:
--------------------------------
Fix Version/s: 4.4.x
(was: 4.4.1.AM3)
> When runtime download asks to reenter credentials, it will not accept them even if valid
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-17615
> URL: https://issues.jboss.org/browse/JBIDE-17615
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2c B130
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.x
>
> Attachments: reenter-password.png
>
>
> I was playing around JBIDE-17601 - that JIRA is about the bug that JBoss.org credentials were not validated when you went through new archetype from central -> Download & Install. So you could enter anything and it would let you carry on. But once the real download is about to start, you will get a popup to enter the credentials again (since the downloader needs the correct password). Even if you now enter the correct credentials, it will ask you 2 more times and then fail on Incorrect password.
> Yes, this will be less likely to happen once JBIDE-17601 is fixed. But I suppose that the popup is in place exactly for the situation when the password needs to be corrected, so it should work, right?
> There may still be a valid use case to hit this issue (although a very rare case):
> 1. User starts the runtime download dialog, enters correct credentials, moves to license
> 2. User changes his password on jboss.org
> 3. User carries on in the dialog to actually start the download - now he will probably be asked to correct his credentials
> So in my opinion, if we already have a mechanism to ask for credentials again, then it should work. If you say this is not needed, then why even allow the popup?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22819) wrap staging build process with a jenkins job
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22819?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22819 at 8/12/16 5:22 PM:
-------------------------------------------------------------
0. Overall buildflow job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow...
1. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-01-check-versions-branches-root-poms_master/}
// Verify correct version set in org.jboss.tools.foundation.core and devstudio.core.central
// Verify all branches have been created & all root poms point to the correct parent pom version.
{code}
1a. By hand:
* Disable jobs [so far has to be done by hand because of permissions]
1b. Using the buildflow or by hand:
* Build Discovery Sites
2. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-02-copy-builds-and-update-sites_master/}
// Copy & rename builds & update sites from "snapshots" to "staging"
{code}
Still To do:
{code}
// 3. Verify sites are correctly populated using curl | grep to check for contents / 404s; fail if anything missing
// 4. TODO: generate PR for Update http://download.jboss.org/jbosstools/neon/staging/updates/
// 5. merge in IS content
// 6. TODO: generate PR for Release the latest staging site to ide-config.properties
// 7. generate notification emails
{code}
8. By hand:
* re-enable jobs [may have to be done by hand because of permissions]
* disable the buildflow and push-to-staging jobs [may have to be done by hand because of permissions]
was (Author: nickboldt):
0. Overall buildflow job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow...
1. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-01-check-versions-branches-root-poms_master/}
// Verify correct version set in org.jboss.tools.foundation.core and devstudio.core.central
// Verify all branches have been created & all root poms point to the correct parent pom version.
{code}
1a. By hand:
* Disable jobs [so far has to be done by hand because of permissions]
1b. Using the buildflow or by hand:
* Build Discovery Sites
2. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-02-copy-builds-and-update-sites_master/}
// Copy & rename builds & update sites from "snapshots" to "staging"
{code}
Still To do:
{code}
// 3. Verify sites are correctly populated using curl | grep to check for contents / 404s; fail if anything missing
// 4. TODO: generate PR for Update http://download.jboss.org/jbosstools/neon/staging/updates/
// 5. merge in IS content
// 6. TODO: generate PR for Release the latest staging site to ide-config.properties
// 7. generate notification emails
{code}
8. By hand:
* re-enable jobs [may have to be done by hand because of permissions]
* disable this job [may have to be done by hand because of permissions]
> wrap staging build process with a jenkins job
> ---------------------------------------------
>
> Key: JBIDE-22819
> URL: https://issues.jboss.org/browse/JBIDE-22819
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.AM3
>
>
> Job requires about 13 params:
> {code}
> version (JBT and JBDS)
> versionWithRespin (JBT and JBDS)
> versionWithRespin_PREV (JBT and JBDS)
> target platforms (min, max, central)
> respin # (- or a, b, c)
> devsuite installerExe url
> stream_JBT=master # or 4.4.neon
> stream_DS=master # or 10.0.neon
> {code}
> See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... for the steps to convert into a job
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22819) wrap staging build process with a jenkins job
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22819?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22819 at 8/12/16 5:21 PM:
-------------------------------------------------------------
0. Overall buildflow job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow...
1. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-01-check-versions-branches-root-poms_master/}
// Verify correct version set in org.jboss.tools.foundation.core and devstudio.core.central
// Verify all branches have been created & all root poms point to the correct parent pom version.
{code}
1a. By hand:
* Disable jobs [so far has to be done by hand because of permissions]
1b. Using the buildflow or by hand:
* Build Discovery Sites
2. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-02-copy-builds-and-update-sites_master/}
// Copy & rename builds & update sites from "snapshots" to "staging"
{code}
Still To do:
{code}
// 3. Verify sites are correctly populated using curl | grep to check for contents / 404s; fail if anything missing
// 4. TODO: generate PR for Update http://download.jboss.org/jbosstools/neon/staging/updates/
// 5. merge in IS content
// 6. TODO: generate PR for Release the latest staging site to ide-config.properties
// 7. generate notification emails
{code}
8. By hand:
* re-enable jobs [may have to be done by hand because of permissions]
* disable this job [may have to be done by hand because of permissions]
was (Author: nickboldt):
Job started: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow...
TODO:
{code}
// Verify correct version set in org.jboss.tools.foundation.core and devstudio.core.central
// Verify all branches have been created & all root poms point to the correct parent pom version.
// Disable jobs
// Build Discovery Sites
// Copy & rename builds & update sites from "snapshots" to "staging"
// Verify sites are correctly populated using curl | grep to check for contents / 404s; fail if anything missing
// TODO: generate PR for Update http://download.jboss.org/jbosstools/neon/staging/updates/
// merge in IS content
// TODO: generate PR for Release the latest staging site to ide-config.properties
// re-enable jobs
// disable this job
// generate notification emails{code}
> wrap staging build process with a jenkins job
> ---------------------------------------------
>
> Key: JBIDE-22819
> URL: https://issues.jboss.org/browse/JBIDE-22819
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.AM3
>
>
> Job requires about 13 params:
> {code}
> version (JBT and JBDS)
> versionWithRespin (JBT and JBDS)
> versionWithRespin_PREV (JBT and JBDS)
> target platforms (min, max, central)
> respin # (- or a, b, c)
> devsuite installerExe url
> stream_JBT=master # or 4.4.neon
> stream_DS=master # or 10.0.neon
> {code}
> See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... for the steps to convert into a job
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ERT-381) Can not select an array element in Outline view (it always re-select the parent) [EBZ#497253]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-381:
---------------------------------------
Summary: Can not select an array element in Outline view (it always re-select the parent) [EBZ#497253]
Key: ERT-381
URL: https://issues.jboss.org/browse/ERT-381
Project: Eclipse Release Train
Issue Type: Task
Components: WTP Source Editing
Reporter: Friendly Jira Robot
Steps:
Create a JSON file with the following contents:
{
"thirdaddition": true,
"name": "JSONEditorTest2",
"secondaddition": 2,
"description": "JSONEditorTest description2",
"version": "1.0.1",
"main": "app.js",
"scripts": {
"start": "node app.js"
},
"array_of_objects": [1, 2, 3],
"value": "test",
"anothervalue": "1234"
}
Navigate in Outline view and try to select there any of the elements in "array_of_objects".
Notice that Outline view does not allow you select any of those elements, selection is reset to the parent "array_of_objects"
Found on MacOS, but I can reproduce it on Windows too.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months