July 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-529) Changing the ModeShape repo or local-cache name breaks S-RAMP

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-529?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated SRAMP-529: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1060678, https://bugzilla.redhat.com/show_bug.cgi?id=1028951 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1060678) > Changing the ModeShape repo or local-cache name breaks S-RAMP > ------------------------------------------------------------- > > Key: SRAMP-529 > URL: https://issues.jboss.org/browse/SRAMP-529 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > https://bugzilla.redhat.com/show_bug.cgi?id=1060678 > https://bugzilla.redhat.com/show_bug.cgi?id=1028951 > First, try setting it up to fully rebuild the indexes upon restart... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-529) Changing the ModeShape repo or local-cache name breaks S-RAMP

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-529?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated SRAMP-529: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1060678 > Changing the ModeShape repo or local-cache name breaks S-RAMP > ------------------------------------------------------------- > > Key: SRAMP-529 > URL: https://issues.jboss.org/browse/SRAMP-529 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > https://bugzilla.redhat.com/show_bug.cgi?id=1060678 > https://bugzilla.redhat.com/show_bug.cgi?id=1028951 > First, try setting it up to fully rebuild the indexes upon restart... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-529) Changing the ModeShape repo or local-cache name breaks S-RAMP

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-529: --------------------------------- Summary: Changing the ModeShape repo or local-cache name breaks S-RAMP Key: SRAMP-529 URL: https://issues.jboss.org/browse/SRAMP-529 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer https://bugzilla.redhat.com/show_bug.cgi?id=1060678 https://bugzilla.redhat.com/show_bug.cgi?id=1028951 First, try setting it up to fully rebuild the indexes upon restart... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 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 POST 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.Beta2 > > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-507) Modify way the snapshot artifacts are stored in s-ramp

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-507?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-507: ----------------------------------------------- Brett Meyer <brmeyer(a)redhat.com> changed the Status of [bug 1060773|https://bugzilla.redhat.com/show_bug.cgi?id=1060773] from POST to MODIFIED > Modify way the snapshot artifacts are stored in s-ramp > ------------------------------------------------------ > > Key: SRAMP-507 > URL: https://issues.jboss.org/browse/SRAMP-507 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 0.5.0.Beta2 > > > Include a property mvn.snapshot.timestamp (in case the name contains the timestamp) > When deploying a snapshot artifact, maven will include a timestamp in the filename. The maven repository facade *and* the s-ramp wagon should be updated to store this timestamp info in a new s-ramp property (see above). In addition, the s-ramp wagon should no longer *ever* attempt to update an artifact. Here is what it should do: > h4. Release artifacts > * If this artifact (GAV) already exists in s-ramp, fail > * If this artifact doesn't yet exist, add it > h4. Snapshot artifacts > * If this artifact (GAV + timestamp) already exists in s-ramp, fail > * If this artifact doesn't yet exist, add it along with its timestamp information -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-526) s-ramp-ui.war includes .junit_symbolMaps

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-526?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-526: ----------------------------------------------- Brett Meyer <brmeyer(a)redhat.com> changed the Status of [bug 1076450|https://bugzilla.redhat.com/show_bug.cgi?id=1076450] from POST to MODIFIED > s-ramp-ui.war includes .junit_symbolMaps > ---------------------------------------- > > Key: SRAMP-526 > URL: https://issues.jboss.org/browse/SRAMP-526 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.5.0.Beta4 > > > The s-ramp-ui.war distribution contains a directory: > app/.junit_symbolMaps > which contains a number of *.symbolMap files. > If these files aren't needed at run time, they should be removed from the deployed war. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-513) s-ramp-wagon should use JavaArchive for a sources JAR's ArtifactType

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-513?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-513. ----------------------------- > s-ramp-wagon should use JavaArchive for a sources JAR's ArtifactType > -------------------------------------------------------------------- > > Key: SRAMP-513 > URL: https://issues.jboss.org/browse/SRAMP-513 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.5.0.Beta2 > > > Reported by David via his 1.3.0.Beta1 Testing: > "Do we want the sources jar to be executed in the dtgov workflow? > I executed the s-ramp-demos/s-ramp-demos-switchyard and then 2 switchyard artifacts were upload, the jar, and the sources-jar. Then 2 tasks appeared in the dtgov tasks." > The answer is "no" - the -sources.jar should *not* trigger a workflow. We need to figure out why that is happening. Perhaps the s-ramp wagon is not setting the correct ArtifactType for the -sources JAR artifact? The primary artifact in the maven build should be a SwitchYardApplication. The -sources JAR should be added to s-ramp as JavaArchive (most likely). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-523) GenerateFeaturesXmlMojo should prevent illegal chars in Bundle-Name

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-523?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-523. ----------------------------- > GenerateFeaturesXmlMojo should prevent illegal chars in Bundle-Name > ------------------------------------------------------------------- > > Key: SRAMP-523 > URL: https://issues.jboss.org/browse/SRAMP-523 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.5.0.Beta3 > > > Productization apparently overrides the Maven project names. When they reach GenerateFeaturesXmlMojo, there are un-resolved variables. The Bundle-Name ends up looking like: > {code} > Bundle-Name=${extension.name} API v.${spec.version} > {code} > If unresolved variables exist, period, just leave off the Bundle-Name -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-394) Support domain mode in EAP

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-394?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-394. ----------------------------- > Support domain mode in EAP > -------------------------- > > Key: SRAMP-394 > URL: https://issues.jboss.org/browse/SRAMP-394 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Kevin Conner > Fix For: 0.5.0.Beta3 > > > Support domain mode deployment of SRAMP and Overlord Commons. This will involve deploying the sramp etc wars as modules, and obtaining the properties from the domain.xml file (?). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-523) GenerateFeaturesXmlMojo should prevent illegal chars in Bundle-Name

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-523?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-523: ------------------------------ Fix Version/s: 0.5.0.Beta3 (was: 0.5.0) > GenerateFeaturesXmlMojo should prevent illegal chars in Bundle-Name > ------------------------------------------------------------------- > > Key: SRAMP-523 > URL: https://issues.jboss.org/browse/SRAMP-523 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.5.0.Beta3 > > > Productization apparently overrides the Maven project names. When they reach GenerateFeaturesXmlMojo, there are un-resolved variables. The Bundle-Name ends up looking like: > {code} > Bundle-Name=${extension.name} API v.${spec.version} > {code} > If unresolved variables exist, period, just leave off the Bundle-Name -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 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