July 2014 - overlord-issues - Jboss List Archives

[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: ------------------------------ Description: 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 was: 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, fall back on using the GAV for the name > 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 > > 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)

9 years, 11 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: ------------------------------ Description: 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, fall back on using the GAV for the name was: Productization apparently overrides the Maven project names. When they reach GenerateFeaturesXmlMojo, there are un-resolved variables. The Bundle-Name ends up looking like: Bundle-Name=${extension.name} API v.${spec.version} If unresolved variables exist, period, fall back on using the GAV for the name > 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 > > 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, fall back on using the GAV for the name -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-523?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated SRAMP-523: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1118698 > 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 > > Productization apparently overrides the Maven project names. When they reach GenerateFeaturesXmlMojo, there are un-resolved variables. The Bundle-Name ends up looking like: > Bundle-Name=${extension.name} API v.${spec.version} > If unresolved variables exist, period, fall back on using the GAV for the name -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-523?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-523: ----------------------------------------------- Brett Meyer <brmeyer(a)redhat.com> changed the Status of [bug 1118698|https://bugzilla.redhat.com/show_bug.cgi?id=1118698] from NEW to ASSIGNED > 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 > > Productization apparently overrides the Maven project names. When they reach GenerateFeaturesXmlMojo, there are un-resolved variables. The Bundle-Name ends up looking like: > Bundle-Name=${extension.name} API v.${spec.version} > If unresolved variables exist, period, fall back on using the GAV for the name -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

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

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-523: --------------------------------- Summary: 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 Productization apparently overrides the Maven project names. When they reach GenerateFeaturesXmlMojo, there are un-resolved variables. The Bundle-Name ends up looking like: Bundle-Name=${extension.name} API v.${spec.version} If unresolved variables exist, period, fall back on using the GAV for the name -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-542) Fix integration tests to use coniguration in standalone-full.xml

by Gary Brown (JIRA)

Gary Brown created RTGOV-542: -------------------------------- Summary: Fix integration tests to use coniguration in standalone-full.xml Key: RTGOV-542 URL: https://issues.jboss.org/browse/RTGOV-542 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final Tests no longer work due to missing configuration information. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-522) Include Modeshape 3.6 only in the community assembly

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-522?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-522. ------------------------------- Resolution: Done > Include Modeshape 3.6 only in the community assembly > ---------------------------------------------------- > > Key: SRAMP-522 > URL: https://issues.jboss.org/browse/SRAMP-522 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Cross > Assignee: Brett Meyer > Fix For: 0.5.0 > > > This is related to SRAMP-493. > Rather than having to pull in two versions of modeshape even in the product version would it be possible to use a profile so that the 3.6.0 version is only required in the community distribution? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-522) Include Modeshape 3.6 only in the community assembly

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-522?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-522: ------------------------------ Summary: Include Modeshape 3.6 only in the community assembly (was: Remove Modeshape ) > Include Modeshape 3.6 only in the community assembly > ---------------------------------------------------- > > Key: SRAMP-522 > URL: https://issues.jboss.org/browse/SRAMP-522 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Cross > Assignee: Brett Meyer > Fix For: 0.5.0 > > > This is related to SRAMP-493. > Rather than having to pull in two versions of modeshape even in the product version would it be possible to use a profile so that the 3.6.0 version is only required in the community distribution? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-522) Remove Modeshape

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-522?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-522: ------------------------------ Summary: Remove Modeshape (was: Distribution and Modeshape ) > Remove Modeshape > ----------------- > > Key: SRAMP-522 > URL: https://issues.jboss.org/browse/SRAMP-522 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Cross > Assignee: Brett Meyer > Fix For: 0.5.0 > > > This is related to SRAMP-493. > Rather than having to pull in two versions of modeshape even in the product version would it be possible to use a profile so that the 3.6.0 version is only required in the community distribution? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-522) Distribution and Modeshape

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-522?page=com.atlassian.jira.plugin.... ] Work on SRAMP-522 started by Brett Meyer. > Distribution and Modeshape > --------------------------- > > Key: SRAMP-522 > URL: https://issues.jboss.org/browse/SRAMP-522 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Nick Cross > Assignee: Brett Meyer > Fix For: 0.5.0 > > > This is related to SRAMP-493. > Rather than having to pull in two versions of modeshape even in the product version would it be possible to use a profile so that the 3.6.0 version is only required in the community distribution? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 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