[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23322:
-------------------------------
Sprint: devex #128 February 2017, devex #131 May 2017 (was: devex #128 February 2017)
> create mojo that takes as input a list of URLs and a name, and generates a composite site
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-23322
> URL: https://issues.jboss.org/browse/JBIDE-23322
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.Final
>
>
> In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 1 or more URLs.
> So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce three files:
> {code}
> target/composite/compositeContent.xml
> target/composite/compositeArtifacts.xml
> target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index )
> {code}
> Secondary use case would be to generate a composite site from subfolders in an existing folder, eg., to replace https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u...
> So we could use this to create composite sites in folders like:
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/core/ (invalid composite points to ../, which has no composite either)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/central/ (no composite)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/earlyaccess/ (no composite)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/integrati... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ (up to date)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/core/ (invalid composite points to ../, which has no composite either)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/cent... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/earl... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/inte... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/core... (composite out of date)
> But also to point to remote (/stable/) URLs from pointer sites, like:
> * http://download.jboss.org/jbosstools/neon/stable/updates/compositeArtifac... (up to date, name = JBoss Tools - Core + Central Update Site)
> * http://download.jboss.org/jbosstools/neon/stable/updates/central/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/stable/updates/earlyaccess/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/stable/updates/coretests/compos... (up to date, name = JBoss Tools 4.4.2.Final Stable Release Tests Site)
> * http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests (404'd)
> * http://download.jboss.org/jbosstools/neon/development/updates/compositeAr... (up to date, name = JBoss Tools - Core + Central Update Site)
> * http://download.jboss.org/jbosstools/neon/development/updates/central/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/development/updates/earlyaccess/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/development/updates/coretests/c... (out of date, points to 4.4.0.Alpha1)
> * http://download.jboss.org/jbosstools/neon/development/updates/integration... (404'd)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24121) Update versionwatch for devstudio 11 - document/update known multiples & report upstream problems to Eclipse CVS, Help, WST
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24121?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24121:
-------------------------------
Sprint: devex #131 May 2017 (was: devex #130 April 2017)
> Update versionwatch for devstudio 11 - document/update known multiples & report upstream problems to Eclipse CVS, Help, WST
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24121
> URL: https://issues.jboss.org/browse/JBIDE-24121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa, versionwatch
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.AM1
>
> Attachments: Screenshot_2017-03-21_12-37-07.png, version-decreased.png
>
>
> {code}
> Version Watch - Summary Report: devstudio-11.0.0.AM1
> Multiple version issues
> Feature Problem Reference Version(s)
> Plugin Problem Reference Version(s)
> org.slf4j.api Multiple versions of same bundle found! 1.7.2.v20121108-1250 1.7.10.v20160921-1923
> org.apache.httpcomponents.httpcore Multiple versions of same bundle found! 4.3.3.v201411290715 4.4.4.v20161115-1643
> org.apache.httpcomponents.httpclient Multiple versions of same bundle found! 4.3.6.v201511171540 4.5.2.v20161115-1643
> Ignored (known issue)
> org.apache.lucene.core Multiple versions of bundle are expected and ignored - {3.5.0,5.4.1} 3.5.0.v20120725-1805 6.1.0.v20161115-1612
> javax.wsdl Multiple versions of bundle are expected and ignored - {1.5.1,1.6.2} 1.5.1.v201012040544 1.6.2.v201012040545
> com.jcraft.jsch Multiple versions of bundle are expected and ignored - {0.1.50,0.1.51} 0.1.53.v201508180515 0.1.54.v20170116-1932
> org.eclipse.jdt.annotation Multiple versions of bundle are expected and ignored - {1.1.0,2.1.0} 1.1.100.v20160418-1457 2.1.0.v20170119-1701
> org.objectweb.asm Multiple versions of bundle are expected and ignored - {4.0.0,5.0.1} 4.0.0.v201302062210 5.0.1.v201404251740
> org.apache.commons.logging Multiple versions of bundle are expected and ignored - {1.0.4,1.1.1} 1.0.4.v201101211617 1.1.1.v201101211721
> com.google.guava Multiple versions of bundle are expected and ignored - 13.0.0,15.0.0 15.0.0.v201403281430 18.0.0.v20161115-1643
> Version decreased issues
> Feature Problem Reference Version(s)
> org.eclipse.cvs Version 1.4.300.v20170126-1030 must be higher than 1.4.301.v20161124-1400 1.4.301.v20161124-1400
> org.eclipse.help Version 2.2.0.v20170126-1030 must be higher than 2.2.1.v20161124-1400 2.2.1.v20161124-1400
> Plugin Problem Reference Version(s)
> org.eclipse.cvs Version 1.4.300.v20170126-1030 must be higher than 1.4.301.v20161124-1400 1.4.301.v20161124-1400
> org.eclipse.wst.server.ui Version 1.5.306.v201610202117 must be higher than 1.5.307.v201611072017 1.5.307.v201611072017
>
> 7 issues found.{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24225) publish p2diff app to Nexus for easier use in jenkins jobs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24225?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24225:
-------------------------------
Sprint: (was: devex #130 April 2017)
> publish p2diff app to Nexus for easier use in jenkins jobs
> ----------------------------------------------------------
>
> Key: JBIDE-24225
> URL: https://issues.jboss.org/browse/JBIDE-24225
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.x
>
> Attachments: maven-releng-fetch.png
>
>
> Rather than bootstrapping by hand and having to reference p2diff like this:
> {code}
> p2diff=/home/hudson/static_build_env/jbds/p2diff/x86$(if [[ $(uname -a | grep x86_64) ]]; then echo _64; fi)/p2diff
> {code}
> It would be way better if we could just fetch it via a maven step (as we do for other releng scripts) ...
> !maven-releng-fetch.png|thumbnail!
> ... and automatically unpack it to the workspace.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4362:
-----------------------------
Sprint: devex #131 May 2017 (was: devex #130 April 2017)
> Consider eliminating the devstudio EAP installer bundle?
> --------------------------------------------------------
>
> Key: JBDS-4362
> URL: https://issues.jboss.org/browse/JBDS-4362
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, integration-platform
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM1
>
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
> That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months