2:23 p.m.
Gerard Ryan created JBIDE-12336:
-----------------------------------
Summary: org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
Key: JBIDE-12336
URL: https://issues.jboss.org/browse/JBIDE-12336
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Environment: Fedora
Reporter: Gerard Ryan
Assignee: Rob Stryker
As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for
Fedora, and the bundled jars in the lib/ directory of the
org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
The root of the issue is that Fedora packages disallow bundled dependencies; and when new
packages are being created, only the latest version of the software must be packaged. This
was not too much of a problem for the truezip dependency, even though some things did need
to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen
any activity in quite a while, and it depends on the seemingly obselete (this may not be
the best description) jboss-reflect. jboss-reflect, in its current state, cannot be
included in Fedora for reasons listed in the review for the package that I proposed for
it[3].
I'm trying to find the optimal solution to this problem. What I would really like to
know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there
anything else that would work as a dropin replacement, or any other workaround possible?
Since development of jbossxb seems dormant, not having to package it for Fedora would be
the best solution for me. I realise that it may be necessary though, but I thought I would
bring it up here, before I go looking for the jbossxb developers, in case my best case
scenario is a possibility!
Thanks in advance for any insight/help you can provide! :)
[1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
[2] http://truezip.java.net/migration.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=836404
--
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
12:38 a.m.
[
https://issues.jboss.org/browse/JBIDE-12336?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-12336:
-------------------------------------
The code for the archives plugin is very very old (think 6-7 years), and hasn't been
significantly modified in a LONG time. I was investigating the possibility of upgrading
some of the libs, but really I doubt anything would work as a 'drop in'
replacement. Whichever library is used would end up requiring substantial changes to
what's basically the core model of the plugin. ALso the test suite for the plugin is
a little lacking, which adds another danger point to simply swapping out what's going
on.
I am sure with some effort, replacing the jbossxb situation with simple raw xml reader
classes would work, but it'd take a bit of effort. Is there a timeline on your issue?
Any deadlines at all?
org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
------------------------------------------------------------------
Key: JBIDE-12336
URL: https://issues.jboss.org/browse/JBIDE-12336
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Environment: Fedora
Reporter: Gerard Ryan
Assignee: Rob Stryker
As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for
Fedora, and the bundled jars in the lib/ directory of the
org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
The root of the issue is that Fedora packages disallow bundled dependencies; and when new
packages are being created, only the latest version of the software must be packaged. This
was not too much of a problem for the truezip dependency, even though some things did need
to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen
any activity in quite a while, and it depends on the seemingly obselete (this may not be
the best description) jboss-reflect. jboss-reflect, in its current state, cannot be
included in Fedora for reasons listed in the review for the package that I proposed for
it[3].
I'm trying to find the optimal solution to this problem. What I would really like to
know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there
anything else that would work as a dropin replacement, or any other workaround possible?
Since development of jbossxb seems dormant, not having to package it for Fedora would be
the best solution for me. I realise that it may be necessary though, but I thought I would
bring it up here, before I go looking for the jbossxb developers, in case my best case
scenario is a possibility!
Thanks in advance for any insight/help you can provide! :)
[1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
[2] http://truezip.java.net/migration.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=836404
--
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
1:16 a.m.
[
https://issues.jboss.org/browse/JBIDE-12336?page=com.atlassian.jira.plugi...
]
Marek Goldmann commented on JBIDE-12336:
----------------------------------------
Speaking of timeline - we need to submit the Spin for a review at the end of the month, so
less than two weeks. But in this time we need to package everything else, not only solve
this small problem.
org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
------------------------------------------------------------------
Key: JBIDE-12336
URL: https://issues.jboss.org/browse/JBIDE-12336
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Environment: Fedora
Reporter: Gerard Ryan
Assignee: Rob Stryker
As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for
Fedora, and the bundled jars in the lib/ directory of the
org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
The root of the issue is that Fedora packages disallow bundled dependencies; and when new
packages are being created, only the latest version of the software must be packaged. This
was not too much of a problem for the truezip dependency, even though some things did need
to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen
any activity in quite a while, and it depends on the seemingly obselete (this may not be
the best description) jboss-reflect. jboss-reflect, in its current state, cannot be
included in Fedora for reasons listed in the review for the package that I proposed for
it[3].
I'm trying to find the optimal solution to this problem. What I would really like to
know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there
anything else that would work as a dropin replacement, or any other workaround possible?
Since development of jbossxb seems dormant, not having to package it for Fedora would be
the best solution for me. I realise that it may be necessary though, but I thought I would
bring it up here, before I go looking for the jbossxb developers, in case my best case
scenario is a possibility!
Thanks in advance for any insight/help you can provide! :)
[1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
[2] http://truezip.java.net/migration.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=836404
--
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
5:19 a.m.
[
https://issues.jboss.org/browse/JBIDE-12336?page=com.atlassian.jira.plugi...
]
Gerard Ryan commented on JBIDE-12336:
-------------------------------------
Looking into this a little further, even the jbossxb that is bundled here depends on
jboss-reflect, which seems to be the only thing that it depends on that isn't being
provided as a jar in that lib/ dir. I also can't find it anywhere else, which makes me
believe that it used to be provided by JBoss AS6...implying (to me anyway), that JBoss
Tools expects JBoss AS6 as a dependency. Does this make sense?
org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
------------------------------------------------------------------
Key: JBIDE-12336
URL: https://issues.jboss.org/browse/JBIDE-12336
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Environment: Fedora
Reporter: Gerard Ryan
Assignee: Rob Stryker
As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for
Fedora, and the bundled jars in the lib/ directory of the
org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
The root of the issue is that Fedora packages disallow bundled dependencies; and when new
packages are being created, only the latest version of the software must be packaged. This
was not too much of a problem for the truezip dependency, even though some things did need
to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen
any activity in quite a while, and it depends on the seemingly obselete (this may not be
the best description) jboss-reflect. jboss-reflect, in its current state, cannot be
included in Fedora for reasons listed in the review for the package that I proposed for
it[3].
I'm trying to find the optimal solution to this problem. What I would really like to
know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there
anything else that would work as a dropin replacement, or any other workaround possible?
Since development of jbossxb seems dormant, not having to package it for Fedora would be
the best solution for me. I realise that it may be necessary though, but I thought I would
bring it up here, before I go looking for the jbossxb developers, in case my best case
scenario is a possibility!
Thanks in advance for any insight/help you can provide! :)
[1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
[2] http://truezip.java.net/migration.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=836404
--
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
8:44 a.m.
[
https://issues.jboss.org/browse/JBIDE-12336?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-12336:
-------------------------------------
.implying (to me anyway), that JBoss Tools expects JBoss AS6 as a
dependency
We do not expect JBoss AS6 as a dependency at all. We found a jar that helped us turn our
xsd into an object model, and we used it as a standalone client lib that we liked and
found useful. The introduction to use JBoss XB was done a loooooooong time ago, about 6
years, so I don't think as6 was even around then ;)
All in all, project archives tools has never ever considered any app server as a
dependency. We just found a client lib that worked for us.
To be fair, I spent today investigating the issue. IT seems we can remove all of the
jboss-xb jars and their dependencies if I simply hard-code our reading of the xml file
through some custom model reader / parser, rather than using the jboss-xb schema-to-object
model. This would remove a lot of the free validation we get by using jboss-xb, but, the
model of the .packages file (the xml file in question) is pretty damn simple and does not
justify the use of a library and its several dependencies in all of these situations.
I can have a patch made, but I'd like to know the end-game here. Currently we've
just released jbt 3.3.1, and trunk is for jbt 3.4.0. So I'd like to know how we
proceed from here. Would you guys be requiring a patch build of some sort? Or is a .patch
file against svn trunk sufficient?
org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
------------------------------------------------------------------
Key: JBIDE-12336
URL: https://issues.jboss.org/browse/JBIDE-12336
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Environment: Fedora
Reporter: Gerard Ryan
Assignee: Rob Stryker
As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for
Fedora, and the bundled jars in the lib/ directory of the
org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
The root of the issue is that Fedora packages disallow bundled dependencies; and when new
packages are being created, only the latest version of the software must be packaged. This
was not too much of a problem for the truezip dependency, even though some things did need
to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen
any activity in quite a while, and it depends on the seemingly obselete (this may not be
the best description) jboss-reflect. jboss-reflect, in its current state, cannot be
included in Fedora for reasons listed in the review for the package that I proposed for
it[3].
I'm trying to find the optimal solution to this problem. What I would really like to
know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there
anything else that would work as a dropin replacement, or any other workaround possible?
Since development of jbossxb seems dormant, not having to package it for Fedora would be
the best solution for me. I realise that it may be necessary though, but I thought I would
bring it up here, before I go looking for the jbossxb developers, in case my best case
scenario is a possibility!
Thanks in advance for any insight/help you can provide! :)
[1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
[2] http://truezip.java.net/migration.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=836404
--
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:45 a.m.
[
https://issues.jboss.org/browse/JBIDE-12336?page=com.atlassian.jira.plugi...
]
Gerard Ryan commented on JBIDE-12336:
-------------------------------------
That sounds fantastic Rob! I'd definitely owe you one if you managed to get that
sorted! A patch file against svn would be perfectly fine for us! It's also not as
urgent for us right now, as we've temporarily worked around the problem by building a
very old version of jboss-reflect that doesn't contain the problems that we were
encountering with the later versions. Not having to depend on this would definitely be
preferable though.
I will also put up the changes I've made for truezip 7.5.5 when I get a chance, in
case you want to have a look at them/include them - there's probably stuff that
you'll want to change if you do decide to go with it! :)
org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
------------------------------------------------------------------
Key: JBIDE-12336
URL: https://issues.jboss.org/browse/JBIDE-12336
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Environment: Fedora
Reporter: Gerard Ryan
Assignee: Rob Stryker
As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for
Fedora, and the bundled jars in the lib/ directory of the
org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
The root of the issue is that Fedora packages disallow bundled dependencies; and when new
packages are being created, only the latest version of the software must be packaged. This
was not too much of a problem for the truezip dependency, even though some things did need
to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen
any activity in quite a while, and it depends on the seemingly obselete (this may not be
the best description) jboss-reflect. jboss-reflect, in its current state, cannot be
included in Fedora for reasons listed in the review for the package that I proposed for
it[3].
I'm trying to find the optimal solution to this problem. What I would really like to
know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there
anything else that would work as a dropin replacement, or any other workaround possible?
Since development of jbossxb seems dormant, not having to package it for Fedora would be
the best solution for me. I realise that it may be necessary though, but I thought I would
bring it up here, before I go looking for the jbossxb developers, in case my best case
scenario is a possibility!
Thanks in advance for any insight/help you can provide! :)
[1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
[2] http://truezip.java.net/migration.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=836404
--
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
12:05 a.m.
[
https://issues.jboss.org/browse/JBIDE-12336?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-12336:
--------------------------------
Attachment: JBIDE-12336.patch
Potential patch to read the xml directly, not using jboss-xb. Some work still needs to be
done to ensure no possible descriptors have regressions. Will investigate further but this
is a first patch
org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
------------------------------------------------------------------
Key: JBIDE-12336
URL: https://issues.jboss.org/browse/JBIDE-12336
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Environment: Fedora
Reporter: Gerard Ryan
Assignee: Rob Stryker
Attachments: JBIDE-12336.patch
As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for
Fedora, and the bundled jars in the lib/ directory of the
org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
The root of the issue is that Fedora packages disallow bundled dependencies; and when new
packages are being created, only the latest version of the software must be packaged. This
was not too much of a problem for the truezip dependency, even though some things did need
to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen
any activity in quite a while, and it depends on the seemingly obselete (this may not be
the best description) jboss-reflect. jboss-reflect, in its current state, cannot be
included in Fedora for reasons listed in the review for the package that I proposed for
it[3].
I'm trying to find the optimal solution to this problem. What I would really like to
know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there
anything else that would work as a dropin replacement, or any other workaround possible?
Since development of jbossxb seems dormant, not having to package it for Fedora would be
the best solution for me. I realise that it may be necessary though, but I thought I would
bring it up here, before I go looking for the jbossxb developers, in case my best case
scenario is a possibility!
Thanks in advance for any insight/help you can provide! :)
[1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
[2] http://truezip.java.net/migration.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=836404
--
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
12:07 a.m.
[
https://issues.jboss.org/browse/JBIDE-12336?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-12336:
-------------------------------------
glad to see you guys have a workaround for now. This allows us to put this in for next
version I guess... and gives us lots of time to regression test it
org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
------------------------------------------------------------------
Key: JBIDE-12336
URL: https://issues.jboss.org/browse/JBIDE-12336
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Environment: Fedora
Reporter: Gerard Ryan
Assignee: Rob Stryker
Attachments: JBIDE-12336.patch
As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for
Fedora, and the bundled jars in the lib/ directory of the
org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
The root of the issue is that Fedora packages disallow bundled dependencies; and when new
packages are being created, only the latest version of the software must be packaged. This
was not too much of a problem for the truezip dependency, even though some things did need
to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen
any activity in quite a while, and it depends on the seemingly obselete (this may not be
the best description) jboss-reflect. jboss-reflect, in its current state, cannot be
included in Fedora for reasons listed in the review for the package that I proposed for
it[3].
I'm trying to find the optimal solution to this problem. What I would really like to
know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there
anything else that would work as a dropin replacement, or any other workaround possible?
Since development of jbossxb seems dormant, not having to package it for Fedora would be
the best solution for me. I realise that it may be necessary though, but I thought I would
bring it up here, before I go looking for the jbossxb developers, in case my best case
scenario is a possibility!
Thanks in advance for any insight/help you can provide! :)
[1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
[2] http://truezip.java.net/migration.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=836404
--
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
1:17 p.m.
[
https://issues.jboss.org/browse/JBIDE-12336?page=com.atlassian.jira.plugi...
]
Gerard Ryan commented on JBIDE-12336:
-------------------------------------
Great stuff Rob, thanks a lot for responding so quickly to this!
org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
------------------------------------------------------------------
Key: JBIDE-12336
URL: https://issues.jboss.org/browse/JBIDE-12336
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Environment: Fedora
Reporter: Gerard Ryan
Assignee: Rob Stryker
Attachments: JBIDE-12336.patch
As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for
Fedora, and the bundled jars in the lib/ directory of the
org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
The root of the issue is that Fedora packages disallow bundled dependencies; and when new
packages are being created, only the latest version of the software must be packaged. This
was not too much of a problem for the truezip dependency, even though some things did need
to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen
any activity in quite a while, and it depends on the seemingly obselete (this may not be
the best description) jboss-reflect. jboss-reflect, in its current state, cannot be
included in Fedora for reasons listed in the review for the package that I proposed for
it[3].
I'm trying to find the optimal solution to this problem. What I would really like to
know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there
anything else that would work as a dropin replacement, or any other workaround possible?
Since development of jbossxb seems dormant, not having to package it for Fedora would be
the best solution for me. I realise that it may be necessary though, but I thought I would
bring it up here, before I go looking for the jbossxb developers, in case my best case
scenario is a possibility!
Thanks in advance for any insight/help you can provide! :)
[1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
[2] http://truezip.java.net/migration.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=836404
--
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
12:06 a.m.
[
https://issues.jboss.org/browse/JBIDE-12336?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-12336.
---------------------------------
Fix Version/s: 3.4.0.M1
Resolution: Done
This has been committed to 3.4.0.M1. This will not be propagated to 3.3.x because of the
change / removal of libs.
org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
------------------------------------------------------------------
Key: JBIDE-12336
URL: https://issues.jboss.org/browse/JBIDE-12336
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Environment: Fedora
Reporter: Gerard Ryan
Assignee: Rob Stryker
Fix For: 3.4.0.M1
Attachments: JBIDE-12336.patch
As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for
Fedora, and the bundled jars in the lib/ directory of the
org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
The root of the issue is that Fedora packages disallow bundled dependencies; and when new
packages are being created, only the latest version of the software must be packaged. This
was not too much of a problem for the truezip dependency, even though some things did need
to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen
any activity in quite a while, and it depends on the seemingly obselete (this may not be
the best description) jboss-reflect. jboss-reflect, in its current state, cannot be
included in Fedora for reasons listed in the review for the package that I proposed for
it[3].
I'm trying to find the optimal solution to this problem. What I would really like to
know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there
anything else that would work as a dropin replacement, or any other workaround possible?
Since development of jbossxb seems dormant, not having to package it for Fedora would be
the best solution for me. I realise that it may be necessary though, but I thought I would
bring it up here, before I go looking for the jbossxb developers, in case my best case
scenario is a possibility!
Thanks in advance for any insight/help you can provide! :)
[1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
[2] http://truezip.java.net/migration.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=836404
--
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
1:18 a.m.
[
https://issues.jboss.org/browse/JBIDE-12336?page=com.atlassian.jira.plugi...
]
Jaroslav Jankovič commented on JBIDE-12336:
-------------------------------------------
Rob could you provide some steps to reproduce, because I don't have any idea :) or you
could verify it by your own, thanks.
org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
------------------------------------------------------------------
Key: JBIDE-12336
URL: https://issues.jboss.org/browse/JBIDE-12336
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Environment: Fedora
Reporter: Gerard Ryan
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha1
Attachments: JBIDE-12336.patch
As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for
Fedora, and the bundled jars in the lib/ directory of the
org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
The root of the issue is that Fedora packages disallow bundled dependencies; and when new
packages are being created, only the latest version of the software must be packaged. This
was not too much of a problem for the truezip dependency, even though some things did need
to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen
any activity in quite a while, and it depends on the seemingly obselete (this may not be
the best description) jboss-reflect. jboss-reflect, in its current state, cannot be
included in Fedora for reasons listed in the review for the package that I proposed for
it[3].
I'm trying to find the optimal solution to this problem. What I would really like to
know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there
anything else that would work as a dropin replacement, or any other workaround possible?
Since development of jbossxb seems dormant, not having to package it for Fedora would be
the best solution for me. I realise that it may be necessary though, but I thought I would
bring it up here, before I go looking for the jbossxb developers, in case my best case
scenario is a possibility!
Thanks in advance for any insight/help you can provide! :)
[1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
[2] http://truezip.java.net/migration.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=836404
--
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
1:39 p.m.
[
https://issues.jboss.org/browse/JBIDE-12336?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-12336:
-------------------------------------
Basically, ensure that persisting (reading / writing) of project archives model is
consistent. So for example, if you create a java project with project archives enabled,
and the model has one set of expectations, then after a workspace restart they should all
be true.
If you create an archive named "blah.jpg" with output folder to
Project1/outputs, then on workspace restart it should still be true.
If you create an archive with a folder nested in it named "folder5", it should
still be there and named "folder5" after workspace restart.
What was changed here was the I/O of the model, reading and writing it.
org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
------------------------------------------------------------------
Key: JBIDE-12336
URL: https://issues.jboss.org/browse/JBIDE-12336
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Environment: Fedora
Reporter: Gerard Ryan
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha1
Attachments: JBIDE-12336.patch
As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for
Fedora, and the bundled jars in the lib/ directory of the
org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
The root of the issue is that Fedora packages disallow bundled dependencies; and when new
packages are being created, only the latest version of the software must be packaged. This
was not too much of a problem for the truezip dependency, even though some things did need
to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen
any activity in quite a while, and it depends on the seemingly obselete (this may not be
the best description) jboss-reflect. jboss-reflect, in its current state, cannot be
included in Fedora for reasons listed in the review for the package that I proposed for
it[3].
I'm trying to find the optimal solution to this problem. What I would really like to
know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there
anything else that would work as a dropin replacement, or any other workaround possible?
Since development of jbossxb seems dormant, not having to package it for Fedora would be
the best solution for me. I realise that it may be necessary though, but I thought I would
bring it up here, before I go looking for the jbossxb developers, in case my best case
scenario is a possibility!
Thanks in advance for any insight/help you can provide! :)
[1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
[2] http://truezip.java.net/migration.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=836404
--
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
7:13 a.m.
[
https://issues.jboss.org/browse/JBIDE-12336?page=com.atlassian.jira.plugi...
]
Jaroslav Jankovič closed JBIDE-12336.
-------------------------------------
Verified in JBT 4.0.0.Beta1-v20121013-1726-B25
org.jboss.ide.eclipse.archives.core bundles some old/obselete jars
------------------------------------------------------------------
Key: JBIDE-12336
URL: https://issues.jboss.org/browse/JBIDE-12336
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Environment: Fedora
Reporter: Gerard Ryan
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha1
Attachments: JBIDE-12336.patch
As detailed on the jbosstools-dev mailing list[1], I'm packaging JBoss Tools for
Fedora, and the bundled jars in the lib/ directory of the
org.jboss.ide.eclipse.archives.core plugin are causing me some trouble.
The root of the issue is that Fedora packages disallow bundled dependencies; and when new
packages are being created, only the latest version of the software must be packaged. This
was not too much of a problem for the truezip dependency, even though some things did need
to be changed for it, as detailed in the truezip migration from v6 to v7 guide[2].
It didn't work so well for the jbossxb dependency, however. jbossxb hasn't seen
any activity in quite a while, and it depends on the seemingly obselete (this may not be
the best description) jboss-reflect. jboss-reflect, in its current state, cannot be
included in Fedora for reasons listed in the review for the package that I proposed for
it[3].
I'm trying to find the optimal solution to this problem. What I would really like to
know from the JBoss Tools perspective is: How crucial to this plugin is jbossxb? Is there
anything else that would work as a dropin replacement, or any other workaround possible?
Since development of jbossxb seems dormant, not having to package it for Fedora would be
the best solution for me. I realise that it may be necessary though, but I thought I would
bring it up here, before I go looking for the jbossxb developers, in case my best case
scenario is a possibility!
Thanks in advance for any insight/help you can provide! :)
[1] http://lists.jboss.org/pipermail/jbosstools-dev/2012-July/005548.html
[2] http://truezip.java.net/migration.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=836404
--
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
4284
days inactive
4375
days old
jbosstools-issues@lists.jboss.org
12 comments
4 participants
participants (4)
-
Gerard Ryan (JIRA) -
Jaroslav Jankovič (JIRA)
-
Marek Goldmann (JIRA)
-
Rob Stryker (JIRA)