[JBoss JIRA] (JBIDE-13334) LinkageError in bot test after installing slf4j
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBIDE-13334:
-----------------------------------------
Summary: LinkageError in bot test after installing slf4j
Key: JBIDE-13334
URL: https://issues.jboss.org/browse/JBIDE-13334
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: QA
Affects Versions: 4.0.0.Final
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Attachments: error.txt
After installing the following libraries into eclipse:
slf4j.api.jar
slf4j.simple.jar
log4j.over.slf4j.jar
the LinkageError occurs during running bot test (see the attachment)
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13326) include Juno SR1+ performance fix in target platform? new connector on Central? In Installer?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13326?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13326:
------------------------------------
Decision made. Will only update Central discovery plugins to add a new connector, and update the Central sites to include a mirror of the feature.
{quote}
(2012-12-21 09:42:15) maxandersen: nickboldt: nickboldt: my hope was that by adding to updatesite users would get an "updates available" but that wont work since this is a feature patch not an actual update.
(2012-12-21 09:42:27) nickboldt: bingo
(2012-12-21 09:42:40) maxandersen: mistria: yes, that is why I wanted it easily available.
(2012-12-21 09:43:40) nickboldt: maxandersen: only way to force it on users is w/ a respin of one of our features which would include it
(2012-12-21 09:43:47) nickboldt: eg., the JBDS Core Features feature
(2012-12-21 09:43:36) maxandersen: nickboldt: so does this require new build of anything but central discovery plugin + add line into the central composite ?
(2012-12-21 09:44:00) nickboldt: just. the. discovery plugin
(2012-12-21 09:44:10) nickboldt: (simplest solution to making it VISIBLE)
(2012-12-21 09:44:32) maxandersen: nickboldt: what site would the connector point to if the central composite is not changed?
(2012-12-21 09:45:02) nickboldt: I would add http://download.jboss.org/jbosstools/updates/requirements/eclipse/4.2.1.v... to the JBT and JBDS Central sites
(2012-12-21 09:45:25) nickboldt: then point JBT and JBDS central disco plugins at the standard place and have it discover the new feature
(2012-12-21 09:45:45) nickboldt: minimal change. single plugin.xml would be changed for both JBT and JBDS versions of central
(2012-12-21 09:45:58) maxandersen: nickboldt: okey so its respin of discovery plugin + add line into the central composite, right?
(2012-12-21 09:46:14) maxandersen: i like that - wouldn't even be a 6.0.1 then ;)
(2012-12-21 09:46:18) nickboldt: right.
(2012-12-21 09:44:21) nickboldt: but if you want it force-installed into the installer, we need to rebuild the installer
(2012-12-21 09:45:08) maxandersen: nickboldt: no, im not talking about doing a full isntaller build - thats for when we do 6.0.x that picks up the new SR
{quote}
> include Juno SR1+ performance fix in target platform? new connector on Central? In Installer?
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-13326
> URL: https://issues.jboss.org/browse/JBIDE-13326
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, target-platform, updatesite
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.0.1.Final
>
>
> Info: https://bugs.eclipse.org/bugs/show_bug.cgi?id=385272, http://wiki.eclipse.org/Platform_UI/Juno_Performance_Investigation
> Update Site: http://download.eclipse.org/eclipse/updates/4.2 --> Eclipse UI Juno SR1 Optimizations should be installed
> For Juno SR2 maintenance builds >= Nov 21, patch feature not needed.
> We could also consider setting these vmargs when installing JBT (community cental feature?) and/or JBDS BYOE:
> {code}
> -Xmn128m
> -Xms1024m
> -Xmx1024m
> -Xss2m
> -XX:PermSize=256m
> -XX:MaxPermSize=384m
> {code}
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13333) Fixing Eclipse/Kepler
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-13333:
-------------------------------------------
Summary: Fixing Eclipse/Kepler
Key: JBIDE-13333
URL: https://issues.jboss.org/browse/JBIDE-13333
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: UpStream
Reporter: Max Rydahl Andersen
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 4.1.0.Alpha1
"container" issue for issues related to fixes important to get into Kepler.
Please link your Eclipse/Kepler issue to this one instead of using subtasks.
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13232:
----------------------------------------
> is it not normal to have a branch use -SNAPSHOT for development?
Yes it is.
> so i'm not following why you mean by "complex operations cannot be made in a single step" ?
It means that we need a branch when setting up a new TP, since we can have several related commits. When we think it's ok, we remove SNAPSHOT, push to Nexus, and tag on Git
> will the target platform stay in jbosstools-build ?
For the moment yes, but I think it may change within the next monthes ;)
> what names will be used for tags/branches here ?
"target-platform-<version>"
> how will it relate to the parent if that is still in here ?
It does not relate, parent references a version of target-platform, but target-platforms are independent from parent.
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13232:
---------------------------------------------
is it not normal to have a branch use -SNAPSHOT for development?
so i'm not following why you mean by "complex operations cannot be made in a single step" ?
will the target platform stay in jbosstools-build ? what names will be used for tags/branches here ? how will it relate to the parent if that is still in here ?
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 4 months