December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13407) Jar signing for JBT plugins/features

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13407?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13407: ---------------------------------------- Shoudl we reject this issue? > Jar signing for JBT plugins/features > ------------------------------------ > > Key: JBIDE-13407 > URL: https://issues.jboss.org/browse/JBIDE-13407 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 3.3.2.Final, 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.Alpha1 > > Attachments: dialog_do-you-trust-these-certs.png, jbds-signed-plugins.png, JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png, no-more-jboss-unsigned-content-but-what-about-org.sonatype.png > > > Investigate jar signing processes/options and locations of certs we can use for signing of JBIDE / JBTIS community jars for repackaging into JBDS product. > Goal is to avoid seeing warning about installing unsigned content from Eclipse Marketplace, p2 installer, or JBoss Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13671: ----------------------------------- Priority: Optional (was: Major) > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.2.x > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13671: ----------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Alpha1) > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.x > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14448) Build doesn't detect cycle dependencies between JBossTools modules

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14448?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-14448: ---------------------------------------- This risk will be strongly reduced with changes introduced by JBIDE-16309. Cyclic dependencies will still be possible, but at least, they'll be explicit and visible from pom files. > Build doesn't detect cycle dependencies between JBossTools modules > ------------------------------------------------------------------ > > Key: JBIDE-14448 > URL: https://issues.jboss.org/browse/JBIDE-14448 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.2.x > > > Currently every component references nightly composite update site during the build to get dependencies. That leads to possibility to introduce cycle dependencies between components that is not detected by build. > Here is example of PR introduced a cycle between JST and VPE. Build works because JST have access to VPE BrowserSim through nightly composite update site. > The solution would be to reference specific nightly update sites for modules that are dependencies for current one. > In this case JST should have reference only to base composite nightly update site. That would solve cycle dependency detection problem and speed up the build because it would not require to download and analyse all metadata from jbosstools nightly composite update site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14610) Design http://download.jboss.org/jbosstools structure

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14610?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-14610: ---------------------------------------- Making it to 4.2.x as this is a forever ongoing task IMO. Some comments: * composite sites will soon disappear (cf JBIDE-16309) * build metadata (sites) should be contained in the repository they produce, in a "buildinfo" folder. So it's one less set of URLs to manage and it's easy to find mapping from site to build info (currently not that trivial). * Nexus provides much of what we want, in a standard way ** versioned repositories ** a "quality" level (snapshot, staging, release) > Design http://download.jboss.org/jbosstools structure > ----------------------------------------------------- > > Key: JBIDE-14610 > URL: https://issues.jboss.org/browse/JBIDE-14610 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, updatesite > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.2.x > > > We have several types of objects which names should be presented in site stucture: > # Project: jbosstools > # Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final > # Subproject: core, soatools > # Module: base, javaee, central, freemarker and etc. > # Distribution Type: updates|builds > # Bits Type: stable|development|nightly > # Targeted Eclipse: indigo|juno|kepler > # You name it ... > Now we mostly use following patterns to publish nightly bits, but not always and not for every project: > # aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\} > # jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure > # jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14448) Build doesn't detect cycle dependencies between JBossTools modules

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14448?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-14448: ----------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Alpha1) > Build doesn't detect cycle dependencies between JBossTools modules > ------------------------------------------------------------------ > > Key: JBIDE-14448 > URL: https://issues.jboss.org/browse/JBIDE-14448 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.2.x > > > Currently every component references nightly composite update site during the build to get dependencies. That leads to possibility to introduce cycle dependencies between components that is not detected by build. > Here is example of PR introduced a cycle between JST and VPE. Build works because JST have access to VPE BrowserSim through nightly composite update site. > The solution would be to reference specific nightly update sites for modules that are dependencies for current one. > In this case JST should have reference only to base composite nightly update site. That would solve cycle dependency detection problem and speed up the build because it would not require to download and analyse all metadata from jbosstools nightly composite update site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14610) Design http://download.jboss.org/jbosstools structure

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14610?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-14610: ----------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Alpha1) > Design http://download.jboss.org/jbosstools structure > ----------------------------------------------------- > > Key: JBIDE-14610 > URL: https://issues.jboss.org/browse/JBIDE-14610 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, updatesite > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.2.x > > > We have several types of objects which names should be presented in site stucture: > # Project: jbosstools > # Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final > # Subproject: core, soatools > # Module: base, javaee, central, freemarker and etc. > # Distribution Type: updates|builds > # Bits Type: stable|development|nightly > # Targeted Eclipse: indigo|juno|kepler > # You name it ... > Now we mostly use following patterns to publish nightly bits, but not always and not for every project: > # aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\} > # jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure > # jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14742) Investigate using or forking eclipse release train repo cheks

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14742?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-14742: ----------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Alpha1) > Investigate using or forking eclipse release train repo cheks > ------------------------------------------------------------- > > Key: JBIDE-14742 > URL: https://issues.jboss.org/browse/JBIDE-14742 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Priority: Minor > Fix For: 4.2.x > > > http://build.eclipse.org/simrel/kepler/reporeports/ > http://wiki.eclipse.org/SimRel/Simultaneous_Release_Reports_FAQ > Seems like very useful tool to run against and updatesite. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14642) How to automate process of bumping version for changed modules/submodules for every release

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14642?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-14642: ----------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Alpha1) > How to automate process of bumping version for changed modules/submodules for every release > ------------------------------------------------------------------------------------------- > > Key: JBIDE-14642 > URL: https://issues.jboss.org/browse/JBIDE-14642 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Assignee: Max Rydahl Andersen > Fix For: 4.2.x > > > The versions of plugins are constantly discovered to not be uptodated when they should and things like Usage and others where it is critical are not getting bumped. > We need two things: > A) detect when versions are not bumped properly - we got parts of this in various places, but they are not run nor documented regularly (having a green build verifying versions are not conflicting would be a Good Thing) > B) document/automate a process which every affected lead can follow to make this happen and if not See #A -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15185) add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15185?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15185: --------------------------------------------- btw. what parts of the configuration are you editing/need to share ? > add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory. > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15185 > URL: https://issues.jboss.org/browse/JBIDE-15185 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Gary Hu > Fix For: 4.2.x > > > The current jbds version only allow users to specify an absolute path for "Home Directory" when creating JBoss Runtime Server. Is it possible to use a user defined variable here? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 December 2013