[JBoss JIRA] (JBIDE-18921) release webtools site for Eclipse 4.3 Mars to so WTP 3.7 discovery upstream can find it
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18921?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18921:
------------------------------------
TODO (based on call w/ Max today):
1. use /updates/webtools/mars/ instead of new URL pattern w/ /stable/ because it will move from alpha to beta to cr to final as we release new milestones, and /stable/ is therefore not an accurate descriptor/path segment.
2. include in that folder whatever build Rob deems happy -- the latest 4.3.0.Alpha
3. document what file in the WTP discovery process actually controls the URL used for JBT so we can better test & develop for this; can then also attach a PR to the upstream bugzilla instead of just a patch
4. EXPERIMENT with:
a) symlink or composite site to point at nightly
b) including the <category name="org.eclipse.wst.server.core.serverAdapter"/> in the JBT site and categorizing the org.jboss.ide.eclipse.as.feature on that site so we no longer need to produce a second update site just for WTP
c) including a useful category description for the above category ( c ) so it can be ignored by users when browsing the JBT site
> release webtools site for Eclipse 4.3 Mars to so WTP 3.7 discovery upstream can find it
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-18921
> URL: https://issues.jboss.org/browse/JBIDE-18921
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, updatesite, upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha1
>
>
> Need a semi-working placeholder (even if it's a weak first alpha or copy of JBT 4.2.0's site) so that WTP can resolve a valid site for server adapters.
> Content that needs to be copied is here:
> http://download.jboss.org/jbosstools/static/updates/JBossTools-4.2.0.Fina... (or something newer?)
> Destination folder (new folder hierarchy as of JBDS-3208 reorg):
> http://download.jboss.org/jbosstools/mars/stable/updates/webtools/
> Upstream issue:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=454810
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18464) For JBIDE 4.2.0.CR2: Prepare for CR2 release
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18464?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18464:
---------------------------------------------
Upgraded parent pom in jbosstools-4.2.x
> For JBIDE 4.2.0.CR2: Prepare for CR2 release
> --------------------------------------------
>
> Key: JBIDE-18464
> URL: https://issues.jboss.org/browse/JBIDE-18464
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR2
>
>
> For JBIDE 4.2.0.CR2: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
> [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT
> mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
> {code}
> 5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*:
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3169
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18652) NPE in Eclipse Error Log View when Central repo isn't available
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18652?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-18652:
------------------------------------
[~mickael_istria] Can you suggest way how to replicate/verify this issue? I tried to malform ide-config.properties as it is described in JBIDE-18675, but I still couldn't reproduce this issue (on 4.2.0.Final).
> NPE in Eclipse Error Log View when Central repo isn't available
> ---------------------------------------------------------------
>
> Key: JBIDE-18652
> URL: https://issues.jboss.org/browse/JBIDE-18652
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR2
> Reporter: Denis Golovin
> Assignee: Mickael Istria
> Labels: respin-a
> Fix For: 4.2.1.CR1
>
>
> Could be related to Central Update Site not being available, but it should not fail with NPE in this case.
> {code}java.lang.NullPointerException
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101)
> at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3258) Docker Tooling (Advanced Integration)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3258?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3258:
-------------------------------------------
initial comment is that this jira is mixing up alot of things.
0,1,2,3:
Making sure docker is running is not something we will do - users will provide a ip to connect to; just like all other tools that uses docker do. If we already know the IP we don't need to run boot2docker, and it should in any way be configured/read from environment variables to fit best with other tools.
3:
Run As functionallity - this does not fit in the overall system afaics. Run As implies you have deployed something, which we can't on a docker instance before it is running. This usecase shuold be separated out and detailed since I as is now it would require a really custom workflow that would not handle many users need for docker being flexible. But lets outline it in separte jira.
5,6,7,9:
Basic docker operations (ps, rm,rmi, etc.) these should be part of JBDS-3256
8:
docker build uses whatever is in your dockerfile - wether it has a war or ear embedded is up to the user.
> Docker Tooling (Advanced Integration)
> -------------------------------------
>
> Key: JBDS-3258
> URL: https://issues.jboss.org/browse/JBDS-3258
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
>
> Once significant delta between the "basic" and advanced scenarios is that here I wish to custom craft my own docker images instead of using an existing one - where my custom crafted image includes my .war or .ear.
> In addition to the basic integrations of pull, run, stop, commit and push
> boot2docker init
> boot2docker up
> boot2docker down
> boot2docker ip
> docker run -d
> docker ps
> docker rm
> docker rmi
> docker build
> End-user steps:
> 0) assumes boot2docker has been dowloaded and installed
> 1) boot2docker init : required to to insure boot2docker-vm is properly initialized
> 2) boot2docker up : starts the VirtualBox boot2docker-vm
> 3) boot2docker ip : returns the IP address - this will be vital when it comes to testing - it would need to be integrated with our Run - As on Docker capability.
> 4) docker run -i -t -p 80:8080 jboss/wildfly -d : the -d means detached, I may need to run N containers simultaneously
> 5) docker ps : allows me to see all my currently running containers
> 6) docker rm : allows me to kill a currently running container
> 7) docker rmi : allows me to remove a local image
> 8) docker build : assumes that I have crafted a Dockerfile - this will create the local image - with my .war or .ear embedded
> 9) docker run : this new created image
> The docker build scenario can be triggered via a Maven plugin
> The docker build scenario can also be triggered via an Eclipse menu option (like a Maven install)
> We need to figure out the file-system layout so that the Dockerfile and the maven project are all nicely checked into git/svn. So that Jenkins can pick up this repository and perform an automated "docker build" (post Maven install) and then run all the appropriate unit, integration and functional tests.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months