[JBoss JIRA] (JBDS-3020) Remove PDE from JBDS
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-3020?page=com.atlassian.jira.plugin.... ]
Rob Stryker commented on JBDS-3020:
-----------------------------------
The second article appears to be advocating the 'mark as deployable' rather than our osgi publisher, but the point is, osgi bundles are a real use case for as7/wf/eap6x servers and removing pde basically removes any entry point for users to make an osgi bundle.
> Remove PDE from JBDS
> ---------------------
>
> Key: JBDS-3020
> URL: https://issues.jboss.org/browse/JBDS-3020
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jsf, jsp/jsf/xml/html source editing, project-examples, servers
> Affects Versions: 8.0.0.Beta1
> Reporter: Denis Golovin
> Assignee: Max Rydahl Andersen
>
> Remove PDE requirements in components mentioned in JBDS-2923. This would let exclude PDE features form JBDS and remove UI artifacts added by PDE in:
> - New Wizars
> - Views
> - Perspectives
> - Preferences
> - Project properties
> - Pop-up menus
--
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
11 years, 11 months
[JBoss JIRA] (JBDS-3020) Remove PDE from JBDS
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-3020?page=com.atlassian.jira.plugin.... ]
Rob Stryker commented on JBDS-3020:
-----------------------------------
I don't know how I missed this jira, but... do not remove PDE. I don't know who told you astools has no dependencies on PDE, but we do.
Our OSGi publisher delegates to PDE.
org.jboss.tools.as.core.server.controllable.subsystems.internal,OSGiPublishController.java:
import org.eclipse.pde.core.plugin.PluginRegistry;
import org.eclipse.pde.internal.core.exports.FeatureExportInfo;
import org.eclipse.pde.internal.core.exports.PluginExportOperation;
> Remove PDE from JBDS
> ---------------------
>
> Key: JBDS-3020
> URL: https://issues.jboss.org/browse/JBDS-3020
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jsf, jsp/jsf/xml/html source editing, project-examples, servers
> Affects Versions: 8.0.0.Beta1
> Reporter: Denis Golovin
> Assignee: Max Rydahl Andersen
>
> Remove PDE requirements in components mentioned in JBDS-2923. This would let exclude PDE features form JBDS and remove UI artifacts added by PDE in:
> - New Wizars
> - Views
> - Perspectives
> - Preferences
> - Project properties
> - Pop-up menus
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-17002) Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17002?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-17002:
-------------------------------
Attachment: java-8-in-kepler-central-site.png
java-8-in-kepler-central-site2.png
As there were no objections, I've pushed the new plugin out to http://download.jboss.org/jbosstools/updates/stable/kepler/plugins/ and updated http://download.jboss.org/jbosstools/updates/stable/kepler/jbosstools-dir...
Just did an install from Central... looks like this:
!java-8-in-kepler-central-site.png!
!java-8-in-kepler-central-site2.png!
----
As to the other issue, all I did was to provide snapshots of the discovery site for 4.1.2 and 4.1.2.1 here:
http://download.jboss.org/jbosstools/discovery/development/
http://download.jboss.org/jbosstools/discovery/stable/
They're not actually linked from anywhere, but are provided for historical purposes in terms of what QE used to test a given release.
> Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2
> -----------------------------------------------------------
>
> Key: JBIDE-17002
> URL: https://issues.jboss.org/browse/JBIDE-17002
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.1.2.Final
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Fix For: 4.1.2.Final
>
> Attachments: java-8-in-kepler-central-site.png, java-8-in-kepler-central-site2.png, jbide17002-3-4-features.png, jbide17002-6-7-features.png, jbide17002-patch-catg.png
>
>
> We decided to provide an easy way for JBT users to install Java 8 support in Eclipse Kepler SR2 in 1 click, instead of have to chase the update sites for JDT, M2e and WTP.
> * JDT Feature patch : http://download.eclipse.org/eclipse/updates/4.3-P-builds/
> * M2E 1.4.1 (org.eclipse.m2e.feature) http://download.eclipse.org/technology/m2e/releases/1.4/1.4.1.20140328-1905
> * WTP Feature Patch : http://download.eclipse.org/webtools/patches/drops/R3.5.2/P-3.5.2-2014032...
> All 3 features should be available via a unique connector in JBoss Central > Software Updates
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-17002) Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17002?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-17002.
------------------------------
Closing. Max, if you need further clarification, feel free to unclose.
> Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2
> -----------------------------------------------------------
>
> Key: JBIDE-17002
> URL: https://issues.jboss.org/browse/JBIDE-17002
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.1.2.Final
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Fix For: 4.1.2.Final
>
> Attachments: java-8-in-kepler-central-site.png, java-8-in-kepler-central-site2.png, jbide17002-3-4-features.png, jbide17002-6-7-features.png, jbide17002-patch-catg.png
>
>
> We decided to provide an easy way for JBT users to install Java 8 support in Eclipse Kepler SR2 in 1 click, instead of have to chase the update sites for JDT, M2e and WTP.
> * JDT Feature patch : http://download.eclipse.org/eclipse/updates/4.3-P-builds/
> * M2E 1.4.1 (org.eclipse.m2e.feature) http://download.eclipse.org/technology/m2e/releases/1.4/1.4.1.20140328-1905
> * WTP Feature Patch : http://download.eclipse.org/webtools/patches/drops/R3.5.2/P-3.5.2-2014032...
> All 3 features should be available via a unique connector in JBoss Central > Software Updates
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-17209) only product for mylyn integration is JBossAS Server
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17209?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-17209:
-------------------------------
Component/s: central
common/jst/core
> only product for mylyn integration is JBossAS Server
> ----------------------------------------------------
>
> Key: JBIDE-17209
> URL: https://issues.jboss.org/browse/JBIDE-17209
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, common/jst/core, server
> Reporter: Max Rydahl Andersen
> Priority: Minor
>
> Using "report bug or enhancement" JBoss Tools shows up but then after that a list of "products" is shown and it just list JBossAS Server.
> I would have expected Developer Studio too at least, and a few more key components.
> Note: this might not be something base should add, but put it into central or jbds product makes sense I think.
> -- Configuration Details --
> Product: Eclipse 4.4.0.20140301-1817 (org.eclipse.epp.package.jee.product)
> Installed Features:
> org.jboss.ide.eclipse.as.feature 3.0.0.Beta2-v20140421-1626-B483
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-17209) only product for mylyn integration is JBossAS Server
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17209?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-17209:
-------------------------------
Component/s: server
> only product for mylyn integration is JBossAS Server
> ----------------------------------------------------
>
> Key: JBIDE-17209
> URL: https://issues.jboss.org/browse/JBIDE-17209
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Priority: Minor
>
> Using "report bug or enhancement" JBoss Tools shows up but then after that a list of "products" is shown and it just list JBossAS Server.
> I would have expected Developer Studio too at least, and a few more key components.
> Note: this might not be something base should add, but put it into central or jbds product makes sense I think.
> -- Configuration Details --
> Product: Eclipse 4.4.0.20140301-1817 (org.eclipse.epp.package.jee.product)
> Installed Features:
> org.jboss.ide.eclipse.as.feature 3.0.0.Beta2-v20140421-1626-B483
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-17207) Run tests on all major OS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17207?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-17207:
------------------------------------
May have problems w/ UI tests, not sure. Could as [~mmalina] or [~ldimaggio] if they run any of our projects' UI tests on Win/OSX slaves in Brno - perhaps for integration tests or Red Deer?
> Run tests on all major OS
> -------------------------
>
> Key: JBIDE-17207
> URL: https://issues.jboss.org/browse/JBIDE-17207
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Alexey Kazakov
> Fix For: 4.2.0.Beta2, 4.2.0.CR1
>
>
> Currently, our jenkins server runs JBT jUnit tests on Linux only. It would be good if we also run the tests on Windows and Mac.
> For example, we recently ran base, jst and javaee tests on Windows and got more than a hundred failures. Some of them indicated real bugs (not just tests problems). See JBIDE-17200.
> We don't have to run them every day. Maybe once a week or month?
> cc: [~maxandersen], [~dgolovin], [~nickboldt], [~mickael_istria]
--
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
11 years, 11 months
[JBoss JIRA] (JBIDE-17210) where is our nightly site OR why is nightly site not actually built regularly?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17210?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-17210:
------------------------------------
If the aggregate builds frequently, people like Denis complain it moves too fast and builds that depend on it break. But now that builds depend on specific components instead of an upstream aggregation (or composite), the only build affected by frequent changes to the JBT aggregate in master is the JBDS build (which depends on it for its content). Meanwhile, frequent builds also trigger complaints from other Jenkins users because we're tying up resources and just respinning content for no reason.
So... ages ago I implemented a bit of logic that says "check the upstream composite site; if content has changed there, we need a new aggregate. If not, don't rebuild the aggregate."
This logic is here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite...
HOWEVER...
when the composite install test fails, it won't report correctly if the site contents are the same or not; in fact, it simply refrains from kicking the downstream aggregation, and the result is the JBT nightly master branch update site aggregate is horribly out of date.
The reason for the failure is logged and simple enough to fix:
{code}
[p2.dir] !MESSAGE The installable unit org.jboss.tools.gwt.feature.feature.group has not been found.
{code}
Basically, we 're trying to install a feature that no longer exists in the composite, and p2 director doesn't take too kindly to that sort of shenanigan.
> where is our nightly site OR why is nightly site not actually built regularly?
> ------------------------------------------------------------------------------
>
> Key: JBIDE-17210
> URL: https://issues.jboss.org/browse/JBIDE-17210
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
>
> http://download.jboss.org/jbosstools/updates/nightly/core/master
> our official "nightly" updatesite has not been rebuilt for ~6 days at the time of writing.
> see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo...
> Why is this ?
> Is there another site that can be used as "nightly" ? i.e. one that just composites instead of aggregates ?
> p.s. i'm going to kick of a build so we get some fixes into the nightly.
--
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
11 years, 11 months