[JBoss JIRA] (JBIDE-24534) Aeri connection problems on startup of devstudio / lucene issue?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24534?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24534:
-------------------------------
Summary: Aeri connection problems on startup of devstudio / lucene issue? (was: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out.)
> Aeri connection problems on startup of devstudio / lucene issue?
> ----------------------------------------------------------------
>
> Key: JBIDE-24534
> URL: https://issues.jboss.org/browse/JBIDE-24534
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aeri, central-update
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.x
>
>
> Having installed devstudio 11.0.0.AM1 into Oxygen.0.M7 JavaEE EPP bundle on Linux x64 (Fedora 24), I tried to install something from Central and instead got an AERI error:
> {code}
> !ENTRY org.eclipse.epp.logging.aeri.ide 2 17 2017-06-02 15:15:10.111
> !MESSAGE Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.5.v20170531-0951
> !STACK 0
> org.apache.http.conn.ConnectTimeoutException: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:150)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.apache.http.client.fluent.Request.internalExecute(Request.java:173)
> at org.apache.http.client.fluent.Executor.execute(Executor.java:262)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.request(IO.java:170)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.refreshConfiguration(IO.java:64)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.startUp(ServerConnection.java:124)
> at com.google.common.util.concurrent.AbstractIdleService$2$1.run(AbstractIdleService.java:54)
> at com.google.common.util.concurrent.Callables$3.run(Callables.java:93)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24534) Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24534?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24534:
------------------------------------
Using Oxygen.0.RC4, I now get this on initial startup or during install of Devstudio 11.0.0.AM1d from staging site.
{code}
Wipe /home/nboldt/eclipse/47clean/eclipse and /home/nboldt/eclipse/workspace-47clean ...
Unpack /home/nboldt/tmp/Eclipse_Bundles/20170620-1800_eclipse-jee-oxygen-RC4-linux.gtk.x86_64.tar.gz ...
Start Eclipse 20170620-1800_eclipse-jee-oxygen-RC4-linux.gtk.x86_64.tar.gz with vm = /usr/bin/java in workspace = /home/nboldt/eclipse/workspace-47clean ...
Install location:
file:/home/nboldt/eclipse/47clean/eclipse/
Configuration file:
file:/home/nboldt/eclipse/47clean/eclipse/configuration/config.ini loaded
Configuration location:
file:/home/nboldt/eclipse/47clean/eclipse/configuration/
Framework located:
file:/home/nboldt/eclipse/47clean/eclipse/plugins/org.eclipse.osgi_3.12.0.v20170512-1932.jar
Loading extension: reference:file:org.eclipse.osgi.compatibility.state_1.1.0.v20170516-1513.jar
eclipse.properties not found
Framework classpath:
file:/home/nboldt/eclipse/47clean/eclipse/plugins/org.eclipse.osgi_3.12.0.v20170512-1932.jar
file:/home/nboldt/eclipse/47clean/eclipse/plugins/
file:/home/nboldt/eclipse/47clean/eclipse/plugins/org.eclipse.osgi.compatibility.state_1.1.0.v20170516-1513.jar
Splash location:
/home/nboldt/eclipse/47clean/eclipse//plugins/org.eclipse.epp.package.common_4.7.0.20170620-1800/splash.bmp
Debug options:
file:/home/nboldt/eclipse/47clean/.options not found
Time to load bundles: 44
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
Starting application: 7137
osgi> org.eclipse.m2e.logback.configuration: Logback config file: /home/nboldt/eclipse/workspace-47clean/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.8.0.20170516-2043.xml
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://984.fwk837764579:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://984.fwk837764579:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
org.eclipse.m2e.logback.configuration: Initializing logback
Application Started: 11579
!SESSION 2017-06-30 11:27:06.175 -----------------------------------------------
eclipse.buildId=4.7.0.I20170612-0950
java.version=1.8.0_121
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -data /home/nboldt/eclipse/workspace-47clean -consolelog -product org.eclipse.epp.package.jee.product -data /home/nboldt/eclipse/workspace-47clean -debug -console -consolelog
!ENTRY org.eclipse.e4.ui.workbench 4 0 2017-06-30 11:40:10.575
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.eclipse.e4.core.di.InjectionException: java.util.concurrent.TimeoutException: Timed out waiting for org.eclipse.epp.logging.aeri.ide.server ServerConnection [STOPPING] to reach a terminal state. Current state: STOPPING
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:990)
at org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:450)
at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:156)
at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:78)
at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111)
at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.handleInvalid(TrackableComputationExt.java:74)
at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:178)
at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:163)
at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:163)
at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:163)
at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.dispose(EclipseContextOSGi.java:99)
at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.bundleChanged(EclipseContextOSGi.java:141)
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:908)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:168)
at org.eclipse.osgi.container.Module.publishEvent(Module.java:476)
at org.eclipse.osgi.container.Module.doStop(Module.java:634)
at org.eclipse.osgi.container.Module.stop(Module.java:498)
at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:202)
at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.util.concurrent.TimeoutException: Timed out waiting for org.eclipse.epp.logging.aeri.ide.server ServerConnection [STOPPING] to reach a terminal state. Current state: STOPPING
at com.google.common.util.concurrent.AbstractService.awaitTerminated(AbstractService.java:317)
at com.google.common.util.concurrent.AbstractIdleService.awaitTerminated(AbstractIdleService.java:199)
at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.diStop(ServerConnection.java:392)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
... 25 more
{code}
After a cold restart of Eclipse, the error is gone, replaced with this:
{code}
Start Eclipse 20170620-1800_eclipse-jee-oxygen-RC4-linux.gtk.x86_64.tar.gz with vm = /usr/bin/java in workspace = /home/nboldt/eclipse/workspace-47clean ...
Install location:
file:/home/nboldt/eclipse/47clean/eclipse/
Configuration file:
file:/home/nboldt/eclipse/47clean/eclipse/configuration/config.ini loaded
Configuration location:
file:/home/nboldt/eclipse/47clean/eclipse/configuration/
Framework located:
file:/home/nboldt/eclipse/47clean/eclipse/plugins/org.eclipse.osgi_3.12.0.v20170512-1932.jar
Loading extension: reference:file:org.eclipse.osgi.compatibility.state_1.1.0.v20170516-1513.jar
eclipse.properties not found
Loading extension: reference:file:org.eclipse.equinox.region_1.4.0.v20170117-1425.jar
eclipse.properties not found
Framework classpath:
file:/home/nboldt/eclipse/47clean/eclipse/plugins/org.eclipse.osgi_3.12.0.v20170512-1932.jar
file:/home/nboldt/eclipse/47clean/eclipse/plugins/
file:/home/nboldt/eclipse/47clean/eclipse/plugins/org.eclipse.osgi.compatibility.state_1.1.0.v20170516-1513.jar
file:/home/nboldt/eclipse/47clean/eclipse/plugins/org.eclipse.equinox.region_1.4.0.v20170117-1425.jar
Splash location:
/home/nboldt/eclipse/47clean/eclipse//plugins/org.eclipse.epp.package.common_4.7.0.20170620-1800/splash.bmp
Debug options:
file:/home/nboldt/eclipse/47clean/.options not found
Time to load bundles: 167
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
Starting application: 10507
osgi> org.eclipse.m2e.logback.configuration: Logback config file: /home/nboldt/eclipse/workspace-47clean/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.8.0.20170516-2043.xml
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://984.fwk21063905:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://984.fwk21063905:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
org.eclipse.m2e.logback.configuration: Initializing logback
Application Started: 18493
!SESSION 2017-06-30 11:43:19.664 -----------------------------------------------
eclipse.buildId=4.7.0.I20170612-0950
java.version=1.8.0_121
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -data /home/nboldt/eclipse/workspace-47clean -consolelog -data /home/nboldt/eclipse/workspace-47clean -consolelog -product org.eclipse.epp.package.jee.product -data /home/nboldt/eclipse/workspace-47clean -debug -console -consolelog
!ENTRY org.eclipse.epp.logging.aeri.ide 2 17 2017-06-30 11:43:39.138
!MESSAGE Server ‘org.eclipse.epp.logging.aeri.ide.server’ failed with exception: Lock held by another program: /home/nboldt/eclipse/workspace-47clean/.metadata/.plugins/org.eclipse.epp.logging.aeri.ide/org.eclipse.epp.logging.aeri.ide.server/http-cache.lucene60/write.lock. ; version: 2.0.5.v20170613-1207
!STACK 0
org.apache.lucene.store.LockObtainFailedException: Lock held by another program: /home/nboldt/eclipse/workspace-47clean/.metadata/.plugins/org.eclipse.epp.logging.aeri.ide/org.eclipse.epp.logging.aeri.ide.server/http-cache.lucene60/write.lock
at org.apache.lucene.store.NativeFSLockFactory.obtainFSLock(NativeFSLockFactory.java:118)
at org.apache.lucene.store.FSLockFactory.obtainLock(FSLockFactory.java:41)
at org.apache.lucene.store.BaseDirectory.obtainLock(BaseDirectory.java:45)
at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:776)
at org.eclipse.epp.internal.logging.aeri.ide.server.rest.LuceneHttpCacheStorage.<init>(LuceneHttpCacheStorage.java:71)
at org.eclipse.epp.internal.logging.aeri.ide.server.rest.RestBasedProblemsHistory.<init>(RestBasedProblemsHistory.java:83)
at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.createRestBasedProblemsHistory(ServerConnection.java:183)
at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.startUp(ServerConnection.java:140)
at com.google.common.util.concurrent.AbstractIdleService$DelegateService$1.run(AbstractIdleService.java:62)
at com.google.common.util.concurrent.Callables$4.run(Callables.java:122)
at java.lang.Thread.run(Thread.java:745)
{code}
> Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out.
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-24534
> URL: https://issues.jboss.org/browse/JBIDE-24534
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aeri, central-update
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.x
>
>
> Having installed devstudio 11.0.0.AM1 into Oxygen.0.M7 JavaEE EPP bundle on Linux x64 (Fedora 24), I tried to install something from Central and instead got an AERI error:
> {code}
> !ENTRY org.eclipse.epp.logging.aeri.ide 2 17 2017-06-02 15:15:10.111
> !MESSAGE Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.5.v20170531-0951
> !STACK 0
> org.apache.http.conn.ConnectTimeoutException: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:150)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.apache.http.client.fluent.Request.internalExecute(Request.java:173)
> at org.apache.http.client.fluent.Executor.execute(Executor.java:262)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.request(IO.java:170)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.refreshConfiguration(IO.java:64)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.startUp(ServerConnection.java:124)
> at com.google.common.util.concurrent.AbstractIdleService$2$1.run(AbstractIdleService.java:54)
> at com.google.common.util.concurrent.Callables$3.run(Callables.java:93)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-22584) jbosstools-central build and jbosstools-discovery build both depend on the existence of a *-earlyaccess.properties file
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22584?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22584:
-------------------------------
Fix Version/s: (was: 4.5.x)
> jbosstools-central build and jbosstools-discovery build both depend on the existence of a *-earlyaccess.properties file
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22584
> URL: https://issues.jboss.org/browse/JBIDE-22584
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central, central-update
> Affects Versions: 4.4.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.Final
>
>
> Normally, jbosstools-central is built before jbosstools-discovery.
> However, running jbosstools-central build for the first time, ran into this:
> {code}
> 22:43:51 [INFO] org.jboss.tools.community.central .................. FAILURE [ 0.556 s]
> 22:43:51 [INFO] org.jboss.tools.community.central.feature .......... SKIPPED
> 22:43:51 [INFO] central.maven.examples.site ........................ SKIPPED
> 22:43:52 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (get-earlyaccess-listing) on project org.jboss.tools.community.central: IO Error: Could not get content -> [Help 1]
> {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs...
> Or, this could be a problem w/ bootstrapping values in ide-config.properties?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19933:
-------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.x)
> Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it
> ----------------------------------------------------------------------------
>
> Key: JBIDE-19933
> URL: https://issues.jboss.org/browse/JBIDE-19933
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.5.0.Final
>
>
> When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master).
> Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch.
> It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point.
> For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months