[JBoss JIRA] (JBIDE-19077) For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [Forge]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19077?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19077:
-----------------------------------
Description:
For JBIDE 4.3.0.Alpha1 [Forge]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
was:
For JBIDE 4.3.0.Alpha1 [Forge]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [Forge]
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-19077
> URL: https://issues.jboss.org/browse/JBIDE-19077
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: forge
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Forge]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
> Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19072) Improve plugin version auditing & how we build
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19072?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19072:
-----------------------------------
Description:
For JBIDE 4.3.0.Alpha1: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
was:
For JBIDE 4.3.0.Alpha1: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> Improve plugin version auditing & how we build
> ----------------------------------------------
>
> Key: JBIDE-19072
> URL: https://issues.jboss.org/browse/JBIDE-19072
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
> Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19073) For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [Central]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19073?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19073:
-----------------------------------
Description:
For JBIDE 4.3.0.Alpha1 [Central]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
was:
For JBIDE 4.3.0.Alpha1 [Central]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [Central]
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-19073
> URL: https://issues.jboss.org/browse/JBIDE-19073
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Central]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
> Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19075) For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19075?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19075:
-----------------------------------
Description:
For JBIDE 4.3.0.Alpha1 [Base]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
was:
For JBIDE 4.3.0.Alpha1 [Base]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [Base]
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19075
> URL: https://issues.jboss.org/browse/JBIDE-19075
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [Base]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
> Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19089) JavaEE Batch component has no junit tests, so all-tests/pom.xml fails
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19089?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-19089:
----------------------------------------
Yes, we only have integration tests in (batch/itests) so far. Thanks for the PR.
> JavaEE Batch component has no junit tests, so all-tests/pom.xml fails
> ---------------------------------------------------------------------
>
> Key: JBIDE-19089
> URL: https://issues.jboss.org/browse/JBIDE-19089
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Fix For: 4.3.0.Alpha1
>
>
> No JUnit tests for batch? That's not good.
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-javaee_master/682/console}
> 04:03:14 [ERROR] Child module /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/all-tests/../batch/tests of /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/all-tests/pom.xml does not exist
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3210) create a JBDS Central feature which includes only JBDS Central branding plugin
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3210?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-3210.
----------------------------
Resolution: Deferred
Closing - deferred. We might decide this is useful in future, but for now it's not needed.
If you later decide you want this, your window to get it done closes at JBDS 9.0.0.Beta1 and reopens if/when we do a JBDS 9.1 next March 2016.
> create a JBDS Central feature which includes only JBDS Central branding plugin
> ------------------------------------------------------------------------------
>
> Key: JBDS-3210
> URL: https://issues.jboss.org/browse/JBDS-3210
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, requirements
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha1
>
>
> Purpose:
> Provide a single feature which includes both JBoss Central (pulled from JBoss Tools, minus its "community" plugin, org.jboss.tools.community.central) and the JBDS Central branding plugin, com.jboss.devstudio.core.central.
> Reason:
> This will allow us to create Marketplace installs for things like JBDS Fuse Tooling which include ONLY the Fuse features + the bare bones of Central, without having all of JBDS come along for the ride. Without this, we can create a JBoss Tools-branded Fuse entry in the Marketplace, or a JBDS-branded Fuse entry in the Marketplace [which includes all of JBDS]. We want a JBDS-branded Fuse entry, which only includes the bare bones, not ALL the JBDS stuff.
> Technical problems:
> * Marketplace can only install features, not individual plugins
> * Today, the only way to install JBDS Central via Marketplace is to include the com.jboss.devstudio.core.feature, which includes the com.jboss.devstudio.core.central branding plugin. But doing so installs ALL of JBDS, too.
> Solution:
> 1. Create a com.jboss.devstudio.core.central.feature which includes:
> * com.jboss.devstudio.core.central
> * org.jboss.tools.central
> 2. Optionally, could also include these plugins:
> * com.jboss.devstudio.core.project.examples
> * com.jboss.devstudio.core.usage.branding
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19086) use delegating progress monitor in foundation.core (was: common.ui)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19086?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19086:
-----------------------------------
Summary: use delegating progress monitor in foundation.core (was: common.ui) (was: use delegating progress monitor in common.core (was: common.ui))
> use delegating progress monitor in foundation.core (was: common.ui)
> -------------------------------------------------------------------
>
> Key: JBIDE-19086
> URL: https://issues.jboss.org/browse/JBIDE-19086
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common/jst/core
> Affects Versions: 4.2.2.Final
> Reporter: Andre Dietisheim
>
> WizardUtils is using *org.jboss.tools.common.ui.* DelegatingProgressMonitor. The DelegatingProgressMonitor was moved to *org.jboss.tools.common.core* while keeping an empty class in common.ui for compatibility reasons. We should now use the "new" class in core.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months