[JBoss JIRA] (JBIDE-16614) skipRevisionCheckWhenPublishing is misleading in aggregators
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16614?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16614:
-----------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Beta1)
> skipRevisionCheckWhenPublishing is misleading in aggregators
> ------------------------------------------------------------
>
> Key: JBIDE-16614
> URL: https://issues.jboss.org/browse/JBIDE-16614
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.x
>
>
> As the *aggregate* and devstudio-product_* are only run for good reasons (change in a component, or change in aggregation repository - category.xml and other, there is no reason why using the skipRevisionCheckWhenPublishing, which is furthermore a bit error prone and misleading (some manual builds are ignored whereas there has been changes).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17610) In JBoss Central rename 'Enable Early Access' check box
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17610?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-17610.
---------------------------------
Resolution: Rejected
Rejecting. We're keeping Enable Early Access. Need to add some blurb in popup dialog about changes in update sites though
> In JBoss Central rename 'Enable Early Access' check box
> -------------------------------------------------------
>
> Key: JBIDE-17610
> URL: https://issues.jboss.org/browse/JBIDE-17610
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.2.0.Beta2
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Labels: early-access
> Fix For: 4.2.0.Beta3
>
>
> The label for the 'Enable Early Access' check box (JBIDE-17392) should be changed.
> It should be labelled 'Show Early Access'.
> * This makes it consistent with the 'Show Installed' check box
> * And by selecting the check box you aren't actually _enabling_ Early Access features - you are merely showing them and still have to install them
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-3079) Offline Central installation misses some JBT bundles
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3079?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3079:
--------------------------------------
Seems like these features are not necessary in order to build JBDS, so I believe your suggestion of removing them from JBDS TP in favor of Central one is the best one.
> Offline Central installation misses some JBT bundles
> ----------------------------------------------------
>
> Key: JBDS-3079
> URL: https://issues.jboss.org/browse/JBDS-3079
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: discovery
> Affects Versions: 8.0.0.Beta2
> Reporter: Mickael Istria
> Priority: Minor
> Fix For: 8.0.0.Beta3
>
>
> Removed items include:
> org.jboss.tools.vpe.cordovasim.feature (and source)
> org.jboss.tools.maven.jbosspackaging.feature (and source)
> org.jboss.tools.common.mylyn.feature (and source)
> Problem w/ removing these is that the JBDS Central plugin.xml requirs all three of them in these connectors:
> JBoss Hybrid Mobile Tools + CordovaSim
> JBoss Tools Maven Packaging Configurator
> Mylyn support for reporting JBoss JIRAs and Red Hat Bugzillas
> So if we remove them, then those connectors can't be installed in JBDS.
> Possible workarounds:
> a) do nothing and accept that for offline installs, you need the update site (not the installer) + central zip; also accept that the installer != update site
> b) put these 3 features in the installer so that the installer contents == the update site contents (except for sources) [I did this in JBDS-3071 but [~dgolovin] reverted it]
> c) move these 3 features into the JBDS TP; this is bad because it creates an ugly dependency chain: JBDS -> JBDS TP -> JBT -> JBT TP... every time JBT rebuilds, we need to update the version of org.jboss.tools.* in the JBDS TP
> d) move these 3 features into the Central TP; this is bad in that as in (c) we would have to keep updating the Central TP each time there's a new JBT release... but we already have this problem because of Arquillian being included in the EA TP.
> Since (b) was rejected, clearly the solution is (d). Or do nothing and annoy offline users with (a). :D
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-3079) Offline Central installation misses some JBT bundles
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3079?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3079:
----------------------------------
Since Max is so against duplication of content (except where he's agreed to it, like when we decided to put TestNG in both the JBDS TP and the Central TP, or having Arquillian available in both JBoss Tools and JBoss Central EA, or in fact 98% of the content in the JBT and JBDS target platforms), we could take my proposal one step further and remove these three features from the JBDS update site entirely, moving them completely to Central, where IMHO they belong.
That would reduce the duplication AND still make them available to both online and offline Central users. [~mickael_istria] WDYT?
Should they ever graduate from "only in Central" to "available OOTB in JBDS" we can of course move them back at that time.
> Offline Central installation misses some JBT bundles
> ----------------------------------------------------
>
> Key: JBDS-3079
> URL: https://issues.jboss.org/browse/JBDS-3079
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: discovery
> Affects Versions: 8.0.0.Beta2
> Reporter: Mickael Istria
> Priority: Minor
> Fix For: 8.0.0.Beta3
>
>
> Removed items include:
> org.jboss.tools.vpe.cordovasim.feature (and source)
> org.jboss.tools.maven.jbosspackaging.feature (and source)
> org.jboss.tools.common.mylyn.feature (and source)
> Problem w/ removing these is that the JBDS Central plugin.xml requirs all three of them in these connectors:
> JBoss Hybrid Mobile Tools + CordovaSim
> JBoss Tools Maven Packaging Configurator
> Mylyn support for reporting JBoss JIRAs and Red Hat Bugzillas
> So if we remove them, then those connectors can't be installed in JBDS.
> Possible workarounds:
> a) do nothing and accept that for offline installs, you need the update site (not the installer) + central zip; also accept that the installer != update site
> b) put these 3 features in the installer so that the installer contents == the update site contents (except for sources) [I did this in JBDS-3071 but [~dgolovin] reverted it]
> c) move these 3 features into the JBDS TP; this is bad because it creates an ugly dependency chain: JBDS -> JBDS TP -> JBT -> JBT TP... every time JBT rebuilds, we need to update the version of org.jboss.tools.* in the JBDS TP
> d) move these 3 features into the Central TP; this is bad in that as in (c) we would have to keep updating the Central TP each time there's a new JBT release... but we already have this problem because of Arquillian being included in the EA TP.
> Since (b) was rejected, clearly the solution is (d). Or do nothing and annoy offline users with (a). :D
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months