[JBoss JIRA] (JBIDE-18366) Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18366?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18366:
---------------------------------------------
JBIDE-18366 is one of many manifestations of this issue.
Have not yet found a reliable way to reproduce it except that it does happen and then launching with exact same arguments it just starts again.
> Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-18366
> URL: https://issues.jboss.org/browse/JBIDE-18366
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> Sometimes, right after start of the IDE, a server fails to start. When this happens, it produces something like this in the server log:
> {code}
> INFO: JBoss MSC version 1.1.5.Final-redhat-1
> Sep 17, 2014 11:27:40 AM org.jboss.as.server.ApplicationServerService start
> INFO: JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting
> Sep 17, 2014 11:27:40 AM org.jboss.as.controller.AbstractOperationContext executeStep
> ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([])
> java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:111)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:611)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:489)
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:290)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:285)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1132)
> at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:299)
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:292)
> at org.jboss.as.server.ServerService.boot(ServerService.java:346)
> at org.jboss.as.server.ServerService.boot(ServerService.java:321)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:254)
> at java.lang.Thread.run(Thread.java:695)
> Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
> at java.util.concurrent.FutureTask.get(FutureTask.java:83)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:103)
> ... 11 more
> Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:106)
> at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:139)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:125)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:695)
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Sep 17, 2014 11:27:40 AM org.jboss.as.server.ServerService boot
> FATAL: JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
> Unfortunately I don't have a reliable way to reproduce this. It happened to me like 3 times over the last few days.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3187) enforce rule that JBDS com.jboss.* bits must have GA, not Final qualifier
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3187?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3187:
----------------------------------
Why hurry? Because master branch is safe for fresh commits. "Why wait?" is a better question. This hurts no one.
It's dead simple to change the way the enforcer works - it's just a line or two of java. So if you don't want to check the parent pom's version, we could just check
{code}
if ( this.shouldIfail && BUILD_ALIAS.equals("Final"))
{
throw new EnforcerRuleException( " ** Parent pom version ("+parentVersion+") contains .Final; must set -DBUILD_ALIAS=GA **");
}
{code}
> enforce rule that JBDS com.jboss.* bits must have GA, not Final qualifier
> -------------------------------------------------------------------------
>
> Key: JBDS-3187
> URL: https://issues.jboss.org/browse/JBDS-3187
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: build
> Affects Versions: 8.0.0.CR2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Add a custom enforcer rule (using org.apache.maven.enforcer.rule) that will check if the parent pom contains .Final, and if so, will fail the build unless BUILD_ALIAS is set to "GA".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3187) enforce rule that JBDS com.jboss.* bits must have GA, not Final qualifier
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3187?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3187:
--------------------------------------
I don't think the important thing is the parent pom here, but more the value of the BUILD_ALIAS. IMO, the enforcer should check the property.
Why did you hurry so much to merge it? It would have been convenient to let us the opportunity to give a review.
> enforce rule that JBDS com.jboss.* bits must have GA, not Final qualifier
> -------------------------------------------------------------------------
>
> Key: JBDS-3187
> URL: https://issues.jboss.org/browse/JBDS-3187
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: build
> Affects Versions: 8.0.0.CR2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Add a custom enforcer rule (using org.apache.maven.enforcer.rule) that will check if the parent pom contains .Final, and if so, will fail the build unless BUILD_ALIAS is set to "GA".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18454) Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-18454:
-------------------------------------------------
John W. Lamb <jolamb(a)redhat.com> changed the Status of [bug 1150287|https://bugzilla.redhat.com/show_bug.cgi?id=1150287] from ASSIGNED to CLOSED
> Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18454
> URL: https://issues.jboss.org/browse/JBIDE-18454
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: new_and_noteworhty
> Fix For: 4.2.0.CR2
>
> Attachments: ssl-error-on-connect.png
>
>
> In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using jdks (openjdk and sun) < 1.8 on linux. We have to verify that this affects the Eclipse based tooling (that's also using openshift-java-client)
> {code}
> java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair
> at hudson.plugins.openshift.OpenShiftCloud.getOpenShiftConnection(OpenShiftCloud.java:186)
> at hudson.plugins.openshift.OpenShiftCloud.getSlaves(OpenShiftCloud.java:877)
> at hudson.plugins.openshift.OpenShiftCloud.provisionSlave(OpenShiftCloud.java:451)
> at hudson.plugins.openshift.OpenShiftCloud.provision(OpenShiftCloud.java:413)
> at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281)
> at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51)
> at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:368)
> at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBTIS-340) JBTIS Target Platform modification - 8.0.0.Beta1b
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-340?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-340:
-----------------------------
Description:
*Reason:* Update BPMN2 modeler to 1.1.1 which includes feature-based source bundles
Update BPEL to 1.0.4, support Luna SR1a and jbosstools core TP 4.41.0.Final.
*Project page/sources:* https://github.com/jbosstools/jbosstools-integration-stack/tree/master/ta...
*Version:* 4.2.0.Beta1b
*License and owner:* EPL
*Original p2 repo:* http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Be...
*JBoss mirror:* n/a
*Include Sources:* No
*Affected projects:* Integration Stack component projects, JBTIS
*Include in JBDS:* No - JBDSIS
*Type of dependency:* distribution
*List of bundles added/removed:* p2diff:
< org.eclipse.bpmn2.modeler.core [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.feature.group [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.help [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.ui [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201409261846]
> org.eclipse.bpmn2.modeler.core [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.feature.group [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.help [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.ui [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201410152001]
=== Summary ===
file:///home/pleacu/git-clone/PR/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 8 unique IUs
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 8 unique IUs
was:
*Reason:* Update BPMN2 modeler to 1.1.1 which includes feature-based source bundles
Update BPEL to 1.0.4
*Project page/sources:* https://github.com/jbosstools/jbosstools-integration-stack/tree/master/ta...
*Version:* 4.2.0.Beta1b
*License and owner:* EPL
*Original p2 repo:* http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Be...
*JBoss mirror:* n/a
*Include Sources:* No
*Affected projects:* Integration Stack component projects, JBTIS
*Include in JBDS:* No - JBDSIS
*Type of dependency:* distribution
*List of bundles added/removed:* p2diff:
< org.eclipse.bpmn2.modeler.core [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.feature.group [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.help [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.ui [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201409261846]
> org.eclipse.bpmn2.modeler.core [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.feature.group [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.help [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.ui [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201410152001]
=== Summary ===
file:///home/pleacu/git-clone/PR/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 8 unique IUs
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 8 unique IUs
> JBTIS Target Platform modification - 8.0.0.Beta1b
> -------------------------------------------------
>
> Key: JBTIS-340
> URL: https://issues.jboss.org/browse/JBTIS-340
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.Beta1a-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> *Reason:* Update BPMN2 modeler to 1.1.1 which includes feature-based source bundles
> Update BPEL to 1.0.4, support Luna SR1a and jbosstools core TP 4.41.0.Final.
> *Project page/sources:* https://github.com/jbosstools/jbosstools-integration-stack/tree/master/ta...
> *Version:* 4.2.0.Beta1b
> *License and owner:* EPL
> *Original p2 repo:* http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Be...
> *JBoss mirror:* n/a
> *Include Sources:* No
> *Affected projects:* Integration Stack component projects, JBTIS
> *Include in JBDS:* No - JBDSIS
> *Type of dependency:* distribution
> *List of bundles added/removed:* p2diff:
> < org.eclipse.bpmn2.modeler.core [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.feature.group [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.help [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.ui [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201409261846]
> > org.eclipse.bpmn2.modeler.core [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.feature.group [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.help [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.ui [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201410152001]
> === Summary ===
> file:///home/pleacu/git-clone/PR/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 8 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 8 unique IUs
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBTIS-340) JBTIS Target Platform modification - 8.0.0.Beta1b
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-340?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-340:
-----------------------------
Description:
*Reason:* Update BPMN2 modeler to 1.1.1 which includes feature-based source bundles
Update BPEL to 1.0.4
*Project page/sources:* https://github.com/jbosstools/jbosstools-integration-stack/tree/master/ta...
*Version:* 4.2.0.Beta1b
*License and owner:* EPL
*Original p2 repo:* http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Be...
*JBoss mirror:* n/a
*Include Sources:* No
*Affected projects:* Integration Stack component projects, JBTIS
*Include in JBDS:* No - JBDSIS
*Type of dependency:* distribution
*List of bundles added/removed:* p2diff:
< org.eclipse.bpmn2.modeler.core [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.feature.group [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.help [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.ui [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201409261846]
< org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201409261846]
> org.eclipse.bpmn2.modeler.core [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.feature.group [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.help [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.ui [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201410152001]
> org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201410152001]
=== Summary ===
file:///home/pleacu/git-clone/PR/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 8 unique IUs
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 8 unique IUs
was:
*Reason:* Update BPMN2 modeler to 1.1.1 which includes feature-based source bundles
Update BPEL to 1.0.4
*Project page/sources:* https://github.com/jbosstools/jbosstools-integration-stack/tree/master/ta...
*Version:* 4.2.0.Beta1b
*License and owner:* EPL
*Original p2 repo:* http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Be...
*JBoss mirror:* n/a
*Include Sources:* No
*Affected projects:* Integration Stack component projects, JBTIS
*Include in JBDS:* No - JBDSIS
*Type of dependency:* distribution
*List of bundles added/removed:* p2diff:
> JBTIS Target Platform modification - 8.0.0.Beta1b
> -------------------------------------------------
>
> Key: JBTIS-340
> URL: https://issues.jboss.org/browse/JBTIS-340
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.Beta1a-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> *Reason:* Update BPMN2 modeler to 1.1.1 which includes feature-based source bundles
> Update BPEL to 1.0.4
> *Project page/sources:* https://github.com/jbosstools/jbosstools-integration-stack/tree/master/ta...
> *Version:* 4.2.0.Beta1b
> *License and owner:* EPL
> *Original p2 repo:* http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Be...
> *JBoss mirror:* n/a
> *Include Sources:* No
> *Affected projects:* Integration Stack component projects, JBTIS
> *Include in JBDS:* No - JBDSIS
> *Type of dependency:* distribution
> *List of bundles added/removed:* p2diff:
> < org.eclipse.bpmn2.modeler.core [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.feature.group [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.help [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.ui [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201409261846]
> < org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201409261846]
> > org.eclipse.bpmn2.modeler.core [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.feature.group [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.help [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.ui [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201410152001]
> > org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201410152001]
> === Summary ===
> file:///home/pleacu/git-clone/PR/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 8 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 8 unique IUs
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3187) enforce rule that JBDS com.jboss.* bits must have GA, not Final qualifier
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3187?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3187 at 10/17/14 3:11 PM:
------------------------------------------------------------
Tests build of JBDS in master branch with different settings:
*works for master branch with 4.3.0.Alpha1-SNAPSHOT parent pom*
{code}
mvn clean install -P hudson -Djbosstools-site-stream=master -Dtpc.version=4.41.0.Final-SNAPSHOT
{code}
*now fails (as expected) for master branch with this change to root pom to use 4.2.0.Final-SNAPSHOT*
{code}
$➔ gd pom.xml
diff --git a/pom.xml b/pom.xml
index fd3a6ae..ead19f7 100644
--- a/pom.xml
+++ b/pom.xml
@@ -6,7 +6,7 @@
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
- <version>4.3.0.Alpha1-SNAPSHOT</version>
+ <version>4.2.0.Final-SNAPSHOT</version>
</parent>
<groupId>com.jboss.devstudio</groupId>
<artifactId>product</artifactId>
mvn install -P hudson -Djbosstools-site-stream=4.2.luna -Dtpc.version=4.41.0.Final-SNAPSHOT
[INFO] ParentPomVersionCheckRule ......................... SUCCESS [2.312s]
[INFO] JBDS - Product, Installers ........................ FAILURE [0.209s]
[WARNING] Rule 0: com.jboss.devstudio.enforcer.rule.ParentPomVersionCheckRule failed with message:
** Parent pom version (4.2.0.Final-SNAPSHOT) contains .Final; must set -DBUILD_ALIAS=GA **
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce (enforce) on project product: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
{code}
*works for master branch with the above same change to root pom to use 4.2.0.Final-SNAPSHOT, and -DBUILD_ALIAS=GA flag added on*
{code}
mvn install -P hudson -Djbosstools-site-stream=4.2.luna -Dtpc.version=4.41.0.Final-SNAPSHOT -DBUILD_ALIAS=GA
[INFO] ParentPomVersionCheckRule ......................... SUCCESS [0.393s]
[INFO] JBDS - Product, Installers ........................ SUCCESS [1.490s]
[INFO] JBDS - Product - Build Rules ...................... SUCCESS [0.008s]
[INFO] JBDS - Product Plugins - Core ..................... SUCCESS [0.007s]
[INFO] com.jboss.devstudio.core .......................... SUCCESS [3.762s]
[INFO] com.jboss.devstudio.core.project.examples ......... SUCCESS [0.228s]
[INFO] com.jboss.devstudio.core.usage.branding ........... SUCCESS [0.265s]
[INFO] com.jboss.devstudio.core.central .................. SUCCESS [1.122s]
[INFO] JBDS - Product Features - Core .................... SUCCESS [0.027s]
[INFO] com.jboss.devstudio.core.feature .................. SUCCESS [0.616s]
[INFO] com.jboss.devstudio.core.feature.source ........... SUCCESS [0.446s]
[INFO] com.jboss.devstudio.core.site ..................... SUCCESS [1:27.254s]
[INFO] p2-director ....................................... SUCCESS [0.168s]
[INFO] com.jboss.devstudio.core.p2.director .............. SUCCESS [0.920s]
[INFO] p2-director ....................................... SUCCESS [21.242s]
[INFO] installer ......................................... SUCCESS [10:45.227s]
[INFO] JBoss Developer Studio Sources .................... SUCCESS [15.659s]
[INFO] JBoss Developer Studio Build Results .............. SUCCESS [7.716s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
{code}
So, I've pushed the above PR to master.
[~maxandersen] [~mickael_istria], if you want it pushed to 4.2.x, let me know.
was (Author: nickboldt):
Tests build of JBDS in master branch with different settings:
*works for master branch with 4.3.0.Alpha1-SNAPSHOT parent pom*
{code}
mvn clean install -P hudson -Djbosstools-site-stream=master -Dtpc.version=4.41.0.Final-SNAPSHOT
{code}
* now fails (as expected) for master branch with this change to root pom to use 4.2.0.Final-SNAPSHOT*
{code}
$➔ gd pom.xml
diff --git a/pom.xml b/pom.xml
index fd3a6ae..ead19f7 100644
--- a/pom.xml
+++ b/pom.xml
@@ -6,7 +6,7 @@
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
- <version>4.3.0.Alpha1-SNAPSHOT</version>
+ <version>4.2.0.Final-SNAPSHOT</version>
</parent>
<groupId>com.jboss.devstudio</groupId>
<artifactId>product</artifactId>
mvn install -P hudson -Djbosstools-site-stream=4.2.luna -Dtpc.version=4.41.0.Final-SNAPSHOT
[INFO] ParentPomVersionCheckRule ......................... SUCCESS [2.312s]
[INFO] JBDS - Product, Installers ........................ FAILURE [0.209s]
[WARNING] Rule 0: com.jboss.devstudio.enforcer.rule.ParentPomVersionCheckRule failed with message:
** Parent pom version (4.2.0.Final-SNAPSHOT) contains .Final; must set -DBUILD_ALIAS=GA **
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce (enforce) on project product: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
{code}
*works for master branch with the above same change to root pom to use 4.2.0.Final-SNAPSHOT, and -DBUILD_ALIAS=GA flag added on*
{code}
mvn install -P hudson -Djbosstools-site-stream=4.2.luna -Dtpc.version=4.41.0.Final-SNAPSHOT -DBUILD_ALIAS=GA
[INFO] ParentPomVersionCheckRule ......................... SUCCESS [0.393s]
[INFO] JBDS - Product, Installers ........................ SUCCESS [1.490s]
[INFO] JBDS - Product - Build Rules ...................... SUCCESS [0.008s]
[INFO] JBDS - Product Plugins - Core ..................... SUCCESS [0.007s]
[INFO] com.jboss.devstudio.core .......................... SUCCESS [3.762s]
[INFO] com.jboss.devstudio.core.project.examples ......... SUCCESS [0.228s]
[INFO] com.jboss.devstudio.core.usage.branding ........... SUCCESS [0.265s]
[INFO] com.jboss.devstudio.core.central .................. SUCCESS [1.122s]
[INFO] JBDS - Product Features - Core .................... SUCCESS [0.027s]
[INFO] com.jboss.devstudio.core.feature .................. SUCCESS [0.616s]
[INFO] com.jboss.devstudio.core.feature.source ........... SUCCESS [0.446s]
[INFO] com.jboss.devstudio.core.site ..................... SUCCESS [1:27.254s]
[INFO] p2-director ....................................... SUCCESS [0.168s]
[INFO] com.jboss.devstudio.core.p2.director .............. SUCCESS [0.920s]
[INFO] p2-director ....................................... SUCCESS [21.242s]
[INFO] installer ......................................... SUCCESS [10:45.227s]
[INFO] JBoss Developer Studio Sources .................... SUCCESS [15.659s]
[INFO] JBoss Developer Studio Build Results .............. SUCCESS [7.716s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
{code}
So, I've pushed the above PR to master.
[~maxandersen] [~mickael_istria], if you want it pushed to 4.2.x, let me know.
> enforce rule that JBDS com.jboss.* bits must have GA, not Final qualifier
> -------------------------------------------------------------------------
>
> Key: JBDS-3187
> URL: https://issues.jboss.org/browse/JBDS-3187
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: build
> Affects Versions: 8.0.0.CR2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Add a custom enforcer rule (using org.apache.maven.enforcer.rule) that will check if the parent pom contains .Final, and if so, will fail the build unless BUILD_ALIAS is set to "GA".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months