[jira] Created: (JETTY-358) Could maven-antrun-plugin as optional while installing?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (JETTY-358) Could maven-antrun-plugin as optional while installing?

JIRA jira@codehaus.org
Could maven-antrun-plugin as optional while installing?
-------------------------------------------------------

                 Key: JETTY-358
                 URL: http://jira.codehaus.org/browse/JETTY-358
             Project: Jetty
          Issue Type: Wish
          Components: Bayeux
            Reporter: Tuomas Kiviaho


In the newest revision, there seems to be added a maven plugin antrun plugin that accesses paths outside the project. Can the execution of plugin be made for instance profile based, so that it could be skipped while installing (or just moved to deploy phase)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (JETTY-358) Could maven-antrun-plugin as optional while installing?

JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/JETTY-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98278 ]

Jan Bartel commented on JETTY-358:
----------------------------------

Hi Tuomas,

Is the problem that when you build it from jetty-contrib that it makes a spurious lib/ext directory? Fixing that might be a little bit tricky, as several of the jetty-contrib projects are mounted into the jetty svn repository and are built as part of the normal jetty build process. I'll have a think about it and see if there is something that can be done.

regards
Jan

> Could maven-antrun-plugin as optional while installing?
> -------------------------------------------------------
>
>                 Key: JETTY-358
>                 URL: http://jira.codehaus.org/browse/JETTY-358
>             Project: Jetty
>          Issue Type: Wish
>          Components: Bayeux
>            Reporter: Tuomas Kiviaho
>
> In the newest revision, there seems to be added a maven plugin antrun plugin that accesses paths outside the project. Can the execution of plugin be made for instance profile based, so that it could be skipped while installing (or just moved to deploy phase)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Assigned: (JETTY-358) Could maven-antrun-plugin as optional while installing?

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/JETTY-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Bartel reassigned JETTY-358:
--------------------------------

    Assignee: Jan Bartel

> Could maven-antrun-plugin as optional while installing?
> -------------------------------------------------------
>
>                 Key: JETTY-358
>                 URL: http://jira.codehaus.org/browse/JETTY-358
>             Project: Jetty
>          Issue Type: Wish
>          Components: Bayeux
>            Reporter: Tuomas Kiviaho
>            Assignee: Jan Bartel
>
> In the newest revision, there seems to be added a maven plugin antrun plugin that accesses paths outside the project. Can the execution of plugin be made for instance profile based, so that it could be skipped while installing (or just moved to deploy phase)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (JETTY-358) Could maven-antrun-plugin as optional while installing?

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/JETTY-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Bartel updated JETTY-358:
-----------------------------

    Priority: Minor  (was: Major)

> Could maven-antrun-plugin as optional while installing?
> -------------------------------------------------------
>
>                 Key: JETTY-358
>                 URL: http://jira.codehaus.org/browse/JETTY-358
>             Project: Jetty
>          Issue Type: Wish
>          Components: Bayeux
>            Reporter: Tuomas Kiviaho
>            Assignee: Jan Bartel
>            Priority: Minor
>
> In the newest revision, there seems to be added a maven plugin antrun plugin that accesses paths outside the project. Can the execution of plugin be made for instance profile based, so that it could be skipped while installing (or just moved to deploy phase)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (JETTY-358) Could maven-antrun-plugin as optional while installing?

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/JETTY-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98407 ]

Tuomas Kiviaho commented on JETTY-358:
--------------------------------------

Yes, that's exactly what I was after. Thanks for clarifying the antrun purpose. A quite radical solution would be splitting the project up as api, impl, and continuation modules and have the installation gimmicks as part of (new) parent pom of these modules. I don't know how this fits into the build process or to Jetty philosophy in general.

> Could maven-antrun-plugin as optional while installing?
> -------------------------------------------------------
>
>                 Key: JETTY-358
>                 URL: http://jira.codehaus.org/browse/JETTY-358
>             Project: Jetty
>          Issue Type: Wish
>          Components: Bayeux
>            Reporter: Tuomas Kiviaho
>            Assignee: Jan Bartel
>            Priority: Minor
>
> In the newest revision, there seems to be added a maven plugin antrun plugin that accesses paths outside the project. Can the execution of plugin be made for instance profile based, so that it could be skipped while installing (or just moved to deploy phase)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (JETTY-358) Could maven-antrun-plugin as optional while installing?

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/JETTY-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tuomas Kiviaho resolved JETTY-358.
----------------------------------

    Resolution: Fixed

It seems that antrun has been removed from cometd poms so I consider this issue as fixed

> Could maven-antrun-plugin as optional while installing?
> -------------------------------------------------------
>
>                 Key: JETTY-358
>                 URL: http://jira.codehaus.org/browse/JETTY-358
>             Project: Jetty
>          Issue Type: Wish
>          Components: Bayeux
>            Reporter: Tuomas Kiviaho
>            Assignee: Jan Bartel
>            Priority: Minor
>
> In the newest revision, there seems to be added a maven plugin antrun plugin that accesses paths outside the project. Can the execution of plugin be made for instance profile based, so that it could be skipped while installing (or just moved to deploy phase)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss