You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Dennis Dam (JIRA)" <je...@portals.apache.org> on 2007/04/20 09:44:15 UTC
[jira] Created: (JS2-686) Including fragments from a library
Including fragments from a library
----------------------------------
Key: JS2-686
URL: https://issues.apache.org/jira/browse/JS2-686
Project: Jetspeed 2
Issue Type: New Feature
Components: PSML
Affects Versions: 2.2-dev
Reporter: Dennis Dam
Fix For: 2.2-dev
See the mail on the user list on April 19:
On Apr 19, 2007, at 9:55 AM, Dennis Dam wrote:
> Hi all,
>
> Is it possible to have fragment libraries, which can be imported from the other PSMLs? What I'm looking for is *including* a collection of fragments with one statement. I found in a previous project that I was copying fragments all the time. This practice is also bad for maintainibility, obviously. Any input would be appreciated..
>
There is no "reference" or "include" PSML tag for Jetspeed-2
If you want to create a new JIRA issue as a new feature, that would be fine
The challenge with fragment "includes" is that we still need to create unique fragment ids
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-686) Including fragments from a library
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma updated JS2-686:
--------------------------
Fix Version/s: (was: 2.2)
2.3
Moving to next "major" release 2.3 for now
> Including fragments from a library
> ----------------------------------
>
> Key: JS2-686
> URL: https://issues.apache.org/jira/browse/JS2-686
> Project: Jetspeed 2
> Issue Type: New Feature
> Components: PSML
> Affects Versions: 2.2
> Reporter: Dennis Dam
> Fix For: 2.3
>
>
> See the mail on the user list on April 19:
> On Apr 19, 2007, at 9:55 AM, Dennis Dam wrote:
> > Hi all,
> >
> > Is it possible to have fragment libraries, which can be imported from the other PSMLs? What I'm looking for is *including* a collection of fragments with one statement. I found in a previous project that I was copying fragments all the time. This practice is also bad for maintainibility, obviously. Any input would be appreciated..
> >
> There is no "reference" or "include" PSML tag for Jetspeed-2
> If you want to create a new JIRA issue as a new feature, that would be fine
> The challenge with fragment "includes" is that we still need to create unique fragment ids
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Assigned: (JS2-686) Including fragments from a library
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randy Watler reassigned JS2-686:
--------------------------------
Assignee: Randy Watler
> Including fragments from a library
> ----------------------------------
>
> Key: JS2-686
> URL: https://issues.apache.org/jira/browse/JS2-686
> Project: Jetspeed 2
> Issue Type: New Feature
> Components: PSML
> Affects Versions: 2.2.0
> Reporter: Dennis Dam
> Assignee: Randy Watler
> Fix For: 2.2.1
>
>
> See the mail on the user list on April 19:
> On Apr 19, 2007, at 9:55 AM, Dennis Dam wrote:
> > Hi all,
> >
> > Is it possible to have fragment libraries, which can be imported from the other PSMLs? What I'm looking for is *including* a collection of fragments with one statement. I found in a previous project that I was copying fragments all the time. This practice is also bad for maintainibility, obviously. Any input would be appreciated..
> >
> There is no "reference" or "include" PSML tag for Jetspeed-2
> If you want to create a new JIRA issue as a new feature, that would be fine
> The challenge with fragment "includes" is that we still need to create unique fragment ids
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-686) Including fragments from a library
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randy Watler updated JS2-686:
-----------------------------
Fix Version/s: (was: 2.2.1)
2.2.2
> Including fragments from a library
> ----------------------------------
>
> Key: JS2-686
> URL: https://issues.apache.org/jira/browse/JS2-686
> Project: Jetspeed 2
> Issue Type: New Feature
> Components: PSML
> Affects Versions: 2.2.0
> Reporter: Dennis Dam
> Assignee: Randy Watler
> Fix For: 2.2.2
>
>
> See the mail on the user list on April 19:
> On Apr 19, 2007, at 9:55 AM, Dennis Dam wrote:
> > Hi all,
> >
> > Is it possible to have fragment libraries, which can be imported from the other PSMLs? What I'm looking for is *including* a collection of fragments with one statement. I found in a previous project that I was copying fragments all the time. This practice is also bad for maintainibility, obviously. Any input would be appreciated..
> >
> There is no "reference" or "include" PSML tag for Jetspeed-2
> If you want to create a new JIRA issue as a new feature, that would be fine
> The challenge with fragment "includes" is that we still need to create unique fragment ids
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-686) Including fragments from a library
Posted by "Dennis Dam (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491907 ]
Dennis Dam commented on JS2-686:
--------------------------------
a first step might be to have a "macro" kind of inclusion of fragments, which just pastes pieces of psml in the place where the macro call is performed. This might be really helpful already for our projects.
> Including fragments from a library
> ----------------------------------
>
> Key: JS2-686
> URL: https://issues.apache.org/jira/browse/JS2-686
> Project: Jetspeed 2
> Issue Type: New Feature
> Components: PSML
> Affects Versions: 2.2-dev
> Reporter: Dennis Dam
> Fix For: 2.2-dev
>
>
> See the mail on the user list on April 19:
> On Apr 19, 2007, at 9:55 AM, Dennis Dam wrote:
> > Hi all,
> >
> > Is it possible to have fragment libraries, which can be imported from the other PSMLs? What I'm looking for is *including* a collection of fragments with one statement. I found in a previous project that I was copying fragments all the time. This practice is also bad for maintainibility, obviously. Any input would be appreciated..
> >
> There is no "reference" or "include" PSML tag for Jetspeed-2
> If you want to create a new JIRA issue as a new feature, that would be fine
> The challenge with fragment "includes" is that we still need to create unique fragment ids
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Resolved: (JS2-686) Including fragments from a library
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randy Watler resolved JS2-686.
------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.2.2)
2.2.1
Supported with PSML Templating, Fragments, and Fragment References.
> Including fragments from a library
> ----------------------------------
>
> Key: JS2-686
> URL: https://issues.apache.org/jira/browse/JS2-686
> Project: Jetspeed 2
> Issue Type: New Feature
> Components: PSML
> Affects Versions: 2.2.0
> Reporter: Dennis Dam
> Assignee: Randy Watler
> Fix For: 2.2.1
>
>
> See the mail on the user list on April 19:
> On Apr 19, 2007, at 9:55 AM, Dennis Dam wrote:
> > Hi all,
> >
> > Is it possible to have fragment libraries, which can be imported from the other PSMLs? What I'm looking for is *including* a collection of fragments with one statement. I found in a previous project that I was copying fragments all the time. This practice is also bad for maintainibility, obviously. Any input would be appreciated..
> >
> There is no "reference" or "include" PSML tag for Jetspeed-2
> If you want to create a new JIRA issue as a new feature, that would be fine
> The challenge with fragment "includes" is that we still need to create unique fragment ids
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org