7:08 a.m.
Mickael Istria created JBIDE-11733:
--------------------------------------
Summary: unified.target and JBoss site not in sync for logback version
Key: JBIDE-11733
URL: https://issues.jboss.org/browse/JBIDE-11733
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 3.3.0.CR1
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Requirements site contains logback 1.0.0 whereas unified.target requests 0.9.27.
We should automate a way to validate that unified.target can be used with latest
requirement site.
--
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
noon
[
https://issues.jboss.org/browse/JBIDE-11733?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11733:
------------------------------------
We do, but there's a glitch in it somehow where often the stuff that ends up in the TP
!= the stuff in the composite reqs mirror.
Run this:
cd ~/trunk/build/target-platform
mvn clean install -Pget.local.target # get multiple.target and unified.target updated
ant jbds # get jbds.target updated
unified.target and JBoss site not in sync for logback version
-------------------------------------------------------------
Key: JBIDE-11733
URL: https://issues.jboss.org/browse/JBIDE-11733
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 3.3.0.CR1
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Requirements site contains logback 1.0.0 whereas unified.target requests 0.9.27.
We should automate a way to validate that unified.target can be used with latest
requirement site.
--
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:36 a.m.
[
https://issues.jboss.org/browse/JBIDE-11733?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11733:
----------------------------------------
No more trouble with logback, now m2e prevent from consuming target-platforms directly...
mvn clean install -Pget.local.target # get multiple.target and
unified.target updated
It take hours to complete. I really feel more efficient with consuming directly
target-platforms without installing them locally on each change.
unified.target and JBoss site not in sync for logback version
-------------------------------------------------------------
Key: JBIDE-11733
URL: https://issues.jboss.org/browse/JBIDE-11733
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 3.3.0.CR1
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Requirements site contains logback 1.0.0 whereas unified.target requests 0.9.27.
We should automate a way to validate that unified.target can be used with latest
requirement site.
--
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:46 a.m.
[
https://issues.jboss.org/browse/JBIDE-11733?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11733:
------------------------------------
- rebuilding incrementally (to adopt changes): mere minutes (under 10)
- downloading the whole damn thing again: hours
Me, I prefer incremental changes to the TP, but of course YMMV.
unified.target and JBoss site not in sync for logback version
-------------------------------------------------------------
Key: JBIDE-11733
URL: https://issues.jboss.org/browse/JBIDE-11733
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 3.3.0.CR1
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Requirements site contains logback 1.0.0 whereas unified.target requests 0.9.27.
We should automate a way to validate that unified.target can be used with latest
requirement site.
--
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:56 a.m.
[
https://issues.jboss.org/browse/JBIDE-11733?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11733:
----------------------------------------
We do, but there's a glitch in it somehow where often the stuff
that ends up in the TP != the stuff in the composite reqs mirror.
Is it because of
the planner vs slicer issue? Target platform are "planner" (exact versions)
whereas site is created using "slicer" (best versions), aren't they?
I think on a longer term approach, it could be cleaner to produce site first (with a
category.xml) and then target platforms containing version 0.0.0 when there is no
ambiguity, as we already discussed.
unified.target and JBoss site not in sync for logback version
-------------------------------------------------------------
Key: JBIDE-11733
URL: https://issues.jboss.org/browse/JBIDE-11733
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 3.3.0.CR1
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Requirements site contains logback 1.0.0 whereas unified.target requests 0.9.27.
We should automate a way to validate that unified.target can be used with latest
requirement site.
--
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
10:03 a.m.
[
https://issues.jboss.org/browse/JBIDE-11733?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11733:
------------------------------------
Pulling content via p2.mirror: can run either in "get latest" or "get
specific" modes:
https://svn.jboss.org/repos/jbosstools/trunk/build/target-platform/unifie...
(useLatest = true/false; generally runs in "useLatest=true" mode)
However, the resulting target file contains *specific versions* (mostly):
https://svn.jboss.org/repos/jbosstools/trunk/build/target-platform/unifie...
(xulrunner and xpcom are included but no versions are specified so that the latest respin
in the composite site can be included)
unified.target and JBoss site not in sync for logback version
-------------------------------------------------------------
Key: JBIDE-11733
URL: https://issues.jboss.org/browse/JBIDE-11733
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 3.3.0.CR1
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Requirements site contains logback 1.0.0 whereas unified.target requests 0.9.27.
We should automate a way to validate that unified.target can be used with latest
requirement site.
--
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
10:32 a.m.
[
https://issues.jboss.org/browse/JBIDE-11733?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11733:
----------------------------------------
So that means that useLatest=true introduce a risk to have wrong sync between site and
TPs. Then why don't we simply set it to false to be sure we always have TP working
well?
unified.target and JBoss site not in sync for logback version
-------------------------------------------------------------
Key: JBIDE-11733
URL: https://issues.jboss.org/browse/JBIDE-11733
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 3.3.0.CR1
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Requirements site contains logback 1.0.0 whereas unified.target requests 0.9.27.
We should automate a way to validate that unified.target can be used with latest
requirement site.
--
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
11:34 a.m.
[
https://issues.jboss.org/browse/JBIDE-11733?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11733:
------------------------------------
No, I use useLatest=true to get the latest versions available from the mirror, then update
the .target file to reflect those versions.
There is a glitch somewhere in the script, though; sometimes the target file reverts to an
older version from what's latest. I suspect it only happens when I have a TP site
which was updated from an older baseline rather than generating it fresh, but I
haven't fully tested/verified that theory.
unified.target and JBoss site not in sync for logback version
-------------------------------------------------------------
Key: JBIDE-11733
URL: https://issues.jboss.org/browse/JBIDE-11733
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 3.3.0.CR1
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Requirements site contains logback 1.0.0 whereas unified.target requests 0.9.27.
We should automate a way to validate that unified.target can be used with latest
requirement site.
--
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:57 a.m.
[
https://issues.jboss.org/browse/JBIDE-11733?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11733:
----------------------------------------
Target Platforms have to be maintained and always working if we want people to use them in
their IDE and to use them for builds. But it is lacking tools to be able to ensure their
consistency.
I suggested this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=378987
unified.target and JBoss site not in sync for logback version
-------------------------------------------------------------
Key: JBIDE-11733
URL: https://issues.jboss.org/browse/JBIDE-11733
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 3.3.0.CR1
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.3.0.CR1
Requirements site contains logback 1.0.0 whereas unified.target requests 0.9.27.
We should automate a way to validate that unified.target can be used with latest
requirement site.
--
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:29 p.m.
[
https://issues.jboss.org/browse/JBIDE-11733?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-11733:
-------------------------------
Fix Version/s: 3.3.1
(was: 3.3.0.CR1)
No runway left to do this for 3.3.0
unified.target and JBoss site not in sync for logback version
-------------------------------------------------------------
Key: JBIDE-11733
URL: https://issues.jboss.org/browse/JBIDE-11733
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 3.3.0.CR1
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.3.1
Requirements site contains logback 1.0.0 whereas unified.target requests 0.9.27.
We should automate a way to validate that unified.target can be used with latest
requirement site.
--
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:31 p.m.
[
https://issues.jboss.org/browse/JBIDE-11733?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-11733:
-------------------------------
Fix Version/s: 3.3.2
3.4.0.M1
(was: 3.3.1)
Assignee: Mickael Istria (was: Nick Boldt)
Slip.
unified.target and JBoss site not in sync for logback version
-------------------------------------------------------------
Key: JBIDE-11733
URL: https://issues.jboss.org/browse/JBIDE-11733
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 3.3.0.CR1
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 3.3.2, 3.4.0.M1
Requirements site contains logback 1.0.0 whereas unified.target requests 0.9.27.
We should automate a way to validate that unified.target can be used with latest
requirement site.
--
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
6:43 a.m.
[
https://issues.jboss.org/browse/JBIDE-11733?page=com.atlassian.jira.plugi...
]
Mickael Istria closed JBIDE-11733.
----------------------------------
Resolution: Cannot Reproduce Bug
Was fixed in the past, cannot reproduce any longer
unified.target and JBoss site not in sync for logback version
-------------------------------------------------------------
Key: JBIDE-11733
URL: https://issues.jboss.org/browse/JBIDE-11733
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 3.3.0.CR1
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 3.3.2, 3.4.0.M1
Requirements site contains logback 1.0.0 whereas unified.target requests 0.9.27.
We should automate a way to validate that unified.target can be used with latest
requirement site.
--
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
5015
days inactive
5086
days old
jbosstools-issues@lists.jboss.org
11 comments
2 participants
participants (2)
-
Mickael Istria (JIRA) -
Nick Boldt (JIRA)