[
https://issues.jboss.org/browse/JBIDE-11734?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11734:
------------------------------------
(2012-05-30 12:30:03) nboldt: anyway, I agree w/ your idea to instead of generating a p2
mirror script from the .target file that you instead generate a category.xml file
(2012-05-30 12:30:14) nboldt: HOWEVER... can the category.xml file include plugins as well
as features?
(2012-05-30 12:30:25) nboldt: because our TP is plugins and features, not just features
(2012-05-30 12:30:47) nboldt: or would you then have to generate BOTH category.xml and
p2.inf to handle the two types of IUs?
(2012-05-30 12:30:56) nboldt: and ultimately, what would this get us?
(2012-05-30 12:31:07) mistria: no, it can't, but we can set up a
"featurelessBundlesHostFeature" for bundles that are not part of a feature
NOW:
(2012-05-30 12:31:17) nboldt: p2 mirror script == runnable artifact w/ a list of IUs and
the site from which to get them
PROPOSED:
(2012-05-30 12:31:37) nboldt: category.xml + pom.xml + p2.inf == runnable artifacts w/ a
list of IUs and the site from which to get them
(2012-05-30 12:31:56) nboldt: I see more metadata, resulting in the same thing (a p2
repo)
(2012-05-30 12:32:05) nboldt: what is the benefit here?
(2012-05-30 12:32:15) mistria: I've never succeeded to get p2.inf to work well, but if
it can solve this, we should use it
(2012-05-30 12:32:33) mistria: the benefit would be a more straightforward approach
(2012-05-30 12:32:48) mistria: people would be able to build TP site locally with a
"mvn install"
This already works.
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.target-platfor...
{code} cd ~/33x/build/target-platform; mvn install -Pget.local.target {code}
(2012-05-30 12:33:29) mistria: and we have a single entry point for customization of TP
site
What about
https://svn.jboss.org/repos/jbosstools/trunk/build/target-platform/unifie... ?
(2012-05-30 12:33:33) mistria: which would be category.xml
Which you'd have to generate in order to keep in sync w/ the .target file, or else
would result in duplication of effort/maintenance.
(2012-05-30 12:35:16) mistria: nboldt: also, we could easily put TP site and .target file
build/publishing into Jenkins
We already do this:
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.target-platfor...
Create TP site using an "eclipse-repository",
<repositories> and category.xml
-----------------------------------------------------------------------------
Key: JBIDE-11734
URL:
https://issues.jboss.org/browse/JBIDE-11734
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.4.0.M1
Instead of parsing and tweaking a .target file to generate the "requirement"
repository, we could make it a normal "eclipse-repository" artifact. We would
manage versions in it.
Then we know the versions of deps in that site, and we can create target platform using
0.0.0 for versions since we are sure they are resolved against our 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