8:43 a.m.
Move all plugins up to baseline
-------------------------------
Key: JBIDE-8866
URL: https://issues.jboss.org/browse/JBIDE-8866
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Rob Stryker
Assignee: Nick Boldt
Fix For: 3.3.0.M2
Not really sure who to assign this to, short of making three dozen separate jira issues ;)
I have 33 patches, one for each module, which modify all manifest.mf version numbers (in
plugins, not in tests) to be brought up to our current baseline.
So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a
dependency on this.specific.runtime into
this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads
this.specific.plugin;bundle-version="3.5.0", it will move it up to
this.specific.runtime;bundle-version="3.6.200".
Etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:50 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8866) Move all plugins up to baseline
[
https://issues.jboss.org/browse/JBIDE-8866?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-8866:
-------------------------------
Attachment: manifests.zip
A selection of non-zero size patches to fix manifest files that do not include minimum
version or version ranges.
Move all plugins up to baseline
-------------------------------
Key: JBIDE-8866
URL: https://issues.jboss.org/browse/JBIDE-8866
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Rob Stryker
Assignee: Nick Boldt
Fix For: 3.3.0.M2
Attachments: manifests.zip
Not really sure who to assign this to, short of making three dozen separate jira issues
;) I have 33 patches, one for each module, which modify all manifest.mf version numbers
(in plugins, not in tests) to be brought up to our current baseline.
So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a
dependency on this.specific.runtime into
this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads
this.specific.plugin;bundle-version="3.5.0", it will move it up to
this.specific.runtime;bundle-version="3.6.200".
Etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:52 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8866) Move all plugins up to baseline
[
https://issues.jboss.org/browse/JBIDE-8866?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-8866:
------------------------------------
I would like to stress that component owners should *REVIEW AND TEST* these paches, as
they have been generated via scripts and utility programs! Do not blindly commit a patch
without verifying it functions properly. While most will work, it is very possible some
are completely incorrect (such as the xulrunner ones) and do not apply.
Move all plugins up to baseline
-------------------------------
Key: JBIDE-8866
URL: https://issues.jboss.org/browse/JBIDE-8866
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Rob Stryker
Assignee: Nick Boldt
Fix For: 3.3.0.M2
Attachments: manifests.zip
Not really sure who to assign this to, short of making three dozen separate jira issues
;) I have 33 patches, one for each module, which modify all manifest.mf version numbers
(in plugins, not in tests) to be brought up to our current baseline.
So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a
dependency on this.specific.runtime into
this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads
this.specific.plugin;bundle-version="3.5.0", it will move it up to
this.specific.runtime;bundle-version="3.6.200".
Etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:37 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8866) Move all plugins up to baseline
[
https://issues.jboss.org/browse/JBIDE-8866?page=com.atlassian.jira.plugin...
]
Dmitry Geraskov updated JBIDE-8866:
-----------------------------------
Attachment: hibernate-tools.patch
Hibernate tools compiles nice with lower eclipse jars versions. But I am sure it will be
possible to use lower eclipse versions with newer jpa jars.
Updated patch attached
Move all plugins up to baseline
-------------------------------
Key: JBIDE-8866
URL: https://issues.jboss.org/browse/JBIDE-8866
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Rob Stryker
Assignee: Nick Boldt
Fix For: 3.3.0.M2
Attachments: hibernate-tools.patch, manifests.zip
Not really sure who to assign this to, short of making three dozen separate jira issues
;) I have 33 patches, one for each module, which modify all manifest.mf version numbers
(in plugins, not in tests) to be brought up to our current baseline.
So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a
dependency on this.specific.runtime into
this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads
this.specific.plugin;bundle-version="3.5.0", it will move it up to
this.specific.runtime;bundle-version="3.6.200".
Etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:39 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8866) Move all plugins up to baseline
[
https://issues.jboss.org/browse/JBIDE-8866?page=com.atlassian.jira.plugin...
]
Dmitry Geraskov commented on JBIDE-8866:
----------------------------------------
All the required jars are from Eclipse 3.6 except jpa. Should I try Eclipse 3.5, 3.4
installations or versions from Eclipse 3.6 are ok?
Move all plugins up to baseline
-------------------------------
Key: JBIDE-8866
URL: https://issues.jboss.org/browse/JBIDE-8866
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Rob Stryker
Assignee: Nick Boldt
Fix For: 3.3.0.M2
Attachments: hibernate-tools.patch, manifests.zip
Not really sure who to assign this to, short of making three dozen separate jira issues
;) I have 33 patches, one for each module, which modify all manifest.mf version numbers
(in plugins, not in tests) to be brought up to our current baseline.
So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a
dependency on this.specific.runtime into
this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads
this.specific.plugin;bundle-version="3.5.0", it will move it up to
this.specific.runtime;bundle-version="3.6.200".
Etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:29 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8866) Move all plugins up to baseline
[
https://issues.jboss.org/browse/JBIDE-8866?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8866:
-----------------------------------
Rob:
In order for this to have the correct visibility, I would think creation of 30+ subtask
jiras are in order, contained under this parent.
That way everyone gets a JIRA assigned to them which they can address.
Can you do so, since you're "owning" this baseline improvement and the
codegen/auditor stuff?
Move all plugins up to baseline
-------------------------------
Key: JBIDE-8866
URL: https://issues.jboss.org/browse/JBIDE-8866
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Rob Stryker
Assignee: Nick Boldt
Fix For: 3.3.0.M2
Attachments: hibernate-tools.patch, manifests.zip
Not really sure who to assign this to, short of making three dozen separate jira issues
;) I have 33 patches, one for each module, which modify all manifest.mf version numbers
(in plugins, not in tests) to be brought up to our current baseline.
So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a
dependency on this.specific.runtime into
this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads
this.specific.plugin;bundle-version="3.5.0", it will move it up to
this.specific.runtime;bundle-version="3.6.200".
Etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:17 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8866) Move all plugins up to baseline
[
https://issues.jboss.org/browse/JBIDE-8866?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-8866:
-------------------------------
Fix Version/s: 3.3.0.Final
(was: 3.3.0.M2)
Move all plugins up to baseline
-------------------------------
Key: JBIDE-8866
URL: https://issues.jboss.org/browse/JBIDE-8866
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.Final
Attachments: hibernate-tools.patch, manifests.zip
Not really sure who to assign this to, short of making three dozen separate jira issues
;) I have 33 patches, one for each module, which modify all manifest.mf version numbers
(in plugins, not in tests) to be brought up to our current baseline.
So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a
dependency on this.specific.runtime into
this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads
this.specific.plugin;bundle-version="3.5.0", it will move it up to
this.specific.runtime;bundle-version="3.6.200".
Etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:37 p.m.
New subject: [JBoss JIRA] (JBIDE-8866) Move all plugins up to baseline
[
https://issues.jboss.org/browse/JBIDE-8866?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-8866:
---------------------------------------
Fix Version/s: 3.4.0.M1
(was: 3.3.0.Final)
Assignee: Rob Stryker (was: Max Rydahl Andersen)
Rob - see Nick's comment.
Move all plugins up to baseline
-------------------------------
Key: JBIDE-8866
URL: https://issues.jboss.org/browse/JBIDE-8866
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.4.0.M1
Attachments: hibernate-tools.patch, manifests.zip
Not really sure who to assign this to, short of making three dozen separate jira issues
;) I have 33 patches, one for each module, which modify all manifest.mf version numbers
(in plugins, not in tests) to be brought up to our current baseline.
So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a
dependency on this.specific.runtime into
this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads
this.specific.plugin;bundle-version="3.5.0", it will move it up to
this.specific.runtime;bundle-version="3.6.200".
Etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:34 a.m.
New subject: [JBoss JIRA] (JBIDE-8866) Move all plugins up to baseline
[
https://issues.jboss.org/browse/JBIDE-8866?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-8866:
-------------------------------
Fix Version/s: 4.0.0.Alpha2
(was: 4.0.0.Alpha1)
Move all plugins up to baseline
-------------------------------
Key: JBIDE-8866
URL: https://issues.jboss.org/browse/JBIDE-8866
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha2
Attachments: hibernate-tools.patch, manifests.zip
Not really sure who to assign this to, short of making three dozen separate jira issues
;) I have 33 patches, one for each module, which modify all manifest.mf version numbers
(in plugins, not in tests) to be brought up to our current baseline.
So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a
dependency on this.specific.runtime into
this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads
this.specific.plugin;bundle-version="3.5.0", it will move it up to
this.specific.runtime;bundle-version="3.6.200".
Etc.
--
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
8:41 a.m.
New subject: [JBoss JIRA] (JBIDE-8866) Move all plugins up to baseline
[
https://issues.jboss.org/browse/JBIDE-8866?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-8866:
-------------------------------
Fix Version/s: 4.0.x
(was: 4.0.0.Alpha2)
Move all plugins up to baseline
-------------------------------
Key: JBIDE-8866
URL: https://issues.jboss.org/browse/JBIDE-8866
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.0.x
Attachments: hibernate-tools.patch, manifests.zip
Not really sure who to assign this to, short of making three dozen separate jira issues
;) I have 33 patches, one for each module, which modify all manifest.mf version numbers
(in plugins, not in tests) to be brought up to our current baseline.
So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a
dependency on this.specific.runtime into
this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads
this.specific.plugin;bundle-version="3.5.0", it will move it up to
this.specific.runtime;bundle-version="3.6.200".
Etc.
--
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:47 p.m.
New subject: [JBoss JIRA] (JBIDE-8866) Move all plugins up to baseline
[
https://issues.jboss.org/browse/JBIDE-8866?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-8866:
-------------------------------
Fix Version/s: LATER
(was: 4.0.x)
I am pushing this off until the next next release. As of now, our 4.0.0 will be targeting
Juno SR2, and so this jira no longer really makes sense.
However, as we move our processes to match the NEXT stream, this will become more
important. So, pushing this off to the unknown. :(
Move all plugins up to baseline
-------------------------------
Key: JBIDE-8866
URL: https://issues.jboss.org/browse/JBIDE-8866
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: LATER
Attachments: hibernate-tools.patch, manifests.zip
Not really sure who to assign this to, short of making three dozen separate jira issues
;) I have 33 patches, one for each module, which modify all manifest.mf version numbers
(in plugins, not in tests) to be brought up to our current baseline.
So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a
dependency on this.specific.runtime into
this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads
this.specific.plugin;bundle-version="3.5.0", it will move it up to
this.specific.runtime;bundle-version="3.6.200".
Etc.
--
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
4377
days inactive
4885
days old
jbosstools-issues@lists.jboss.org
10 comments
4 participants
participants (4)
-
Dmitry Geraskov (JIRA) -
Max Rydahl Andersen (JIRA)
-
Nick Boldt (JIRA)
-
Rob Stryker (JIRA)