[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18837:
------------------------------------
PR for master branch; same concept for Base in 4.2.x branch: https://github.com/jbosstools/jbosstools-base/pull/360
> because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18837
> URL: https://issues.jboss.org/browse/JBIDE-18837
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, central, common/jst/core, project-examples
> Affects Versions: 4.2.1.CR1
> Reporter: Nick Boldt
> Fix For: 4.3.0.Alpha1
>
>
> When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples.
> Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating.
> And we need to use the maven enforcer plugin to fail the build if these versions get out of sync.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3208 at 12/1/14 5:04 PM:
-----------------------------------------------------------
Based on side conversation (w/ Max) re: JBIDE-18833:
* we need to provide an update site that is a *composite of multiple nightly builds*, updates/\*/snapshots/
* this URL must in fact be a *symlink* to builds/\*/snapshots/ (or builds/<jobname>/) so that the N latest builds can be accessed from a single URL
* we must ensure that the cleanup script [1] is amended to perform deletes in these new folders, too.
[1] http://hudson.qa.jboss.com/hudson/job/jbosstools-cleanup/
was (Author: nickboldt):
Based on side conversation w/ Max re: JBIDE-18833:
To provide an update site that is a *composite of multiple nightly builds*, updates/\*/snapshots/ must in fact be a *symlink* to builds/\*/snapshots/ (or builds/<jobname>/) so that the N latest builds can be accessed from a single URL. And we'll have to ensure that the cleanup script [1] is amended to perform deletes in these new folders, too.
[1] http://hudson.qa.jboss.com/hudson/job/jbosstools-cleanup/
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha1
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> {code}
> download.jboss.org
> <earlyaccess,updates,discovery>/mars
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/mars/stable is a pointer back into updates/mars)
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last 2 builds
> targetplatforms/<type>/<version>
> {code}
> and
> {code}
> devstudio.redhat.com
> <earlyaccess,updates,discovery>/9.0
> /snapshots
> /staging
> /development
> /stable (updates/9.0/stable is a pointer back into updates/9.0)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last 2 builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18856) Fix forge build from master
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-18856:
-------------------------------------
Summary: Fix forge build from master
Key: JBIDE-18856
URL: https://issues.jboss.org/browse/JBIDE-18856
Project: Tools (JBoss Tools)
Issue Type: Task
Components: forge
Affects Versions: 4.3.0.Alpha1
Reporter: Denis Golovin
Build is failing with output,it seems some artifacts are not available from maven repository. It works fine when use latest commit with final version of forge runtime.
{code}[INFO] [INFO] Installation request for [org.jboss.forge.addon:core,2.12.3-SNAPSHOT] will:
[INFO] Deploy: [org.jboss.forge.addon:core,2.12.3-SNAPSHOT]
[INFO]
[INFO] Downloading: http://repo1.maven.org/maven2/org/jboss/forge/addon/core/2.12.3-SNAPSHOT/...
[INFO]
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Reactor Summary:
[INFO] [INFO]
...
[INFO] [INFO] jbosstools-forge ................................... SUCCESS [ 0.002 s]
[INFO] [INFO] forge.plugins ...................................... SUCCESS [ 0.002 s]
[INFO] [INFO] org.jboss.tools.aesh.runtime ....................... SUCCESS [ 0.045 s]
[INFO] [INFO] org.jboss.tools.aesh.core .......................... SUCCESS [ 0.123 s]
[INFO] [INFO] org.jboss.tools.aesh.ui ............................ SUCCESS [ 0.120 s]
[INFO] [INFO] org.jboss.tools.aesh.example ....................... SUCCESS [ 0.110 s]
[INFO] [INFO] org.jboss.tools.forge2.runtime ..................... FAILURE [ 9.596 s]
[INFO] [INFO] org.jboss.tools.forge.core ......................... SKIPPED
[INFO] [INFO] org.jboss.tools.forge.core.ext ..................... SKIPPED
[INFO] [INFO] org.jboss.tools.forge.m2e .......................... SKIPPED
[INFO] [INFO] org.jboss.tools.forge.runtime ...................... SKIPPED
[INFO] [INFO] org.jboss.tools.forge.runtime.ext .................. SKIPPED
[INFO] [INFO] org.jboss.tools.forge.ui.notifications ............. SKIPPED
[INFO] [INFO] org.jboss.tools.forge.ui ........................... SKIPPED
[INFO] [INFO] org.jboss.tools.forge.ui.ext ....................... SKIPPED
[INFO] [INFO] forge.tests ........................................ SKIPPED
[INFO] [INFO] org.jboss.tools.aesh.core.test ..................... SKIPPED
[INFO] [INFO] org.jboss.tools.aesh.ui.test ....................... SKIPPED
[INFO] [INFO] org.jboss.tools.forge.core.test .................... SKIPPED
[INFO] [INFO] org.jboss.tools.forge.core.ext.test ................ SKIPPED
[INFO] [INFO] org.jboss.tools.forge.ui.test ...................... SKIPPED
[INFO] [INFO] org.jboss.tools.forge.ui.ext.test .................. SKIPPED
[INFO] [INFO] forge.features ..................................... SKIPPED
[INFO] [INFO] org.jboss.tools.forge.m2e.feature .................. SKIPPED
[INFO] [INFO] org.jboss.tools.forge.feature ...................... SKIPPED
[INFO] [INFO] org.jboss.tools.forge.ext.feature .................. SKIPPED
[INFO] [INFO] org.jboss.tools.forge.test.feature ................. SKIPPED
[INFO] [INFO] org.jboss.tools.forge.ext.test.feature ............. SKIPPED
[INFO] [INFO] forge.site ......................................... SKIPPED
...
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Total time: 12:46 min
[INFO] [INFO] Finished at: 2014-12-01T12:45:27-08:00
[INFO] [INFO] Final Memory: 931M/3005M
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] Failed to execute goal org.jboss.forge.furnace:furnace-maven-plugin:2.12.3-SNAPSHOT:addon-install (deploy-addons) on project org.jboss.tools.forge2.runtime: Execution deploy-addons of goal org.jboss.forge.furnace:furnace-maven-plugin:2.12.3-SNAPSHOT:addon-install failed: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact org.jboss.forge.addon:core:jar:forge-addon:2.12.3-SNAPSHOT in central (http://repo1.maven.org/maven2) -> [Help 1]
[INFO] [ERROR]
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[INFO] [ERROR]
[INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[INFO] [ERROR]
[INFO] [ERROR] After correcting the problems, you can resume the build with the command
[INFO] [ERROR] mvn <goals> -rf :org.jboss.tools.forge2.runtime
[INFO] ..FAILED (771.9 s)
[INFO] The build exited with code 1. See /dev/shm/jbds-releng/jbosstools-dev/build.log for details.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3208:
-----------------------------
Comment: was deleted
(was: To be clear - the requirement is not necessarily that it is a composite of multiple nightly builds; it is just the simplest way I know of providing a *stable* url for the release train that does not change just because our branch name changes.
i.e. /luna/nightly vs first its called luna/master then /luna/4.2.x
And no, this does not mean I think master and 4.2.x are bad names for internal sanity - but the url we make public for nightly and/or snapshot testing makes sense to follow similar layout as our staging, development and stable sites for two reasons:
A) so users/testers/developers don't need to changed URL's in their test eclipse installs
B) the sites we test/build are as close to the real published content.
)
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha1
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> {code}
> download.jboss.org
> <earlyaccess,updates,discovery>/mars
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/mars/stable is a pointer back into updates/mars)
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last 2 builds
> targetplatforms/<type>/<version>
> {code}
> and
> {code}
> devstudio.redhat.com
> <earlyaccess,updates,discovery>/9.0
> /snapshots
> /staging
> /development
> /stable (updates/9.0/stable is a pointer back into updates/9.0)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last 2 builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months