[JBoss JIRA] (JBIDE-13835) Improve publish script (split? Move to maven?)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13835?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13835:
---------------------------------------------
The installable source bundles are buildable so I actually think it is enough.
But lets put that aside.
If it is about having "raw sources" why don't our maven builds produce -source artifacts, just like ordinary maven projects does ? why do we need a separate github fetching process for this when we already have maven that can do this for us during build time ?
> Improve publish script (split? Move to maven?)
> ----------------------------------------------
>
> Key: JBIDE-13835
> URL: https://issues.jboss.org/browse/JBIDE-13835
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Fix For: 4.3.x
>
>
> Publish script deals with a lot of different and not-always-related things. It makes it difficult to maintain it. We should think about some improvements such as
> * different conventions from different stream
> * components vs aggregate
> * devstudio vs jbosstools.
> Or,
> * Make publishing part of a "mvn deploy" step.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3297) Download/Import Existing OpenShift Project
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3297?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3297:
-------------------------------------------
Yes - in my POV our openshift v3 user should *not* need to know about Docker, but I do not think we will end up being there shortly.
Thus for now I'm very much focused on the parts that is tangible and kinda playing around/waiting for something more tangible to appear around openshift before settling on what this feature can/will do.
> Download/Import Existing OpenShift Project
> ------------------------------------------
>
> Key: JBDS-3297
> URL: https://issues.jboss.org/browse/JBDS-3297
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift, requirements
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
> Priority: Blocker
>
> Use Case #1 - Download/Import Existing OpenShift Project
> a) Assume OpenShift is started remotely and provides an entrypoint URL (e.g. http://localhost:8080/osapi/v1beta1/projects)
> b) Assume end-user is logged in (ignore auth for now)
> c) Assume OpenShift already has some deployed "projects", this "project" definition includes the buildconfig, deployconfig, docker image, source git URL, routes and services.
> d) Eclipse user will open a dialog and enter the URL from step a
> e) Eclipse user will see a list of "things" associated with "projects" from step 1c
> "things"
> f) Embedded in one of those things is a Git URL - that will be displayed to the user who will agree to git clone it [1f]
> g) If the downloaded items include a Maven project, the Eclipse user will see a newly configured Eclipse project based on Maven with the appropriately configured facets
> h) If there is no pom.xml, the Eclipse user will see a newly configured generic Eclipse project containing the downloaded files
> i) It is expected that a Maven-based Java project will build locally (leveraging Maven Central and/or maven.repository.redhat.com)
> j) It is expected that a Maven-based Java project will deploy to a localhost EAP/Wildfly or a locally running Docker container:
> docker run -it -p 8080:8080 openshift/wildfly-8-centos
> [1f] https://github.com/openshift/origin/blob/master/examples/sample-app/appli...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-19352) kitchensink-backbone example demands javaee-6.0-with-hibernate:pom:6.3.2.GA
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19352?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-19352.
---------------------------------
Assignee: Fred Bricon
Fix Version/s: 4.3.0.Alpha1
Resolution: Done
example descriptor fixed and redeployed. Please try again.
> kitchensink-backbone example demands javaee-6.0-with-hibernate:pom:6.3.2.GA
> ---------------------------------------------------------------------------
>
> Key: JBIDE-19352
> URL: https://issues.jboss.org/browse/JBIDE-19352
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.3.0.Alpha1
> Environment: JBDS 9.0.0.Alpha1
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha1
>
>
> In import wizard of kitchensink-backbone example (JBoss Central -> Strat From Sample -> Mobile Applications -> kitchensink-backbone) is shown warning of missing maven repositories:
> http://i.imgur.com/v4I5PCm.png
> The error is, that it cannot resolve org.jboss.bom:jboss-javaee-6.0-with-hibernate:pom:6.3.2.GA.
> After importing this example, it has no errors, because in pom.xml is demanded different bom: org.jboss.bom *.eap*:jboss-javaee-6.0-with-hibernate:pom:6.3.2.GA.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3354) Seam 2 is still included in JBDS 9 Alpha1 installed from jar
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3354?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3354:
--------------------------------------
I'm not sure about 100% of seam3 features but some of them (like @Veto) were implemented in CDI 1.1 and some in Deltaspike. But probably some of them are still seam3 specific. Need to investigate.
> Seam 2 is still included in JBDS 9 Alpha1 installed from jar
> ------------------------------------------------------------
>
> Key: JBDS-3354
> URL: https://issues.jboss.org/browse/JBDS-3354
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, cdi, seam
> Affects Versions: 9.0.0.Alpha1
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
>
> It seems to me that we removed the wrong feature.
> This is JBDS 8.0.2:
> {code}
> nattura:features rasp$ ls |grep seam
> org.jboss.tools.cdi.seam.feature_1.6.1.Final-v20141209-0505-B79
> org.jboss.tools.maven.seam.feature_1.6.1.Final-v20150109-2320-B116
> org.jboss.tools.runtime.seam.detector.feature_3.6.1.Final-v20141209-0505-B79
> org.jboss.tools.seam.feature_3.6.1.Final-v20141209-0505-B79
> {code}
> And this is JBDS 9.0.0.Alpha1 B11:
> {code}
> nattura:features rasp$ ls |grep seam
> org.jboss.tools.seam.feature_3.7.0.Alpha1-v20150213-0551-B3
> {code}
> When you look at plugins, it looks as follows:
> JBDS 8.0.2:
> {code}
> nattura:plugins rasp$ ls|grep seam
> org.jboss.tools.cdi.seam.config.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.config.ui_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.faces.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.solder.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.text.ext_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.jsf.vpe.seam_3.6.1.Final-v20141209-0505-B79
> org.jboss.tools.maven.seam_1.6.1.Final-v20150109-2320-B116.jar
> org.jboss.tools.runtime.seam.detector_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.pages.xml_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.text.ext_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.ui.pages_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.ui_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.xml.ui_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.xml_3.6.1.Final-v20141209-0505-B79.jar
> {code}
> JBDS 9.0.0.Alpha1 B11:
> {code}
> nattura:plugins rasp$ ls|grep seam
> org.jboss.tools.cdi.seam.solder.core_1.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.jsf.vpe.seam_3.7.0.Alpha1-v20150213-0551-B3
> org.jboss.tools.seam.core_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.pages.xml_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.text.ext_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.ui.pages_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.xml.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.xml_3.7.0.Alpha1-v20150213-0551-B3.jar
> {code}
> For JBoss Tools, both are there (seam and cdi.seam) - I'm not sure if that's intentional. Is there a JIRA for dropping seam?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month