[JBoss JIRA] (JBTIS-172) "JBoss jbpm5 runtime extension feature" is not using Red Hat license text
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-172?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-172:
----------------------------------
Hey [~bbrodt] - Trying to clean up some old Jiras. When installing the 'BPMN2 Modeler - jBPM Runtime Extension Feature' I do get the Eclipse Foundation Software User Agreement dialog instead of the RedHat one (with the latest 8.0.2 JBDSIS).
> "JBoss jbpm5 runtime extension feature" is not using Red Hat license text
> -------------------------------------------------------------------------
>
> Key: JBTIS-172
> URL: https://issues.jboss.org/browse/JBTIS-172
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: drools/ jBPM
> Affects Versions: 4.1.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Robert (Bob) Brodt
>
> When installing from Beta1 "JBoss jbpm5 runtime extension feature" uses Eclipse Foundation Software User Agreement.
> It should be using Red Hat, Inc. instead.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19896) Atlassian JIRA Connector 3.2.2.v20130909 (com.atlassian.connector.eclipse.jira.feature.group 3.2.2.v20130909) requires 'javax.activation [1.1.0.v201108011116]' but it could not be found
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19896?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-19896:
----------------------------------
Assignee: Nick Boldt
> Atlassian JIRA Connector 3.2.2.v20130909 (com.atlassian.connector.eclipse.jira.feature.group 3.2.2.v20130909) requires 'javax.activation [1.1.0.v201108011116]' but it could not be found
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19896
> URL: https://issues.jboss.org/browse/JBIDE-19896
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: target-platform
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
>
> While installing everything from Central, the following occurred resolving deps for com.atlassian.connector.eclipse 3.2.2 to javax.activation [1.1.0.v201108011116]:
> {code}
> 13:20:41 [p2.dir] Cannot complete the install because one or more required items could not be found.
> 13:20:41 [p2.dir] Software being installed: Atlassian Connector for Eclipse 3.2.2.v20130909 (com.atlassian.connector.eclipse.feature.group 3.2.2.v20130909)
> 13:20:41 [p2.dir] Missing requirement: Atlassian JIRA Connector (Recommended) 3.2.2.v20130909 (com.atlassian.connector.eclipse.jira.feature.group 3.2.2.v20130909) requires 'javax.activation [1.1.0.v201108011116]' but it could not be found
> 13:20:41 [p2.dir] Cannot satisfy dependency:
> 13:20:41 [p2.dir] From: Atlassian Connector for Eclipse 3.2.2.v20130909 (com.atlassian.connector.eclipse.feature.group 3.2.2.v20130909)
> 13:20:41 [p2.dir] To: com.atlassian.connector.eclipse.jira.feature.group [3.2.2.v20130909]
> 13:20:41 [p2.dir] Application failed, log file location: /mnt/hudson_workspace/workspace/jbosstools-install-p2director.install-tests.matrix_master/6661f455/eclipse/configuration/1433179218565.log
> 13:20:41 [p2.dir] Installation failed.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19776) Create and use Mars RC2/RC3 target-platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19776:
-------------------------------
Summary: Create and use Mars RC2/RC3 target-platform (was: Create and use Mars RC2 target-platform)
> Create and use Mars RC2/RC3 target-platform
> -------------------------------------------
>
> Key: JBIDE-19776
> URL: https://issues.jboss.org/browse/JBIDE-19776
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v20150514.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v20150514.txt, jbosstools.p2diff.v3.txt
>
>
> Mars M7 was released and contains interesting changes.
> We need to start using it ASAP to leverage new functionalities and adapt to the most important changes.
> However, moving to RC1 or RC2 might be ever better as RC1 includes a fix for JBIDE-19773.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19829) Connection wizard: Add Oauth support
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19829?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19829:
-------------------------------------
Summary: Connection wizard: Add Oauth support (was: Add Oauth support to the Openshift Connection Wizard)
> Connection wizard: Add Oauth support
> ------------------------------------
>
> Key: JBIDE-19829
> URL: https://issues.jboss.org/browse/JBIDE-19829
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: connection_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: check-server-type-disabled.png, enlessly-loading.png, ok-enabled.png, Proposed Connection Wizard Chages.png, retrieve-error.png
>
>
> Modify the connection wizard so the v3 server can auto-detect the auth type and support OAuth
> * Remove server type verify button
> * Add v3 auth box (Auto/OAuth/Basic)
> * Optional...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19829) Add Oauth support to the Openshift Connection Wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19829?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19829:
------------------------------------------
resolving this for now since we merged the code in and will file remaining issue to new jiras.
> Add Oauth support to the Openshift Connection Wizard
> ----------------------------------------------------
>
> Key: JBIDE-19829
> URL: https://issues.jboss.org/browse/JBIDE-19829
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: connection_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: check-server-type-disabled.png, enlessly-loading.png, ok-enabled.png, Proposed Connection Wizard Chages.png, retrieve-error.png
>
>
> Modify the connection wizard so the v3 server can auto-detect the auth type and support OAuth
> * Remove server type verify button
> * Add v3 auth box (Auto/OAuth/Basic)
> * Optional...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19795) Bower support
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19795:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-jst/pull/488, https://github.com/jbosstools/jbosstools-jst/pull/489 (was: https://github.com/jbosstools/jbosstools-jst/pull/488)
> Bower support
> -------------
>
> Key: JBIDE-19795
> URL: https://issues.jboss.org/browse/JBIDE-19795
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: javascript
> Affects Versions: 4.3.0.Alpha2
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Final
>
>
> Need to have initial [Bower|http://bower.io/] tools support:
> *The gist*
> Bower tooling should initially support several bower API commands :
> |Command||Description|
> | *bower init* |creates a *bower.json* file|
> |*bower install <package>*|installs packages to *bower_components* folder|
> |*bower uninstall <package>*|uninstalls a package locally from *bower_components* directory|
> |*bower update* |updates installed packages to their newest version according to *bower.json*|
> Basically, the main idea of the implementation is the following:
> Eclipse plugin that will execute *external* bower commands - implementation will fall back on *native* bower installation via *ILaunchConfiguration*
> Native bower tools must be preinstalled
> *The main questions & proposals:*
> 1. https://github.com/jbosstools/jbosstools-playground is probably the best place for initial implementation of bower stuff (infrastructure / build etc.)
> 2. UI. should it be ILaunchShortcuts ("bower init" / "bower update" etc.) + launch configuration enabled for projects with js nature?
> 3. Implementation details:
> - the way of detecting bower? Should user point to it's installation dir and this location will be used for IExternalToolConstants.ATTR_LOCATION (windows case: *\user\AppData\Roaming\npm\node_modules\bower* )
> - if bower was not detected / installed - "Error message with a link to the bower website with installation details depending on the platform"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months