[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:
-----------------------------
Fix Version/s: (was: 9.0.0.Alpha2)
> 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.Beta1
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> *** /*updates*/
> **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> *** /*builds*/
> **** /<job-name>/
> ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
> <earlyaccess,updates,discovery>/<mars,9.0>
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last N 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.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3384:
-----------------------------
Fix Version/s: 9.0.0.Beta1
(was: 9.0.0.Alpha2)
> Investigate how the terminal changes in Mars will/should affect us
> -------------------------------------------------------------------
>
> Key: JBDS-3384
> URL: https://issues.jboss.org/browse/JBDS-3384
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: build, forge, openshift
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 9.0.0.Beta1
>
>
> Terminal (console) support in eclipse mars is changing and we should
> make sure we adjust for it.
> Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html
> Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now.
> This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new.
> As we find what it entails we should link those issues to this jira.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19049:
-------------------------------------
Correct. Step 0) Use latest code from master.
I do worry, however, that this will lead to conflicting requests from downstream consumers (like Lars) who only want compatible VMs present, and want these non-supported JRE's removed from the list.
For this reason, I added a protected boolean method where subclasses can override this support and only show strictly compatible ones. See AbstractJREComposite.includeIncompatibleJREs(). So Fuse / etc can override this and return false if they wish.
> Enable JBoss servers to run with java 9
> ---------------------------------------
>
> Key: JBIDE-19049
> URL: https://issues.jboss.org/browse/JBIDE-19049
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: Java9
> Fix For: 4.3.0.Beta1
>
>
> I briefly tried to use java 9 for our tooling and to run servers.
> I downloaded it from here:
> https://jdk9.java.net/download/
> {code}
> nattura:8.0.2 rasp$ java -version
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b45)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode)
> {code}
> I use OS X 10.10 Yosemite.
> There are a couple of problems:
> 1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that.
> 2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all.
> {code}
> nattura:bin rasp$ ./standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final
> JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> Unrecognized VM option 'MaxPermSize=256m'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months