[JBoss JIRA] (JBIDE-20005) Navigation to Batch artifacts from properties editor
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20005?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-20005.
------------------------------------
Resolution: Done
> Navigation to Batch artifacts from properties editor
> ----------------------------------------------------
>
> Key: JBIDE-20005
> URL: https://issues.jboss.org/browse/JBIDE-20005
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta2
>
> Attachments: create.gif, open.png
>
>
> It would be useful to be able to navigate from Properties editor and Tree form editor tab (feel free to create a separate issue if needed) to the corresponding artifact. If the reference is empty then the new artifact wizard should be opened.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20005) Navigation to Batch artifacts from properties editor
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20005?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-20005:
----------------------------------------
[~ljelinko] could you please create a separate issue for that? I'm going to resolve this JIRa since it's already in Beta2 and let's fix the issue you found for CR1 (or Beta2 if we have time). Thanks.
> Navigation to Batch artifacts from properties editor
> ----------------------------------------------------
>
> Key: JBIDE-20005
> URL: https://issues.jboss.org/browse/JBIDE-20005
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta2
>
> Attachments: create.gif, open.png
>
>
> It would be useful to be able to navigate from Properties editor and Tree form editor tab (feel free to create a separate issue if needed) to the corresponding artifact. If the reference is empty then the new artifact wizard should be opened.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20259) error when opening hybrid mobile wizard
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20259?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-20259.
----------------------------------
Resolution: Done
This is already fixed upstream. I have pulled in a new Thym version to get the fix to JBT
> error when opening hybrid mobile wizard
> ---------------------------------------
>
> Key: JBIDE-20259
> URL: https://issues.jboss.org/browse/JBIDE-20259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Reporter: Max Rydahl Andersen
> Assignee: Gorkem Ercan
> Fix For: 4.3.0.Beta2
>
>
> running devstudio b1 I run hybrid mobile wizard I get the following error:
> "Error retrieving the Cordova plug-in registry catalog
> Expected a string but was NULL at line 1 column 8274"
> no other stacktrace
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19814) sources zip should include local sources too (jbosstools-build-sites or jbdevstudio-product)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19814?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19814:
------------------------------------
Reminder to me: need to update JBDS src zip usage instructions [1] because now the sources are in a subfolder.
[1] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/results/cu...
Thus:
{code}
# unpack the Red Hat JBoss Developer Studio sources zip
unzip jboss-devstudio-*-installer-src.zip
# find the Red Hat JBoss Developer Studio sources
cd jboss-devstudio-*-installer-src/jbdevstudio-product-*/
# verify you're using Maven 3.2 or later, with Java 8 or later
mvn --version
# eg., Apache Maven 3.2.5
# Java version: 1.8.0, vendor: Oracle Corporation
# finally, run a build
mvn clean install {code}
> sources zip should include local sources too (jbosstools-build-sites or jbdevstudio-product)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-19814
> URL: https://issues.jboss.org/browse/JBIDE-19814
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2, 4.3.0.CR1
>
>
> If we change the way the jbosstools-src.zip is produced, such that in addition to upstream projects it ALSO includes the contents of jbosstools-build-sites too, then we can reuse that mojo for the jbdevstudio-product src.zip too, as it will ALSO include the 17 upstream JBT zips (from Github) and also the local JBDS sources.
> This would mean a large chunk of ant code in jbdevstudio-product/sources/build.xml (if not all of it) could go away. Hooray for 1 solution spanning both projects and product! :D
> Max also suggested that we use a clean copy of the sources just in case the build process makes them dirty:
> {code}
> git clone --depth=1 . clean-sources-dir && rm -rf clean-sources-dir/.git{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19814) sources zip should include local sources too (jbosstools-build-sites or jbdevstudio-product)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19814?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19814:
-------------------------------
Fix Version/s: 4.3.0.CR1
> sources zip should include local sources too (jbosstools-build-sites or jbdevstudio-product)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-19814
> URL: https://issues.jboss.org/browse/JBIDE-19814
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2, 4.3.0.CR1
>
>
> If we change the way the jbosstools-src.zip is produced, such that in addition to upstream projects it ALSO includes the contents of jbosstools-build-sites too, then we can reuse that mojo for the jbdevstudio-product src.zip too, as it will ALSO include the 17 upstream JBT zips (from Github) and also the local JBDS sources.
> This would mean a large chunk of ant code in jbdevstudio-product/sources/build.xml (if not all of it) could go away. Hooray for 1 solution spanning both projects and product! :D
> Max also suggested that we use a clean copy of the sources just in case the build process makes them dirty:
> {code}
> git clone --depth=1 . clean-sources-dir && rm -rf clean-sources-dir/.git{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months