[JBoss JIRA] (JBDS-2683) Errors in Error Log after IDE is switched to Spring Perspective
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2683?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2683:
--------------------------------------
Component/s: upstream
> Errors in Error Log after IDE is switched to Spring Perspective
> ---------------------------------------------------------------
>
> Key: JBDS-2683
> URL: https://issues.jboss.org/browse/JBDS-2683
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 7.0.0.CR1
> Reporter: Jiri Peterka
> Priority: Critical
> Fix For: 7.1.0.Beta1
>
> Attachments: spring-perspective-errors.png
>
>
> !ENTRY org.eclipse.ui 4 4 2013-07-12 08:29:37.176
> !MESSAGE Unable to find Action Set: ajnavigation
> !ENTRY org.eclipse.ui 4 4 2013-07-12 08:29:37.177
> !MESSAGE Unable to find Action Set: ajelementCreation
> !ENTRY org.eclipse.ui 4 4 2013-07-12 08:29:37.177
> !MESSAGE Unable to find Action Set: com.springsource.sts.roo.ui.actionSet
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2785) Cannot install central content (missing deps)
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-2785?page=com.atlassian.jira.plugin.... ]
Pavol Srna commented on JBDS-2785:
----------------------------------
Successfully installed Spring tooling on beta1b build. No missing deps error seen this time.
> Cannot install central content (missing deps)
> ---------------------------------------------
>
> Key: JBDS-2785
> URL: https://issues.jboss.org/browse/JBDS-2785
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.Alpha2
> Reporter: Pavol Srna
> Fix For: 7.1.0.Beta1
>
>
> stack trace:
> {code}
> Problems occurred while performing installation: Operation details
> Operation details
> Your original request has been modified.
> "m2e-wtp - Maven Integration for WTP" is already present because other installed software requires it. It will be added to the installed software list.
> "Java implementation of Git" is already present because other installed software requires it. It will be added to the installed software list.
> "m2e - Maven Integration for Eclipse" is already present because other installed software requires it. It will be added to the installed software list.
> "Eclipse Git Team Provider" is already present because other installed software requires it. It will be added to the installed software list.
> "JBossAS Tools" is already present because other installed software requires it. It will be added to the installed software list.
> Cannot complete the install because one or more required items could not be found.
> Software being installed: Spring IDE Web Flow Extension (optional) 3.3.0.201307091516-RELEASE (org.springframework.ide.eclipse.webflow.feature.feature.group 3.3.0.201307091516-RELEASE)
> Missing requirement: Spring IDE Live Beans Graph 3.3.0.201307091516-RELEASE (org.springframework.ide.eclipse.beans.ui.livegraph 3.3.0.201307091516-RELEASE) requires 'bundle org.json 0.0.0' but it could not be found
> Cannot satisfy dependency:
> From: Spring IDE Core (required) 3.3.0.201307091516-RELEASE (org.springframework.ide.eclipse.feature.feature.group 3.3.0.201307091516-RELEASE)
> To: org.springframework.ide.eclipse.beans.ui.livegraph [3.3.0.201307091516-RELEASE]
> Cannot satisfy dependency:
> From: Spring IDE Web Flow Extension (optional) 3.3.0.201307091516-RELEASE (org.springframework.ide.eclipse.webflow.feature.feature.group 3.3.0.201307091516-RELEASE)
> To: org.springframework.ide.eclipse.feature.feature.group 0.0.0
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2623:
-----------------------------
Fix Version/s: 7.1.0.GA
(was: 7.1.0.Beta1)
> Create target platform for mirrored parts of Central / 3rd Party Extras
> -----------------------------------------------------------------------
>
> Key: JBDS-2623
> URL: https://issues.jboss.org/browse/JBDS-2623
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.GA
>
> Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png
>
>
> As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central.
> Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files.
> In future, we would:
> * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org]
> * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com]
> * add a whole new aggregate for old + new content
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2819) release updated JBoss Central content for 4.1.1.Final / 7.1.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2819?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2819:
-----------------------------
Description:
See JBDS-2766.
When JBDS 7.1.0.GA drops, we can update this [7] to point at [4].
[7] https://devstudio.jboss.com/updates/7.0/extras/compositeArtifacts.xml & compositeContent.xml
was:
When we release JBT 4.1.1.Alpha2, we can update this [1], [2] to point to the new 4.31.0.Alpha1 Central TP [3], [4] instead of the older URL [5].
[1] http://download.jboss.org/jbosstools/updates/kepler/extras/compositeArtif... & compositeContent.xml
[2] https://devstudio.jboss.com/updates/7.0-staging/extras/compositeArtifacts... & compositeContent.xml
[3] http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/kep...
[4] https://devstudio.jboss.com/targetplatforms/jbtcentraltarget/kepler/
[5] http://download.jboss.org/jbosstools/updates/kepler/extras/ (currently contains released version associated w/ JBT 4.1.0.Final and JBDS 7.0.0.GA)
Then later when JBDS 7.1.0.Beta1 drops, we can update this [6] to point at this [4].
[6] https://devstudio.jboss.com/updates/7.0-development/extras/compositeArtif... & compositeContent.xml
And finally, when JBDS 7.1.0.GA drops, we can update this [7] to point at [4].
[7] https://devstudio.jboss.com/updates/7.0/extras/compositeArtifacts.xml & compositeContent.xml
> release updated JBoss Central content for 4.1.1.Final / 7.1.0.GA
> ----------------------------------------------------------------
>
> Key: JBDS-2819
> URL: https://issues.jboss.org/browse/JBDS-2819
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1
>
>
> See JBDS-2766.
> When JBDS 7.1.0.GA drops, we can update this [7] to point at [4].
> [7] https://devstudio.jboss.com/updates/7.0/extras/compositeArtifacts.xml & compositeContent.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2766) release updated JBoss Central content for 4.1.1.Beta1 / 7.1.0.Beta1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2766?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2766:
-----------------------------
Description:
See JBDS-2765.
When JBDS 7.1.0.Beta1 drops, we can update this [6] to point at this [4].
[6] https://devstudio.jboss.com/updates/7.0-development/extras/compositeArtif... & compositeContent.xml
And finally, when JBDS 7.1.0.GA drops, we can update this [7] to point at [4].
[7] https://devstudio.jboss.com/updates/7.0/extras/compositeArtifacts.xml & compositeContent.xml
was:
When we release JBT 4.1.1.Alpha2, we can update this [1], [2] to point to the new 4.31.0.Alpha1 Central TP [3], [4] instead of the older URL [5].
[1] http://download.jboss.org/jbosstools/updates/kepler/extras/compositeArtif... & compositeContent.xml
[2] https://devstudio.jboss.com/updates/7.0-staging/extras/compositeArtifacts... & compositeContent.xml
[3] http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/kep...
[4] https://devstudio.jboss.com/targetplatforms/jbtcentraltarget/kepler/
[5] http://download.jboss.org/jbosstools/updates/kepler/extras/ (currently contains released version associated w/ JBT 4.1.0.Final and JBDS 7.0.0.GA)
Then later when JBDS 7.1.0.Beta1 drops, we can update this [6] to point at this [4].
[6] https://devstudio.jboss.com/updates/7.0-development/extras/compositeArtif... & compositeContent.xml
And finally, when JBDS 7.1.0.GA drops, we can update this [7] to point at [4].
[7] https://devstudio.jboss.com/updates/7.0/extras/compositeArtifacts.xml & compositeContent.xml
> release updated JBoss Central content for 4.1.1.Beta1 / 7.1.0.Beta1
> -------------------------------------------------------------------
>
> Key: JBDS-2766
> URL: https://issues.jboss.org/browse/JBDS-2766
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1
>
>
> See JBDS-2765.
> When JBDS 7.1.0.Beta1 drops, we can update this [6] to point at this [4].
> [6] https://devstudio.jboss.com/updates/7.0-development/extras/compositeArtif... & compositeContent.xml
> And finally, when JBDS 7.1.0.GA drops, we can update this [7] to point at [4].
> [7] https://devstudio.jboss.com/updates/7.0/extras/compositeArtifacts.xml & compositeContent.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months