March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18772: ------------------------------------ Alternatively, we could start rewriting rsync.sh as some-kinda-deployment-mojo and jbosstools-cleanup.sh as some-kinda-cleanup-mojo. More work but ultimately way more portable. > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19009) As a user, I want to create OpenShift resources from a template

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19009?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19009: ---------------------------------- Attachment: create from template.png > As a user, I want to create OpenShift resources from a template > --------------------------------------------------------------- > > Key: JBIDE-19009 > URL: https://issues.jboss.org/browse/JBIDE-19009 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > Attachments: Create app from template mockup.bmml, Create app from template mockup.png, create from source.png, create from template.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19009) As a user, I want to create OpenShift resources from a template

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19009?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19009: ---------------------------------- Attachment: create from source.png > As a user, I want to create OpenShift resources from a template > --------------------------------------------------------------- > > Key: JBIDE-19009 > URL: https://issues.jboss.org/browse/JBIDE-19009 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > Attachments: Create app from template mockup.bmml, Create app from template mockup.png, create from source.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18772: ---------------------------------------- Ok, I'll rework my proposal to consume the rsync.sh from pom. Stay tuned! > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18772 at 3/23/15 9:51 AM: ------------------------------------------------------------- I love the idea! However, when migrating to a pom, there are a few other things that rsync.sh does that we need to do. Things this doesn't do: * ensure that the full target path actually exists before trying to rsync there; if it's a first time publish, we might be missing some/intermediate/folders/before/ (ie., if we use Jenkins to push to staging or development instead of snapshots, we would need to ensure those folders exist first, or the rsync will fail.) * create a symlink from this latest $\{JOB_NAME}/$\{BUILD_ID}-B$\{BUILD_NUMBER} folder to $\{JOB_NAME}/latest/ * create a composite site in $\{JOB_NAME}/ of all the */all/repo/ folders, and purge old published folders older than 2 days old * create a copy of the build log in the $\{JOB_NAME}/$\{BUILD_ID}-B$\{BUILD_NUMBER}/logs/ folder * create a link to the published content from within the Jenkins job's BUILD_DESCRIPTION [not required but nice to have] For aggregate site publishes, we also need: * a second rsync call to push content into mars/snapshots/updates/*/ was (Author: nickboldt): I love the idea! However, when migrating to a pom, there are a few other things that rsync.sh does that we need to do. Things this doesn't do: * ensure that the full target path actually exists before trying to rsync there; if it's a first time publish, we might be missing some/intermediate/folders/before/ (ie., if we use Jenkins to push to staging or development instead of snapshots, we would need to ensure those folders exist first, or the rsync will fail.) * create a symlink from this latest ${JOB_NAME}/${BUILD_ID}-B${BUILD_NUMBER} folder to ${JOB_NAME}/latest/ * create a composite site in ${JOB_NAME}/ of all the */all/repo/ folders, and purge old published folders older than 2 days old * create a copy of the build log in the ${JOB_NAME}/${BUILD_ID}-B${BUILD_NUMBER}/logs/ folder * create a link to the published content from within the Jenkins job's BUILD_DESCRIPTION [not required but nice to have] For aggregate site publishes, we also need: * a second rsync call to push content into mars/snapshots/updates/*/ > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18772: ------------------------------------ I love the idea! However, when migrating to a pom, there are a few other things that rsync.sh does that we need to do. Things this doesn't do: * ensure that the full target path actually exists before trying to rsync there; if it's a first time publish, we might be missing some/intermediate/folders/before/ (ie., if we use Jenkins to push to staging or development instead of snapshots, we would need to ensure those folders exist first, or the rsync will fail.) * create a symlink from this latest ${JOB_NAME}/${BUILD_ID}-B${BUILD_NUMBER} folder to ${JOB_NAME}/latest/ * create a composite site in ${JOB_NAME}/ of all the */all/repo/ folders, and purge old published folders older than 2 days old * create a copy of the build log in the ${JOB_NAME}/${BUILD_ID}-B${BUILD_NUMBER}/logs/ folder * create a link to the published content from within the Jenkins job's BUILD_DESCRIPTION [not required but nice to have] For aggregate site publishes, we also need: * a second rsync call to push content into mars/snapshots/updates/*/ > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18772: ---------------------------------------- Using the following piece of pom file, we can simply have p2 repo deployed with "mvn deploy" {code:xml} <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.3.2</version> <executions> <execution> <goals> <goal>exec</goal> </goals> <phase>deploy</phase> <configuration> <executable>rsync</executable> <arguments> <arg>-aPrz</arg> <arg>--rsh=ssh</arg> <arg>--protocol=28</arg> <arg>${project.build.directory}/repository</arg> <arg>tools@filemgmt.jboss.org:jbosstools/updates/mars/snapshots/builds/${JOB_NAME}/${BUILD_ID}-B${BUILD_NUMBER}/all/repo/</arg> </arguments> </configuration> </execution> </executions> </plugin> </plugins> </build> {code} So we can replace directly invocation of rsync.sh in scripts by a "mvn deploy -f site/pom.xml" [~nickboldt] WDYT? > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-526) IDE How To: Prepare the IDE for Working Offline

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-526?page=com.atlassian.jira.plug... ] Martin Malina closed TOOLSDOC-526. ---------------------------------- Doc is available here: https://access.redhat.com/articles/1367643 Closing. > IDE How To: Prepare the IDE for Working Offline > ----------------------------------------------- > > Key: TOOLSDOC-526 > URL: https://issues.jboss.org/browse/TOOLSDOC-526 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Affects Versions: 4.2.0.Final > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Final > > > Write a How To article, including the following information/tasks: > * Assume IDE (+ JBDS or JBT) is already installed > * 1. Prepare project wizards in JBoss for use when offline > ** See for info: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > * 2. Prepare JBoss Central Update tab for installing software when offline > ** See for info: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > Need to point out that can't use OpenShift Tooling if offline -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-584) Can we recreate the JBDS 7.x Offline Mode documentation?

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-584?page=com.atlassian.jira.plug... ] Martin Malina closed TOOLSDOC-584. ---------------------------------- The doc is available here: https://access.redhat.com/articles/1367643 Closing. > Can we recreate the JBDS 7.x Offline Mode documentation? > -------------------------------------------------------- > > Key: TOOLSDOC-584 > URL: https://issues.jboss.org/browse/TOOLSDOC-584 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide > Affects Versions: 4.2.3.Final > Reporter: Len DiMaggio > Assignee: Michelle Murray > Fix For: 4.2.3.Final > > Attachments: offline.png > > > Can we receate/extend the offline mode docs from the 7.x user guide: > http://documentation-devel.engineering.redhat.com/site/documentation/en-U... > There's also a misconception that should be cleared up in that "offline" mode actually requires a user to be online when they run the offline mode setup script to populate their maven repo. After this is complete, they can go offline. The user docs should reflect the required sequence of tasks that must be performed to go into offline mode - Thx! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19494) Migrate to Jetty 9

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19494?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19494: -------------------------------- Component/s: browsersim cordovasim > Migrate to Jetty 9 > ------------------ > > Key: JBIDE-19494 > URL: https://issues.jboss.org/browse/JBIDE-19494 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: browsersim, cordovasim, livereload > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > Following JBIDE-18804 which migrates to Jetty 9, we should also do the move to have a single version of the Jetty bundles in our TP. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2015