July 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-493) 2 different modeshape dependency versions required to build

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-493?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-493: ----------------------------------------------- Brett Meyer <brmeyer(a)redhat.com> changed the Status of [bug 1115531|https://bugzilla.redhat.com/show_bug.cgi?id=1115531] from NEW to ASSIGNED > 2 different modeshape dependency versions required to build > ----------------------------------------------------------- > > Key: SRAMP-493 > URL: https://issues.jboss.org/browse/SRAMP-493 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > When productized, s-ramp-distro-assembly fails since modeshape-distribution no longer includes the old jbosseap-61-dist. Instead of declaring it as an actual dependency, manually pull down the jar with maven-dependency-plugin, then use a fileSet in the assembly. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-493) 2 different modeshape dependency versions required to build

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-493: --------------------------------- Summary: 2 different modeshape dependency versions required to build Key: SRAMP-493 URL: https://issues.jboss.org/browse/SRAMP-493 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer When productized, s-ramp-distro-assembly fails since modeshape-distribution no longer includes the old jbosseap-61-dist. Instead of declaring it as an actual dependency, manually pull down the jar with maven-dependency-plugin, then use a fileSet in the assembly. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-492) Maven release configuration is broken

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-492?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-492. ----------------------------- Resolution: Cannot Reproduce Bug I'm no longer able to reproduce -- the release (w/ -DdryRun=true) appears to work perfectly, including the javadocs. It's possible that SRAMP-490 affected it > Maven release configuration is broken > ------------------------------------- > > Key: SRAMP-492 > URL: https://issues.jboss.org/browse/SRAMP-492 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > There appears to be some issues within the javadocs plugin during the package phase. The root POM contains exclude and include packages in the plugin configuration -- I'm wondering if this section is off, missing an exclude, etc. For now, I manually built and deployed S-RAMP, but it's missing the javadocs in Nexus entirely. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-492) Maven release configuration is broken

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-492?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-492: ------------------------------ Fix Version/s: (was: 0.5.0) > Maven release configuration is broken > ------------------------------------- > > Key: SRAMP-492 > URL: https://issues.jboss.org/browse/SRAMP-492 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > There appears to be some issues within the javadocs plugin during the package phase. The root POM contains exclude and include packages in the plugin configuration -- I'm wondering if this section is off, missing an exclude, etc. For now, I manually built and deployed S-RAMP, but it's missing the javadocs in Nexus entirely. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-492) Maven release configuration is broken

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-492: --------------------------------- Summary: Maven release configuration is broken Key: SRAMP-492 URL: https://issues.jboss.org/browse/SRAMP-492 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 0.5.0 There appears to be some issues within the javadocs plugin during the package phase. The root POM contains exclude and include packages in the plugin configuration -- I'm wondering if this section is off, missing an exclude, etc. For now, I manually built and deployed S-RAMP, but it's missing the javadocs in Nexus entirely. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-486) s-ramp.sh should not require JAVA_HOME to be set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-486?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-486: ----------------------------------------------- Brett Meyer <brmeyer(a)redhat.com> changed the Status of [bug 1057022|https://bugzilla.redhat.com/show_bug.cgi?id=1057022] from ASSIGNED to MODIFIED > s-ramp.sh should not require JAVA_HOME to be set > ------------------------------------------------ > > Key: SRAMP-486 > URL: https://issues.jboss.org/browse/SRAMP-486 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.5.0 > > > s-ramp.sh is the only FSW script that requires JAVA_HOME to be set. As RHEL installations by default do not set it, the requirement should be relaxed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-486) s-ramp.sh should not require JAVA_HOME to be set

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-486?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-486. ------------------------------- Resolution: Done > s-ramp.sh should not require JAVA_HOME to be set > ------------------------------------------------ > > Key: SRAMP-486 > URL: https://issues.jboss.org/browse/SRAMP-486 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.5.0 > > > s-ramp.sh is the only FSW script that requires JAVA_HOME to be set. As RHEL installations by default do not set it, the requirement should be relaxed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-490) Remove version overrides for plugins (inherit from jboss-parent)

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-490?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-490. ------------------------------- Resolution: Done > Remove version overrides for plugins (inherit from jboss-parent) > ---------------------------------------------------------------- > > Key: SRAMP-490 > URL: https://issues.jboss.org/browse/SRAMP-490 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.5.0 > > > In some cases we are overriding the versions of plugins in various projects (overlord-commons, s-ramp, dtgov). > We should remove any version overrides unless they are actually necessary. I don't know of any required overrides, so I think they can all be removed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-489) Remove newlines from WAR bundle classpaths in pom.xml files

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-489?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-489. ------------------------------- Resolution: Done > Remove newlines from WAR bundle classpaths in pom.xml files > ----------------------------------------------------------- > > Key: SRAMP-489 > URL: https://issues.jboss.org/browse/SRAMP-489 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.5.0 > > > We use the WAR plugin to add manifest entries to support osgi in all our WARs. Currently the import packages, export packages, and bundle classpath all have newlines in their content. This is throwing off the maven pipeline for certain versions of the war plugin. > Remove all newlines from pom.xml bundle entries. > Do this for all projects: overlord-commons, s-ramp, dtgov. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-490) Remove version overrides for plugins (inherit from jboss-parent)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-490?page=com.atlassian.jira.plugin.... ] Eric Wittmann commented on SRAMP-490: ------------------------------------- Based on what I learned from [~ncross] and dcoleman I would say that it's limited to the WAR projects. The bundle plugin is used for anything that's not a WAR, and it appears to be the war plugin that is messing up the manifest. > Remove version overrides for plugins (inherit from jboss-parent) > ---------------------------------------------------------------- > > Key: SRAMP-490 > URL: https://issues.jboss.org/browse/SRAMP-490 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.5.0 > > > In some cases we are overriding the versions of plugins in various projects (overlord-commons, s-ramp, dtgov). > We should remove any version overrides unless they are actually necessary. I don't know of any required overrides, so I think they can all be removed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues July 2014